Executive summary
kodlamaio-projects/nArchitecture is rated At risk because critical security findings are open, most of them in the packages it uses. Its score is held back because we found no encryption of stored data, no key vault and no enforced HTTPS and no access checks on the code's endpoints or handlers. It scores 39 out of 100, which the At risk rating leaves unchanged.
Security and Compliance, at 18, is the weakest lens and counts most in the score. The best first step for the work it takes is recording design decisions, worth about 6 points. Encrypting the sensitive stored data and keeping its keys in a vault would lift Security and Compliance itself, worth about 10 points. Raising Security and Compliance to 70 would lift the score to about 55.
Eight known security holes in the packages the code depends on can be used by attackers. Three pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Updating the vulnerable packages and pinning each tool to an exact version would close both risks.
The product code is 3,677 lines, about €3,200 to rebuild.
If Security and Compliance rose from 18 to 70, the lowest score rated Strong, the score would rise from 39 to about 55.
New since the last survey: 1 finding
- Web-Security Posture · Secure cookie flags not detected REDACTED
Fixed since the last survey: 41 findings
- Dependency Hygiene · Vulnerable: AutoMapper
- Cancellation propagation · Async method without CancellationToken: EmailAuthenticatorShouldBeExists src/starterProject/Application/Features/Auth/Rules/AuthBusinessRules.cs
- Cancellation propagation · Async method without CancellationToken: OtpAuthenticatorShouldBeExists src/starterProject/Application/Features/Auth/Rules/AuthBusinessRules.cs
- Cancellation propagation · Async method without CancellationToken: OtpAuthenticatorThatVerifiedShouldNotBeExists src/starterProject/Application/Features/Auth/Rules/AuthBusinessRules.cs
- Cancellation propagation · Async method without CancellationToken: EmailAuthenticatorActivationKeyShouldBeExists src/starterProject/Application/Features/Auth/Rules/AuthBusinessRules.cs
- Cancellation propagation · Async method without CancellationToken: UserShouldBeExistsWhenSelected src/starterProject/Application/Features/Auth/Rules/AuthBusinessRules.cs
- Cancellation propagation · Async method without CancellationToken: UserShouldNotBeHaveAuthenticator src/starterProject/Application/Features/Auth/Rules/AuthBusinessRules.cs
- Cancellation propagation · Async method without CancellationToken: RefreshTokenShouldBeExists src/starterProject/Application/Features/Auth/Rules/AuthBusinessRules.cs
- Cancellation propagation · Async method without CancellationToken: RefreshTokenShouldBeActive src/starterProject/Application/Features/Auth/Rules/AuthBusinessRules.cs
- Cancellation propagation · Async method without CancellationToken: UserPasswordShouldBeMatch src/starterProject/Application/Features/Auth/Rules/AuthBusinessRules.cs
- Cancellation propagation · Async method without CancellationToken: OperationClaimShouldExistWhenSelected src/starterProject/Application/Features/OperationClaims/Rules/OperationClaimBusinessRules.cs
- Cancellation propagation · Async method without CancellationToken: UserOperationClaimShouldExistWhenSelected src/starterProject/Application/Features/UserOperationClaims/Rules/UserOperationClaimBusinessRules.cs
- Cancellation propagation · Async method without CancellationToken: UserOperationClaimShouldNotExistWhenSelected src/starterProject/Application/Features/UserOperationClaims/Rules/UserOperationClaimBusinessRules.cs
- Cancellation propagation · Async method without CancellationToken: UserShouldBeExistsWhenSelected src/starterProject/Application/Features/Users/Rules/UserBusinessRules.cs
- Cancellation propagation · Async method without CancellationToken: UserPasswordShouldBeMatched src/starterProject/Application/Features/Users/Rules/UserBusinessRules.cs
- Cancellation propagation · Async method without CancellationToken: EnableOtpAuthenticator REDACTED
- Cancellation propagation · Async method without CancellationToken: VerifyEmailAuthenticator REDACTED
- Cancellation propagation · Async method without CancellationToken: VerifyOtpAuthenticator REDACTED
- Cancellation propagation · Async method without CancellationToken: GetById REDACTED
- Cancellation propagation · Async method without CancellationToken: GetList REDACTED
- Cancellation propagation · Async method without CancellationToken: Add REDACTED
- Cancellation propagation · Async method without CancellationToken: Update REDACTED
- Cancellation propagation · Async method without CancellationToken: Delete REDACTED
- Cancellation propagation · Async method without CancellationToken: GetById REDACTED
- Cancellation propagation · Async method without CancellationToken: GetList REDACTED
- Cancellation propagation · Async method without CancellationToken: Add REDACTED
- Cancellation propagation · Async method without CancellationToken: Update REDACTED
- Cancellation propagation · Async method without CancellationToken: Delete REDACTED
- Cancellation propagation · Async method without CancellationToken: GetById REDACTED
- Cancellation propagation · Async method without CancellationToken: GetFromAuth REDACTED
- Cancellation propagation · Async method without CancellationToken: GetList REDACTED
- Cancellation propagation · Async method without CancellationToken: Add REDACTED
- Cancellation propagation · Async method without CancellationToken: Update REDACTED
- Cancellation propagation · Async method without CancellationToken: UpdateFromAuth REDACTED
- Cancellation propagation · Async method without CancellationToken: Delete REDACTED
- Cancellation propagation · Async method without CancellationToken: UploadAsync src/starterProject/Infrastructure/Adapters/ImageService/CloudinaryImageServiceAdapter.cs
- Cancellation propagation · Async method drops its CancellationToken: Handle src/starterProject/Application/Features/Auth/Commands/Register/RegisterCommand.cs
- Cancellation propagation · Async method drops its CancellationToken: Handle src/starterProject/Application/Features/OperationClaims/Commands/Create/CreateOperationClaimCommand.cs
- Cancellation propagation · Async method drops its CancellationToken: Handle src/starterProject/Application/Features/UserOperationClaims/Commands/Create/CreateUserOperationClaimCommand.cs
- Cancellation propagation · Async method drops its CancellationToken: Handle src/starterProject/Application/Features/UserOperationClaims/Queries/GetList/GetListUserOperationClaimQuery.cs
- Cancellation propagation · Async method drops its CancellationToken: Handle src/starterProject/Application/Features/Users/Commands/Create/CreateUserCommand.cs
Rebuild cost: about €3,200 · Estimate
| Cost to rebuild | €1,100 to €5,300, for 18 to 56 hours of work, under 0.1 person-years for one engineer |
|---|---|
| Difficulty of the problem | Standard, 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 39. 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: 3,677 lines of product code, of which 54% is declarations and boilerplate, 41% straight logic and 4% logic with branches |
| Comment lines | The estimate prices 3,676 lines. Comment lines count towards the size of 3,677 lines but aren't priced as work. |
| What it is not | Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one. |
Top priorities
Diagnosis: what the measurements show together
Architecture — module dependency graph
Architecture: which parts of the code depend on which
| uses → | 1 Application.Services.ImageService | 2 Domain.Entities | 3 Application.Services.Repositories | 4 Infrastructure.Adapters.ImageService | 5 Persistence.Contexts | 6 Application.Features.Auth.Rules | 7 Application.Features.OperationClaims.Queries.GetList | 8 Application.Features.OperationClaims.Rules | 9 Application.Features.UserOperationClaims.Queries.GetList | 10 Application.Features.UserOperationClaims.Rules | 11 Application.Features.Users.Queries.GetList | 12 Application.Features.Users.Rules | 13 Application.Services.AuthService | 14 Application.Services.AuthenticatorService | 15 Persistence.Repositories | 16 Application.Features.Auth.Commands.Register | 17 Application.Features.Auth.Commands.RevokeToken | 18 Application.Features.Auth.Commands.VerifyEmailAuthenticator | 19 Application.Features.OperationClaims.Commands.Create | 20 Application.Features.OperationClaims.Commands.Delete | 21 Application.Features.OperationClaims.Commands.Update | 22 Application.Features.OperationClaims.Queries.GetById | 23 Application.Features.UserOperationClaims.Commands.Create | 24 Application.Features.UserOperationClaims.Commands.Delete | 25 Application.Features.UserOperationClaims.Commands.Update | 26 Application.Features.UserOperationClaims.Queries.GetById | 27 Application.Features.Users.Commands.Create | 28 Application.Features.Users.Commands.Delete | 29 Application.Features.Users.Commands.Update | 30 Application.Features.Users.Commands.UpdateFromAuth | 31 Application.Features.Users.Queries.GetById | 32 Application.Services.OperationClaims | 33 Application.Services.UserOperationClaims | 34 Application.Services.UsersService | 35 Application.Features.Auth.Commands.EnableEmailAuthenticator | 36 Application.Features.Auth.Commands.EnableOtpAuthenticator | 37 Application.Features.Auth.Commands.Login | 38 Application.Features.Auth.Commands.RefreshToken | 39 Application.Features.Auth.Commands.VerifyOtpAuthenticator | 40 WebAPI.Controllers |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 Application.Services.ImageService | ||||||||||||||||||||||||||||||||||||||||
| 2 Domain.Entities | ||||||||||||||||||||||||||||||||||||||||
| 3 Application.Services.Repositories | 2 | |||||||||||||||||||||||||||||||||||||||
| 4 Infrastructure.Adapters.ImageService | 1 | |||||||||||||||||||||||||||||||||||||||
| 5 Persistence.Contexts | 6 | |||||||||||||||||||||||||||||||||||||||
| 6 Application.Features.Auth.Rules | 4 | 1 | ||||||||||||||||||||||||||||||||||||||
| 7 Application.Features.OperationClaims.Queries.GetList | 1 | |||||||||||||||||||||||||||||||||||||||
| 8 Application.Features.OperationClaims.Rules | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 9 Application.Features.UserOperationClaims.Queries.GetList | 1 | |||||||||||||||||||||||||||||||||||||||
| 10 Application.Features.UserOperationClaims.Rules | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 11 Application.Features.Users.Queries.GetList | 1 | |||||||||||||||||||||||||||||||||||||||
| 12 Application.Features.Users.Rules | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 13 Application.Services.AuthService | 4 | 2 | ||||||||||||||||||||||||||||||||||||||
| 14 Application.Services.AuthenticatorService | 6 | 2 | ||||||||||||||||||||||||||||||||||||||
| 15 Persistence.Repositories | 2 | 6 | 6 | |||||||||||||||||||||||||||||||||||||
| 16 Application.Features.Auth.Commands.Register | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 17 Application.Features.Auth.Commands.RevokeToken | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 18 Application.Features.Auth.Commands.VerifyEmailAuthenticator | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 19 Application.Features.OperationClaims.Commands.Create | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 20 Application.Features.OperationClaims.Commands.Delete | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 21 Application.Features.OperationClaims.Commands.Update | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 22 Application.Features.OperationClaims.Queries.GetById | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 23 Application.Features.UserOperationClaims.Commands.Create | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 24 Application.Features.UserOperationClaims.Commands.Delete | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 25 Application.Features.UserOperationClaims.Commands.Update | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 26 Application.Features.UserOperationClaims.Queries.GetById | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 27 Application.Features.Users.Commands.Create | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 28 Application.Features.Users.Commands.Delete | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 29 Application.Features.Users.Commands.Update | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 30 Application.Features.Users.Commands.UpdateFromAuth | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 31 Application.Features.Users.Queries.GetById | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 32 Application.Services.OperationClaims | 2 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 33 Application.Services.UserOperationClaims | 2 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 34 Application.Services.UsersService | 2 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 35 Application.Features.Auth.Commands.EnableEmailAuthenticator | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 36 Application.Features.Auth.Commands.EnableOtpAuthenticator | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 37 Application.Features.Auth.Commands.Login | 1 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 38 Application.Features.Auth.Commands.RefreshToken | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 39 Application.Features.Auth.Commands.VerifyOtpAuthenticator | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 40 WebAPI.Controllers | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 |
3→2 Application.Services.Repositories uses Domain.Entities✕
- Connections
- 2 pairs of types, where a type in Application.Services.Repositories uses a type in Domain.Entities.
- The types involved
Application.Services.Repositories.IRefreshTokenRepository→Domain.Entities.RefreshTokenApplication.Services.Repositories.IUserOperationClaimRepository→Domain.Entities.OperationClaim
- Direction
- Application.Services.Repositories uses Domain.Entities, so a change to Domain.Entities can break Application.Services.Repositories, while a change to Application.Services.Repositories can't break Domain.Entities.
- Position
- Below the diagonal: Application.Services.Repositories uses a module listed above it, which is the healthy direction.
4→1 Infrastructure.Adapters.ImageService uses Application.Services.ImageService✕
- Connections
- 1 pair of types, where a type in Infrastructure.Adapters.ImageService uses a type in Application.Services.ImageService.
- The types involved
Infrastructure.Adapters.ImageService.CloudinaryImageServiceAdapter→Application.Services.ImageService.ImageServiceBase
- Direction
- Infrastructure.Adapters.ImageService uses Application.Services.ImageService, so a change to Application.Services.ImageService can break Infrastructure.Adapters.ImageService, while a change to Infrastructure.Adapters.ImageService can't break Application.Services.ImageService.
- Position
- Below the diagonal: Infrastructure.Adapters.ImageService uses a module listed above it, which is the healthy direction.
5→2 Persistence.Contexts uses Domain.Entities✕
- Connections
- 6 pairs of types, where a type in Persistence.Contexts uses a type in Domain.Entities.
- The types involved
Persistence.Contexts.BaseDbContext→Domain.Entities.EmailAuthenticatorPersistence.Contexts.BaseDbContext→Domain.Entities.OperationClaimPersistence.Contexts.BaseDbContext→Domain.Entities.OtpAuthenticatorPersistence.Contexts.BaseDbContext→Domain.Entities.RefreshTokenPersistence.Contexts.BaseDbContext→Domain.Entities.UserPersistence.Contexts.BaseDbContext→Domain.Entities.UserOperationClaim
- Direction
- Persistence.Contexts uses Domain.Entities, so a change to Domain.Entities can break Persistence.Contexts, while a change to Persistence.Contexts can't break Domain.Entities.
- Position
- Below the diagonal: Persistence.Contexts uses a module listed above it, which is the healthy direction.
6→2 Application.Features.Auth.Rules uses Domain.Entities✕
- Connections
- 4 pairs of types, where a type in Application.Features.Auth.Rules uses a type in Domain.Entities.
- The types involved
Application.Features.Auth.Rules.AuthBusinessRules→Domain.Entities.EmailAuthenticatorApplication.Features.Auth.Rules.AuthBusinessRules→Domain.Entities.OtpAuthenticatorApplication.Features.Auth.Rules.AuthBusinessRules→Domain.Entities.RefreshTokenApplication.Features.Auth.Rules.AuthBusinessRules→Domain.Entities.User
- Direction
- Application.Features.Auth.Rules uses Domain.Entities, so a change to Domain.Entities can break Application.Features.Auth.Rules, while a change to Application.Features.Auth.Rules can't break Domain.Entities.
- Position
- Below the diagonal: Application.Features.Auth.Rules uses a module listed above it, which is the healthy direction.
6→3 Application.Features.Auth.Rules uses Application.Services.Repositories✕
- Connections
- 1 pair of types, where a type in Application.Features.Auth.Rules uses a type in Application.Services.Repositories.
- The types involved
Application.Features.Auth.Rules.AuthBusinessRules→Application.Services.Repositories.IUserRepository
- Direction
- Application.Features.Auth.Rules uses Application.Services.Repositories, so a change to Application.Services.Repositories can break Application.Features.Auth.Rules, while a change to Application.Features.Auth.Rules can't break Application.Services.Repositories.
- Position
- Below the diagonal: Application.Features.Auth.Rules uses a module listed above it, which is the healthy direction.
7→3 Application.Features.OperationClaims.Queries.GetList uses Application.Services.Repositories✕
- Connections
- 1 pair of types, where a type in Application.Features.OperationClaims.Queries.GetList uses a type in Application.Services.Repositories.
- The types involved
Application.Features.OperationClaims.Queries.GetList.GetListOperationClaimQueryHandler→Application.Services.Repositories.IOperationClaimRepository
- Direction
- Application.Features.OperationClaims.Queries.GetList uses Application.Services.Repositories, so a change to Application.Services.Repositories can break Application.Features.OperationClaims.Queries.GetList, while a change to Application.Features.OperationClaims.Queries.GetList can't break Application.Services.Repositories.
- Position
- Below the diagonal: Application.Features.OperationClaims.Queries.GetList uses a module listed above it, which is the healthy direction.
8→2 Application.Features.OperationClaims.Rules uses Domain.Entities✕
- Connections
- 1 pair of types, where a type in Application.Features.OperationClaims.Rules uses a type in Domain.Entities.
- The types involved
Application.Features.OperationClaims.Rules.OperationClaimBusinessRules→Domain.Entities.OperationClaim
- Direction
- Application.Features.OperationClaims.Rules uses Domain.Entities, so a change to Domain.Entities can break Application.Features.OperationClaims.Rules, while a change to Application.Features.OperationClaims.Rules can't break Domain.Entities.
- Position
- Below the diagonal: Application.Features.OperationClaims.Rules uses a module listed above it, which is the healthy direction.
8→3 Application.Features.OperationClaims.Rules uses Application.Services.Repositories✕
- Connections
- 1 pair of types, where a type in Application.Features.OperationClaims.Rules uses a type in Application.Services.Repositories.
- The types involved
Application.Features.OperationClaims.Rules.OperationClaimBusinessRules→Application.Services.Repositories.IOperationClaimRepository
- Direction
- Application.Features.OperationClaims.Rules uses Application.Services.Repositories, so a change to Application.Services.Repositories can break Application.Features.OperationClaims.Rules, while a change to Application.Features.OperationClaims.Rules can't break Application.Services.Repositories.
- Position
- Below the diagonal: Application.Features.OperationClaims.Rules uses a module listed above it, which is the healthy direction.
9→3 Application.Features.UserOperationClaims.Queries.GetList uses Application.Services.Repositories✕
- Connections
- 1 pair of types, where a type in Application.Features.UserOperationClaims.Queries.GetList uses a type in Application.Services.Repositories.
- The types involved
Application.Features.UserOperationClaims.Queries.GetList.GetListUserOperationClaimQueryHandler→Application.Services.Repositories.IUserOperationClaimRepository
- Direction
- Application.Features.UserOperationClaims.Queries.GetList uses Application.Services.Repositories, so a change to Application.Services.Repositories can break Application.Features.UserOperationClaims.Queries.GetList, while a change to Application.Features.UserOperationClaims.Queries.GetList can't break Application.Services.Repositories.
- Position
- Below the diagonal: Application.Features.UserOperationClaims.Queries.GetList uses a module listed above it, which is the healthy direction.
10→2 Application.Features.UserOperationClaims.Rules uses Domain.Entities✕
- Connections
- 1 pair of types, where a type in Application.Features.UserOperationClaims.Rules uses a type in Domain.Entities.
- The types involved
Application.Features.UserOperationClaims.Rules.UserOperationClaimBusinessRules→Domain.Entities.UserOperationClaim
- Direction
- Application.Features.UserOperationClaims.Rules uses Domain.Entities, so a change to Domain.Entities can break Application.Features.UserOperationClaims.Rules, while a change to Application.Features.UserOperationClaims.Rules can't break Domain.Entities.
- Position
- Below the diagonal: Application.Features.UserOperationClaims.Rules uses a module listed above it, which is the healthy direction.
10→3 Application.Features.UserOperationClaims.Rules uses Application.Services.Repositories✕
- Connections
- 1 pair of types, where a type in Application.Features.UserOperationClaims.Rules uses a type in Application.Services.Repositories.
- The types involved
Application.Features.UserOperationClaims.Rules.UserOperationClaimBusinessRules→Application.Services.Repositories.IUserOperationClaimRepository
- Direction
- Application.Features.UserOperationClaims.Rules uses Application.Services.Repositories, so a change to Application.Services.Repositories can break Application.Features.UserOperationClaims.Rules, while a change to Application.Features.UserOperationClaims.Rules can't break Application.Services.Repositories.
- Position
- Below the diagonal: Application.Features.UserOperationClaims.Rules uses a module listed above it, which is the healthy direction.
11→3 Application.Features.Users.Queries.GetList uses Application.Services.Repositories✕
- Connections
- 1 pair of types, where a type in Application.Features.Users.Queries.GetList uses a type in Application.Services.Repositories.
- The types involved
Application.Features.Users.Queries.GetList.GetListUserQueryHandler→Application.Services.Repositories.IUserRepository
- Direction
- Application.Features.Users.Queries.GetList uses Application.Services.Repositories, so a change to Application.Services.Repositories can break Application.Features.Users.Queries.GetList, while a change to Application.Features.Users.Queries.GetList can't break Application.Services.Repositories.
- Position
- Below the diagonal: Application.Features.Users.Queries.GetList uses a module listed above it, which is the healthy direction.
12→2 Application.Features.Users.Rules uses Domain.Entities✕
- Connections
- 1 pair of types, where a type in Application.Features.Users.Rules uses a type in Domain.Entities.
- The types involved
Application.Features.Users.Rules.UserBusinessRules→Domain.Entities.User
- Direction
- Application.Features.Users.Rules uses Domain.Entities, so a change to Domain.Entities can break Application.Features.Users.Rules, while a change to Application.Features.Users.Rules can't break Domain.Entities.
- Position
- Below the diagonal: Application.Features.Users.Rules uses a module listed above it, which is the healthy direction.
12→3 Application.Features.Users.Rules uses Application.Services.Repositories✕
- Connections
- 1 pair of types, where a type in Application.Features.Users.Rules uses a type in Application.Services.Repositories.
- The types involved
Application.Features.Users.Rules.UserBusinessRules→Application.Services.Repositories.IUserRepository
- Direction
- Application.Features.Users.Rules uses Application.Services.Repositories, so a change to Application.Services.Repositories can break Application.Features.Users.Rules, while a change to Application.Features.Users.Rules can't break Application.Services.Repositories.
- Position
- Below the diagonal: Application.Features.Users.Rules uses a module listed above it, which is the healthy direction.
13→2 Application.Services.AuthService uses Domain.Entities✕
- Connections
- 4 pairs of types, where a type in Application.Services.AuthService uses a type in Domain.Entities.
- The types involved
Application.Services.AuthService.AuthManager→Domain.Entities.RefreshTokenApplication.Services.AuthService.AuthManager→Domain.Entities.UserApplication.Services.AuthService.IAuthService→Domain.Entities.RefreshTokenApplication.Services.AuthService.IAuthService→Domain.Entities.User
- Direction
- Application.Services.AuthService uses Domain.Entities, so a change to Domain.Entities can break Application.Services.AuthService, while a change to Application.Services.AuthService can't break Domain.Entities.
- Position
- Below the diagonal: Application.Services.AuthService uses a module listed above it, which is the healthy direction.
13→3 Application.Services.AuthService uses Application.Services.Repositories✕
- Connections
- 2 pairs of types, where a type in Application.Services.AuthService uses a type in Application.Services.Repositories.
- The types involved
Application.Services.AuthService.AuthManager→Application.Services.Repositories.IRefreshTokenRepositoryApplication.Services.AuthService.AuthManager→Application.Services.Repositories.IUserOperationClaimRepository
- Direction
- Application.Services.AuthService uses Application.Services.Repositories, so a change to Application.Services.Repositories can break Application.Services.AuthService, while a change to Application.Services.AuthService can't break Application.Services.Repositories.
- Position
- Below the diagonal: Application.Services.AuthService uses a module listed above it, which is the healthy direction.
14→2 Application.Services.AuthenticatorService uses Domain.Entities✕
- Connections
- 6 pairs of types, where a type in Application.Services.AuthenticatorService uses a type in Domain.Entities.
- The types involved
Application.Services.AuthenticatorService.AuthenticatorManager→Domain.Entities.EmailAuthenticatorApplication.Services.AuthenticatorService.AuthenticatorManager→Domain.Entities.OtpAuthenticatorApplication.Services.AuthenticatorService.AuthenticatorManager→Domain.Entities.UserApplication.Services.AuthenticatorService.IAuthenticatorService→Domain.Entities.EmailAuthenticatorApplication.Services.AuthenticatorService.IAuthenticatorService→Domain.Entities.OtpAuthenticatorApplication.Services.AuthenticatorService.IAuthenticatorService→Domain.Entities.User
- Direction
- Application.Services.AuthenticatorService uses Domain.Entities, so a change to Domain.Entities can break Application.Services.AuthenticatorService, while a change to Application.Services.AuthenticatorService can't break Domain.Entities.
- Position
- Below the diagonal: Application.Services.AuthenticatorService uses a module listed above it, which is the healthy direction.
14→3 Application.Services.AuthenticatorService uses Application.Services.Repositories✕
- Connections
- 2 pairs of types, where a type in Application.Services.AuthenticatorService uses a type in Application.Services.Repositories.
- The types involved
Application.Services.AuthenticatorService.AuthenticatorManager→Application.Services.Repositories.IEmailAuthenticatorRepositoryApplication.Services.AuthenticatorService.AuthenticatorManager→Application.Services.Repositories.IOtpAuthenticatorRepository
- Direction
- Application.Services.AuthenticatorService uses Application.Services.Repositories, so a change to Application.Services.Repositories can break Application.Services.AuthenticatorService, while a change to Application.Services.AuthenticatorService can't break Application.Services.Repositories.
- Position
- Below the diagonal: Application.Services.AuthenticatorService uses a module listed above it, which is the healthy direction.
15→2 Persistence.Repositories uses Domain.Entities✕
- Connections
- 2 pairs of types, where a type in Persistence.Repositories uses a type in Domain.Entities.
- The types involved
Persistence.Repositories.RefreshTokenRepository→Domain.Entities.RefreshTokenPersistence.Repositories.UserOperationClaimRepository→Domain.Entities.OperationClaim
- Direction
- Persistence.Repositories uses Domain.Entities, so a change to Domain.Entities can break Persistence.Repositories, while a change to Persistence.Repositories can't break Domain.Entities.
- Position
- Below the diagonal: Persistence.Repositories uses a module listed above it, which is the healthy direction.
15→3 Persistence.Repositories uses Application.Services.Repositories✕
- Connections
- 6 pairs of types, where a type in Persistence.Repositories uses a type in Application.Services.Repositories.
- The types involved
Persistence.Repositories.EmailAuthenticatorRepository→Application.Services.Repositories.IEmailAuthenticatorRepositoryPersistence.Repositories.OperationClaimRepository→Application.Services.Repositories.IOperationClaimRepositoryPersistence.Repositories.OtpAuthenticatorRepository→Application.Services.Repositories.IOtpAuthenticatorRepositoryPersistence.Repositories.RefreshTokenRepository→Application.Services.Repositories.IRefreshTokenRepositoryPersistence.Repositories.UserOperationClaimRepository→Application.Services.Repositories.IUserOperationClaimRepositoryPersistence.Repositories.UserRepository→Application.Services.Repositories.IUserRepository
- Direction
- Persistence.Repositories uses Application.Services.Repositories, so a change to Application.Services.Repositories can break Persistence.Repositories, while a change to Persistence.Repositories can't break Application.Services.Repositories.
- Position
- Below the diagonal: Persistence.Repositories uses a module listed above it, which is the healthy direction.
15→5 Persistence.Repositories uses Persistence.Contexts✕
- Connections
- 6 pairs of types, where a type in Persistence.Repositories uses a type in Persistence.Contexts.
- The types involved
Persistence.Repositories.EmailAuthenticatorRepository→Persistence.Contexts.BaseDbContextPersistence.Repositories.OperationClaimRepository→Persistence.Contexts.BaseDbContextPersistence.Repositories.OtpAuthenticatorRepository→Persistence.Contexts.BaseDbContextPersistence.Repositories.RefreshTokenRepository→Persistence.Contexts.BaseDbContextPersistence.Repositories.UserOperationClaimRepository→Persistence.Contexts.BaseDbContextPersistence.Repositories.UserRepository→Persistence.Contexts.BaseDbContext
- Direction
- Persistence.Repositories uses Persistence.Contexts, so a change to Persistence.Contexts can break Persistence.Repositories, while a change to Persistence.Repositories can't break Persistence.Contexts.
- Position
- Below the diagonal: Persistence.Repositories uses a module listed above it, which is the healthy direction.
16→2 Application.Features.Auth.Commands.Register uses Domain.Entities✕
- Connections
- 1 pair of types, where a type in Application.Features.Auth.Commands.Register uses a type in Domain.Entities.
- The types involved
Application.Features.Auth.Commands.Register.RegisteredResponse→Domain.Entities.RefreshToken
- Direction
- Application.Features.Auth.Commands.Register uses Domain.Entities, so a change to Domain.Entities can break Application.Features.Auth.Commands.Register, while a change to Application.Features.Auth.Commands.Register can't break Domain.Entities.
- Position
- Below the diagonal: Application.Features.Auth.Commands.Register uses a module listed above it, which is the healthy direction.
16→3 Application.Features.Auth.Commands.Register uses Application.Services.Repositories✕
- Connections
- 1 pair of types, where a type in Application.Features.Auth.Commands.Register uses a type in Application.Services.Repositories.
- The types involved
Application.Features.Auth.Commands.Register.RegisterCommandHandler→Application.Services.Repositories.IUserRepository
- Direction
- Application.Features.Auth.Commands.Register uses Application.Services.Repositories, so a change to Application.Services.Repositories can break Application.Features.Auth.Commands.Register, while a change to Application.Features.Auth.Commands.Register can't break Application.Services.Repositories.
- Position
- Below the diagonal: Application.Features.Auth.Commands.Register uses a module listed above it, which is the healthy direction.
16→6 Application.Features.Auth.Commands.Register uses Application.Features.Auth.Rules✕
- Connections
- 1 pair of types, where a type in Application.Features.Auth.Commands.Register uses a type in Application.Features.Auth.Rules.
- The types involved
Application.Features.Auth.Commands.Register.RegisterCommandHandler→Application.Features.Auth.Rules.AuthBusinessRules
- Direction
- Application.Features.Auth.Commands.Register uses Application.Features.Auth.Rules, so a change to Application.Features.Auth.Rules can break Application.Features.Auth.Commands.Register, while a change to Application.Features.Auth.Commands.Register can't break Application.Features.Auth.Rules.
- Position
- Below the diagonal: Application.Features.Auth.Commands.Register uses a module listed above it, which is the healthy direction.
16→13 Application.Features.Auth.Commands.Register uses Application.Services.AuthService✕
- Connections
- 1 pair of types, where a type in Application.Features.Auth.Commands.Register uses a type in Application.Services.AuthService.
- The types involved
Application.Features.Auth.Commands.Register.RegisterCommandHandler→Application.Services.AuthService.IAuthService
- Direction
- Application.Features.Auth.Commands.Register uses Application.Services.AuthService, so a change to Application.Services.AuthService can break Application.Features.Auth.Commands.Register, while a change to Application.Features.Auth.Commands.Register can't break Application.Services.AuthService.
- Position
- Below the diagonal: Application.Features.Auth.Commands.Register uses a module listed above it, which is the healthy direction.
17→6 Application.Features.Auth.Commands.RevokeToken uses Application.Features.Auth.Rules✕
- Connections
- 1 pair of types, where a type in Application.Features.Auth.Commands.RevokeToken uses a type in Application.Features.Auth.Rules.
- The types involved
Application.Features.Auth.Commands.RevokeToken.RevokeTokenCommandHandler→Application.Features.Auth.Rules.AuthBusinessRules
- Direction
- Application.Features.Auth.Commands.RevokeToken uses Application.Features.Auth.Rules, so a change to Application.Features.Auth.Rules can break Application.Features.Auth.Commands.RevokeToken, while a change to Application.Features.Auth.Commands.RevokeToken can't break Application.Features.Auth.Rules.
- Position
- Below the diagonal: Application.Features.Auth.Commands.RevokeToken uses a module listed above it, which is the healthy direction.
17→13 Application.Features.Auth.Commands.RevokeToken uses Application.Services.AuthService✕
- Connections
- 1 pair of types, where a type in Application.Features.Auth.Commands.RevokeToken uses a type in Application.Services.AuthService.
- The types involved
Application.Features.Auth.Commands.RevokeToken.RevokeTokenCommandHandler→Application.Services.AuthService.IAuthService
- Direction
- Application.Features.Auth.Commands.RevokeToken uses Application.Services.AuthService, so a change to Application.Services.AuthService can break Application.Features.Auth.Commands.RevokeToken, while a change to Application.Features.Auth.Commands.RevokeToken can't break Application.Services.AuthService.
- Position
- Below the diagonal: Application.Features.Auth.Commands.RevokeToken uses a module listed above it, which is the healthy direction.
18→3 Application.Features.Auth.Commands.VerifyEmailAuthenticator uses Application.Services.Repositories✕
- Connections
- 1 pair of types, where a type in Application.Features.Auth.Commands.VerifyEmailAuthenticator uses a type in Application.Services.Repositories.
- The types involved
Application.Features.Auth.Commands.VerifyEmailAuthenticator.VerifyEmailAuthenticatorCommandHandler→Application.Services.Repositories.IEmailAuthenticatorRepository
- Direction
- Application.Features.Auth.Commands.VerifyEmailAuthenticator uses Application.Services.Repositories, so a change to Application.Services.Repositories can break Application.Features.Auth.Commands.VerifyEmailAuthenticator, while a change to Application.Features.Auth.Commands.VerifyEmailAuthenticator can't break Application.Services.Repositories.
- Position
- Below the diagonal: Application.Features.Auth.Commands.VerifyEmailAuthenticator uses a module listed above it, which is the healthy direction.
18→6 Application.Features.Auth.Commands.VerifyEmailAuthenticator uses Application.Features.Auth.Rules✕
- Connections
- 1 pair of types, where a type in Application.Features.Auth.Commands.VerifyEmailAuthenticator uses a type in Application.Features.Auth.Rules.
- The types involved
Application.Features.Auth.Commands.VerifyEmailAuthenticator.VerifyEmailAuthenticatorCommandHandler→Application.Features.Auth.Rules.AuthBusinessRules
- Direction
- Application.Features.Auth.Commands.VerifyEmailAuthenticator uses Application.Features.Auth.Rules, so a change to Application.Features.Auth.Rules can break Application.Features.Auth.Commands.VerifyEmailAuthenticator, while a change to Application.Features.Auth.Commands.VerifyEmailAuthenticator can't break Application.Features.Auth.Rules.
- Position
- Below the diagonal: Application.Features.Auth.Commands.VerifyEmailAuthenticator uses a module listed above it, which is the healthy direction.
19→3 Application.Features.OperationClaims.Commands.Create uses Application.Services.Repositories✕
- Connections
- 1 pair of types, where a type in Application.Features.OperationClaims.Commands.Create uses a type in Application.Services.Repositories.
- The types involved
Application.Features.OperationClaims.Commands.Create.CreateOperationClaimCommandHandler→Application.Services.Repositories.IOperationClaimRepository
- Direction
- Application.Features.OperationClaims.Commands.Create uses Application.Services.Repositories, so a change to Application.Services.Repositories can break Application.Features.OperationClaims.Commands.Create, while a change to Application.Features.OperationClaims.Commands.Create can't break Application.Services.Repositories.
- Position
- Below the diagonal: Application.Features.OperationClaims.Commands.Create uses a module listed above it, which is the healthy direction.
19→8 Application.Features.OperationClaims.Commands.Create uses Application.Features.OperationClaims.Rules✕
- Connections
- 1 pair of types, where a type in Application.Features.OperationClaims.Commands.Create uses a type in Application.Features.OperationClaims.Rules.
- The types involved
Application.Features.OperationClaims.Commands.Create.CreateOperationClaimCommandHandler→Application.Features.OperationClaims.Rules.OperationClaimBusinessRules
- Direction
- Application.Features.OperationClaims.Commands.Create uses Application.Features.OperationClaims.Rules, so a change to Application.Features.OperationClaims.Rules can break Application.Features.OperationClaims.Commands.Create, while a change to Application.Features.OperationClaims.Commands.Create can't break Application.Features.OperationClaims.Rules.
- Position
- Below the diagonal: Application.Features.OperationClaims.Commands.Create uses a module listed above it, which is the healthy direction.
20→3 Application.Features.OperationClaims.Commands.Delete uses Application.Services.Repositories✕
- Connections
- 1 pair of types, where a type in Application.Features.OperationClaims.Commands.Delete uses a type in Application.Services.Repositories.
- The types involved
Application.Features.OperationClaims.Commands.Delete.DeleteOperationClaimCommandHandler→Application.Services.Repositories.IOperationClaimRepository
- Direction
- Application.Features.OperationClaims.Commands.Delete uses Application.Services.Repositories, so a change to Application.Services.Repositories can break Application.Features.OperationClaims.Commands.Delete, while a change to Application.Features.OperationClaims.Commands.Delete can't break Application.Services.Repositories.
- Position
- Below the diagonal: Application.Features.OperationClaims.Commands.Delete uses a module listed above it, which is the healthy direction.
20→8 Application.Features.OperationClaims.Commands.Delete uses Application.Features.OperationClaims.Rules✕
- Connections
- 1 pair of types, where a type in Application.Features.OperationClaims.Commands.Delete uses a type in Application.Features.OperationClaims.Rules.
- The types involved
Application.Features.OperationClaims.Commands.Delete.DeleteOperationClaimCommandHandler→Application.Features.OperationClaims.Rules.OperationClaimBusinessRules
- Direction
- Application.Features.OperationClaims.Commands.Delete uses Application.Features.OperationClaims.Rules, so a change to Application.Features.OperationClaims.Rules can break Application.Features.OperationClaims.Commands.Delete, while a change to Application.Features.OperationClaims.Commands.Delete can't break Application.Features.OperationClaims.Rules.
- Position
- Below the diagonal: Application.Features.OperationClaims.Commands.Delete uses a module listed above it, which is the healthy direction.
21→3 Application.Features.OperationClaims.Commands.Update uses Application.Services.Repositories✕
- Connections
- 1 pair of types, where a type in Application.Features.OperationClaims.Commands.Update uses a type in Application.Services.Repositories.
- The types involved
Application.Features.OperationClaims.Commands.Update.UpdateOperationClaimCommandHandler→Application.Services.Repositories.IOperationClaimRepository
- Direction
- Application.Features.OperationClaims.Commands.Update uses Application.Services.Repositories, so a change to Application.Services.Repositories can break Application.Features.OperationClaims.Commands.Update, while a change to Application.Features.OperationClaims.Commands.Update can't break Application.Services.Repositories.
- Position
- Below the diagonal: Application.Features.OperationClaims.Commands.Update uses a module listed above it, which is the healthy direction.
21→8 Application.Features.OperationClaims.Commands.Update uses Application.Features.OperationClaims.Rules✕
- Connections
- 1 pair of types, where a type in Application.Features.OperationClaims.Commands.Update uses a type in Application.Features.OperationClaims.Rules.
- The types involved
Application.Features.OperationClaims.Commands.Update.UpdateOperationClaimCommandHandler→Application.Features.OperationClaims.Rules.OperationClaimBusinessRules
- Direction
- Application.Features.OperationClaims.Commands.Update uses Application.Features.OperationClaims.Rules, so a change to Application.Features.OperationClaims.Rules can break Application.Features.OperationClaims.Commands.Update, while a change to Application.Features.OperationClaims.Commands.Update can't break Application.Features.OperationClaims.Rules.
- Position
- Below the diagonal: Application.Features.OperationClaims.Commands.Update uses a module listed above it, which is the healthy direction.
22→3 Application.Features.OperationClaims.Queries.GetById uses Application.Services.Repositories✕
- Connections
- 1 pair of types, where a type in Application.Features.OperationClaims.Queries.GetById uses a type in Application.Services.Repositories.
- The types involved
Application.Features.OperationClaims.Queries.GetById.GetByIdOperationClaimQueryHandler→Application.Services.Repositories.IOperationClaimRepository
- Direction
- Application.Features.OperationClaims.Queries.GetById uses Application.Services.Repositories, so a change to Application.Services.Repositories can break Application.Features.OperationClaims.Queries.GetById, while a change to Application.Features.OperationClaims.Queries.GetById can't break Application.Services.Repositories.
- Position
- Below the diagonal: Application.Features.OperationClaims.Queries.GetById uses a module listed above it, which is the healthy direction.
22→8 Application.Features.OperationClaims.Queries.GetById uses Application.Features.OperationClaims.Rules✕
- Connections
- 1 pair of types, where a type in Application.Features.OperationClaims.Queries.GetById uses a type in Application.Features.OperationClaims.Rules.
- The types involved
Application.Features.OperationClaims.Queries.GetById.GetByIdOperationClaimQueryHandler→Application.Features.OperationClaims.Rules.OperationClaimBusinessRules
- Direction
- Application.Features.OperationClaims.Queries.GetById uses Application.Features.OperationClaims.Rules, so a change to Application.Features.OperationClaims.Rules can break Application.Features.OperationClaims.Queries.GetById, while a change to Application.Features.OperationClaims.Queries.GetById can't break Application.Features.OperationClaims.Rules.
- Position
- Below the diagonal: Application.Features.OperationClaims.Queries.GetById uses a module listed above it, which is the healthy direction.
23→3 Application.Features.UserOperationClaims.Commands.Create uses Application.Services.Repositories✕
- Connections
- 1 pair of types, where a type in Application.Features.UserOperationClaims.Commands.Create uses a type in Application.Services.Repositories.
- The types involved
Application.Features.UserOperationClaims.Commands.Create.CreateUserOperationClaimCommandHandler→Application.Services.Repositories.IUserOperationClaimRepository
- Direction
- Application.Features.UserOperationClaims.Commands.Create uses Application.Services.Repositories, so a change to Application.Services.Repositories can break Application.Features.UserOperationClaims.Commands.Create, while a change to Application.Features.UserOperationClaims.Commands.Create can't break Application.Services.Repositories.
- Position
- Below the diagonal: Application.Features.UserOperationClaims.Commands.Create uses a module listed above it, which is the healthy direction.
23→10 Application.Features.UserOperationClaims.Commands.Create uses Application.Features.UserOperationClaims.Rules✕
- Connections
- 1 pair of types, where a type in Application.Features.UserOperationClaims.Commands.Create uses a type in Application.Features.UserOperationClaims.Rules.
- The types involved
Application.Features.UserOperationClaims.Commands.Create.CreateUserOperationClaimCommandHandler→Application.Features.UserOperationClaims.Rules.UserOperationClaimBusinessRules
- Direction
- Application.Features.UserOperationClaims.Commands.Create uses Application.Features.UserOperationClaims.Rules, so a change to Application.Features.UserOperationClaims.Rules can break Application.Features.UserOperationClaims.Commands.Create, while a change to Application.Features.UserOperationClaims.Commands.Create can't break Application.Features.UserOperationClaims.Rules.
- Position
- Below the diagonal: Application.Features.UserOperationClaims.Commands.Create uses a module listed above it, which is the healthy direction.
24→3 Application.Features.UserOperationClaims.Commands.Delete uses Application.Services.Repositories✕
- Connections
- 1 pair of types, where a type in Application.Features.UserOperationClaims.Commands.Delete uses a type in Application.Services.Repositories.
- The types involved
Application.Features.UserOperationClaims.Commands.Delete.DeleteUserOperationClaimCommandHandler→Application.Services.Repositories.IUserOperationClaimRepository
- Direction
- Application.Features.UserOperationClaims.Commands.Delete uses Application.Services.Repositories, so a change to Application.Services.Repositories can break Application.Features.UserOperationClaims.Commands.Delete, while a change to Application.Features.UserOperationClaims.Commands.Delete can't break Application.Services.Repositories.
- Position
- Below the diagonal: Application.Features.UserOperationClaims.Commands.Delete uses a module listed above it, which is the healthy direction.
24→10 Application.Features.UserOperationClaims.Commands.Delete uses Application.Features.UserOperationClaims.Rules✕
- Connections
- 1 pair of types, where a type in Application.Features.UserOperationClaims.Commands.Delete uses a type in Application.Features.UserOperationClaims.Rules.
- The types involved
Application.Features.UserOperationClaims.Commands.Delete.DeleteUserOperationClaimCommandHandler→Application.Features.UserOperationClaims.Rules.UserOperationClaimBusinessRules
- Direction
- Application.Features.UserOperationClaims.Commands.Delete uses Application.Features.UserOperationClaims.Rules, so a change to Application.Features.UserOperationClaims.Rules can break Application.Features.UserOperationClaims.Commands.Delete, while a change to Application.Features.UserOperationClaims.Commands.Delete can't break Application.Features.UserOperationClaims.Rules.
- Position
- Below the diagonal: Application.Features.UserOperationClaims.Commands.Delete uses a module listed above it, which is the healthy direction.
25→3 Application.Features.UserOperationClaims.Commands.Update uses Application.Services.Repositories✕
- Connections
- 1 pair of types, where a type in Application.Features.UserOperationClaims.Commands.Update uses a type in Application.Services.Repositories.
- The types involved
Application.Features.UserOperationClaims.Commands.Update.UpdateUserOperationClaimCommandHandler→Application.Services.Repositories.IUserOperationClaimRepository
- Direction
- Application.Features.UserOperationClaims.Commands.Update uses Application.Services.Repositories, so a change to Application.Services.Repositories can break Application.Features.UserOperationClaims.Commands.Update, while a change to Application.Features.UserOperationClaims.Commands.Update can't break Application.Services.Repositories.
- Position
- Below the diagonal: Application.Features.UserOperationClaims.Commands.Update uses a module listed above it, which is the healthy direction.
25→10 Application.Features.UserOperationClaims.Commands.Update uses Application.Features.UserOperationClaims.Rules✕
- Connections
- 1 pair of types, where a type in Application.Features.UserOperationClaims.Commands.Update uses a type in Application.Features.UserOperationClaims.Rules.
- The types involved
Application.Features.UserOperationClaims.Commands.Update.UpdateUserOperationClaimCommandHandler→Application.Features.UserOperationClaims.Rules.UserOperationClaimBusinessRules
- Direction
- Application.Features.UserOperationClaims.Commands.Update uses Application.Features.UserOperationClaims.Rules, so a change to Application.Features.UserOperationClaims.Rules can break Application.Features.UserOperationClaims.Commands.Update, while a change to Application.Features.UserOperationClaims.Commands.Update can't break Application.Features.UserOperationClaims.Rules.
- Position
- Below the diagonal: Application.Features.UserOperationClaims.Commands.Update uses a module listed above it, which is the healthy direction.
26→3 Application.Features.UserOperationClaims.Queries.GetById uses Application.Services.Repositories✕
- Connections
- 1 pair of types, where a type in Application.Features.UserOperationClaims.Queries.GetById uses a type in Application.Services.Repositories.
- The types involved
Application.Features.UserOperationClaims.Queries.GetById.GetByIdUserOperationClaimQueryHandler→Application.Services.Repositories.IUserOperationClaimRepository
- Direction
- Application.Features.UserOperationClaims.Queries.GetById uses Application.Services.Repositories, so a change to Application.Services.Repositories can break Application.Features.UserOperationClaims.Queries.GetById, while a change to Application.Features.UserOperationClaims.Queries.GetById can't break Application.Services.Repositories.
- Position
- Below the diagonal: Application.Features.UserOperationClaims.Queries.GetById uses a module listed above it, which is the healthy direction.
26→10 Application.Features.UserOperationClaims.Queries.GetById uses Application.Features.UserOperationClaims.Rules✕
- Connections
- 1 pair of types, where a type in Application.Features.UserOperationClaims.Queries.GetById uses a type in Application.Features.UserOperationClaims.Rules.
- The types involved
Application.Features.UserOperationClaims.Queries.GetById.GetByIdUserOperationClaimQueryHandler→Application.Features.UserOperationClaims.Rules.UserOperationClaimBusinessRules
- Direction
- Application.Features.UserOperationClaims.Queries.GetById uses Application.Features.UserOperationClaims.Rules, so a change to Application.Features.UserOperationClaims.Rules can break Application.Features.UserOperationClaims.Queries.GetById, while a change to Application.Features.UserOperationClaims.Queries.GetById can't break Application.Features.UserOperationClaims.Rules.
- Position
- Below the diagonal: Application.Features.UserOperationClaims.Queries.GetById uses a module listed above it, which is the healthy direction.
27→3 Application.Features.Users.Commands.Create uses Application.Services.Repositories✕
- Connections
- 1 pair of types, where a type in Application.Features.Users.Commands.Create uses a type in Application.Services.Repositories.
- The types involved
Application.Features.Users.Commands.Create.CreateUserCommandHandler→Application.Services.Repositories.IUserRepository
- Direction
- Application.Features.Users.Commands.Create uses Application.Services.Repositories, so a change to Application.Services.Repositories can break Application.Features.Users.Commands.Create, while a change to Application.Features.Users.Commands.Create can't break Application.Services.Repositories.
- Position
- Below the diagonal: Application.Features.Users.Commands.Create uses a module listed above it, which is the healthy direction.
27→12 Application.Features.Users.Commands.Create uses Application.Features.Users.Rules✕
- Connections
- 1 pair of types, where a type in Application.Features.Users.Commands.Create uses a type in Application.Features.Users.Rules.
- The types involved
Application.Features.Users.Commands.Create.CreateUserCommandHandler→Application.Features.Users.Rules.UserBusinessRules
- Direction
- Application.Features.Users.Commands.Create uses Application.Features.Users.Rules, so a change to Application.Features.Users.Rules can break Application.Features.Users.Commands.Create, while a change to Application.Features.Users.Commands.Create can't break Application.Features.Users.Rules.
- Position
- Below the diagonal: Application.Features.Users.Commands.Create uses a module listed above it, which is the healthy direction.
28→3 Application.Features.Users.Commands.Delete uses Application.Services.Repositories✕
- Connections
- 1 pair of types, where a type in Application.Features.Users.Commands.Delete uses a type in Application.Services.Repositories.
- The types involved
Application.Features.Users.Commands.Delete.DeleteUserCommandHandler→Application.Services.Repositories.IUserRepository
- Direction
- Application.Features.Users.Commands.Delete uses Application.Services.Repositories, so a change to Application.Services.Repositories can break Application.Features.Users.Commands.Delete, while a change to Application.Features.Users.Commands.Delete can't break Application.Services.Repositories.
- Position
- Below the diagonal: Application.Features.Users.Commands.Delete uses a module listed above it, which is the healthy direction.
28→12 Application.Features.Users.Commands.Delete uses Application.Features.Users.Rules✕
- Connections
- 1 pair of types, where a type in Application.Features.Users.Commands.Delete uses a type in Application.Features.Users.Rules.
- The types involved
Application.Features.Users.Commands.Delete.DeleteUserCommandHandler→Application.Features.Users.Rules.UserBusinessRules
- Direction
- Application.Features.Users.Commands.Delete uses Application.Features.Users.Rules, so a change to Application.Features.Users.Rules can break Application.Features.Users.Commands.Delete, while a change to Application.Features.Users.Commands.Delete can't break Application.Features.Users.Rules.
- Position
- Below the diagonal: Application.Features.Users.Commands.Delete uses a module listed above it, which is the healthy direction.
29→3 Application.Features.Users.Commands.Update uses Application.Services.Repositories✕
- Connections
- 1 pair of types, where a type in Application.Features.Users.Commands.Update uses a type in Application.Services.Repositories.
- The types involved
Application.Features.Users.Commands.Update.UpdateUserCommandHandler→Application.Services.Repositories.IUserRepository
- Direction
- Application.Features.Users.Commands.Update uses Application.Services.Repositories, so a change to Application.Services.Repositories can break Application.Features.Users.Commands.Update, while a change to Application.Features.Users.Commands.Update can't break Application.Services.Repositories.
- Position
- Below the diagonal: Application.Features.Users.Commands.Update uses a module listed above it, which is the healthy direction.
29→12 Application.Features.Users.Commands.Update uses Application.Features.Users.Rules✕
- Connections
- 1 pair of types, where a type in Application.Features.Users.Commands.Update uses a type in Application.Features.Users.Rules.
- The types involved
Application.Features.Users.Commands.Update.UpdateUserCommandHandler→Application.Features.Users.Rules.UserBusinessRules
- Direction
- Application.Features.Users.Commands.Update uses Application.Features.Users.Rules, so a change to Application.Features.Users.Rules can break Application.Features.Users.Commands.Update, while a change to Application.Features.Users.Commands.Update can't break Application.Features.Users.Rules.
- Position
- Below the diagonal: Application.Features.Users.Commands.Update uses a module listed above it, which is the healthy direction.
30→3 Application.Features.Users.Commands.UpdateFromAuth uses Application.Services.Repositories✕
- Connections
- 1 pair of types, where a type in Application.Features.Users.Commands.UpdateFromAuth uses a type in Application.Services.Repositories.
- The types involved
Application.Features.Users.Commands.UpdateFromAuth.UpdateUserFromAuthCommandHandler→Application.Services.Repositories.IUserRepository
- Direction
- Application.Features.Users.Commands.UpdateFromAuth uses Application.Services.Repositories, so a change to Application.Services.Repositories can break Application.Features.Users.Commands.UpdateFromAuth, while a change to Application.Features.Users.Commands.UpdateFromAuth can't break Application.Services.Repositories.
- Position
- Below the diagonal: Application.Features.Users.Commands.UpdateFromAuth uses a module listed above it, which is the healthy direction.
30→12 Application.Features.Users.Commands.UpdateFromAuth uses Application.Features.Users.Rules✕
- Connections
- 1 pair of types, where a type in Application.Features.Users.Commands.UpdateFromAuth uses a type in Application.Features.Users.Rules.
- The types involved
Application.Features.Users.Commands.UpdateFromAuth.UpdateUserFromAuthCommandHandler→Application.Features.Users.Rules.UserBusinessRules
- Direction
- Application.Features.Users.Commands.UpdateFromAuth uses Application.Features.Users.Rules, so a change to Application.Features.Users.Rules can break Application.Features.Users.Commands.UpdateFromAuth, while a change to Application.Features.Users.Commands.UpdateFromAuth can't break Application.Features.Users.Rules.
- Position
- Below the diagonal: Application.Features.Users.Commands.UpdateFromAuth uses a module listed above it, which is the healthy direction.
30→13 Application.Features.Users.Commands.UpdateFromAuth uses Application.Services.AuthService✕
- Connections
- 1 pair of types, where a type in Application.Features.Users.Commands.UpdateFromAuth uses a type in Application.Services.AuthService.
- The types involved
Application.Features.Users.Commands.UpdateFromAuth.UpdateUserFromAuthCommandHandler→Application.Services.AuthService.IAuthService
- Direction
- Application.Features.Users.Commands.UpdateFromAuth uses Application.Services.AuthService, so a change to Application.Services.AuthService can break Application.Features.Users.Commands.UpdateFromAuth, while a change to Application.Features.Users.Commands.UpdateFromAuth can't break Application.Services.AuthService.
- Position
- Below the diagonal: Application.Features.Users.Commands.UpdateFromAuth uses a module listed above it, which is the healthy direction.
31→3 Application.Features.Users.Queries.GetById uses Application.Services.Repositories✕
- Connections
- 1 pair of types, where a type in Application.Features.Users.Queries.GetById uses a type in Application.Services.Repositories.
- The types involved
Application.Features.Users.Queries.GetById.GetByIdUserQueryHandler→Application.Services.Repositories.IUserRepository
- Direction
- Application.Features.Users.Queries.GetById uses Application.Services.Repositories, so a change to Application.Services.Repositories can break Application.Features.Users.Queries.GetById, while a change to Application.Features.Users.Queries.GetById can't break Application.Services.Repositories.
- Position
- Below the diagonal: Application.Features.Users.Queries.GetById uses a module listed above it, which is the healthy direction.
31→12 Application.Features.Users.Queries.GetById uses Application.Features.Users.Rules✕
- Connections
- 1 pair of types, where a type in Application.Features.Users.Queries.GetById uses a type in Application.Features.Users.Rules.
- The types involved
Application.Features.Users.Queries.GetById.GetByIdUserQueryHandler→Application.Features.Users.Rules.UserBusinessRules
- Direction
- Application.Features.Users.Queries.GetById uses Application.Features.Users.Rules, so a change to Application.Features.Users.Rules can break Application.Features.Users.Queries.GetById, while a change to Application.Features.Users.Queries.GetById can't break Application.Features.Users.Rules.
- Position
- Below the diagonal: Application.Features.Users.Queries.GetById uses a module listed above it, which is the healthy direction.
32→2 Application.Services.OperationClaims uses Domain.Entities✕
- Connections
- 2 pairs of types, where a type in Application.Services.OperationClaims uses a type in Domain.Entities.
- The types involved
Application.Services.OperationClaims.IOperationClaimService→Domain.Entities.OperationClaimApplication.Services.OperationClaims.OperationClaimManager→Domain.Entities.OperationClaim
- Direction
- Application.Services.OperationClaims uses Domain.Entities, so a change to Domain.Entities can break Application.Services.OperationClaims, while a change to Application.Services.OperationClaims can't break Domain.Entities.
- Position
- Below the diagonal: Application.Services.OperationClaims uses a module listed above it, which is the healthy direction.
32→3 Application.Services.OperationClaims uses Application.Services.Repositories✕
- Connections
- 1 pair of types, where a type in Application.Services.OperationClaims uses a type in Application.Services.Repositories.
- The types involved
Application.Services.OperationClaims.OperationClaimManager→Application.Services.Repositories.IOperationClaimRepository
- Direction
- Application.Services.OperationClaims uses Application.Services.Repositories, so a change to Application.Services.Repositories can break Application.Services.OperationClaims, while a change to Application.Services.OperationClaims can't break Application.Services.Repositories.
- Position
- Below the diagonal: Application.Services.OperationClaims uses a module listed above it, which is the healthy direction.
32→8 Application.Services.OperationClaims uses Application.Features.OperationClaims.Rules✕
- Connections
- 1 pair of types, where a type in Application.Services.OperationClaims uses a type in Application.Features.OperationClaims.Rules.
- The types involved
Application.Services.OperationClaims.OperationClaimManager→Application.Features.OperationClaims.Rules.OperationClaimBusinessRules
- Direction
- Application.Services.OperationClaims uses Application.Features.OperationClaims.Rules, so a change to Application.Features.OperationClaims.Rules can break Application.Services.OperationClaims, while a change to Application.Services.OperationClaims can't break Application.Features.OperationClaims.Rules.
- Position
- Below the diagonal: Application.Services.OperationClaims uses a module listed above it, which is the healthy direction.
33→2 Application.Services.UserOperationClaims uses Domain.Entities✕
- Connections
- 2 pairs of types, where a type in Application.Services.UserOperationClaims uses a type in Domain.Entities.
- The types involved
Application.Services.UserOperationClaims.IUserOperationClaimService→Domain.Entities.UserOperationClaimApplication.Services.UserOperationClaims.UserUserOperationClaimManager→Domain.Entities.UserOperationClaim
- Direction
- Application.Services.UserOperationClaims uses Domain.Entities, so a change to Domain.Entities can break Application.Services.UserOperationClaims, while a change to Application.Services.UserOperationClaims can't break Domain.Entities.
- Position
- Below the diagonal: Application.Services.UserOperationClaims uses a module listed above it, which is the healthy direction.
33→3 Application.Services.UserOperationClaims uses Application.Services.Repositories✕
- Connections
- 1 pair of types, where a type in Application.Services.UserOperationClaims uses a type in Application.Services.Repositories.
- The types involved
Application.Services.UserOperationClaims.UserUserOperationClaimManager→Application.Services.Repositories.IUserOperationClaimRepository
- Direction
- Application.Services.UserOperationClaims uses Application.Services.Repositories, so a change to Application.Services.Repositories can break Application.Services.UserOperationClaims, while a change to Application.Services.UserOperationClaims can't break Application.Services.Repositories.
- Position
- Below the diagonal: Application.Services.UserOperationClaims uses a module listed above it, which is the healthy direction.
33→10 Application.Services.UserOperationClaims uses Application.Features.UserOperationClaims.Rules✕
- Connections
- 1 pair of types, where a type in Application.Services.UserOperationClaims uses a type in Application.Features.UserOperationClaims.Rules.
- The types involved
Application.Services.UserOperationClaims.UserUserOperationClaimManager→Application.Features.UserOperationClaims.Rules.UserOperationClaimBusinessRules
- Direction
- Application.Services.UserOperationClaims uses Application.Features.UserOperationClaims.Rules, so a change to Application.Features.UserOperationClaims.Rules can break Application.Services.UserOperationClaims, while a change to Application.Services.UserOperationClaims can't break Application.Features.UserOperationClaims.Rules.
- Position
- Below the diagonal: Application.Services.UserOperationClaims uses a module listed above it, which is the healthy direction.
34→2 Application.Services.UsersService uses Domain.Entities✕
- Connections
- 2 pairs of types, where a type in Application.Services.UsersService uses a type in Domain.Entities.
- The types involved
Application.Services.UsersService.IUserService→Domain.Entities.UserApplication.Services.UsersService.UserManager→Domain.Entities.User
- Direction
- Application.Services.UsersService uses Domain.Entities, so a change to Domain.Entities can break Application.Services.UsersService, while a change to Application.Services.UsersService can't break Domain.Entities.
- Position
- Below the diagonal: Application.Services.UsersService uses a module listed above it, which is the healthy direction.
34→3 Application.Services.UsersService uses Application.Services.Repositories✕
- Connections
- 1 pair of types, where a type in Application.Services.UsersService uses a type in Application.Services.Repositories.
- The types involved
Application.Services.UsersService.UserManager→Application.Services.Repositories.IUserRepository
- Direction
- Application.Services.UsersService uses Application.Services.Repositories, so a change to Application.Services.Repositories can break Application.Services.UsersService, while a change to Application.Services.UsersService can't break Application.Services.Repositories.
- Position
- Below the diagonal: Application.Services.UsersService uses a module listed above it, which is the healthy direction.
34→12 Application.Services.UsersService uses Application.Features.Users.Rules✕
- Connections
- 1 pair of types, where a type in Application.Services.UsersService uses a type in Application.Features.Users.Rules.
- The types involved
Application.Services.UsersService.UserManager→Application.Features.Users.Rules.UserBusinessRules
- Direction
- Application.Services.UsersService uses Application.Features.Users.Rules, so a change to Application.Features.Users.Rules can break Application.Services.UsersService, while a change to Application.Services.UsersService can't break Application.Features.Users.Rules.
- Position
- Below the diagonal: Application.Services.UsersService uses a module listed above it, which is the healthy direction.
35→3 Application.Features.Auth.Commands.EnableEmailAuthenticator uses Application.Services.Repositories✕
- Connections
- 1 pair of types, where a type in Application.Features.Auth.Commands.EnableEmailAuthenticator uses a type in Application.Services.Repositories.
- The types involved
Application.Features.Auth.Commands.EnableEmailAuthenticator.EnableEmailAuthenticatorCommandHandler→Application.Services.Repositories.IEmailAuthenticatorRepository
- Direction
- Application.Features.Auth.Commands.EnableEmailAuthenticator uses Application.Services.Repositories, so a change to Application.Services.Repositories can break Application.Features.Auth.Commands.EnableEmailAuthenticator, while a change to Application.Features.Auth.Commands.EnableEmailAuthenticator can't break Application.Services.Repositories.
- Position
- Below the diagonal: Application.Features.Auth.Commands.EnableEmailAuthenticator uses a module listed above it, which is the healthy direction.
35→6 Application.Features.Auth.Commands.EnableEmailAuthenticator uses Application.Features.Auth.Rules✕
- Connections
- 1 pair of types, where a type in Application.Features.Auth.Commands.EnableEmailAuthenticator uses a type in Application.Features.Auth.Rules.
- The types involved
Application.Features.Auth.Commands.EnableEmailAuthenticator.EnableEmailAuthenticatorCommandHandler→Application.Features.Auth.Rules.AuthBusinessRules
- Direction
- Application.Features.Auth.Commands.EnableEmailAuthenticator uses Application.Features.Auth.Rules, so a change to Application.Features.Auth.Rules can break Application.Features.Auth.Commands.EnableEmailAuthenticator, while a change to Application.Features.Auth.Commands.EnableEmailAuthenticator can't break Application.Features.Auth.Rules.
- Position
- Below the diagonal: Application.Features.Auth.Commands.EnableEmailAuthenticator uses a module listed above it, which is the healthy direction.
35→14 Application.Features.Auth.Commands.EnableEmailAuthenticator uses Application.Services.AuthenticatorService✕
- Connections
- 1 pair of types, where a type in Application.Features.Auth.Commands.EnableEmailAuthenticator uses a type in Application.Services.AuthenticatorService.
- The types involved
Application.Features.Auth.Commands.EnableEmailAuthenticator.EnableEmailAuthenticatorCommandHandler→Application.Services.AuthenticatorService.IAuthenticatorService
- Direction
- Application.Features.Auth.Commands.EnableEmailAuthenticator uses Application.Services.AuthenticatorService, so a change to Application.Services.AuthenticatorService can break Application.Features.Auth.Commands.EnableEmailAuthenticator, while a change to Application.Features.Auth.Commands.EnableEmailAuthenticator can't break Application.Services.AuthenticatorService.
- Position
- Below the diagonal: Application.Features.Auth.Commands.EnableEmailAuthenticator uses a module listed above it, which is the healthy direction.
35→34 Application.Features.Auth.Commands.EnableEmailAuthenticator uses Application.Services.UsersService✕
- Connections
- 1 pair of types, where a type in Application.Features.Auth.Commands.EnableEmailAuthenticator uses a type in Application.Services.UsersService.
- The types involved
Application.Features.Auth.Commands.EnableEmailAuthenticator.EnableEmailAuthenticatorCommandHandler→Application.Services.UsersService.IUserService
- Direction
- Application.Features.Auth.Commands.EnableEmailAuthenticator uses Application.Services.UsersService, so a change to Application.Services.UsersService can break Application.Features.Auth.Commands.EnableEmailAuthenticator, while a change to Application.Features.Auth.Commands.EnableEmailAuthenticator can't break Application.Services.UsersService.
- Position
- Below the diagonal: Application.Features.Auth.Commands.EnableEmailAuthenticator uses a module listed above it, which is the healthy direction.
36→3 Application.Features.Auth.Commands.EnableOtpAuthenticator uses Application.Services.Repositories✕
- Connections
- 1 pair of types, where a type in Application.Features.Auth.Commands.EnableOtpAuthenticator uses a type in Application.Services.Repositories.
- The types involved
Application.Features.Auth.Commands.EnableOtpAuthenticator.EnableOtpAuthenticatorCommandHandler→Application.Services.Repositories.IOtpAuthenticatorRepository
- Direction
- Application.Features.Auth.Commands.EnableOtpAuthenticator uses Application.Services.Repositories, so a change to Application.Services.Repositories can break Application.Features.Auth.Commands.EnableOtpAuthenticator, while a change to Application.Features.Auth.Commands.EnableOtpAuthenticator can't break Application.Services.Repositories.
- Position
- Below the diagonal: Application.Features.Auth.Commands.EnableOtpAuthenticator uses a module listed above it, which is the healthy direction.
36→6 Application.Features.Auth.Commands.EnableOtpAuthenticator uses Application.Features.Auth.Rules✕
- Connections
- 1 pair of types, where a type in Application.Features.Auth.Commands.EnableOtpAuthenticator uses a type in Application.Features.Auth.Rules.
- The types involved
Application.Features.Auth.Commands.EnableOtpAuthenticator.EnableOtpAuthenticatorCommandHandler→Application.Features.Auth.Rules.AuthBusinessRules
- Direction
- Application.Features.Auth.Commands.EnableOtpAuthenticator uses Application.Features.Auth.Rules, so a change to Application.Features.Auth.Rules can break Application.Features.Auth.Commands.EnableOtpAuthenticator, while a change to Application.Features.Auth.Commands.EnableOtpAuthenticator can't break Application.Features.Auth.Rules.
- Position
- Below the diagonal: Application.Features.Auth.Commands.EnableOtpAuthenticator uses a module listed above it, which is the healthy direction.
36→14 Application.Features.Auth.Commands.EnableOtpAuthenticator uses Application.Services.AuthenticatorService✕
- Connections
- 1 pair of types, where a type in Application.Features.Auth.Commands.EnableOtpAuthenticator uses a type in Application.Services.AuthenticatorService.
- The types involved
Application.Features.Auth.Commands.EnableOtpAuthenticator.EnableOtpAuthenticatorCommandHandler→Application.Services.AuthenticatorService.IAuthenticatorService
- Direction
- Application.Features.Auth.Commands.EnableOtpAuthenticator uses Application.Services.AuthenticatorService, so a change to Application.Services.AuthenticatorService can break Application.Features.Auth.Commands.EnableOtpAuthenticator, while a change to Application.Features.Auth.Commands.EnableOtpAuthenticator can't break Application.Services.AuthenticatorService.
- Position
- Below the diagonal: Application.Features.Auth.Commands.EnableOtpAuthenticator uses a module listed above it, which is the healthy direction.
36→34 Application.Features.Auth.Commands.EnableOtpAuthenticator uses Application.Services.UsersService✕
- Connections
- 1 pair of types, where a type in Application.Features.Auth.Commands.EnableOtpAuthenticator uses a type in Application.Services.UsersService.
- The types involved
Application.Features.Auth.Commands.EnableOtpAuthenticator.EnableOtpAuthenticatorCommandHandler→Application.Services.UsersService.IUserService
- Direction
- Application.Features.Auth.Commands.EnableOtpAuthenticator uses Application.Services.UsersService, so a change to Application.Services.UsersService can break Application.Features.Auth.Commands.EnableOtpAuthenticator, while a change to Application.Features.Auth.Commands.EnableOtpAuthenticator can't break Application.Services.UsersService.
- Position
- Below the diagonal: Application.Features.Auth.Commands.EnableOtpAuthenticator uses a module listed above it, which is the healthy direction.
37→2 Application.Features.Auth.Commands.Login uses Domain.Entities✕
- Connections
- 1 pair of types, where a type in Application.Features.Auth.Commands.Login uses a type in Domain.Entities.
- The types involved
Application.Features.Auth.Commands.Login.LoggedResponse→Domain.Entities.RefreshToken
- Direction
- Application.Features.Auth.Commands.Login uses Domain.Entities, so a change to Domain.Entities can break Application.Features.Auth.Commands.Login, while a change to Application.Features.Auth.Commands.Login can't break Domain.Entities.
- Position
- Below the diagonal: Application.Features.Auth.Commands.Login uses a module listed above it, which is the healthy direction.
37→6 Application.Features.Auth.Commands.Login uses Application.Features.Auth.Rules✕
- Connections
- 1 pair of types, where a type in Application.Features.Auth.Commands.Login uses a type in Application.Features.Auth.Rules.
- The types involved
Application.Features.Auth.Commands.Login.LoginCommandHandler→Application.Features.Auth.Rules.AuthBusinessRules
- Direction
- Application.Features.Auth.Commands.Login uses Application.Features.Auth.Rules, so a change to Application.Features.Auth.Rules can break Application.Features.Auth.Commands.Login, while a change to Application.Features.Auth.Commands.Login can't break Application.Features.Auth.Rules.
- Position
- Below the diagonal: Application.Features.Auth.Commands.Login uses a module listed above it, which is the healthy direction.
37→13 Application.Features.Auth.Commands.Login uses Application.Services.AuthService✕
- Connections
- 1 pair of types, where a type in Application.Features.Auth.Commands.Login uses a type in Application.Services.AuthService.
- The types involved
Application.Features.Auth.Commands.Login.LoginCommandHandler→Application.Services.AuthService.IAuthService
- Direction
- Application.Features.Auth.Commands.Login uses Application.Services.AuthService, so a change to Application.Services.AuthService can break Application.Features.Auth.Commands.Login, while a change to Application.Features.Auth.Commands.Login can't break Application.Services.AuthService.
- Position
- Below the diagonal: Application.Features.Auth.Commands.Login uses a module listed above it, which is the healthy direction.
37→14 Application.Features.Auth.Commands.Login uses Application.Services.AuthenticatorService✕
- Connections
- 1 pair of types, where a type in Application.Features.Auth.Commands.Login uses a type in Application.Services.AuthenticatorService.
- The types involved
Application.Features.Auth.Commands.Login.LoginCommandHandler→Application.Services.AuthenticatorService.IAuthenticatorService
- Direction
- Application.Features.Auth.Commands.Login uses Application.Services.AuthenticatorService, so a change to Application.Services.AuthenticatorService can break Application.Features.Auth.Commands.Login, while a change to Application.Features.Auth.Commands.Login can't break Application.Services.AuthenticatorService.
- Position
- Below the diagonal: Application.Features.Auth.Commands.Login uses a module listed above it, which is the healthy direction.
37→34 Application.Features.Auth.Commands.Login uses Application.Services.UsersService✕
- Connections
- 1 pair of types, where a type in Application.Features.Auth.Commands.Login uses a type in Application.Services.UsersService.
- The types involved
Application.Features.Auth.Commands.Login.LoginCommandHandler→Application.Services.UsersService.IUserService
- Direction
- Application.Features.Auth.Commands.Login uses Application.Services.UsersService, so a change to Application.Services.UsersService can break Application.Features.Auth.Commands.Login, while a change to Application.Features.Auth.Commands.Login can't break Application.Services.UsersService.
- Position
- Below the diagonal: Application.Features.Auth.Commands.Login uses a module listed above it, which is the healthy direction.
38→2 Application.Features.Auth.Commands.RefreshToken uses Domain.Entities✕
- Connections
- 1 pair of types, where a type in Application.Features.Auth.Commands.RefreshToken uses a type in Domain.Entities.
- The types involved
Application.Features.Auth.Commands.RefreshToken.RefreshedTokensResponse→Domain.Entities.RefreshToken
- Direction
- Application.Features.Auth.Commands.RefreshToken uses Domain.Entities, so a change to Domain.Entities can break Application.Features.Auth.Commands.RefreshToken, while a change to Application.Features.Auth.Commands.RefreshToken can't break Domain.Entities.
- Position
- Below the diagonal: Application.Features.Auth.Commands.RefreshToken uses a module listed above it, which is the healthy direction.
38→6 Application.Features.Auth.Commands.RefreshToken uses Application.Features.Auth.Rules✕
- Connections
- 1 pair of types, where a type in Application.Features.Auth.Commands.RefreshToken uses a type in Application.Features.Auth.Rules.
- The types involved
Application.Features.Auth.Commands.RefreshToken.RefreshTokenCommandHandler→Application.Features.Auth.Rules.AuthBusinessRules
- Direction
- Application.Features.Auth.Commands.RefreshToken uses Application.Features.Auth.Rules, so a change to Application.Features.Auth.Rules can break Application.Features.Auth.Commands.RefreshToken, while a change to Application.Features.Auth.Commands.RefreshToken can't break Application.Features.Auth.Rules.
- Position
- Below the diagonal: Application.Features.Auth.Commands.RefreshToken uses a module listed above it, which is the healthy direction.
38→13 Application.Features.Auth.Commands.RefreshToken uses Application.Services.AuthService✕
- Connections
- 1 pair of types, where a type in Application.Features.Auth.Commands.RefreshToken uses a type in Application.Services.AuthService.
- The types involved
Application.Features.Auth.Commands.RefreshToken.RefreshTokenCommandHandler→Application.Services.AuthService.IAuthService
- Direction
- Application.Features.Auth.Commands.RefreshToken uses Application.Services.AuthService, so a change to Application.Services.AuthService can break Application.Features.Auth.Commands.RefreshToken, while a change to Application.Features.Auth.Commands.RefreshToken can't break Application.Services.AuthService.
- Position
- Below the diagonal: Application.Features.Auth.Commands.RefreshToken uses a module listed above it, which is the healthy direction.
38→34 Application.Features.Auth.Commands.RefreshToken uses Application.Services.UsersService✕
- Connections
- 1 pair of types, where a type in Application.Features.Auth.Commands.RefreshToken uses a type in Application.Services.UsersService.
- The types involved
Application.Features.Auth.Commands.RefreshToken.RefreshTokenCommandHandler→Application.Services.UsersService.IUserService
- Direction
- Application.Features.Auth.Commands.RefreshToken uses Application.Services.UsersService, so a change to Application.Services.UsersService can break Application.Features.Auth.Commands.RefreshToken, while a change to Application.Features.Auth.Commands.RefreshToken can't break Application.Services.UsersService.
- Position
- Below the diagonal: Application.Features.Auth.Commands.RefreshToken uses a module listed above it, which is the healthy direction.
39→3 Application.Features.Auth.Commands.VerifyOtpAuthenticator uses Application.Services.Repositories✕
- Connections
- 1 pair of types, where a type in Application.Features.Auth.Commands.VerifyOtpAuthenticator uses a type in Application.Services.Repositories.
- The types involved
Application.Features.Auth.Commands.VerifyOtpAuthenticator.VerifyOtpAuthenticatorCommandHandler→Application.Services.Repositories.IOtpAuthenticatorRepository
- Direction
- Application.Features.Auth.Commands.VerifyOtpAuthenticator uses Application.Services.Repositories, so a change to Application.Services.Repositories can break Application.Features.Auth.Commands.VerifyOtpAuthenticator, while a change to Application.Features.Auth.Commands.VerifyOtpAuthenticator can't break Application.Services.Repositories.
- Position
- Below the diagonal: Application.Features.Auth.Commands.VerifyOtpAuthenticator uses a module listed above it, which is the healthy direction.
39→6 Application.Features.Auth.Commands.VerifyOtpAuthenticator uses Application.Features.Auth.Rules✕
- Connections
- 1 pair of types, where a type in Application.Features.Auth.Commands.VerifyOtpAuthenticator uses a type in Application.Features.Auth.Rules.
- The types involved
Application.Features.Auth.Commands.VerifyOtpAuthenticator.VerifyOtpAuthenticatorCommandHandler→Application.Features.Auth.Rules.AuthBusinessRules
- Direction
- Application.Features.Auth.Commands.VerifyOtpAuthenticator uses Application.Features.Auth.Rules, so a change to Application.Features.Auth.Rules can break Application.Features.Auth.Commands.VerifyOtpAuthenticator, while a change to Application.Features.Auth.Commands.VerifyOtpAuthenticator can't break Application.Features.Auth.Rules.
- Position
- Below the diagonal: Application.Features.Auth.Commands.VerifyOtpAuthenticator uses a module listed above it, which is the healthy direction.
39→14 Application.Features.Auth.Commands.VerifyOtpAuthenticator uses Application.Services.AuthenticatorService✕
- Connections
- 1 pair of types, where a type in Application.Features.Auth.Commands.VerifyOtpAuthenticator uses a type in Application.Services.AuthenticatorService.
- The types involved
Application.Features.Auth.Commands.VerifyOtpAuthenticator.VerifyOtpAuthenticatorCommandHandler→Application.Services.AuthenticatorService.IAuthenticatorService
- Direction
- Application.Features.Auth.Commands.VerifyOtpAuthenticator uses Application.Services.AuthenticatorService, so a change to Application.Services.AuthenticatorService can break Application.Features.Auth.Commands.VerifyOtpAuthenticator, while a change to Application.Features.Auth.Commands.VerifyOtpAuthenticator can't break Application.Services.AuthenticatorService.
- Position
- Below the diagonal: Application.Features.Auth.Commands.VerifyOtpAuthenticator uses a module listed above it, which is the healthy direction.
39→34 Application.Features.Auth.Commands.VerifyOtpAuthenticator uses Application.Services.UsersService✕
- Connections
- 1 pair of types, where a type in Application.Features.Auth.Commands.VerifyOtpAuthenticator uses a type in Application.Services.UsersService.
- The types involved
Application.Features.Auth.Commands.VerifyOtpAuthenticator.VerifyOtpAuthenticatorCommandHandler→Application.Services.UsersService.IUserService
- Direction
- Application.Features.Auth.Commands.VerifyOtpAuthenticator uses Application.Services.UsersService, so a change to Application.Services.UsersService can break Application.Features.Auth.Commands.VerifyOtpAuthenticator, while a change to Application.Features.Auth.Commands.VerifyOtpAuthenticator can't break Application.Services.UsersService.
- Position
- Below the diagonal: Application.Features.Auth.Commands.VerifyOtpAuthenticator uses a module listed above it, which is the healthy direction.
40→2 WebAPI.Controllers uses Domain.Entities✕
- Connections
- 1 pair of types, where a type in WebAPI.Controllers uses a type in Domain.Entities.
- The types involved
WebAPI.Controllers.AuthController→Domain.Entities.RefreshToken
- Direction
- WebAPI.Controllers uses Domain.Entities, so a change to Domain.Entities can break WebAPI.Controllers, while a change to WebAPI.Controllers can't break Domain.Entities.
- Position
- Below the diagonal: WebAPI.Controllers uses a module listed above it, which is the healthy direction.
40→18 WebAPI.Controllers uses Application.Features.Auth.Commands.VerifyEmailAuthenticator✕
- Connections
- 1 pair of types, where a type in WebAPI.Controllers uses a type in Application.Features.Auth.Commands.VerifyEmailAuthenticator.
- The types involved
WebAPI.Controllers.AuthController→Application.Features.Auth.Commands.VerifyEmailAuthenticator.VerifyEmailAuthenticatorCommand
- Direction
- WebAPI.Controllers uses Application.Features.Auth.Commands.VerifyEmailAuthenticator, so a change to Application.Features.Auth.Commands.VerifyEmailAuthenticator can break WebAPI.Controllers, while a change to WebAPI.Controllers can't break Application.Features.Auth.Commands.VerifyEmailAuthenticator.
- Position
- Below the diagonal: WebAPI.Controllers uses a module listed above it, which is the healthy direction.
40→19 WebAPI.Controllers uses Application.Features.OperationClaims.Commands.Create✕
- Connections
- 1 pair of types, where a type in WebAPI.Controllers uses a type in Application.Features.OperationClaims.Commands.Create.
- The types involved
WebAPI.Controllers.OperationClaimsController→Application.Features.OperationClaims.Commands.Create.CreateOperationClaimCommand
- Direction
- WebAPI.Controllers uses Application.Features.OperationClaims.Commands.Create, so a change to Application.Features.OperationClaims.Commands.Create can break WebAPI.Controllers, while a change to WebAPI.Controllers can't break Application.Features.OperationClaims.Commands.Create.
- Position
- Below the diagonal: WebAPI.Controllers uses a module listed above it, which is the healthy direction.
40→20 WebAPI.Controllers uses Application.Features.OperationClaims.Commands.Delete✕
- Connections
- 1 pair of types, where a type in WebAPI.Controllers uses a type in Application.Features.OperationClaims.Commands.Delete.
- The types involved
WebAPI.Controllers.OperationClaimsController→Application.Features.OperationClaims.Commands.Delete.DeleteOperationClaimCommand
- Direction
- WebAPI.Controllers uses Application.Features.OperationClaims.Commands.Delete, so a change to Application.Features.OperationClaims.Commands.Delete can break WebAPI.Controllers, while a change to WebAPI.Controllers can't break Application.Features.OperationClaims.Commands.Delete.
- Position
- Below the diagonal: WebAPI.Controllers uses a module listed above it, which is the healthy direction.
40→21 WebAPI.Controllers uses Application.Features.OperationClaims.Commands.Update✕
- Connections
- 1 pair of types, where a type in WebAPI.Controllers uses a type in Application.Features.OperationClaims.Commands.Update.
- The types involved
WebAPI.Controllers.OperationClaimsController→Application.Features.OperationClaims.Commands.Update.UpdateOperationClaimCommand
- Direction
- WebAPI.Controllers uses Application.Features.OperationClaims.Commands.Update, so a change to Application.Features.OperationClaims.Commands.Update can break WebAPI.Controllers, while a change to WebAPI.Controllers can't break Application.Features.OperationClaims.Commands.Update.
- Position
- Below the diagonal: WebAPI.Controllers uses a module listed above it, which is the healthy direction.
40→22 WebAPI.Controllers uses Application.Features.OperationClaims.Queries.GetById✕
- Connections
- 1 pair of types, where a type in WebAPI.Controllers uses a type in Application.Features.OperationClaims.Queries.GetById.
- The types involved
WebAPI.Controllers.OperationClaimsController→Application.Features.OperationClaims.Queries.GetById.GetByIdOperationClaimQuery
- Direction
- WebAPI.Controllers uses Application.Features.OperationClaims.Queries.GetById, so a change to Application.Features.OperationClaims.Queries.GetById can break WebAPI.Controllers, while a change to WebAPI.Controllers can't break Application.Features.OperationClaims.Queries.GetById.
- Position
- Below the diagonal: WebAPI.Controllers uses a module listed above it, which is the healthy direction.
40→23 WebAPI.Controllers uses Application.Features.UserOperationClaims.Commands.Create✕
- Connections
- 1 pair of types, where a type in WebAPI.Controllers uses a type in Application.Features.UserOperationClaims.Commands.Create.
- The types involved
WebAPI.Controllers.UserOperationClaimsController→Application.Features.UserOperationClaims.Commands.Create.CreateUserOperationClaimCommand
- Direction
- WebAPI.Controllers uses Application.Features.UserOperationClaims.Commands.Create, so a change to Application.Features.UserOperationClaims.Commands.Create can break WebAPI.Controllers, while a change to WebAPI.Controllers can't break Application.Features.UserOperationClaims.Commands.Create.
- Position
- Below the diagonal: WebAPI.Controllers uses a module listed above it, which is the healthy direction.
40→24 WebAPI.Controllers uses Application.Features.UserOperationClaims.Commands.Delete✕
- Connections
- 1 pair of types, where a type in WebAPI.Controllers uses a type in Application.Features.UserOperationClaims.Commands.Delete.
- The types involved
WebAPI.Controllers.UserOperationClaimsController→Application.Features.UserOperationClaims.Commands.Delete.DeleteUserOperationClaimCommand
- Direction
- WebAPI.Controllers uses Application.Features.UserOperationClaims.Commands.Delete, so a change to Application.Features.UserOperationClaims.Commands.Delete can break WebAPI.Controllers, while a change to WebAPI.Controllers can't break Application.Features.UserOperationClaims.Commands.Delete.
- Position
- Below the diagonal: WebAPI.Controllers uses a module listed above it, which is the healthy direction.
40→25 WebAPI.Controllers uses Application.Features.UserOperationClaims.Commands.Update✕
- Connections
- 1 pair of types, where a type in WebAPI.Controllers uses a type in Application.Features.UserOperationClaims.Commands.Update.
- The types involved
WebAPI.Controllers.UserOperationClaimsController→Application.Features.UserOperationClaims.Commands.Update.UpdateUserOperationClaimCommand
- Direction
- WebAPI.Controllers uses Application.Features.UserOperationClaims.Commands.Update, so a change to Application.Features.UserOperationClaims.Commands.Update can break WebAPI.Controllers, while a change to WebAPI.Controllers can't break Application.Features.UserOperationClaims.Commands.Update.
- Position
- Below the diagonal: WebAPI.Controllers uses a module listed above it, which is the healthy direction.
40→26 WebAPI.Controllers uses Application.Features.UserOperationClaims.Queries.GetById✕
- Connections
- 1 pair of types, where a type in WebAPI.Controllers uses a type in Application.Features.UserOperationClaims.Queries.GetById.
- The types involved
WebAPI.Controllers.UserOperationClaimsController→Application.Features.UserOperationClaims.Queries.GetById.GetByIdUserOperationClaimQuery
- Direction
- WebAPI.Controllers uses Application.Features.UserOperationClaims.Queries.GetById, so a change to Application.Features.UserOperationClaims.Queries.GetById can break WebAPI.Controllers, while a change to WebAPI.Controllers can't break Application.Features.UserOperationClaims.Queries.GetById.
- Position
- Below the diagonal: WebAPI.Controllers uses a module listed above it, which is the healthy direction.
40→27 WebAPI.Controllers uses Application.Features.Users.Commands.Create✕
- Connections
- 1 pair of types, where a type in WebAPI.Controllers uses a type in Application.Features.Users.Commands.Create.
- The types involved
WebAPI.Controllers.UsersController→Application.Features.Users.Commands.Create.CreateUserCommand
- Direction
- WebAPI.Controllers uses Application.Features.Users.Commands.Create, so a change to Application.Features.Users.Commands.Create can break WebAPI.Controllers, while a change to WebAPI.Controllers can't break Application.Features.Users.Commands.Create.
- Position
- Below the diagonal: WebAPI.Controllers uses a module listed above it, which is the healthy direction.
40→28 WebAPI.Controllers uses Application.Features.Users.Commands.Delete✕
- Connections
- 1 pair of types, where a type in WebAPI.Controllers uses a type in Application.Features.Users.Commands.Delete.
- The types involved
WebAPI.Controllers.UsersController→Application.Features.Users.Commands.Delete.DeleteUserCommand
- Direction
- WebAPI.Controllers uses Application.Features.Users.Commands.Delete, so a change to Application.Features.Users.Commands.Delete can break WebAPI.Controllers, while a change to WebAPI.Controllers can't break Application.Features.Users.Commands.Delete.
- Position
- Below the diagonal: WebAPI.Controllers uses a module listed above it, which is the healthy direction.
40→29 WebAPI.Controllers uses Application.Features.Users.Commands.Update✕
- Connections
- 1 pair of types, where a type in WebAPI.Controllers uses a type in Application.Features.Users.Commands.Update.
- The types involved
WebAPI.Controllers.UsersController→Application.Features.Users.Commands.Update.UpdateUserCommand
- Direction
- WebAPI.Controllers uses Application.Features.Users.Commands.Update, so a change to Application.Features.Users.Commands.Update can break WebAPI.Controllers, while a change to WebAPI.Controllers can't break Application.Features.Users.Commands.Update.
- Position
- Below the diagonal: WebAPI.Controllers uses a module listed above it, which is the healthy direction.
40→30 WebAPI.Controllers uses Application.Features.Users.Commands.UpdateFromAuth✕
- Connections
- 1 pair of types, where a type in WebAPI.Controllers uses a type in Application.Features.Users.Commands.UpdateFromAuth.
- The types involved
WebAPI.Controllers.UsersController→Application.Features.Users.Commands.UpdateFromAuth.UpdateUserFromAuthCommand
- Direction
- WebAPI.Controllers uses Application.Features.Users.Commands.UpdateFromAuth, so a change to Application.Features.Users.Commands.UpdateFromAuth can break WebAPI.Controllers, while a change to WebAPI.Controllers can't break Application.Features.Users.Commands.UpdateFromAuth.
- Position
- Below the diagonal: WebAPI.Controllers uses a module listed above it, which is the healthy direction.
40→31 WebAPI.Controllers uses Application.Features.Users.Queries.GetById✕
- Connections
- 1 pair of types, where a type in WebAPI.Controllers uses a type in Application.Features.Users.Queries.GetById.
- The types involved
WebAPI.Controllers.UsersController→Application.Features.Users.Queries.GetById.GetByIdUserQuery
- Direction
- WebAPI.Controllers uses Application.Features.Users.Queries.GetById, so a change to Application.Features.Users.Queries.GetById can break WebAPI.Controllers, while a change to WebAPI.Controllers can't break Application.Features.Users.Queries.GetById.
- Position
- Below the diagonal: WebAPI.Controllers 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 — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A05:2025 — Injection | 31 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 19 | High / Critical |
Roadmap
Top priorities: Encrypt sensitive data at rest (ASP.NET Core Data Protection / column encryption) and manage keys in a vault. Skip if delegated to infra (Postgres TDE, KMS, etc.); Protect endpoints by default-deny: [Authorize] + role/policy authorization, or imperative guard methods (throw-on-violation) called from every handler; Resolve the 1 No ADRs found finding(s) in ADR Quality.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 1 No ADRs found finding(s) in ADR Quality. | +5.6 pts | Low | ADR Quality |
| Encrypt sensitive data at rest (ASP.NET Core Data Protection / column encryption) and manage keys in a vault. Skip if delegated to infra (Postgres TDE, KMS, etc.). | +9.9 pts | Medium | Data Protection |
| Protect endpoints by default-deny: [Authorize] + role/policy authorization, or imperative guard methods (throw-on-violation) called from every handler. | +9.9 pts | Medium | Access Controls |
| Resolve the 4 Outdated finding(s) in Dependency Hygiene — start with REDACTED (2), REDACTED, WebAPI.csproj. | +3.4 pts | Low | Dependency Hygiene |
| Resolve the 7 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (4), REDACTED (3). | +2.9 pts | Low | Dependency Vulnerabilities |
| Resolve the 24 Orphaned file finding(s) in Knowledge Freshness — start with AuthenticatorManager.cs, REDACTED, AuthManager.cs. | +5.5 pts | Medium | Knowledge Freshness |
| Resolve the 25 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (8), REDACTED (7), REDACTED (5). | +5.3 pts | Medium | Static Analysis (SAST) |
| Resolve the 2 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED. | +2.2 pts | Low | Supply-chain Provenance & Signing |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 0.9 | Slop | Dependency Vulnerabilities: Critical CVE: REDACTED |
| REDACTED | 1.9 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.9 | Slop | Dependency Vulnerabilities: High CVE: REDACTED |
| REDACTED | 5.1 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.4 | Mixed | Dependency Vulnerabilities: Medium CVE: REDACTED |
| REDACTED | 5.8 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| REDACTED | 5.8 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| REDACTED | 5.9 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| REDACTED | 5.9 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| src/starterProject/WebAPI/WebAPI.csproj | 6.5 | Mixed | Code Coverage: No test project references WebAPI |
| src/starterProject/Application/Services/UserOperationClaims/UserOperationClaimManager.cs | 6.7 | Mixed | Explicit Debt: Dead code: UserUserOperationClaimManager |
| src/starterProject/Application/Services/OperationClaims/OperationClaimManager.cs | 6.7 | Mixed | Explicit Debt: Dead code: OperationClaimManager |
| src/starterProject/Persistence/EntityConfigurations/EmailAuthenticatorConfiguration.cs | 7.4 | Mixed | Code Duplication: Members sharing a duplicated core (6 members, 50+ identical tokens) |
| src/starterProject/WebAPI/Controllers/BaseController.cs | 8.2 | Near-clean | Explicit Debt: TodoComment |
| src/starterProject/Application/Services/TranslateService/ITranslateService.cs | 8.2 | Near-clean | Explicit Debt: Dead code: ITranslateService |
| src/starterProject/WebAPI/Controllers/Dtos/UpdateByAuthFromServiceRequestDto.cs | 8.2 | Near-clean | Explicit Debt: Dead code: UpdateByAuthFromServiceRequestDto |
| src/starterProject/Application/Features/OperationClaims/Constants/OperationClaimsOperationClaims.cs | 8.5 | Near-clean | Code Duplication: Duplicated block (8 lines × 3) |
| src/starterProject/Application/Features/Users/Commands/Create/CreateUserCommandValidator.cs | 8.5 | Near-clean | Code Duplication: Duplicated block (5 lines × 2) |
| src/starterProject/Application/Features/Users/Commands/Create/CreatedUserResponse.cs | 8.5 | Near-clean | Code Duplication: Duplicated block (6 lines × 4) |
| src/starterProject/Application/ApplicationServiceRegistration.cs | 8.5 | Near-clean | Code Coverage: Low coverage: src/starterProject/Application/ApplicationServiceRegistration.cs |
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 78 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 — 78 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, 203 of 257 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Canine Code Analyzer duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 | ✓ deterministic |
Run transparency — what happened this run
- 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. All 24 significant source file(s) were last meaningfully changed so long ago that no living knowledge remains — nothing since has been substantial enough to re-establish ownership (a broad, mechanical sweep that touches many files shallowly does not count, and neither does no activity at all). There is no concentration to measure, so the bus factor is not scored. This is not a clean bill: nobody currently holds working knowledge of this code (see D34 Knowledge Freshness). Counted over 24 of the 119 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
- 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.
- D22 Internal API Consistency — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. The loaded project set declares no packable project and no `.Contracts` project, so there is no intentionally-exposed surface for API consistency to be judged over.
- ED5 Idempotency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check classifies a mutation as idempotent when a guard is visible (an exists check, an upsert, an idempotency key or inbox, a versioned or fixed-value write) and as at risk only on positive evidence that a re-run double-applies it (a fresh-identity insert, an accumulation, a growing collection, an unkeyed outbound send or charge). The rest show neither, and they are the majority here, so a score over the classified minority would not describe this repository. That is a limit of the analyzer, not a finding about your code.
- 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. Every other migration runner — DbUp, FluentMigrator, Evolve, Flyway, Liquibase, RoundhousE, a hand-rolled versioned-SQL runner — is invisible to the detector, so an absence here is our blind spot rather than a missing migration strategy in the repository. The card abstains instead of scoring. You can widen what we reach: if the schema is created and evolved by a tool other than EF Core migrations, naming it lets us teach the detector to read it.
- 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. 26 further occurrence(s) are not listed individually; the score already reflects all 66.
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 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D18 Solution Shape: Build integrity reflects whether the solution compiled in this environment — a build that needs a private feed, a specific SDK, or a generated file absent from the repo can read as broken when it is merely unreproducible here.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
- D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
- D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- 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.
- M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
- P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
- P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
Dimensions
D1 · Cyclomatic Complexity
0 method(s) exceeded the cyclomatic complexity threshold of 15.
D2 · Cognitive Complexity
0 method(s) exceeded the cognitive complexity threshold of 15.
D3 · God Classes
0 god class(es) detected.
D4 · Code Duplication
5 duplicated block group(s) detected. One further row reports members as variants of one another; it aggregates block groups already counted above and is not itself counted.
What to do
- Resolve the 1 Members sharing a duplicated core (6 members, 50+ identical tokens) finding(s) in Code Duplication — start with EmailAuthenticatorConfiguration.cs. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Duplicated block (8 lines × 3) finding(s) in Code Duplication — start with OperationClaimsOperationClaims.cs. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Duplicated block (9 lines × 3) finding(s) in Code Duplication — start with EmailAuthenticatorConfiguration.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
6 projects, 0 dependency cycle(s), 0 unstable depended-on project(s).
D6 · Cohesion (LCOM4)
0 of 9 classes have LCOM4 above 3.
D8 · Code Coverage
Line coverage 21.8% — 43 file(s) below 50%.
What to do
- Resolve the 43 Low coverage finding(s) in Code Coverage — start with MappingProfiles.cs (2), ApplicationServiceRegistration.cs, UserManager.cs. — One of this dimension's main actionable groups (43 warning-level).
- Resolve the 1 No test project references Persistence finding(s) in Code Coverage — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 No test project references WebAPI finding(s) in Code Coverage — start with WebAPI.csproj. — One of this dimension's main actionable groups (1 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
19 test methods: 19 unit, 0 integration, 0 BDD, 0 e2e.
D10 · Test Quality
0 skipped, 0 zero-assertion, 1 mock references across 19 tests.
D11 · Test Reliability
0 flaky across 1 measured tier(s). unit: measured (0 flaky).
D12 · Dependency Hygiene
37 outdated, 1 vulnerable, 2 deprecated packages.
What to do
- Resolve the 4 Outdated finding(s) in Dependency Hygiene — start with REDACTED (2), REDACTED, WebAPI.csproj. — One of this dimension's main actionable groups (4 recommendation-level).
- Resolve the 2 Deprecated finding(s) in Dependency Hygiene — start with WebAPI.csproj, REDACTED. — One of this dimension's main actionable groups (2 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 · Secret Scanning
Secret scan ran and found no leaked secrets.
D14 · License Compliance
0 of 251 packages use a banned license. ★ DEPTH: this repository's MSBuild projects declare 37 direct `PackageReference`(s), and 213 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
1 deducted debt markers + 4 dead symbols across 3677 LoC in the .NET projects (0.2/KLoC) → score 9.6.
What to do
- Resolve the 4 Dead code finding(s) in Explicit Debt — start with OperationClaimManager.cs, ITranslateService.cs, UserOperationClaimManager.cs. — One of this dimension's main actionable groups (4 warning-level).
- Resolve the 1 TodoComment finding(s) in Explicit Debt — start with BaseController.cs. — One of this dimension's main actionable groups (1 warning-level).
- Enforce Explicit Debt in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D18 · Solution Shape
6 projects, 139 source files, 4290 hand-written lines of code (3677 production / 613 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), 7 inter-project edges.
D19 · Documentation Quality
2 of 2 documentation facets pass in full. 2 document(s) read across 6 unit(s).
D20 · ADR Quality
No architecture decision records were found.
What to do
- Resolve the 1 No ADRs found finding(s) in ADR Quality. — One of this dimension's main actionable groups (1 recommendation-level).
D26 · Project Cohesion
0 of 6 projects flagged as possibly oversized/incoherent.
D27 · Navigability
92 % of calls cross a namespace and 28 % go through an interface, but 56 % of collaborators are co-located — so following a call takes several hops. Baseline: small — navigation cost is tolerated.
What to do
- Resolve the 1 Scattered collaborators finding(s) in Navigability. — One of this dimension's main actionable groups (1 recommendation-level).
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
31 finding(s): 0 critical, 3 high, 28 medium, 0 low. 3 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens.
What to do
- Resolve the 25 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (8), REDACTED (7), REDACTED (5). — One of this dimension's main actionable groups (25 warning-level).
- Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2). — One of this dimension's main actionable groups (2 warning-level).
- No action in Static Analysis (SAST) — all 3 REDACTED finding(s) are reported here at file:line but scored by D36 (supply-chain provenance), so none is charged to this dimension. — One of this dimension's main actionable groups (3 issue-level, 0 of them charged here).
D30 · Dependency Vulnerabilities
12 finding(s): 1 critical, 7 high, 4 medium, 0 low.
What to do
- Resolve the 7 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (4), REDACTED (3). — One of this dimension's main actionable groups (7 issue-level).
- Resolve the 4 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (2), REDACTED (2). — One of this dimension's main actionable groups (4 warning-level).
- Resolve the 1 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
D34 · Knowledge Freshness
24 of 24 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is src/starterProject/Application/Services/AuthenticatorService/AuthenticatorManager.cs. Counted over 24 of the 119 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 24 Orphaned file finding(s) in Knowledge Freshness — start with AuthenticatorManager.cs, REDACTED, AuthManager.cs. — One of this dimension's main actionable groups (24 recommendation-level).
- Resolve the 1 Dormant codebase finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
D35 · Change Coupling
No strong hidden change-coupling between production files.
D36 · Supply-chain Provenance & Signing
0/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).
What to do
- Resolve the 2 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).
D39 · IL Efficiency
3 of 308 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 6 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
AX5 · Architecture & structure
AX6 · Interface segregation
AX7 · Slice cohesion
AX8 · Test isolation
AX9 · CQS / query purity
C1 · Data Protection
- No data-protection or encryption usage (ASP.NET Data Protection, AES, column encryption, PBKDF2) was found — sensitive data at rest may be unprotected. If TDE/KMS/vault is delegated to infrastructure, ignore.
What to do
- Encrypt sensitive data at rest (ASP.NET Core Data Protection / column encryption) and manage keys in a vault. Skip if delegated to infra (Postgres TDE, KMS, etc.).
- Enforce HTTPS (UseHttpsRedirection / RequireHttpsMetadata) so data in transit is always encrypted.
C2 · Access Controls
- No [Authorize]/policies and no imperative guard methods (throw-on-violation) were found — endpoints may be unprotected.
- `AuthController.Login` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. — REDACTED:31
- `AuthController.Register` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. — REDACTED:43
- `AuthController.RefreshToken` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. — REDACTED:52
- `AuthController.RevokeToken` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. — REDACTED:62
- `AuthController.EnableEmailAuthenticator` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. — REDACTED:71
- `AuthController.EnableOtpAuthenticator` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. — REDACTED:85
- `AuthController.VerifyEmailAuthenticator` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. — REDACTED:94
- `AuthController.VerifyOtpAuthenticator` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. — REDACTED:103
- `OperationClaimsController.GetById` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. — REDACTED:17
- `OperationClaimsController.GetList` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. — REDACTED:24
- `OperationClaimsController.Add` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. — REDACTED:32
- `OperationClaimsController.Update` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. — REDACTED:39
- `OperationClaimsController.Delete` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. — REDACTED:46
- `UserOperationClaimsController.GetById` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. — REDACTED:17
- `UserOperationClaimsController.GetList` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. — REDACTED:24
- `UserOperationClaimsController.Add` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. — REDACTED:32
- `UserOperationClaimsController.Update` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. — REDACTED:39
- `UserOperationClaimsController.Delete` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. — REDACTED:46
- `UsersController.GetById` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. — REDACTED:18
- `UsersController.GetFromAuth` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. — REDACTED:25
- `UsersController.GetList` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. — REDACTED:33
- `UsersController.Add` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. — REDACTED:41
- `UsersController.Update` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. — REDACTED:48
- `UsersController.UpdateFromAuth` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. — REDACTED:55
- `UsersController.Delete` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. — REDACTED:63
What to do
- Protect endpoints by default-deny: [Authorize] + role/policy authorization, or imperative guard methods (throw-on-violation) called from every handler.
GD1 · Unfinished & placeholder code
IC1 · Incompleteness & stubs
M1 · Documentation (README)
What to do
- Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
- Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
- Add a README to the 5 of 5 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
- Only 1/6 projects share a common root namespace — the code's module identity is inconsistent.
What to do
- Adopt a consistent root-namespace convention (a shared prefix, e.g. Acme.*); short project-file/directory names are fine as long as the RootNamespace is uniform.
M4 · Documentation accuracy
- README.md names .NET 7, but the projects target .NET 8. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — README.md:41
What to do
- Reconcile the README with reality: README.md names .NET 7, but the projects target .NET 8.
P1 · CI/CD gates
P2 · Observability
- Only 1/4 service-like projects use logging (pure contract/DTO projects are excluded — they have nothing to log). Of those 4, 1 ship a process this repository operates; the rest are libraries their consumer hosts, where the logging decision belongs to the host.
What to do
- Extend structured logging across the projects you operate, and give the library ones a diagnostics seam instead — an `EventSource`/`ActivitySource` the host can subscribe to, or an optional logger on your options object — rather than taking a logging dependency on your consumers' behalf.
- Consider OpenTelemetry tracing/metrics and a health-check endpoint for operability.
P3 · Security & performance tooling
- No static application security testing detected. For this repository's stack, add CodeQL's csharp pack, or a .NET security analyzer package (or `semgrep --config=auto`, which runs on any language) as a CI step. What was searched, so you can tell an absence from a miss: the 853 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner. — REDACTED:6
- `REDACTED` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`. — REDACTED:11
What to do
- Add a SAST step to CI running what this repository's stack ships: CodeQL's csharp pack, or a .NET security analyzer package — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing.
- Enable Dependabot/Renovate or a dependency-review gate.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
- Deployment is automated and no gate that pauses it for a human is DECLARED IN THIS REPOSITORY'S PIPELINE FILES. What was read: every file under `.github/workflows/`, `.forgejo/workflows/`, `.gitea/workflows/`, `.azuredevops/` and `.azure-pipelines/`, plus `.gitlab-ci*` and `azure-pipelines*` — with comment text stripped, so documenting a gate is not declaring one. What would have counted: GitLab's `when: manual`, CircleCI's `type: approval`, an Azure `ManualValidation@` task or an `approvals:` block, a Jenkins `input` step, a `uses:` step naming an approval action, an `environment:` paired with `reviewers` / `required_reviewers` / `protection` / `wait-timer` / `deployment_branch_policy`, a draft-release step, a `workflow_dispatch` promotion, or a release-event gate. ★ What this cannot see, because none of it is a file: a GitHub environment whose required reviewers are configured in repo SETTINGS, a branch protection rule, or an organisation deployment policy — all of them real, enforced gates that live outside the repository. If yours is one of those, this row is wrong and nothing in the tree could have told us. Otherwise: whatever reaches the release trigger goes to production unreviewed, so a mistaken merge or tag is live before anyone can stop it.
What to do
- Add an approval/environment gate (required reviewers / protection rules) before production promotion.
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
What to do
- Raise domain coverage toward 100% — cover the remaining aggregates / value objects / domain services where the business invariants and costly bugs live.
PF3 · Async & latency hygiene
S1 · Web-Security Posture
- 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/starterProject/WebAPI/Program.cs:19
- 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/starterProject/WebAPI/Program.cs:19
- The `refreshToken` cookie (`Cookies.Append`) carries who is signed in, and it is set without Secure, SameSite. Without Secure the browser also sends it over plain http://, where anyone on the same network can read it. Without SameSite other websites can make the browser send it along with requests they trigger (cross-site request forgery). (−1.5 on this card.) — REDACTED:120
What to do
- 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.
- Lock down every session and sign-in cookie: `new CookieOptions { HttpOnly = true, Secure = true, SameSite = SameSiteMode.Lax }` on `Response.Cookies.Append`, leave `Cookie.HttpOnly` on and set `Cookie.SecurePolicy = CookieSecurePolicy.Always` in `AddCookie`/`AddSession`, or force both for every cookie with `app.UseCookiePolicy(new CookiePolicyOptions { HttpOnly = HttpOnlyPolicy.Always, Secure = CookieSecurePolicy.Always })`.
X1 · Async correctness
X12 · Unreachable branch
X13 · Undrained process stream
X14 · Bypassable address classification
X15 · Unvalidated length from an untrusted reader
X16 · Unfloored truncation loop
X17 · Uncapped recursion over a caller-supplied document
X18 · Disposal-pattern correctness
X19 · Unrestored process-global state
X2 · Cancellation propagation
- Only 30/89 async methods accept a CancellationToken, so in-flight work can't be stopped early when the caller gives up — whatever ends it in your host (shutdown signal, timeout, abandoned request, user cancel). Thread a token through the call chain and honour it at each await and loop; where a method genuinely cannot be interrupted, omitting it is a deliberate choice — judge against your hosting model.
- No CancellationToken parameter — this work can't be stopped early once started. (×39) — src/starterProject/Application/Features/Auth/Rules/AuthBusinessRules.cs:77, src/starterProject/Application/Features/OperationClaims/Rules/OperationClaimBusinessRules.cs:36, src/starterProject/Application/Features/OperationClaims/Rules/OperationClaimBusinessRules.cs:43, …
What to do
- Thread a CancellationToken through async methods so work stops promptly on cancellation.
X20 · Mistyped argument guard
X21 · Side-effecting pattern guard
X22 · Contradicted release guard
X23 · Unguarded diagnostic materialisation
X24 · Document value interpolated into markup unescaped
X25 · Inert configuration knob
X26 · Unsynchronised callback handoff
X27 · Collection changed while being enumerated
X28 · Index access outside its own emptiness guard
X29 · Per-element action decided by a fixed element
X3 · Exception handling
X30 · Support guard that admits what it rejects
X32 · Type resolved by simple name across every loaded assembly
X4 · Structured logging
X5 · Nullable reference types
- ~2.7 `!` suppressions per 1k syntax nodes — 53 suppression(s) across the 19514 syntax node(s) in code where nullable warnings are ENABLED, which is the only code a `!` can suppress anything in (a `!` under `#nullable disable` is inert and is not counted, and its file's nodes are not in the denominator). Each one tells the compiler to trust you about null, suppressing the very safety NRTs provide.
What to do
- Enable <Nullable>enable</Nullable> across all projects and resolve warnings rather than suppressing with `!`.
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 83% | Strong | Solid. |
| Architecture | 93% | Exemplary | Solid. |
| Maturity | 51% | Adequate — gated by D34, M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 43% | Weak — gated by P3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 18% | Critical — gated by D29, D36, C1, C2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Performance | 100% | Exemplary | Strongest area. |
Unscored — 1 check(s) recorded observations but carry no score
- SC1 Supply-chain hygiene — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Not evidenced — 4 control(s) we could not find positive evidence for
- C3 Audit Trail — Repo shows no audit-logging mechanism (IAuditable, an immutable audit log, an EF SaveChanges interceptor) for sensitive changes — absence of evidence is not evidence of a working control. Record an audit trail in code (or document where it lives) so this dimension can be scored.
- C4 Data Retention — Repo shows no data-retention / TTL / cleanup mechanism for personal data — absence of evidence is not evidence of a working control. Define retention periods and a purge/cleanup job (or TTL) in code, or document where retention is enforced, so this dimension can be scored.
- C5 Data-Subject Rights — Repo shows no corroborated data-subject-rights mechanism (erasure / export-portability / consent) tied to a subject id or GDPR vocabulary — absence of evidence is not evidence of a working control. Implement erasure, data export/portability and consent tracking over the subject's records.
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 39 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
- AX4 Dependency direction — not applicable to a vertical-slice + CQRS architecture (the inward-dependency rule is for layered/clean styles)
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXO1 Runtime API surface — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXR1 Runtime accessibility — This repository has no user interface to render — no markup (HTML, Razor, JSX, Vue, Svelte or server templates), no UI framework dependency, no UI component source and no native UI project — so WCAG's runtime success criteria have nothing to apply to here. Not applicable: this is neither a gap in the scan nor a finding about your code.
- AXS1 Runtime exposed surface — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- D16 Bus Factor — dormant codebase — no living knowledge left to concentrate
- D21 Naming Consistency — N/A — too few peers to establish a naming convention (903 declarations, no unit with a dominant convention).
- D22 Internal API Consistency — No intentionally-exposed public API to evaluate for consistency.
- D23 Boundary Type-Coupling — small single-context codebase (3,677 production LoC in the .NET projects) — bounded contexts are not needed at this size No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D24 Comment Value — Too few judgeable comments (1 of at least 30); comment value is not applicable here.
- D25 ADR Conformance — no ADRs to check
- D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
- D32 Data Compliance (PII/GDPR) — 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.
- 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 — not scored — this repository shows only 1 of the 3 signals this lens looks for (4 repository port(s) loading or saving an aggregate/entity)
- ED1 Event-Driven — applicable but not scored (2 of 3 signals for this style — below the bar we score at): a message-bus package; 24 CQRS handler(s)
- ED5 Idempotency — not scored — 13 of 18 retry-prone mutations could not be classified (no visible guard and no positive evidence of a double-applied effect)
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
- P7 Outbound HTTP resilience — no outbound HTTP usage detected — no HttpClient/IHttpClientFactory/AddHttpClient in source, and no Refit/RestSharp/Flurl.Http namespace or package reference
- P8 Schema migrations — EF Core is used, but the schema-migration mechanism could not be identified — this check only recognises EF migrations, so any other migration runner reads as an absence. Our limit, not a verdict on this repository.
- PF1 Benchmark discipline — Performance is assessed only for perf-relevant repos — a packaged library, one that ships benchmarks, or one already using allocation-aware APIs. This repo isn't one, so the Performance lens is not applicable and is excluded from the score.
- PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
- X10 Duplicated predicate — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- 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 — 11 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
Serious — 162 finding(s)
- Low coverage: src/starterProject/Application/ApplicationServiceRegistration.cs src/starterProject/Application/ApplicationServiceRegistration.cs:1
- Low coverage: src/starterProject/Application/Services/UsersService/UserManager.cs src/starterProject/Application/Services/UsersService/UserManager.cs:1
- Low coverage: src/starterProject/Application/Services/UserOperationClaims/UserOperationClaimManager.cs src/starterProject/Application/Services/UserOperationClaims/UserOperationClaimManager.cs:1
- Low coverage: src/starterProject/Application/Services/OperationClaims/OperationClaimManager.cs src/starterProject/Application/Services/OperationClaims/OperationClaimManager.cs:1
- Low coverage: src/starterProject/Application/Services/ImageService/ImageServiceBase.cs src/starterProject/Application/Services/ImageService/ImageServiceBase.cs:1
- Low coverage: src/starterProject/Application/Services/AuthenticatorService/AuthenticatorManager.cs src/starterProject/Application/Services/AuthenticatorService/AuthenticatorManager.cs:1
- Low coverage: src/starterProject/Application/Features/Users/Commands/UpdateFromAuth/UpdatedUserFromAuthResponse.cs src/starterProject/Application/Features/Users/Commands/UpdateFromAuth/UpdatedUserFromAuthResponse.cs:1
- Low coverage: src/starterProject/Application/Features/Users/Commands/UpdateFromAuth/UpdateUserFromAuthCommand.cs src/starterProject/Application/Features/Users/Commands/UpdateFromAuth/UpdateUserFromAuthCommand.cs:1
- Low coverage: src/starterProject/Application/Features/Users/Commands/UpdateFromAuth/UpdateUserFromAuthCommandValidator.cs src/starterProject/Application/Features/Users/Commands/UpdateFromAuth/UpdateUserFromAuthCommandValidator.cs:1
- Low coverage: src/starterProject/Application/Features/UserOperationClaims/Rules/UserOperationClaimBusinessRules.cs src/starterProject/Application/Features/UserOperationClaims/Rules/UserOperationClaimBusinessRules.cs:1
- Low coverage: src/starterProject/Application/Features/UserOperationClaims/Queries/GetList/GetListUserOperationClaimQuery.cs src/starterProject/Application/Features/UserOperationClaims/Queries/GetList/GetListUserOperationClaimQuery.cs:1
- Low coverage: src/starterProject/Application/Features/UserOperationClaims/Queries/GetById/GetByIdUserOperationClaimQuery.cs src/starterProject/Application/Features/UserOperationClaims/Queries/GetById/GetByIdUserOperationClaimQuery.cs:1
- Low coverage: src/starterProject/Application/Features/UserOperationClaims/Profiles/MappingProfiles.cs src/starterProject/Application/Features/UserOperationClaims/Profiles/MappingProfiles.cs:1
- Low coverage: src/starterProject/Application/Features/UserOperationClaims/Commands/Update/UpdateUserOperationClaimCommand.cs src/starterProject/Application/Features/UserOperationClaims/Commands/Update/UpdateUserOperationClaimCommand.cs:1
- Low coverage: src/starterProject/Application/Features/UserOperationClaims/Commands/Update/UpdateUserOperationClaimCommandValidator.cs src/starterProject/Application/Features/UserOperationClaims/Commands/Update/UpdateUserOperationClaimCommandValidator.cs:1
- Low coverage: src/starterProject/Application/Features/UserOperationClaims/Commands/Delete/DeleteUserOperationClaimCommand.cs src/starterProject/Application/Features/UserOperationClaims/Commands/Delete/DeleteUserOperationClaimCommand.cs:1
- Low coverage: src/starterProject/Application/Features/UserOperationClaims/Commands/Create/CreateUserOperationClaimCommand.cs src/starterProject/Application/Features/UserOperationClaims/Commands/Create/CreateUserOperationClaimCommand.cs:1
- Low coverage: src/starterProject/Application/Features/UserOperationClaims/Commands/Create/CreateUserOperationClaimCommandValidator.cs src/starterProject/Application/Features/UserOperationClaims/Commands/Create/CreateUserOperationClaimCommandValidator.cs:1
- Low coverage: src/starterProject/Application/Features/OperationClaims/Rules/OperationClaimBusinessRules.cs src/starterProject/Application/Features/OperationClaims/Rules/OperationClaimBusinessRules.cs:1
- Low coverage: src/starterProject/Application/Features/OperationClaims/Queries/GetList/GetListOperationClaimListItemDto.cs src/starterProject/Application/Features/OperationClaims/Queries/GetList/GetListOperationClaimListItemDto.cs:1
- Low coverage: src/starterProject/Application/Features/OperationClaims/Queries/GetList/GetListOperationClaimQuery.cs src/starterProject/Application/Features/OperationClaims/Queries/GetList/GetListOperationClaimQuery.cs:1
- Low coverage: src/starterProject/Application/Features/OperationClaims/Queries/GetById/GetByIdOperationClaimQuery.cs src/starterProject/Application/Features/OperationClaims/Queries/GetById/GetByIdOperationClaimQuery.cs:1
- Low coverage: src/starterProject/Application/Features/OperationClaims/Queries/GetById/GetByIdOperationClaimResponse.cs src/starterProject/Application/Features/OperationClaims/Queries/GetById/GetByIdOperationClaimResponse.cs:1
- Low coverage: src/starterProject/Application/Features/OperationClaims/Profiles/MappingProfiles.cs src/starterProject/Application/Features/OperationClaims/Profiles/MappingProfiles.cs:1
- Low coverage: src/starterProject/Application/Features/OperationClaims/Commands/Update/UpdatedOperationClaimResponse.cs src/starterProject/Application/Features/OperationClaims/Commands/Update/UpdatedOperationClaimResponse.cs:1
- Async method without CancellationToken: UserEmailShouldBeNotExists src/starterProject/Application/Features/Auth/Rules/AuthBusinessRules.cs:77
- Async method without CancellationToken: OperationClaimIdShouldExistWhenSelected src/starterProject/Application/Features/OperationClaims/Rules/OperationClaimBusinessRules.cs:36
- Async method without CancellationToken: OperationClaimNameShouldNotExistWhenCreating src/starterProject/Application/Features/OperationClaims/Rules/OperationClaimBusinessRules.cs:43
- Async method without CancellationToken: OperationClaimNameShouldNotExistWhenUpdating src/starterProject/Application/Features/OperationClaims/Rules/OperationClaimBusinessRules.cs:50
- Async method without CancellationToken: UserOperationClaimIdShouldExistWhenSelected src/starterProject/Application/Features/UserOperationClaims/Rules/UserOperationClaimBusinessRules.cs:36
- Async method without CancellationToken: UserShouldNotHasOperationClaimAlreadyWhenInsert src/starterProject/Application/Features/UserOperationClaims/Rules/UserOperationClaimBusinessRules.cs:49
- Async method without CancellationToken: UserShouldNotHasOperationClaimAlreadyWhenUpdated src/starterProject/Application/Features/UserOperationClaims/Rules/UserOperationClaimBusinessRules.cs:58
- Async method without CancellationToken: UserIdShouldBeExistsWhenSelected src/starterProject/Application/Features/Users/Rules/UserBusinessRules.cs:34
- Async method without CancellationToken: UserEmailShouldNotExistsWhenInsert src/starterProject/Application/Features/Users/Rules/UserBusinessRules.cs:47
- Async method without CancellationToken: UserEmailShouldNotExistsWhenUpdate src/starterProject/Application/Features/Users/Rules/UserBusinessRules.cs:54
- Async method without CancellationToken: SendAuthenticatorCode src/starterProject/Application/Services/AuthenticatorService/AuthenticatorManager.cs:65
- Async method without CancellationToken: VerifyAuthenticatorCode src/starterProject/Application/Services/AuthenticatorService/AuthenticatorManager.cs:71
- Async method without CancellationToken: SendAuthenticatorCodeWithEmail src/starterProject/Application/Services/AuthenticatorService/AuthenticatorManager.cs:79
- Async method without CancellationToken: VerifyAuthenticatorCodeWithEmail src/starterProject/Application/Services/AuthenticatorService/AuthenticatorManager.cs:105
- Async method without CancellationToken: VerifyAuthenticatorCodeWithOtp src/starterProject/Application/Services/AuthenticatorService/AuthenticatorManager.cs:118
- Async method without CancellationToken: CreateAccessToken src/starterProject/Application/Services/AuthService/AuthManager.cs:37
- Async method without CancellationToken: AddRefreshToken src/starterProject/Application/Services/AuthService/AuthManager.cs:47
- Async method without CancellationToken: DeleteOldRefreshTokens src/starterProject/Application/Services/AuthService/AuthManager.cs:53
- Async method without CancellationToken: GetRefreshTokenByToken src/starterProject/Application/Services/AuthService/AuthManager.cs:62
- Async method without CancellationToken: RevokeRefreshToken src/starterProject/Application/Services/AuthService/AuthManager.cs:68
- Async method without CancellationToken: RotateRefreshToken src/starterProject/Application/Services/AuthService/AuthManager.cs:82
- Async method without CancellationToken: RevokeDescendantRefreshTokens src/starterProject/Application/Services/AuthService/AuthManager.cs:93
- Async method without CancellationToken: UpdateAsync src/starterProject/Application/Services/ImageService/ImageServiceBase.cs:10
- Async method without CancellationToken: AddAsync src/starterProject/Application/Services/OperationClaims/OperationClaimManager.cs:66
- Async method without CancellationToken: UpdateAsync src/starterProject/Application/Services/OperationClaims/OperationClaimManager.cs:75
- No authorization
- No authorization REDACTED:31
- No authorization REDACTED:43
- No authorization REDACTED:52
- No authorization REDACTED:62
- No authorization REDACTED:71
- No authorization REDACTED:85
- No authorization REDACTED:94
- No authorization REDACTED:103
- No authorization REDACTED:17
- No authorization REDACTED:24
- No authorization REDACTED:32
- No authorization REDACTED:39
- No authorization REDACTED:46
- No authorization REDACTED:17
- No authorization REDACTED:24
- No authorization REDACTED:32
- No authorization REDACTED:39
- No authorization REDACTED:46
- No authorization REDACTED:18
- No authorization REDACTED:25
- No authorization REDACTED:33
- No authorization REDACTED:41
- No authorization REDACTED:48
- No authorization REDACTED:55
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Dead code: OperationClaimManager src/starterProject/Application/Services/OperationClaims/OperationClaimManager.cs:10
- Dead code: ITranslateService src/starterProject/Application/Services/TranslateService/ITranslateService.cs:3
- Dead code: UserUserOperationClaimManager src/starterProject/Application/Services/UserOperationClaims/UserOperationClaimManager.cs:10
- Dead code: UpdateByAuthFromServiceRequestDto src/starterProject/WebAPI/Controllers/Dtos/UpdateByAuthFromServiceRequestDto.cs:3
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Deprecated: System.IdentityModel.Tokens.Jwt src/starterProject/WebAPI/WebAPI.csproj:9
- Deprecated: xunit REDACTED:10
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- No data-protection/encryption
- TodoComment src/starterProject/WebAPI/Controllers/BaseController.cs:25
- REDACTED
- REDACTED
- Members sharing a duplicated core (6 members, 50+ identical tokens) src/starterProject/Persistence/EntityConfigurations/EmailAuthenticatorConfiguration.cs:10
- Duplicated block (8 lines × 3) src/starterProject/Application/Features/OperationClaims/Constants/OperationClaimsOperationClaims.cs:7
- Duplicated block (9 lines × 3) src/starterProject/Persistence/EntityConfigurations/EmailAuthenticatorConfiguration.cs:18
- Duplicated block (8 lines × 6) src/starterProject/Persistence/EntityConfigurations/EmailAuthenticatorConfiguration.cs:16
- Duplicated block (5 lines × 2) src/starterProject/Application/Features/Users/Commands/Create/CreateUserCommandValidator.cs:9
- Duplicated block (6 lines × 4) src/starterProject/Application/Features/Users/Commands/Create/CreatedUserResponse.cs:22
- No test project references Persistence REDACTED
- No test project references WebAPI src/starterProject/WebAPI/WebAPI.csproj
- No test project references Infrastructure src/starterProject/Infrastructure/Infrastructure.csproj
- Secure cookie flags not detected REDACTED:120
- NuGet dependencies are not locked
Minor — 50 finding(s)
- Orphaned file src/starterProject/Application/Services/AuthenticatorService/AuthenticatorManager.cs:1
- Orphaned file REDACTED:1
- Orphaned file src/starterProject/Application/Services/AuthService/AuthManager.cs:1
- Orphaned file src/starterProject/WebAPI/Program.cs:1
- Orphaned file src/starterProject/Persistence/EntityConfigurations/OperationClaimConfiguration.cs:1
- Orphaned file src/starterProject/Application/Services/UserOperationClaims/UserOperationClaimManager.cs:1
- Orphaned file src/starterProject/Application/ApplicationServiceRegistration.cs:1
- Orphaned file src/starterProject/Application/Features/Auth/Rules/AuthBusinessRules.cs:1
- Orphaned file src/starterProject/Application/Features/Auth/Commands/EnableEmailAuthenticator/EnableEmailAuthenticatorCommand.cs:1
- Orphaned file src/starterProject/Application/Services/OperationClaims/OperationClaimManager.cs:1
- Orphaned file src/starterProject/Application/Features/Auth/Commands/Login/LoginCommand.cs:1
- Orphaned file src/starterProject/Application/Features/Users/Commands/UpdateFromAuth/UpdateUserFromAuthCommand.cs:1
- Orphaned file src/starterProject/Application/Features/Auth/Commands/EnableOtpAuthenticator/EnableOtpAuthenticatorCommand.cs:1
- Orphaned file src/starterProject/Application/Features/Auth/Commands/RefreshToken/RefreshTokenCommand.cs:1
- Orphaned file src/starterProject/Application/Features/UserOperationClaims/Commands/Update/UpdateUserOperationClaimCommand.cs:1
- Orphaned file src/starterProject/Application/Features/UserOperationClaims/Rules/UserOperationClaimBusinessRules.cs:1
- Orphaned file src/starterProject/Application/Features/Auth/Commands/Register/RegisterCommand.cs:1
- Orphaned file src/starterProject/Application/Features/Auth/Commands/VerifyOtpAuthenticator/VerifyOtpAuthenticatorCommand.cs:1
- Orphaned file src/starterProject/Application/Features/Users/Commands/Update/UpdateUserCommand.cs:1
- Orphaned file src/starterProject/Application/Features/OperationClaims/Commands/Update/UpdateOperationClaimCommand.cs:1
- Orphaned file src/starterProject/Application/Services/UsersService/UserManager.cs:1
- Orphaned file src/starterProject/Application/Features/Users/Commands/Create/CreateUserCommand.cs:1
- Orphaned file src/starterProject/Application/Features/UserOperationClaims/Commands/Create/CreateUserOperationClaimCommand.cs:1
- Orphaned file REDACTED:1
- Outdated: AutoMapper REDACTED:11
- Outdated: Swashbuckle.AspNetCore src/starterProject/WebAPI/WebAPI.csproj:8
- Outdated: coverlet.collector REDACTED:18
- Outdated: Xunit.DependencyInjection REDACTED:13
- No security response headers detected
- No security response headers detected src/starterProject/WebAPI/Program.cs:19
- No app-layer HTTPS enforcement detected
- No app-layer HTTPS enforcement detected src/starterProject/WebAPI/Program.cs:19
- No ADRs found
- Scattered collaborators
- Dormant codebase
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- IL efficiency: 3 authored method(s) exceed the IL budget src/starterProject/Persistence/EntityConfigurations/RefreshTokenConfiguration.cs:11
- No ADRs
- Inconsistent root namespaces
- README/code drift README.md:41
- Logging is not universal
- No SAST REDACTED:6
- No dependency-update automation REDACTED:11
- No release approval gate
- No changelog
- Not all async methods take a CancellationToken
- Null-forgiving operator (`!`) suppressions reduce the NRT score
Minor — 34 finding(s)
- Outdated: MediatR
- Outdated: NArchitecture.Core.Application
- Outdated: NArchitecture.Core.CrossCuttingConcerns.Exception
- Outdated: NArchitecture.Core.CrossCuttingConcerns.Logging.Serilog.File
- Outdated: NArchitecture.Core.ElasticSearch
- Outdated: NArchitecture.Core.Localization.Abstraction
- Outdated: NArchitecture.Core.Localization.Resource.Yaml.DependencyInjection
- Outdated: NArchitecture.Core.Mailing
- Outdated: NArchitecture.Core.Mailing.Mailkit
- Outdated: NArchitecture.Core.Security.DependencyInjection
- Outdated: NArchitecture.Core.Persistence
- Outdated: NArchitecture.Core.Security
- Outdated: Microsoft.EntityFrameworkCore.InMemory
- Outdated: Microsoft.EntityFrameworkCore.SqlServer
- Outdated: Microsoft.Extensions.Configuration.Abstractions
- Outdated: NArchitecture.Core.Persistence.DependencyInjection
- Outdated: Microsoft.AspNetCore.Authentication.JwtBearer
- Outdated: Microsoft.EntityFrameworkCore.Tools
- Outdated: Microsoft.Extensions.Caching.StackExchangeRedis
- Outdated: Microsoft.Extensions.DependencyInjection
- Outdated: Microsoft.Extensions.Logging
- Outdated: NArchitecture.Core.CrossCuttingConcerns.Exception.WebApi
- Outdated: NArchitecture.Core.Localization.WebApi
- Outdated: NArchitecture.Core.Persistence.WebApi
- Outdated: NArchitecture.Core.Security.WebApi.Swagger
- Mock framework: Moq
Appendix B — Reproduction & audit trail
| Dimension | Tool | Version | Command | Findings | Raw output |
|---|---|---|---|---|---|
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-1cf1ee6659fb40958ac50e06971ae648/history.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-1cf1ee6659fb40958ac50e06971ae648/tree.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-tree.json |
| D29 · Static Analysis (SAST) | semgrep | — | semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/canine-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt . | 31 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | dotnet | — | dotnet list NArchitecture.sln package --vulnerable --include-transitive --format json | 12 | artifacts/raw/dotnet-vulnerable.json |
| D31 · IaC & Container Security | trivy | — | trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan. | 0 | — |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. | 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-cc56317a3d0341da8de633965584b8fe | 0 | artifacts/raw/osv-scanner.json |
Appendix C — Personal-data map
Name — 16 field(s)
- CreateUserCommand.FirstName src/starterProject/Application/Features/Users/Commands/Create/CreateUserCommand.cs:15
- CreateUserCommand.LastName src/starterProject/Application/Features/Users/Commands/Create/CreateUserCommand.cs:16
- CreatedUserResponse.FirstName src/starterProject/Application/Features/Users/Commands/Create/CreatedUserResponse.cs:8
- CreatedUserResponse.LastName src/starterProject/Application/Features/Users/Commands/Create/CreatedUserResponse.cs:9
- UpdateUserCommand.FirstName src/starterProject/Application/Features/Users/Commands/Update/UpdateUserCommand.cs:16
- UpdateUserCommand.LastName src/starterProject/Application/Features/Users/Commands/Update/UpdateUserCommand.cs:17
- UpdatedUserResponse.FirstName src/starterProject/Application/Features/Users/Commands/Update/UpdatedUserResponse.cs:8
- UpdatedUserResponse.LastName src/starterProject/Application/Features/Users/Commands/Update/UpdatedUserResponse.cs:9
- UpdateUserFromAuthCommand.FirstName src/starterProject/Application/Features/Users/Commands/UpdateFromAuth/UpdateUserFromAuthCommand.cs:14
- UpdateUserFromAuthCommand.LastName src/starterProject/Application/Features/Users/Commands/UpdateFromAuth/UpdateUserFromAuthCommand.cs:15
- UpdatedUserFromAuthResponse.FirstName src/starterProject/Application/Features/Users/Commands/UpdateFromAuth/UpdatedUserFromAuthResponse.cs:9
- UpdatedUserFromAuthResponse.LastName src/starterProject/Application/Features/Users/Commands/UpdateFromAuth/UpdatedUserFromAuthResponse.cs:10
- GetByIdUserResponse.FirstName src/starterProject/Application/Features/Users/Queries/GetById/GetByIdUserResponse.cs:8
- GetByIdUserResponse.LastName src/starterProject/Application/Features/Users/Queries/GetById/GetByIdUserResponse.cs:9
- GetListUserListItemDto.FirstName src/starterProject/Application/Features/Users/Queries/GetList/GetListUserListItemDto.cs:8
- GetListUserListItemDto.LastName src/starterProject/Application/Features/Users/Queries/GetList/GetListUserListItemDto.cs:9
Email — 10 field(s)
- EnableEmailAuthenticatorCommand.VerifyEmailUrlPrefix src/starterProject/Application/Features/Auth/Commands/EnableEmailAuthenticator/EnableEmailAuthenticatorCommand.cs:18
- CreateUserCommand.Email src/starterProject/Application/Features/Users/Commands/Create/CreateUserCommand.cs:17
- CreatedUserResponse.Email src/starterProject/Application/Features/Users/Commands/Create/CreatedUserResponse.cs:10
- UpdateUserCommand.Email src/starterProject/Application/Features/Users/Commands/Update/UpdateUserCommand.cs:18
- UpdatedUserResponse.Email src/starterProject/Application/Features/Users/Commands/Update/UpdatedUserResponse.cs:10
- UpdatedUserFromAuthResponse.Email src/starterProject/Application/Features/Users/Commands/UpdateFromAuth/UpdatedUserFromAuthResponse.cs:11
- GetByIdUserResponse.Email src/starterProject/Application/Features/Users/Queries/GetById/GetByIdUserResponse.cs:10
- GetListUserListItemDto.Email src/starterProject/Application/Features/Users/Queries/GetList/GetListUserListItemDto.cs:10
- User.EmailAuthenticators src/starterProject/Domain/Entities/User.cs:8
- BaseDbContext.EmailAuthenticators src/starterProject/Persistence/Contexts/BaseDbContext.cs:11