Executive summary
yilmazmustafayilmaz/MY.OnionArchitecture is rated At risk because critical security findings are open, most of them in the packages it uses. Its score is held back in part because the project has no automated tests. It scores 39 out of 100, which the At risk rating leaves unchanged.
Production Readiness, at 22, is the weakest lens and counts most in the score. The best first step is adding automated tests, worth about 14 points. Fixing the password or key in the code comes next, worth about 10 points. Raising Production Readiness to 70 would lift the score to about 52.
Six known security holes in the packages the code depends on can be used by attackers. One password or key is open to anyone who can read the repository, and the project has no automated tests, so a change can break it without warning. Replacing the exposed password or key, adding automated tests and updating the vulnerable packages would close these risks. The two data fields that are written but never read need removing.
The product code is 1,923 lines, about €1,800 to rebuild.
If Production Readiness rose from 22 to 70, the lowest score rated Strong, the score would rise from 39 to about 52.
New since the last survey: 5 findings
- Platform End-of-Life · End-of-life runtime: .NET net6.0 REDACTED
- Platform End-of-Life · End-of-life runtime: .NET net6.0 REDACTED
- Platform End-of-Life · End-of-life runtime: .NET net6.0 REDACTED
- Platform End-of-Life · End-of-life runtime: .NET net6.0 REDACTED
- Platform End-of-Life · End-of-life runtime: .NET net6.0 REDACTED
Fixed since the last survey: 2 findings
- Secret Scanning · Leaked secret: signing-key REDACTED
- Platform End-of-Life · End-of-life runtime: .NET net6.0 REDACTED
Rebuild cost: about €1,800 · Estimate
| Cost to rebuild | €610 to €3,000, for 10 to 31 hours of work, under 0.1 person-years for one engineer |
|---|---|
| Difficulty of the problem | Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.7 at a score of 39. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it. |
| Size | Very small: 1,923 lines of product code, of which 51% is declarations and boilerplate, 46% straight logic and 4% 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 — module dependency graph
Architecture: which parts of the code depend on which
| uses → | 1 Application.Abstract.Paginate | 2 Application.Repositories.BaseRepositories | 3 Domain.Comman | 4 Domain.Dtos | 5 Infrastructure.SignalR.Hubs | 6 Infrastructure.Storages | 7 Application.Abstract.Storages | 8 Application.Repositories.Articles | 9 Application.Repositories.AuthorImagesFiles | 10 Application.Repositories.Authors | 11 Application.Repositories.Files | 12 Domain.Entities | 13 Application.Abstract.Services | 14 Application.Abstract.Storages.Local | 15 Application.Features.Articles.Commands.RemoveArticle | 16 Application.Features.Articles.Commands.UpdateArticle | 17 Application.Features.Articles.Queries.GetByIdArticle | 18 Application.Features.Authors.Commands.RemoveAuthor | 19 Application.Features.Authors.Commands.RemoveAuthorImage | 20 Application.Features.Authors.Commands.UpdateAuthor | 21 Application.Features.Authors.Queries.GetByIdAuthor | 22 Application.Services | 23 Persistence.Contexts | 24 Application.Features.Articles.Commands.CreateArticle | 25 Application.Features.Articles.Queries.GetAllArticle | 26 Application.Features.Authors.Commands.CreateAuthor | 27 Application.Features.Authors.Commands.CreateAuthorImage | 28 Application.Features.Authors.Queries.GetAllAuthor | 29 Application.Features.Users.Commands.CreateUser | 30 Application.Features.Users.Commands.LoginUser | 31 Application.Features.Users.Commands.RefreshTokenUser | 32 Infrastructure.Services | 33 Infrastructure.Storages.Local | 34 Persistence.Repositories.BaseRepositories | 35 Persistence.Services | 36 Persistence.Repositories.Articles | 37 Persistence.Repositories.AuthorImageFiles | 38 Persistence.Repositories.Authors | 39 Persistence.Repositories.Files | 40 Web.API.Controllers |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 Application.Abstract.Paginate | ||||||||||||||||||||||||||||||||||||||||
| 2 Application.Repositories.BaseRepositories | ||||||||||||||||||||||||||||||||||||||||
| 3 Domain.Comman | ||||||||||||||||||||||||||||||||||||||||
| 4 Domain.Dtos | ||||||||||||||||||||||||||||||||||||||||
| 5 Infrastructure.SignalR.Hubs | ||||||||||||||||||||||||||||||||||||||||
| 6 Infrastructure.Storages | ||||||||||||||||||||||||||||||||||||||||
| 7 Application.Abstract.Storages | 1 | |||||||||||||||||||||||||||||||||||||||
| 8 Application.Repositories.Articles | 2 | |||||||||||||||||||||||||||||||||||||||
| 9 Application.Repositories.AuthorImagesFiles | 2 | |||||||||||||||||||||||||||||||||||||||
| 10 Application.Repositories.Authors | 2 | |||||||||||||||||||||||||||||||||||||||
| 11 Application.Repositories.Files | 2 | |||||||||||||||||||||||||||||||||||||||
| 12 Domain.Entities | 7 | |||||||||||||||||||||||||||||||||||||||
| 13 Application.Abstract.Services | 1 | |||||||||||||||||||||||||||||||||||||||
| 14 Application.Abstract.Storages.Local | 1 | |||||||||||||||||||||||||||||||||||||||
| 15 Application.Features.Articles.Commands.RemoveArticle | 1 | |||||||||||||||||||||||||||||||||||||||
| 16 Application.Features.Articles.Commands.UpdateArticle | 2 | |||||||||||||||||||||||||||||||||||||||
| 17 Application.Features.Articles.Queries.GetByIdArticle | 1 | |||||||||||||||||||||||||||||||||||||||
| 18 Application.Features.Authors.Commands.RemoveAuthor | 1 | |||||||||||||||||||||||||||||||||||||||
| 19 Application.Features.Authors.Commands.RemoveAuthorImage | 2 | |||||||||||||||||||||||||||||||||||||||
| 20 Application.Features.Authors.Commands.UpdateAuthor | 2 | |||||||||||||||||||||||||||||||||||||||
| 21 Application.Features.Authors.Queries.GetByIdAuthor | 1 | |||||||||||||||||||||||||||||||||||||||
| 22 Application.Services | 1 | 4 | 2 | |||||||||||||||||||||||||||||||||||||
| 23 Persistence.Contexts | 1 | 3 | ||||||||||||||||||||||||||||||||||||||
| 24 Application.Features.Articles.Commands.CreateArticle | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 25 Application.Features.Articles.Queries.GetAllArticle | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 26 Application.Features.Authors.Commands.CreateAuthor | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 27 Application.Features.Authors.Commands.CreateAuthorImage | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 28 Application.Features.Authors.Queries.GetAllAuthor | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 29 Application.Features.Users.Commands.CreateUser | 1 | |||||||||||||||||||||||||||||||||||||||
| 30 Application.Features.Users.Commands.LoginUser | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 31 Application.Features.Users.Commands.RefreshTokenUser | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 32 Infrastructure.Services | 1 | 2 | 2 | 1 | 1 | 1 | 5 | |||||||||||||||||||||||||||||||||
| 33 Infrastructure.Storages.Local | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 34 Persistence.Repositories.BaseRepositories | 2 | 2 | ||||||||||||||||||||||||||||||||||||||
| 35 Persistence.Services | 3 | 2 | 4 | |||||||||||||||||||||||||||||||||||||
| 36 Persistence.Repositories.Articles | 2 | 2 | 2 | |||||||||||||||||||||||||||||||||||||
| 37 Persistence.Repositories.AuthorImageFiles | 2 | 2 | 2 | |||||||||||||||||||||||||||||||||||||
| 38 Persistence.Repositories.Authors | 2 | 2 | 2 | |||||||||||||||||||||||||||||||||||||
| 39 Persistence.Repositories.Files | 2 | 2 | 2 | |||||||||||||||||||||||||||||||||||||
| 40 Web.API.Controllers | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 |
7→4 Application.Abstract.Storages uses Domain.Dtos✕
- Connections
- 1 pair of types, where a type in Application.Abstract.Storages uses a type in Domain.Dtos.
- The types involved
Application.Abstract.Storages.IStorage→Domain.Dtos.UploadDto
- Direction
- Application.Abstract.Storages uses Domain.Dtos, so a change to Domain.Dtos can break Application.Abstract.Storages, while a change to Application.Abstract.Storages can't break Domain.Dtos.
- Position
- Below the diagonal: Application.Abstract.Storages uses a module listed above it, which is the healthy direction.
8→2 Application.Repositories.Articles uses Application.Repositories.BaseRepositories✕
- Connections
- 2 pairs of types, where a type in Application.Repositories.Articles uses a type in Application.Repositories.BaseRepositories.
- The types involved
Application.Repositories.Articles.IArticleCommandRepository→Application.Repositories.BaseRepositories.ICommandRepositoryApplication.Repositories.Articles.IArticleQueryRepository→Application.Repositories.BaseRepositories.IQueryRepository
- Direction
- Application.Repositories.Articles uses Application.Repositories.BaseRepositories, so a change to Application.Repositories.BaseRepositories can break Application.Repositories.Articles, while a change to Application.Repositories.Articles can't break Application.Repositories.BaseRepositories.
- Position
- Below the diagonal: Application.Repositories.Articles uses a module listed above it, which is the healthy direction.
9→2 Application.Repositories.AuthorImagesFiles uses Application.Repositories.BaseRepositories✕
- Connections
- 2 pairs of types, where a type in Application.Repositories.AuthorImagesFiles uses a type in Application.Repositories.BaseRepositories.
- The types involved
Application.Repositories.AuthorImagesFiles.IAuthorImageFileCommandRepository→Application.Repositories.BaseRepositories.ICommandRepositoryApplication.Repositories.AuthorImagesFiles.IAuthorImageFileQueryRepository→Application.Repositories.BaseRepositories.IQueryRepository
- Direction
- Application.Repositories.AuthorImagesFiles uses Application.Repositories.BaseRepositories, so a change to Application.Repositories.BaseRepositories can break Application.Repositories.AuthorImagesFiles, while a change to Application.Repositories.AuthorImagesFiles can't break Application.Repositories.BaseRepositories.
- Position
- Below the diagonal: Application.Repositories.AuthorImagesFiles uses a module listed above it, which is the healthy direction.
10→2 Application.Repositories.Authors uses Application.Repositories.BaseRepositories✕
- Connections
- 2 pairs of types, where a type in Application.Repositories.Authors uses a type in Application.Repositories.BaseRepositories.
- The types involved
Application.Repositories.Authors.IAuthorCommandRepository→Application.Repositories.BaseRepositories.ICommandRepositoryApplication.Repositories.Authors.IAuthorQueryRepository→Application.Repositories.BaseRepositories.IQueryRepository
- Direction
- Application.Repositories.Authors uses Application.Repositories.BaseRepositories, so a change to Application.Repositories.BaseRepositories can break Application.Repositories.Authors, while a change to Application.Repositories.Authors can't break Application.Repositories.BaseRepositories.
- Position
- Below the diagonal: Application.Repositories.Authors uses a module listed above it, which is the healthy direction.
11→2 Application.Repositories.Files uses Application.Repositories.BaseRepositories✕
- Connections
- 2 pairs of types, where a type in Application.Repositories.Files uses a type in Application.Repositories.BaseRepositories.
- The types involved
Application.Repositories.Files.IFileCommandRepository→Application.Repositories.BaseRepositories.ICommandRepositoryApplication.Repositories.Files.IFileQueryRepository→Application.Repositories.BaseRepositories.IQueryRepository
- Direction
- Application.Repositories.Files uses Application.Repositories.BaseRepositories, so a change to Application.Repositories.BaseRepositories can break Application.Repositories.Files, while a change to Application.Repositories.Files can't break Application.Repositories.BaseRepositories.
- Position
- Below the diagonal: Application.Repositories.Files uses a module listed above it, which is the healthy direction.
12→3 Domain.Entities uses Domain.Comman✕
- Connections
- 7 pairs of types, where a type in Domain.Entities uses a type in Domain.Comman.
- The types involved
Domain.Entities.Article→Domain.Comman.BaseEntityDomain.Entities.Article→Domain.Comman.ICreatedDateDomain.Entities.Article→Domain.Comman.IUpdatedDateDomain.Entities.Author→Domain.Comman.BaseEntityDomain.Entities.Author→Domain.Comman.ICreatedDateDomain.Entities.Author→Domain.Comman.IUpdatedDateDomain.Entities.AuthorImageFile→Domain.Comman.BaseFile
- Direction
- Domain.Entities uses Domain.Comman, so a change to Domain.Comman can break Domain.Entities, while a change to Domain.Entities can't break Domain.Comman.
- Position
- Below the diagonal: Domain.Entities uses a module listed above it, which is the healthy direction.
13→7 Application.Abstract.Services uses Application.Abstract.Storages✕
- Connections
- 1 pair of types, where a type in Application.Abstract.Services uses a type in Application.Abstract.Storages.
- The types involved
Application.Abstract.Services.IStorageService→Application.Abstract.Storages.IStorage
- Direction
- Application.Abstract.Services uses Application.Abstract.Storages, so a change to Application.Abstract.Storages can break Application.Abstract.Services, while a change to Application.Abstract.Services can't break Application.Abstract.Storages.
- Position
- Below the diagonal: Application.Abstract.Services uses a module listed above it, which is the healthy direction.
14→7 Application.Abstract.Storages.Local uses Application.Abstract.Storages✕
- Connections
- 1 pair of types, where a type in Application.Abstract.Storages.Local uses a type in Application.Abstract.Storages.
- The types involved
Application.Abstract.Storages.Local.ILocalStorage→Application.Abstract.Storages.IStorage
- Direction
- Application.Abstract.Storages.Local uses Application.Abstract.Storages, so a change to Application.Abstract.Storages can break Application.Abstract.Storages.Local, while a change to Application.Abstract.Storages.Local can't break Application.Abstract.Storages.
- Position
- Below the diagonal: Application.Abstract.Storages.Local uses a module listed above it, which is the healthy direction.
15→8 Application.Features.Articles.Commands.RemoveArticle uses Application.Repositories.Articles✕
- Connections
- 1 pair of types, where a type in Application.Features.Articles.Commands.RemoveArticle uses a type in Application.Repositories.Articles.
- The types involved
Application.Features.Articles.Commands.RemoveArticle.RemoveArticleCommandHandler→Application.Repositories.Articles.IArticleCommandRepository
- Direction
- Application.Features.Articles.Commands.RemoveArticle uses Application.Repositories.Articles, so a change to Application.Repositories.Articles can break Application.Features.Articles.Commands.RemoveArticle, while a change to Application.Features.Articles.Commands.RemoveArticle can't break Application.Repositories.Articles.
- Position
- Below the diagonal: Application.Features.Articles.Commands.RemoveArticle uses a module listed above it, which is the healthy direction.
16→8 Application.Features.Articles.Commands.UpdateArticle uses Application.Repositories.Articles✕
- Connections
- 2 pairs of types, where a type in Application.Features.Articles.Commands.UpdateArticle uses a type in Application.Repositories.Articles.
- The types involved
Application.Features.Articles.Commands.UpdateArticle.UpdateArticleCommandHandler→Application.Repositories.Articles.IArticleCommandRepositoryApplication.Features.Articles.Commands.UpdateArticle.UpdateArticleCommandHandler→Application.Repositories.Articles.IArticleQueryRepository
- Direction
- Application.Features.Articles.Commands.UpdateArticle uses Application.Repositories.Articles, so a change to Application.Repositories.Articles can break Application.Features.Articles.Commands.UpdateArticle, while a change to Application.Features.Articles.Commands.UpdateArticle can't break Application.Repositories.Articles.
- Position
- Below the diagonal: Application.Features.Articles.Commands.UpdateArticle uses a module listed above it, which is the healthy direction.
17→8 Application.Features.Articles.Queries.GetByIdArticle uses Application.Repositories.Articles✕
- Connections
- 1 pair of types, where a type in Application.Features.Articles.Queries.GetByIdArticle uses a type in Application.Repositories.Articles.
- The types involved
Application.Features.Articles.Queries.GetByIdArticle.GetByIdArticleQueryHandler→Application.Repositories.Articles.IArticleQueryRepository
- Direction
- Application.Features.Articles.Queries.GetByIdArticle uses Application.Repositories.Articles, so a change to Application.Repositories.Articles can break Application.Features.Articles.Queries.GetByIdArticle, while a change to Application.Features.Articles.Queries.GetByIdArticle can't break Application.Repositories.Articles.
- Position
- Below the diagonal: Application.Features.Articles.Queries.GetByIdArticle uses a module listed above it, which is the healthy direction.
18→10 Application.Features.Authors.Commands.RemoveAuthor uses Application.Repositories.Authors✕
- Connections
- 1 pair of types, where a type in Application.Features.Authors.Commands.RemoveAuthor uses a type in Application.Repositories.Authors.
- The types involved
Application.Features.Authors.Commands.RemoveAuthor.RemoveAuthorCommandHandler→Application.Repositories.Authors.IAuthorCommandRepository
- Direction
- Application.Features.Authors.Commands.RemoveAuthor uses Application.Repositories.Authors, so a change to Application.Repositories.Authors can break Application.Features.Authors.Commands.RemoveAuthor, while a change to Application.Features.Authors.Commands.RemoveAuthor can't break Application.Repositories.Authors.
- Position
- Below the diagonal: Application.Features.Authors.Commands.RemoveAuthor uses a module listed above it, which is the healthy direction.
19→9 Application.Features.Authors.Commands.RemoveAuthorImage uses Application.Repositories.AuthorImagesFiles✕
- Connections
- 2 pairs of types, where a type in Application.Features.Authors.Commands.RemoveAuthorImage uses a type in Application.Repositories.AuthorImagesFiles.
- The types involved
Application.Features.Authors.Commands.RemoveAuthorImage.RemoveAuthorImageCommandHandler→Application.Repositories.AuthorImagesFiles.IAuthorImageFileCommandRepositoryApplication.Features.Authors.Commands.RemoveAuthorImage.RemoveAuthorImageCommandHandler→Application.Repositories.AuthorImagesFiles.IAuthorImageFileQueryRepository
- Direction
- Application.Features.Authors.Commands.RemoveAuthorImage uses Application.Repositories.AuthorImagesFiles, so a change to Application.Repositories.AuthorImagesFiles can break Application.Features.Authors.Commands.RemoveAuthorImage, while a change to Application.Features.Authors.Commands.RemoveAuthorImage can't break Application.Repositories.AuthorImagesFiles.
- Position
- Below the diagonal: Application.Features.Authors.Commands.RemoveAuthorImage uses a module listed above it, which is the healthy direction.
20→10 Application.Features.Authors.Commands.UpdateAuthor uses Application.Repositories.Authors✕
- Connections
- 2 pairs of types, where a type in Application.Features.Authors.Commands.UpdateAuthor uses a type in Application.Repositories.Authors.
- The types involved
Application.Features.Authors.Commands.UpdateAuthor.UpdateAuthorCommandHandler→Application.Repositories.Authors.IAuthorCommandRepositoryApplication.Features.Authors.Commands.UpdateAuthor.UpdateAuthorCommandHandler→Application.Repositories.Authors.IAuthorQueryRepository
- Direction
- Application.Features.Authors.Commands.UpdateAuthor uses Application.Repositories.Authors, so a change to Application.Repositories.Authors can break Application.Features.Authors.Commands.UpdateAuthor, while a change to Application.Features.Authors.Commands.UpdateAuthor can't break Application.Repositories.Authors.
- Position
- Below the diagonal: Application.Features.Authors.Commands.UpdateAuthor uses a module listed above it, which is the healthy direction.
21→10 Application.Features.Authors.Queries.GetByIdAuthor uses Application.Repositories.Authors✕
- Connections
- 1 pair of types, where a type in Application.Features.Authors.Queries.GetByIdAuthor uses a type in Application.Repositories.Authors.
- The types involved
Application.Features.Authors.Queries.GetByIdAuthor.GetByIdAuthorQueryHandler→Application.Repositories.Authors.IAuthorQueryRepository
- Direction
- Application.Features.Authors.Queries.GetByIdAuthor uses Application.Repositories.Authors, so a change to Application.Repositories.Authors can break Application.Features.Authors.Queries.GetByIdAuthor, while a change to Application.Features.Authors.Queries.GetByIdAuthor can't break Application.Repositories.Authors.
- Position
- Below the diagonal: Application.Features.Authors.Queries.GetByIdAuthor uses a module listed above it, which is the healthy direction.
22→1 Application.Services uses Application.Abstract.Paginate✕
- Connections
- 1 pair of types, where a type in Application.Services uses a type in Application.Abstract.Paginate.
- The types involved
Application.Services.IPaginationService→Application.Abstract.Paginate.Pagination
- Direction
- Application.Services uses Application.Abstract.Paginate, so a change to Application.Abstract.Paginate can break Application.Services, while a change to Application.Services can't break Application.Abstract.Paginate.
- Position
- Below the diagonal: Application.Services uses a module listed above it, which is the healthy direction.
22→4 Application.Services uses Domain.Dtos✕
- Connections
- 4 pairs of types, where a type in Application.Services uses a type in Domain.Dtos.
- The types involved
Application.Services.IAuthService→Domain.Dtos.TokenDtoApplication.Services.ITokenHandlerService→Domain.Dtos.TokenDtoApplication.Services.IUserService→Domain.Dtos.CreateUserDtoApplication.Services.IUserService→Domain.Dtos.CreateUserResponseDto
- Direction
- Application.Services uses Domain.Dtos, so a change to Domain.Dtos can break Application.Services, while a change to Application.Services can't break Domain.Dtos.
- Position
- Below the diagonal: Application.Services uses a module listed above it, which is the healthy direction.
22→12 Application.Services uses Domain.Entities✕
- Connections
- 2 pairs of types, where a type in Application.Services uses a type in Domain.Entities.
- The types involved
Application.Services.ITokenHandlerService→Domain.Entities.AppUserApplication.Services.IUserService→Domain.Entities.AppUser
- Direction
- Application.Services uses Domain.Entities, so a change to Domain.Entities can break Application.Services, while a change to Application.Services can't break Domain.Entities.
- Position
- Below the diagonal: Application.Services uses a module listed above it, which is the healthy direction.
23→3 Persistence.Contexts uses Domain.Comman✕
- Connections
- 1 pair of types, where a type in Persistence.Contexts uses a type in Domain.Comman.
- The types involved
Persistence.Contexts.Context→Domain.Comman.BaseFile
- Direction
- Persistence.Contexts uses Domain.Comman, so a change to Domain.Comman can break Persistence.Contexts, while a change to Persistence.Contexts can't break Domain.Comman.
- Position
- Below the diagonal: Persistence.Contexts uses a module listed above it, which is the healthy direction.
23→12 Persistence.Contexts uses Domain.Entities✕
- Connections
- 3 pairs of types, where a type in Persistence.Contexts uses a type in Domain.Entities.
- The types involved
Persistence.Contexts.Context→Domain.Entities.ArticlePersistence.Contexts.Context→Domain.Entities.AuthorPersistence.Contexts.Context→Domain.Entities.AuthorImageFile
- Direction
- Persistence.Contexts uses Domain.Entities, so a change to Domain.Entities can break Persistence.Contexts, while a change to Persistence.Contexts can't break Domain.Entities.
- Position
- Below the diagonal: Persistence.Contexts uses a module listed above it, which is the healthy direction.
24→8 Application.Features.Articles.Commands.CreateArticle uses Application.Repositories.Articles✕
- Connections
- 1 pair of types, where a type in Application.Features.Articles.Commands.CreateArticle uses a type in Application.Repositories.Articles.
- The types involved
Application.Features.Articles.Commands.CreateArticle.CreateArticleCommandHandler→Application.Repositories.Articles.IArticleCommandRepository
- Direction
- Application.Features.Articles.Commands.CreateArticle uses Application.Repositories.Articles, so a change to Application.Repositories.Articles can break Application.Features.Articles.Commands.CreateArticle, while a change to Application.Features.Articles.Commands.CreateArticle can't break Application.Repositories.Articles.
- Position
- Below the diagonal: Application.Features.Articles.Commands.CreateArticle uses a module listed above it, which is the healthy direction.
24→22 Application.Features.Articles.Commands.CreateArticle uses Application.Services✕
- Connections
- 1 pair of types, where a type in Application.Features.Articles.Commands.CreateArticle uses a type in Application.Services.
- The types involved
Application.Features.Articles.Commands.CreateArticle.CreateArticleCommandHandler→Application.Services.IArticleHubService
- Direction
- Application.Features.Articles.Commands.CreateArticle uses Application.Services, so a change to Application.Services can break Application.Features.Articles.Commands.CreateArticle, while a change to Application.Features.Articles.Commands.CreateArticle can't break Application.Services.
- Position
- Below the diagonal: Application.Features.Articles.Commands.CreateArticle uses a module listed above it, which is the healthy direction.
25→1 Application.Features.Articles.Queries.GetAllArticle uses Application.Abstract.Paginate✕
- Connections
- 1 pair of types, where a type in Application.Features.Articles.Queries.GetAllArticle uses a type in Application.Abstract.Paginate.
- The types involved
Application.Features.Articles.Queries.GetAllArticle.GetAllArticleQueryRequest→Application.Abstract.Paginate.Pagination
- Direction
- Application.Features.Articles.Queries.GetAllArticle uses Application.Abstract.Paginate, so a change to Application.Abstract.Paginate can break Application.Features.Articles.Queries.GetAllArticle, while a change to Application.Features.Articles.Queries.GetAllArticle can't break Application.Abstract.Paginate.
- Position
- Below the diagonal: Application.Features.Articles.Queries.GetAllArticle uses a module listed above it, which is the healthy direction.
25→8 Application.Features.Articles.Queries.GetAllArticle uses Application.Repositories.Articles✕
- Connections
- 1 pair of types, where a type in Application.Features.Articles.Queries.GetAllArticle uses a type in Application.Repositories.Articles.
- The types involved
Application.Features.Articles.Queries.GetAllArticle.GetAllArticleQueryHandler→Application.Repositories.Articles.IArticleQueryRepository
- Direction
- Application.Features.Articles.Queries.GetAllArticle uses Application.Repositories.Articles, so a change to Application.Repositories.Articles can break Application.Features.Articles.Queries.GetAllArticle, while a change to Application.Features.Articles.Queries.GetAllArticle can't break Application.Repositories.Articles.
- Position
- Below the diagonal: Application.Features.Articles.Queries.GetAllArticle uses a module listed above it, which is the healthy direction.
25→12 Application.Features.Articles.Queries.GetAllArticle uses Domain.Entities✕
- Connections
- 1 pair of types, where a type in Application.Features.Articles.Queries.GetAllArticle uses a type in Domain.Entities.
- The types involved
Application.Features.Articles.Queries.GetAllArticle.GetAllArticleQueryHandler→Domain.Entities.Article
- Direction
- Application.Features.Articles.Queries.GetAllArticle uses Domain.Entities, so a change to Domain.Entities can break Application.Features.Articles.Queries.GetAllArticle, while a change to Application.Features.Articles.Queries.GetAllArticle can't break Domain.Entities.
- Position
- Below the diagonal: Application.Features.Articles.Queries.GetAllArticle uses a module listed above it, which is the healthy direction.
25→22 Application.Features.Articles.Queries.GetAllArticle uses Application.Services✕
- Connections
- 1 pair of types, where a type in Application.Features.Articles.Queries.GetAllArticle uses a type in Application.Services.
- The types involved
Application.Features.Articles.Queries.GetAllArticle.GetAllArticleQueryHandler→Application.Services.IPaginationService
- Direction
- Application.Features.Articles.Queries.GetAllArticle uses Application.Services, so a change to Application.Services can break Application.Features.Articles.Queries.GetAllArticle, while a change to Application.Features.Articles.Queries.GetAllArticle can't break Application.Services.
- Position
- Below the diagonal: Application.Features.Articles.Queries.GetAllArticle uses a module listed above it, which is the healthy direction.
26→10 Application.Features.Authors.Commands.CreateAuthor uses Application.Repositories.Authors✕
- Connections
- 1 pair of types, where a type in Application.Features.Authors.Commands.CreateAuthor uses a type in Application.Repositories.Authors.
- The types involved
Application.Features.Authors.Commands.CreateAuthor.CreateAuthorCommandHandler→Application.Repositories.Authors.IAuthorCommandRepository
- Direction
- Application.Features.Authors.Commands.CreateAuthor uses Application.Repositories.Authors, so a change to Application.Repositories.Authors can break Application.Features.Authors.Commands.CreateAuthor, while a change to Application.Features.Authors.Commands.CreateAuthor can't break Application.Repositories.Authors.
- Position
- Below the diagonal: Application.Features.Authors.Commands.CreateAuthor uses a module listed above it, which is the healthy direction.
26→22 Application.Features.Authors.Commands.CreateAuthor uses Application.Services✕
- Connections
- 1 pair of types, where a type in Application.Features.Authors.Commands.CreateAuthor uses a type in Application.Services.
- The types involved
Application.Features.Authors.Commands.CreateAuthor.CreateAuthorCommandHandler→Application.Services.IAuthorHubService
- Direction
- Application.Features.Authors.Commands.CreateAuthor uses Application.Services, so a change to Application.Services can break Application.Features.Authors.Commands.CreateAuthor, while a change to Application.Features.Authors.Commands.CreateAuthor can't break Application.Services.
- Position
- Below the diagonal: Application.Features.Authors.Commands.CreateAuthor uses a module listed above it, which is the healthy direction.
27→9 Application.Features.Authors.Commands.CreateAuthorImage uses Application.Repositories.AuthorImagesFiles✕
- Connections
- 1 pair of types, where a type in Application.Features.Authors.Commands.CreateAuthorImage uses a type in Application.Repositories.AuthorImagesFiles.
- The types involved
Application.Features.Authors.Commands.CreateAuthorImage.UploadAuthorImageCommandHandler→Application.Repositories.AuthorImagesFiles.IAuthorImageFileCommandRepository
- Direction
- Application.Features.Authors.Commands.CreateAuthorImage uses Application.Repositories.AuthorImagesFiles, so a change to Application.Repositories.AuthorImagesFiles can break Application.Features.Authors.Commands.CreateAuthorImage, while a change to Application.Features.Authors.Commands.CreateAuthorImage can't break Application.Repositories.AuthorImagesFiles.
- Position
- Below the diagonal: Application.Features.Authors.Commands.CreateAuthorImage uses a module listed above it, which is the healthy direction.
27→10 Application.Features.Authors.Commands.CreateAuthorImage uses Application.Repositories.Authors✕
- Connections
- 1 pair of types, where a type in Application.Features.Authors.Commands.CreateAuthorImage uses a type in Application.Repositories.Authors.
- The types involved
Application.Features.Authors.Commands.CreateAuthorImage.UploadAuthorImageCommandHandler→Application.Repositories.Authors.IAuthorQueryRepository
- Direction
- Application.Features.Authors.Commands.CreateAuthorImage uses Application.Repositories.Authors, so a change to Application.Repositories.Authors can break Application.Features.Authors.Commands.CreateAuthorImage, while a change to Application.Features.Authors.Commands.CreateAuthorImage can't break Application.Repositories.Authors.
- Position
- Below the diagonal: Application.Features.Authors.Commands.CreateAuthorImage uses a module listed above it, which is the healthy direction.
27→13 Application.Features.Authors.Commands.CreateAuthorImage uses Application.Abstract.Services✕
- Connections
- 1 pair of types, where a type in Application.Features.Authors.Commands.CreateAuthorImage uses a type in Application.Abstract.Services.
- The types involved
Application.Features.Authors.Commands.CreateAuthorImage.UploadAuthorImageCommandHandler→Application.Abstract.Services.IStorageService
- Direction
- Application.Features.Authors.Commands.CreateAuthorImage uses Application.Abstract.Services, so a change to Application.Abstract.Services can break Application.Features.Authors.Commands.CreateAuthorImage, while a change to Application.Features.Authors.Commands.CreateAuthorImage can't break Application.Abstract.Services.
- Position
- Below the diagonal: Application.Features.Authors.Commands.CreateAuthorImage uses a module listed above it, which is the healthy direction.
28→1 Application.Features.Authors.Queries.GetAllAuthor uses Application.Abstract.Paginate✕
- Connections
- 1 pair of types, where a type in Application.Features.Authors.Queries.GetAllAuthor uses a type in Application.Abstract.Paginate.
- The types involved
Application.Features.Authors.Queries.GetAllAuthor.GetAllAuthorQueryRequest→Application.Abstract.Paginate.Pagination
- Direction
- Application.Features.Authors.Queries.GetAllAuthor uses Application.Abstract.Paginate, so a change to Application.Abstract.Paginate can break Application.Features.Authors.Queries.GetAllAuthor, while a change to Application.Features.Authors.Queries.GetAllAuthor can't break Application.Abstract.Paginate.
- Position
- Below the diagonal: Application.Features.Authors.Queries.GetAllAuthor uses a module listed above it, which is the healthy direction.
28→10 Application.Features.Authors.Queries.GetAllAuthor uses Application.Repositories.Authors✕
- Connections
- 1 pair of types, where a type in Application.Features.Authors.Queries.GetAllAuthor uses a type in Application.Repositories.Authors.
- The types involved
Application.Features.Authors.Queries.GetAllAuthor.GetAllAuthorQueryHandler→Application.Repositories.Authors.IAuthorQueryRepository
- Direction
- Application.Features.Authors.Queries.GetAllAuthor uses Application.Repositories.Authors, so a change to Application.Repositories.Authors can break Application.Features.Authors.Queries.GetAllAuthor, while a change to Application.Features.Authors.Queries.GetAllAuthor can't break Application.Repositories.Authors.
- Position
- Below the diagonal: Application.Features.Authors.Queries.GetAllAuthor uses a module listed above it, which is the healthy direction.
28→12 Application.Features.Authors.Queries.GetAllAuthor uses Domain.Entities✕
- Connections
- 1 pair of types, where a type in Application.Features.Authors.Queries.GetAllAuthor uses a type in Domain.Entities.
- The types involved
Application.Features.Authors.Queries.GetAllAuthor.GetAllAuthorQueryHandler→Domain.Entities.Author
- Direction
- Application.Features.Authors.Queries.GetAllAuthor uses Domain.Entities, so a change to Domain.Entities can break Application.Features.Authors.Queries.GetAllAuthor, while a change to Application.Features.Authors.Queries.GetAllAuthor can't break Domain.Entities.
- Position
- Below the diagonal: Application.Features.Authors.Queries.GetAllAuthor uses a module listed above it, which is the healthy direction.
28→22 Application.Features.Authors.Queries.GetAllAuthor uses Application.Services✕
- Connections
- 1 pair of types, where a type in Application.Features.Authors.Queries.GetAllAuthor uses a type in Application.Services.
- The types involved
Application.Features.Authors.Queries.GetAllAuthor.GetAllAuthorQueryHandler→Application.Services.IPaginationService
- Direction
- Application.Features.Authors.Queries.GetAllAuthor uses Application.Services, so a change to Application.Services can break Application.Features.Authors.Queries.GetAllAuthor, while a change to Application.Features.Authors.Queries.GetAllAuthor can't break Application.Services.
- Position
- Below the diagonal: Application.Features.Authors.Queries.GetAllAuthor uses a module listed above it, which is the healthy direction.
29→22 Application.Features.Users.Commands.CreateUser uses Application.Services✕
- Connections
- 1 pair of types, where a type in Application.Features.Users.Commands.CreateUser uses a type in Application.Services.
- The types involved
Application.Features.Users.Commands.CreateUser.CreateUserCommandHandler→Application.Services.IUserService
- Direction
- Application.Features.Users.Commands.CreateUser uses Application.Services, so a change to Application.Services can break Application.Features.Users.Commands.CreateUser, while a change to Application.Features.Users.Commands.CreateUser can't break Application.Services.
- Position
- Below the diagonal: Application.Features.Users.Commands.CreateUser uses a module listed above it, which is the healthy direction.
30→4 Application.Features.Users.Commands.LoginUser uses Domain.Dtos✕
- Connections
- 1 pair of types, where a type in Application.Features.Users.Commands.LoginUser uses a type in Domain.Dtos.
- The types involved
Application.Features.Users.Commands.LoginUser.LoginUserCommandResponse→Domain.Dtos.TokenDto
- Direction
- Application.Features.Users.Commands.LoginUser uses Domain.Dtos, so a change to Domain.Dtos can break Application.Features.Users.Commands.LoginUser, while a change to Application.Features.Users.Commands.LoginUser can't break Domain.Dtos.
- Position
- Below the diagonal: Application.Features.Users.Commands.LoginUser uses a module listed above it, which is the healthy direction.
30→22 Application.Features.Users.Commands.LoginUser uses Application.Services✕
- Connections
- 1 pair of types, where a type in Application.Features.Users.Commands.LoginUser uses a type in Application.Services.
- The types involved
Application.Features.Users.Commands.LoginUser.LoginUserCommandHandler→Application.Services.IAuthService
- Direction
- Application.Features.Users.Commands.LoginUser uses Application.Services, so a change to Application.Services can break Application.Features.Users.Commands.LoginUser, while a change to Application.Features.Users.Commands.LoginUser can't break Application.Services.
- Position
- Below the diagonal: Application.Features.Users.Commands.LoginUser uses a module listed above it, which is the healthy direction.
31→4 Application.Features.Users.Commands.RefreshTokenUser uses Domain.Dtos✕
- Connections
- 1 pair of types, where a type in Application.Features.Users.Commands.RefreshTokenUser uses a type in Domain.Dtos.
- The types involved
Application.Features.Users.Commands.RefreshTokenUser.RefreshTokenUserResponse→Domain.Dtos.TokenDto
- Direction
- Application.Features.Users.Commands.RefreshTokenUser uses Domain.Dtos, so a change to Domain.Dtos can break Application.Features.Users.Commands.RefreshTokenUser, while a change to Application.Features.Users.Commands.RefreshTokenUser can't break Domain.Dtos.
- Position
- Below the diagonal: Application.Features.Users.Commands.RefreshTokenUser uses a module listed above it, which is the healthy direction.
31→22 Application.Features.Users.Commands.RefreshTokenUser uses Application.Services✕
- Connections
- 1 pair of types, where a type in Application.Features.Users.Commands.RefreshTokenUser uses a type in Application.Services.
- The types involved
Application.Features.Users.Commands.RefreshTokenUser.RefreshTokenUserHandler→Application.Services.IAuthService
- Direction
- Application.Features.Users.Commands.RefreshTokenUser uses Application.Services, so a change to Application.Services can break Application.Features.Users.Commands.RefreshTokenUser, while a change to Application.Features.Users.Commands.RefreshTokenUser can't break Application.Services.
- Position
- Below the diagonal: Application.Features.Users.Commands.RefreshTokenUser uses a module listed above it, which is the healthy direction.
32→1 Infrastructure.Services uses Application.Abstract.Paginate✕
- Connections
- 1 pair of types, where a type in Infrastructure.Services uses a type in Application.Abstract.Paginate.
- The types involved
Infrastructure.Services.PaginationService→Application.Abstract.Paginate.Pagination
- Direction
- Infrastructure.Services uses Application.Abstract.Paginate, so a change to Application.Abstract.Paginate can break Infrastructure.Services, while a change to Infrastructure.Services can't break Application.Abstract.Paginate.
- Position
- Below the diagonal: Infrastructure.Services uses a module listed above it, which is the healthy direction.
32→4 Infrastructure.Services uses Domain.Dtos✕
- Connections
- 2 pairs of types, where a type in Infrastructure.Services uses a type in Domain.Dtos.
- The types involved
Infrastructure.Services.StorageService→Domain.Dtos.UploadDtoInfrastructure.Services.TokenHandlerService→Domain.Dtos.TokenDto
- Direction
- Infrastructure.Services uses Domain.Dtos, so a change to Domain.Dtos can break Infrastructure.Services, while a change to Infrastructure.Services can't break Domain.Dtos.
- Position
- Below the diagonal: Infrastructure.Services uses a module listed above it, which is the healthy direction.
32→5 Infrastructure.Services uses Infrastructure.SignalR.Hubs✕
- Connections
- 2 pairs of types, where a type in Infrastructure.Services uses a type in Infrastructure.SignalR.Hubs.
- The types involved
Infrastructure.Services.ArticleHubService→Infrastructure.SignalR.Hubs.ArticleHubInfrastructure.Services.AuthorHubService→Infrastructure.SignalR.Hubs.AuthorHub
- Direction
- Infrastructure.Services uses Infrastructure.SignalR.Hubs, so a change to Infrastructure.SignalR.Hubs can break Infrastructure.Services, while a change to Infrastructure.Services can't break Infrastructure.SignalR.Hubs.
- Position
- Below the diagonal: Infrastructure.Services uses a module listed above it, which is the healthy direction.
32→7 Infrastructure.Services uses Application.Abstract.Storages✕
- Connections
- 1 pair of types, where a type in Infrastructure.Services uses a type in Application.Abstract.Storages.
- The types involved
Infrastructure.Services.StorageService→Application.Abstract.Storages.IStorage
- Direction
- Infrastructure.Services uses Application.Abstract.Storages, so a change to Application.Abstract.Storages can break Infrastructure.Services, while a change to Infrastructure.Services can't break Application.Abstract.Storages.
- Position
- Below the diagonal: Infrastructure.Services uses a module listed above it, which is the healthy direction.
32→12 Infrastructure.Services uses Domain.Entities✕
- Connections
- 1 pair of types, where a type in Infrastructure.Services uses a type in Domain.Entities.
- The types involved
Infrastructure.Services.TokenHandlerService→Domain.Entities.AppUser
- Direction
- Infrastructure.Services uses Domain.Entities, so a change to Domain.Entities can break Infrastructure.Services, while a change to Infrastructure.Services can't break Domain.Entities.
- Position
- Below the diagonal: Infrastructure.Services uses a module listed above it, which is the healthy direction.
32→13 Infrastructure.Services uses Application.Abstract.Services✕
- Connections
- 1 pair of types, where a type in Infrastructure.Services uses a type in Application.Abstract.Services.
- The types involved
Infrastructure.Services.StorageService→Application.Abstract.Services.IStorageService
- Direction
- Infrastructure.Services uses Application.Abstract.Services, so a change to Application.Abstract.Services can break Infrastructure.Services, while a change to Infrastructure.Services can't break Application.Abstract.Services.
- Position
- Below the diagonal: Infrastructure.Services uses a module listed above it, which is the healthy direction.
32→22 Infrastructure.Services uses Application.Services✕
- Connections
- 5 pairs of types, where a type in Infrastructure.Services uses a type in Application.Services.
- The types involved
Infrastructure.Services.ArticleHubService→Application.Services.IArticleHubServiceInfrastructure.Services.AuthorHubService→Application.Services.IAuthorHubServiceInfrastructure.Services.MailService→Application.Services.IMailServiceInfrastructure.Services.PaginationService→Application.Services.IPaginationServiceInfrastructure.Services.TokenHandlerService→Application.Services.ITokenHandlerService
- Direction
- Infrastructure.Services uses Application.Services, so a change to Application.Services can break Infrastructure.Services, while a change to Infrastructure.Services can't break Application.Services.
- Position
- Below the diagonal: Infrastructure.Services uses a module listed above it, which is the healthy direction.
33→4 Infrastructure.Storages.Local uses Domain.Dtos✕
- Connections
- 1 pair of types, where a type in Infrastructure.Storages.Local uses a type in Domain.Dtos.
- The types involved
Infrastructure.Storages.Local.LocalStorage→Domain.Dtos.UploadDto
- Direction
- Infrastructure.Storages.Local uses Domain.Dtos, so a change to Domain.Dtos can break Infrastructure.Storages.Local, while a change to Infrastructure.Storages.Local can't break Domain.Dtos.
- Position
- Below the diagonal: Infrastructure.Storages.Local uses a module listed above it, which is the healthy direction.
33→6 Infrastructure.Storages.Local uses Infrastructure.Storages✕
- Connections
- 1 pair of types, where a type in Infrastructure.Storages.Local uses a type in Infrastructure.Storages.
- The types involved
Infrastructure.Storages.Local.LocalStorage→Infrastructure.Storages.Storage
- Direction
- Infrastructure.Storages.Local uses Infrastructure.Storages, so a change to Infrastructure.Storages can break Infrastructure.Storages.Local, while a change to Infrastructure.Storages.Local can't break Infrastructure.Storages.
- Position
- Below the diagonal: Infrastructure.Storages.Local uses a module listed above it, which is the healthy direction.
33→14 Infrastructure.Storages.Local uses Application.Abstract.Storages.Local✕
- Connections
- 1 pair of types, where a type in Infrastructure.Storages.Local uses a type in Application.Abstract.Storages.Local.
- The types involved
Infrastructure.Storages.Local.LocalStorage→Application.Abstract.Storages.Local.ILocalStorage
- Direction
- Infrastructure.Storages.Local uses Application.Abstract.Storages.Local, so a change to Application.Abstract.Storages.Local can break Infrastructure.Storages.Local, while a change to Infrastructure.Storages.Local can't break Application.Abstract.Storages.Local.
- Position
- Below the diagonal: Infrastructure.Storages.Local uses a module listed above it, which is the healthy direction.
34→2 Persistence.Repositories.BaseRepositories uses Application.Repositories.BaseRepositories✕
- Connections
- 2 pairs of types, where a type in Persistence.Repositories.BaseRepositories uses a type in Application.Repositories.BaseRepositories.
- The types involved
Persistence.Repositories.BaseRepositories.CommandRepository→Application.Repositories.BaseRepositories.ICommandRepositoryPersistence.Repositories.BaseRepositories.QueryRepository→Application.Repositories.BaseRepositories.IQueryRepository
- Direction
- Persistence.Repositories.BaseRepositories uses Application.Repositories.BaseRepositories, so a change to Application.Repositories.BaseRepositories can break Persistence.Repositories.BaseRepositories, while a change to Persistence.Repositories.BaseRepositories can't break Application.Repositories.BaseRepositories.
- Position
- Below the diagonal: Persistence.Repositories.BaseRepositories uses a module listed above it, which is the healthy direction.
34→23 Persistence.Repositories.BaseRepositories uses Persistence.Contexts✕
- Connections
- 2 pairs of types, where a type in Persistence.Repositories.BaseRepositories uses a type in Persistence.Contexts.
- The types involved
Persistence.Repositories.BaseRepositories.CommandRepository→Persistence.Contexts.ContextPersistence.Repositories.BaseRepositories.QueryRepository→Persistence.Contexts.Context
- Direction
- Persistence.Repositories.BaseRepositories uses Persistence.Contexts, so a change to Persistence.Contexts can break Persistence.Repositories.BaseRepositories, while a change to Persistence.Repositories.BaseRepositories can't break Persistence.Contexts.
- Position
- Below the diagonal: Persistence.Repositories.BaseRepositories uses a module listed above it, which is the healthy direction.
35→4 Persistence.Services uses Domain.Dtos✕
- Connections
- 3 pairs of types, where a type in Persistence.Services uses a type in Domain.Dtos.
- The types involved
Persistence.Services.AuthService→Domain.Dtos.TokenDtoPersistence.Services.UserService→Domain.Dtos.CreateUserDtoPersistence.Services.UserService→Domain.Dtos.CreateUserResponseDto
- Direction
- Persistence.Services uses Domain.Dtos, so a change to Domain.Dtos can break Persistence.Services, while a change to Persistence.Services can't break Domain.Dtos.
- Position
- Below the diagonal: Persistence.Services uses a module listed above it, which is the healthy direction.
35→12 Persistence.Services uses Domain.Entities✕
- Connections
- 2 pairs of types, where a type in Persistence.Services uses a type in Domain.Entities.
- The types involved
Persistence.Services.AuthService→Domain.Entities.AppUserPersistence.Services.UserService→Domain.Entities.AppUser
- Direction
- Persistence.Services uses Domain.Entities, so a change to Domain.Entities can break Persistence.Services, while a change to Persistence.Services can't break Domain.Entities.
- Position
- Below the diagonal: Persistence.Services uses a module listed above it, which is the healthy direction.
35→22 Persistence.Services uses Application.Services✕
- Connections
- 4 pairs of types, where a type in Persistence.Services uses a type in Application.Services.
- The types involved
Persistence.Services.AuthService→Application.Services.IAuthServicePersistence.Services.AuthService→Application.Services.ITokenHandlerServicePersistence.Services.AuthService→Application.Services.IUserServicePersistence.Services.UserService→Application.Services.IUserService
- Direction
- Persistence.Services uses Application.Services, so a change to Application.Services can break Persistence.Services, while a change to Persistence.Services can't break Application.Services.
- Position
- Below the diagonal: Persistence.Services uses a module listed above it, which is the healthy direction.
36→8 Persistence.Repositories.Articles uses Application.Repositories.Articles✕
- Connections
- 2 pairs of types, where a type in Persistence.Repositories.Articles uses a type in Application.Repositories.Articles.
- The types involved
Persistence.Repositories.Articles.ArticleCommandRepository→Application.Repositories.Articles.IArticleCommandRepositoryPersistence.Repositories.Articles.ArticleQueryRepository→Application.Repositories.Articles.IArticleQueryRepository
- Direction
- Persistence.Repositories.Articles uses Application.Repositories.Articles, so a change to Application.Repositories.Articles can break Persistence.Repositories.Articles, while a change to Persistence.Repositories.Articles can't break Application.Repositories.Articles.
- Position
- Below the diagonal: Persistence.Repositories.Articles uses a module listed above it, which is the healthy direction.
36→23 Persistence.Repositories.Articles uses Persistence.Contexts✕
- Connections
- 2 pairs of types, where a type in Persistence.Repositories.Articles uses a type in Persistence.Contexts.
- The types involved
Persistence.Repositories.Articles.ArticleCommandRepository→Persistence.Contexts.ContextPersistence.Repositories.Articles.ArticleQueryRepository→Persistence.Contexts.Context
- Direction
- Persistence.Repositories.Articles uses Persistence.Contexts, so a change to Persistence.Contexts can break Persistence.Repositories.Articles, while a change to Persistence.Repositories.Articles can't break Persistence.Contexts.
- Position
- Below the diagonal: Persistence.Repositories.Articles uses a module listed above it, which is the healthy direction.
36→34 Persistence.Repositories.Articles uses Persistence.Repositories.BaseRepositories✕
- Connections
- 2 pairs of types, where a type in Persistence.Repositories.Articles uses a type in Persistence.Repositories.BaseRepositories.
- The types involved
Persistence.Repositories.Articles.ArticleCommandRepository→Persistence.Repositories.BaseRepositories.CommandRepositoryPersistence.Repositories.Articles.ArticleQueryRepository→Persistence.Repositories.BaseRepositories.QueryRepository
- Direction
- Persistence.Repositories.Articles uses Persistence.Repositories.BaseRepositories, so a change to Persistence.Repositories.BaseRepositories can break Persistence.Repositories.Articles, while a change to Persistence.Repositories.Articles can't break Persistence.Repositories.BaseRepositories.
- Position
- Below the diagonal: Persistence.Repositories.Articles uses a module listed above it, which is the healthy direction.
37→9 Persistence.Repositories.AuthorImageFiles uses Application.Repositories.AuthorImagesFiles✕
- Connections
- 2 pairs of types, where a type in Persistence.Repositories.AuthorImageFiles uses a type in Application.Repositories.AuthorImagesFiles.
- The types involved
Persistence.Repositories.AuthorImageFiles.AuthorImageFileCommandRepository→Application.Repositories.AuthorImagesFiles.IAuthorImageFileCommandRepositoryPersistence.Repositories.AuthorImageFiles.AuthorImageFileQueryRepository→Application.Repositories.AuthorImagesFiles.IAuthorImageFileQueryRepository
- Direction
- Persistence.Repositories.AuthorImageFiles uses Application.Repositories.AuthorImagesFiles, so a change to Application.Repositories.AuthorImagesFiles can break Persistence.Repositories.AuthorImageFiles, while a change to Persistence.Repositories.AuthorImageFiles can't break Application.Repositories.AuthorImagesFiles.
- Position
- Below the diagonal: Persistence.Repositories.AuthorImageFiles uses a module listed above it, which is the healthy direction.
37→23 Persistence.Repositories.AuthorImageFiles uses Persistence.Contexts✕
- Connections
- 2 pairs of types, where a type in Persistence.Repositories.AuthorImageFiles uses a type in Persistence.Contexts.
- The types involved
Persistence.Repositories.AuthorImageFiles.AuthorImageFileCommandRepository→Persistence.Contexts.ContextPersistence.Repositories.AuthorImageFiles.AuthorImageFileQueryRepository→Persistence.Contexts.Context
- Direction
- Persistence.Repositories.AuthorImageFiles uses Persistence.Contexts, so a change to Persistence.Contexts can break Persistence.Repositories.AuthorImageFiles, while a change to Persistence.Repositories.AuthorImageFiles can't break Persistence.Contexts.
- Position
- Below the diagonal: Persistence.Repositories.AuthorImageFiles uses a module listed above it, which is the healthy direction.
37→34 Persistence.Repositories.AuthorImageFiles uses Persistence.Repositories.BaseRepositories✕
- Connections
- 2 pairs of types, where a type in Persistence.Repositories.AuthorImageFiles uses a type in Persistence.Repositories.BaseRepositories.
- The types involved
Persistence.Repositories.AuthorImageFiles.AuthorImageFileCommandRepository→Persistence.Repositories.BaseRepositories.CommandRepositoryPersistence.Repositories.AuthorImageFiles.AuthorImageFileQueryRepository→Persistence.Repositories.BaseRepositories.QueryRepository
- Direction
- Persistence.Repositories.AuthorImageFiles uses Persistence.Repositories.BaseRepositories, so a change to Persistence.Repositories.BaseRepositories can break Persistence.Repositories.AuthorImageFiles, while a change to Persistence.Repositories.AuthorImageFiles can't break Persistence.Repositories.BaseRepositories.
- Position
- Below the diagonal: Persistence.Repositories.AuthorImageFiles uses a module listed above it, which is the healthy direction.
38→10 Persistence.Repositories.Authors uses Application.Repositories.Authors✕
- Connections
- 2 pairs of types, where a type in Persistence.Repositories.Authors uses a type in Application.Repositories.Authors.
- The types involved
Persistence.Repositories.Authors.AuthorCommandRepository→Application.Repositories.Authors.IAuthorCommandRepositoryPersistence.Repositories.Authors.AuthorQueryRepository→Application.Repositories.Authors.IAuthorQueryRepository
- Direction
- Persistence.Repositories.Authors uses Application.Repositories.Authors, so a change to Application.Repositories.Authors can break Persistence.Repositories.Authors, while a change to Persistence.Repositories.Authors can't break Application.Repositories.Authors.
- Position
- Below the diagonal: Persistence.Repositories.Authors uses a module listed above it, which is the healthy direction.
38→23 Persistence.Repositories.Authors uses Persistence.Contexts✕
- Connections
- 2 pairs of types, where a type in Persistence.Repositories.Authors uses a type in Persistence.Contexts.
- The types involved
Persistence.Repositories.Authors.AuthorCommandRepository→Persistence.Contexts.ContextPersistence.Repositories.Authors.AuthorQueryRepository→Persistence.Contexts.Context
- Direction
- Persistence.Repositories.Authors uses Persistence.Contexts, so a change to Persistence.Contexts can break Persistence.Repositories.Authors, while a change to Persistence.Repositories.Authors can't break Persistence.Contexts.
- Position
- Below the diagonal: Persistence.Repositories.Authors uses a module listed above it, which is the healthy direction.
38→34 Persistence.Repositories.Authors uses Persistence.Repositories.BaseRepositories✕
- Connections
- 2 pairs of types, where a type in Persistence.Repositories.Authors uses a type in Persistence.Repositories.BaseRepositories.
- The types involved
Persistence.Repositories.Authors.AuthorCommandRepository→Persistence.Repositories.BaseRepositories.CommandRepositoryPersistence.Repositories.Authors.AuthorQueryRepository→Persistence.Repositories.BaseRepositories.QueryRepository
- Direction
- Persistence.Repositories.Authors uses Persistence.Repositories.BaseRepositories, so a change to Persistence.Repositories.BaseRepositories can break Persistence.Repositories.Authors, while a change to Persistence.Repositories.Authors can't break Persistence.Repositories.BaseRepositories.
- Position
- Below the diagonal: Persistence.Repositories.Authors uses a module listed above it, which is the healthy direction.
39→11 Persistence.Repositories.Files uses Application.Repositories.Files✕
- Connections
- 2 pairs of types, where a type in Persistence.Repositories.Files uses a type in Application.Repositories.Files.
- The types involved
Persistence.Repositories.Files.FileCommandRepository→Application.Repositories.Files.IFileCommandRepositoryPersistence.Repositories.Files.FileQueryRepository→Application.Repositories.Files.IFileQueryRepository
- Direction
- Persistence.Repositories.Files uses Application.Repositories.Files, so a change to Application.Repositories.Files can break Persistence.Repositories.Files, while a change to Persistence.Repositories.Files can't break Application.Repositories.Files.
- Position
- Below the diagonal: Persistence.Repositories.Files uses a module listed above it, which is the healthy direction.
39→23 Persistence.Repositories.Files uses Persistence.Contexts✕
- Connections
- 2 pairs of types, where a type in Persistence.Repositories.Files uses a type in Persistence.Contexts.
- The types involved
Persistence.Repositories.Files.FileCommandRepository→Persistence.Contexts.ContextPersistence.Repositories.Files.FileQueryRepository→Persistence.Contexts.Context
- Direction
- Persistence.Repositories.Files uses Persistence.Contexts, so a change to Persistence.Contexts can break Persistence.Repositories.Files, while a change to Persistence.Repositories.Files can't break Persistence.Contexts.
- Position
- Below the diagonal: Persistence.Repositories.Files uses a module listed above it, which is the healthy direction.
39→34 Persistence.Repositories.Files uses Persistence.Repositories.BaseRepositories✕
- Connections
- 2 pairs of types, where a type in Persistence.Repositories.Files uses a type in Persistence.Repositories.BaseRepositories.
- The types involved
Persistence.Repositories.Files.FileCommandRepository→Persistence.Repositories.BaseRepositories.CommandRepositoryPersistence.Repositories.Files.FileQueryRepository→Persistence.Repositories.BaseRepositories.QueryRepository
- Direction
- Persistence.Repositories.Files uses Persistence.Repositories.BaseRepositories, so a change to Persistence.Repositories.BaseRepositories can break Persistence.Repositories.Files, while a change to Persistence.Repositories.Files can't break Persistence.Repositories.BaseRepositories.
- Position
- Below the diagonal: Persistence.Repositories.Files uses a module listed above it, which is the healthy direction.
40→15 Web.API.Controllers uses Application.Features.Articles.Commands.RemoveArticle✕
- Connections
- 1 pair of types, where a type in Web.API.Controllers uses a type in Application.Features.Articles.Commands.RemoveArticle.
- The types involved
Web.API.Controllers.ArticlesController→Application.Features.Articles.Commands.RemoveArticle.RemoveArticleCommandRequest
- Direction
- Web.API.Controllers uses Application.Features.Articles.Commands.RemoveArticle, so a change to Application.Features.Articles.Commands.RemoveArticle can break Web.API.Controllers, while a change to Web.API.Controllers can't break Application.Features.Articles.Commands.RemoveArticle.
- Position
- Below the diagonal: Web.API.Controllers uses a module listed above it, which is the healthy direction.
40→16 Web.API.Controllers uses Application.Features.Articles.Commands.UpdateArticle✕
- Connections
- 1 pair of types, where a type in Web.API.Controllers uses a type in Application.Features.Articles.Commands.UpdateArticle.
- The types involved
Web.API.Controllers.ArticlesController→Application.Features.Articles.Commands.UpdateArticle.UpdateArticleCommandRequest
- Direction
- Web.API.Controllers uses Application.Features.Articles.Commands.UpdateArticle, so a change to Application.Features.Articles.Commands.UpdateArticle can break Web.API.Controllers, while a change to Web.API.Controllers can't break Application.Features.Articles.Commands.UpdateArticle.
- Position
- Below the diagonal: Web.API.Controllers uses a module listed above it, which is the healthy direction.
40→17 Web.API.Controllers uses Application.Features.Articles.Queries.GetByIdArticle✕
- Connections
- 1 pair of types, where a type in Web.API.Controllers uses a type in Application.Features.Articles.Queries.GetByIdArticle.
- The types involved
Web.API.Controllers.ArticlesController→Application.Features.Articles.Queries.GetByIdArticle.GetByIdArticleQueryRequest
- Direction
- Web.API.Controllers uses Application.Features.Articles.Queries.GetByIdArticle, so a change to Application.Features.Articles.Queries.GetByIdArticle can break Web.API.Controllers, while a change to Web.API.Controllers can't break Application.Features.Articles.Queries.GetByIdArticle.
- Position
- Below the diagonal: Web.API.Controllers uses a module listed above it, which is the healthy direction.
40→18 Web.API.Controllers uses Application.Features.Authors.Commands.RemoveAuthor✕
- Connections
- 1 pair of types, where a type in Web.API.Controllers uses a type in Application.Features.Authors.Commands.RemoveAuthor.
- The types involved
Web.API.Controllers.AuthorsController→Application.Features.Authors.Commands.RemoveAuthor.RemoveAuthorCommandReqeust
- Direction
- Web.API.Controllers uses Application.Features.Authors.Commands.RemoveAuthor, so a change to Application.Features.Authors.Commands.RemoveAuthor can break Web.API.Controllers, while a change to Web.API.Controllers can't break Application.Features.Authors.Commands.RemoveAuthor.
- Position
- Below the diagonal: Web.API.Controllers uses a module listed above it, which is the healthy direction.
40→19 Web.API.Controllers uses Application.Features.Authors.Commands.RemoveAuthorImage✕
- Connections
- 1 pair of types, where a type in Web.API.Controllers uses a type in Application.Features.Authors.Commands.RemoveAuthorImage.
- The types involved
Web.API.Controllers.AuthorsController→Application.Features.Authors.Commands.RemoveAuthorImage.RemoveAuthorImageCommandRequest
- Direction
- Web.API.Controllers uses Application.Features.Authors.Commands.RemoveAuthorImage, so a change to Application.Features.Authors.Commands.RemoveAuthorImage can break Web.API.Controllers, while a change to Web.API.Controllers can't break Application.Features.Authors.Commands.RemoveAuthorImage.
- Position
- Below the diagonal: Web.API.Controllers uses a module listed above it, which is the healthy direction.
40→20 Web.API.Controllers uses Application.Features.Authors.Commands.UpdateAuthor✕
- Connections
- 1 pair of types, where a type in Web.API.Controllers uses a type in Application.Features.Authors.Commands.UpdateAuthor.
- The types involved
Web.API.Controllers.AuthorsController→Application.Features.Authors.Commands.UpdateAuthor.UpdateAuthorCommandRequest
- Direction
- Web.API.Controllers uses Application.Features.Authors.Commands.UpdateAuthor, so a change to Application.Features.Authors.Commands.UpdateAuthor can break Web.API.Controllers, while a change to Web.API.Controllers can't break Application.Features.Authors.Commands.UpdateAuthor.
- Position
- Below the diagonal: Web.API.Controllers uses a module listed above it, which is the healthy direction.
40→21 Web.API.Controllers uses Application.Features.Authors.Queries.GetByIdAuthor✕
- Connections
- 1 pair of types, where a type in Web.API.Controllers uses a type in Application.Features.Authors.Queries.GetByIdAuthor.
- The types involved
Web.API.Controllers.AuthorsController→Application.Features.Authors.Queries.GetByIdAuthor.GetByIdAuthorQueryReqeust
- Direction
- Web.API.Controllers uses Application.Features.Authors.Queries.GetByIdAuthor, so a change to Application.Features.Authors.Queries.GetByIdAuthor can break Web.API.Controllers, while a change to Web.API.Controllers can't break Application.Features.Authors.Queries.GetByIdAuthor.
- Position
- Below the diagonal: Web.API.Controllers uses a module listed above it, which is the healthy direction.
40→22 Web.API.Controllers uses Application.Services✕
- Connections
- 1 pair of types, where a type in Web.API.Controllers uses a type in Application.Services.
- The types involved
Web.API.Controllers.ArticlesController→Application.Services.IMailService
- Direction
- Web.API.Controllers uses Application.Services, so a change to Application.Services can break Web.API.Controllers, while a change to Web.API.Controllers can't break Application.Services.
- Position
- Below the diagonal: Web.API.Controllers uses a module listed above it, which is the healthy direction.
40→24 Web.API.Controllers uses Application.Features.Articles.Commands.CreateArticle✕
- Connections
- 1 pair of types, where a type in Web.API.Controllers uses a type in Application.Features.Articles.Commands.CreateArticle.
- The types involved
Web.API.Controllers.ArticlesController→Application.Features.Articles.Commands.CreateArticle.CreateArticleCommandRequest
- Direction
- Web.API.Controllers uses Application.Features.Articles.Commands.CreateArticle, so a change to Application.Features.Articles.Commands.CreateArticle can break Web.API.Controllers, while a change to Web.API.Controllers can't break Application.Features.Articles.Commands.CreateArticle.
- Position
- Below the diagonal: Web.API.Controllers uses a module listed above it, which is the healthy direction.
40→25 Web.API.Controllers uses Application.Features.Articles.Queries.GetAllArticle✕
- Connections
- 1 pair of types, where a type in Web.API.Controllers uses a type in Application.Features.Articles.Queries.GetAllArticle.
- The types involved
Web.API.Controllers.ArticlesController→Application.Features.Articles.Queries.GetAllArticle.GetAllArticleQueryRequest
- Direction
- Web.API.Controllers uses Application.Features.Articles.Queries.GetAllArticle, so a change to Application.Features.Articles.Queries.GetAllArticle can break Web.API.Controllers, while a change to Web.API.Controllers can't break Application.Features.Articles.Queries.GetAllArticle.
- Position
- Below the diagonal: Web.API.Controllers uses a module listed above it, which is the healthy direction.
40→26 Web.API.Controllers uses Application.Features.Authors.Commands.CreateAuthor✕
- Connections
- 1 pair of types, where a type in Web.API.Controllers uses a type in Application.Features.Authors.Commands.CreateAuthor.
- The types involved
Web.API.Controllers.AuthorsController→Application.Features.Authors.Commands.CreateAuthor.CreateAuthorCommandRequest
- Direction
- Web.API.Controllers uses Application.Features.Authors.Commands.CreateAuthor, so a change to Application.Features.Authors.Commands.CreateAuthor can break Web.API.Controllers, while a change to Web.API.Controllers can't break Application.Features.Authors.Commands.CreateAuthor.
- Position
- Below the diagonal: Web.API.Controllers uses a module listed above it, which is the healthy direction.
40→27 Web.API.Controllers uses Application.Features.Authors.Commands.CreateAuthorImage✕
- Connections
- 1 pair of types, where a type in Web.API.Controllers uses a type in Application.Features.Authors.Commands.CreateAuthorImage.
- The types involved
Web.API.Controllers.AuthorsController→Application.Features.Authors.Commands.CreateAuthorImage.UploadAuthorImageCommandRequest
- Direction
- Web.API.Controllers uses Application.Features.Authors.Commands.CreateAuthorImage, so a change to Application.Features.Authors.Commands.CreateAuthorImage can break Web.API.Controllers, while a change to Web.API.Controllers can't break Application.Features.Authors.Commands.CreateAuthorImage.
- Position
- Below the diagonal: Web.API.Controllers uses a module listed above it, which is the healthy direction.
40→28 Web.API.Controllers uses Application.Features.Authors.Queries.GetAllAuthor✕
- Connections
- 1 pair of types, where a type in Web.API.Controllers uses a type in Application.Features.Authors.Queries.GetAllAuthor.
- The types involved
Web.API.Controllers.AuthorsController→Application.Features.Authors.Queries.GetAllAuthor.GetAllAuthorQueryRequest
- Direction
- Web.API.Controllers uses Application.Features.Authors.Queries.GetAllAuthor, so a change to Application.Features.Authors.Queries.GetAllAuthor can break Web.API.Controllers, while a change to Web.API.Controllers can't break Application.Features.Authors.Queries.GetAllAuthor.
- Position
- Below the diagonal: Web.API.Controllers uses a module listed above it, which is the healthy direction.
40→29 Web.API.Controllers uses Application.Features.Users.Commands.CreateUser✕
- Connections
- 1 pair of types, where a type in Web.API.Controllers uses a type in Application.Features.Users.Commands.CreateUser.
- The types involved
Web.API.Controllers.UsersController→Application.Features.Users.Commands.CreateUser.CreateUserCommandRequest
- Direction
- Web.API.Controllers uses Application.Features.Users.Commands.CreateUser, so a change to Application.Features.Users.Commands.CreateUser can break Web.API.Controllers, while a change to Web.API.Controllers can't break Application.Features.Users.Commands.CreateUser.
- Position
- Below the diagonal: Web.API.Controllers uses a module listed above it, which is the healthy direction.
40→30 Web.API.Controllers uses Application.Features.Users.Commands.LoginUser✕
- Connections
- 1 pair of types, where a type in Web.API.Controllers uses a type in Application.Features.Users.Commands.LoginUser.
- The types involved
Web.API.Controllers.AuthController→Application.Features.Users.Commands.LoginUser.LoginUserCommandRequest
- Direction
- Web.API.Controllers uses Application.Features.Users.Commands.LoginUser, so a change to Application.Features.Users.Commands.LoginUser can break Web.API.Controllers, while a change to Web.API.Controllers can't break Application.Features.Users.Commands.LoginUser.
- Position
- Below the diagonal: Web.API.Controllers uses a module listed above it, which is the healthy direction.
40→31 Web.API.Controllers uses Application.Features.Users.Commands.RefreshTokenUser✕
- Connections
- 1 pair of types, where a type in Web.API.Controllers uses a type in Application.Features.Users.Commands.RefreshTokenUser.
- The types involved
Web.API.Controllers.AuthController→Application.Features.Users.Commands.RefreshTokenUser.RefreshTokenUserReqeust
- Direction
- Web.API.Controllers uses Application.Features.Users.Commands.RefreshTokenUser, so a change to Application.Features.Users.Commands.RefreshTokenUser can break Web.API.Controllers, while a change to Web.API.Controllers can't break Application.Features.Users.Commands.RefreshTokenUser.
- Position
- Below the diagonal: Web.API.Controllers uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A03:2025 — Software Supply Chain Failures | 10 | High / Critical |
| A05:2025 — Injection | 8 | Medium |
| A07:2025 — Authentication Failures | 1 | High / Critical |
Roadmap
Top priorities: Resolve the 1 No automated tests finding(s) in Code Coverage; Resolve the 1 No tests found finding(s) in Test Distribution; Resolve the 1 Leaked secret finding(s) in Secret Scanning — start with REDACTED.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 1 No tests found finding(s) in Test Distribution. | +13.5 pts | Low | Test Distribution |
| Resolve the 1 Leaked secret finding(s) in Secret Scanning — start with REDACTED. | +10.4 pts | Low | Secret Scanning |
| Resolve the 5 Deprecated finding(s) in Dependency Hygiene — start with REDACTED (4), REDACTED. | +4.9 pts | Low | Dependency Hygiene |
| Resolve the 10 Outdated finding(s) in Dependency Hygiene — start with REDACTED (4), REDACTED (3), REDACTED. | +9.5 pts | Medium | Dependency Hygiene |
| Resolve the 3 Orphaned file finding(s) in Knowledge Freshness — start with Program.cs, AuthorsController.cs, REDACTED. | +4.1 pts | Low | Knowledge Freshness |
| Resolve the 1 No ADRs found finding(s) in ADR Quality. | +3.8 pts | Low | ADR Quality |
| Resolve the 1 No automated tests finding(s) in Code Coverage. | +13.5 pts | High | Code Coverage |
| Add a CI workflow that builds and runs the test suite on every push/PR. | +5.8 pts | Medium | CI/CD gates |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 0.0 | Slop | Dependency Vulnerabilities: Critical CVE: REDACTED |
| REDACTED | 0.6 | Slop | Dependency Vulnerabilities: High CVE: REDACTED |
| REDACTED | 2.8 | Slop | Dependency Vulnerabilities: High CVE: REDACTED |
| REDACTED | 3.5 | Slop | Explicit Debt: WriteOnlyPrivateField |
| REDACTED | 5.8 | Mixed | Dependency Vulnerabilities: Medium CVE: REDACTED |
| REDACTED | 5.9 | Mixed | Dependency Vulnerabilities: Medium CVE: REDACTED |
| REDACTED | 6.9 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| REDACTED | 7.2 | Mixed | Secret Scanning: Leaked secret: REDACTED |
| src/Application/Repositories/BaseRepositories/ICommandRepository.cs | 7.3 | Mixed | Explicit Debt: Dead code: RemoveByIdAsync |
| src/Application/Services/IPaginationService.cs | 7.3 | Mixed | Explicit Debt: Dead code: ListPagination |
| src/Application/Features/Authors/Commands/UploadAuthorImage/UploadAuthorImageCommandHandler.cs | 7.6 | Mixed | Explicit Debt: WriteOnlyPrivateField |
| REDACTED | 7.9 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| src/Application/Repositories/BaseRepositories/IQueryRepository.cs | 8.2 | Near-clean | Explicit Debt: Dead code: GetByFilterAsync |
| README.md | 9.5 | Near-clean | Documentation Quality: Documentation: no build, run or usage example |
| src/Application/Services/IUserService.cs | 9.5 | Near-clean | Naming Consistency: `InsertRefreshToken` returns an awaitable but lacks the `Async` suffix its 18 peers carry |
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 72 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 — 72 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, 91 of 112 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Canine Code Analyzer duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 | ✓ deterministic |
Run transparency — what happened this run
- D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. All 3 significant source file(s) were last meaningfully changed so long ago that no living knowledge remains — nothing since has been substantial enough to re-establish ownership (a broad, mechanical sweep that touches many files shallowly does not count, and neither does no activity at all). There is no concentration to measure, so the bus factor is not scored. This is not a clean bill: nobody currently holds working knowledge of this code (see D34 Knowledge Freshness). Counted over 3 of the 126 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
- D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This kind did not reach the 95 % precision gate in three adjudicated runs (docs/plans/deterministic-engine/adjudication/D19-sample3-v3.md), so by the pre-registered fallback it publishes no row until a re-measurement shows it does. The candidates are counted here, not reported as findings, and the score does not include them.
- D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This kind did not reach the 95 % precision gate in three adjudicated runs (docs/plans/deterministic-engine/adjudication/D19-sample3-v3.md), so by the pre-registered fallback it publishes no row until a re-measurement shows it does. The candidates are counted here, not reported as findings, and the score does not include them.
- D22 Internal API Consistency — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. The loaded project set declares no packable project and no `.Contracts` project, so there is no intentionally-exposed surface for API consistency to be judged over.
- ED5 Idempotency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check classifies a mutation as idempotent when a guard is visible (an exists check, an upsert, an idempotency key or inbox, a versioned or fixed-value write) and as at risk only on positive evidence that a re-run double-applies it (a fresh-identity insert, an accumulation, a growing collection, an unkeyed outbound send or charge). The rest show neither, and they are the majority here, so a score over the classified minority would not describe this repository. That is a limit of the analyzer, not a finding about your code.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
- D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- D8 Code Coverage: Coverage is measured by building and running the test suite inside our isolated image — the target repo is never modified, and nothing on your systems runs. So coverage exists only when the suite builds and runs within the inline time budget; one that needs external services, can't build, or exceeds the budget yields no coverage (D8 then degrades to not-measured, not a low score). Line coverage also says nothing about assertion quality.
- D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
- D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
- D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D18 Solution Shape: Build integrity reflects whether the solution compiled in this environment — a build that needs a private feed, a specific SDK, or a generated file absent from the repo can read as broken when it is merely unreproducible here.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
- D21 Naming Consistency: Naming consistency compares each name with the convention its structural peers follow in this repository: it cannot tell whether a consistently used name is a good one, and languages other than C# and TypeScript are not measured.
- D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
- D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- AX9 CQS / query purity: Handlers are found by interface/name convention — a query handler using neither is not seen. Mutation is a resolved write/publish invocation (SaveChanges/repository/bus), so a write hidden behind a hand-rolled wrapper, reflection, or a string-keyed service locator resolves to a non-persistence type and isn't flagged; it detects that a query writes state, not whether the write is a legitimate read-side cache update. Clean means "no resolved write/publish in a query body", not a proof of CQS purity.
Dimensions
D1 · Cyclomatic Complexity
0 method(s) exceeded the cyclomatic complexity threshold of 15.
D2 · Cognitive Complexity
0 method(s) exceeded the cognitive complexity threshold of 15.
D3 · God Classes
0 god class(es) detected.
D4 · Code Duplication
0 duplicated block group(s) detected.
D5 · Coupling
5 projects, 0 dependency cycle(s), 0 unstable depended-on project(s).
What to do
- Resolve the 1 Off the main sequence finding(s) in Coupling — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
- Stand up a CI pipeline, then gate Coupling in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D6 · Cohesion (LCOM4)
0 of 5 classes have LCOM4 above 3.
D8 · Code Coverage
No automated tests — no test code was found in this repository.
What to do
- Resolve the 1 No automated tests finding(s) in Code Coverage. — One of this dimension's main actionable groups (1 issue-level).
- Stand up a CI pipeline, then gate Code Coverage in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D9 · Test Distribution
No test suite found.
What to do
- Resolve the 1 No tests found finding(s) in Test Distribution. — One of this dimension's main actionable groups (1 recommendation-level).
D12 · Dependency Hygiene
17 outdated, 0 vulnerable, 5 deprecated packages.
What to do
- Resolve the 10 Outdated finding(s) in Dependency Hygiene — start with REDACTED (4), REDACTED (3), REDACTED. — One of this dimension's main actionable groups (10 recommendation-level).
- Resolve the 5 Deprecated finding(s) in Dependency Hygiene — start with REDACTED (4), REDACTED. — One of this dimension's main actionable groups (5 warning-level).
- Stand up a CI pipeline, then gate Dependency Hygiene in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D13 · Secret Scanning
1 secret(s) detected.
What to do
- Resolve the 1 Leaked secret finding(s) in Secret Scanning — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- Stand up a CI pipeline, then gate Secret Scanning in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D14 · License Compliance
0 of 206 packages use a banned license. ★ DEPTH: this repository's MSBuild projects declare 19 direct `PackageReference`(s), and 185 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
2 deducted debt markers + 5 dead symbols across 1923 LoC in the .NET projects (0.8/KLoC) → score 8.3.
What to do
- Resolve the 2 WriteOnlyPrivateField finding(s) in Explicit Debt — start with UploadAuthorImageCommandHandler.cs, REDACTED. — One of this dimension's main actionable groups (2 issue-level).
- Resolve the 5 Dead code finding(s) in Explicit Debt — start with ICommandRepository.cs (2), IPaginationService.cs (2), IQueryRepository.cs. — One of this dimension's main actionable groups (5 warning-level).
- Stand up a CI pipeline, then gate Explicit Debt in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D18 · Solution Shape
5 projects, 126 source files, 1923 hand-written lines of code (1923 production / 0 test — the split is derived per file: test is what its project, its own path, or a compile-guarded region marks as test, and a file carrying no test signal counts as production), plus 1269 generated (machine-written code — designer, scaffolded and tool-emitted files — excluded from quality), 6 inter-project edges.
D19 · Documentation Quality
1 of 2 documentation facets pass in full; short on: F2 example. 1 document(s) read across 6 unit(s).
What to do
- Resolve the 1 Documentation finding(s) in Documentation Quality — start with README.md. — One of this dimension's main actionable groups (1 recommendation-level).
D20 · ADR Quality
No architecture decision records were found.
What to do
- Resolve the 1 No ADRs found finding(s) in ADR Quality. — One of this dimension's main actionable groups (1 recommendation-level).
D21 · Naming Consistency
1 naming inconsistencies among 19 declarations measured against a convention their peers follow.
What to do
- Resolve the 1 `InsertRefreshToken` returns an awaitable but lacks the `Async` suffix… finding(s) in Naming Consistency — start with IUserService.cs. — One of this dimension's main actionable groups (1 recommendation-level).
D26 · Project Cohesion
0 of 5 projects flagged as possibly oversized/incoherent.
D27 · Navigability
99 % of calls cross a namespace and 6 % go through an interface, but 75 % of collaborators are co-located — so following a call takes several hops. Baseline: small — navigation cost is tolerated.
What to do
- Improve Navigability — currently 8.5/10. — 99 % of calls cross a namespace and 6 % go through an interface, but 75 % of collaborators are co-located — so following a call takes several hops. 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)
8 finding(s): 0 critical, 0 high, 8 medium, 0 low.
What to do
- Resolve the 8 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (5), REDACTED (2), REDACTED. — One of this dimension's main actionable groups (8 warning-level).
D30 · Dependency Vulnerabilities
10 finding(s): 1 critical, 5 high, 4 medium, 0 low.
What to do
- Resolve the 5 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (2), REDACTED (2), REDACTED. — One of this dimension's main actionable groups (5 issue-level).
- Resolve the 4 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (2), REDACTED, REDACTED. — One of this dimension's main actionable groups (4 warning-level).
- Resolve the 1 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
D34 · Knowledge Freshness
3 of 3 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is src/Web.API/Program.cs. Counted over 3 of the 126 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
What to do
- Resolve the 3 Orphaned file finding(s) in Knowledge Freshness — start with Program.cs, AuthorsController.cs, REDACTED. — One of this dimension's main actionable groups (3 recommendation-level).
- Resolve the 1 Orphaned files with no living knowledge finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
D35 · Change Coupling
No strong hidden change-coupling between production files.
D39 · IL Efficiency
0 of 172 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
1 end-of-life runtime(s) and 0 end-of-life framework(s), read from 5 platform declaration(s) and 0 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
What to do
- Resolve the 5 End-of-life runtime finding(s) in Platform End-of-Life — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (5 warning-level).
Frontend & cross-cutting dimensions
AX1 · Captive dependencies
AX10 · Code composition
What to do
- The domain core is a small share of production code — check that business logic isn't leaking into the application/infrastructure layers (a thin domain is the anemic-domain smell).
AX3 · Project dependency cycles
AX5 · Architecture & structure
AX6 · Interface segregation
AX7 · Slice cohesion
AX9 · CQS / query purity
C1 · Data Protection
- No data-protection or encryption usage (ASP.NET Data Protection, AES, column encryption, PBKDF2) was found — sensitive data at rest may be unprotected. If TDE/KMS/vault is delegated to infrastructure, ignore.
What to do
- Encrypt sensitive data at rest (ASP.NET Core Data Protection / column encryption) and manage keys in a vault. Skip if delegated to infra (Postgres TDE, KMS, etc.).
- Enforce HTTPS (UseHttpsRedirection / RequireHttpsMetadata) so data in transit is always encrypted.
C2 · Access Controls
- Authorization IS enforced here (via [Authorize]/guards) — this is NOT a claim that endpoints are unprotected. What's missing is NAMED policies (AddAuthorization/AddPolicy, RequireRole/RequireClaim, RequireAuthorization): the access rules are implicit rather than named and testable. Recommendation, not a defect — name the rules so they're reviewable.
What to do
- Add policy-based authorization — name the access rules (AddAuthorization(o => o.AddPolicy(…))) and apply them via [Authorize(Policy = …)] or RequireAuthorization.
GD1 · Unfinished & placeholder code
IC1 · Incompleteness & stubs
- `Handle` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. (×2) — src/Application/Features/Articles/Queries/GetAllArticle/GetAllArticleQueryHandler.cs:22, src/Application/Features/Authors/Queries/GetAllAuthor/GetAllAuthorQueryHandler.cs:22
- `DeleteAsync` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — src/Infrastructure/Storages/Local/LocalStorage.cs:9
What to do
- Remove the dead code that still moves this score: delete dead if(false) / #if false branches and either do the real async work or drop the async keyword from fake-async methods.
M1 · Documentation (README)
What to do
- Add a build/run (quick start) section to the root README — the first thing a newcomer needs.
- Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
- Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
- Add a README to the 5 of 5 project(s) that lack one — worth up to 2 pts.
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
M3 · Folder & project structure
- Only 1/5 projects share a common root namespace — the code's module identity is inconsistent.
What to do
- Start a test surface where your build system looks for one (tests/, test/, spec/, or your ecosystem's test source set) — the separation follows from putting the first tests in the right place.
- Adopt a consistent root-namespace convention (a shared prefix, e.g. Acme.*); short project-file/directory names are fine as long as the RootNamespace is uniform.
P1 · CI/CD gates
- No CI workflow found (.github/workflows, azure-pipelines.yml, .gitlab-ci.yml, …) — changes aren't gated by an automated build/test.
What to do
- Add a CI workflow that builds and runs the test suite on every push/PR.
P2 · Observability
What to do
- Consider OpenTelemetry tracing/metrics and a health-check endpoint for operability.
P3 · Security & performance tooling
- No static application security testing detected. For this repository's stack, add CodeQL's csharp pack, or a .NET security analyzer package (or `semgrep --config=auto`, which runs on any language) — this repository has no CI pipeline yet, so run it locally to clear the existing findings, then make it a step of the first workflow you add so a regression fails the build. What was searched, so you can tell an absence from a miss: the 0 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.
- `REDACTED` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`. — REDACTED:10
What to do
- Run what this repository's stack ships: CodeQL's csharp pack, or a .NET security analyzer package — or `semgrep --config=auto`, which runs on any language — locally for now, since there is no CI pipeline here yet, and as a step of the first workflow you add so a security regression fails the build instead of landing.
- Enable Dependabot/Renovate or a dependency-review gate.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P8 · Schema migrations
PF3 · Async & latency hygiene
S1 · Web-Security Posture
- None of the 11 security response headers the OWASP Secure Headers Project recommends (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options, …) is configured — defense in depth, even when a reverse proxy could set them. (−2.0 on this card.)
- This web host's pipeline is composed here and adds no security response header (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, a frame policy) to what it serves. — src/Web.API/Program.cs:19
- No UseHttpsRedirection/UseHsts and no reverse-proxy signal — transport security is unverified at the app layer. (−2.0 on this card.)
- This web host's pipeline is composed here with no UseHttpsRedirection/UseHsts, and nothing says a reverse proxy terminates TLS in front of it. — src/Web.API/Program.cs:19
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.
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
- `smtp` is a `SmtpClient`, which implements `IDisposable`, and it is created here (line 30). Every use of it in `SendMailAsync` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var smtp = …;`), which releases it at the end of the scope on every path including a throw. — src/Infrastructure/Services/MailService.cs:30
What to do
- Each finding names the value and the span that decides who owns it — the `new` that created it, or the constructor parameter that handed it over. Confirm ownership from that span, then make the disposal match it: release what this type created, leave what it was injected with to whoever created THAT, and drop a finalizer whose type holds nothing unmanaged to release.
X19 · Unrestored process-global state
X2 · Cancellation propagation
- Only 15/46 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. (×31) — src/Persistence/Repositories/BaseRepositories/CommandRepository.cs:15, src/Persistence/Repositories/BaseRepositories/CommandRepository.cs:22, src/Persistence/Repositories/BaseRepositories/CommandRepository.cs:29, …
What to do
- Thread a CancellationToken through async methods so work stops promptly on cancellation.
X20 · Mistyped argument guard
X21 · Side-effecting pattern guard
X22 · Contradicted release guard
X23 · Unguarded diagnostic materialisation
X24 · Document value interpolated into markup unescaped
X25 · Inert configuration knob
X26 · Unsynchronised callback handoff
X27 · Collection changed while being enumerated
X28 · Index access outside its own emptiness guard
X29 · Per-element action decided by a fixed element
X3 · Exception handling
X30 · Support guard that admits what it rejects
X32 · Type resolved by simple name across every loaded assembly
X4 · Structured logging
- Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it. — src/Web.API/Extensions/ConfigurationExceptionHandlerExtension.cs:22
What to do
- Interpolated log message defeats structured logging
X5 · Nullable reference types
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 66% | Adequate — gated by X4 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 84% | Strong | Solid. |
| Maturity | 46% | Weak — gated by D34, M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 22% | Critical — gated by D8, D9, P1, P3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 42% | Weak — gated by C1 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Performance | 100% | Exemplary | Strongest area. |
Unscored — 1 check(s) recorded observations but carry no score
- SC1 Supply-chain hygiene — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Not evidenced — 6 control(s) we could not find positive evidence for
- C3 Audit Trail — Repo shows no audit-logging mechanism (IAuditable, an immutable audit log, an EF SaveChanges interceptor) for sensitive changes — absence of evidence is not evidence of a working control. Record an audit trail in code (or document where it lives) so this dimension can be scored.
- C4 Data Retention — Repo shows no data-retention / TTL / cleanup mechanism for personal data — absence of evidence is not evidence of a working control. Define retention periods and a purge/cleanup job (or TTL) in code, or document where retention is enforced, so this dimension can be scored.
- C5 Data-Subject Rights — Repo shows no corroborated data-subject-rights mechanism (erasure / export-portability / consent) tied to a subject id or GDPR vocabulary — absence of evidence is not evidence of a working control. Implement erasure, data export/portability and consent tracking over the subject's records.
- P4 Deployment & Rollback — not evidenced — no deploy/rollback/approval signal in the repo; absence of evidence is not evidence of a manual release
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
- P6 Release Hygiene — not evidenced — no changelog, version stamp or semver release tag in the repo
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.
- AX2 Stateful singletons — no singleton implementations detected
- AX4 Dependency direction — not applicable to a vertical-slice + CQRS architecture (the inward-dependency rule is for layered/clean styles)
- AX8 Test isolation — no test/production split to check
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXO1 Runtime API surface — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXR1 Runtime accessibility — This repository has no user interface to render — no markup (HTML, Razor, JSX, Vue, Svelte or server templates), no UI framework dependency, no UI component source and no native UI project — so WCAG's runtime success criteria have nothing to apply to here. Not applicable: this is neither a gap in the scan nor a finding about your code.
- AXS1 Runtime exposed surface — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- D10 Test Quality — No tests were found in the analyzed repository to assess for quality.
- D11 Test Reliability — No test suite was found to re-run, so reliability couldn't be assessed. Two searches produced that zero and both came back empty: the classifier that reads the loaded workspace recognised no suite it could run, and a walk of the source on disk — which covers the JS/TS `*.test.*` and `*.spec.*` conventions and probes for a Pester suite — found no test source in any other ecosystem either. Neither search reaches a suite that is missing from the loaded workspace and carries no name either walk recognises, so this is 'no suite found by those two searches', not a verdict that the repository has none.
- D16 Bus Factor — dormant codebase — no living knowledge left to concentrate
- D22 Internal API Consistency — No intentionally-exposed public API to evaluate for consistency.
- D23 Boundary Type-Coupling — small single-context codebase (1,923 production LoC in the .NET projects) — bounded contexts are not needed at this size No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D24 Comment Value — Too few judgeable comments (7 of at least 30); comment value is not applicable here.
- D25 ADR Conformance — no ADRs to check
- D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
- D32 Data Compliance (PII/GDPR) — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
- D36 Supply-chain Provenance & Signing — No CI/build pipeline found (.github/.forgejo/.gitea workflows, .circleci, .buildkite, .woodpecker, .teamcity, .gitlab-ci.yml, .travis.yml, bitbucket-pipelines.yml, .drone.yml, .cirrus.yml, .woodpecker.yml, appveyor.yml, azure-pipelines*.yml, .pipelines/, .vsts-ci/, .azuredevops/, Jenkinsfile); there is no build to attest provenance for.
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D7 Architectural Integrity — no checkable ADRs and no dependency cycles — architectural integrity not assessed
- DM1 Domain Modelling — not scored — this repository shows none of the 3 signals this lens looks for
- ED1 Event-Driven — applicable but not scored (2 of 3 signals for this style — below the bar we score at): a message-bus package; 15 CQRS handler(s)
- ED5 Idempotency — not scored — 5 of 8 retry-prone mutations could not be classified (no visible guard and no positive evidence of a double-applied effect)
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- M4 Documentation accuracy — Not applicable: the 1 current-state document(s) make no claim of a kind M4 checks.
- P12 CI test-gate honesty — no CI workflow found
- 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
- PF1 Benchmark discipline — Performance is assessed only for perf-relevant repos — a packaged library, one that ships benchmarks, or one already using allocation-aware APIs. This repo isn't one, so the Performance lens is not applicable and is excluded from the score.
- PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
- X10 Duplicated predicate — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X7 Silent fallback defaults — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
Critical — 10 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- WriteOnlyPrivateField src/Application/Features/Authors/Commands/UploadAuthorImage/UploadAuthorImageCommandHandler.cs:17
- WriteOnlyPrivateField REDACTED:18
- REDACTED
- REDACTED
- No automated tests
Serious — 66 finding(s)
- Async method without CancellationToken: AddAsync src/Persistence/Repositories/BaseRepositories/CommandRepository.cs:15
- Async method without CancellationToken: AddRangeAsync src/Persistence/Repositories/BaseRepositories/CommandRepository.cs:22
- Async method without CancellationToken: RemoveAsync src/Persistence/Repositories/BaseRepositories/CommandRepository.cs:29
- Async method without CancellationToken: RemoveByIdAsync src/Persistence/Repositories/BaseRepositories/CommandRepository.cs:36
- Async method without CancellationToken: RemoveRangeAsync src/Persistence/Repositories/BaseRepositories/CommandRepository.cs:44
- Async method without CancellationToken: SaveChangesAsync src/Persistence/Repositories/BaseRepositories/CommandRepository.cs:51
- Async method without CancellationToken: UpdateAsync src/Persistence/Repositories/BaseRepositories/CommandRepository.cs:56
- Async method without CancellationToken: GetByFilterAsync src/Persistence/Repositories/BaseRepositories/QueryRepository.cs:24
- Async method without CancellationToken: GetByIdAsync src/Persistence/Repositories/BaseRepositories/QueryRepository.cs:31
- Async method without CancellationToken: RefreshTokenLoginAsync src/Persistence/Services/AuthService.cs:41
- Async method without CancellationToken: ArticleAddedMessageAsync src/Infrastructure/Services/ArticleHubService.cs:14
- Async method without CancellationToken: AuthorAddedMessageAsync src/Infrastructure/Services/AuthorHubService.cs:14
- Async method without CancellationToken: SendMailAsync src/Infrastructure/Services/MailService.cs:15
- Async method without CancellationToken: SendMailAsync src/Infrastructure/Services/MailService.cs:20
- Async method without CancellationToken: UploadAsync src/Infrastructure/Storages/Local/LocalStorage.cs:14
- Async method without CancellationToken: CopyFileAsync src/Infrastructure/Storages/Local/LocalStorage.cs:30
- Async method without CancellationToken: Add REDACTED:32
- Async method without CancellationToken: Update REDACTED:40
- Async method without CancellationToken: Delete REDACTED:48
- Async method without CancellationToken: GetById REDACTED:56
- Async method without CancellationToken: GetAll REDACTED:64
- Async method without CancellationToken: Login REDACTED:22
- Async method without CancellationToken: RefreshToken REDACTED:30
- Async method without CancellationToken: Add src/Web.API/Controllers/AuthorsController.cs:29
- Async method without CancellationToken: Update src/Web.API/Controllers/AuthorsController.cs:37
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Deprecated: FluentValidation.AspNetCore REDACTED:11
- Deprecated: Microsoft.AspNetCore.Http.Features REDACTED:14
- Deprecated: Microsoft.AspNetCore.Mvc.Abstractions REDACTED:15
- Deprecated: Microsoft.AspNetCore.Mvc.Core REDACTED:16
- Deprecated: Microsoft.AspNetCore.Identity REDACTED:10
- Dead code: RemoveByIdAsync src/Application/Repositories/BaseRepositories/ICommandRepository.cs:10
- Dead code: RemoveRangeAsync src/Application/Repositories/BaseRepositories/ICommandRepository.cs:11
- Dead code: GetByFilterAsync src/Application/Repositories/BaseRepositories/IQueryRepository.cs:9
- Dead code: ListPagination src/Application/Services/IPaginationService.cs:8
- Dead code: EnumerablePagination src/Application/Services/IPaginationService.cs:10
- End-of-life runtime: .NET net6.0 REDACTED:4
- End-of-life runtime: .NET net6.0 REDACTED:4
- End-of-life runtime: .NET net6.0 REDACTED:4
- End-of-life runtime: .NET net6.0 REDACTED:4
- End-of-life runtime: .NET net6.0 REDACTED:4
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Fake-async — async method never awaits src/Application/Features/Articles/Queries/GetAllArticle/GetAllArticleQueryHandler.cs:22
- Fake-async — async method never awaits src/Application/Features/Authors/Queries/GetAllAuthor/GetAllAuthorQueryHandler.cs:22
- Fake-async — async method never awaits src/Infrastructure/Storages/Local/LocalStorage.cs:9
- No data-protection/encryption
- Off the main sequence: Domain REDACTED:1
- No CI pipeline
- NuGet dependencies are not locked
- Disposable created and abandoned in the method that made it src/Infrastructure/Services/MailService.cs:30
Minor — 29 finding(s)
- Outdated: Microsoft.EntityFrameworkCore REDACTED:17
- Outdated: Microsoft.EntityFrameworkCore.Tools REDACTED:11
- Outdated: Microsoft.Extensions.DependencyInjection.Abstractions REDACTED:15
- Outdated: Npgsql.EntityFrameworkCore.PostgreSQL REDACTED:16
- Outdated: Microsoft.AspNetCore.Authentication.JwtBearer REDACTED:10
- Outdated: Microsoft.AspNetCore.Identity.EntityFrameworkCore REDACTED:11
- Outdated: Microsoft.AspNetCore.Mvc.NewtonsoftJson REDACTED:15
- Outdated: Microsoft.EntityFrameworkCore.Design REDACTED:16
- Outdated: Serilog.AspNetCore REDACTED:20
- Outdated: Swashbuckle.AspNetCore REDACTED:22
- Orphaned file src/Web.API/Program.cs:1
- Orphaned file src/Web.API/Controllers/AuthorsController.cs:1
- Orphaned file REDACTED:1
- No security response headers detected
- No security response headers detected src/Web.API/Program.cs:19
- No app-layer HTTPS enforcement detected
- No app-layer HTTPS enforcement detected src/Web.API/Program.cs:19
- No named authorization policies
- Documentation: no build, run or usage example README.md:1
- No ADRs found
- `InsertRefreshToken` returns an awaitable but lacks the `Async` suffix its 18 peers carry src/Application/Services/IUserService.cs:9
- Orphaned files with no living knowledge
- No tests found
- No ADRs
- Inconsistent root namespaces
- No SAST
- No dependency-update automation REDACTED:10
- Not all async methods take a CancellationToken
- Interpolated log message defeats structured logging src/Web.API/Extensions/ConfigurationExceptionHandlerExtension.cs:22
Minor — 7 finding(s)
- Outdated: AutoMapper.Extensions.Microsoft.DependencyInjection
- Outdated: FluentValidation.AspNetCore
- Outdated: FluentValidation.DependencyInjectionExtensions
- Outdated: MediatR.Extensions.Microsoft.DependencyInjection
- Outdated: Microsoft.AspNetCore.Mvc.Abstractions
- Outdated: Microsoft.AspNetCore.Mvc.Core
- Outdated: Microsoft.AspNetCore.Identity
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-7528f565232a4af29d62cac13601589a/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-7528f565232a4af29d62cac13601589a/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 src/Persistence/Migrations . | 8 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | dotnet | — | dotnet list MY.OnionArchitecture.sln package --vulnerable --include-transitive --format json | 10 | artifacts/raw/dotnet-vulnerable.json |
| D31 · IaC & Container Security | trivy | — | trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan. | 0 | — |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. | 0 | — |
| D36 · Supply-chain Provenance & Signing | provenance | — | provenance: not applicable — No CI/build pipeline found (.github/.forgejo/.gitea workflows, .circleci, .buildkite, .woodpecker, .teamcity, .gitlab-ci.yml, .travis.yml, bitbucket-pipelines.yml, .drone.yml, .cirrus.yml, .woodpecker.yml, appveyor.yml, azure-pipelines*.yml, .pipelines/, .vsts-ci/, .azuredevops/, Jenkinsfile); there is no build to attest provenance for. | 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-037f790935194f0c91d3cc639848f33d | 0 | artifacts/raw/osv-scanner.json |
Appendix C — Personal-data map
Name — 10 field(s)
- CreateAuthorCommandRequest.Surname src/Application/Features/Authors/Commands/CreateAuthor/CreateAuthorCommandRequest.cs:8
- CreateAuthorCommandResponse.Surname src/Application/Features/Authors/Commands/CreateAuthor/CreateAuthorCommandResponse.cs:7
- UpdateAuthorCommandRequest.Surname src/Application/Features/Authors/Commands/UpdateAuthor/UpdateAuthorCommandRequest.cs:9
- UpdateAuthorCommandResponse.Surname src/Application/Features/Authors/Commands/UpdateAuthor/UpdateAuthorCommandResponse.cs:7
- GetAllAuthorQueryResponse.Surname src/Application/Features/Authors/Queries/GetAllAuthor/GetAllAuthorQueryResponse.cs:7
- GetByIdAuthorQueryResponse.Surname src/Application/Features/Authors/Queries/GetByIdAuthor/GetByIdAuthorQueryResponse.cs:7
- CreateUserCommandRequest.Surname src/Application/Features/Users/Commands/CreateUser/CreateUserCommandRequest.cs:8
- CreateUserDto.Surname src/Domain/Dtos/CreateUserDto.cs:6
- AppUser.Surname src/Domain/Entities/AppUser.cs:8
- Author.Surname src/Domain/Entities/Author.cs:8
Email — 3 field(s)
- CreateUserCommandRequest.Email src/Application/Features/Users/Commands/CreateUser/CreateUserCommandRequest.cs:10
- LoginUserCommandRequest.UsernameOrEmail src/Application/Features/Users/Commands/LoginUser/LoginUserCommandRequest.cs:7
- CreateUserDto.Email src/Domain/Dtos/CreateUserDto.cs:8