Executive summary
marlonajgayle/dotnet-web-api-template falls short of our standard for a template or a sample because its Testing dimensions are rated Critical, and the project has no automated tests. It scores 47 out of 100, which alone would earn Adequate, but it is rated Weak: a rating can't sit more than one step above its weakest group.
Production Readiness, at 36, is the weakest lens and counts most in the score. The best first steps are adding automated tests and replacing the three exposed passwords or keys and switching the old ones off, each worth about 9 points. Raising Production Readiness to 52 would lift the score to about 54.
Seven pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Three known security holes in the packages the code depends on can be used by attackers, and three passwords or keys in the code and two in the code's history are open to anyone who can read the repository. Pinning each tool to an exact version, updating the vulnerable packages and replacing each exposed password or key would close these risks. Limiting each secret to its own step would fix the three secrets exposed to more of the pipeline than needed, and fixing the weaknesses the scanner points to would deal with the two security weaknesses in the code. The two data fields that are written but never read need removing.
The product code is 3,256 lines, about €3,500 to rebuild.
If Production Readiness rose from 36 to 52, the lowest score rated Strong, the score would rise from 47 to about 54.
New since the last survey: 3 findings
- Outbound HTTP resilience · Outbound HTTP without resilience src/content/src/NetWebApiTemplate.Infrastructure/DependencyInjection.cs
- Ambient inputs in the domain · Domain type reads the wall clock: RefreshToken src/content/src/NetWebApiTemplate.Domain/Entities/RefreshToken.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/content/src/NetWebApiTemplate.Application/Shared/Behaviours/ValidationBehaviour.cs
Fixed since the last survey: 46 findings
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/content/src/NetWebApiTemplate.Application/Shared/Behaviours/ValidationBehaviour.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/content/src/NetWebApiTemplate.Application/Shared/Behaviours/ValidationBehaviour.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/content/src/NetWebApiTemplate.Application/Shared/Models/PaginatedList.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/content/src/NetWebApiTemplate.Application/Shared/Models/PaginatedList.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/content/src/NetWebApiTemplate.Infrastructure/ApiClients/GitHub/GitHubApiService.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/content/src/NetWebApiTemplate.Infrastructure/Auth/AuthenticationService.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/content/src/NetWebApiTemplate.Infrastructure/Auth/AuthenticationService.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/content/src/NetWebApiTemplate.Infrastructure/Auth/AuthenticationService.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/content/src/NetWebApiTemplate.Infrastructure/Auth/AuthenticationService.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/content/src/NetWebApiTemplate.Infrastructure/Auth/AuthenticationService.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/content/src/NetWebApiTemplate.Infrastructure/Auth/AuthenticationService.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/content/src/NetWebApiTemplate.Infrastructure/Auth/AuthenticationService.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/content/src/NetWebApiTemplate.Infrastructure/Auth/AuthenticationService.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/content/src/NetWebApiTemplate.Infrastructure/Auth/AuthenticationService.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/content/src/NetWebApiTemplate.Infrastructure/Auth/AuthenticationService.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/content/src/NetWebApiTemplate.Infrastructure/Auth/AuthenticationService.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/content/src/NetWebApiTemplate.Infrastructure/Auth/AuthenticationService.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/content/src/NetWebApiTemplate.Infrastructure/Auth/AuthenticationService.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/content/src/NetWebApiTemplate.Infrastructure/Auth/AuthenticationService.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/content/src/NetWebApiTemplate.Infrastructure/Auth/AuthenticationService.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/content/src/NetWebApiTemplate.Infrastructure/Auth/AuthenticationService.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/content/src/NetWebApiTemplate.Infrastructure/Auth/AuthenticationService.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/content/src/NetWebApiTemplate.Infrastructure/Auth/AuthenticationService.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/content/src/NetWebApiTemplate.Infrastructure/Auth/JwtTokenService.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/content/src/NetWebApiTemplate.Infrastructure/Auth/JwtTokenService.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/content/src/NetWebApiTemplate.Infrastructure/Auth/JwtTokenService.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/content/src/NetWebApiTemplate.Infrastructure/Auth/JwtTokenService.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/content/src/NetWebApiTemplate.Infrastructure/Auth/JwtTokenService.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/content/src/NetWebApiTemplate.Infrastructure/Auth/JwtTokenService.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/content/src/NetWebApiTemplate.Infrastructure/Auth/JwtTokenService.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/content/src/NetWebApiTemplate.Infrastructure/Auth/JwtTokenService.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/content/src/NetWebApiTemplate.Infrastructure/Auth/JwtTokenService.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/content/src/NetWebApiTemplate.Infrastructure/Auth/JwtTokenService.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/content/src/NetWebApiTemplate.Infrastructure/Auth/JwtTokenService.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/content/src/NetWebApiTemplate.Infrastructure/Auth/JwtTokenService.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/content/src/NetWebApiTemplate.Infrastructure/Auth/JwtTokenService.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) REDACTED
- Async & latency hygiene · Awaits without ConfigureAwait(false) REDACTED
- Async & latency hygiene · Awaits without ConfigureAwait(false) REDACTED
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/content/src/NetWebApiTemplate.Infrastructure/Email/EmailSenderService.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) REDACTED
- Async & latency hygiene · Awaits without ConfigureAwait(false) REDACTED
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/content/src/NetWebApiTemplate.Persistence/Repositories/FaqRepository.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/content/src/NetWebApiTemplate.Persistence/Repositories/FaqRepository.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/content/src/NetWebApiTemplate.Persistence/Repositories/ProductRepository.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/content/src/NetWebApiTemplate.Persistence/Repositories/ProductRepository.cs
Rebuild cost: about €3,500 · Estimate
| Cost to rebuild | €1,200 to €5,800, for 20 to 61 hours of work, under 0.1 person-years for one engineer |
|---|---|
| Difficulty of the problem | Very high, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.7 at a score of 47. 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,256 lines of product code, of which 54% is declarations and boilerplate, 37% straight logic and 9% logic with branches |
| Comment lines | The estimate prices 3,128 lines. Comment lines count towards the size of 3,256 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 Api.Endpoints | 2 Application.Features.Authentication | 3 Application.Features.Authentication.Models | 4 Application.Features.EmailNotification | 5 Application.Shared.Models | 6 Domain.Entities | 7 Domain.Shared | 8 Api.Endpoints.Faqs | 9 Application.Features.Authentication.Interfaces | 10 Application.Features.Faqs.Interfaces | 11 Application.Features.Products.Interfaces | 12 Application.Shared.Extensions | 13 Application.Shared.Interface | 14 Persistence.Configurations | 15 Api.Endpoints.Faq | 16 Api.Services | 17 Application.Features.Authentication.Commands.AddClaimToUser | 18 Application.Features.Authentication.Commands.AddUserToRole | 19 Application.Features.Authentication.Commands.CreateRole | 20 Application.Features.Authentication.Commands.Login | 21 Application.Features.Authentication.Commands.RefreshToken | 22 Application.Features.Authentication.Commands.RegisterUser | 23 Application.Features.Authentication.Commands.RemoveUserFromRole | 24 Application.Features.Authentication.Queries.GetAllRoles | 25 Application.Features.Authentication.Queries.GetUserClaims | 26 Application.Features.Authentication.Queries.GetUserRoles | 27 Application.Features.Faqs.Queries.GetAllFaqs | 28 Application.Features.Products.Commands | 29 Application.Features.Products.Commands.DeleteProduct | 30 Application.Features.Products.Commands.UpdateProduct | 31 Application.Features.Products.Queries.GetAllProducts | 32 Infrastructure.ApiClients.GitHub | 33 Infrastructure.Auth | 34 Infrastructure.BackgroundJobs | 35 Infrastructure.Cache.InMemory | 36 Infrastructure.DataProtection | 37 Infrastructure.Email | 38 Infrastructure.Outboxes | 39 Persistence | 40 Persistence.Repositories |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 Api.Endpoints | ||||||||||||||||||||||||||||||||||||||||
| 2 Application.Features.Authentication | ||||||||||||||||||||||||||||||||||||||||
| 3 Application.Features.Authentication.Models | ||||||||||||||||||||||||||||||||||||||||
| 4 Application.Features.EmailNotification | ||||||||||||||||||||||||||||||||||||||||
| 5 Application.Shared.Models | ||||||||||||||||||||||||||||||||||||||||
| 6 Domain.Entities | ||||||||||||||||||||||||||||||||||||||||
| 7 Domain.Shared | ||||||||||||||||||||||||||||||||||||||||
| 8 Api.Endpoints.Faqs | 1 | |||||||||||||||||||||||||||||||||||||||
| 9 Application.Features.Authentication.Interfaces | 3 | |||||||||||||||||||||||||||||||||||||||
| 10 Application.Features.Faqs.Interfaces | 1 | |||||||||||||||||||||||||||||||||||||||
| 11 Application.Features.Products.Interfaces | 1 | |||||||||||||||||||||||||||||||||||||||
| 12 Application.Shared.Extensions | 1 | |||||||||||||||||||||||||||||||||||||||
| 13 Application.Shared.Interface | 2 | 5 | 1 | |||||||||||||||||||||||||||||||||||||
| 14 Persistence.Configurations | 5 | |||||||||||||||||||||||||||||||||||||||
| 15 Api.Endpoints.Faq | 1 | |||||||||||||||||||||||||||||||||||||||
| 16 Api.Services | 1 | |||||||||||||||||||||||||||||||||||||||
| 17 Application.Features.Authentication.Commands.AddClaimToUser | 1 | |||||||||||||||||||||||||||||||||||||||
| 18 Application.Features.Authentication.Commands.AddUserToRole | 1 | |||||||||||||||||||||||||||||||||||||||
| 19 Application.Features.Authentication.Commands.CreateRole | 1 | |||||||||||||||||||||||||||||||||||||||
| 20 Application.Features.Authentication.Commands.Login | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 21 Application.Features.Authentication.Commands.RefreshToken | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 22 Application.Features.Authentication.Commands.RegisterUser | 1 | 1 | 1 | 2 | ||||||||||||||||||||||||||||||||||||
| 23 Application.Features.Authentication.Commands.RemoveUserFromRole | 1 | |||||||||||||||||||||||||||||||||||||||
| 24 Application.Features.Authentication.Queries.GetAllRoles | 1 | |||||||||||||||||||||||||||||||||||||||
| 25 Application.Features.Authentication.Queries.GetUserClaims | 1 | |||||||||||||||||||||||||||||||||||||||
| 26 Application.Features.Authentication.Queries.GetUserRoles | 1 | |||||||||||||||||||||||||||||||||||||||
| 27 Application.Features.Faqs.Queries.GetAllFaqs | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 28 Application.Features.Products.Commands | 1 | |||||||||||||||||||||||||||||||||||||||
| 29 Application.Features.Products.Commands.DeleteProduct | 1 | |||||||||||||||||||||||||||||||||||||||
| 30 Application.Features.Products.Commands.UpdateProduct | 1 | |||||||||||||||||||||||||||||||||||||||
| 31 Application.Features.Products.Queries.GetAllProducts | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 32 Infrastructure.ApiClients.GitHub | 1 | |||||||||||||||||||||||||||||||||||||||
| 33 Infrastructure.Auth | 4 | 2 | 1 | |||||||||||||||||||||||||||||||||||||
| 34 Infrastructure.BackgroundJobs | 1 | |||||||||||||||||||||||||||||||||||||||
| 35 Infrastructure.Cache.InMemory | 1 | |||||||||||||||||||||||||||||||||||||||
| 36 Infrastructure.DataProtection | 1 | |||||||||||||||||||||||||||||||||||||||
| 37 Infrastructure.Email | 2 | 1 | ||||||||||||||||||||||||||||||||||||||
| 38 Infrastructure.Outboxes | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 39 Persistence | 5 | 3 | ||||||||||||||||||||||||||||||||||||||
| 40 Persistence.Repositories | 2 | 1 | 1 | 2 |
8→1 Api.Endpoints.Faqs uses Api.Endpoints✕
- Connections
- 1 pair of types, where a type in Api.Endpoints.Faqs uses a type in Api.Endpoints.
- The types involved
NetWebApiTemplate.Api.Endpoints.Faqs.FaqRequest→NetWebApiTemplate.Api.Endpoints.PaginationRequest
- Direction
- Api.Endpoints.Faqs uses Api.Endpoints, so a change to Api.Endpoints can break Api.Endpoints.Faqs, while a change to Api.Endpoints.Faqs can't break Api.Endpoints.
- Position
- Below the diagonal: Api.Endpoints.Faqs uses a module listed above it, which is the healthy direction.
9→3 Application.Features.Authentication.Interfaces uses Application.Features.Authentication.Models✕
- Connections
- 3 pairs of types, where a type in Application.Features.Authentication.Interfaces uses a type in Application.Features.Authentication.Models.
- The types involved
NetWebApiTemplate.Application.Features.Authentication.Interfaces.IAuthenticationService→NetWebApiTemplate.Application.Features.Authentication.Models.AppUserNetWebApiTemplate.Application.Features.Authentication.Interfaces.IAuthenticationService→NetWebApiTemplate.Application.Features.Authentication.Models.ResultNetWebApiTemplate.Application.Features.Authentication.Interfaces.IJwtTokenService→NetWebApiTemplate.Application.Features.Authentication.Models.TokenResult
- Direction
- Application.Features.Authentication.Interfaces uses Application.Features.Authentication.Models, so a change to Application.Features.Authentication.Models can break Application.Features.Authentication.Interfaces, while a change to Application.Features.Authentication.Interfaces can't break Application.Features.Authentication.Models.
- Position
- Below the diagonal: Application.Features.Authentication.Interfaces uses a module listed above it, which is the healthy direction.
10→6 Application.Features.Faqs.Interfaces uses Domain.Entities✕
- Connections
- 1 pair of types, where a type in Application.Features.Faqs.Interfaces uses a type in Domain.Entities.
- The types involved
NetWebApiTemplate.Application.Features.Faqs.Interfaces.IFaqRepository→NetWebApiTemplate.Domain.Entities.Faq
- Direction
- Application.Features.Faqs.Interfaces uses Domain.Entities, so a change to Domain.Entities can break Application.Features.Faqs.Interfaces, while a change to Application.Features.Faqs.Interfaces can't break Domain.Entities.
- Position
- Below the diagonal: Application.Features.Faqs.Interfaces uses a module listed above it, which is the healthy direction.
11→6 Application.Features.Products.Interfaces uses Domain.Entities✕
- Connections
- 1 pair of types, where a type in Application.Features.Products.Interfaces uses a type in Domain.Entities.
- The types involved
NetWebApiTemplate.Application.Features.Products.Interfaces.IProductRepository→NetWebApiTemplate.Domain.Entities.Product
- Direction
- Application.Features.Products.Interfaces uses Domain.Entities, so a change to Domain.Entities can break Application.Features.Products.Interfaces, while a change to Application.Features.Products.Interfaces can't break Domain.Entities.
- Position
- Below the diagonal: Application.Features.Products.Interfaces uses a module listed above it, which is the healthy direction.
12→5 Application.Shared.Extensions uses Application.Shared.Models✕
- Connections
- 1 pair of types, where a type in Application.Shared.Extensions uses a type in Application.Shared.Models.
- The types involved
NetWebApiTemplate.Application.Shared.Extensions.PaginationExtension→NetWebApiTemplate.Application.Shared.Models.PaginatedList
- Direction
- Application.Shared.Extensions uses Application.Shared.Models, so a change to Application.Shared.Models can break Application.Shared.Extensions, while a change to Application.Shared.Extensions can't break Application.Shared.Models.
- Position
- Below the diagonal: Application.Shared.Extensions uses a module listed above it, which is the healthy direction.
13→4 Application.Shared.Interface uses Application.Features.EmailNotification✕
- Connections
- 2 pairs of types, where a type in Application.Shared.Interface uses a type in Application.Features.EmailNotification.
- The types involved
NetWebApiTemplate.Application.Shared.Interface.IEmailSender→NetWebApiTemplate.Application.Features.EmailNotification.EmailMessageNetWebApiTemplate.Application.Shared.Interface.IEmailSender→NetWebApiTemplate.Application.Features.EmailNotification.EmailTemplates
- Direction
- Application.Shared.Interface uses Application.Features.EmailNotification, so a change to Application.Features.EmailNotification can break Application.Shared.Interface, while a change to Application.Shared.Interface can't break Application.Features.EmailNotification.
- Position
- Below the diagonal: Application.Shared.Interface uses a module listed above it, which is the healthy direction.
13→6 Application.Shared.Interface uses Domain.Entities✕
- Connections
- 5 pairs of types, where a type in Application.Shared.Interface uses a type in Domain.Entities.
- The types involved
NetWebApiTemplate.Application.Shared.Interface.INetWebApiTemplateDbContext→NetWebApiTemplate.Domain.Entities.FaqNetWebApiTemplate.Application.Shared.Interface.INetWebApiTemplateDbContext→NetWebApiTemplate.Domain.Entities.OutboxMessageNetWebApiTemplate.Application.Shared.Interface.INetWebApiTemplateDbContext→NetWebApiTemplate.Domain.Entities.ProductNetWebApiTemplate.Application.Shared.Interface.INetWebApiTemplateDbContext→NetWebApiTemplate.Domain.Entities.ProductCatergoryNetWebApiTemplate.Application.Shared.Interface.INetWebApiTemplateDbContext→NetWebApiTemplate.Domain.Entities.RefreshToken
- Direction
- Application.Shared.Interface uses Domain.Entities, so a change to Domain.Entities can break Application.Shared.Interface, while a change to Application.Shared.Interface can't break Domain.Entities.
- Position
- Below the diagonal: Application.Shared.Interface uses a module listed above it, which is the healthy direction.
13→7 Application.Shared.Interface uses Domain.Shared✕
- Connections
- 1 pair of types, where a type in Application.Shared.Interface uses a type in Domain.Shared.
- The types involved
NetWebApiTemplate.Application.Shared.Interface.IOutboxService→NetWebApiTemplate.Domain.Shared.IDomainEvent
- Direction
- Application.Shared.Interface uses Domain.Shared, so a change to Domain.Shared can break Application.Shared.Interface, while a change to Application.Shared.Interface can't break Domain.Shared.
- Position
- Below the diagonal: Application.Shared.Interface uses a module listed above it, which is the healthy direction.
14→6 Persistence.Configurations uses Domain.Entities✕
- Connections
- 5 pairs of types, where a type in Persistence.Configurations uses a type in Domain.Entities.
- The types involved
NetWebApiTemplate.Persistence.Configurations.FaqConfiguration→NetWebApiTemplate.Domain.Entities.FaqNetWebApiTemplate.Persistence.Configurations.OutboxMessageConfiguration→NetWebApiTemplate.Domain.Entities.OutboxMessageNetWebApiTemplate.Persistence.Configurations.ProductCategoryConfiguration→NetWebApiTemplate.Domain.Entities.ProductCatergoryNetWebApiTemplate.Persistence.Configurations.ProductConfiguration→NetWebApiTemplate.Domain.Entities.ProductNetWebApiTemplate.Persistence.Configurations.RefreshTokenConfigurations→NetWebApiTemplate.Domain.Entities.RefreshToken
- Direction
- Persistence.Configurations uses Domain.Entities, so a change to Domain.Entities can break Persistence.Configurations, while a change to Persistence.Configurations can't break Domain.Entities.
- Position
- Below the diagonal: Persistence.Configurations uses a module listed above it, which is the healthy direction.
15→8 Api.Endpoints.Faq uses Api.Endpoints.Faqs✕
- Connections
- 1 pair of types, where a type in Api.Endpoints.Faq uses a type in Api.Endpoints.Faqs.
- The types involved
NetWebApiTemplate.Api.Endpoints.Faq.FaqsController→NetWebApiTemplate.Api.Endpoints.Faqs.FaqRequest
- Direction
- Api.Endpoints.Faq uses Api.Endpoints.Faqs, so a change to Api.Endpoints.Faqs can break Api.Endpoints.Faq, while a change to Api.Endpoints.Faq can't break Api.Endpoints.Faqs.
- Position
- Below the diagonal: Api.Endpoints.Faq uses a module listed above it, which is the healthy direction.
16→13 Api.Services uses Application.Shared.Interface✕
- Connections
- 1 pair of types, where a type in Api.Services uses a type in Application.Shared.Interface.
- The types involved
NetWebApiTemplate.Api.Services.CurrentUserService→NetWebApiTemplate.Application.Shared.Interface.ICurrentUserService
- Direction
- Api.Services uses Application.Shared.Interface, so a change to Application.Shared.Interface can break Api.Services, while a change to Api.Services can't break Application.Shared.Interface.
- Position
- Below the diagonal: Api.Services uses a module listed above it, which is the healthy direction.
17→9 Application.Features.Authentication.Commands.AddClaimToUser uses Application.Features.Authentication.Interfaces✕
- Connections
- 1 pair of types, where a type in Application.Features.Authentication.Commands.AddClaimToUser uses a type in Application.Features.Authentication.Interfaces.
- The types involved
NetWebApiTemplate.Application.Features.Authentication.Commands.AddClaimToUser.AddClaimToUserCommandHandler→NetWebApiTemplate.Application.Features.Authentication.Interfaces.IAuthenticationService
- Direction
- Application.Features.Authentication.Commands.AddClaimToUser uses Application.Features.Authentication.Interfaces, so a change to Application.Features.Authentication.Interfaces can break Application.Features.Authentication.Commands.AddClaimToUser, while a change to Application.Features.Authentication.Commands.AddClaimToUser can't break Application.Features.Authentication.Interfaces.
- Position
- Below the diagonal: Application.Features.Authentication.Commands.AddClaimToUser uses a module listed above it, which is the healthy direction.
18→9 Application.Features.Authentication.Commands.AddUserToRole uses Application.Features.Authentication.Interfaces✕
- Connections
- 1 pair of types, where a type in Application.Features.Authentication.Commands.AddUserToRole uses a type in Application.Features.Authentication.Interfaces.
- The types involved
NetWebApiTemplate.Application.Features.Authentication.Commands.AddUserToRole.AddUserToRoleCommandHandler→NetWebApiTemplate.Application.Features.Authentication.Interfaces.IAuthenticationService
- Direction
- Application.Features.Authentication.Commands.AddUserToRole uses Application.Features.Authentication.Interfaces, so a change to Application.Features.Authentication.Interfaces can break Application.Features.Authentication.Commands.AddUserToRole, while a change to Application.Features.Authentication.Commands.AddUserToRole can't break Application.Features.Authentication.Interfaces.
- Position
- Below the diagonal: Application.Features.Authentication.Commands.AddUserToRole uses a module listed above it, which is the healthy direction.
19→9 Application.Features.Authentication.Commands.CreateRole uses Application.Features.Authentication.Interfaces✕
- Connections
- 1 pair of types, where a type in Application.Features.Authentication.Commands.CreateRole uses a type in Application.Features.Authentication.Interfaces.
- The types involved
NetWebApiTemplate.Application.Features.Authentication.Commands.CreateRole.CreateRoleCommandHandler→NetWebApiTemplate.Application.Features.Authentication.Interfaces.IAuthenticationService
- Direction
- Application.Features.Authentication.Commands.CreateRole uses Application.Features.Authentication.Interfaces, so a change to Application.Features.Authentication.Interfaces can break Application.Features.Authentication.Commands.CreateRole, while a change to Application.Features.Authentication.Commands.CreateRole can't break Application.Features.Authentication.Interfaces.
- Position
- Below the diagonal: Application.Features.Authentication.Commands.CreateRole uses a module listed above it, which is the healthy direction.
20→2 Application.Features.Authentication.Commands.Login uses Application.Features.Authentication✕
- Connections
- 1 pair of types, where a type in Application.Features.Authentication.Commands.Login uses a type in Application.Features.Authentication.
- The types involved
NetWebApiTemplate.Application.Features.Authentication.Commands.Login.LoginCommandHandler→NetWebApiTemplate.Application.Features.Authentication.AuthenticationResult
- Direction
- Application.Features.Authentication.Commands.Login uses Application.Features.Authentication, so a change to Application.Features.Authentication can break Application.Features.Authentication.Commands.Login, while a change to Application.Features.Authentication.Commands.Login can't break Application.Features.Authentication.
- Position
- Below the diagonal: Application.Features.Authentication.Commands.Login uses a module listed above it, which is the healthy direction.
20→9 Application.Features.Authentication.Commands.Login uses Application.Features.Authentication.Interfaces✕
- Connections
- 2 pairs of types, where a type in Application.Features.Authentication.Commands.Login uses a type in Application.Features.Authentication.Interfaces.
- The types involved
NetWebApiTemplate.Application.Features.Authentication.Commands.Login.LoginCommandHandler→NetWebApiTemplate.Application.Features.Authentication.Interfaces.IAuthenticationServiceNetWebApiTemplate.Application.Features.Authentication.Commands.Login.LoginCommandHandler→NetWebApiTemplate.Application.Features.Authentication.Interfaces.IJwtTokenService
- Direction
- Application.Features.Authentication.Commands.Login uses Application.Features.Authentication.Interfaces, so a change to Application.Features.Authentication.Interfaces can break Application.Features.Authentication.Commands.Login, while a change to Application.Features.Authentication.Commands.Login can't break Application.Features.Authentication.Interfaces.
- Position
- Below the diagonal: Application.Features.Authentication.Commands.Login uses a module listed above it, which is the healthy direction.
21→2 Application.Features.Authentication.Commands.RefreshToken uses Application.Features.Authentication✕
- Connections
- 1 pair of types, where a type in Application.Features.Authentication.Commands.RefreshToken uses a type in Application.Features.Authentication.
- The types involved
NetWebApiTemplate.Application.Features.Authentication.Commands.RefreshToken.RefreshTokenCommandHandler→NetWebApiTemplate.Application.Features.Authentication.AuthenticationResult
- Direction
- Application.Features.Authentication.Commands.RefreshToken uses Application.Features.Authentication, so a change to Application.Features.Authentication can break Application.Features.Authentication.Commands.RefreshToken, while a change to Application.Features.Authentication.Commands.RefreshToken can't break Application.Features.Authentication.
- Position
- Below the diagonal: Application.Features.Authentication.Commands.RefreshToken uses a module listed above it, which is the healthy direction.
21→9 Application.Features.Authentication.Commands.RefreshToken uses Application.Features.Authentication.Interfaces✕
- Connections
- 1 pair of types, where a type in Application.Features.Authentication.Commands.RefreshToken uses a type in Application.Features.Authentication.Interfaces.
- The types involved
NetWebApiTemplate.Application.Features.Authentication.Commands.RefreshToken.RefreshTokenCommandHandler→NetWebApiTemplate.Application.Features.Authentication.Interfaces.IJwtTokenService
- Direction
- Application.Features.Authentication.Commands.RefreshToken uses Application.Features.Authentication.Interfaces, so a change to Application.Features.Authentication.Interfaces can break Application.Features.Authentication.Commands.RefreshToken, while a change to Application.Features.Authentication.Commands.RefreshToken can't break Application.Features.Authentication.Interfaces.
- Position
- Below the diagonal: Application.Features.Authentication.Commands.RefreshToken uses a module listed above it, which is the healthy direction.
22→4 Application.Features.Authentication.Commands.RegisterUser uses Application.Features.EmailNotification✕
- Connections
- 1 pair of types, where a type in Application.Features.Authentication.Commands.RegisterUser uses a type in Application.Features.EmailNotification.
- The types involved
NetWebApiTemplate.Application.Features.Authentication.Commands.RegisterUser.UserRegisteredEventHandler→NetWebApiTemplate.Application.Features.EmailNotification.EmailTemplates
- Direction
- Application.Features.Authentication.Commands.RegisterUser uses Application.Features.EmailNotification, so a change to Application.Features.EmailNotification can break Application.Features.Authentication.Commands.RegisterUser, while a change to Application.Features.Authentication.Commands.RegisterUser can't break Application.Features.EmailNotification.
- Position
- Below the diagonal: Application.Features.Authentication.Commands.RegisterUser uses a module listed above it, which is the healthy direction.
22→7 Application.Features.Authentication.Commands.RegisterUser uses Domain.Shared✕
- Connections
- 1 pair of types, where a type in Application.Features.Authentication.Commands.RegisterUser uses a type in Domain.Shared.
- The types involved
NetWebApiTemplate.Application.Features.Authentication.Commands.RegisterUser.UserRegisteredEvent→NetWebApiTemplate.Domain.Shared.IDomainEvent
- Direction
- Application.Features.Authentication.Commands.RegisterUser uses Domain.Shared, so a change to Domain.Shared can break Application.Features.Authentication.Commands.RegisterUser, while a change to Application.Features.Authentication.Commands.RegisterUser can't break Domain.Shared.
- Position
- Below the diagonal: Application.Features.Authentication.Commands.RegisterUser uses a module listed above it, which is the healthy direction.
22→9 Application.Features.Authentication.Commands.RegisterUser uses Application.Features.Authentication.Interfaces✕
- Connections
- 1 pair of types, where a type in Application.Features.Authentication.Commands.RegisterUser uses a type in Application.Features.Authentication.Interfaces.
- The types involved
NetWebApiTemplate.Application.Features.Authentication.Commands.RegisterUser.RegisterUserCommandHandler→NetWebApiTemplate.Application.Features.Authentication.Interfaces.IAuthenticationService
- Direction
- Application.Features.Authentication.Commands.RegisterUser uses Application.Features.Authentication.Interfaces, so a change to Application.Features.Authentication.Interfaces can break Application.Features.Authentication.Commands.RegisterUser, while a change to Application.Features.Authentication.Commands.RegisterUser can't break Application.Features.Authentication.Interfaces.
- Position
- Below the diagonal: Application.Features.Authentication.Commands.RegisterUser uses a module listed above it, which is the healthy direction.
22→13 Application.Features.Authentication.Commands.RegisterUser uses Application.Shared.Interface✕
- Connections
- 2 pairs of types, where a type in Application.Features.Authentication.Commands.RegisterUser uses a type in Application.Shared.Interface.
- The types involved
NetWebApiTemplate.Application.Features.Authentication.Commands.RegisterUser.RegisterUserCommandHandler→NetWebApiTemplate.Application.Shared.Interface.IOutboxServiceNetWebApiTemplate.Application.Features.Authentication.Commands.RegisterUser.UserRegisteredEventHandler→NetWebApiTemplate.Application.Shared.Interface.IEmailSender
- Direction
- Application.Features.Authentication.Commands.RegisterUser uses Application.Shared.Interface, so a change to Application.Shared.Interface can break Application.Features.Authentication.Commands.RegisterUser, while a change to Application.Features.Authentication.Commands.RegisterUser can't break Application.Shared.Interface.
- Position
- Below the diagonal: Application.Features.Authentication.Commands.RegisterUser uses a module listed above it, which is the healthy direction.
23→9 Application.Features.Authentication.Commands.RemoveUserFromRole uses Application.Features.Authentication.Interfaces✕
- Connections
- 1 pair of types, where a type in Application.Features.Authentication.Commands.RemoveUserFromRole uses a type in Application.Features.Authentication.Interfaces.
- The types involved
NetWebApiTemplate.Application.Features.Authentication.Commands.RemoveUserFromRole.RemoveUserFromRoleCommandHandler→NetWebApiTemplate.Application.Features.Authentication.Interfaces.IAuthenticationService
- Direction
- Application.Features.Authentication.Commands.RemoveUserFromRole uses Application.Features.Authentication.Interfaces, so a change to Application.Features.Authentication.Interfaces can break Application.Features.Authentication.Commands.RemoveUserFromRole, while a change to Application.Features.Authentication.Commands.RemoveUserFromRole can't break Application.Features.Authentication.Interfaces.
- Position
- Below the diagonal: Application.Features.Authentication.Commands.RemoveUserFromRole uses a module listed above it, which is the healthy direction.
24→9 Application.Features.Authentication.Queries.GetAllRoles uses Application.Features.Authentication.Interfaces✕
- Connections
- 1 pair of types, where a type in Application.Features.Authentication.Queries.GetAllRoles uses a type in Application.Features.Authentication.Interfaces.
- The types involved
NetWebApiTemplate.Application.Features.Authentication.Queries.GetAllRoles.GetAllRolesQueryHandler→NetWebApiTemplate.Application.Features.Authentication.Interfaces.IAuthenticationService
- Direction
- Application.Features.Authentication.Queries.GetAllRoles uses Application.Features.Authentication.Interfaces, so a change to Application.Features.Authentication.Interfaces can break Application.Features.Authentication.Queries.GetAllRoles, while a change to Application.Features.Authentication.Queries.GetAllRoles can't break Application.Features.Authentication.Interfaces.
- Position
- Below the diagonal: Application.Features.Authentication.Queries.GetAllRoles uses a module listed above it, which is the healthy direction.
25→9 Application.Features.Authentication.Queries.GetUserClaims uses Application.Features.Authentication.Interfaces✕
- Connections
- 1 pair of types, where a type in Application.Features.Authentication.Queries.GetUserClaims uses a type in Application.Features.Authentication.Interfaces.
- The types involved
NetWebApiTemplate.Application.Features.Authentication.Queries.GetUserClaims.GetUserClaimsQueryHandler→NetWebApiTemplate.Application.Features.Authentication.Interfaces.IAuthenticationService
- Direction
- Application.Features.Authentication.Queries.GetUserClaims uses Application.Features.Authentication.Interfaces, so a change to Application.Features.Authentication.Interfaces can break Application.Features.Authentication.Queries.GetUserClaims, while a change to Application.Features.Authentication.Queries.GetUserClaims can't break Application.Features.Authentication.Interfaces.
- Position
- Below the diagonal: Application.Features.Authentication.Queries.GetUserClaims uses a module listed above it, which is the healthy direction.
26→9 Application.Features.Authentication.Queries.GetUserRoles uses Application.Features.Authentication.Interfaces✕
- Connections
- 1 pair of types, where a type in Application.Features.Authentication.Queries.GetUserRoles uses a type in Application.Features.Authentication.Interfaces.
- The types involved
NetWebApiTemplate.Application.Features.Authentication.Queries.GetUserRoles.GetUserRolesQueryHandler→NetWebApiTemplate.Application.Features.Authentication.Interfaces.IAuthenticationService
- Direction
- Application.Features.Authentication.Queries.GetUserRoles uses Application.Features.Authentication.Interfaces, so a change to Application.Features.Authentication.Interfaces can break Application.Features.Authentication.Queries.GetUserRoles, while a change to Application.Features.Authentication.Queries.GetUserRoles can't break Application.Features.Authentication.Interfaces.
- Position
- Below the diagonal: Application.Features.Authentication.Queries.GetUserRoles uses a module listed above it, which is the healthy direction.
27→5 Application.Features.Faqs.Queries.GetAllFaqs uses Application.Shared.Models✕
- Connections
- 1 pair of types, where a type in Application.Features.Faqs.Queries.GetAllFaqs uses a type in Application.Shared.Models.
- The types involved
NetWebApiTemplate.Application.Features.Faqs.Queries.GetAllFaqs.GetAllFaqsQueryHandler→NetWebApiTemplate.Application.Shared.Models.PaginatedList
- Direction
- Application.Features.Faqs.Queries.GetAllFaqs uses Application.Shared.Models, so a change to Application.Shared.Models can break Application.Features.Faqs.Queries.GetAllFaqs, while a change to Application.Features.Faqs.Queries.GetAllFaqs can't break Application.Shared.Models.
- Position
- Below the diagonal: Application.Features.Faqs.Queries.GetAllFaqs uses a module listed above it, which is the healthy direction.
27→13 Application.Features.Faqs.Queries.GetAllFaqs uses Application.Shared.Interface✕
- Connections
- 1 pair of types, where a type in Application.Features.Faqs.Queries.GetAllFaqs uses a type in Application.Shared.Interface.
- The types involved
NetWebApiTemplate.Application.Features.Faqs.Queries.GetAllFaqs.GetAllFaqsQueryHandler→NetWebApiTemplate.Application.Shared.Interface.INetWebApiTemplateDbContext
- Direction
- Application.Features.Faqs.Queries.GetAllFaqs uses Application.Shared.Interface, so a change to Application.Shared.Interface can break Application.Features.Faqs.Queries.GetAllFaqs, while a change to Application.Features.Faqs.Queries.GetAllFaqs can't break Application.Shared.Interface.
- Position
- Below the diagonal: Application.Features.Faqs.Queries.GetAllFaqs uses a module listed above it, which is the healthy direction.
28→13 Application.Features.Products.Commands uses Application.Shared.Interface✕
- Connections
- 1 pair of types, where a type in Application.Features.Products.Commands uses a type in Application.Shared.Interface.
- The types involved
NetWebApiTemplate.Application.Features.Products.Commands.CreateProductCommandHandler→NetWebApiTemplate.Application.Shared.Interface.INetWebApiTemplateDbContext
- Direction
- Application.Features.Products.Commands uses Application.Shared.Interface, so a change to Application.Shared.Interface can break Application.Features.Products.Commands, while a change to Application.Features.Products.Commands can't break Application.Shared.Interface.
- Position
- Below the diagonal: Application.Features.Products.Commands uses a module listed above it, which is the healthy direction.
29→13 Application.Features.Products.Commands.DeleteProduct uses Application.Shared.Interface✕
- Connections
- 1 pair of types, where a type in Application.Features.Products.Commands.DeleteProduct uses a type in Application.Shared.Interface.
- The types involved
NetWebApiTemplate.Application.Features.Products.Commands.DeleteProduct.DeleteProductCommandHandler→NetWebApiTemplate.Application.Shared.Interface.INetWebApiTemplateDbContext
- Direction
- Application.Features.Products.Commands.DeleteProduct uses Application.Shared.Interface, so a change to Application.Shared.Interface can break Application.Features.Products.Commands.DeleteProduct, while a change to Application.Features.Products.Commands.DeleteProduct can't break Application.Shared.Interface.
- Position
- Below the diagonal: Application.Features.Products.Commands.DeleteProduct uses a module listed above it, which is the healthy direction.
30→11 Application.Features.Products.Commands.UpdateProduct uses Application.Features.Products.Interfaces✕
- Connections
- 1 pair of types, where a type in Application.Features.Products.Commands.UpdateProduct uses a type in Application.Features.Products.Interfaces.
- The types involved
NetWebApiTemplate.Application.Features.Products.Commands.UpdateProduct.UpdateProductCommandHandler→NetWebApiTemplate.Application.Features.Products.Interfaces.IProductRepository
- Direction
- Application.Features.Products.Commands.UpdateProduct uses Application.Features.Products.Interfaces, so a change to Application.Features.Products.Interfaces can break Application.Features.Products.Commands.UpdateProduct, while a change to Application.Features.Products.Commands.UpdateProduct can't break Application.Features.Products.Interfaces.
- Position
- Below the diagonal: Application.Features.Products.Commands.UpdateProduct uses a module listed above it, which is the healthy direction.
31→5 Application.Features.Products.Queries.GetAllProducts uses Application.Shared.Models✕
- Connections
- 1 pair of types, where a type in Application.Features.Products.Queries.GetAllProducts uses a type in Application.Shared.Models.
- The types involved
NetWebApiTemplate.Application.Features.Products.Queries.GetAllProducts.GetAllProductsQueryHandler→NetWebApiTemplate.Application.Shared.Models.PaginatedList
- Direction
- Application.Features.Products.Queries.GetAllProducts uses Application.Shared.Models, so a change to Application.Shared.Models can break Application.Features.Products.Queries.GetAllProducts, while a change to Application.Features.Products.Queries.GetAllProducts can't break Application.Shared.Models.
- Position
- Below the diagonal: Application.Features.Products.Queries.GetAllProducts uses a module listed above it, which is the healthy direction.
31→13 Application.Features.Products.Queries.GetAllProducts uses Application.Shared.Interface✕
- Connections
- 1 pair of types, where a type in Application.Features.Products.Queries.GetAllProducts uses a type in Application.Shared.Interface.
- The types involved
NetWebApiTemplate.Application.Features.Products.Queries.GetAllProducts.GetAllProductsQueryHandler→NetWebApiTemplate.Application.Shared.Interface.INetWebApiTemplateDbContext
- Direction
- Application.Features.Products.Queries.GetAllProducts uses Application.Shared.Interface, so a change to Application.Shared.Interface can break Application.Features.Products.Queries.GetAllProducts, while a change to Application.Features.Products.Queries.GetAllProducts can't break Application.Shared.Interface.
- Position
- Below the diagonal: Application.Features.Products.Queries.GetAllProducts uses a module listed above it, which is the healthy direction.
32→13 Infrastructure.ApiClients.GitHub uses Application.Shared.Interface✕
- Connections
- 1 pair of types, where a type in Infrastructure.ApiClients.GitHub uses a type in Application.Shared.Interface.
- The types involved
NetWebApiTemplate.Infrastructure.ApiClients.GitHub.GitHubApiService→NetWebApiTemplate.Application.Shared.Interface.IGitHubService
- Direction
- Infrastructure.ApiClients.GitHub uses Application.Shared.Interface, so a change to Application.Shared.Interface can break Infrastructure.ApiClients.GitHub, while a change to Infrastructure.ApiClients.GitHub can't break Application.Shared.Interface.
- Position
- Below the diagonal: Infrastructure.ApiClients.GitHub uses a module listed above it, which is the healthy direction.
33→3 Infrastructure.Auth uses Application.Features.Authentication.Models✕
- Connections
- 4 pairs of types, where a type in Infrastructure.Auth uses a type in Application.Features.Authentication.Models.
- The types involved
NetWebApiTemplate.Infrastructure.Auth.AuthenticationService→NetWebApiTemplate.Application.Features.Authentication.Models.AppUserNetWebApiTemplate.Infrastructure.Auth.AuthenticationService→NetWebApiTemplate.Application.Features.Authentication.Models.ResultNetWebApiTemplate.Infrastructure.Auth.IdentityResultextensions→NetWebApiTemplate.Application.Features.Authentication.Models.ResultNetWebApiTemplate.Infrastructure.Auth.JwtTokenService→NetWebApiTemplate.Application.Features.Authentication.Models.TokenResult
- Direction
- Infrastructure.Auth uses Application.Features.Authentication.Models, so a change to Application.Features.Authentication.Models can break Infrastructure.Auth, while a change to Infrastructure.Auth can't break Application.Features.Authentication.Models.
- Position
- Below the diagonal: Infrastructure.Auth uses a module listed above it, which is the healthy direction.
33→9 Infrastructure.Auth uses Application.Features.Authentication.Interfaces✕
- Connections
- 2 pairs of types, where a type in Infrastructure.Auth uses a type in Application.Features.Authentication.Interfaces.
- The types involved
NetWebApiTemplate.Infrastructure.Auth.AuthenticationService→NetWebApiTemplate.Application.Features.Authentication.Interfaces.IAuthenticationServiceNetWebApiTemplate.Infrastructure.Auth.JwtTokenService→NetWebApiTemplate.Application.Features.Authentication.Interfaces.IJwtTokenService
- Direction
- Infrastructure.Auth uses Application.Features.Authentication.Interfaces, so a change to Application.Features.Authentication.Interfaces can break Infrastructure.Auth, while a change to Infrastructure.Auth can't break Application.Features.Authentication.Interfaces.
- Position
- Below the diagonal: Infrastructure.Auth uses a module listed above it, which is the healthy direction.
33→13 Infrastructure.Auth uses Application.Shared.Interface✕
- Connections
- 1 pair of types, where a type in Infrastructure.Auth uses a type in Application.Shared.Interface.
- The types involved
NetWebApiTemplate.Infrastructure.Auth.JwtTokenService→NetWebApiTemplate.Application.Shared.Interface.INetWebApiTemplateDbContext
- Direction
- Infrastructure.Auth uses Application.Shared.Interface, so a change to Application.Shared.Interface can break Infrastructure.Auth, while a change to Infrastructure.Auth can't break Application.Shared.Interface.
- Position
- Below the diagonal: Infrastructure.Auth uses a module listed above it, which is the healthy direction.
34→13 Infrastructure.BackgroundJobs uses Application.Shared.Interface✕
- Connections
- 1 pair of types, where a type in Infrastructure.BackgroundJobs uses a type in Application.Shared.Interface.
- The types involved
NetWebApiTemplate.Infrastructure.BackgroundJobs.ProcessOutboxMessagesJob→NetWebApiTemplate.Application.Shared.Interface.INetWebApiTemplateDbContext
- Direction
- Infrastructure.BackgroundJobs uses Application.Shared.Interface, so a change to Application.Shared.Interface can break Infrastructure.BackgroundJobs, while a change to Infrastructure.BackgroundJobs can't break Application.Shared.Interface.
- Position
- Below the diagonal: Infrastructure.BackgroundJobs uses a module listed above it, which is the healthy direction.
35→13 Infrastructure.Cache.InMemory uses Application.Shared.Interface✕
- Connections
- 1 pair of types, where a type in Infrastructure.Cache.InMemory uses a type in Application.Shared.Interface.
- The types involved
NetWebApiTemplate.Infrastructure.Cache.InMemory.InMemoryCacheProvider→NetWebApiTemplate.Application.Shared.Interface.ICacheProvider
- Direction
- Infrastructure.Cache.InMemory uses Application.Shared.Interface, so a change to Application.Shared.Interface can break Infrastructure.Cache.InMemory, while a change to Infrastructure.Cache.InMemory can't break Application.Shared.Interface.
- Position
- Below the diagonal: Infrastructure.Cache.InMemory uses a module listed above it, which is the healthy direction.
36→13 Infrastructure.DataProtection uses Application.Shared.Interface✕
- Connections
- 1 pair of types, where a type in Infrastructure.DataProtection uses a type in Application.Shared.Interface.
- The types involved
NetWebApiTemplate.Infrastructure.DataProtection.EncryptionManager→NetWebApiTemplate.Application.Shared.Interface.IEncryptionManager
- Direction
- Infrastructure.DataProtection uses Application.Shared.Interface, so a change to Application.Shared.Interface can break Infrastructure.DataProtection, while a change to Infrastructure.DataProtection can't break Application.Shared.Interface.
- Position
- Below the diagonal: Infrastructure.DataProtection uses a module listed above it, which is the healthy direction.
37→4 Infrastructure.Email uses Application.Features.EmailNotification✕
- Connections
- 2 pairs of types, where a type in Infrastructure.Email uses a type in Application.Features.EmailNotification.
- The types involved
NetWebApiTemplate.Infrastructure.Email.EmailSenderService→NetWebApiTemplate.Application.Features.EmailNotification.EmailMessageNetWebApiTemplate.Infrastructure.Email.EmailSenderService→NetWebApiTemplate.Application.Features.EmailNotification.EmailTemplates
- Direction
- Infrastructure.Email uses Application.Features.EmailNotification, so a change to Application.Features.EmailNotification can break Infrastructure.Email, while a change to Infrastructure.Email can't break Application.Features.EmailNotification.
- Position
- Below the diagonal: Infrastructure.Email uses a module listed above it, which is the healthy direction.
37→13 Infrastructure.Email uses Application.Shared.Interface✕
- Connections
- 1 pair of types, where a type in Infrastructure.Email uses a type in Application.Shared.Interface.
- The types involved
NetWebApiTemplate.Infrastructure.Email.EmailSenderService→NetWebApiTemplate.Application.Shared.Interface.IEmailSender
- Direction
- Infrastructure.Email uses Application.Shared.Interface, so a change to Application.Shared.Interface can break Infrastructure.Email, while a change to Infrastructure.Email can't break Application.Shared.Interface.
- Position
- Below the diagonal: Infrastructure.Email uses a module listed above it, which is the healthy direction.
38→7 Infrastructure.Outboxes uses Domain.Shared✕
- Connections
- 1 pair of types, where a type in Infrastructure.Outboxes uses a type in Domain.Shared.
- The types involved
NetWebApiTemplate.Infrastructure.Outboxes.OutboxService→NetWebApiTemplate.Domain.Shared.IDomainEvent
- Direction
- Infrastructure.Outboxes uses Domain.Shared, so a change to Domain.Shared can break Infrastructure.Outboxes, while a change to Infrastructure.Outboxes can't break Domain.Shared.
- Position
- Below the diagonal: Infrastructure.Outboxes uses a module listed above it, which is the healthy direction.
38→13 Infrastructure.Outboxes uses Application.Shared.Interface✕
- Connections
- 2 pairs of types, where a type in Infrastructure.Outboxes uses a type in Application.Shared.Interface.
- The types involved
NetWebApiTemplate.Infrastructure.Outboxes.OutboxService→NetWebApiTemplate.Application.Shared.Interface.INetWebApiTemplateDbContextNetWebApiTemplate.Infrastructure.Outboxes.OutboxService→NetWebApiTemplate.Application.Shared.Interface.IOutboxService
- Direction
- Infrastructure.Outboxes uses Application.Shared.Interface, so a change to Application.Shared.Interface can break Infrastructure.Outboxes, while a change to Infrastructure.Outboxes can't break Application.Shared.Interface.
- Position
- Below the diagonal: Infrastructure.Outboxes uses a module listed above it, which is the healthy direction.
39→6 Persistence uses Domain.Entities✕
- Connections
- 5 pairs of types, where a type in Persistence uses a type in Domain.Entities.
- The types involved
NetWebApiTemplate.Persistence.NetWebApiTemplateDbContext→NetWebApiTemplate.Domain.Entities.FaqNetWebApiTemplate.Persistence.NetWebApiTemplateDbContext→NetWebApiTemplate.Domain.Entities.OutboxMessageNetWebApiTemplate.Persistence.NetWebApiTemplateDbContext→NetWebApiTemplate.Domain.Entities.ProductNetWebApiTemplate.Persistence.NetWebApiTemplateDbContext→NetWebApiTemplate.Domain.Entities.ProductCatergoryNetWebApiTemplate.Persistence.NetWebApiTemplateDbContext→NetWebApiTemplate.Domain.Entities.RefreshToken
- Direction
- Persistence uses Domain.Entities, so a change to Domain.Entities can break Persistence, while a change to Persistence can't break Domain.Entities.
- Position
- Below the diagonal: Persistence uses a module listed above it, which is the healthy direction.
39→13 Persistence uses Application.Shared.Interface✕
- Connections
- 3 pairs of types, where a type in Persistence uses a type in Application.Shared.Interface.
- The types involved
NetWebApiTemplate.Persistence.NetWebApiTemplateDbContext→NetWebApiTemplate.Application.Shared.Interface.ICurrentUserServiceNetWebApiTemplate.Persistence.NetWebApiTemplateDbContext→NetWebApiTemplate.Application.Shared.Interface.INetWebApiTemplateDbContextNetWebApiTemplate.Persistence.SqlConnectionFactory→NetWebApiTemplate.Application.Shared.Interface.ISqlConnectionFactory
- Direction
- Persistence uses Application.Shared.Interface, so a change to Application.Shared.Interface can break Persistence, while a change to Persistence can't break Application.Shared.Interface.
- Position
- Below the diagonal: Persistence uses a module listed above it, which is the healthy direction.
40→6 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
NetWebApiTemplate.Persistence.Repositories.FaqRepository→NetWebApiTemplate.Domain.Entities.FaqNetWebApiTemplate.Persistence.Repositories.ProductRepository→NetWebApiTemplate.Domain.Entities.Product
- 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.
40→10 Persistence.Repositories uses Application.Features.Faqs.Interfaces✕
- Connections
- 1 pair of types, where a type in Persistence.Repositories uses a type in Application.Features.Faqs.Interfaces.
- The types involved
NetWebApiTemplate.Persistence.Repositories.FaqRepository→NetWebApiTemplate.Application.Features.Faqs.Interfaces.IFaqRepository
- Direction
- Persistence.Repositories uses Application.Features.Faqs.Interfaces, so a change to Application.Features.Faqs.Interfaces can break Persistence.Repositories, while a change to Persistence.Repositories can't break Application.Features.Faqs.Interfaces.
- Position
- Below the diagonal: Persistence.Repositories uses a module listed above it, which is the healthy direction.
40→11 Persistence.Repositories uses Application.Features.Products.Interfaces✕
- Connections
- 1 pair of types, where a type in Persistence.Repositories uses a type in Application.Features.Products.Interfaces.
- The types involved
NetWebApiTemplate.Persistence.Repositories.ProductRepository→NetWebApiTemplate.Application.Features.Products.Interfaces.IProductRepository
- Direction
- Persistence.Repositories uses Application.Features.Products.Interfaces, so a change to Application.Features.Products.Interfaces can break Persistence.Repositories, while a change to Persistence.Repositories can't break Application.Features.Products.Interfaces.
- Position
- Below the diagonal: Persistence.Repositories uses a module listed above it, which is the healthy direction.
40→13 Persistence.Repositories uses Application.Shared.Interface✕
- Connections
- 2 pairs of types, where a type in Persistence.Repositories uses a type in Application.Shared.Interface.
- The types involved
NetWebApiTemplate.Persistence.Repositories.FaqRepository→NetWebApiTemplate.Application.Shared.Interface.ISqlConnectionFactoryNetWebApiTemplate.Persistence.Repositories.ProductRepository→NetWebApiTemplate.Application.Shared.Interface.ISqlConnectionFactory
- Direction
- Persistence.Repositories uses Application.Shared.Interface, so a change to Application.Shared.Interface can break Persistence.Repositories, while a change to Persistence.Repositories can't break Application.Shared.Interface.
- Position
- Below the diagonal: Persistence.Repositories uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
At a glance — Domain Modelling
At a glance — Event-Driven
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A05:2025 — Injection | 34 | High / Critical |
| A07:2025 — Authentication Failures | 6 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 5 | High / Critical |
| A02:2025 — Security Misconfiguration | 5 | High / Critical |
| A01:2025 — Broken Access Control | 2 | Medium |
Roadmap
Top priorities: Resolve the 1 No tests found finding(s) in Test Distribution; Resolve the 3 Leaked secret finding(s) in Secret Scanning — start with REDACTED (2), REDACTED; Resolve the 4 Deprecated finding(s) in Dependency Hygiene — start with REDACTED (2), REDACTED (2).
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 1 No tests found finding(s) in Test Distribution. | +9.4 pts | Low | Test Distribution |
| Resolve the 3 Leaked secret finding(s) in Secret Scanning — start with REDACTED (2), REDACTED. | +9.1 pts | Low | Secret Scanning |
| Resolve the 4 Deprecated finding(s) in Dependency Hygiene — start with REDACTED (2), REDACTED (2). | +7.3 pts | Low | Dependency Hygiene |
| Resolve the 8 Orphaned file finding(s) in Knowledge Freshness — start with JwtTokenService.cs, Program.cs, REDACTED. | +3.8 pts | Low | Knowledge Freshness |
| Resolve the 3 redundant comment finding(s) in Comment Value — start with Program.cs, RegisterUserCommand.cs, DependencyInjection.cs. | +3.1 pts | Low | Comment Value |
| Resolve the 1 Outdated finding(s) in Dependency Hygiene — start with REDACTED. | +2.4 pts | Low | Dependency Hygiene |
| Resolve the 1 Orphaned files with no living knowledge finding(s) in Knowledge Freshness. | +1.4 pts | Low | Knowledge Freshness |
| Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them. | +2.7 pts | Medium | Architecture documentation |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 0.7 | Slop | Dependency Vulnerabilities: High CVE: REDACTED |
| REDACTED | 0.9 | Slop | Secret Scanning: Leaked secret: REDACTED |
| REDACTED | 1.3 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 3.4 | Mixed | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 3.7 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.6 | Mixed | Dependency Vulnerabilities: Medium CVE: REDACTED |
| REDACTED | 5.1 | Mixed | Secret Scanning: Leaked secret: REDACTED |
| src/content/src/NetWebApiTemplate.Api/Filters/ApiExceptionFilterAttribute.cs | 5.8 | Mixed | Explicit Debt: WriteOnlyPrivateField |
| REDACTED | 5.8 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| REDACTED | 6.1 | Near-clean | Static Analysis (SAST): Medium: REDACTED |
| REDACTED | 6.3 | Near-clean | Static Analysis (SAST): Medium: REDACTED |
| src/content/src/NetWebApiTemplate.Application/Shared/Interface/ICacheProvider.cs | 6.6 | Near-clean | Explicit Debt: Dead code: GetFromCache |
| REDACTED | 7.2 | Near-clean | Secrets (history): High secret: REDACTED |
| REDACTED | 7.2 | Near-clean | Static Analysis (SAST): High: REDACTED |
| REDACTED | 7.2 | Near-clean | Static Analysis (SAST): High: REDACTED |
| REDACTED | 7.2 | Near-clean | Dependency Vulnerabilities: High CVE: REDACTED |
| src/content/src/NetWebApiTemplate.Application/Features/Faqs/Interfaces/IFaqRepository.cs | 7.3 | Near-clean | Explicit Debt: Dead code: GetFaqByIdAsync |
| src/content/src/NetWebApiTemplate.Application/Shared/Interface/IEncryptionManager.cs | 7.3 | Near-clean | Explicit Debt: Dead code: Encrypt |
| src/content/src/NetWebApiTemplate.Application/Features/Authentication/Commands/RegisterUser/UserRegisteredEvent.cs | 7.6 | Near-clean | Explicit Debt: WriteOnlyPrivateField |
| REDACTED | 7.9 | Near-clean | Static Analysis (SAST): Medium: REDACTED |
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 87 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.9, the weighted average across measured dimensions.
What we checked — 87 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, 161 of 198 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Canine Code Analyzer duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy · checkov | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 · 3.2.533 | ✓ deterministic |
Run transparency — what happened this run
- D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Single-maintainer repository — bus factor is not applicable (2 contributor(s) across 300 commit(s) sampled, automation and bot accounts excluded). One of them holds 99% of the history; the other 1 hold 1% each on average, below the 5% at which there is somebody to hand the work to. That is a single maintainer with drive-by contributors, not a team whose knowledge has concentrated — so the bus factor is not applicable and there is nothing here for the owner to act on.
- D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
- D32 Data Compliance (PII/GDPR) — 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. `src/content/.frontier/template/query/query.cs`, `REDACTED`, `REDACTED` produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
- DM8 Value-object opportunities — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check finds primitive parameters that travel together through several signatures of the domain (a missing value object). Its deterministic rule has not yet shown 95 % precision on adjudicated rows, so the clumps it finds are counted here and not published as findings, and the card carries no score. That is a limit of the analyzer, not a finding about your code.
- PF3 Async & latency hygiene — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 45 further occurrence(s) are not listed individually; the score already reflects all 85.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
- D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
- 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.
- D24 Comment Value: Comment value is measured as redundancy only: a comment that repeats its code's words is found, but a paraphrase in other words, a vague comment, or one the code contradicts is not, and whether a comment is valuable is not claimed. Comments in other scripts or languages, and outside C#, are not judged.
- D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
- D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
- D32 Data Compliance (PII/GDPR): PII/GDPR signals are heuristic pattern matches in code — they flag likely handling concerns, not legal compliance, and cannot trace where data actually flows at runtime.
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a REDACTED (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- AX9 CQS / query purity: Handlers are found by interface/name convention — a query handler using neither is not seen. Mutation is a resolved write/publish invocation (SaveChanges/repository/bus), so a write hidden behind a hand-rolled wrapper, reflection, or a string-keyed service locator resolves to a non-persistence type and isn't flagged; it detects that a query writes state, not whether the write is a legitimate read-side cache update. Clean means "no resolved write/publish in a query body", not a proof of CQS purity.
- DM6 Domain ↔ infrastructure boundary: Infrastructure reached through a hand-rolled wrapper, a domain-named facade, reflection, or a string-keyed service locator resolves to a non-infra type and isn't seen; the body scan is symbol resolution over syntax, not full dataflow. A clean result means "no resolved infra reference in a domain body", not a proof of purity.
- ED5 Idempotency: Idempotency is read from the handler body and one hop below: a mutation is flagged only on structural double-apply evidence (a fresh-identity insert, an accumulation, a growing list, an unkeyed POST/send/charge), so a duplicate effect through a home-grown gateway two hops down, or an insert keyed on the message with no unique constraint, is not flagged but counted as not classified; a guard enforced by a database constraint or a broker's exactly-once delivery is invisible either way. It flags the at-least-once double-apply SHAPE, not a runtime proof of a duplicate effect.
- M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
- P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
- P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
Dimensions
D1 · Cyclomatic Complexity
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
0 duplicated block group(s) detected.
D5 · Coupling
5 projects, 0 dependency cycle(s), 0 unstable depended-on project(s).
D6 · Cohesion (LCOM4)
0 of 7 classes have LCOM4 above 3.
D9 · Test Distribution
No test suite found.
What to do
- Resolve the 1 No tests found finding(s) in Test Distribution. — One of this dimension's main actionable groups (1 recommendation-level).
D12 · Dependency Hygiene
23 outdated, 0 vulnerable, 3 deprecated packages.
What to do
- Resolve the 4 Deprecated finding(s) in Dependency Hygiene — start with REDACTED (2), REDACTED (2). — One of this dimension's main actionable groups (4 warning-level).
- Resolve the 1 Outdated finding(s) in Dependency Hygiene — start with REDACTED. — One of this dimension's main actionable groups (1 recommendation-level).
- Enforce Dependency Hygiene in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D13 · Secret Scanning
2 secret(s) detected.
What to do
- Resolve the 3 Leaked secret finding(s) in Secret Scanning — start with REDACTED (2), REDACTED. — One of this dimension's main actionable groups (3 issue-level).
- Enforce Secret Scanning in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D14 · License Compliance
0 of 261 packages use a banned license. ★ DEPTH: this repository's MSBuild projects declare 35 direct `PackageReference`(s), and 215 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
5 deducted debt markers + 14 dead symbols across 3256 LoC in the .NET projects (1.3/KLoC) → score 7.5.
What to do
- Resolve the 2 WriteOnlyPrivateField finding(s) in Explicit Debt — start with ApiExceptionFilterAttribute.cs, UserRegisteredEvent.cs. — One of this dimension's main actionable groups (2 issue-level).
- Resolve the 1 NoWarnInCsproj finding(s) in Explicit Debt — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 14 Dead code finding(s) in Explicit Debt — start with ICacheProvider.cs (4), IFaqRepository.cs (2), IEncryptionManager.cs (2). — One of this dimension's main actionable groups (14 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
5 projects, 115 source files, 3256 hand-written lines of code (3256 production / 0 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
1 of 1 documentation facets pass in full. 4 document(s) read across 1 unit(s).
D24 · Comment Value
3 of 60 judged comments only repeat the code they sit on (5.0 %). 1 comment(s) in another language or script were not judged.
What to do
- Resolve the 3 redundant comment finding(s) in Comment Value — start with Program.cs, RegisterUserCommand.cs, DependencyInjection.cs. — One of this dimension's main actionable groups (3 recommendation-level).
D26 · Project Cohesion
0 of 5 projects flagged as possibly oversized/incoherent.
D27 · Navigability
95 % of calls cross a namespace and 13 % go through an interface, but 100 % of collaborators are co-located — so a call's collaborators sit together and tracing stays easy. Baseline: small — navigation cost is tolerated.
D28 · Secrets (history)
2 finding(s): 0 critical, 2 high, 0 medium, 0 low. Remediation for historically-committed secrets is credential rotation — they remain in history regardless of later deletion.
What to do
- Resolve the 2 High secret finding(s) in Secrets (history) — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
- Resolve the 1 Rotate the exposed credentials finding(s) in Secrets (history). — One of this dimension's main actionable groups (1 recommendation-level).
D29 · Static Analysis (SAST)
34 finding(s): 0 critical, 13 high, 21 medium, 0 low. semgrep hit a parse error in 4 file(s) — `REDACTED`, `src/content/.frontier/template/query/query.cs` (line 6, line 10, line 19), `REDACTED` (line 12, line 16, lines 17–18, …), `REDACTED` (line 9, line 11, line 13, …) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them. In 2 of those file(s) — `REDACTED`, `REDACTED` — the break is a C# primary constructor, which semgrep's grammar cannot parse and which hides the type from every rule scoped to it; those files were re-scanned from a shadow copy with the constructor's parameter list blanked (line and column preserving), which restores the type to the rules, and 0 additional row(s) came from that pass. Only the header's own parameter list is unread in them. Separately, one or more rules could not re-parse an embedded snippet in 1 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.
What to do
- Resolve the 7 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (5), REDACTED (2). — One of this dimension's main actionable groups (7 issue-level).
- Resolve the 3 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (3). — One of this dimension's main actionable groups (3 issue-level).
- Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 issue-level).
D30 · Dependency Vulnerabilities
5 finding(s): 0 critical, 3 high, 2 medium, 0 low.
What to do
- Resolve the 3 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (2), REDACTED. — One of this dimension's main actionable groups (3 issue-level).
- Resolve the 2 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (2). — One of this dimension's main actionable groups (2 warning-level).
D31 · IaC & Container Security
5 finding(s): 0 critical, 1 high, 3 medium, 1 low.
What to do
- Resolve the 1 High IaC finding(s) in IaC & Container Security — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 3 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (2), REDACTED. — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 1 Low IaC finding(s) in IaC & Container Security — start with REDACTED. — One of this dimension's main actionable groups (1 recommendation-level).
D32 · Data Compliance (PII/GDPR)
2 finding(s): 0 critical, 0 high, 2 medium, 0 low. semgrep could not parse 3 file(s) — `src/content/.frontier/template/query/query.cs`, `REDACTED`, `REDACTED` — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real.
What to do
- Resolve the 2 REDACTED finding(s) in Data Compliance (PII/GDPR) — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 warning-level).
D34 · Knowledge Freshness
8 of 8 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is src/content/src/NetWebApiTemplate.Infrastructure/Auth/JwtTokenService.cs. Counted over 8 of the 124 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 8 Orphaned file finding(s) in Knowledge Freshness — start with JwtTokenService.cs, Program.cs, REDACTED. — One of this dimension's main actionable groups (8 recommendation-level).
- Resolve the 1 Orphaned files with no living knowledge finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
D35 · Change Coupling
No strong hidden change-coupling between production files.
D39 · IL Efficiency
0 of 222 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 5 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).
AX2 · Stateful singletons
AX3 · Project dependency cycles
AX4 · Dependency direction
AX5 · Architecture & structure
AX6 · Interface segregation
AX7 · Slice cohesion
- `UserRegisteredEventHandler` (slice 'Authentication') depends on `EmailTemplates` from slice 'EmailNotification'. — src/content/src/NetWebApiTemplate.Application/Features/Authentication/Commands/RegisterUser/UserRegisteredEvent.cs:17
- `UserRegisteredEventHandler` (slice 'Authentication') depends on `EmailMessage` from slice 'EmailNotification'. — src/content/src/NetWebApiTemplate.Application/Features/Authentication/Commands/RegisterUser/UserRegisteredEvent.cs:28
What to do
- Keep slices independent: share cross-slice needs via an explicit contract/shared-kernel, not direct references between slices.
AX9 · CQS / query purity
DM10 · One transaction, one aggregate
DM12 · Ambient inputs in the domain
- `RefreshToken` reads `DateTime.UtcNow` inside `IsExpired`. The rule this feeds is not a function of its inputs: it cannot be tested at the instant that matters without moving the machine clock, and two reads inside one operation can observe different times. Pass the instant in as a parameter, or inject `TimeProvider`. — src/content/src/NetWebApiTemplate.Domain/Entities/RefreshToken.cs:12
What to do
- Pass the instant into the domain method that needs it, or inject `TimeProvider` (BCL, .NET 8+) and read it there — then a test can choose the moment a rule is evaluated at.
DM6 · Domain ↔ infrastructure boundary
DM9 · Scattered domain decisions
ED1 · Handler temporal coupling
ED2 · Event/command shape
ED3 · Event naming
ED4 · Outbox / dual-write
ED5 · Idempotency
- `Commands.CreateProductCommandHandler.Handle` mutates persistent state (a database save) and inserts a new `Product` with no identity assigned (the store or its constructor generates a new one) (line 33), so a re-run inserts another one. A retry or at-least-once redelivery runs it again — add an exists/dedup check, an upsert, an idempotency-key/inbox, or a versioned write. — src/content/src/NetWebApiTemplate.Application/Features/Products/Commands/CreateProduct/CreateProductCommand.cs:23
What to do
- Make retry-prone mutations idempotent — guard each write with an exists/dedup check, an upsert, an idempotency-key/inbox, or a versioned write, so a re-run doesn't double-apply.
GD1 · Unfinished & placeholder code
IC1 · Incompleteness & stubs
- `Handle` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — src/content/src/NetWebApiTemplate.Application/Features/Authentication/Commands/RegisterUser/UserRegisteredEvent.cs:25
- A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers). (×4) — src/content/src/NetWebApiTemplate.Api/Filters/ApiExceptionFilterAttribute.cs:37, src/content/src/NetWebApiTemplate.Application/DependencyInjection.cs:26, src/content/src/NetWebApiTemplate.Application/Features/Authentication/Commands/RegisterUser/UserRegisteredEvent.cs:40, …
What to do
- Clear the softer debt: remove commented-out code and dead branches, re-enable or delete skipped tests, and replace blanket warning suppressions with targeted ones.
M1 · Documentation (README)
What to do
- Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
- Add a README to the 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
What to do
- Start a test surface where your build system looks for one (tests/, test/, spec/, or your ecosystem's test source set) — the separation follows from putting the first tests in the right place.
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:37
- docs/Getting-Started.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. — docs/Getting-Started.md:11
What to do
- Reconcile the README with reality: README.md names .NET 7, but the projects target .NET 8; docs/Getting-Started.md names .NET 7, but the projects target .NET 8.
P1 · CI/CD gates
P10 · Library API & versioning
- 16/17 types (94%) are public. For a library, every public type is a stability contract — make internal-by-default and expose only the intended API.
What to do
- Make types internal by default; expose only the deliberate public API so internals can change without breaking consumers.
P2 · Observability
- `src/content/src/NetWebApiTemplate.Application/Features/Authentication/Commands/RegisterUser/UserRegisteredEvent.cs` reports through `Console.Write…` at line 39 although other files in its project log through a logger. Console lines carry no level, category or structured properties and never reach the log pipeline or its exporters. — src/content/src/NetWebApiTemplate.Application/Features/Authentication/Commands/RegisterUser/UserRegisteredEvent.cs:39
What to do
- Replace `Console.Write…` in service code with the project's injected `ILogger<T>` (message templates with named properties), so delivery outcomes and failures reach the log pipeline with a level and a category.
- Add OpenTelemetry tracing/metrics (ActivitySource / AddMetrics) so requests are traceable across the system, not just health-probable.
P3 · Security & performance tooling
- `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:38
What to do
- Enable Dependabot/Renovate or a dependency-review gate.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
- Deployment is orchestrated by compose, but no service declares a `healthcheck:` and nothing pins a previous image to fall back to — the runtime can tell that the container is up, not that it is serving, so a bad release is harder to detect and reverse.
What to do
- Add a `healthcheck:` to the served compose service — probing the endpoint it already answers on where it has one — with `depends_on: condition: service_healthy` on whatever waits for it, and keep the deployed image tag immutable and recorded so rolling back is re-pointing at the previous tag rather than rebuilding.
P6 · Release Hygiene
- No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
What to do
- Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.
P7 · Outbound HTTP resilience
- `services.AddHttpClient(name: "GitHub", client => { client.BaseAddress = new U...` registers an outbound HTTP client, and what is applied to it does not bound it. Its resilience pipeline only retries: no timeout ends a hung attempt and no circuit breaker stops calling a failing dependency, so the retries multiply the calls instead of bounding them. A slow or failing dependency will hold this service's request, thread or connection — and cascade — until the call gives up on its own (100 s for HttpClient's default). — src/content/src/NetWebApiTemplate.Infrastructure/DependencyInjection.cs:71
What to do
- Add `AddStandardResilienceHandler()` (or a Polly policy and an explicit timeout) to each client registration flagged here, so a flaky dependency can't take the app down.
P8 · Schema migrations
PF1 · Benchmark discipline
- No benchmark suite was found by the two searches this check runs. FIRST, a BenchmarkDotNet package reference in any project file — every project the workspace loaded, plus a walk of project files on disk that never loaded, because a benchmark suite is exactly the project a partial load drops. SECOND, a script harness: a file whose name contains `benchmark` and ends `.py`, `.sh`, `.ps1`, `.bash`, `.rb`, `.js` or `.mjs`, credited ONLY when this repository's CI text also mentions benchmarks — a harness no pipeline runs is read as a fixture, deliberately. Neither search can see a benchmark suite in another ecosystem's idiom (a Go `testing.B` file, a JMH or criterion project, a pytest-benchmark run), so this is 'no benchmark found by those two searches', not a verdict that the repository has none. Where code is performance-sensitive, a benchmark guards against silent regressions — but it's a bonus here, not a deduction.
What to do
- Add a benchmarking harness for the hot paths and run it in CI to catch regressions (for .NET, a BenchmarkDotNet project with [MemoryDiagnoser] to track allocations).
PF3 · Async & latency hygiene
- Only 0/84 awaits in library code use ConfigureAwait(false). A library that captures the caller's context can stall or deadlock its host — the classic way a dependency drags an app down.
- `await _mediator.Send(command)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. (×10) — REDACTED:45, REDACTED:67, REDACTED:91, …
- `await _mediator.Send(query)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. (×5) — REDACTED:106, REDACTED:170, REDACTED:212, …
- `await next.Invoke()` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/content/src/NetWebApiTemplate.Api/Program.cs:218
- `await httpContext.Response.WriteAsync(text: JsonConvert.SerializeObject(response, F...` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/content/src/NetWebApiTemplate.Api/Services/HealthCheckResponseWriter.cs:26
- `await _authenticationService.AddClaimToUser(request.Email, request.ClaimName, reque...` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/content/src/NetWebApiTemplate.Application/Features/Authentication/Commands/AddClaimToUser/AddClaimToUserCommand.cs:24
- `await _authenticationService.AddUserToRoleAsync(request.Email, request.RoleName)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/content/src/NetWebApiTemplate.Application/Features/Authentication/Commands/AddUserToRole/AddUserToRoleCommand.cs:23
- `await _authenticationService.CreateRoleAsync(request.RoleName)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/content/src/NetWebApiTemplate.Application/Features/Authentication/Commands/CreateRole/CreateRoleCommand.cs:22
- `await _authenticationService.PasswordSignInAsync(request.Email, request.Password, f...` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/content/src/NetWebApiTemplate.Application/Features/Authentication/Commands/Login/LoginCommand.cs:26
- `await _jwtTokenService.GenerateClaimsTokenAsync(request.Email, cancellationToken)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/content/src/NetWebApiTemplate.Application/Features/Authentication/Commands/Login/LoginCommand.cs:35
- `await _jwtTokenService.RefreshTokenAsync(request.AccessToken, request.RefreshToken,...` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/content/src/NetWebApiTemplate.Application/Features/Authentication/Commands/RefreshToken/RefreshTokenCommand.cs:24
- `await _authenticationService.RegisterUserAsync(user, request.Password)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/content/src/NetWebApiTemplate.Application/Features/Authentication/Commands/RegisterUser/RegisterUserCommand.cs:38
- `await _outboxService.StoreDomainEvent(new UserRegisteredEvent { FirstName = request...` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/content/src/NetWebApiTemplate.Application/Features/Authentication/Commands/RegisterUser/RegisterUserCommand.cs:46
- `await _authenticationService.RemoveUserFromRoleAsync(request.Email, request.RoleName)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/content/src/NetWebApiTemplate.Application/Features/Authentication/Commands/RemoveUserFromRole/RemoveUserFromRoleCommand.cs:23
- `await _authenticationService.GetRolesAsync()` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/content/src/NetWebApiTemplate.Application/Features/Authentication/Queries/GetAllRoles/GetAllRolesQuery.cs:21
- `await _authenticationService.GetUserClaimsAsync(request.Email)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/content/src/NetWebApiTemplate.Application/Features/Authentication/Queries/GetUserClaims/GetUserClaimsQuery.cs:22
- `await _authenticationService.GetUserRolesAsync(request.Email)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/content/src/NetWebApiTemplate.Application/Features/Authentication/Queries/GetUserRoles/GetUserRolesQuery.cs:22
- `await faqQuery .AsNoTracking() .Select(f => new GetFaqDto { Question = f.Question, ...` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/content/src/NetWebApiTemplate.Application/Features/Faqs/Queries/GetAllFaqs/GetAllFaqsQueryHandler.cs:30
- `await _dbContext.SaveChangesAsync(cancellationToken)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. (×2) — src/content/src/NetWebApiTemplate.Application/Features/Products/Commands/CreateProduct/CreateProductCommand.cs:35, src/content/src/NetWebApiTemplate.Application/Features/Products/Commands/DeleteProduct/DeleteProductCommand.cs:31
- `await _productRepository.GetById(request.Id)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/content/src/NetWebApiTemplate.Application/Features/Products/Commands/UpdateProduct/UpdateProductCommand.cs:27
- `await _productRepository.Update(entity)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/content/src/NetWebApiTemplate.Application/Features/Products/Commands/UpdateProduct/UpdateProductCommand.cs:36
- `await _dbContext.Products .AsNoTracking() .Select(p => new ProductsDto { Id = p.Pro...` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/content/src/NetWebApiTemplate.Application/Features/Products/Queries/GetAllProducts/GetAllProductsQuery.cs:26
- `await next(message, cancellationToken)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. (×3) — src/content/src/NetWebApiTemplate.Application/Shared/Behaviours/LoggingBehaviour.cs:21, REDACTED:23, REDACTED:22
- `await Task.WhenAll(_validators.Select(v => v.ValidateAsync(context, cancellationTok...` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/content/src/NetWebApiTemplate.Application/Shared/Behaviours/ValidationBehaviour.cs:22
What to do
- In library code, append .ConfigureAwait(false) to every await (or set <ConfigureAwait>false</ConfigureAwait> / use the analyzer CA2007) so the library never captures the host's context.
S1 · Web-Security Posture
- 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.)
- No UseHttpsRedirection/UseHsts and no reverse-proxy signal — transport security is unverified at the app layer. (−2.0 on this card.)
- No ModelState/[ApiController]/FluentValidation signal — inbound payloads reach handlers unvalidated. (−2.0 on this card.)
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.
- Validate inbound models (ModelState/[ApiController]/FluentValidation) to reduce injection and bad-data risk.
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 24/44 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. (×19) — REDACTED:37, REDACTED:59, REDACTED:81, …
- No CancellationToken parameter, and the token `httpContext.RequestAborted` carries reaches none of the calls here that take one — this work can't be stopped early once started. Pass `httpContext.RequestAborted` on, or take a CancellationToken. — src/content/src/NetWebApiTemplate.Api/Services/HealthCheckResponseWriter.cs:10
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
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 85% | Exemplary | Solid. |
| Architecture | 71% | Strong | Solid. |
| Maturity | 48% | Adequate — gated by D34, M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 36% | Adequate — gated by D9, D13, P7 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 54% | Adequate — gated by D29 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Domain Modelling | 96% | Exemplary | Solid. |
| Event-Driven | 100% | Exemplary | Strongest area. |
| Performance | 60% | Strong | Solid. |
Unscored — 2 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.
- X7 Silent fallback defaults — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 1 control(s) we could not find positive evidence for
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 46 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.
- AX8 Test isolation — no test/production split to check
- AXB2 Runtime readiness — 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.
- C1 Data Protection — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
- C2 Access Controls — This is a dotnet-new template — authorization is deferred to the application you build from it. Add [Authorize]/policies (or imperative guards) when you wire up real users; until then there are no real endpoints to protect.
- C3 Audit Trail — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
- C4 Data Retention — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
- C5 Data-Subject Rights — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
- D10 Test Quality — No tests were found in the analyzed repository to assess for quality.
- D11 Test Reliability — No test suite was found to re-run, so reliability couldn't be assessed. Two searches produced that zero and both came back empty: the classifier that reads the loaded workspace recognised no suite it could run, and a walk of the source on disk — which covers the JS/TS `*.test.*` and `*.spec.*` conventions and probes for a Pester suite — found no test source in any other ecosystem either. Neither search reaches a suite that is missing from the loaded workspace and carries no name either walk recognises, so this is 'no suite found by those two searches', not a verdict that the repository has none.
- D16 Bus Factor — single-maintainer repository — bus factor is not applicable
- D20 ADR Quality — N/A — this repo declares itself a template / kata / sample / demo; a formal ADR log is deferred to a real application built from it.
- D21 Naming Consistency — D21 withholds its case and prefix conventions rows: 1 candidate(s) found and not reported.
- D22 Internal API Consistency — N/A — too few peer members to establish a convention across 16 exposed C# types.
- D23 Boundary Type-Coupling — small single-context codebase (3,256 production LoC in the .NET projects) — bounded contexts are not needed at this size No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D25 ADR Conformance — no ADRs to check
- D36 Supply-chain Provenance & Signing — This is a dotnet-new template — it produces no released artifact to attest. Supply-chain provenance, signing and SBOM are deferred to the application you build from it (add SLSA provenance / cosign signing / an SBOM in your app's release pipeline).
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D7 Architectural Integrity — no checkable ADRs and no dependency cycles — architectural integrity not assessed
- D8 Code Coverage — This repo declares itself a template / kata / sample; tests are deferred to the application built from it, so coverage is not scored here.
- DM1 Aggregate boundaries — no aggregates detected — aggregate-boundary check not applicable
- DM11 Constructible invalid state — no entities detected — construction-time invariants not assessable
- DM2 Strongly-typed ids — no id-bearing domain types detected — strongly-typed-id adoption not assessable
- DM3 Integration-event coupling — no integration events detected — coupling check not applicable
- DM4 Rich vs anemic model — no data-bearing entities detected — rich-vs-anemic model not assessable
- DM5 Encapsulated state — no domain entities found — DM5 grades how entities protect their state, and this repository declares none
- DM7 Repository granularity — no repository abstraction detected (e.g. uses a document session)
- DM8 Value-object opportunities — not scored — the deterministic rule found 0 candidate clump(s); its rows are withheld until it has a measured precision of 95 % (a sample of fewer than 10 rows cannot show one)
- 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'.
- P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (Cobertura — `dotnet test --collect:"XPlat Code Coverage"` with a `coverlet.collector` PackageReference) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures, or wire coverage collection into CI, to enable this cross-layer check
- PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
- X10 Duplicated predicate — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
Critical — 25 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- WriteOnlyPrivateField src/content/src/NetWebApiTemplate.Api/Filters/ApiExceptionFilterAttribute.cs:11
- WriteOnlyPrivateField src/content/src/NetWebApiTemplate.Application/Features/Authentication/Commands/RegisterUser/UserRegisteredEvent.cs:18
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- NoWarnInCsproj REDACTED:12
- REDACTED
- REDACTED
Serious — 115 finding(s)
- Awaits without ConfigureAwait(false)
- Awaits without ConfigureAwait(false) REDACTED:45
- Awaits without ConfigureAwait(false) REDACTED:67
- Awaits without ConfigureAwait(false) REDACTED:91
- Awaits without ConfigureAwait(false) REDACTED:106
- Awaits without ConfigureAwait(false) REDACTED:127
- Awaits without ConfigureAwait(false) REDACTED:150
- Awaits without ConfigureAwait(false) REDACTED:170
- Awaits without ConfigureAwait(false) REDACTED:192
- Awaits without ConfigureAwait(false) REDACTED:212
- Awaits without ConfigureAwait(false) REDACTED:236
- Awaits without ConfigureAwait(false) REDACTED:36
- Awaits without ConfigureAwait(false) REDACTED:28
- Awaits without ConfigureAwait(false) REDACTED:45
- Awaits without ConfigureAwait(false) REDACTED:63
- Awaits without ConfigureAwait(false) REDACTED:80
- Awaits without ConfigureAwait(false) src/content/src/NetWebApiTemplate.Api/Program.cs:218
- Awaits without ConfigureAwait(false) src/content/src/NetWebApiTemplate.Api/Services/HealthCheckResponseWriter.cs:26
- Awaits without ConfigureAwait(false) src/content/src/NetWebApiTemplate.Application/Features/Authentication/Commands/AddClaimToUser/AddClaimToUserCommand.cs:24
- Awaits without ConfigureAwait(false) src/content/src/NetWebApiTemplate.Application/Features/Authentication/Commands/AddUserToRole/AddUserToRoleCommand.cs:23
- Awaits without ConfigureAwait(false) src/content/src/NetWebApiTemplate.Application/Features/Authentication/Commands/CreateRole/CreateRoleCommand.cs:22
- Awaits without ConfigureAwait(false) src/content/src/NetWebApiTemplate.Application/Features/Authentication/Commands/Login/LoginCommand.cs:26
- Awaits without ConfigureAwait(false) src/content/src/NetWebApiTemplate.Application/Features/Authentication/Commands/Login/LoginCommand.cs:35
- Awaits without ConfigureAwait(false) src/content/src/NetWebApiTemplate.Application/Features/Authentication/Commands/RefreshToken/RefreshTokenCommand.cs:24
- Awaits without ConfigureAwait(false) src/content/src/NetWebApiTemplate.Application/Features/Authentication/Commands/RegisterUser/RegisterUserCommand.cs:38
- Async method without CancellationToken: Login REDACTED:37
- Async method without CancellationToken: Refresh REDACTED:59
- Async method without CancellationToken: Register REDACTED:81
- Async method without CancellationToken: GetAllRoles REDACTED:103
- Async method without CancellationToken: CreateRole REDACTED:120
- Async method without CancellationToken: AddUserToRole REDACTED:142
- Async method without CancellationToken: GetUserRoles REDACTED:163
- Async method without CancellationToken: RemoveUserFromRole REDACTED:184
- Async method without CancellationToken: GetUserClaims REDACTED:205
- Async method without CancellationToken: AddClaimToUser REDACTED:227
- Async method without CancellationToken: GetAll REDACTED:28
- Async method without CancellationToken: GetAll REDACTED:25
- Async method without CancellationToken: Create REDACTED:37
- Async method without CancellationToken: Update REDACTED:54
- Async method without CancellationToken: Delete REDACTED:73
- Async method without CancellationToken: WriterHealthCheckResponse src/content/src/NetWebApiTemplate.Api/Services/HealthCheckResponseWriter.cs:10
- Async method without CancellationToken: LoadAccountAsync src/content/src/NetWebApiTemplate.Infrastructure/ApiClients/GitHub/GitHubApiService.cs:14
- Async method without CancellationToken: GetAllUsersAsync src/content/src/NetWebApiTemplate.Infrastructure/Auth/AuthenticationService.cs:83
- Async method without CancellationToken: GetRolesAsync src/content/src/NetWebApiTemplate.Infrastructure/Auth/AuthenticationService.cs:96
- Async method without CancellationToken: GetPrincipFromTokenAsync src/content/src/NetWebApiTemplate.Infrastructure/Auth/JwtTokenService.cs:79
- Dead code: SwaggerOptions src/content/src/NetWebApiTemplate.Api/Swagger/SwaggerOptions.cs:3
- Dead code: GetAllUsersAsync src/content/src/NetWebApiTemplate.Application/Features/Authentication/Interfaces/IAuthenticationService.cs:11
- Dead code: GetFaqByIdAsync src/content/src/NetWebApiTemplate.Application/Features/Faqs/Interfaces/IFaqRepository.cs:8
- Dead code: GetAll src/content/src/NetWebApiTemplate.Application/Features/Faqs/Interfaces/IFaqRepository.cs:9
- Dead code: GetFromCache src/content/src/NetWebApiTemplate.Application/Shared/Interface/ICacheProvider.cs:7
- Dead code: SetCache src/content/src/NetWebApiTemplate.Application/Shared/Interface/ICacheProvider.cs:8
- Dead code: SetCache src/content/src/NetWebApiTemplate.Application/Shared/Interface/ICacheProvider.cs:9
- Dead code: ClearCache src/content/src/NetWebApiTemplate.Application/Shared/Interface/ICacheProvider.cs:10
- Dead code: SendEmailAsync src/content/src/NetWebApiTemplate.Application/Shared/Interface/IEmailSender.cs:7
- Dead code: Encrypt src/content/src/NetWebApiTemplate.Application/Shared/Interface/IEncryptionManager.cs:5
- Dead code: Decrypt src/content/src/NetWebApiTemplate.Application/Shared/Interface/IEncryptionManager.cs:6
- Dead code: LoadAccountAsync src/content/src/NetWebApiTemplate.Application/Shared/Interface/IGitHubService.cs:5
- Dead code: IUnitOfWork src/content/src/NetWebApiTemplate.Application/Shared/Interface/IUnitOfWork.cs:3
- Dead code: DateTimeUtilities src/content/src/NetWebApiTemplate.Application/Shared/Utilities/DateTimeUtilities.cs:3
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Deprecated: Microsoft.AspNetCore.Diagnostics.HealthChecks REDACTED:42
- Deprecated: Microsoft.AspNetCore.Diagnostics.HealthChecks REDACTED:21
- Deprecated: Microsoft.AspNetCore.Mvc.Versioning.ApiExplorer REDACTED:43
- Deprecated: FluentValidation.AspNetCore REDACTED:17
- REDACTED
- REDACTED
- REDACTED
- Cross-slice coupling: Authentication → EmailNotification src/content/src/NetWebApiTemplate.Application/Features/Authentication/Commands/RegisterUser/UserRegisteredEvent.cs:17
- Cross-slice coupling: Authentication → EmailNotification src/content/src/NetWebApiTemplate.Application/Features/Authentication/Commands/RegisterUser/UserRegisteredEvent.cs:28
- TodoComment src/content/src/NetWebApiTemplate.Api/Filters/ApiExceptionFilterAttribute.cs:176
- TodoComment src/content/src/NetWebApiTemplate.Persistence/DbInitializer.cs:21
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Domain type reads the wall clock: RefreshToken src/content/src/NetWebApiTemplate.Domain/Entities/RefreshToken.cs:12
- Non-idempotent mutation: Commands.CreateProductCommandHandler.Handle src/content/src/NetWebApiTemplate.Application/Features/Products/Commands/CreateProduct/CreateProductCommand.cs:23
- Fake-async — async method never awaits src/content/src/NetWebApiTemplate.Application/Features/Authentication/Commands/RegisterUser/UserRegisteredEvent.cs:25
- Outbound HTTP without resilience src/content/src/NetWebApiTemplate.Infrastructure/DependencyInjection.cs:71
- NuGet dependencies are not locked
Minor — 35 finding(s)
- Orphaned file src/content/src/NetWebApiTemplate.Infrastructure/Auth/JwtTokenService.cs:1
- Orphaned file src/content/src/NetWebApiTemplate.Api/Program.cs:1
- Orphaned file REDACTED:1
- Orphaned file src/content/src/NetWebApiTemplate.Infrastructure/DependencyInjection.cs:1
- Orphaned file src/content/src/NetWebApiTemplate.Api/Filters/ApiExceptionFilterAttribute.cs:1
- Orphaned file src/content/src/NetWebApiTemplate.Infrastructure/Auth/AuthenticationService.cs:1
- Orphaned file REDACTED:1
- Orphaned file REDACTED:1
- Commented-out code src/content/src/NetWebApiTemplate.Api/Filters/ApiExceptionFilterAttribute.cs:37
- Commented-out code src/content/src/NetWebApiTemplate.Application/DependencyInjection.cs:26
- Commented-out code src/content/src/NetWebApiTemplate.Application/Features/Authentication/Commands/RegisterUser/UserRegisteredEvent.cs:40
- Commented-out code src/content/src/NetWebApiTemplate.Persistence/DbInitializer.cs:22
- redundant comment src/content/src/NetWebApiTemplate.Api/Program.cs:45
- redundant comment src/content/src/NetWebApiTemplate.Application/Features/Authentication/Commands/RegisterUser/RegisterUserCommand.cs:45
- redundant comment src/content/src/NetWebApiTemplate.Infrastructure/DependencyInjection.cs:80
- README/code drift README.md:37
- README/code drift docs/Getting-Started.md:11
- Outdated: Swashbuckle.AspNetCore REDACTED:58
- REDACTED
- REDACTED
- Orphaned files with no living knowledge
- No tests — template/sample
- No tests found
- No ADRs
- Large public API surface
- Console output used as the logging channel src/content/src/NetWebApiTemplate.Application/Features/Authentication/Commands/RegisterUser/UserRegisteredEvent.cs:39
- No dependency-update automation REDACTED:38
- No rollback/health safety
- No changelog
- No performance benchmarks
- No security response headers detected
- No app-layer HTTPS enforcement detected
- No inbound model validation detected
- Not all async methods take a CancellationToken
- Silent fallback default in catch src/content/src/NetWebApiTemplate.Infrastructure/Auth/JwtTokenService.cs:97
Minor — 23 finding(s)
- Outdated: Mediator.Abstractions
- Outdated: MediatR
- Outdated: Microsoft.AspNetCore.Authentication.JwtBearer
- Outdated: Microsoft.AspNetCore.OpenApi
- Outdated: Microsoft.EntityFrameworkCore.Tools
- Outdated: Newtonsoft.Json
- Outdated: Quartz.Extensions.Hosting
- Outdated: Sentry.AspNetCore
- Outdated: Serilog.AspNetCore
- Outdated: Dapper
- Outdated: FluentValidation
- Outdated: FluentValidation.AspNetCore
- Outdated: Microsoft.Data.SqlClient
- Outdated: Microsoft.EntityFrameworkCore
- Outdated: Microsoft.Extensions.DependencyInjection.Abstractions
- Outdated: Microsoft.Extensions.Logging.Abstractions
- Outdated: Microsoft.EntityFrameworkCore.SqlServer
- Outdated: Microsoft.Extensions.Configuration.Abstractions
- Outdated: Microsoft.Extensions.Http.Polly
- Outdated: Quartz
- Outdated: Microsoft.AspNetCore.Identity.EntityFrameworkCore
- Outdated: Microsoft.Extensions.Diagnostics.HealthChecks.EntityFrameworkCore
- doc comments repeat the names REDACTED:132
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-b49459aff6724cd0930e49ae3faf6436/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-b49459aff6724cd0930e49ae3faf6436/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 . | 34 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | dotnet | — | dotnet list NetWebApiTemplate.sln package --vulnerable --include-transitive --format json | 5 | artifacts/raw/dotnet-vulnerable.json |
| D31 · IaC & Container Security | trivy | — | trivy config --format json --quiet . | 5 | artifacts/raw/trivy-config.json |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep --config /opt/semgrep-rules/gdpr.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt . | 2 | artifacts/raw/semgrep-gdpr.json |
| D36 · Supply-chain Provenance & Signing | provenance | — | provenance: not applicable — This is a dotnet-new template — it produces no released artifact to attest. Supply-chain provenance, signing and SBOM are deferred to the application you build from it (add SLSA provenance / cosign signing / an SBOM in your app's release pipeline). | 0 | — |
| D37 · Vulnerability-disclosure Policy | disclosure | — | disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . /tmp/codehealth-osv-sbom-6d22de58e4374a0cb6bd23c49d55d274 | 0 | artifacts/raw/osv-scanner.json |
Appendix C — Personal-data map
Email — 16 field(s)
- LoginRequest.Email src/content/src/NetWebApiTemplate.Api/Endpoints/Auth/LoginRequest.cs:5
- RegisterRequest.Email src/content/src/NetWebApiTemplate.Api/Endpoints/Auth/RegisterRequest.cs:7
- CurrentUserService.Email src/content/src/NetWebApiTemplate.Api/Services/CurrentUserService.cs:9
- SwaggerDocOptions.Email src/content/src/NetWebApiTemplate.Api/Swagger/SwaggerDocOptions.cs:8
- AddClaimToUserCommand.Email src/content/src/NetWebApiTemplate.Application/Features/Authentication/Commands/AddClaimToUser/AddClaimToUserCommand.cs:8
- AddUserToRoleCommand.Email src/content/src/NetWebApiTemplate.Application/Features/Authentication/Commands/AddUserToRole/AddUserToRoleCommand.cs:8
- LoginCommand.Email src/content/src/NetWebApiTemplate.Application/Features/Authentication/Commands/Login/LoginCommand.cs:9
- RegisterUserCommand.Email src/content/src/NetWebApiTemplate.Application/Features/Authentication/Commands/RegisterUser/RegisterUserCommand.cs:13
- UserRegisteredEvent.Email src/content/src/NetWebApiTemplate.Application/Features/Authentication/Commands/RegisterUser/UserRegisteredEvent.cs:12
- UserRegisteredEventHandler.EmailTemplates src/content/src/NetWebApiTemplate.Application/Features/Authentication/Commands/RegisterUser/UserRegisteredEvent.cs:17
- RemoveUserFromRoleCommand.Email src/content/src/NetWebApiTemplate.Application/Features/Authentication/Commands/RemoveUserFromRole/RemoveUserFromRoleCommand.cs:8
- AppUser.Email src/content/src/NetWebApiTemplate.Application/Features/Authentication/Models/AppUser.cs:7
- GetUserClaimsQuery.Email src/content/src/NetWebApiTemplate.Application/Features/Authentication/Queries/GetUserClaims/GetUserClaimsQuery.cs:8
- GetUserRolesQuery.Email src/content/src/NetWebApiTemplate.Application/Features/Authentication/Queries/GetUserRoles/GetUserRolesQuery.cs:8
- ICurrentUserService.Email src/content/src/NetWebApiTemplate.Application/Shared/Interface/ICurrentUserService.cs:6
- EmailSenderOptions.FromEmail src/content/src/NetWebApiTemplate.Infrastructure/Email/EmailSenderOptions.cs:5
Name — 10 field(s)
- RegisterRequest.FirstName src/content/src/NetWebApiTemplate.Api/Endpoints/Auth/RegisterRequest.cs:5
- RegisterRequest.LastName src/content/src/NetWebApiTemplate.Api/Endpoints/Auth/RegisterRequest.cs:6
- RegisterUserCommand.FirstName src/content/src/NetWebApiTemplate.Application/Features/Authentication/Commands/RegisterUser/RegisterUserCommand.cs:11
- RegisterUserCommand.LastName src/content/src/NetWebApiTemplate.Application/Features/Authentication/Commands/RegisterUser/RegisterUserCommand.cs:12
- UserRegisteredEvent.FirstName src/content/src/NetWebApiTemplate.Application/Features/Authentication/Commands/RegisterUser/UserRegisteredEvent.cs:10
- UserRegisteredEvent.LastName src/content/src/NetWebApiTemplate.Application/Features/Authentication/Commands/RegisterUser/UserRegisteredEvent.cs:11
- AppUser.FirstName src/content/src/NetWebApiTemplate.Application/Features/Authentication/Models/AppUser.cs:5
- AppUser.LastName src/content/src/NetWebApiTemplate.Application/Features/Authentication/Models/AppUser.cs:6
- ApplicationUser.FirstName src/content/src/NetWebApiTemplate.Infrastructure/Auth/ApplicationUser.cs:7
- ApplicationUser.LastName src/content/src/NetWebApiTemplate.Infrastructure/Auth/ApplicationUser.cs:8