Executive summary
samanazadi1996/Sam.CleanArchitecture falls short of our standard for a template or a sample, in part because three passwords or keys sit in the current code. It scores 55 out of 100 and is rated Adequate, and 14 of its 18 critical findings are security problems.
Production Readiness, at 46, is the weakest lens and counts most in the score. The best first step is replacing the three exposed passwords or keys and switching the old ones off, worth about 8 points. Documenting the recovery plan comes next, worth about 6 points. Raising Production Readiness to 52 would lift the score to about 58.
Eight pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Three passwords or keys are open to anyone who can read the repository, and one automatic update takes new releases before a bad one can be spotted. Pinning each tool to an exact version, replacing each exposed password or key and setting a waiting period for automatic updates would close these risks. Updating the vulnerable packages would fix the package with a known security hole, and the unsafe setting in infrastructure or container files needs changing to safe values. The four warnings switched off for a whole file need narrowing to the lines that need them.
The product code is 1,728 lines, about €4,100 to rebuild.
If Production Readiness rose from 46 to 52, the lowest score rated Strong, the score would rise from 55 to about 58.
New since the last survey: 2 findings
- Cancellation propagation · Async delegate without CancellationToken: AddIdentityInfrastructure Source/Src/Infrastructure/CleanArchitecture.Infrastructure.Identity/ServiceRegistration.cs
- Rich vs anemic model · Anemic entity: Product Source/Src/Core/CleanArchitecture.Domain/Products/Entities/Product.cs
Fixed since the last survey: 1 finding
- Code Coverage · Coverage not measured — no coverage collector is wired up
Rebuild cost: about €4,100 · Estimate
| Cost to rebuild | €1,400 to €6,900, for 23 to 73 hours of work, under 0.1 person-years for one engineer |
|---|---|
| Difficulty of the problem | High, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.8 at a score of 55. 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 | Very small: 1,728 lines of product code, of which 45% is declarations and boilerplate, 42% straight logic and 12% logic with branches |
| What it is not | Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one. |
Top priorities
Diagnosis: what the measurements show together
Architecture — bounded-context dependency graph
Architecture: which parts of the code depend on which
| uses → | 1 (global) | 2 CleanArchitecture.Application | 3 CleanArchitecture.Application.DTOs | 4 CleanArchitecture.Application.DTOs.Account.Responses | 5 CleanArchitecture.Application.Parameters | 6 CleanArchitecture.Domain.Common | 7 CleanArchitecture.Infrastructure.Identity | 8 CleanArchitecture.Infrastructure.Identity.Contexts | 9 CleanArchitecture.Infrastructure.Identity.Models | 10 CleanArchitecture.Infrastructure.Identity.Settings | 11 CleanArchitecture.Infrastructure.Persistence | 12 CleanArchitecture.WebApi.Infrastructure.Extensions | 13 CleanArchitecture.Application.DTOs.Account.Requests | 14 CleanArchitecture.Application.Helpers | 15 CleanArchitecture.Application.Interfaces | 16 CleanArchitecture.Application.Wrappers | 17 CleanArchitecture.Domain.Products.Entities | 18 CleanArchitecture.Infrastructure.Identity.Seeds | 19 CleanArchitecture.Application.Behaviours | 20 CleanArchitecture.Application.Interfaces.UserInterfaces | 21 CleanArchitecture.Domain.Products.DTOs | 22 CleanArchitecture.Infrastructure.Persistence.Contexts | 23 CleanArchitecture.Infrastructure.Persistence.Contexts.Configurations | 24 CleanArchitecture.Infrastructure.Persistence.Extensions | 25 CleanArchitecture.Infrastructure.Resources.Services | 26 CleanArchitecture.WebApi.Infrastructure.Services | 27 CleanArchitecture.Application.Features.Accounts.Commands.Authenticate | 28 CleanArchitecture.Application.Features.Accounts.Commands.ChangePassword | 29 CleanArchitecture.Application.Features.Accounts.Commands.ChangeUserName | 30 CleanArchitecture.Application.Features.Accounts.Commands.Start | 31 CleanArchitecture.Application.Interfaces.Repositories | 32 CleanArchitecture.Infrastructure.Identity.Services | 33 CleanArchitecture.Infrastructure.Persistence.Seeds | 34 CleanArchitecture.Application.Features.Products.Commands.CreateProduct | 35 CleanArchitecture.Application.Features.Products.Commands.DeleteProduct | 36 CleanArchitecture.Application.Features.Products.Commands.UpdateProduct | 37 CleanArchitecture.Application.Features.Products.Queries.GetPagedListProduct | 38 CleanArchitecture.Application.Features.Products.Queries.GetProductById | 39 CleanArchitecture.Infrastructure.Persistence.Repositories | 40 CleanArchitecture.WebApi.Endpoints |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 (global) | ||||||||||||||||||||||||||||||||||||||||
| 2 CleanArchitecture.Application | ||||||||||||||||||||||||||||||||||||||||
| 3 CleanArchitecture.Application.DTOs | ||||||||||||||||||||||||||||||||||||||||
| 4 CleanArchitecture.Application.DTOs.Account.Responses | ||||||||||||||||||||||||||||||||||||||||
| 5 CleanArchitecture.Application.Parameters | ||||||||||||||||||||||||||||||||||||||||
| 6 CleanArchitecture.Domain.Common | ||||||||||||||||||||||||||||||||||||||||
| 7 CleanArchitecture.Infrastructure.Identity | ||||||||||||||||||||||||||||||||||||||||
| 8 CleanArchitecture.Infrastructure.Identity.Contexts | ||||||||||||||||||||||||||||||||||||||||
| 9 CleanArchitecture.Infrastructure.Identity.Models | ||||||||||||||||||||||||||||||||||||||||
| 10 CleanArchitecture.Infrastructure.Identity.Settings | ||||||||||||||||||||||||||||||||||||||||
| 11 CleanArchitecture.Infrastructure.Persistence | ||||||||||||||||||||||||||||||||||||||||
| 12 CleanArchitecture.WebApi.Infrastructure.Extensions | ||||||||||||||||||||||||||||||||||||||||
| 13 CleanArchitecture.Application.DTOs.Account.Requests | 1 | |||||||||||||||||||||||||||||||||||||||
| 14 CleanArchitecture.Application.Helpers | 2 | |||||||||||||||||||||||||||||||||||||||
| 15 CleanArchitecture.Application.Interfaces | 1 | |||||||||||||||||||||||||||||||||||||||
| 16 CleanArchitecture.Application.Wrappers | 1 | |||||||||||||||||||||||||||||||||||||||
| 17 CleanArchitecture.Domain.Products.Entities | 1 | |||||||||||||||||||||||||||||||||||||||
| 18 CleanArchitecture.Infrastructure.Identity.Seeds | 2 | |||||||||||||||||||||||||||||||||||||||
| 19 CleanArchitecture.Application.Behaviours | 1 | |||||||||||||||||||||||||||||||||||||||
| 20 CleanArchitecture.Application.Interfaces.UserInterfaces | 2 | 4 | 2 | |||||||||||||||||||||||||||||||||||||
| 21 CleanArchitecture.Domain.Products.DTOs | 1 | |||||||||||||||||||||||||||||||||||||||
| 22 CleanArchitecture.Infrastructure.Persistence.Contexts | 2 | 1 | ||||||||||||||||||||||||||||||||||||||
| 23 CleanArchitecture.Infrastructure.Persistence.Contexts.Configurations | 1 | |||||||||||||||||||||||||||||||||||||||
| 24 CleanArchitecture.Infrastructure.Persistence.Extensions | 1 | |||||||||||||||||||||||||||||||||||||||
| 25 CleanArchitecture.Infrastructure.Resources.Services | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 26 CleanArchitecture.WebApi.Infrastructure.Services | 2 | |||||||||||||||||||||||||||||||||||||||
| 27 CleanArchitecture.Application.Features.Accounts.Commands.Authenticate | 1 | 1 | 3 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 28 CleanArchitecture.Application.Features.Accounts.Commands.ChangePassword | 1 | 3 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 29 CleanArchitecture.Application.Features.Accounts.Commands.ChangeUserName | 1 | 3 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 30 CleanArchitecture.Application.Features.Accounts.Commands.Start | 1 | 2 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 31 CleanArchitecture.Application.Interfaces.Repositories | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 32 CleanArchitecture.Infrastructure.Identity.Services | 2 | 1 | 1 | 1 | 4 | 2 | 2 | 2 | ||||||||||||||||||||||||||||||||
| 33 CleanArchitecture.Infrastructure.Persistence.Seeds | 1 | |||||||||||||||||||||||||||||||||||||||
| 34 CleanArchitecture.Application.Features.Products.Commands.CreateProduct | 4 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 35 CleanArchitecture.Application.Features.Products.Commands.DeleteProduct | 4 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 36 CleanArchitecture.Application.Features.Products.Commands.UpdateProduct | 5 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 37 CleanArchitecture.Application.Features.Products.Queries.GetPagedListProduct | 1 | 2 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 38 CleanArchitecture.Application.Features.Products.Queries.GetProductById | 3 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 39 CleanArchitecture.Infrastructure.Persistence.Repositories | 2 | 1 | 1 | 2 | ||||||||||||||||||||||||||||||||||||
| 40 CleanArchitecture.WebApi.Endpoints | 1 | 3 | 2 | 4 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 |
13→5 CleanArchitecture.Application.DTOs.Account.Requests uses CleanArchitecture.Application.Parameters✕
- Connections
- 1 pair of types, where a type in CleanArchitecture.Application.DTOs.Account.Requests uses a type in CleanArchitecture.Application.Parameters.
- The types involved
CleanArchitecture.Application.DTOs.Account.Requests.GetAllUsersRequest→CleanArchitecture.Application.Parameters.PaginationRequestParameter
- Direction
- CleanArchitecture.Application.DTOs.Account.Requests uses CleanArchitecture.Application.Parameters, so a change to CleanArchitecture.Application.Parameters can break CleanArchitecture.Application.DTOs.Account.Requests, while a change to CleanArchitecture.Application.DTOs.Account.Requests can't break CleanArchitecture.Application.Parameters.
- Position
- Below the diagonal: CleanArchitecture.Application.DTOs.Account.Requests uses a module listed above it, which is the healthy direction.
14→3 CleanArchitecture.Application.Helpers uses CleanArchitecture.Application.DTOs✕
- Connections
- 2 pairs of types, where a type in CleanArchitecture.Application.Helpers uses a type in CleanArchitecture.Application.DTOs.
- The types involved
CleanArchitecture.Application.Helpers.AccountMessages→CleanArchitecture.Application.DTOs.TranslatorMessageDtoCleanArchitecture.Application.Helpers.ProductMessages→CleanArchitecture.Application.DTOs.TranslatorMessageDto
- Direction
- CleanArchitecture.Application.Helpers uses CleanArchitecture.Application.DTOs, so a change to CleanArchitecture.Application.DTOs can break CleanArchitecture.Application.Helpers, while a change to CleanArchitecture.Application.Helpers can't break CleanArchitecture.Application.DTOs.
- Position
- Below the diagonal: CleanArchitecture.Application.Helpers uses a module listed above it, which is the healthy direction.
15→3 CleanArchitecture.Application.Interfaces uses CleanArchitecture.Application.DTOs✕
- Connections
- 1 pair of types, where a type in CleanArchitecture.Application.Interfaces uses a type in CleanArchitecture.Application.DTOs.
- The types involved
CleanArchitecture.Application.Interfaces.ITranslator→CleanArchitecture.Application.DTOs.TranslatorMessageDto
- Direction
- CleanArchitecture.Application.Interfaces uses CleanArchitecture.Application.DTOs, so a change to CleanArchitecture.Application.DTOs can break CleanArchitecture.Application.Interfaces, while a change to CleanArchitecture.Application.Interfaces can't break CleanArchitecture.Application.DTOs.
- Position
- Below the diagonal: CleanArchitecture.Application.Interfaces uses a module listed above it, which is the healthy direction.
16→3 CleanArchitecture.Application.Wrappers uses CleanArchitecture.Application.DTOs✕
- Connections
- 1 pair of types, where a type in CleanArchitecture.Application.Wrappers uses a type in CleanArchitecture.Application.DTOs.
- The types involved
CleanArchitecture.Application.Wrappers.PagedResponse→CleanArchitecture.Application.DTOs.PaginationResponseDto
- Direction
- CleanArchitecture.Application.Wrappers uses CleanArchitecture.Application.DTOs, so a change to CleanArchitecture.Application.DTOs can break CleanArchitecture.Application.Wrappers, while a change to CleanArchitecture.Application.Wrappers can't break CleanArchitecture.Application.DTOs.
- Position
- Below the diagonal: CleanArchitecture.Application.Wrappers uses a module listed above it, which is the healthy direction.
17→6 CleanArchitecture.Domain.Products.Entities uses CleanArchitecture.Domain.Common✕
- Connections
- 1 pair of types, where a type in CleanArchitecture.Domain.Products.Entities uses a type in CleanArchitecture.Domain.Common.
- The types involved
CleanArchitecture.Domain.Products.Entities.Product→CleanArchitecture.Domain.Common.AuditableBaseEntity
- Direction
- CleanArchitecture.Domain.Products.Entities uses CleanArchitecture.Domain.Common, so a change to CleanArchitecture.Domain.Common can break CleanArchitecture.Domain.Products.Entities, while a change to CleanArchitecture.Domain.Products.Entities can't break CleanArchitecture.Domain.Common.
- Position
- Below the diagonal: CleanArchitecture.Domain.Products.Entities uses a module listed above it, which is the healthy direction.
18→9 CleanArchitecture.Infrastructure.Identity.Seeds uses CleanArchitecture.Infrastructure.Identity.Models✕
- Connections
- 2 pairs of types, where a type in CleanArchitecture.Infrastructure.Identity.Seeds uses a type in CleanArchitecture.Infrastructure.Identity.Models.
- The types involved
CleanArchitecture.Infrastructure.Identity.Seeds.DefaultBasicUser→CleanArchitecture.Infrastructure.Identity.Models.ApplicationUserCleanArchitecture.Infrastructure.Identity.Seeds.DefaultRoles→CleanArchitecture.Infrastructure.Identity.Models.ApplicationRole
- Direction
- CleanArchitecture.Infrastructure.Identity.Seeds uses CleanArchitecture.Infrastructure.Identity.Models, so a change to CleanArchitecture.Infrastructure.Identity.Models can break CleanArchitecture.Infrastructure.Identity.Seeds, while a change to CleanArchitecture.Infrastructure.Identity.Seeds can't break CleanArchitecture.Infrastructure.Identity.Models.
- Position
- Below the diagonal: CleanArchitecture.Infrastructure.Identity.Seeds uses a module listed above it, which is the healthy direction.
19→15 CleanArchitecture.Application.Behaviours uses CleanArchitecture.Application.Interfaces✕
- Connections
- 1 pair of types, where a type in CleanArchitecture.Application.Behaviours uses a type in CleanArchitecture.Application.Interfaces.
- The types involved
CleanArchitecture.Application.Behaviours.ValidationBehavior→CleanArchitecture.Application.Interfaces.IPipelineBehavior
- Direction
- CleanArchitecture.Application.Behaviours uses CleanArchitecture.Application.Interfaces, so a change to CleanArchitecture.Application.Interfaces can break CleanArchitecture.Application.Behaviours, while a change to CleanArchitecture.Application.Behaviours can't break CleanArchitecture.Application.Interfaces.
- Position
- Below the diagonal: CleanArchitecture.Application.Behaviours uses a module listed above it, which is the healthy direction.
20→4 CleanArchitecture.Application.Interfaces.UserInterfaces uses CleanArchitecture.Application.DTOs.Account.Responses✕
- Connections
- 2 pairs of types, where a type in CleanArchitecture.Application.Interfaces.UserInterfaces uses a type in CleanArchitecture.Application.DTOs.Account.Responses.
- The types involved
CleanArchitecture.Application.Interfaces.UserInterfaces.IAccountServices→CleanArchitecture.Application.DTOs.Account.Responses.AuthenticationResponseCleanArchitecture.Application.Interfaces.UserInterfaces.IGetUserServices→CleanArchitecture.Application.DTOs.Account.Responses.UserDto
- Direction
- CleanArchitecture.Application.Interfaces.UserInterfaces uses CleanArchitecture.Application.DTOs.Account.Responses, so a change to CleanArchitecture.Application.DTOs.Account.Responses can break CleanArchitecture.Application.Interfaces.UserInterfaces, while a change to CleanArchitecture.Application.Interfaces.UserInterfaces can't break CleanArchitecture.Application.DTOs.Account.Responses.
- Position
- Below the diagonal: CleanArchitecture.Application.Interfaces.UserInterfaces uses a module listed above it, which is the healthy direction.
20→13 CleanArchitecture.Application.Interfaces.UserInterfaces uses CleanArchitecture.Application.DTOs.Account.Requests✕
- Connections
- 4 pairs of types, where a type in CleanArchitecture.Application.Interfaces.UserInterfaces uses a type in CleanArchitecture.Application.DTOs.Account.Requests.
- The types involved
CleanArchitecture.Application.Interfaces.UserInterfaces.IAccountServices→CleanArchitecture.Application.DTOs.Account.Requests.AuthenticationRequestCleanArchitecture.Application.Interfaces.UserInterfaces.IAccountServices→CleanArchitecture.Application.DTOs.Account.Requests.ChangePasswordRequestCleanArchitecture.Application.Interfaces.UserInterfaces.IAccountServices→CleanArchitecture.Application.DTOs.Account.Requests.ChangeUserNameRequestCleanArchitecture.Application.Interfaces.UserInterfaces.IGetUserServices→CleanArchitecture.Application.DTOs.Account.Requests.GetAllUsersRequest
- Direction
- CleanArchitecture.Application.Interfaces.UserInterfaces uses CleanArchitecture.Application.DTOs.Account.Requests, so a change to CleanArchitecture.Application.DTOs.Account.Requests can break CleanArchitecture.Application.Interfaces.UserInterfaces, while a change to CleanArchitecture.Application.Interfaces.UserInterfaces can't break CleanArchitecture.Application.DTOs.Account.Requests.
- Position
- Below the diagonal: CleanArchitecture.Application.Interfaces.UserInterfaces uses a module listed above it, which is the healthy direction.
20→16 CleanArchitecture.Application.Interfaces.UserInterfaces uses CleanArchitecture.Application.Wrappers✕
- Connections
- 2 pairs of types, where a type in CleanArchitecture.Application.Interfaces.UserInterfaces uses a type in CleanArchitecture.Application.Wrappers.
- The types involved
CleanArchitecture.Application.Interfaces.UserInterfaces.IAccountServices→CleanArchitecture.Application.Wrappers.BaseResultCleanArchitecture.Application.Interfaces.UserInterfaces.IGetUserServices→CleanArchitecture.Application.Wrappers.PagedResponse
- Direction
- CleanArchitecture.Application.Interfaces.UserInterfaces uses CleanArchitecture.Application.Wrappers, so a change to CleanArchitecture.Application.Wrappers can break CleanArchitecture.Application.Interfaces.UserInterfaces, while a change to CleanArchitecture.Application.Interfaces.UserInterfaces can't break CleanArchitecture.Application.Wrappers.
- Position
- Below the diagonal: CleanArchitecture.Application.Interfaces.UserInterfaces uses a module listed above it, which is the healthy direction.
21→17 CleanArchitecture.Domain.Products.DTOs uses CleanArchitecture.Domain.Products.Entities✕
- Connections
- 1 pair of types, where a type in CleanArchitecture.Domain.Products.DTOs uses a type in CleanArchitecture.Domain.Products.Entities.
- The types involved
CleanArchitecture.Domain.Products.DTOs.ProductDto→CleanArchitecture.Domain.Products.Entities.Product
- Direction
- CleanArchitecture.Domain.Products.DTOs uses CleanArchitecture.Domain.Products.Entities, so a change to CleanArchitecture.Domain.Products.Entities can break CleanArchitecture.Domain.Products.DTOs, while a change to CleanArchitecture.Domain.Products.DTOs can't break CleanArchitecture.Domain.Products.Entities.
- Position
- Below the diagonal: CleanArchitecture.Domain.Products.DTOs uses a module listed above it, which is the healthy direction.
22→15 CleanArchitecture.Infrastructure.Persistence.Contexts uses CleanArchitecture.Application.Interfaces✕
- Connections
- 2 pairs of types, where a type in CleanArchitecture.Infrastructure.Persistence.Contexts uses a type in CleanArchitecture.Application.Interfaces.
- The types involved
CleanArchitecture.Infrastructure.Persistence.Contexts.ApplicationDbContext→CleanArchitecture.Application.Interfaces.IAuthenticatedUserServiceCleanArchitecture.Infrastructure.Persistence.Contexts.UnitOfWork→CleanArchitecture.Application.Interfaces.IUnitOfWork
- Direction
- CleanArchitecture.Infrastructure.Persistence.Contexts uses CleanArchitecture.Application.Interfaces, so a change to CleanArchitecture.Application.Interfaces can break CleanArchitecture.Infrastructure.Persistence.Contexts, while a change to CleanArchitecture.Infrastructure.Persistence.Contexts can't break CleanArchitecture.Application.Interfaces.
- Position
- Below the diagonal: CleanArchitecture.Infrastructure.Persistence.Contexts uses a module listed above it, which is the healthy direction.
22→17 CleanArchitecture.Infrastructure.Persistence.Contexts uses CleanArchitecture.Domain.Products.Entities✕
- Connections
- 1 pair of types, where a type in CleanArchitecture.Infrastructure.Persistence.Contexts uses a type in CleanArchitecture.Domain.Products.Entities.
- The types involved
CleanArchitecture.Infrastructure.Persistence.Contexts.ApplicationDbContext→CleanArchitecture.Domain.Products.Entities.Product
- Direction
- CleanArchitecture.Infrastructure.Persistence.Contexts uses CleanArchitecture.Domain.Products.Entities, so a change to CleanArchitecture.Domain.Products.Entities can break CleanArchitecture.Infrastructure.Persistence.Contexts, while a change to CleanArchitecture.Infrastructure.Persistence.Contexts can't break CleanArchitecture.Domain.Products.Entities.
- Position
- Below the diagonal: CleanArchitecture.Infrastructure.Persistence.Contexts uses a module listed above it, which is the healthy direction.
23→17 CleanArchitecture.Infrastructure.Persistence.Contexts.Configurations uses CleanArchitecture.Domain.Products.Entities✕
- Connections
- 1 pair of types, where a type in CleanArchitecture.Infrastructure.Persistence.Contexts.Configurations uses a type in CleanArchitecture.Domain.Products.Entities.
- The types involved
CleanArchitecture.Infrastructure.Persistence.Contexts.Configurations.ProductConfiguration→CleanArchitecture.Domain.Products.Entities.Product
- Direction
- CleanArchitecture.Infrastructure.Persistence.Contexts.Configurations uses CleanArchitecture.Domain.Products.Entities, so a change to CleanArchitecture.Domain.Products.Entities can break CleanArchitecture.Infrastructure.Persistence.Contexts.Configurations, while a change to CleanArchitecture.Infrastructure.Persistence.Contexts.Configurations can't break CleanArchitecture.Domain.Products.Entities.
- Position
- Below the diagonal: CleanArchitecture.Infrastructure.Persistence.Contexts.Configurations uses a module listed above it, which is the healthy direction.
24→15 CleanArchitecture.Infrastructure.Persistence.Extensions uses CleanArchitecture.Application.Interfaces✕
- Connections
- 1 pair of types, where a type in CleanArchitecture.Infrastructure.Persistence.Extensions uses a type in CleanArchitecture.Application.Interfaces.
- The types involved
CleanArchitecture.Infrastructure.Persistence.Extensions.EntityFrameworkExtensions→CleanArchitecture.Application.Interfaces.IAuthenticatedUserService
- Direction
- CleanArchitecture.Infrastructure.Persistence.Extensions uses CleanArchitecture.Application.Interfaces, so a change to CleanArchitecture.Application.Interfaces can break CleanArchitecture.Infrastructure.Persistence.Extensions, while a change to CleanArchitecture.Infrastructure.Persistence.Extensions can't break CleanArchitecture.Application.Interfaces.
- Position
- Below the diagonal: CleanArchitecture.Infrastructure.Persistence.Extensions uses a module listed above it, which is the healthy direction.
25→3 CleanArchitecture.Infrastructure.Resources.Services uses CleanArchitecture.Application.DTOs✕
- Connections
- 1 pair of types, where a type in CleanArchitecture.Infrastructure.Resources.Services uses a type in CleanArchitecture.Application.DTOs.
- The types involved
CleanArchitecture.Infrastructure.Resources.Services.Translator→CleanArchitecture.Application.DTOs.TranslatorMessageDto
- Direction
- CleanArchitecture.Infrastructure.Resources.Services uses CleanArchitecture.Application.DTOs, so a change to CleanArchitecture.Application.DTOs can break CleanArchitecture.Infrastructure.Resources.Services, while a change to CleanArchitecture.Infrastructure.Resources.Services can't break CleanArchitecture.Application.DTOs.
- Position
- Below the diagonal: CleanArchitecture.Infrastructure.Resources.Services uses a module listed above it, which is the healthy direction.
25→15 CleanArchitecture.Infrastructure.Resources.Services uses CleanArchitecture.Application.Interfaces✕
- Connections
- 1 pair of types, where a type in CleanArchitecture.Infrastructure.Resources.Services uses a type in CleanArchitecture.Application.Interfaces.
- The types involved
CleanArchitecture.Infrastructure.Resources.Services.Translator→CleanArchitecture.Application.Interfaces.ITranslator
- Direction
- CleanArchitecture.Infrastructure.Resources.Services uses CleanArchitecture.Application.Interfaces, so a change to CleanArchitecture.Application.Interfaces can break CleanArchitecture.Infrastructure.Resources.Services, while a change to CleanArchitecture.Infrastructure.Resources.Services can't break CleanArchitecture.Application.Interfaces.
- Position
- Below the diagonal: CleanArchitecture.Infrastructure.Resources.Services uses a module listed above it, which is the healthy direction.
26→15 CleanArchitecture.WebApi.Infrastructure.Services uses CleanArchitecture.Application.Interfaces✕
- Connections
- 2 pairs of types, where a type in CleanArchitecture.WebApi.Infrastructure.Services uses a type in CleanArchitecture.Application.Interfaces.
- The types involved
CleanArchitecture.WebApi.Infrastructure.Services.AuthenticatedUserService→CleanArchitecture.Application.Interfaces.IAuthenticatedUserServiceCleanArchitecture.WebApi.Infrastructure.Services.MediatorService→CleanArchitecture.Application.Interfaces.IMediator
- Direction
- CleanArchitecture.WebApi.Infrastructure.Services uses CleanArchitecture.Application.Interfaces, so a change to CleanArchitecture.Application.Interfaces can break CleanArchitecture.WebApi.Infrastructure.Services, while a change to CleanArchitecture.WebApi.Infrastructure.Services can't break CleanArchitecture.Application.Interfaces.
- Position
- Below the diagonal: CleanArchitecture.WebApi.Infrastructure.Services uses a module listed above it, which is the healthy direction.
27→4 CleanArchitecture.Application.Features.Accounts.Commands.Authenticate uses CleanArchitecture.Application.DTOs.Account.Responses✕
- Connections
- 1 pair of types, where a type in CleanArchitecture.Application.Features.Accounts.Commands.Authenticate uses a type in CleanArchitecture.Application.DTOs.Account.Responses.
- The types involved
CleanArchitecture.Application.Features.Accounts.Commands.Authenticate.AuthenticateCommandHandler→CleanArchitecture.Application.DTOs.Account.Responses.AuthenticationResponse
- Direction
- CleanArchitecture.Application.Features.Accounts.Commands.Authenticate uses CleanArchitecture.Application.DTOs.Account.Responses, so a change to CleanArchitecture.Application.DTOs.Account.Responses can break CleanArchitecture.Application.Features.Accounts.Commands.Authenticate, while a change to CleanArchitecture.Application.Features.Accounts.Commands.Authenticate can't break CleanArchitecture.Application.DTOs.Account.Responses.
- Position
- Below the diagonal: CleanArchitecture.Application.Features.Accounts.Commands.Authenticate uses a module listed above it, which is the healthy direction.
27→13 CleanArchitecture.Application.Features.Accounts.Commands.Authenticate uses CleanArchitecture.Application.DTOs.Account.Requests✕
- Connections
- 1 pair of types, where a type in CleanArchitecture.Application.Features.Accounts.Commands.Authenticate uses a type in CleanArchitecture.Application.DTOs.Account.Requests.
- The types involved
CleanArchitecture.Application.Features.Accounts.Commands.Authenticate.AuthenticateCommand→CleanArchitecture.Application.DTOs.Account.Requests.AuthenticationRequest
- Direction
- CleanArchitecture.Application.Features.Accounts.Commands.Authenticate uses CleanArchitecture.Application.DTOs.Account.Requests, so a change to CleanArchitecture.Application.DTOs.Account.Requests can break CleanArchitecture.Application.Features.Accounts.Commands.Authenticate, while a change to CleanArchitecture.Application.Features.Accounts.Commands.Authenticate can't break CleanArchitecture.Application.DTOs.Account.Requests.
- Position
- Below the diagonal: CleanArchitecture.Application.Features.Accounts.Commands.Authenticate uses a module listed above it, which is the healthy direction.
27→15 CleanArchitecture.Application.Features.Accounts.Commands.Authenticate uses CleanArchitecture.Application.Interfaces✕
- Connections
- 3 pairs of types, where a type in CleanArchitecture.Application.Features.Accounts.Commands.Authenticate uses a type in CleanArchitecture.Application.Interfaces.
- The types involved
CleanArchitecture.Application.Features.Accounts.Commands.Authenticate.AuthenticateCommand→CleanArchitecture.Application.Interfaces.IRequestCleanArchitecture.Application.Features.Accounts.Commands.Authenticate.AuthenticateCommandHandler→CleanArchitecture.Application.Interfaces.IRequestHandlerCleanArchitecture.Application.Features.Accounts.Commands.Authenticate.AuthenticateCommandValidator→CleanArchitecture.Application.Interfaces.ITranslator
- Direction
- CleanArchitecture.Application.Features.Accounts.Commands.Authenticate uses CleanArchitecture.Application.Interfaces, so a change to CleanArchitecture.Application.Interfaces can break CleanArchitecture.Application.Features.Accounts.Commands.Authenticate, while a change to CleanArchitecture.Application.Features.Accounts.Commands.Authenticate can't break CleanArchitecture.Application.Interfaces.
- Position
- Below the diagonal: CleanArchitecture.Application.Features.Accounts.Commands.Authenticate uses a module listed above it, which is the healthy direction.
27→16 CleanArchitecture.Application.Features.Accounts.Commands.Authenticate uses CleanArchitecture.Application.Wrappers✕
- Connections
- 1 pair of types, where a type in CleanArchitecture.Application.Features.Accounts.Commands.Authenticate uses a type in CleanArchitecture.Application.Wrappers.
- The types involved
CleanArchitecture.Application.Features.Accounts.Commands.Authenticate.AuthenticateCommandHandler→CleanArchitecture.Application.Wrappers.BaseResult
- Direction
- CleanArchitecture.Application.Features.Accounts.Commands.Authenticate uses CleanArchitecture.Application.Wrappers, so a change to CleanArchitecture.Application.Wrappers can break CleanArchitecture.Application.Features.Accounts.Commands.Authenticate, while a change to CleanArchitecture.Application.Features.Accounts.Commands.Authenticate can't break CleanArchitecture.Application.Wrappers.
- Position
- Below the diagonal: CleanArchitecture.Application.Features.Accounts.Commands.Authenticate uses a module listed above it, which is the healthy direction.
27→20 CleanArchitecture.Application.Features.Accounts.Commands.Authenticate uses CleanArchitecture.Application.Interfaces.UserInterfaces✕
- Connections
- 1 pair of types, where a type in CleanArchitecture.Application.Features.Accounts.Commands.Authenticate uses a type in CleanArchitecture.Application.Interfaces.UserInterfaces.
- The types involved
CleanArchitecture.Application.Features.Accounts.Commands.Authenticate.AuthenticateCommandHandler→CleanArchitecture.Application.Interfaces.UserInterfaces.IAccountServices
- Direction
- CleanArchitecture.Application.Features.Accounts.Commands.Authenticate uses CleanArchitecture.Application.Interfaces.UserInterfaces, so a change to CleanArchitecture.Application.Interfaces.UserInterfaces can break CleanArchitecture.Application.Features.Accounts.Commands.Authenticate, while a change to CleanArchitecture.Application.Features.Accounts.Commands.Authenticate can't break CleanArchitecture.Application.Interfaces.UserInterfaces.
- Position
- Below the diagonal: CleanArchitecture.Application.Features.Accounts.Commands.Authenticate uses a module listed above it, which is the healthy direction.
28→13 CleanArchitecture.Application.Features.Accounts.Commands.ChangePassword uses CleanArchitecture.Application.DTOs.Account.Requests✕
- Connections
- 1 pair of types, where a type in CleanArchitecture.Application.Features.Accounts.Commands.ChangePassword uses a type in CleanArchitecture.Application.DTOs.Account.Requests.
- The types involved
CleanArchitecture.Application.Features.Accounts.Commands.ChangePassword.ChangePasswordCommand→CleanArchitecture.Application.DTOs.Account.Requests.ChangePasswordRequest
- Direction
- CleanArchitecture.Application.Features.Accounts.Commands.ChangePassword uses CleanArchitecture.Application.DTOs.Account.Requests, so a change to CleanArchitecture.Application.DTOs.Account.Requests can break CleanArchitecture.Application.Features.Accounts.Commands.ChangePassword, while a change to CleanArchitecture.Application.Features.Accounts.Commands.ChangePassword can't break CleanArchitecture.Application.DTOs.Account.Requests.
- Position
- Below the diagonal: CleanArchitecture.Application.Features.Accounts.Commands.ChangePassword uses a module listed above it, which is the healthy direction.
28→15 CleanArchitecture.Application.Features.Accounts.Commands.ChangePassword uses CleanArchitecture.Application.Interfaces✕
- Connections
- 3 pairs of types, where a type in CleanArchitecture.Application.Features.Accounts.Commands.ChangePassword uses a type in CleanArchitecture.Application.Interfaces.
- The types involved
CleanArchitecture.Application.Features.Accounts.Commands.ChangePassword.ChangePasswordCommand→CleanArchitecture.Application.Interfaces.IRequestCleanArchitecture.Application.Features.Accounts.Commands.ChangePassword.ChangePasswordCommandHandler→CleanArchitecture.Application.Interfaces.IRequestHandlerCleanArchitecture.Application.Features.Accounts.Commands.ChangePassword.ChangePasswordCommandValidator→CleanArchitecture.Application.Interfaces.ITranslator
- Direction
- CleanArchitecture.Application.Features.Accounts.Commands.ChangePassword uses CleanArchitecture.Application.Interfaces, so a change to CleanArchitecture.Application.Interfaces can break CleanArchitecture.Application.Features.Accounts.Commands.ChangePassword, while a change to CleanArchitecture.Application.Features.Accounts.Commands.ChangePassword can't break CleanArchitecture.Application.Interfaces.
- Position
- Below the diagonal: CleanArchitecture.Application.Features.Accounts.Commands.ChangePassword uses a module listed above it, which is the healthy direction.
28→16 CleanArchitecture.Application.Features.Accounts.Commands.ChangePassword uses CleanArchitecture.Application.Wrappers✕
- Connections
- 1 pair of types, where a type in CleanArchitecture.Application.Features.Accounts.Commands.ChangePassword uses a type in CleanArchitecture.Application.Wrappers.
- The types involved
CleanArchitecture.Application.Features.Accounts.Commands.ChangePassword.ChangePasswordCommandHandler→CleanArchitecture.Application.Wrappers.BaseResult
- Direction
- CleanArchitecture.Application.Features.Accounts.Commands.ChangePassword uses CleanArchitecture.Application.Wrappers, so a change to CleanArchitecture.Application.Wrappers can break CleanArchitecture.Application.Features.Accounts.Commands.ChangePassword, while a change to CleanArchitecture.Application.Features.Accounts.Commands.ChangePassword can't break CleanArchitecture.Application.Wrappers.
- Position
- Below the diagonal: CleanArchitecture.Application.Features.Accounts.Commands.ChangePassword uses a module listed above it, which is the healthy direction.
28→20 CleanArchitecture.Application.Features.Accounts.Commands.ChangePassword uses CleanArchitecture.Application.Interfaces.UserInterfaces✕
- Connections
- 1 pair of types, where a type in CleanArchitecture.Application.Features.Accounts.Commands.ChangePassword uses a type in CleanArchitecture.Application.Interfaces.UserInterfaces.
- The types involved
CleanArchitecture.Application.Features.Accounts.Commands.ChangePassword.ChangePasswordCommandHandler→CleanArchitecture.Application.Interfaces.UserInterfaces.IAccountServices
- Direction
- CleanArchitecture.Application.Features.Accounts.Commands.ChangePassword uses CleanArchitecture.Application.Interfaces.UserInterfaces, so a change to CleanArchitecture.Application.Interfaces.UserInterfaces can break CleanArchitecture.Application.Features.Accounts.Commands.ChangePassword, while a change to CleanArchitecture.Application.Features.Accounts.Commands.ChangePassword can't break CleanArchitecture.Application.Interfaces.UserInterfaces.
- Position
- Below the diagonal: CleanArchitecture.Application.Features.Accounts.Commands.ChangePassword uses a module listed above it, which is the healthy direction.
29→13 CleanArchitecture.Application.Features.Accounts.Commands.ChangeUserName uses CleanArchitecture.Application.DTOs.Account.Requests✕
- Connections
- 1 pair of types, where a type in CleanArchitecture.Application.Features.Accounts.Commands.ChangeUserName uses a type in CleanArchitecture.Application.DTOs.Account.Requests.
- The types involved
CleanArchitecture.Application.Features.Accounts.Commands.ChangeUserName.ChangeUserNameCommand→CleanArchitecture.Application.DTOs.Account.Requests.ChangeUserNameRequest
- Direction
- CleanArchitecture.Application.Features.Accounts.Commands.ChangeUserName uses CleanArchitecture.Application.DTOs.Account.Requests, so a change to CleanArchitecture.Application.DTOs.Account.Requests can break CleanArchitecture.Application.Features.Accounts.Commands.ChangeUserName, while a change to CleanArchitecture.Application.Features.Accounts.Commands.ChangeUserName can't break CleanArchitecture.Application.DTOs.Account.Requests.
- Position
- Below the diagonal: CleanArchitecture.Application.Features.Accounts.Commands.ChangeUserName uses a module listed above it, which is the healthy direction.
29→15 CleanArchitecture.Application.Features.Accounts.Commands.ChangeUserName uses CleanArchitecture.Application.Interfaces✕
- Connections
- 3 pairs of types, where a type in CleanArchitecture.Application.Features.Accounts.Commands.ChangeUserName uses a type in CleanArchitecture.Application.Interfaces.
- The types involved
CleanArchitecture.Application.Features.Accounts.Commands.ChangeUserName.ChangeUserNameCommand→CleanArchitecture.Application.Interfaces.IRequestCleanArchitecture.Application.Features.Accounts.Commands.ChangeUserName.ChangeUserNameCommandHandler→CleanArchitecture.Application.Interfaces.IRequestHandlerCleanArchitecture.Application.Features.Accounts.Commands.ChangeUserName.ChangeUserNameCommandValidator→CleanArchitecture.Application.Interfaces.ITranslator
- Direction
- CleanArchitecture.Application.Features.Accounts.Commands.ChangeUserName uses CleanArchitecture.Application.Interfaces, so a change to CleanArchitecture.Application.Interfaces can break CleanArchitecture.Application.Features.Accounts.Commands.ChangeUserName, while a change to CleanArchitecture.Application.Features.Accounts.Commands.ChangeUserName can't break CleanArchitecture.Application.Interfaces.
- Position
- Below the diagonal: CleanArchitecture.Application.Features.Accounts.Commands.ChangeUserName uses a module listed above it, which is the healthy direction.
29→16 CleanArchitecture.Application.Features.Accounts.Commands.ChangeUserName uses CleanArchitecture.Application.Wrappers✕
- Connections
- 1 pair of types, where a type in CleanArchitecture.Application.Features.Accounts.Commands.ChangeUserName uses a type in CleanArchitecture.Application.Wrappers.
- The types involved
CleanArchitecture.Application.Features.Accounts.Commands.ChangeUserName.ChangeUserNameCommandHandler→CleanArchitecture.Application.Wrappers.BaseResult
- Direction
- CleanArchitecture.Application.Features.Accounts.Commands.ChangeUserName uses CleanArchitecture.Application.Wrappers, so a change to CleanArchitecture.Application.Wrappers can break CleanArchitecture.Application.Features.Accounts.Commands.ChangeUserName, while a change to CleanArchitecture.Application.Features.Accounts.Commands.ChangeUserName can't break CleanArchitecture.Application.Wrappers.
- Position
- Below the diagonal: CleanArchitecture.Application.Features.Accounts.Commands.ChangeUserName uses a module listed above it, which is the healthy direction.
29→20 CleanArchitecture.Application.Features.Accounts.Commands.ChangeUserName uses CleanArchitecture.Application.Interfaces.UserInterfaces✕
- Connections
- 1 pair of types, where a type in CleanArchitecture.Application.Features.Accounts.Commands.ChangeUserName uses a type in CleanArchitecture.Application.Interfaces.UserInterfaces.
- The types involved
CleanArchitecture.Application.Features.Accounts.Commands.ChangeUserName.ChangeUserNameCommandHandler→CleanArchitecture.Application.Interfaces.UserInterfaces.IAccountServices
- Direction
- CleanArchitecture.Application.Features.Accounts.Commands.ChangeUserName uses CleanArchitecture.Application.Interfaces.UserInterfaces, so a change to CleanArchitecture.Application.Interfaces.UserInterfaces can break CleanArchitecture.Application.Features.Accounts.Commands.ChangeUserName, while a change to CleanArchitecture.Application.Features.Accounts.Commands.ChangeUserName can't break CleanArchitecture.Application.Interfaces.UserInterfaces.
- Position
- Below the diagonal: CleanArchitecture.Application.Features.Accounts.Commands.ChangeUserName uses a module listed above it, which is the healthy direction.
30→4 CleanArchitecture.Application.Features.Accounts.Commands.Start uses CleanArchitecture.Application.DTOs.Account.Responses✕
- Connections
- 1 pair of types, where a type in CleanArchitecture.Application.Features.Accounts.Commands.Start uses a type in CleanArchitecture.Application.DTOs.Account.Responses.
- The types involved
CleanArchitecture.Application.Features.Accounts.Commands.Start.StartCommandHandler→CleanArchitecture.Application.DTOs.Account.Responses.AuthenticationResponse
- Direction
- CleanArchitecture.Application.Features.Accounts.Commands.Start uses CleanArchitecture.Application.DTOs.Account.Responses, so a change to CleanArchitecture.Application.DTOs.Account.Responses can break CleanArchitecture.Application.Features.Accounts.Commands.Start, while a change to CleanArchitecture.Application.Features.Accounts.Commands.Start can't break CleanArchitecture.Application.DTOs.Account.Responses.
- Position
- Below the diagonal: CleanArchitecture.Application.Features.Accounts.Commands.Start uses a module listed above it, which is the healthy direction.
30→15 CleanArchitecture.Application.Features.Accounts.Commands.Start uses CleanArchitecture.Application.Interfaces✕
- Connections
- 2 pairs of types, where a type in CleanArchitecture.Application.Features.Accounts.Commands.Start uses a type in CleanArchitecture.Application.Interfaces.
- The types involved
CleanArchitecture.Application.Features.Accounts.Commands.Start.StartCommand→CleanArchitecture.Application.Interfaces.IRequestCleanArchitecture.Application.Features.Accounts.Commands.Start.StartCommandHandler→CleanArchitecture.Application.Interfaces.IRequestHandler
- Direction
- CleanArchitecture.Application.Features.Accounts.Commands.Start uses CleanArchitecture.Application.Interfaces, so a change to CleanArchitecture.Application.Interfaces can break CleanArchitecture.Application.Features.Accounts.Commands.Start, while a change to CleanArchitecture.Application.Features.Accounts.Commands.Start can't break CleanArchitecture.Application.Interfaces.
- Position
- Below the diagonal: CleanArchitecture.Application.Features.Accounts.Commands.Start uses a module listed above it, which is the healthy direction.
30→16 CleanArchitecture.Application.Features.Accounts.Commands.Start uses CleanArchitecture.Application.Wrappers✕
- Connections
- 1 pair of types, where a type in CleanArchitecture.Application.Features.Accounts.Commands.Start uses a type in CleanArchitecture.Application.Wrappers.
- The types involved
CleanArchitecture.Application.Features.Accounts.Commands.Start.StartCommandHandler→CleanArchitecture.Application.Wrappers.BaseResult
- Direction
- CleanArchitecture.Application.Features.Accounts.Commands.Start uses CleanArchitecture.Application.Wrappers, so a change to CleanArchitecture.Application.Wrappers can break CleanArchitecture.Application.Features.Accounts.Commands.Start, while a change to CleanArchitecture.Application.Features.Accounts.Commands.Start can't break CleanArchitecture.Application.Wrappers.
- Position
- Below the diagonal: CleanArchitecture.Application.Features.Accounts.Commands.Start uses a module listed above it, which is the healthy direction.
30→20 CleanArchitecture.Application.Features.Accounts.Commands.Start uses CleanArchitecture.Application.Interfaces.UserInterfaces✕
- Connections
- 1 pair of types, where a type in CleanArchitecture.Application.Features.Accounts.Commands.Start uses a type in CleanArchitecture.Application.Interfaces.UserInterfaces.
- The types involved
CleanArchitecture.Application.Features.Accounts.Commands.Start.StartCommandHandler→CleanArchitecture.Application.Interfaces.UserInterfaces.IAccountServices
- Direction
- CleanArchitecture.Application.Features.Accounts.Commands.Start uses CleanArchitecture.Application.Interfaces.UserInterfaces, so a change to CleanArchitecture.Application.Interfaces.UserInterfaces can break CleanArchitecture.Application.Features.Accounts.Commands.Start, while a change to CleanArchitecture.Application.Features.Accounts.Commands.Start can't break CleanArchitecture.Application.Interfaces.UserInterfaces.
- Position
- Below the diagonal: CleanArchitecture.Application.Features.Accounts.Commands.Start uses a module listed above it, which is the healthy direction.
31→3 CleanArchitecture.Application.Interfaces.Repositories uses CleanArchitecture.Application.DTOs✕
- Connections
- 1 pair of types, where a type in CleanArchitecture.Application.Interfaces.Repositories uses a type in CleanArchitecture.Application.DTOs.
- The types involved
CleanArchitecture.Application.Interfaces.Repositories.IProductRepository→CleanArchitecture.Application.DTOs.PaginationResponseDto
- Direction
- CleanArchitecture.Application.Interfaces.Repositories uses CleanArchitecture.Application.DTOs, so a change to CleanArchitecture.Application.DTOs can break CleanArchitecture.Application.Interfaces.Repositories, while a change to CleanArchitecture.Application.Interfaces.Repositories can't break CleanArchitecture.Application.DTOs.
- Position
- Below the diagonal: CleanArchitecture.Application.Interfaces.Repositories uses a module listed above it, which is the healthy direction.
31→21 CleanArchitecture.Application.Interfaces.Repositories uses CleanArchitecture.Domain.Products.DTOs✕
- Connections
- 1 pair of types, where a type in CleanArchitecture.Application.Interfaces.Repositories uses a type in CleanArchitecture.Domain.Products.DTOs.
- The types involved
CleanArchitecture.Application.Interfaces.Repositories.IProductRepository→CleanArchitecture.Domain.Products.DTOs.ProductDto
- Direction
- CleanArchitecture.Application.Interfaces.Repositories uses CleanArchitecture.Domain.Products.DTOs, so a change to CleanArchitecture.Domain.Products.DTOs can break CleanArchitecture.Application.Interfaces.Repositories, while a change to CleanArchitecture.Application.Interfaces.Repositories can't break CleanArchitecture.Domain.Products.DTOs.
- Position
- Below the diagonal: CleanArchitecture.Application.Interfaces.Repositories uses a module listed above it, which is the healthy direction.
32→4 CleanArchitecture.Infrastructure.Identity.Services uses CleanArchitecture.Application.DTOs.Account.Responses✕
- Connections
- 2 pairs of types, where a type in CleanArchitecture.Infrastructure.Identity.Services uses a type in CleanArchitecture.Application.DTOs.Account.Responses.
- The types involved
CleanArchitecture.Infrastructure.Identity.Services.AccountServices→CleanArchitecture.Application.DTOs.Account.Responses.AuthenticationResponseCleanArchitecture.Infrastructure.Identity.Services.GetUserServices→CleanArchitecture.Application.DTOs.Account.Responses.UserDto
- Direction
- CleanArchitecture.Infrastructure.Identity.Services uses CleanArchitecture.Application.DTOs.Account.Responses, so a change to CleanArchitecture.Application.DTOs.Account.Responses can break CleanArchitecture.Infrastructure.Identity.Services, while a change to CleanArchitecture.Infrastructure.Identity.Services can't break CleanArchitecture.Application.DTOs.Account.Responses.
- Position
- Below the diagonal: CleanArchitecture.Infrastructure.Identity.Services uses a module listed above it, which is the healthy direction.
32→8 CleanArchitecture.Infrastructure.Identity.Services uses CleanArchitecture.Infrastructure.Identity.Contexts✕
- Connections
- 1 pair of types, where a type in CleanArchitecture.Infrastructure.Identity.Services uses a type in CleanArchitecture.Infrastructure.Identity.Contexts.
- The types involved
CleanArchitecture.Infrastructure.Identity.Services.GetUserServices→CleanArchitecture.Infrastructure.Identity.Contexts.IdentityContext
- Direction
- CleanArchitecture.Infrastructure.Identity.Services uses CleanArchitecture.Infrastructure.Identity.Contexts, so a change to CleanArchitecture.Infrastructure.Identity.Contexts can break CleanArchitecture.Infrastructure.Identity.Services, while a change to CleanArchitecture.Infrastructure.Identity.Services can't break CleanArchitecture.Infrastructure.Identity.Contexts.
- Position
- Below the diagonal: CleanArchitecture.Infrastructure.Identity.Services uses a module listed above it, which is the healthy direction.
32→9 CleanArchitecture.Infrastructure.Identity.Services uses CleanArchitecture.Infrastructure.Identity.Models✕
- Connections
- 1 pair of types, where a type in CleanArchitecture.Infrastructure.Identity.Services uses a type in CleanArchitecture.Infrastructure.Identity.Models.
- The types involved
CleanArchitecture.Infrastructure.Identity.Services.AccountServices→CleanArchitecture.Infrastructure.Identity.Models.ApplicationUser
- Direction
- CleanArchitecture.Infrastructure.Identity.Services uses CleanArchitecture.Infrastructure.Identity.Models, so a change to CleanArchitecture.Infrastructure.Identity.Models can break CleanArchitecture.Infrastructure.Identity.Services, while a change to CleanArchitecture.Infrastructure.Identity.Services can't break CleanArchitecture.Infrastructure.Identity.Models.
- Position
- Below the diagonal: CleanArchitecture.Infrastructure.Identity.Services uses a module listed above it, which is the healthy direction.
32→10 CleanArchitecture.Infrastructure.Identity.Services uses CleanArchitecture.Infrastructure.Identity.Settings✕
- Connections
- 1 pair of types, where a type in CleanArchitecture.Infrastructure.Identity.Services uses a type in CleanArchitecture.Infrastructure.Identity.Settings.
- The types involved
CleanArchitecture.Infrastructure.Identity.Services.AccountServices→CleanArchitecture.Infrastructure.Identity.Settings.JwtSettings
- Direction
- CleanArchitecture.Infrastructure.Identity.Services uses CleanArchitecture.Infrastructure.Identity.Settings, so a change to CleanArchitecture.Infrastructure.Identity.Settings can break CleanArchitecture.Infrastructure.Identity.Services, while a change to CleanArchitecture.Infrastructure.Identity.Services can't break CleanArchitecture.Infrastructure.Identity.Settings.
- Position
- Below the diagonal: CleanArchitecture.Infrastructure.Identity.Services uses a module listed above it, which is the healthy direction.
32→13 CleanArchitecture.Infrastructure.Identity.Services uses CleanArchitecture.Application.DTOs.Account.Requests✕
- Connections
- 4 pairs of types, where a type in CleanArchitecture.Infrastructure.Identity.Services uses a type in CleanArchitecture.Application.DTOs.Account.Requests.
- The types involved
CleanArchitecture.Infrastructure.Identity.Services.AccountServices→CleanArchitecture.Application.DTOs.Account.Requests.AuthenticationRequestCleanArchitecture.Infrastructure.Identity.Services.AccountServices→CleanArchitecture.Application.DTOs.Account.Requests.ChangePasswordRequestCleanArchitecture.Infrastructure.Identity.Services.AccountServices→CleanArchitecture.Application.DTOs.Account.Requests.ChangeUserNameRequestCleanArchitecture.Infrastructure.Identity.Services.GetUserServices→CleanArchitecture.Application.DTOs.Account.Requests.GetAllUsersRequest
- Direction
- CleanArchitecture.Infrastructure.Identity.Services uses CleanArchitecture.Application.DTOs.Account.Requests, so a change to CleanArchitecture.Application.DTOs.Account.Requests can break CleanArchitecture.Infrastructure.Identity.Services, while a change to CleanArchitecture.Infrastructure.Identity.Services can't break CleanArchitecture.Application.DTOs.Account.Requests.
- Position
- Below the diagonal: CleanArchitecture.Infrastructure.Identity.Services uses a module listed above it, which is the healthy direction.
32→15 CleanArchitecture.Infrastructure.Identity.Services uses CleanArchitecture.Application.Interfaces✕
- Connections
- 2 pairs of types, where a type in CleanArchitecture.Infrastructure.Identity.Services uses a type in CleanArchitecture.Application.Interfaces.
- The types involved
CleanArchitecture.Infrastructure.Identity.Services.AccountServices→CleanArchitecture.Application.Interfaces.IAuthenticatedUserServiceCleanArchitecture.Infrastructure.Identity.Services.AccountServices→CleanArchitecture.Application.Interfaces.ITranslator
- Direction
- CleanArchitecture.Infrastructure.Identity.Services uses CleanArchitecture.Application.Interfaces, so a change to CleanArchitecture.Application.Interfaces can break CleanArchitecture.Infrastructure.Identity.Services, while a change to CleanArchitecture.Infrastructure.Identity.Services can't break CleanArchitecture.Application.Interfaces.
- Position
- Below the diagonal: CleanArchitecture.Infrastructure.Identity.Services uses a module listed above it, which is the healthy direction.
32→16 CleanArchitecture.Infrastructure.Identity.Services uses CleanArchitecture.Application.Wrappers✕
- Connections
- 2 pairs of types, where a type in CleanArchitecture.Infrastructure.Identity.Services uses a type in CleanArchitecture.Application.Wrappers.
- The types involved
CleanArchitecture.Infrastructure.Identity.Services.AccountServices→CleanArchitecture.Application.Wrappers.BaseResultCleanArchitecture.Infrastructure.Identity.Services.GetUserServices→CleanArchitecture.Application.Wrappers.PagedResponse
- Direction
- CleanArchitecture.Infrastructure.Identity.Services uses CleanArchitecture.Application.Wrappers, so a change to CleanArchitecture.Application.Wrappers can break CleanArchitecture.Infrastructure.Identity.Services, while a change to CleanArchitecture.Infrastructure.Identity.Services can't break CleanArchitecture.Application.Wrappers.
- Position
- Below the diagonal: CleanArchitecture.Infrastructure.Identity.Services uses a module listed above it, which is the healthy direction.
32→20 CleanArchitecture.Infrastructure.Identity.Services uses CleanArchitecture.Application.Interfaces.UserInterfaces✕
- Connections
- 2 pairs of types, where a type in CleanArchitecture.Infrastructure.Identity.Services uses a type in CleanArchitecture.Application.Interfaces.UserInterfaces.
- The types involved
CleanArchitecture.Infrastructure.Identity.Services.AccountServices→CleanArchitecture.Application.Interfaces.UserInterfaces.IAccountServicesCleanArchitecture.Infrastructure.Identity.Services.GetUserServices→CleanArchitecture.Application.Interfaces.UserInterfaces.IGetUserServices
- Direction
- CleanArchitecture.Infrastructure.Identity.Services uses CleanArchitecture.Application.Interfaces.UserInterfaces, so a change to CleanArchitecture.Application.Interfaces.UserInterfaces can break CleanArchitecture.Infrastructure.Identity.Services, while a change to CleanArchitecture.Infrastructure.Identity.Services can't break CleanArchitecture.Application.Interfaces.UserInterfaces.
- Position
- Below the diagonal: CleanArchitecture.Infrastructure.Identity.Services uses a module listed above it, which is the healthy direction.
33→22 CleanArchitecture.Infrastructure.Persistence.Seeds uses CleanArchitecture.Infrastructure.Persistence.Contexts✕
- Connections
- 1 pair of types, where a type in CleanArchitecture.Infrastructure.Persistence.Seeds uses a type in CleanArchitecture.Infrastructure.Persistence.Contexts.
- The types involved
CleanArchitecture.Infrastructure.Persistence.Seeds.DefaultData→CleanArchitecture.Infrastructure.Persistence.Contexts.ApplicationDbContext
- Direction
- CleanArchitecture.Infrastructure.Persistence.Seeds uses CleanArchitecture.Infrastructure.Persistence.Contexts, so a change to CleanArchitecture.Infrastructure.Persistence.Contexts can break CleanArchitecture.Infrastructure.Persistence.Seeds, while a change to CleanArchitecture.Infrastructure.Persistence.Seeds can't break CleanArchitecture.Infrastructure.Persistence.Contexts.
- Position
- Below the diagonal: CleanArchitecture.Infrastructure.Persistence.Seeds uses a module listed above it, which is the healthy direction.
34→15 CleanArchitecture.Application.Features.Products.Commands.CreateProduct uses CleanArchitecture.Application.Interfaces✕
- Connections
- 4 pairs of types, where a type in CleanArchitecture.Application.Features.Products.Commands.CreateProduct uses a type in CleanArchitecture.Application.Interfaces.
- The types involved
CleanArchitecture.Application.Features.Products.Commands.CreateProduct.CreateProductCommand→CleanArchitecture.Application.Interfaces.IRequestCleanArchitecture.Application.Features.Products.Commands.CreateProduct.CreateProductCommandHandler→CleanArchitecture.Application.Interfaces.IRequestHandlerCleanArchitecture.Application.Features.Products.Commands.CreateProduct.CreateProductCommandHandler→CleanArchitecture.Application.Interfaces.IUnitOfWorkCleanArchitecture.Application.Features.Products.Commands.CreateProduct.CreateProductCommandValidator→CleanArchitecture.Application.Interfaces.ITranslator
- Direction
- CleanArchitecture.Application.Features.Products.Commands.CreateProduct uses CleanArchitecture.Application.Interfaces, so a change to CleanArchitecture.Application.Interfaces can break CleanArchitecture.Application.Features.Products.Commands.CreateProduct, while a change to CleanArchitecture.Application.Features.Products.Commands.CreateProduct can't break CleanArchitecture.Application.Interfaces.
- Position
- Below the diagonal: CleanArchitecture.Application.Features.Products.Commands.CreateProduct uses a module listed above it, which is the healthy direction.
34→16 CleanArchitecture.Application.Features.Products.Commands.CreateProduct uses CleanArchitecture.Application.Wrappers✕
- Connections
- 1 pair of types, where a type in CleanArchitecture.Application.Features.Products.Commands.CreateProduct uses a type in CleanArchitecture.Application.Wrappers.
- The types involved
CleanArchitecture.Application.Features.Products.Commands.CreateProduct.CreateProductCommandHandler→CleanArchitecture.Application.Wrappers.BaseResult
- Direction
- CleanArchitecture.Application.Features.Products.Commands.CreateProduct uses CleanArchitecture.Application.Wrappers, so a change to CleanArchitecture.Application.Wrappers can break CleanArchitecture.Application.Features.Products.Commands.CreateProduct, while a change to CleanArchitecture.Application.Features.Products.Commands.CreateProduct can't break CleanArchitecture.Application.Wrappers.
- Position
- Below the diagonal: CleanArchitecture.Application.Features.Products.Commands.CreateProduct uses a module listed above it, which is the healthy direction.
34→31 CleanArchitecture.Application.Features.Products.Commands.CreateProduct uses CleanArchitecture.Application.Interfaces.Repositories✕
- Connections
- 1 pair of types, where a type in CleanArchitecture.Application.Features.Products.Commands.CreateProduct uses a type in CleanArchitecture.Application.Interfaces.Repositories.
- The types involved
CleanArchitecture.Application.Features.Products.Commands.CreateProduct.CreateProductCommandHandler→CleanArchitecture.Application.Interfaces.Repositories.IProductRepository
- Direction
- CleanArchitecture.Application.Features.Products.Commands.CreateProduct uses CleanArchitecture.Application.Interfaces.Repositories, so a change to CleanArchitecture.Application.Interfaces.Repositories can break CleanArchitecture.Application.Features.Products.Commands.CreateProduct, while a change to CleanArchitecture.Application.Features.Products.Commands.CreateProduct can't break CleanArchitecture.Application.Interfaces.Repositories.
- Position
- Below the diagonal: CleanArchitecture.Application.Features.Products.Commands.CreateProduct uses a module listed above it, which is the healthy direction.
35→15 CleanArchitecture.Application.Features.Products.Commands.DeleteProduct uses CleanArchitecture.Application.Interfaces✕
- Connections
- 4 pairs of types, where a type in CleanArchitecture.Application.Features.Products.Commands.DeleteProduct uses a type in CleanArchitecture.Application.Interfaces.
- The types involved
CleanArchitecture.Application.Features.Products.Commands.DeleteProduct.DeleteProductCommand→CleanArchitecture.Application.Interfaces.IRequestCleanArchitecture.Application.Features.Products.Commands.DeleteProduct.DeleteProductCommandHandler→CleanArchitecture.Application.Interfaces.IRequestHandlerCleanArchitecture.Application.Features.Products.Commands.DeleteProduct.DeleteProductCommandHandler→CleanArchitecture.Application.Interfaces.ITranslatorCleanArchitecture.Application.Features.Products.Commands.DeleteProduct.DeleteProductCommandHandler→CleanArchitecture.Application.Interfaces.IUnitOfWork
- Direction
- CleanArchitecture.Application.Features.Products.Commands.DeleteProduct uses CleanArchitecture.Application.Interfaces, so a change to CleanArchitecture.Application.Interfaces can break CleanArchitecture.Application.Features.Products.Commands.DeleteProduct, while a change to CleanArchitecture.Application.Features.Products.Commands.DeleteProduct can't break CleanArchitecture.Application.Interfaces.
- Position
- Below the diagonal: CleanArchitecture.Application.Features.Products.Commands.DeleteProduct uses a module listed above it, which is the healthy direction.
35→16 CleanArchitecture.Application.Features.Products.Commands.DeleteProduct uses CleanArchitecture.Application.Wrappers✕
- Connections
- 1 pair of types, where a type in CleanArchitecture.Application.Features.Products.Commands.DeleteProduct uses a type in CleanArchitecture.Application.Wrappers.
- The types involved
CleanArchitecture.Application.Features.Products.Commands.DeleteProduct.DeleteProductCommandHandler→CleanArchitecture.Application.Wrappers.BaseResult
- Direction
- CleanArchitecture.Application.Features.Products.Commands.DeleteProduct uses CleanArchitecture.Application.Wrappers, so a change to CleanArchitecture.Application.Wrappers can break CleanArchitecture.Application.Features.Products.Commands.DeleteProduct, while a change to CleanArchitecture.Application.Features.Products.Commands.DeleteProduct can't break CleanArchitecture.Application.Wrappers.
- Position
- Below the diagonal: CleanArchitecture.Application.Features.Products.Commands.DeleteProduct uses a module listed above it, which is the healthy direction.
35→31 CleanArchitecture.Application.Features.Products.Commands.DeleteProduct uses CleanArchitecture.Application.Interfaces.Repositories✕
- Connections
- 1 pair of types, where a type in CleanArchitecture.Application.Features.Products.Commands.DeleteProduct uses a type in CleanArchitecture.Application.Interfaces.Repositories.
- The types involved
CleanArchitecture.Application.Features.Products.Commands.DeleteProduct.DeleteProductCommandHandler→CleanArchitecture.Application.Interfaces.Repositories.IProductRepository
- Direction
- CleanArchitecture.Application.Features.Products.Commands.DeleteProduct uses CleanArchitecture.Application.Interfaces.Repositories, so a change to CleanArchitecture.Application.Interfaces.Repositories can break CleanArchitecture.Application.Features.Products.Commands.DeleteProduct, while a change to CleanArchitecture.Application.Features.Products.Commands.DeleteProduct can't break CleanArchitecture.Application.Interfaces.Repositories.
- Position
- Below the diagonal: CleanArchitecture.Application.Features.Products.Commands.DeleteProduct uses a module listed above it, which is the healthy direction.
36→15 CleanArchitecture.Application.Features.Products.Commands.UpdateProduct uses CleanArchitecture.Application.Interfaces✕
- Connections
- 5 pairs of types, where a type in CleanArchitecture.Application.Features.Products.Commands.UpdateProduct uses a type in CleanArchitecture.Application.Interfaces.
- The types involved
CleanArchitecture.Application.Features.Products.Commands.UpdateProduct.UpdateProductCommand→CleanArchitecture.Application.Interfaces.IRequestCleanArchitecture.Application.Features.Products.Commands.UpdateProduct.UpdateProductCommandHandler→CleanArchitecture.Application.Interfaces.IRequestHandlerCleanArchitecture.Application.Features.Products.Commands.UpdateProduct.UpdateProductCommandHandler→CleanArchitecture.Application.Interfaces.ITranslatorCleanArchitecture.Application.Features.Products.Commands.UpdateProduct.UpdateProductCommandHandler→CleanArchitecture.Application.Interfaces.IUnitOfWorkCleanArchitecture.Application.Features.Products.Commands.UpdateProduct.UpdateProductCommandValidator→CleanArchitecture.Application.Interfaces.ITranslator
- Direction
- CleanArchitecture.Application.Features.Products.Commands.UpdateProduct uses CleanArchitecture.Application.Interfaces, so a change to CleanArchitecture.Application.Interfaces can break CleanArchitecture.Application.Features.Products.Commands.UpdateProduct, while a change to CleanArchitecture.Application.Features.Products.Commands.UpdateProduct can't break CleanArchitecture.Application.Interfaces.
- Position
- Below the diagonal: CleanArchitecture.Application.Features.Products.Commands.UpdateProduct uses a module listed above it, which is the healthy direction.
36→16 CleanArchitecture.Application.Features.Products.Commands.UpdateProduct uses CleanArchitecture.Application.Wrappers✕
- Connections
- 1 pair of types, where a type in CleanArchitecture.Application.Features.Products.Commands.UpdateProduct uses a type in CleanArchitecture.Application.Wrappers.
- The types involved
CleanArchitecture.Application.Features.Products.Commands.UpdateProduct.UpdateProductCommandHandler→CleanArchitecture.Application.Wrappers.BaseResult
- Direction
- CleanArchitecture.Application.Features.Products.Commands.UpdateProduct uses CleanArchitecture.Application.Wrappers, so a change to CleanArchitecture.Application.Wrappers can break CleanArchitecture.Application.Features.Products.Commands.UpdateProduct, while a change to CleanArchitecture.Application.Features.Products.Commands.UpdateProduct can't break CleanArchitecture.Application.Wrappers.
- Position
- Below the diagonal: CleanArchitecture.Application.Features.Products.Commands.UpdateProduct uses a module listed above it, which is the healthy direction.
36→31 CleanArchitecture.Application.Features.Products.Commands.UpdateProduct uses CleanArchitecture.Application.Interfaces.Repositories✕
- Connections
- 1 pair of types, where a type in CleanArchitecture.Application.Features.Products.Commands.UpdateProduct uses a type in CleanArchitecture.Application.Interfaces.Repositories.
- The types involved
CleanArchitecture.Application.Features.Products.Commands.UpdateProduct.UpdateProductCommandHandler→CleanArchitecture.Application.Interfaces.Repositories.IProductRepository
- Direction
- CleanArchitecture.Application.Features.Products.Commands.UpdateProduct uses CleanArchitecture.Application.Interfaces.Repositories, so a change to CleanArchitecture.Application.Interfaces.Repositories can break CleanArchitecture.Application.Features.Products.Commands.UpdateProduct, while a change to CleanArchitecture.Application.Features.Products.Commands.UpdateProduct can't break CleanArchitecture.Application.Interfaces.Repositories.
- Position
- Below the diagonal: CleanArchitecture.Application.Features.Products.Commands.UpdateProduct uses a module listed above it, which is the healthy direction.
37→5 CleanArchitecture.Application.Features.Products.Queries.GetPagedListProduct uses CleanArchitecture.Application.Parameters✕
- Connections
- 1 pair of types, where a type in CleanArchitecture.Application.Features.Products.Queries.GetPagedListProduct uses a type in CleanArchitecture.Application.Parameters.
- The types involved
CleanArchitecture.Application.Features.Products.Queries.GetPagedListProduct.GetPagedListProductQuery→CleanArchitecture.Application.Parameters.PaginationRequestParameter
- Direction
- CleanArchitecture.Application.Features.Products.Queries.GetPagedListProduct uses CleanArchitecture.Application.Parameters, so a change to CleanArchitecture.Application.Parameters can break CleanArchitecture.Application.Features.Products.Queries.GetPagedListProduct, while a change to CleanArchitecture.Application.Features.Products.Queries.GetPagedListProduct can't break CleanArchitecture.Application.Parameters.
- Position
- Below the diagonal: CleanArchitecture.Application.Features.Products.Queries.GetPagedListProduct uses a module listed above it, which is the healthy direction.
37→15 CleanArchitecture.Application.Features.Products.Queries.GetPagedListProduct uses CleanArchitecture.Application.Interfaces✕
- Connections
- 2 pairs of types, where a type in CleanArchitecture.Application.Features.Products.Queries.GetPagedListProduct uses a type in CleanArchitecture.Application.Interfaces.
- The types involved
CleanArchitecture.Application.Features.Products.Queries.GetPagedListProduct.GetPagedListProductQuery→CleanArchitecture.Application.Interfaces.IRequestCleanArchitecture.Application.Features.Products.Queries.GetPagedListProduct.GetPagedListProductQueryHandler→CleanArchitecture.Application.Interfaces.IRequestHandler
- Direction
- CleanArchitecture.Application.Features.Products.Queries.GetPagedListProduct uses CleanArchitecture.Application.Interfaces, so a change to CleanArchitecture.Application.Interfaces can break CleanArchitecture.Application.Features.Products.Queries.GetPagedListProduct, while a change to CleanArchitecture.Application.Features.Products.Queries.GetPagedListProduct can't break CleanArchitecture.Application.Interfaces.
- Position
- Below the diagonal: CleanArchitecture.Application.Features.Products.Queries.GetPagedListProduct uses a module listed above it, which is the healthy direction.
37→16 CleanArchitecture.Application.Features.Products.Queries.GetPagedListProduct uses CleanArchitecture.Application.Wrappers✕
- Connections
- 1 pair of types, where a type in CleanArchitecture.Application.Features.Products.Queries.GetPagedListProduct uses a type in CleanArchitecture.Application.Wrappers.
- The types involved
CleanArchitecture.Application.Features.Products.Queries.GetPagedListProduct.GetPagedListProductQueryHandler→CleanArchitecture.Application.Wrappers.PagedResponse
- Direction
- CleanArchitecture.Application.Features.Products.Queries.GetPagedListProduct uses CleanArchitecture.Application.Wrappers, so a change to CleanArchitecture.Application.Wrappers can break CleanArchitecture.Application.Features.Products.Queries.GetPagedListProduct, while a change to CleanArchitecture.Application.Features.Products.Queries.GetPagedListProduct can't break CleanArchitecture.Application.Wrappers.
- Position
- Below the diagonal: CleanArchitecture.Application.Features.Products.Queries.GetPagedListProduct uses a module listed above it, which is the healthy direction.
37→21 CleanArchitecture.Application.Features.Products.Queries.GetPagedListProduct uses CleanArchitecture.Domain.Products.DTOs✕
- Connections
- 1 pair of types, where a type in CleanArchitecture.Application.Features.Products.Queries.GetPagedListProduct uses a type in CleanArchitecture.Domain.Products.DTOs.
- The types involved
CleanArchitecture.Application.Features.Products.Queries.GetPagedListProduct.GetPagedListProductQueryHandler→CleanArchitecture.Domain.Products.DTOs.ProductDto
- Direction
- CleanArchitecture.Application.Features.Products.Queries.GetPagedListProduct uses CleanArchitecture.Domain.Products.DTOs, so a change to CleanArchitecture.Domain.Products.DTOs can break CleanArchitecture.Application.Features.Products.Queries.GetPagedListProduct, while a change to CleanArchitecture.Application.Features.Products.Queries.GetPagedListProduct can't break CleanArchitecture.Domain.Products.DTOs.
- Position
- Below the diagonal: CleanArchitecture.Application.Features.Products.Queries.GetPagedListProduct uses a module listed above it, which is the healthy direction.
37→31 CleanArchitecture.Application.Features.Products.Queries.GetPagedListProduct uses CleanArchitecture.Application.Interfaces.Repositories✕
- Connections
- 1 pair of types, where a type in CleanArchitecture.Application.Features.Products.Queries.GetPagedListProduct uses a type in CleanArchitecture.Application.Interfaces.Repositories.
- The types involved
CleanArchitecture.Application.Features.Products.Queries.GetPagedListProduct.GetPagedListProductQueryHandler→CleanArchitecture.Application.Interfaces.Repositories.IProductRepository
- Direction
- CleanArchitecture.Application.Features.Products.Queries.GetPagedListProduct uses CleanArchitecture.Application.Interfaces.Repositories, so a change to CleanArchitecture.Application.Interfaces.Repositories can break CleanArchitecture.Application.Features.Products.Queries.GetPagedListProduct, while a change to CleanArchitecture.Application.Features.Products.Queries.GetPagedListProduct can't break CleanArchitecture.Application.Interfaces.Repositories.
- Position
- Below the diagonal: CleanArchitecture.Application.Features.Products.Queries.GetPagedListProduct uses a module listed above it, which is the healthy direction.
38→15 CleanArchitecture.Application.Features.Products.Queries.GetProductById uses CleanArchitecture.Application.Interfaces✕
- Connections
- 3 pairs of types, where a type in CleanArchitecture.Application.Features.Products.Queries.GetProductById uses a type in CleanArchitecture.Application.Interfaces.
- The types involved
CleanArchitecture.Application.Features.Products.Queries.GetProductById.GetProductByIdQuery→CleanArchitecture.Application.Interfaces.IRequestCleanArchitecture.Application.Features.Products.Queries.GetProductById.GetProductByIdQueryHandler→CleanArchitecture.Application.Interfaces.IRequestHandlerCleanArchitecture.Application.Features.Products.Queries.GetProductById.GetProductByIdQueryHandler→CleanArchitecture.Application.Interfaces.ITranslator
- Direction
- CleanArchitecture.Application.Features.Products.Queries.GetProductById uses CleanArchitecture.Application.Interfaces, so a change to CleanArchitecture.Application.Interfaces can break CleanArchitecture.Application.Features.Products.Queries.GetProductById, while a change to CleanArchitecture.Application.Features.Products.Queries.GetProductById can't break CleanArchitecture.Application.Interfaces.
- Position
- Below the diagonal: CleanArchitecture.Application.Features.Products.Queries.GetProductById uses a module listed above it, which is the healthy direction.
38→16 CleanArchitecture.Application.Features.Products.Queries.GetProductById uses CleanArchitecture.Application.Wrappers✕
- Connections
- 1 pair of types, where a type in CleanArchitecture.Application.Features.Products.Queries.GetProductById uses a type in CleanArchitecture.Application.Wrappers.
- The types involved
CleanArchitecture.Application.Features.Products.Queries.GetProductById.GetProductByIdQueryHandler→CleanArchitecture.Application.Wrappers.BaseResult
- Direction
- CleanArchitecture.Application.Features.Products.Queries.GetProductById uses CleanArchitecture.Application.Wrappers, so a change to CleanArchitecture.Application.Wrappers can break CleanArchitecture.Application.Features.Products.Queries.GetProductById, while a change to CleanArchitecture.Application.Features.Products.Queries.GetProductById can't break CleanArchitecture.Application.Wrappers.
- Position
- Below the diagonal: CleanArchitecture.Application.Features.Products.Queries.GetProductById uses a module listed above it, which is the healthy direction.
38→21 CleanArchitecture.Application.Features.Products.Queries.GetProductById uses CleanArchitecture.Domain.Products.DTOs✕
- Connections
- 1 pair of types, where a type in CleanArchitecture.Application.Features.Products.Queries.GetProductById uses a type in CleanArchitecture.Domain.Products.DTOs.
- The types involved
CleanArchitecture.Application.Features.Products.Queries.GetProductById.GetProductByIdQueryHandler→CleanArchitecture.Domain.Products.DTOs.ProductDto
- Direction
- CleanArchitecture.Application.Features.Products.Queries.GetProductById uses CleanArchitecture.Domain.Products.DTOs, so a change to CleanArchitecture.Domain.Products.DTOs can break CleanArchitecture.Application.Features.Products.Queries.GetProductById, while a change to CleanArchitecture.Application.Features.Products.Queries.GetProductById can't break CleanArchitecture.Domain.Products.DTOs.
- Position
- Below the diagonal: CleanArchitecture.Application.Features.Products.Queries.GetProductById uses a module listed above it, which is the healthy direction.
38→31 CleanArchitecture.Application.Features.Products.Queries.GetProductById uses CleanArchitecture.Application.Interfaces.Repositories✕
- Connections
- 1 pair of types, where a type in CleanArchitecture.Application.Features.Products.Queries.GetProductById uses a type in CleanArchitecture.Application.Interfaces.Repositories.
- The types involved
CleanArchitecture.Application.Features.Products.Queries.GetProductById.GetProductByIdQueryHandler→CleanArchitecture.Application.Interfaces.Repositories.IProductRepository
- Direction
- CleanArchitecture.Application.Features.Products.Queries.GetProductById uses CleanArchitecture.Application.Interfaces.Repositories, so a change to CleanArchitecture.Application.Interfaces.Repositories can break CleanArchitecture.Application.Features.Products.Queries.GetProductById, while a change to CleanArchitecture.Application.Features.Products.Queries.GetProductById can't break CleanArchitecture.Application.Interfaces.Repositories.
- Position
- Below the diagonal: CleanArchitecture.Application.Features.Products.Queries.GetProductById uses a module listed above it, which is the healthy direction.
39→3 CleanArchitecture.Infrastructure.Persistence.Repositories uses CleanArchitecture.Application.DTOs✕
- Connections
- 2 pairs of types, where a type in CleanArchitecture.Infrastructure.Persistence.Repositories uses a type in CleanArchitecture.Application.DTOs.
- The types involved
CleanArchitecture.Infrastructure.Persistence.Repositories.GenericRepository→CleanArchitecture.Application.DTOs.PaginationResponseDtoCleanArchitecture.Infrastructure.Persistence.Repositories.ProductRepository→CleanArchitecture.Application.DTOs.PaginationResponseDto
- Direction
- CleanArchitecture.Infrastructure.Persistence.Repositories uses CleanArchitecture.Application.DTOs, so a change to CleanArchitecture.Application.DTOs can break CleanArchitecture.Infrastructure.Persistence.Repositories, while a change to CleanArchitecture.Infrastructure.Persistence.Repositories can't break CleanArchitecture.Application.DTOs.
- Position
- Below the diagonal: CleanArchitecture.Infrastructure.Persistence.Repositories uses a module listed above it, which is the healthy direction.
39→21 CleanArchitecture.Infrastructure.Persistence.Repositories uses CleanArchitecture.Domain.Products.DTOs✕
- Connections
- 1 pair of types, where a type in CleanArchitecture.Infrastructure.Persistence.Repositories uses a type in CleanArchitecture.Domain.Products.DTOs.
- The types involved
CleanArchitecture.Infrastructure.Persistence.Repositories.ProductRepository→CleanArchitecture.Domain.Products.DTOs.ProductDto
- Direction
- CleanArchitecture.Infrastructure.Persistence.Repositories uses CleanArchitecture.Domain.Products.DTOs, so a change to CleanArchitecture.Domain.Products.DTOs can break CleanArchitecture.Infrastructure.Persistence.Repositories, while a change to CleanArchitecture.Infrastructure.Persistence.Repositories can't break CleanArchitecture.Domain.Products.DTOs.
- Position
- Below the diagonal: CleanArchitecture.Infrastructure.Persistence.Repositories uses a module listed above it, which is the healthy direction.
39→22 CleanArchitecture.Infrastructure.Persistence.Repositories uses CleanArchitecture.Infrastructure.Persistence.Contexts✕
- Connections
- 1 pair of types, where a type in CleanArchitecture.Infrastructure.Persistence.Repositories uses a type in CleanArchitecture.Infrastructure.Persistence.Contexts.
- The types involved
CleanArchitecture.Infrastructure.Persistence.Repositories.ProductRepository→CleanArchitecture.Infrastructure.Persistence.Contexts.ApplicationDbContext
- Direction
- CleanArchitecture.Infrastructure.Persistence.Repositories uses CleanArchitecture.Infrastructure.Persistence.Contexts, so a change to CleanArchitecture.Infrastructure.Persistence.Contexts can break CleanArchitecture.Infrastructure.Persistence.Repositories, while a change to CleanArchitecture.Infrastructure.Persistence.Repositories can't break CleanArchitecture.Infrastructure.Persistence.Contexts.
- Position
- Below the diagonal: CleanArchitecture.Infrastructure.Persistence.Repositories uses a module listed above it, which is the healthy direction.
39→31 CleanArchitecture.Infrastructure.Persistence.Repositories uses CleanArchitecture.Application.Interfaces.Repositories✕
- Connections
- 2 pairs of types, where a type in CleanArchitecture.Infrastructure.Persistence.Repositories uses a type in CleanArchitecture.Application.Interfaces.Repositories.
- The types involved
CleanArchitecture.Infrastructure.Persistence.Repositories.GenericRepository→CleanArchitecture.Application.Interfaces.Repositories.IGenericRepositoryCleanArchitecture.Infrastructure.Persistence.Repositories.ProductRepository→CleanArchitecture.Application.Interfaces.Repositories.IProductRepository
- Direction
- CleanArchitecture.Infrastructure.Persistence.Repositories uses CleanArchitecture.Application.Interfaces.Repositories, so a change to CleanArchitecture.Application.Interfaces.Repositories can break CleanArchitecture.Infrastructure.Persistence.Repositories, while a change to CleanArchitecture.Infrastructure.Persistence.Repositories can't break CleanArchitecture.Application.Interfaces.Repositories.
- Position
- Below the diagonal: CleanArchitecture.Infrastructure.Persistence.Repositories uses a module listed above it, which is the healthy direction.
40→4 CleanArchitecture.WebApi.Endpoints uses CleanArchitecture.Application.DTOs.Account.Responses✕
- Connections
- 1 pair of types, where a type in CleanArchitecture.WebApi.Endpoints uses a type in CleanArchitecture.Application.DTOs.Account.Responses.
- The types involved
CleanArchitecture.WebApi.Endpoints.AccountEndpoint→CleanArchitecture.Application.DTOs.Account.Responses.AuthenticationResponse
- Direction
- CleanArchitecture.WebApi.Endpoints uses CleanArchitecture.Application.DTOs.Account.Responses, so a change to CleanArchitecture.Application.DTOs.Account.Responses can break CleanArchitecture.WebApi.Endpoints, while a change to CleanArchitecture.WebApi.Endpoints can't break CleanArchitecture.Application.DTOs.Account.Responses.
- Position
- Below the diagonal: CleanArchitecture.WebApi.Endpoints uses a module listed above it, which is the healthy direction.
40→12 CleanArchitecture.WebApi.Endpoints uses CleanArchitecture.WebApi.Infrastructure.Extensions✕
- Connections
- 3 pairs of types, where a type in CleanArchitecture.WebApi.Endpoints uses a type in CleanArchitecture.WebApi.Infrastructure.Extensions.
- The types involved
CleanArchitecture.WebApi.Endpoints.AccountEndpoint→CleanArchitecture.WebApi.Infrastructure.Extensions.EndpointGroupBaseCleanArchitecture.WebApi.Endpoints.DocEndpoint→CleanArchitecture.WebApi.Infrastructure.Extensions.EndpointGroupBaseCleanArchitecture.WebApi.Endpoints.ProductEndpoint→CleanArchitecture.WebApi.Infrastructure.Extensions.EndpointGroupBase
- Direction
- CleanArchitecture.WebApi.Endpoints uses CleanArchitecture.WebApi.Infrastructure.Extensions, so a change to CleanArchitecture.WebApi.Infrastructure.Extensions can break CleanArchitecture.WebApi.Endpoints, while a change to CleanArchitecture.WebApi.Endpoints can't break CleanArchitecture.WebApi.Infrastructure.Extensions.
- Position
- Below the diagonal: CleanArchitecture.WebApi.Endpoints uses a module listed above it, which is the healthy direction.
40→15 CleanArchitecture.WebApi.Endpoints uses CleanArchitecture.Application.Interfaces✕
- Connections
- 2 pairs of types, where a type in CleanArchitecture.WebApi.Endpoints uses a type in CleanArchitecture.Application.Interfaces.
- The types involved
CleanArchitecture.WebApi.Endpoints.AccountEndpoint→CleanArchitecture.Application.Interfaces.IMediatorCleanArchitecture.WebApi.Endpoints.ProductEndpoint→CleanArchitecture.Application.Interfaces.IMediator
- Direction
- CleanArchitecture.WebApi.Endpoints uses CleanArchitecture.Application.Interfaces, so a change to CleanArchitecture.Application.Interfaces can break CleanArchitecture.WebApi.Endpoints, while a change to CleanArchitecture.WebApi.Endpoints can't break CleanArchitecture.Application.Interfaces.
- Position
- Below the diagonal: CleanArchitecture.WebApi.Endpoints uses a module listed above it, which is the healthy direction.
40→16 CleanArchitecture.WebApi.Endpoints uses CleanArchitecture.Application.Wrappers✕
- Connections
- 4 pairs of types, where a type in CleanArchitecture.WebApi.Endpoints uses a type in CleanArchitecture.Application.Wrappers.
- The types involved
CleanArchitecture.WebApi.Endpoints.AccountEndpoint→CleanArchitecture.Application.Wrappers.BaseResultCleanArchitecture.WebApi.Endpoints.DocEndpoint→CleanArchitecture.Application.Wrappers.BaseResultCleanArchitecture.WebApi.Endpoints.ProductEndpoint→CleanArchitecture.Application.Wrappers.BaseResultCleanArchitecture.WebApi.Endpoints.ProductEndpoint→CleanArchitecture.Application.Wrappers.PagedResponse
- Direction
- CleanArchitecture.WebApi.Endpoints uses CleanArchitecture.Application.Wrappers, so a change to CleanArchitecture.Application.Wrappers can break CleanArchitecture.WebApi.Endpoints, while a change to CleanArchitecture.WebApi.Endpoints can't break CleanArchitecture.Application.Wrappers.
- Position
- Below the diagonal: CleanArchitecture.WebApi.Endpoints uses a module listed above it, which is the healthy direction.
40→21 CleanArchitecture.WebApi.Endpoints uses CleanArchitecture.Domain.Products.DTOs✕
- Connections
- 1 pair of types, where a type in CleanArchitecture.WebApi.Endpoints uses a type in CleanArchitecture.Domain.Products.DTOs.
- The types involved
CleanArchitecture.WebApi.Endpoints.ProductEndpoint→CleanArchitecture.Domain.Products.DTOs.ProductDto
- Direction
- CleanArchitecture.WebApi.Endpoints uses CleanArchitecture.Domain.Products.DTOs, so a change to CleanArchitecture.Domain.Products.DTOs can break CleanArchitecture.WebApi.Endpoints, while a change to CleanArchitecture.WebApi.Endpoints can't break CleanArchitecture.Domain.Products.DTOs.
- Position
- Below the diagonal: CleanArchitecture.WebApi.Endpoints uses a module listed above it, which is the healthy direction.
40→27 CleanArchitecture.WebApi.Endpoints uses CleanArchitecture.Application.Features.Accounts.Commands.Authenticate✕
- Connections
- 1 pair of types, where a type in CleanArchitecture.WebApi.Endpoints uses a type in CleanArchitecture.Application.Features.Accounts.Commands.Authenticate.
- The types involved
CleanArchitecture.WebApi.Endpoints.AccountEndpoint→CleanArchitecture.Application.Features.Accounts.Commands.Authenticate.AuthenticateCommand
- Direction
- CleanArchitecture.WebApi.Endpoints uses CleanArchitecture.Application.Features.Accounts.Commands.Authenticate, so a change to CleanArchitecture.Application.Features.Accounts.Commands.Authenticate can break CleanArchitecture.WebApi.Endpoints, while a change to CleanArchitecture.WebApi.Endpoints can't break CleanArchitecture.Application.Features.Accounts.Commands.Authenticate.
- Position
- Below the diagonal: CleanArchitecture.WebApi.Endpoints uses a module listed above it, which is the healthy direction.
40→28 CleanArchitecture.WebApi.Endpoints uses CleanArchitecture.Application.Features.Accounts.Commands.ChangePassword✕
- Connections
- 1 pair of types, where a type in CleanArchitecture.WebApi.Endpoints uses a type in CleanArchitecture.Application.Features.Accounts.Commands.ChangePassword.
- The types involved
CleanArchitecture.WebApi.Endpoints.AccountEndpoint→CleanArchitecture.Application.Features.Accounts.Commands.ChangePassword.ChangePasswordCommand
- Direction
- CleanArchitecture.WebApi.Endpoints uses CleanArchitecture.Application.Features.Accounts.Commands.ChangePassword, so a change to CleanArchitecture.Application.Features.Accounts.Commands.ChangePassword can break CleanArchitecture.WebApi.Endpoints, while a change to CleanArchitecture.WebApi.Endpoints can't break CleanArchitecture.Application.Features.Accounts.Commands.ChangePassword.
- Position
- Below the diagonal: CleanArchitecture.WebApi.Endpoints uses a module listed above it, which is the healthy direction.
40→29 CleanArchitecture.WebApi.Endpoints uses CleanArchitecture.Application.Features.Accounts.Commands.ChangeUserName✕
- Connections
- 1 pair of types, where a type in CleanArchitecture.WebApi.Endpoints uses a type in CleanArchitecture.Application.Features.Accounts.Commands.ChangeUserName.
- The types involved
CleanArchitecture.WebApi.Endpoints.AccountEndpoint→CleanArchitecture.Application.Features.Accounts.Commands.ChangeUserName.ChangeUserNameCommand
- Direction
- CleanArchitecture.WebApi.Endpoints uses CleanArchitecture.Application.Features.Accounts.Commands.ChangeUserName, so a change to CleanArchitecture.Application.Features.Accounts.Commands.ChangeUserName can break CleanArchitecture.WebApi.Endpoints, while a change to CleanArchitecture.WebApi.Endpoints can't break CleanArchitecture.Application.Features.Accounts.Commands.ChangeUserName.
- Position
- Below the diagonal: CleanArchitecture.WebApi.Endpoints uses a module listed above it, which is the healthy direction.
40→34 CleanArchitecture.WebApi.Endpoints uses CleanArchitecture.Application.Features.Products.Commands.CreateProduct✕
- Connections
- 1 pair of types, where a type in CleanArchitecture.WebApi.Endpoints uses a type in CleanArchitecture.Application.Features.Products.Commands.CreateProduct.
- The types involved
CleanArchitecture.WebApi.Endpoints.ProductEndpoint→CleanArchitecture.Application.Features.Products.Commands.CreateProduct.CreateProductCommand
- Direction
- CleanArchitecture.WebApi.Endpoints uses CleanArchitecture.Application.Features.Products.Commands.CreateProduct, so a change to CleanArchitecture.Application.Features.Products.Commands.CreateProduct can break CleanArchitecture.WebApi.Endpoints, while a change to CleanArchitecture.WebApi.Endpoints can't break CleanArchitecture.Application.Features.Products.Commands.CreateProduct.
- Position
- Below the diagonal: CleanArchitecture.WebApi.Endpoints uses a module listed above it, which is the healthy direction.
40→35 CleanArchitecture.WebApi.Endpoints uses CleanArchitecture.Application.Features.Products.Commands.DeleteProduct✕
- Connections
- 1 pair of types, where a type in CleanArchitecture.WebApi.Endpoints uses a type in CleanArchitecture.Application.Features.Products.Commands.DeleteProduct.
- The types involved
CleanArchitecture.WebApi.Endpoints.ProductEndpoint→CleanArchitecture.Application.Features.Products.Commands.DeleteProduct.DeleteProductCommand
- Direction
- CleanArchitecture.WebApi.Endpoints uses CleanArchitecture.Application.Features.Products.Commands.DeleteProduct, so a change to CleanArchitecture.Application.Features.Products.Commands.DeleteProduct can break CleanArchitecture.WebApi.Endpoints, while a change to CleanArchitecture.WebApi.Endpoints can't break CleanArchitecture.Application.Features.Products.Commands.DeleteProduct.
- Position
- Below the diagonal: CleanArchitecture.WebApi.Endpoints uses a module listed above it, which is the healthy direction.
40→36 CleanArchitecture.WebApi.Endpoints uses CleanArchitecture.Application.Features.Products.Commands.UpdateProduct✕
- Connections
- 1 pair of types, where a type in CleanArchitecture.WebApi.Endpoints uses a type in CleanArchitecture.Application.Features.Products.Commands.UpdateProduct.
- The types involved
CleanArchitecture.WebApi.Endpoints.ProductEndpoint→CleanArchitecture.Application.Features.Products.Commands.UpdateProduct.UpdateProductCommand
- Direction
- CleanArchitecture.WebApi.Endpoints uses CleanArchitecture.Application.Features.Products.Commands.UpdateProduct, so a change to CleanArchitecture.Application.Features.Products.Commands.UpdateProduct can break CleanArchitecture.WebApi.Endpoints, while a change to CleanArchitecture.WebApi.Endpoints can't break CleanArchitecture.Application.Features.Products.Commands.UpdateProduct.
- Position
- Below the diagonal: CleanArchitecture.WebApi.Endpoints uses a module listed above it, which is the healthy direction.
40→37 CleanArchitecture.WebApi.Endpoints uses CleanArchitecture.Application.Features.Products.Queries.GetPagedListProduct✕
- Connections
- 1 pair of types, where a type in CleanArchitecture.WebApi.Endpoints uses a type in CleanArchitecture.Application.Features.Products.Queries.GetPagedListProduct.
- The types involved
CleanArchitecture.WebApi.Endpoints.ProductEndpoint→CleanArchitecture.Application.Features.Products.Queries.GetPagedListProduct.GetPagedListProductQuery
- Direction
- CleanArchitecture.WebApi.Endpoints uses CleanArchitecture.Application.Features.Products.Queries.GetPagedListProduct, so a change to CleanArchitecture.Application.Features.Products.Queries.GetPagedListProduct can break CleanArchitecture.WebApi.Endpoints, while a change to CleanArchitecture.WebApi.Endpoints can't break CleanArchitecture.Application.Features.Products.Queries.GetPagedListProduct.
- Position
- Below the diagonal: CleanArchitecture.WebApi.Endpoints uses a module listed above it, which is the healthy direction.
40→38 CleanArchitecture.WebApi.Endpoints uses CleanArchitecture.Application.Features.Products.Queries.GetProductById✕
- Connections
- 1 pair of types, where a type in CleanArchitecture.WebApi.Endpoints uses a type in CleanArchitecture.Application.Features.Products.Queries.GetProductById.
- The types involved
CleanArchitecture.WebApi.Endpoints.ProductEndpoint→CleanArchitecture.Application.Features.Products.Queries.GetProductById.GetProductByIdQuery
- Direction
- CleanArchitecture.WebApi.Endpoints uses CleanArchitecture.Application.Features.Products.Queries.GetProductById, so a change to CleanArchitecture.Application.Features.Products.Queries.GetProductById can break CleanArchitecture.WebApi.Endpoints, while a change to CleanArchitecture.WebApi.Endpoints can't break CleanArchitecture.Application.Features.Products.Queries.GetProductById.
- Position
- Below the diagonal: CleanArchitecture.WebApi.Endpoints uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
At a glance — Domain Modelling
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A05:2025 — Injection | 13 | High / Critical |
| A07:2025 — Authentication Failures | 3 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 1 | High / Critical |
| A02:2025 — Security Misconfiguration | 1 | High / Critical |
Roadmap
Top priorities: Resolve the 3 Leaked secret finding(s) in Secret Scanning — start with REDACTED, REDACTED, REDACTED; Codify backups + geo-recovery in IaC and document RTO/RPO and the restore procedure — a persistence guard alone is not disaster recovery; 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.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 3 Leaked secret finding(s) in Secret Scanning — start with REDACTED, REDACTED, REDACTED. | +8.2 pts | Low | Secret Scanning |
| Codify backups + geo-recovery in IaC and document RTO/RPO and the restore procedure — a persistence guard alone is not disaster recovery. | +6.4 pts | Medium | DR & Backup |
| Resolve the 8 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (3), REDACTED (3), REDACTED (2). | +2.1 pts | Low | Static Analysis (SAST) |
| 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. | +3.2 pts | Medium | Web-Security Posture |
| Resolve the 4 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (4). | +1.1 pts | Low | Static Analysis (SAST) |
| Add readiness/liveness probes and a rolling-update (or blue/green) strategy so a bad release is caught and rolled back automatically. | +1.7 pts | Medium | Deployment & Rollback |
| Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release. | +1.7 pts | Medium | Release Hygiene |
| Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. | +0.8 pts | Low | Static Analysis (SAST) |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 5.1 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.1 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.8 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 6.1 | Near-clean | Static Analysis (SAST): Medium: REDACTED |
| Source/Src/Core/CleanArchitecture.Domain/Products/Entities/Product.cs | 6.4 | Near-clean | Explicit Debt: FileScopedPragmaDisable |
| Source/Src/Infrastructure/CleanArchitecture.Infrastructure.Identity/Settings/JwtSettings.cs | 6.4 | Near-clean | Explicit Debt: FileScopedPragmaDisable |
| REDACTED | 7.2 | Near-clean | Secret Scanning: Leaked secret: REDACTED |
| REDACTED | 7.2 | Near-clean | Secret Scanning: Leaked secret: REDACTED |
| REDACTED | 7.2 | Near-clean | Secret Scanning: Leaked secret: REDACTED |
| REDACTED | 7.2 | Near-clean | Static Analysis (SAST): High: REDACTED |
| REDACTED | 7.2 | Near-clean | Dependency Vulnerabilities: High CVE: REDACTED |
| REDACTED | 7.2 | Near-clean | IaC & Container Security: High IaC: REDACTED |
| Source/Src/Core/CleanArchitecture.Domain/Products/DTOs/ProductDto.cs | 8.2 | Near-clean | Explicit Debt: BarePragmaDisable |
| Source/Src/Core/CleanArchitecture.Application/Interfaces/UserInterfaces/IGetUserServices.cs | 8.2 | Near-clean | Explicit Debt: Dead code: GetPagedUsers |
| Source/Src/Core/CleanArchitecture.Domain/Common/BaseEntity.cs | 8.2 | Near-clean | Explicit Debt: Dead code: BaseEntity |
| Source/Src/Core/CleanArchitecture.Application/Features/Products/Commands/CreateProduct/CreateProductCommandValidator.cs | 8.5 | Near-clean | Code Duplication: Duplicated block (10 lines × 2) |
How the grades work
A definite problem that already costs you something and drags the score down: a missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here tends to cause failures elsewhere.
Likely wrong, but not failing yet. It degrades the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to carry for two years either.
Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.
Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.
Methodology & how to trust this report
This survey is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. All 88 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 — 88 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, 60 of 74 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
- D8 Code Coverage — 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. Coverage NOT MEASURED: `--collect:"XPlat Code Coverage"` names a data collector that ships in the `coverlet.collector` package, and this repository wires up none — no test project references it and no runsettings declares one. The absence of coverage here is therefore not evidence about the suite or about our analyzer environment: without a collector, `--collect` produces nothing even from a suite that builds and passes. Add a `coverlet.collector` PackageReference to the test project(s) (or commit the Cobertura/OpenCover/lcov report your CI produces) and real coverage will be measured. It is excluded from the score rather than counted as a near-zero defect. You can widen what we reach: add the `coverlet.collector` package to the test projects to enable coverage (or commit the Cobertura/OpenCover/lcov report your CI produces).
- D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Single-contributor repository — bus factor is not applicable (1 contributor(s) across 652 commit(s) sampled, automation and bot accounts excluded). Concentration needs a team to concentrate: with one contributor there is nobody to spread the knowledge to, so there is nothing here for the owner to act on.
- D22 Internal API Consistency — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. The loaded project set declares no packable project and no `.Contracts` project, so there is no intentionally-exposed surface for API consistency to be judged over.
- D32 Data Compliance (PII/GDPR) — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `Source/Src/Core/CleanArchitecture.Application/Behaviours/ValidationBehavior.cs`, `Source/Src/Core/CleanArchitecture.Application/DTOs/PaginationResponseDto.cs`, `Source/Src/Core/CleanArchitecture.Application/DTOs/TranslatorMessageDto.cs`, `Source/Src/Core/CleanArchitecture.Application/Features/Accounts/Commands/Authenticate/AuthenticateCommandHandler.cs`, `Source/Src/Core/CleanArchitecture.Application/Features/Accounts/Commands/ChangePassword/ChangePasswordCommandHandler.cs`, … (+19 more) produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
- AXR1 Runtime accessibility — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via DockerCompose (REDACTED). compose up failed (exit 17 — an image could not be built) — cleanarchitecture.webapi Pulling cleanarchitecture.webapi Warning pull access denied for cleanarchitecturewebapi, repository does not exist or may require 'docker login': denied: requested access to the resource is denied failed to solve: failed to read dockerfile: open Dockerfile: no such file or directory; runtime evidence skipped.
- 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.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
- D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
- D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
- D11 Test Reliability: Flakiness is inferred from history/markers — we run the suite once (for coverage), not the repeated runs under varied conditions that reveal nondeterminism, so a flaky test never recorded as failing is invisible here.
- D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
- D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D18 Solution Shape: Build integrity reflects whether the solution compiled in this environment — a build that needs a private feed, a specific SDK, or a generated file absent from the repo can read as broken when it is merely unreproducible here.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
- D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- AX9 CQS / query purity: Handlers are found by interface/name convention — a query handler using neither is not seen. Mutation is a resolved write/publish invocation (SaveChanges/repository/bus), so a write hidden behind a hand-rolled wrapper, reflection, or a string-keyed service locator resolves to a non-persistence type and isn't flagged; it detects that a query writes state, not whether the write is a legitimate read-side cache update. Clean means "no resolved write/publish in a query body", not a proof of CQS purity.
- DM4 Rich vs anemic model: Behaviour is detected as state mutation inside a method body — a method that enforces an invariant by validating-and-throwing without mutating reads as a query, and mutation delegated through an interface the scan can't resolve isn't credited; entities with zero public properties still drop out of the population. It detects that state changes, not whether the rule is correct.
- DM6 Domain ↔ infrastructure boundary: Infrastructure reached through a hand-rolled wrapper, a domain-named facade, reflection, or a string-keyed service locator resolves to a non-infra type and isn't seen; the body scan is symbol resolution over syntax, not full dataflow. A clean result means "no resolved infra reference in a domain body", not a proof of purity.
- 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".
- P5 DR & Backup: Backup/restore and disaster-recovery readiness is judged from in-repo evidence — a config that exists is not a tested restore, so the absence of positive evidence is reported as "not evidenced", never scored as present.
- P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
Dimensions
D1 · Cyclomatic Complexity
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
1 duplicated block group(s) detected.
What to do
- Resolve the 1 Duplicated block (10 lines × 2) finding(s) in Code Duplication — start with CreateProductCommandValidator.cs. — One of this dimension's main actionable groups (1 warning-level).
- Enforce Code Duplication in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D5 · Coupling
10 projects, 0 dependency cycle(s), 0 unstable depended-on project(s).
D6 · Cohesion (LCOM4)
0 of 6 classes have LCOM4 above 3.
D9 · Test Distribution
28 test methods: 22 unit, 6 integration, 0 BDD, 0 e2e.
D10 · Test Quality
0 skipped, 0 zero-assertion, 1 mock references across 28 tests.
D11 · Test Reliability
0 flaky across 2 measured tier(s). unit: measured (0 flaky); integration: measured (0 flaky).
D12 · Dependency Hygiene
0 outdated, 0 vulnerable, 0 deprecated packages.
D13 · Secret Scanning
3 secret(s) detected.
What to do
- Resolve the 3 Leaked secret finding(s) in Secret Scanning — start with REDACTED, REDACTED, 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 251 packages use a banned license. ★ DEPTH: this repository's MSBuild projects declare 23 direct `PackageReference`(s), and 218 further package(s) were reached beyond them by closing the graph over nuget.org's own nuspec dependency graph — so a banned licence pulled in only by a dependency's OWN dependencies is inside this verdict. A package whose licence nuget.org could not be asked for is not graded, and version ranges are taken at their lower bound, so this is the closure as that graph states it rather than a restored consumer's exact resolution.
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window.
D17 · Explicit Debt
5 deducted debt markers + 2 dead symbols across 1728 LoC in the .NET projects (1.1/KLoC) → score 7.9.
What to do
- Resolve the 4 FileScopedPragmaDisable finding(s) in Explicit Debt — start with Product.cs (2), JwtSettings.cs (2). — One of this dimension's main actionable groups (4 issue-level).
- Resolve the 2 Dead code finding(s) in Explicit Debt — start with IGetUserServices.cs, BaseEntity.cs. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 BarePragmaDisable finding(s) in Explicit Debt — start with ProductDto.cs. — One of this dimension's main actionable groups (1 warning-level).
- Enforce Explicit Debt in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D18 · Solution Shape
9 projects, 103 source files, 2502 hand-written lines of code (1728 production / 774 test — the split is derived per file: test is what its project, its own path, or a compile-guarded region marks as test, and a file carrying no test signal counts as production), plus 925 generated (machine-written code — designer, scaffolded and tool-emitted files — excluded from quality), 13 inter-project edges.
D19 · Documentation Quality
1 of 1 documentation facets pass in full. 2 document(s) read across 1 unit(s).
D26 · Project Cohesion
0 of 10 projects flagged as possibly oversized/incoherent.
D27 · Navigability
97 % of calls cross a namespace and 6 % 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)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
13 finding(s): 0 critical, 9 high, 4 medium, 0 low. semgrep hit a parse error in 27 file(s) — `Source/Src/Core/CleanArchitecture.Application/Behaviours/ValidationBehavior.cs` (line 11), `Source/Src/Core/CleanArchitecture.Application/DTOs/PaginationResponseDto.cs` (line 5), `Source/Src/Core/CleanArchitecture.Application/DTOs/TranslatorMessageDto.cs` (line 3), `Source/Src/Core/CleanArchitecture.Application/Features/Accounts/Commands/Authenticate/AuthenticateCommandHandler.cs` (line 10), `Source/Src/Core/CleanArchitecture.Application/Features/Accounts/Commands/ChangePassword/ChangePasswordCommandHandler.cs` (line 9), … (+22 more) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them. In 27 of those file(s) — `Source/Src/Core/CleanArchitecture.Application/Behaviours/ValidationBehavior.cs`, `Source/Src/Core/CleanArchitecture.Application/DTOs/PaginationResponseDto.cs`, `Source/Src/Core/CleanArchitecture.Application/DTOs/TranslatorMessageDto.cs`, `Source/Src/Core/CleanArchitecture.Application/Features/Accounts/Commands/Authenticate/AuthenticateCommandHandler.cs`, `Source/Src/Core/CleanArchitecture.Application/Features/Accounts/Commands/ChangePassword/ChangePasswordCommandHandler.cs`, … (+22 more) — the break is a C# primary constructor, which semgrep's grammar cannot parse and which hides the type from every rule scoped to it; those files were re-scanned from a shadow copy with the constructor's parameter list blanked (line and column preserving), which restores the type to the rules, and 0 additional row(s) came from that pass. Only the header's own parameter list is unread in them.
What to do
- Resolve the 8 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (3), REDACTED (3), REDACTED (2). — One of this dimension's main actionable groups (8 issue-level).
- Resolve the 4 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (4). — One of this dimension's main actionable groups (4 warning-level).
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
D30 · Dependency Vulnerabilities
1 finding(s): 0 critical, 1 high, 0 medium, 0 low.
What to do
- Resolve the 1 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
D31 · IaC & Container Security
1 finding(s): 0 critical, 1 high, 0 medium, 0 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).
D34 · Knowledge Freshness
Every significant source file has living knowledge — recently and meaningfully worked. Counted over 5 of the 85 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
D35 · Change Coupling
No strong hidden change-coupling between production files.
D39 · IL Efficiency
0 of 163 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 10 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
AX8 · Test isolation
AX9 · CQS / query purity
DM1 · Aggregate boundaries
DM10 · One transaction, one aggregate
DM11 · Constructible invalid state
- `Product`'s public constructor takes `name`, `price`, `barCode` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `Product` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. — Source/Src/Core/CleanArchitecture.Domain/Products/Entities/Product.cs:12
What to do
- Give each aggregate one way in that can refuse — a guarded constructor, value-object parameters that validate themselves, or a private constructor behind a factory that returns a failure.
DM12 · Ambient inputs in the domain
DM4 · Rich vs anemic model
- `Product` is an aggregate/entity with 3 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — Source/Src/Core/CleanArchitecture.Domain/Products/Entities/Product.cs:5
What to do
- Move business rules onto the aggregates/entities they govern so invariants are enforced at the source, not in anemic services.
DM5 · Encapsulated state
- `AuditableBaseEntity` exposes publicly writable state (CreatedBy, Created, LastModifiedBy, LastModified). — Source/Src/Core/CleanArchitecture.Domain/Common/AuditableBaseEntity.cs:5
What to do
- Make entity setters private/init-only and hand collections out as IReadOnlyList/IReadOnlyCollection over a private backing field; change state only through methods that enforce the invariants (Marten/EF can bind via constructor or private setters).
DM6 · Domain ↔ infrastructure boundary
DM7 · Repository granularity
DM9 · Scattered domain decisions
ED5 · Idempotency
- `CreateProduct.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 16), 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. — Source/Src/Core/CleanArchitecture.Application/Features/Products/Commands/CreateProduct/CreateProductCommandHandler.cs:12
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
- A `#pragma warning disable` with no error codes silences every warning for the rest of the file — hidden debt. Suppress specific codes with a justification instead. (×5) — Source/Src/Core/CleanArchitecture.Domain/Products/DTOs/ProductDto.cs:8, Source/Src/Core/CleanArchitecture.Domain/Products/Entities/Product.cs:7, Source/Src/Core/CleanArchitecture.Domain/Products/Entities/Product.cs:11, …
What to do
- Clear the softer debt: remove commented-out code and dead branches, re-enable or delete skipped tests, and replace blanket warning suppressions with targeted ones.
M1 · Documentation (README)
What to do
- Add a README to the 6 of 7 project(s) that lack one — worth up to 1.7 pts.
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
M3 · Folder & project structure
M4 · Documentation accuracy
P1 · CI/CD gates
P10 · Library API & versioning
P2 · Observability
What to do
- Add OpenTelemetry tracing/metrics (ActivitySource / AddMetrics) so requests are traceable across the system, not just health-probable.
P3 · Security & performance tooling
- `REDACTED` schedules updates, but no `package-ecosystem` entry covers `github-actions`, which this tree depends on — so those dependencies get no update pull requests and no advisory pressure, however complete the dep-scan credit looks. Add the missing entry to the `updates:` list. — REDACTED:2
What to do
- Dependabot is configured but does not watch `github-actions` — add that `package-ecosystem` entry to REDACTED so those dependencies get the same automatic update and advisory pressure as the ones it already covers.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
- Deployment automation exists but no readiness/liveness probes, rolling-update strategy, lifecycle hooks or migration job were evidenced — a bad release is harder to detect and reverse.
What to do
- Add readiness/liveness probes and a rolling-update (or blue/green) strategy so a bad release is caught and rolled back automatically.
- Add an approval/environment gate (required reviewers / protection rules) before production promotion.
P5 · DR & Backup
- A persistence guard (data volume / purge-protection) was found, but no backup, geo-recovery or RTO/RPO controls were evidenced — a volume that survives a container recreate is not a tested restore from catastrophic loss.
What to do
- Codify backups + geo-recovery in IaC and document RTO/RPO and the restore procedure — a persistence guard alone is not disaster recovery.
P6 · Release Hygiene
- No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
What to do
- Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.
P8 · Schema migrations
PF1 · Benchmark discipline
- No benchmark suite was found by the two searches this check runs. FIRST, a BenchmarkDotNet package reference in any project file — every project the workspace loaded, plus a walk of project files on disk that never loaded, because a benchmark suite is exactly the project a partial load drops. SECOND, a script harness: a file whose name contains `benchmark` and ends `.py`, `.sh`, `.ps1`, `.bash`, `.rb`, `.js` or `.mjs`, credited ONLY when this repository's CI text also mentions benchmarks — a harness no pipeline runs is read as a fixture, deliberately. Neither search can see a benchmark suite in another ecosystem's idiom (a Go `testing.B` file, a JMH or criterion project, a pytest-benchmark run), so this is 'no benchmark found by those two searches', not a verdict that the repository has none. Where code is performance-sensitive, a benchmark guards against silent regressions — but it's a bonus here, not a deduction.
What to do
- Add a benchmarking harness for the hot paths and run it in CI to catch regressions (for .NET, a BenchmarkDotNet project with [MemoryDiagnoser] to track allocations).
PF3 · Async & latency hygiene
S1 · Web-Security Posture
- 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 11/35 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. (×22) — Source/Src/Infrastructure/CleanArchitecture.Infrastructure.Identity/Seeds/DefaultBasicUser.cs:10, Source/Src/Infrastructure/CleanArchitecture.Infrastructure.Identity/Seeds/DefaultRoles.cs:10, Source/Src/Infrastructure/CleanArchitecture.Infrastructure.Identity/Services/AccountServices.cs:48, …
- Queues or hands on an async lambda whose work calls something that takes a CancellationToken, while neither this method nor the delegate supplies one — that work can't be stopped early once started. Take a CancellationToken here and let the lambda capture it, or use a delegate that is handed one (`Func<CancellationToken, Task>`). — Source/Src/Infrastructure/CleanArchitecture.Infrastructure.Identity/ServiceRegistration.cs:80
- 1 async method(s) await work their caller's cancellation cannot reach: a CancellationToken they hold (a parameter, or the one a framework-fixed signature carries) is never passed on, or the call is handed CancellationToken.None, default or an already-cancelled token. Forward the caller's token to that call.
- Its signature is fixed by the framework, and the token it carries (`context.RequestAborted`) reaches none of the calls here that take one — so an aborted request or a stopping host still waits for that work. Pass `context.RequestAborted` to them. — Source/Src/Presentation/CleanArchitecture.WebApi/Infrastructure/Middlewares/ErrorHandlerMiddleware.cs:17
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
- 1/7 NRT-eligible project(s) enable <Nullable>enable</Nullable> (projects targeting a pre-C#-8 framework are excluded — NRTs aren't available there). NRTs catch a whole class of null-deref bugs at compile time.
- ~0.2 `!` suppressions per 1k syntax nodes — 1 suppression(s) across the 5364 syntax node(s) in code where nullable warnings are ENABLED, which is the only code a `!` can suppress anything in (a `!` under `#nullable disable` is inert and is not counted, and its file's nodes are not in the denominator). Each one tells the compiler to trust you about null, suppressing the very safety NRTs provide.
What to do
- Enable <Nullable>enable</Nullable> across all projects and resolve warnings rather than suppressing with `!`.
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 69% | Adequate — gated by X5 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 84% | Exemplary | Strongest area. |
| Maturity | 70% | Adequate — gated by M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 46% | Adequate — gated by D13, P5 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 56% | Adequate — gated by D29 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Domain Modelling | 64% | Adequate — gated by DM4, DM11 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Performance | 77% | Strong | Solid. |
Unscored — 1 check(s) recorded observations but carry no score
- SC1 Supply-chain hygiene — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Not included — 43 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.
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXR1 Runtime accessibility — compose up failed (exit 17 — an image could not be built) — cleanarchitecture.webapi Pulling cleanarchitecture.webapi Warning pull access denied for cleanarchitecturewebapi, repository does not exist or may require 'docker login': denied: requested access to the resource is denied failed to solve: failed to read dockerfile: open Dockerfile: no such file or directory; runtime evidence skipped This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
- 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.
- D16 Bus Factor — single-contributor repository — bus factor is not applicable
- D20 ADR Quality — N/A — this repo declares itself a template / kata / sample / demo; a formal ADR log is deferred to a real application built from it.
- D21 Naming Consistency — N/A — too few peers to establish a naming convention (433 declarations, no unit with a dominant convention).
- D22 Internal API Consistency — No intentionally-exposed public API to evaluate for consistency.
- D23 Boundary Type-Coupling — small single-context codebase (1,728 production LoC in the .NET projects) — bounded contexts are not needed at this size No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Aggregate roots were found in only one source directory (Core), which is a layered codebase, not two contexts. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D24 Comment Value — Too few judgeable comments (4 of at least 30); comment value is not applicable here.
- D25 ADR Conformance — no ADRs to check
- D32 Data Compliance (PII/GDPR) — 24 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
- D36 Supply-chain Provenance & Signing — This is a dotnet-new template — it produces no released artifact to attest. Supply-chain provenance, signing and SBOM are deferred to the application you build from it (add SLSA provenance / cosign signing / an SBOM in your app's release pipeline).
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D7 Architectural Integrity — no checkable ADRs and no dependency cycles — architectural integrity not assessed
- D8 Code Coverage — Coverage not measured — no coverage collector is wired up
- 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
- DM8 Value-object opportunities — not scored — the deterministic rule found 0 candidate clump(s); its rows are withheld until it has a measured precision of 95 % (a sample of fewer than 10 rows cannot show one)
- ED1 Event-Driven — not scored — this repository shows only 1 of the 3 signals this lens looks for (9 CQRS handler(s))
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
- P7 Outbound HTTP resilience — no outbound HTTP usage detected — no HttpClient/IHttpClientFactory/AddHttpClient in source, and no Refit/RestSharp/Flurl.Http namespace or package reference
- P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (Cobertura — `dotnet test --collect:"XPlat Code Coverage"` with a `coverlet.collector` PackageReference) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures, or wire coverage collection into CI, to enable this cross-layer check
- PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
- X10 Duplicated predicate — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X7 Silent fallback defaults — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
Critical — 18 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- FileScopedPragmaDisable Source/Src/Core/CleanArchitecture.Domain/Products/Entities/Product.cs:7
- FileScopedPragmaDisable Source/Src/Core/CleanArchitecture.Domain/Products/Entities/Product.cs:11
- FileScopedPragmaDisable Source/Src/Infrastructure/CleanArchitecture.Infrastructure.Identity/Settings/JwtSettings.cs:3
- FileScopedPragmaDisable Source/Src/Infrastructure/CleanArchitecture.Infrastructure.Identity/Settings/JwtSettings.cs:11
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
Serious — 37 finding(s)
- Async method without CancellationToken: SeedAsync Source/Src/Infrastructure/CleanArchitecture.Infrastructure.Identity/Seeds/DefaultBasicUser.cs:10
- Async method without CancellationToken: SeedAsync Source/Src/Infrastructure/CleanArchitecture.Infrastructure.Identity/Seeds/DefaultRoles.cs:10
- Async method without CancellationToken: Authenticate Source/Src/Infrastructure/CleanArchitecture.Infrastructure.Identity/Services/AccountServices.cs:48
- Async method without CancellationToken: AuthenticateByUserName Source/Src/Infrastructure/CleanArchitecture.Infrastructure.Identity/Services/AccountServices.cs:65
- Async method without CancellationToken: GetAuthenticationResponse Source/Src/Infrastructure/CleanArchitecture.Infrastructure.Identity/Services/AccountServices.cs:99
- Async method without CancellationToken: GetPagedUsers Source/Src/Infrastructure/CleanArchitecture.Infrastructure.Identity/Services/GetUserServices.cs:15
- Async method without CancellationToken: SaveChangesAsync Source/Src/Infrastructure/CleanArchitecture.Infrastructure.Persistence/Contexts/UnitOfWork.cs:8
- Async method without CancellationToken: GetByIdAsync Source/Src/Infrastructure/CleanArchitecture.Infrastructure.Persistence/Repositories/GenericRepository.cs:12
- Async method without CancellationToken: AddAsync Source/Src/Infrastructure/CleanArchitecture.Infrastructure.Persistence/Repositories/GenericRepository.cs:17
- Async method without CancellationToken: GetAllAsync Source/Src/Infrastructure/CleanArchitecture.Infrastructure.Persistence/Repositories/GenericRepository.cs:33
- Async method without CancellationToken: Paged Source/Src/Infrastructure/CleanArchitecture.Infrastructure.Persistence/Repositories/GenericRepository.cs:41
- Async method without CancellationToken: GetPagedListAsync Source/Src/Infrastructure/CleanArchitecture.Infrastructure.Persistence/Repositories/ProductRepository.cs:13
- Async method without CancellationToken: SeedAsync Source/Src/Infrastructure/CleanArchitecture.Infrastructure.Persistence/Seeds/DefaultData.cs:11
- Async method without CancellationToken: Authenticate Source/Src/Presentation/CleanArchitecture.WebApi/Endpoints/AccountEndpoint.cs:25
- Async method without CancellationToken: ChangeUserName Source/Src/Presentation/CleanArchitecture.WebApi/Endpoints/AccountEndpoint.cs:28
- Async method without CancellationToken: ChangePassword Source/Src/Presentation/CleanArchitecture.WebApi/Endpoints/AccountEndpoint.cs:31
- Async method without CancellationToken: Start Source/Src/Presentation/CleanArchitecture.WebApi/Endpoints/AccountEndpoint.cs:34
- Async method without CancellationToken: GetPagedListProduct Source/Src/Presentation/CleanArchitecture.WebApi/Endpoints/ProductEndpoint.cs:29
- Async method without CancellationToken: GetProductById Source/Src/Presentation/CleanArchitecture.WebApi/Endpoints/ProductEndpoint.cs:32
- Async method without CancellationToken: CreateProduct Source/Src/Presentation/CleanArchitecture.WebApi/Endpoints/ProductEndpoint.cs:35
- Async method without CancellationToken: UpdateProduct Source/Src/Presentation/CleanArchitecture.WebApi/Endpoints/ProductEndpoint.cs:38
- Async method without CancellationToken: DeleteProduct Source/Src/Presentation/CleanArchitecture.WebApi/Endpoints/ProductEndpoint.cs:41
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Dead code: GetPagedUsers Source/Src/Core/CleanArchitecture.Application/Interfaces/UserInterfaces/IGetUserServices.cs:10
- Dead code: BaseEntity Source/Src/Core/CleanArchitecture.Domain/Common/BaseEntity.cs:7
- BarePragmaDisable Source/Src/Core/CleanArchitecture.Domain/Products/DTOs/ProductDto.cs:8
- Duplicated block (10 lines × 2) Source/Src/Core/CleanArchitecture.Application/Features/Products/Commands/CreateProduct/CreateProductCommandValidator.cs:11
- Constructible in an invalid state: Product Source/Src/Core/CleanArchitecture.Domain/Products/Entities/Product.cs:12
- Anemic entity: Product Source/Src/Core/CleanArchitecture.Domain/Products/Entities/Product.cs:5
- Non-idempotent mutation: CreateProduct.CreateProductCommandHandler.Handle Source/Src/Core/CleanArchitecture.Application/Features/Products/Commands/CreateProduct/CreateProductCommandHandler.cs:12
- No DR/backup evidence
- NuGet dependencies are not locked
- Async delegate without CancellationToken: AddIdentityInfrastructure Source/Src/Infrastructure/CleanArchitecture.Infrastructure.Identity/ServiceRegistration.cs:80
- Async method drops its ambient CancellationToken: Invoke Source/Src/Presentation/CleanArchitecture.WebApi/Infrastructure/Middlewares/ErrorHandlerMiddleware.cs:17
Minor — 18 finding(s)
- Blanket warning suppression Source/Src/Core/CleanArchitecture.Domain/Products/DTOs/ProductDto.cs:8
- Blanket warning suppression Source/Src/Core/CleanArchitecture.Domain/Products/Entities/Product.cs:7
- Blanket warning suppression Source/Src/Core/CleanArchitecture.Domain/Products/Entities/Product.cs:11
- Blanket warning suppression Source/Src/Infrastructure/CleanArchitecture.Infrastructure.Identity/Settings/JwtSettings.cs:3
- Blanket warning suppression Source/Src/Infrastructure/CleanArchitecture.Infrastructure.Identity/Settings/JwtSettings.cs:11
- Mutable entity: AuditableBaseEntity Source/Src/Core/CleanArchitecture.Domain/Common/AuditableBaseEntity.cs:5
- No ADRs
- Dependabot does not watch github-actions REDACTED:2
- 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
- Some async methods drop the CancellationToken they accept
- Nullable reference types not enabled everywhere
- Null-forgiving operator (`!`) suppressions reduce the NRT score
Minor — 1 finding(s)
- Mock framework: Moq
Appendix B — Reproduction & audit trail
| Dimension | Tool | Version | Command | Findings | Raw output |
|---|---|---|---|---|---|
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-7f671efd8270423fb7906ca621677d3e/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-7f671efd8270423fb7906ca621677d3e/tree.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-tree.json |
| D29 · Static Analysis (SAST) | semgrep | — | semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/canine-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt --exclude Source/Src/Infrastructure/CleanArchitecture.Infrastructure.Identity/Migrations --exclude Source/Src/Infrastructure/CleanArchitecture.Infrastructure.Persistence/Migrations . | 13 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | dotnet | — | dotnet list Source/CleanArchitecture.slnx package --vulnerable --include-transitive --format json | 1 | artifacts/raw/dotnet-vulnerable.json |
| D31 · IaC & Container Security | trivy | — | trivy config --format json --quiet . | 1 | artifacts/raw/trivy-config.json |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. semgrep could not parse 24 file(s) — `Source/Src/Core/CleanArchitecture.Application/Behaviours/ValidationBehavior.cs`, `Source/Src/Core/CleanArchitecture.Application/DTOs/PaginationResponseDto.cs`, `Source/Src/Core/CleanArchitecture.Application/DTOs/TranslatorMessageDto.cs`, `Source/Src/Core/CleanArchitecture.Application/Features/Accounts/Commands/Authenticate/AuthenticateCommandHandler.cs`, `Source/Src/Core/CleanArchitecture.Application/Features/Accounts/Commands/ChangePassword/ChangePasswordCommandHandler.cs`, … (+19 more) — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real. | 0 | — |
| D36 · Supply-chain Provenance & Signing | provenance | — | provenance: not applicable — This is a dotnet-new template — it produces no released artifact to attest. Supply-chain provenance, signing and SBOM are deferred to the application you build from it (add SLSA provenance / cosign signing / an SBOM in your app's release pipeline). | 0 | — |
| D37 · Vulnerability-disclosure Policy | disclosure | — | disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . /tmp/codehealth-osv-sbom-e059271636bf475cb68f3b78b060da28 | 0 | artifacts/raw/osv-scanner.json |
Appendix C — Personal-data map
Email — 2 field(s)
- AuthenticationResponse.Email Source/Src/Core/CleanArchitecture.Application/DTOs/Account/Responses/AuthenticationResponse.cs:9
- UserDto.Email Source/Src/Core/CleanArchitecture.Application/DTOs/Account/Responses/UserDto.cs:11
Phone — 1 field(s)
- UserDto.PhoneNumber Source/Src/Core/CleanArchitecture.Application/DTOs/Account/Responses/UserDto.cs:12