Executive summary
Rezakazemi890/Clean-Architecture-CQRS falls short of our standard for production because two passwords or keys sit in the current code and we found no automated security scanning of the code, its secrets or its dependencies. It scores 50 out of 100 and is rated Weak, and all five of its critical findings are security problems.
Production Readiness, at 39, is the weakest lens and counts most in the score. The best first step is replacing the two exposed passwords or keys and switching the old ones off, worth about 9 points. Updating the outdated dependencies comes next, worth about 5 points. Raising Production Readiness to 70 would lift the score to about 58.
Two passwords or keys are open to anyone who can read the repository. Two pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Replacing each exposed password or key and pinning each tool to an exact version would close both risks. Updating the vulnerable packages would fix the package with a known security hole.
The product code is 1,132 lines, about €1,100 to rebuild.
If Production Readiness rose from 39 to 70, the lowest score rated Strong, the score would rise from 50 to about 58.
Fixed since the last survey: 4 findings
- Static Analysis (SAST) · Medium: watchdog-eol-dotnet-runtime-in-workflow REDACTED
- Platform End-of-Life · End-of-life runtime: .NET net9.0 REDACTED
- Cancellation propagation · Async method without CancellationToken: Get REDACTED
- Cancellation propagation · Async method without CancellationToken: Get REDACTED
Rebuild cost: about €1,100 · Estimate
| Cost to rebuild | €390 to €1,900, for 6 to 20 hours of work, under 0.1 person-years for one engineer |
|---|---|
| Difficulty of the problem | High, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.7 at a score of 50. 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,132 lines of product code, of which 58% is declarations and boilerplate, 39% straight logic and 3% logic with branches |
| Comment lines | The estimate prices 1,115 lines. Comment lines count towards the size of 1,132 lines but aren't priced as work. |
| What it is not | Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one. |
Top priorities
Diagnosis: what the measurements show together
Architecture — module dependency graph
Architecture: which parts of the code depend on which
| uses → | 1 (global) | 2 CleanArchitectureCQRS.Application | 3 CleanArchitectureCQRS.Application.DTOs | 4 CleanArchitectureCQRS.Application.Services | 5 CleanArchitectureCQRS.Domain.Consts | 6 CleanArchitectureCQRS.Domain.ValueObjects | 7 CleanArchitectureCQRS.Infrastructure | 8 CleanArchitectureCQRS.Infrastructure.EF | 9 CleanArchitectureCQRS.Infrastructure.EF.Models | 10 CleanArchitectureCQRS.Infrastructure.EF.Options | 11 CleanArchitectureCQRS.Infrastructure.Services | 12 CleanArchitectureCQRS.Shared | 13 CleanArchitectureCQRS.Shared.Abstractions.Commands | 14 CleanArchitectureCQRS.Shared.Abstractions.Domains | 15 CleanArchitectureCQRS.Shared.Abstractions.Exceptions | 16 CleanArchitectureCQRS.Shared.Abstractions.Queries | 17 CleanArchitectureCQRS.Shared.Exceptions | 18 CleanArchitectureCQRS.Shared.Options | 19 CleanArchitectureCQRS.Shared.Services | 20 CleanArchitectureCQRS.Application.Commands | 21 CleanArchitectureCQRS.Application.Exceptions | 22 CleanArchitectureCQRS.Application.Queries | 23 CleanArchitectureCQRS.Domain.Entities | 24 CleanArchitectureCQRS.Domain.Exceptions | 25 CleanArchitectureCQRS.Domain.Policies | 26 CleanArchitectureCQRS.Infrastructure.EF.Queries | 27 CleanArchitectureCQRS.Infrastructure.Logging | 28 CleanArchitectureCQRS.Shared.Commands | 29 CleanArchitectureCQRS.Shared.Queries | 30 CleanArchitectureCQRS.Domain.Events | 31 CleanArchitectureCQRS.Domain.Factories | 32 CleanArchitectureCQRS.Domain.Policies.Gender | 33 CleanArchitectureCQRS.Domain.Repositories | 34 CleanArchitectureCQRS.Infrastructure.EF.Config | 35 CleanArchitectureCQRS.Infrastructure.EF.Contexts | 36 CleanArchitectureCQRS.Application.Commands.Handlers | 37 CleanArchitectureCQRS.Infrastructure.EF.Queries.Handlers | 38 CleanArchitectureCQRS.Infrastructure.EF.Repositories | 39 CleanArchitectureCQRS.Infrastructure.EF.Services | 40 CleanArchitectureCQRS.Api.Controllers |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 (global) | ||||||||||||||||||||||||||||||||||||||||
| 2 CleanArchitectureCQRS.Application | ||||||||||||||||||||||||||||||||||||||||
| 3 CleanArchitectureCQRS.Application.DTOs | ||||||||||||||||||||||||||||||||||||||||
| 4 CleanArchitectureCQRS.Application.Services | ||||||||||||||||||||||||||||||||||||||||
| 5 CleanArchitectureCQRS.Domain.Consts | ||||||||||||||||||||||||||||||||||||||||
| 6 CleanArchitectureCQRS.Domain.ValueObjects | ||||||||||||||||||||||||||||||||||||||||
| 7 CleanArchitectureCQRS.Infrastructure | ||||||||||||||||||||||||||||||||||||||||
| 8 CleanArchitectureCQRS.Infrastructure.EF | ||||||||||||||||||||||||||||||||||||||||
| 9 CleanArchitectureCQRS.Infrastructure.EF.Models | ||||||||||||||||||||||||||||||||||||||||
| 10 CleanArchitectureCQRS.Infrastructure.EF.Options | ||||||||||||||||||||||||||||||||||||||||
| 11 CleanArchitectureCQRS.Infrastructure.Services | ||||||||||||||||||||||||||||||||||||||||
| 12 CleanArchitectureCQRS.Shared | ||||||||||||||||||||||||||||||||||||||||
| 13 CleanArchitectureCQRS.Shared.Abstractions.Commands | ||||||||||||||||||||||||||||||||||||||||
| 14 CleanArchitectureCQRS.Shared.Abstractions.Domains | ||||||||||||||||||||||||||||||||||||||||
| 15 CleanArchitectureCQRS.Shared.Abstractions.Exceptions | ||||||||||||||||||||||||||||||||||||||||
| 16 CleanArchitectureCQRS.Shared.Abstractions.Queries | ||||||||||||||||||||||||||||||||||||||||
| 17 CleanArchitectureCQRS.Shared.Exceptions | ||||||||||||||||||||||||||||||||||||||||
| 18 CleanArchitectureCQRS.Shared.Options | ||||||||||||||||||||||||||||||||||||||||
| 19 CleanArchitectureCQRS.Shared.Services | ||||||||||||||||||||||||||||||||||||||||
| 20 CleanArchitectureCQRS.Application.Commands | 1 | 4 | ||||||||||||||||||||||||||||||||||||||
| 21 CleanArchitectureCQRS.Application.Exceptions | 2 | |||||||||||||||||||||||||||||||||||||||
| 22 CleanArchitectureCQRS.Application.Queries | 2 | |||||||||||||||||||||||||||||||||||||||
| 23 CleanArchitectureCQRS.Domain.Entities | 4 | 1 | ||||||||||||||||||||||||||||||||||||||
| 24 CleanArchitectureCQRS.Domain.Exceptions | 2 | |||||||||||||||||||||||||||||||||||||||
| 25 CleanArchitectureCQRS.Domain.Policies | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 26 CleanArchitectureCQRS.Infrastructure.EF.Queries | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 27 CleanArchitectureCQRS.Infrastructure.Logging | 1 | |||||||||||||||||||||||||||||||||||||||
| 28 CleanArchitectureCQRS.Shared.Commands | 1 | |||||||||||||||||||||||||||||||||||||||
| 29 CleanArchitectureCQRS.Shared.Queries | 2 | |||||||||||||||||||||||||||||||||||||||
| 30 CleanArchitectureCQRS.Domain.Events | 3 | 3 | 3 | |||||||||||||||||||||||||||||||||||||
| 31 CleanArchitectureCQRS.Domain.Factories | 2 | 6 | 2 | 1 | ||||||||||||||||||||||||||||||||||||
| 32 CleanArchitectureCQRS.Domain.Policies.Gender | 2 | 4 | ||||||||||||||||||||||||||||||||||||||
| 33 CleanArchitectureCQRS.Domain.Repositories | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 34 CleanArchitectureCQRS.Infrastructure.EF.Config | 1 | 2 | 1 | |||||||||||||||||||||||||||||||||||||
| 35 CleanArchitectureCQRS.Infrastructure.EF.Contexts | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 36 CleanArchitectureCQRS.Application.Commands.Handlers | 1 | 6 | 4 | 1 | 5 | |||||||||||||||||||||||||||||||||||
| 37 CleanArchitectureCQRS.Infrastructure.EF.Queries.Handlers | 2 | 2 | 2 | 2 | 2 | |||||||||||||||||||||||||||||||||||
| 38 CleanArchitectureCQRS.Infrastructure.EF.Repositories | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 39 CleanArchitectureCQRS.Infrastructure.EF.Services | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 40 CleanArchitectureCQRS.Api.Controllers | 1 | 1 | 1 | 4 | 2 | 1 |
20→5 CleanArchitectureCQRS.Application.Commands uses CleanArchitectureCQRS.Domain.Consts✕
- Connections
- 1 pair of types, where a type in CleanArchitectureCQRS.Application.Commands uses a type in CleanArchitectureCQRS.Domain.Consts.
- The types involved
CleanArchitectureCQRS.Application.Commands.CreateSampleEntityWithItems→CleanArchitectureCQRS.Domain.Consts.Gender
- Direction
- CleanArchitectureCQRS.Application.Commands uses CleanArchitectureCQRS.Domain.Consts, so a change to CleanArchitectureCQRS.Domain.Consts can break CleanArchitectureCQRS.Application.Commands, while a change to CleanArchitectureCQRS.Application.Commands can't break CleanArchitectureCQRS.Domain.Consts.
- Position
- Below the diagonal: CleanArchitectureCQRS.Application.Commands uses a module listed above it, which is the healthy direction.
20→13 CleanArchitectureCQRS.Application.Commands uses CleanArchitectureCQRS.Shared.Abstractions.Commands✕
- Connections
- 4 pairs of types, where a type in CleanArchitectureCQRS.Application.Commands uses a type in CleanArchitectureCQRS.Shared.Abstractions.Commands.
- The types involved
CleanArchitectureCQRS.Application.Commands.CreateSampleEntityWithItems→CleanArchitectureCQRS.Shared.Abstractions.Commands.ICommandCleanArchitectureCQRS.Application.Commands.RemoveSampleEntity→CleanArchitectureCQRS.Shared.Abstractions.Commands.ICommandCleanArchitectureCQRS.Application.Commands.RemoveSampleEntityItem→CleanArchitectureCQRS.Shared.Abstractions.Commands.ICommandCleanArchitectureCQRS.Application.Commands.TakeItem→CleanArchitectureCQRS.Shared.Abstractions.Commands.ICommand
- Direction
- CleanArchitectureCQRS.Application.Commands uses CleanArchitectureCQRS.Shared.Abstractions.Commands, so a change to CleanArchitectureCQRS.Shared.Abstractions.Commands can break CleanArchitectureCQRS.Application.Commands, while a change to CleanArchitectureCQRS.Application.Commands can't break CleanArchitectureCQRS.Shared.Abstractions.Commands.
- Position
- Below the diagonal: CleanArchitectureCQRS.Application.Commands uses a module listed above it, which is the healthy direction.
21→15 CleanArchitectureCQRS.Application.Exceptions uses CleanArchitectureCQRS.Shared.Abstractions.Exceptions✕
- Connections
- 2 pairs of types, where a type in CleanArchitectureCQRS.Application.Exceptions uses a type in CleanArchitectureCQRS.Shared.Abstractions.Exceptions.
- The types involved
CleanArchitectureCQRS.Application.Exceptions.SampleEntityAlreadyExistsException→CleanArchitectureCQRS.Shared.Abstractions.Exceptions.PublicExceptionCleanArchitectureCQRS.Application.Exceptions.SampleEntityNotFound→CleanArchitectureCQRS.Shared.Abstractions.Exceptions.PublicException
- Direction
- CleanArchitectureCQRS.Application.Exceptions uses CleanArchitectureCQRS.Shared.Abstractions.Exceptions, so a change to CleanArchitectureCQRS.Shared.Abstractions.Exceptions can break CleanArchitectureCQRS.Application.Exceptions, while a change to CleanArchitectureCQRS.Application.Exceptions can't break CleanArchitectureCQRS.Shared.Abstractions.Exceptions.
- Position
- Below the diagonal: CleanArchitectureCQRS.Application.Exceptions uses a module listed above it, which is the healthy direction.
22→16 CleanArchitectureCQRS.Application.Queries uses CleanArchitectureCQRS.Shared.Abstractions.Queries✕
- Connections
- 2 pairs of types, where a type in CleanArchitectureCQRS.Application.Queries uses a type in CleanArchitectureCQRS.Shared.Abstractions.Queries.
- The types involved
CleanArchitectureCQRS.Application.Queries.GetSampleEntity→CleanArchitectureCQRS.Shared.Abstractions.Queries.IQueryCleanArchitectureCQRS.Application.Queries.SearchSampleEntity→CleanArchitectureCQRS.Shared.Abstractions.Queries.IQuery
- Direction
- CleanArchitectureCQRS.Application.Queries uses CleanArchitectureCQRS.Shared.Abstractions.Queries, so a change to CleanArchitectureCQRS.Shared.Abstractions.Queries can break CleanArchitectureCQRS.Application.Queries, while a change to CleanArchitectureCQRS.Application.Queries can't break CleanArchitectureCQRS.Shared.Abstractions.Queries.
- Position
- Below the diagonal: CleanArchitectureCQRS.Application.Queries uses a module listed above it, which is the healthy direction.
23→6 CleanArchitectureCQRS.Domain.Entities uses CleanArchitectureCQRS.Domain.ValueObjects✕
- Connections
- 4 pairs of types, where a type in CleanArchitectureCQRS.Domain.Entities uses a type in CleanArchitectureCQRS.Domain.ValueObjects.
- The types involved
CleanArchitectureCQRS.Domain.Entities.SampleEntity→CleanArchitectureCQRS.Domain.ValueObjects.SampleEntityDestinationCleanArchitectureCQRS.Domain.Entities.SampleEntity→CleanArchitectureCQRS.Domain.ValueObjects.SampleEntityIdCleanArchitectureCQRS.Domain.Entities.SampleEntity→CleanArchitectureCQRS.Domain.ValueObjects.SampleEntityItemCleanArchitectureCQRS.Domain.Entities.SampleEntity→CleanArchitectureCQRS.Domain.ValueObjects.SampleEntityName
- Direction
- CleanArchitectureCQRS.Domain.Entities uses CleanArchitectureCQRS.Domain.ValueObjects, so a change to CleanArchitectureCQRS.Domain.ValueObjects can break CleanArchitectureCQRS.Domain.Entities, while a change to CleanArchitectureCQRS.Domain.Entities can't break CleanArchitectureCQRS.Domain.ValueObjects.
- Position
- Below the diagonal: CleanArchitectureCQRS.Domain.Entities uses a module listed above it, which is the healthy direction.
23→14 CleanArchitectureCQRS.Domain.Entities uses CleanArchitectureCQRS.Shared.Abstractions.Domains✕
- Connections
- 1 pair of types, where a type in CleanArchitectureCQRS.Domain.Entities uses a type in CleanArchitectureCQRS.Shared.Abstractions.Domains.
- The types involved
CleanArchitectureCQRS.Domain.Entities.SampleEntity→CleanArchitectureCQRS.Shared.Abstractions.Domains.AggregateRoot
- Direction
- CleanArchitectureCQRS.Domain.Entities uses CleanArchitectureCQRS.Shared.Abstractions.Domains, so a change to CleanArchitectureCQRS.Shared.Abstractions.Domains can break CleanArchitectureCQRS.Domain.Entities, while a change to CleanArchitectureCQRS.Domain.Entities can't break CleanArchitectureCQRS.Shared.Abstractions.Domains.
- Position
- Below the diagonal: CleanArchitectureCQRS.Domain.Entities uses a module listed above it, which is the healthy direction.
24→15 CleanArchitectureCQRS.Domain.Exceptions uses CleanArchitectureCQRS.Shared.Abstractions.Exceptions✕
- Connections
- 2 pairs of types, where a type in CleanArchitectureCQRS.Domain.Exceptions uses a type in CleanArchitectureCQRS.Shared.Abstractions.Exceptions.
- The types involved
CleanArchitectureCQRS.Domain.Exceptions.SampleDuplicateException→CleanArchitectureCQRS.Shared.Abstractions.Exceptions.PublicExceptionCleanArchitectureCQRS.Domain.Exceptions.SampleInvalidException→CleanArchitectureCQRS.Shared.Abstractions.Exceptions.PublicException
- Direction
- CleanArchitectureCQRS.Domain.Exceptions uses CleanArchitectureCQRS.Shared.Abstractions.Exceptions, so a change to CleanArchitectureCQRS.Shared.Abstractions.Exceptions can break CleanArchitectureCQRS.Domain.Exceptions, while a change to CleanArchitectureCQRS.Domain.Exceptions can't break CleanArchitectureCQRS.Shared.Abstractions.Exceptions.
- Position
- Below the diagonal: CleanArchitectureCQRS.Domain.Exceptions uses a module listed above it, which is the healthy direction.
25→5 CleanArchitectureCQRS.Domain.Policies uses CleanArchitectureCQRS.Domain.Consts✕
- Connections
- 1 pair of types, where a type in CleanArchitectureCQRS.Domain.Policies uses a type in CleanArchitectureCQRS.Domain.Consts.
- The types involved
CleanArchitectureCQRS.Domain.Policies.PolicyData→CleanArchitectureCQRS.Domain.Consts.Gender
- Direction
- CleanArchitectureCQRS.Domain.Policies uses CleanArchitectureCQRS.Domain.Consts, so a change to CleanArchitectureCQRS.Domain.Consts can break CleanArchitectureCQRS.Domain.Policies, while a change to CleanArchitectureCQRS.Domain.Policies can't break CleanArchitectureCQRS.Domain.Consts.
- Position
- Below the diagonal: CleanArchitectureCQRS.Domain.Policies uses a module listed above it, which is the healthy direction.
25→6 CleanArchitectureCQRS.Domain.Policies uses CleanArchitectureCQRS.Domain.ValueObjects✕
- Connections
- 2 pairs of types, where a type in CleanArchitectureCQRS.Domain.Policies uses a type in CleanArchitectureCQRS.Domain.ValueObjects.
- The types involved
CleanArchitectureCQRS.Domain.Policies.ISampleEntityItemsPolicy→CleanArchitectureCQRS.Domain.ValueObjects.SampleEntityItemCleanArchitectureCQRS.Domain.Policies.PolicyData→CleanArchitectureCQRS.Domain.ValueObjects.SampleEntityDestination
- Direction
- CleanArchitectureCQRS.Domain.Policies uses CleanArchitectureCQRS.Domain.ValueObjects, so a change to CleanArchitectureCQRS.Domain.ValueObjects can break CleanArchitectureCQRS.Domain.Policies, while a change to CleanArchitectureCQRS.Domain.Policies can't break CleanArchitectureCQRS.Domain.ValueObjects.
- Position
- Below the diagonal: CleanArchitectureCQRS.Domain.Policies uses a module listed above it, which is the healthy direction.
26→3 CleanArchitectureCQRS.Infrastructure.EF.Queries uses CleanArchitectureCQRS.Application.DTOs✕
- Connections
- 1 pair of types, where a type in CleanArchitectureCQRS.Infrastructure.EF.Queries uses a type in CleanArchitectureCQRS.Application.DTOs.
- The types involved
CleanArchitectureCQRS.Infrastructure.EF.Queries.Extensions→CleanArchitectureCQRS.Application.DTOs.SampleEntityDto
- Direction
- CleanArchitectureCQRS.Infrastructure.EF.Queries uses CleanArchitectureCQRS.Application.DTOs, so a change to CleanArchitectureCQRS.Application.DTOs can break CleanArchitectureCQRS.Infrastructure.EF.Queries, while a change to CleanArchitectureCQRS.Infrastructure.EF.Queries can't break CleanArchitectureCQRS.Application.DTOs.
- Position
- Below the diagonal: CleanArchitectureCQRS.Infrastructure.EF.Queries uses a module listed above it, which is the healthy direction.
26→9 CleanArchitectureCQRS.Infrastructure.EF.Queries uses CleanArchitectureCQRS.Infrastructure.EF.Models✕
- Connections
- 1 pair of types, where a type in CleanArchitectureCQRS.Infrastructure.EF.Queries uses a type in CleanArchitectureCQRS.Infrastructure.EF.Models.
- The types involved
CleanArchitectureCQRS.Infrastructure.EF.Queries.Extensions→CleanArchitectureCQRS.Infrastructure.EF.Models.SampleEntityReadModel
- Direction
- CleanArchitectureCQRS.Infrastructure.EF.Queries uses CleanArchitectureCQRS.Infrastructure.EF.Models, so a change to CleanArchitectureCQRS.Infrastructure.EF.Models can break CleanArchitectureCQRS.Infrastructure.EF.Queries, while a change to CleanArchitectureCQRS.Infrastructure.EF.Queries can't break CleanArchitectureCQRS.Infrastructure.EF.Models.
- Position
- Below the diagonal: CleanArchitectureCQRS.Infrastructure.EF.Queries uses a module listed above it, which is the healthy direction.
27→13 CleanArchitectureCQRS.Infrastructure.Logging uses CleanArchitectureCQRS.Shared.Abstractions.Commands✕
- Connections
- 1 pair of types, where a type in CleanArchitectureCQRS.Infrastructure.Logging uses a type in CleanArchitectureCQRS.Shared.Abstractions.Commands.
- The types involved
CleanArchitectureCQRS.Infrastructure.Logging.LoggingCommandHandlerDecorator→CleanArchitectureCQRS.Shared.Abstractions.Commands.ICommandHandler
- Direction
- CleanArchitectureCQRS.Infrastructure.Logging uses CleanArchitectureCQRS.Shared.Abstractions.Commands, so a change to CleanArchitectureCQRS.Shared.Abstractions.Commands can break CleanArchitectureCQRS.Infrastructure.Logging, while a change to CleanArchitectureCQRS.Infrastructure.Logging can't break CleanArchitectureCQRS.Shared.Abstractions.Commands.
- Position
- Below the diagonal: CleanArchitectureCQRS.Infrastructure.Logging uses a module listed above it, which is the healthy direction.
28→13 CleanArchitectureCQRS.Shared.Commands uses CleanArchitectureCQRS.Shared.Abstractions.Commands✕
- Connections
- 1 pair of types, where a type in CleanArchitectureCQRS.Shared.Commands uses a type in CleanArchitectureCQRS.Shared.Abstractions.Commands.
- The types involved
CleanArchitectureCQRS.Shared.Commands.InMemoryCommandDispatcher→CleanArchitectureCQRS.Shared.Abstractions.Commands.ICommandDispatcher
- Direction
- CleanArchitectureCQRS.Shared.Commands uses CleanArchitectureCQRS.Shared.Abstractions.Commands, so a change to CleanArchitectureCQRS.Shared.Abstractions.Commands can break CleanArchitectureCQRS.Shared.Commands, while a change to CleanArchitectureCQRS.Shared.Commands can't break CleanArchitectureCQRS.Shared.Abstractions.Commands.
- Position
- Below the diagonal: CleanArchitectureCQRS.Shared.Commands uses a module listed above it, which is the healthy direction.
29→16 CleanArchitectureCQRS.Shared.Queries uses CleanArchitectureCQRS.Shared.Abstractions.Queries✕
- Connections
- 2 pairs of types, where a type in CleanArchitectureCQRS.Shared.Queries uses a type in CleanArchitectureCQRS.Shared.Abstractions.Queries.
- The types involved
CleanArchitectureCQRS.Shared.Queries.InMemoryQueryDispatcher→CleanArchitectureCQRS.Shared.Abstractions.Queries.IQueryCleanArchitectureCQRS.Shared.Queries.InMemoryQueryDispatcher→CleanArchitectureCQRS.Shared.Abstractions.Queries.IQueryDispatcher
- Direction
- CleanArchitectureCQRS.Shared.Queries uses CleanArchitectureCQRS.Shared.Abstractions.Queries, so a change to CleanArchitectureCQRS.Shared.Abstractions.Queries can break CleanArchitectureCQRS.Shared.Queries, while a change to CleanArchitectureCQRS.Shared.Queries can't break CleanArchitectureCQRS.Shared.Abstractions.Queries.
- Position
- Below the diagonal: CleanArchitectureCQRS.Shared.Queries uses a module listed above it, which is the healthy direction.
30→6 CleanArchitectureCQRS.Domain.Events uses CleanArchitectureCQRS.Domain.ValueObjects✕
- Connections
- 3 pairs of types, where a type in CleanArchitectureCQRS.Domain.Events uses a type in CleanArchitectureCQRS.Domain.ValueObjects.
- The types involved
CleanArchitectureCQRS.Domain.Events.SampleEntityItemAdded→CleanArchitectureCQRS.Domain.ValueObjects.SampleEntityItemCleanArchitectureCQRS.Domain.Events.SampleEntityItemRemoved→CleanArchitectureCQRS.Domain.ValueObjects.SampleEntityItemCleanArchitectureCQRS.Domain.Events.SampleEntityItemTaken→CleanArchitectureCQRS.Domain.ValueObjects.SampleEntityItem
- Direction
- CleanArchitectureCQRS.Domain.Events uses CleanArchitectureCQRS.Domain.ValueObjects, so a change to CleanArchitectureCQRS.Domain.ValueObjects can break CleanArchitectureCQRS.Domain.Events, while a change to CleanArchitectureCQRS.Domain.Events can't break CleanArchitectureCQRS.Domain.ValueObjects.
- Position
- Below the diagonal: CleanArchitectureCQRS.Domain.Events uses a module listed above it, which is the healthy direction.
30→14 CleanArchitectureCQRS.Domain.Events uses CleanArchitectureCQRS.Shared.Abstractions.Domains✕
- Connections
- 3 pairs of types, where a type in CleanArchitectureCQRS.Domain.Events uses a type in CleanArchitectureCQRS.Shared.Abstractions.Domains.
- The types involved
CleanArchitectureCQRS.Domain.Events.SampleEntityItemAdded→CleanArchitectureCQRS.Shared.Abstractions.Domains.IDomainEventCleanArchitectureCQRS.Domain.Events.SampleEntityItemRemoved→CleanArchitectureCQRS.Shared.Abstractions.Domains.IDomainEventCleanArchitectureCQRS.Domain.Events.SampleEntityItemTaken→CleanArchitectureCQRS.Shared.Abstractions.Domains.IDomainEvent
- Direction
- CleanArchitectureCQRS.Domain.Events uses CleanArchitectureCQRS.Shared.Abstractions.Domains, so a change to CleanArchitectureCQRS.Shared.Abstractions.Domains can break CleanArchitectureCQRS.Domain.Events, while a change to CleanArchitectureCQRS.Domain.Events can't break CleanArchitectureCQRS.Shared.Abstractions.Domains.
- Position
- Below the diagonal: CleanArchitectureCQRS.Domain.Events uses a module listed above it, which is the healthy direction.
30→23 CleanArchitectureCQRS.Domain.Events uses CleanArchitectureCQRS.Domain.Entities✕
- Connections
- 3 pairs of types, where a type in CleanArchitectureCQRS.Domain.Events uses a type in CleanArchitectureCQRS.Domain.Entities.
- The types involved
CleanArchitectureCQRS.Domain.Events.SampleEntityItemAdded→CleanArchitectureCQRS.Domain.Entities.SampleEntityCleanArchitectureCQRS.Domain.Events.SampleEntityItemRemoved→CleanArchitectureCQRS.Domain.Entities.SampleEntityCleanArchitectureCQRS.Domain.Events.SampleEntityItemTaken→CleanArchitectureCQRS.Domain.Entities.SampleEntity
- Direction
- CleanArchitectureCQRS.Domain.Events uses CleanArchitectureCQRS.Domain.Entities, so a change to CleanArchitectureCQRS.Domain.Entities can break CleanArchitectureCQRS.Domain.Events, while a change to CleanArchitectureCQRS.Domain.Events can't break CleanArchitectureCQRS.Domain.Entities.
- Position
- Below the diagonal: CleanArchitectureCQRS.Domain.Events uses a module listed above it, which is the healthy direction.
31→5 CleanArchitectureCQRS.Domain.Factories uses CleanArchitectureCQRS.Domain.Consts✕
- Connections
- 2 pairs of types, where a type in CleanArchitectureCQRS.Domain.Factories uses a type in CleanArchitectureCQRS.Domain.Consts.
- The types involved
CleanArchitectureCQRS.Domain.Factories.ISampleEntityFactory→CleanArchitectureCQRS.Domain.Consts.GenderCleanArchitectureCQRS.Domain.Factories.SampleEntityFactory→CleanArchitectureCQRS.Domain.Consts.Gender
- Direction
- CleanArchitectureCQRS.Domain.Factories uses CleanArchitectureCQRS.Domain.Consts, so a change to CleanArchitectureCQRS.Domain.Consts can break CleanArchitectureCQRS.Domain.Factories, while a change to CleanArchitectureCQRS.Domain.Factories can't break CleanArchitectureCQRS.Domain.Consts.
- Position
- Below the diagonal: CleanArchitectureCQRS.Domain.Factories uses a module listed above it, which is the healthy direction.
31→6 CleanArchitectureCQRS.Domain.Factories uses CleanArchitectureCQRS.Domain.ValueObjects✕
- Connections
- 6 pairs of types, where a type in CleanArchitectureCQRS.Domain.Factories uses a type in CleanArchitectureCQRS.Domain.ValueObjects.
- The types involved
CleanArchitectureCQRS.Domain.Factories.ISampleEntityFactory→CleanArchitectureCQRS.Domain.ValueObjects.SampleEntityDestinationCleanArchitectureCQRS.Domain.Factories.ISampleEntityFactory→CleanArchitectureCQRS.Domain.ValueObjects.SampleEntityIdCleanArchitectureCQRS.Domain.Factories.ISampleEntityFactory→CleanArchitectureCQRS.Domain.ValueObjects.SampleEntityNameCleanArchitectureCQRS.Domain.Factories.SampleEntityFactory→CleanArchitectureCQRS.Domain.ValueObjects.SampleEntityDestinationCleanArchitectureCQRS.Domain.Factories.SampleEntityFactory→CleanArchitectureCQRS.Domain.ValueObjects.SampleEntityIdCleanArchitectureCQRS.Domain.Factories.SampleEntityFactory→CleanArchitectureCQRS.Domain.ValueObjects.SampleEntityName
- Direction
- CleanArchitectureCQRS.Domain.Factories uses CleanArchitectureCQRS.Domain.ValueObjects, so a change to CleanArchitectureCQRS.Domain.ValueObjects can break CleanArchitectureCQRS.Domain.Factories, while a change to CleanArchitectureCQRS.Domain.Factories can't break CleanArchitectureCQRS.Domain.ValueObjects.
- Position
- Below the diagonal: CleanArchitectureCQRS.Domain.Factories uses a module listed above it, which is the healthy direction.
31→23 CleanArchitectureCQRS.Domain.Factories uses CleanArchitectureCQRS.Domain.Entities✕
- Connections
- 2 pairs of types, where a type in CleanArchitectureCQRS.Domain.Factories uses a type in CleanArchitectureCQRS.Domain.Entities.
- The types involved
CleanArchitectureCQRS.Domain.Factories.ISampleEntityFactory→CleanArchitectureCQRS.Domain.Entities.SampleEntityCleanArchitectureCQRS.Domain.Factories.SampleEntityFactory→CleanArchitectureCQRS.Domain.Entities.SampleEntity
- Direction
- CleanArchitectureCQRS.Domain.Factories uses CleanArchitectureCQRS.Domain.Entities, so a change to CleanArchitectureCQRS.Domain.Entities can break CleanArchitectureCQRS.Domain.Factories, while a change to CleanArchitectureCQRS.Domain.Factories can't break CleanArchitectureCQRS.Domain.Entities.
- Position
- Below the diagonal: CleanArchitectureCQRS.Domain.Factories uses a module listed above it, which is the healthy direction.
31→25 CleanArchitectureCQRS.Domain.Factories uses CleanArchitectureCQRS.Domain.Policies✕
- Connections
- 1 pair of types, where a type in CleanArchitectureCQRS.Domain.Factories uses a type in CleanArchitectureCQRS.Domain.Policies.
- The types involved
CleanArchitectureCQRS.Domain.Factories.SampleEntityFactory→CleanArchitectureCQRS.Domain.Policies.ISampleEntityItemsPolicy
- Direction
- CleanArchitectureCQRS.Domain.Factories uses CleanArchitectureCQRS.Domain.Policies, so a change to CleanArchitectureCQRS.Domain.Policies can break CleanArchitectureCQRS.Domain.Factories, while a change to CleanArchitectureCQRS.Domain.Factories can't break CleanArchitectureCQRS.Domain.Policies.
- Position
- Below the diagonal: CleanArchitectureCQRS.Domain.Factories uses a module listed above it, which is the healthy direction.
32→6 CleanArchitectureCQRS.Domain.Policies.Gender uses CleanArchitectureCQRS.Domain.ValueObjects✕
- Connections
- 2 pairs of types, where a type in CleanArchitectureCQRS.Domain.Policies.Gender uses a type in CleanArchitectureCQRS.Domain.ValueObjects.
- The types involved
CleanArchitectureCQRS.Domain.Policies.Gender.FemaleGenderPolicy→CleanArchitectureCQRS.Domain.ValueObjects.SampleEntityItemCleanArchitectureCQRS.Domain.Policies.Gender.MaleGenderPolicy→CleanArchitectureCQRS.Domain.ValueObjects.SampleEntityItem
- Direction
- CleanArchitectureCQRS.Domain.Policies.Gender uses CleanArchitectureCQRS.Domain.ValueObjects, so a change to CleanArchitectureCQRS.Domain.ValueObjects can break CleanArchitectureCQRS.Domain.Policies.Gender, while a change to CleanArchitectureCQRS.Domain.Policies.Gender can't break CleanArchitectureCQRS.Domain.ValueObjects.
- Position
- Below the diagonal: CleanArchitectureCQRS.Domain.Policies.Gender uses a module listed above it, which is the healthy direction.
32→25 CleanArchitectureCQRS.Domain.Policies.Gender uses CleanArchitectureCQRS.Domain.Policies✕
- Connections
- 4 pairs of types, where a type in CleanArchitectureCQRS.Domain.Policies.Gender uses a type in CleanArchitectureCQRS.Domain.Policies.
- The types involved
CleanArchitectureCQRS.Domain.Policies.Gender.FemaleGenderPolicy→CleanArchitectureCQRS.Domain.Policies.ISampleEntityItemsPolicyCleanArchitectureCQRS.Domain.Policies.Gender.FemaleGenderPolicy→CleanArchitectureCQRS.Domain.Policies.PolicyDataCleanArchitectureCQRS.Domain.Policies.Gender.MaleGenderPolicy→CleanArchitectureCQRS.Domain.Policies.ISampleEntityItemsPolicyCleanArchitectureCQRS.Domain.Policies.Gender.MaleGenderPolicy→CleanArchitectureCQRS.Domain.Policies.PolicyData
- Direction
- CleanArchitectureCQRS.Domain.Policies.Gender uses CleanArchitectureCQRS.Domain.Policies, so a change to CleanArchitectureCQRS.Domain.Policies can break CleanArchitectureCQRS.Domain.Policies.Gender, while a change to CleanArchitectureCQRS.Domain.Policies.Gender can't break CleanArchitectureCQRS.Domain.Policies.
- Position
- Below the diagonal: CleanArchitectureCQRS.Domain.Policies.Gender uses a module listed above it, which is the healthy direction.
33→6 CleanArchitectureCQRS.Domain.Repositories uses CleanArchitectureCQRS.Domain.ValueObjects✕
- Connections
- 1 pair of types, where a type in CleanArchitectureCQRS.Domain.Repositories uses a type in CleanArchitectureCQRS.Domain.ValueObjects.
- The types involved
CleanArchitectureCQRS.Domain.Repositories.ISampleEntityRepository→CleanArchitectureCQRS.Domain.ValueObjects.SampleEntityId
- Direction
- CleanArchitectureCQRS.Domain.Repositories uses CleanArchitectureCQRS.Domain.ValueObjects, so a change to CleanArchitectureCQRS.Domain.ValueObjects can break CleanArchitectureCQRS.Domain.Repositories, while a change to CleanArchitectureCQRS.Domain.Repositories can't break CleanArchitectureCQRS.Domain.ValueObjects.
- Position
- Below the diagonal: CleanArchitectureCQRS.Domain.Repositories uses a module listed above it, which is the healthy direction.
33→23 CleanArchitectureCQRS.Domain.Repositories uses CleanArchitectureCQRS.Domain.Entities✕
- Connections
- 1 pair of types, where a type in CleanArchitectureCQRS.Domain.Repositories uses a type in CleanArchitectureCQRS.Domain.Entities.
- The types involved
CleanArchitectureCQRS.Domain.Repositories.ISampleEntityRepository→CleanArchitectureCQRS.Domain.Entities.SampleEntity
- Direction
- CleanArchitectureCQRS.Domain.Repositories uses CleanArchitectureCQRS.Domain.Entities, so a change to CleanArchitectureCQRS.Domain.Entities can break CleanArchitectureCQRS.Domain.Repositories, while a change to CleanArchitectureCQRS.Domain.Repositories can't break CleanArchitectureCQRS.Domain.Entities.
- Position
- Below the diagonal: CleanArchitectureCQRS.Domain.Repositories uses a module listed above it, which is the healthy direction.
34→6 CleanArchitectureCQRS.Infrastructure.EF.Config uses CleanArchitectureCQRS.Domain.ValueObjects✕
- Connections
- 1 pair of types, where a type in CleanArchitectureCQRS.Infrastructure.EF.Config uses a type in CleanArchitectureCQRS.Domain.ValueObjects.
- The types involved
CleanArchitectureCQRS.Infrastructure.EF.Config.WriteConfiguration→CleanArchitectureCQRS.Domain.ValueObjects.SampleEntityItem
- Direction
- CleanArchitectureCQRS.Infrastructure.EF.Config uses CleanArchitectureCQRS.Domain.ValueObjects, so a change to CleanArchitectureCQRS.Domain.ValueObjects can break CleanArchitectureCQRS.Infrastructure.EF.Config, while a change to CleanArchitectureCQRS.Infrastructure.EF.Config can't break CleanArchitectureCQRS.Domain.ValueObjects.
- Position
- Below the diagonal: CleanArchitectureCQRS.Infrastructure.EF.Config uses a module listed above it, which is the healthy direction.
34→9 CleanArchitectureCQRS.Infrastructure.EF.Config uses CleanArchitectureCQRS.Infrastructure.EF.Models✕
- Connections
- 2 pairs of types, where a type in CleanArchitectureCQRS.Infrastructure.EF.Config uses a type in CleanArchitectureCQRS.Infrastructure.EF.Models.
- The types involved
CleanArchitectureCQRS.Infrastructure.EF.Config.ReadConfiguration→CleanArchitectureCQRS.Infrastructure.EF.Models.SampleEntityItemReadModelCleanArchitectureCQRS.Infrastructure.EF.Config.ReadConfiguration→CleanArchitectureCQRS.Infrastructure.EF.Models.SampleEntityReadModel
- Direction
- CleanArchitectureCQRS.Infrastructure.EF.Config uses CleanArchitectureCQRS.Infrastructure.EF.Models, so a change to CleanArchitectureCQRS.Infrastructure.EF.Models can break CleanArchitectureCQRS.Infrastructure.EF.Config, while a change to CleanArchitectureCQRS.Infrastructure.EF.Config can't break CleanArchitectureCQRS.Infrastructure.EF.Models.
- Position
- Below the diagonal: CleanArchitectureCQRS.Infrastructure.EF.Config uses a module listed above it, which is the healthy direction.
34→23 CleanArchitectureCQRS.Infrastructure.EF.Config uses CleanArchitectureCQRS.Domain.Entities✕
- Connections
- 1 pair of types, where a type in CleanArchitectureCQRS.Infrastructure.EF.Config uses a type in CleanArchitectureCQRS.Domain.Entities.
- The types involved
CleanArchitectureCQRS.Infrastructure.EF.Config.WriteConfiguration→CleanArchitectureCQRS.Domain.Entities.SampleEntity
- Direction
- CleanArchitectureCQRS.Infrastructure.EF.Config uses CleanArchitectureCQRS.Domain.Entities, so a change to CleanArchitectureCQRS.Domain.Entities can break CleanArchitectureCQRS.Infrastructure.EF.Config, while a change to CleanArchitectureCQRS.Infrastructure.EF.Config can't break CleanArchitectureCQRS.Domain.Entities.
- Position
- Below the diagonal: CleanArchitectureCQRS.Infrastructure.EF.Config uses a module listed above it, which is the healthy direction.
35→9 CleanArchitectureCQRS.Infrastructure.EF.Contexts uses CleanArchitectureCQRS.Infrastructure.EF.Models✕
- Connections
- 1 pair of types, where a type in CleanArchitectureCQRS.Infrastructure.EF.Contexts uses a type in CleanArchitectureCQRS.Infrastructure.EF.Models.
- The types involved
CleanArchitectureCQRS.Infrastructure.EF.Contexts.ReadDbContext→CleanArchitectureCQRS.Infrastructure.EF.Models.SampleEntityReadModel
- Direction
- CleanArchitectureCQRS.Infrastructure.EF.Contexts uses CleanArchitectureCQRS.Infrastructure.EF.Models, so a change to CleanArchitectureCQRS.Infrastructure.EF.Models can break CleanArchitectureCQRS.Infrastructure.EF.Contexts, while a change to CleanArchitectureCQRS.Infrastructure.EF.Contexts can't break CleanArchitectureCQRS.Infrastructure.EF.Models.
- Position
- Below the diagonal: CleanArchitectureCQRS.Infrastructure.EF.Contexts uses a module listed above it, which is the healthy direction.
35→23 CleanArchitectureCQRS.Infrastructure.EF.Contexts uses CleanArchitectureCQRS.Domain.Entities✕
- Connections
- 1 pair of types, where a type in CleanArchitectureCQRS.Infrastructure.EF.Contexts uses a type in CleanArchitectureCQRS.Domain.Entities.
- The types involved
CleanArchitectureCQRS.Infrastructure.EF.Contexts.WriteDbContext→CleanArchitectureCQRS.Domain.Entities.SampleEntity
- Direction
- CleanArchitectureCQRS.Infrastructure.EF.Contexts uses CleanArchitectureCQRS.Domain.Entities, so a change to CleanArchitectureCQRS.Domain.Entities can break CleanArchitectureCQRS.Infrastructure.EF.Contexts, while a change to CleanArchitectureCQRS.Infrastructure.EF.Contexts can't break CleanArchitectureCQRS.Domain.Entities.
- Position
- Below the diagonal: CleanArchitectureCQRS.Infrastructure.EF.Contexts uses a module listed above it, which is the healthy direction.
36→4 CleanArchitectureCQRS.Application.Commands.Handlers uses CleanArchitectureCQRS.Application.Services✕
- Connections
- 1 pair of types, where a type in CleanArchitectureCQRS.Application.Commands.Handlers uses a type in CleanArchitectureCQRS.Application.Services.
- The types involved
CleanArchitectureCQRS.Application.Commands.Handlers.CreateSampleEntityWithItemHandler→CleanArchitectureCQRS.Application.Services.ISampleEntityReadService
- Direction
- CleanArchitectureCQRS.Application.Commands.Handlers uses CleanArchitectureCQRS.Application.Services, so a change to CleanArchitectureCQRS.Application.Services can break CleanArchitectureCQRS.Application.Commands.Handlers, while a change to CleanArchitectureCQRS.Application.Commands.Handlers can't break CleanArchitectureCQRS.Application.Services.
- Position
- Below the diagonal: CleanArchitectureCQRS.Application.Commands.Handlers uses a module listed above it, which is the healthy direction.
36→13 CleanArchitectureCQRS.Application.Commands.Handlers uses CleanArchitectureCQRS.Shared.Abstractions.Commands✕
- Connections
- 6 pairs of types, where a type in CleanArchitectureCQRS.Application.Commands.Handlers uses a type in CleanArchitectureCQRS.Shared.Abstractions.Commands.
- The types involved
CleanArchitectureCQRS.Application.Commands.Handlers.AddSampleEntityItem→CleanArchitectureCQRS.Shared.Abstractions.Commands.ICommandCleanArchitectureCQRS.Application.Commands.Handlers.AddSampleEntityItemHandler→CleanArchitectureCQRS.Shared.Abstractions.Commands.ICommandHandlerCleanArchitectureCQRS.Application.Commands.Handlers.CreateSampleEntityWithItemHandler→CleanArchitectureCQRS.Shared.Abstractions.Commands.ICommandHandlerCleanArchitectureCQRS.Application.Commands.Handlers.RemoveSampleEntityHandler→CleanArchitectureCQRS.Shared.Abstractions.Commands.ICommandHandlerCleanArchitectureCQRS.Application.Commands.Handlers.RemoveSampleEntityItemHandler→CleanArchitectureCQRS.Shared.Abstractions.Commands.ICommandHandlerCleanArchitectureCQRS.Application.Commands.Handlers.TakeItemHandler→CleanArchitectureCQRS.Shared.Abstractions.Commands.ICommandHandler
- Direction
- CleanArchitectureCQRS.Application.Commands.Handlers uses CleanArchitectureCQRS.Shared.Abstractions.Commands, so a change to CleanArchitectureCQRS.Shared.Abstractions.Commands can break CleanArchitectureCQRS.Application.Commands.Handlers, while a change to CleanArchitectureCQRS.Application.Commands.Handlers can't break CleanArchitectureCQRS.Shared.Abstractions.Commands.
- Position
- Below the diagonal: CleanArchitectureCQRS.Application.Commands.Handlers uses a module listed above it, which is the healthy direction.
36→20 CleanArchitectureCQRS.Application.Commands.Handlers uses CleanArchitectureCQRS.Application.Commands✕
- Connections
- 4 pairs of types, where a type in CleanArchitectureCQRS.Application.Commands.Handlers uses a type in CleanArchitectureCQRS.Application.Commands.
- The types involved
CleanArchitectureCQRS.Application.Commands.Handlers.CreateSampleEntityWithItemHandler→CleanArchitectureCQRS.Application.Commands.CreateSampleEntityWithItemsCleanArchitectureCQRS.Application.Commands.Handlers.RemoveSampleEntityHandler→CleanArchitectureCQRS.Application.Commands.RemoveSampleEntityCleanArchitectureCQRS.Application.Commands.Handlers.RemoveSampleEntityItemHandler→CleanArchitectureCQRS.Application.Commands.RemoveSampleEntityItemCleanArchitectureCQRS.Application.Commands.Handlers.TakeItemHandler→CleanArchitectureCQRS.Application.Commands.TakeItem
- Direction
- CleanArchitectureCQRS.Application.Commands.Handlers uses CleanArchitectureCQRS.Application.Commands, so a change to CleanArchitectureCQRS.Application.Commands can break CleanArchitectureCQRS.Application.Commands.Handlers, while a change to CleanArchitectureCQRS.Application.Commands.Handlers can't break CleanArchitectureCQRS.Application.Commands.
- Position
- Below the diagonal: CleanArchitectureCQRS.Application.Commands.Handlers uses a module listed above it, which is the healthy direction.
36→31 CleanArchitectureCQRS.Application.Commands.Handlers uses CleanArchitectureCQRS.Domain.Factories✕
- Connections
- 1 pair of types, where a type in CleanArchitectureCQRS.Application.Commands.Handlers uses a type in CleanArchitectureCQRS.Domain.Factories.
- The types involved
CleanArchitectureCQRS.Application.Commands.Handlers.CreateSampleEntityWithItemHandler→CleanArchitectureCQRS.Domain.Factories.ISampleEntityFactory
- Direction
- CleanArchitectureCQRS.Application.Commands.Handlers uses CleanArchitectureCQRS.Domain.Factories, so a change to CleanArchitectureCQRS.Domain.Factories can break CleanArchitectureCQRS.Application.Commands.Handlers, while a change to CleanArchitectureCQRS.Application.Commands.Handlers can't break CleanArchitectureCQRS.Domain.Factories.
- Position
- Below the diagonal: CleanArchitectureCQRS.Application.Commands.Handlers uses a module listed above it, which is the healthy direction.
36→33 CleanArchitectureCQRS.Application.Commands.Handlers uses CleanArchitectureCQRS.Domain.Repositories✕
- Connections
- 5 pairs of types, where a type in CleanArchitectureCQRS.Application.Commands.Handlers uses a type in CleanArchitectureCQRS.Domain.Repositories.
- The types involved
CleanArchitectureCQRS.Application.Commands.Handlers.AddSampleEntityItemHandler→CleanArchitectureCQRS.Domain.Repositories.ISampleEntityRepositoryCleanArchitectureCQRS.Application.Commands.Handlers.CreateSampleEntityWithItemHandler→CleanArchitectureCQRS.Domain.Repositories.ISampleEntityRepositoryCleanArchitectureCQRS.Application.Commands.Handlers.RemoveSampleEntityHandler→CleanArchitectureCQRS.Domain.Repositories.ISampleEntityRepositoryCleanArchitectureCQRS.Application.Commands.Handlers.RemoveSampleEntityItemHandler→CleanArchitectureCQRS.Domain.Repositories.ISampleEntityRepositoryCleanArchitectureCQRS.Application.Commands.Handlers.TakeItemHandler→CleanArchitectureCQRS.Domain.Repositories.ISampleEntityRepository
- Direction
- CleanArchitectureCQRS.Application.Commands.Handlers uses CleanArchitectureCQRS.Domain.Repositories, so a change to CleanArchitectureCQRS.Domain.Repositories can break CleanArchitectureCQRS.Application.Commands.Handlers, while a change to CleanArchitectureCQRS.Application.Commands.Handlers can't break CleanArchitectureCQRS.Domain.Repositories.
- Position
- Below the diagonal: CleanArchitectureCQRS.Application.Commands.Handlers uses a module listed above it, which is the healthy direction.
37→3 CleanArchitectureCQRS.Infrastructure.EF.Queries.Handlers uses CleanArchitectureCQRS.Application.DTOs✕
- Connections
- 2 pairs of types, where a type in CleanArchitectureCQRS.Infrastructure.EF.Queries.Handlers uses a type in CleanArchitectureCQRS.Application.DTOs.
- The types involved
CleanArchitectureCQRS.Infrastructure.EF.Queries.Handlers.GetSampleEntityHandler→CleanArchitectureCQRS.Application.DTOs.SampleEntityDtoCleanArchitectureCQRS.Infrastructure.EF.Queries.Handlers.SearchSampleEntityHandler→CleanArchitectureCQRS.Application.DTOs.SampleEntityDto
- Direction
- CleanArchitectureCQRS.Infrastructure.EF.Queries.Handlers uses CleanArchitectureCQRS.Application.DTOs, so a change to CleanArchitectureCQRS.Application.DTOs can break CleanArchitectureCQRS.Infrastructure.EF.Queries.Handlers, while a change to CleanArchitectureCQRS.Infrastructure.EF.Queries.Handlers can't break CleanArchitectureCQRS.Application.DTOs.
- Position
- Below the diagonal: CleanArchitectureCQRS.Infrastructure.EF.Queries.Handlers uses a module listed above it, which is the healthy direction.
37→9 CleanArchitectureCQRS.Infrastructure.EF.Queries.Handlers uses CleanArchitectureCQRS.Infrastructure.EF.Models✕
- Connections
- 2 pairs of types, where a type in CleanArchitectureCQRS.Infrastructure.EF.Queries.Handlers uses a type in CleanArchitectureCQRS.Infrastructure.EF.Models.
- The types involved
CleanArchitectureCQRS.Infrastructure.EF.Queries.Handlers.GetSampleEntityHandler→CleanArchitectureCQRS.Infrastructure.EF.Models.SampleEntityReadModelCleanArchitectureCQRS.Infrastructure.EF.Queries.Handlers.SearchSampleEntityHandler→CleanArchitectureCQRS.Infrastructure.EF.Models.SampleEntityReadModel
- Direction
- CleanArchitectureCQRS.Infrastructure.EF.Queries.Handlers uses CleanArchitectureCQRS.Infrastructure.EF.Models, so a change to CleanArchitectureCQRS.Infrastructure.EF.Models can break CleanArchitectureCQRS.Infrastructure.EF.Queries.Handlers, while a change to CleanArchitectureCQRS.Infrastructure.EF.Queries.Handlers can't break CleanArchitectureCQRS.Infrastructure.EF.Models.
- Position
- Below the diagonal: CleanArchitectureCQRS.Infrastructure.EF.Queries.Handlers uses a module listed above it, which is the healthy direction.
37→16 CleanArchitectureCQRS.Infrastructure.EF.Queries.Handlers uses CleanArchitectureCQRS.Shared.Abstractions.Queries✕
- Connections
- 2 pairs of types, where a type in CleanArchitectureCQRS.Infrastructure.EF.Queries.Handlers uses a type in CleanArchitectureCQRS.Shared.Abstractions.Queries.
- The types involved
CleanArchitectureCQRS.Infrastructure.EF.Queries.Handlers.GetSampleEntityHandler→CleanArchitectureCQRS.Shared.Abstractions.Queries.IQueryHandlerCleanArchitectureCQRS.Infrastructure.EF.Queries.Handlers.SearchSampleEntityHandler→CleanArchitectureCQRS.Shared.Abstractions.Queries.IQueryHandler
- Direction
- CleanArchitectureCQRS.Infrastructure.EF.Queries.Handlers uses CleanArchitectureCQRS.Shared.Abstractions.Queries, so a change to CleanArchitectureCQRS.Shared.Abstractions.Queries can break CleanArchitectureCQRS.Infrastructure.EF.Queries.Handlers, while a change to CleanArchitectureCQRS.Infrastructure.EF.Queries.Handlers can't break CleanArchitectureCQRS.Shared.Abstractions.Queries.
- Position
- Below the diagonal: CleanArchitectureCQRS.Infrastructure.EF.Queries.Handlers uses a module listed above it, which is the healthy direction.
37→22 CleanArchitectureCQRS.Infrastructure.EF.Queries.Handlers uses CleanArchitectureCQRS.Application.Queries✕
- Connections
- 2 pairs of types, where a type in CleanArchitectureCQRS.Infrastructure.EF.Queries.Handlers uses a type in CleanArchitectureCQRS.Application.Queries.
- The types involved
CleanArchitectureCQRS.Infrastructure.EF.Queries.Handlers.GetSampleEntityHandler→CleanArchitectureCQRS.Application.Queries.GetSampleEntityCleanArchitectureCQRS.Infrastructure.EF.Queries.Handlers.SearchSampleEntityHandler→CleanArchitectureCQRS.Application.Queries.SearchSampleEntity
- Direction
- CleanArchitectureCQRS.Infrastructure.EF.Queries.Handlers uses CleanArchitectureCQRS.Application.Queries, so a change to CleanArchitectureCQRS.Application.Queries can break CleanArchitectureCQRS.Infrastructure.EF.Queries.Handlers, while a change to CleanArchitectureCQRS.Infrastructure.EF.Queries.Handlers can't break CleanArchitectureCQRS.Application.Queries.
- Position
- Below the diagonal: CleanArchitectureCQRS.Infrastructure.EF.Queries.Handlers uses a module listed above it, which is the healthy direction.
37→35 CleanArchitectureCQRS.Infrastructure.EF.Queries.Handlers uses CleanArchitectureCQRS.Infrastructure.EF.Contexts✕
- Connections
- 2 pairs of types, where a type in CleanArchitectureCQRS.Infrastructure.EF.Queries.Handlers uses a type in CleanArchitectureCQRS.Infrastructure.EF.Contexts.
- The types involved
CleanArchitectureCQRS.Infrastructure.EF.Queries.Handlers.GetSampleEntityHandler→CleanArchitectureCQRS.Infrastructure.EF.Contexts.ReadDbContextCleanArchitectureCQRS.Infrastructure.EF.Queries.Handlers.SearchSampleEntityHandler→CleanArchitectureCQRS.Infrastructure.EF.Contexts.ReadDbContext
- Direction
- CleanArchitectureCQRS.Infrastructure.EF.Queries.Handlers uses CleanArchitectureCQRS.Infrastructure.EF.Contexts, so a change to CleanArchitectureCQRS.Infrastructure.EF.Contexts can break CleanArchitectureCQRS.Infrastructure.EF.Queries.Handlers, while a change to CleanArchitectureCQRS.Infrastructure.EF.Queries.Handlers can't break CleanArchitectureCQRS.Infrastructure.EF.Contexts.
- Position
- Below the diagonal: CleanArchitectureCQRS.Infrastructure.EF.Queries.Handlers uses a module listed above it, which is the healthy direction.
38→6 CleanArchitectureCQRS.Infrastructure.EF.Repositories uses CleanArchitectureCQRS.Domain.ValueObjects✕
- Connections
- 1 pair of types, where a type in CleanArchitectureCQRS.Infrastructure.EF.Repositories uses a type in CleanArchitectureCQRS.Domain.ValueObjects.
- The types involved
CleanArchitectureCQRS.Infrastructure.EF.Repositories.SampleEntityRepository→CleanArchitectureCQRS.Domain.ValueObjects.SampleEntityId
- Direction
- CleanArchitectureCQRS.Infrastructure.EF.Repositories uses CleanArchitectureCQRS.Domain.ValueObjects, so a change to CleanArchitectureCQRS.Domain.ValueObjects can break CleanArchitectureCQRS.Infrastructure.EF.Repositories, while a change to CleanArchitectureCQRS.Infrastructure.EF.Repositories can't break CleanArchitectureCQRS.Domain.ValueObjects.
- Position
- Below the diagonal: CleanArchitectureCQRS.Infrastructure.EF.Repositories uses a module listed above it, which is the healthy direction.
38→23 CleanArchitectureCQRS.Infrastructure.EF.Repositories uses CleanArchitectureCQRS.Domain.Entities✕
- Connections
- 1 pair of types, where a type in CleanArchitectureCQRS.Infrastructure.EF.Repositories uses a type in CleanArchitectureCQRS.Domain.Entities.
- The types involved
CleanArchitectureCQRS.Infrastructure.EF.Repositories.SampleEntityRepository→CleanArchitectureCQRS.Domain.Entities.SampleEntity
- Direction
- CleanArchitectureCQRS.Infrastructure.EF.Repositories uses CleanArchitectureCQRS.Domain.Entities, so a change to CleanArchitectureCQRS.Domain.Entities can break CleanArchitectureCQRS.Infrastructure.EF.Repositories, while a change to CleanArchitectureCQRS.Infrastructure.EF.Repositories can't break CleanArchitectureCQRS.Domain.Entities.
- Position
- Below the diagonal: CleanArchitectureCQRS.Infrastructure.EF.Repositories uses a module listed above it, which is the healthy direction.
38→33 CleanArchitectureCQRS.Infrastructure.EF.Repositories uses CleanArchitectureCQRS.Domain.Repositories✕
- Connections
- 1 pair of types, where a type in CleanArchitectureCQRS.Infrastructure.EF.Repositories uses a type in CleanArchitectureCQRS.Domain.Repositories.
- The types involved
CleanArchitectureCQRS.Infrastructure.EF.Repositories.SampleEntityRepository→CleanArchitectureCQRS.Domain.Repositories.ISampleEntityRepository
- Direction
- CleanArchitectureCQRS.Infrastructure.EF.Repositories uses CleanArchitectureCQRS.Domain.Repositories, so a change to CleanArchitectureCQRS.Domain.Repositories can break CleanArchitectureCQRS.Infrastructure.EF.Repositories, while a change to CleanArchitectureCQRS.Infrastructure.EF.Repositories can't break CleanArchitectureCQRS.Domain.Repositories.
- Position
- Below the diagonal: CleanArchitectureCQRS.Infrastructure.EF.Repositories uses a module listed above it, which is the healthy direction.
38→35 CleanArchitectureCQRS.Infrastructure.EF.Repositories uses CleanArchitectureCQRS.Infrastructure.EF.Contexts✕
- Connections
- 1 pair of types, where a type in CleanArchitectureCQRS.Infrastructure.EF.Repositories uses a type in CleanArchitectureCQRS.Infrastructure.EF.Contexts.
- The types involved
CleanArchitectureCQRS.Infrastructure.EF.Repositories.SampleEntityRepository→CleanArchitectureCQRS.Infrastructure.EF.Contexts.WriteDbContext
- Direction
- CleanArchitectureCQRS.Infrastructure.EF.Repositories uses CleanArchitectureCQRS.Infrastructure.EF.Contexts, so a change to CleanArchitectureCQRS.Infrastructure.EF.Contexts can break CleanArchitectureCQRS.Infrastructure.EF.Repositories, while a change to CleanArchitectureCQRS.Infrastructure.EF.Repositories can't break CleanArchitectureCQRS.Infrastructure.EF.Contexts.
- Position
- Below the diagonal: CleanArchitectureCQRS.Infrastructure.EF.Repositories uses a module listed above it, which is the healthy direction.
39→4 CleanArchitectureCQRS.Infrastructure.EF.Services uses CleanArchitectureCQRS.Application.Services✕
- Connections
- 1 pair of types, where a type in CleanArchitectureCQRS.Infrastructure.EF.Services uses a type in CleanArchitectureCQRS.Application.Services.
- The types involved
CleanArchitectureCQRS.Infrastructure.EF.Services.SampleEntityReadService→CleanArchitectureCQRS.Application.Services.ISampleEntityReadService
- Direction
- CleanArchitectureCQRS.Infrastructure.EF.Services uses CleanArchitectureCQRS.Application.Services, so a change to CleanArchitectureCQRS.Application.Services can break CleanArchitectureCQRS.Infrastructure.EF.Services, while a change to CleanArchitectureCQRS.Infrastructure.EF.Services can't break CleanArchitectureCQRS.Application.Services.
- Position
- Below the diagonal: CleanArchitectureCQRS.Infrastructure.EF.Services uses a module listed above it, which is the healthy direction.
39→9 CleanArchitectureCQRS.Infrastructure.EF.Services uses CleanArchitectureCQRS.Infrastructure.EF.Models✕
- Connections
- 1 pair of types, where a type in CleanArchitectureCQRS.Infrastructure.EF.Services uses a type in CleanArchitectureCQRS.Infrastructure.EF.Models.
- The types involved
CleanArchitectureCQRS.Infrastructure.EF.Services.SampleEntityReadService→CleanArchitectureCQRS.Infrastructure.EF.Models.SampleEntityReadModel
- Direction
- CleanArchitectureCQRS.Infrastructure.EF.Services uses CleanArchitectureCQRS.Infrastructure.EF.Models, so a change to CleanArchitectureCQRS.Infrastructure.EF.Models can break CleanArchitectureCQRS.Infrastructure.EF.Services, while a change to CleanArchitectureCQRS.Infrastructure.EF.Services can't break CleanArchitectureCQRS.Infrastructure.EF.Models.
- Position
- Below the diagonal: CleanArchitectureCQRS.Infrastructure.EF.Services uses a module listed above it, which is the healthy direction.
39→35 CleanArchitectureCQRS.Infrastructure.EF.Services uses CleanArchitectureCQRS.Infrastructure.EF.Contexts✕
- Connections
- 1 pair of types, where a type in CleanArchitectureCQRS.Infrastructure.EF.Services uses a type in CleanArchitectureCQRS.Infrastructure.EF.Contexts.
- The types involved
CleanArchitectureCQRS.Infrastructure.EF.Services.SampleEntityReadService→CleanArchitectureCQRS.Infrastructure.EF.Contexts.ReadDbContext
- Direction
- CleanArchitectureCQRS.Infrastructure.EF.Services uses CleanArchitectureCQRS.Infrastructure.EF.Contexts, so a change to CleanArchitectureCQRS.Infrastructure.EF.Contexts can break CleanArchitectureCQRS.Infrastructure.EF.Services, while a change to CleanArchitectureCQRS.Infrastructure.EF.Services can't break CleanArchitectureCQRS.Infrastructure.EF.Contexts.
- Position
- Below the diagonal: CleanArchitectureCQRS.Infrastructure.EF.Services uses a module listed above it, which is the healthy direction.
40→3 CleanArchitectureCQRS.Api.Controllers uses CleanArchitectureCQRS.Application.DTOs✕
- Connections
- 1 pair of types, where a type in CleanArchitectureCQRS.Api.Controllers uses a type in CleanArchitectureCQRS.Application.DTOs.
- The types involved
CleanArchitectureCQRS.Api.Controllers.SampleEntityController→CleanArchitectureCQRS.Application.DTOs.SampleEntityDto
- Direction
- CleanArchitectureCQRS.Api.Controllers uses CleanArchitectureCQRS.Application.DTOs, so a change to CleanArchitectureCQRS.Application.DTOs can break CleanArchitectureCQRS.Api.Controllers, while a change to CleanArchitectureCQRS.Api.Controllers can't break CleanArchitectureCQRS.Application.DTOs.
- Position
- Below the diagonal: CleanArchitectureCQRS.Api.Controllers uses a module listed above it, which is the healthy direction.
40→13 CleanArchitectureCQRS.Api.Controllers uses CleanArchitectureCQRS.Shared.Abstractions.Commands✕
- Connections
- 1 pair of types, where a type in CleanArchitectureCQRS.Api.Controllers uses a type in CleanArchitectureCQRS.Shared.Abstractions.Commands.
- The types involved
CleanArchitectureCQRS.Api.Controllers.SampleEntityController→CleanArchitectureCQRS.Shared.Abstractions.Commands.ICommandDispatcher
- Direction
- CleanArchitectureCQRS.Api.Controllers uses CleanArchitectureCQRS.Shared.Abstractions.Commands, so a change to CleanArchitectureCQRS.Shared.Abstractions.Commands can break CleanArchitectureCQRS.Api.Controllers, while a change to CleanArchitectureCQRS.Api.Controllers can't break CleanArchitectureCQRS.Shared.Abstractions.Commands.
- Position
- Below the diagonal: CleanArchitectureCQRS.Api.Controllers uses a module listed above it, which is the healthy direction.
40→16 CleanArchitectureCQRS.Api.Controllers uses CleanArchitectureCQRS.Shared.Abstractions.Queries✕
- Connections
- 1 pair of types, where a type in CleanArchitectureCQRS.Api.Controllers uses a type in CleanArchitectureCQRS.Shared.Abstractions.Queries.
- The types involved
CleanArchitectureCQRS.Api.Controllers.SampleEntityController→CleanArchitectureCQRS.Shared.Abstractions.Queries.IQueryDispatcher
- Direction
- CleanArchitectureCQRS.Api.Controllers uses CleanArchitectureCQRS.Shared.Abstractions.Queries, so a change to CleanArchitectureCQRS.Shared.Abstractions.Queries can break CleanArchitectureCQRS.Api.Controllers, while a change to CleanArchitectureCQRS.Api.Controllers can't break CleanArchitectureCQRS.Shared.Abstractions.Queries.
- Position
- Below the diagonal: CleanArchitectureCQRS.Api.Controllers uses a module listed above it, which is the healthy direction.
40→20 CleanArchitectureCQRS.Api.Controllers uses CleanArchitectureCQRS.Application.Commands✕
- Connections
- 4 pairs of types, where a type in CleanArchitectureCQRS.Api.Controllers uses a type in CleanArchitectureCQRS.Application.Commands.
- The types involved
CleanArchitectureCQRS.Api.Controllers.SampleEntityController→CleanArchitectureCQRS.Application.Commands.CreateSampleEntityWithItemsCleanArchitectureCQRS.Api.Controllers.SampleEntityController→CleanArchitectureCQRS.Application.Commands.RemoveSampleEntityCleanArchitectureCQRS.Api.Controllers.SampleEntityController→CleanArchitectureCQRS.Application.Commands.RemoveSampleEntityItemCleanArchitectureCQRS.Api.Controllers.SampleEntityController→CleanArchitectureCQRS.Application.Commands.TakeItem
- Direction
- CleanArchitectureCQRS.Api.Controllers uses CleanArchitectureCQRS.Application.Commands, so a change to CleanArchitectureCQRS.Application.Commands can break CleanArchitectureCQRS.Api.Controllers, while a change to CleanArchitectureCQRS.Api.Controllers can't break CleanArchitectureCQRS.Application.Commands.
- Position
- Below the diagonal: CleanArchitectureCQRS.Api.Controllers uses a module listed above it, which is the healthy direction.
40→22 CleanArchitectureCQRS.Api.Controllers uses CleanArchitectureCQRS.Application.Queries✕
- Connections
- 2 pairs of types, where a type in CleanArchitectureCQRS.Api.Controllers uses a type in CleanArchitectureCQRS.Application.Queries.
- The types involved
CleanArchitectureCQRS.Api.Controllers.SampleEntityController→CleanArchitectureCQRS.Application.Queries.GetSampleEntityCleanArchitectureCQRS.Api.Controllers.SampleEntityController→CleanArchitectureCQRS.Application.Queries.SearchSampleEntity
- Direction
- CleanArchitectureCQRS.Api.Controllers uses CleanArchitectureCQRS.Application.Queries, so a change to CleanArchitectureCQRS.Application.Queries can break CleanArchitectureCQRS.Api.Controllers, while a change to CleanArchitectureCQRS.Api.Controllers can't break CleanArchitectureCQRS.Application.Queries.
- Position
- Below the diagonal: CleanArchitectureCQRS.Api.Controllers uses a module listed above it, which is the healthy direction.
40→36 CleanArchitectureCQRS.Api.Controllers uses CleanArchitectureCQRS.Application.Commands.Handlers✕
- Connections
- 1 pair of types, where a type in CleanArchitectureCQRS.Api.Controllers uses a type in CleanArchitectureCQRS.Application.Commands.Handlers.
- The types involved
CleanArchitectureCQRS.Api.Controllers.SampleEntityController→CleanArchitectureCQRS.Application.Commands.Handlers.AddSampleEntityItem
- Direction
- CleanArchitectureCQRS.Api.Controllers uses CleanArchitectureCQRS.Application.Commands.Handlers, so a change to CleanArchitectureCQRS.Application.Commands.Handlers can break CleanArchitectureCQRS.Api.Controllers, while a change to CleanArchitectureCQRS.Api.Controllers can't break CleanArchitectureCQRS.Application.Commands.Handlers.
- Position
- Below the diagonal: CleanArchitectureCQRS.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 — Domain Modelling
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A05:2025 — Injection | 11 | High / Critical |
| A07:2025 — Authentication Failures | 2 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 1 | High / Critical |
Roadmap
Top priorities: Resolve the 2 Leaked secret finding(s) in Secret Scanning — start with REDACTED, REDACTED; Add a SAST step to CI running what this repository's stack ships: CodeQL's csharp pack, or a .NET security analyzer package — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing; Protect endpoints by default-deny: [Authorize] + role/policy authorization, or imperative guard methods (throw-on-violation) called from every handler.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 2 Leaked secret finding(s) in Secret Scanning — start with REDACTED, REDACTED. | +9.3 pts | Low | Secret Scanning |
| Resolve the 3 Outdated finding(s) in Dependency Hygiene — start with REDACTED, CleanArchitectureCQRS.Api.csproj, CleanArchitecture.CQRS.UnitTest.csproj. | +4.7 pts | Low | Dependency Hygiene |
| Resolve the 2 Deprecated finding(s) in Dependency Hygiene — start with REDACTED, CleanArchitecture.CQRS.UnitTest.csproj. | +3.6 pts | Low | Dependency Hygiene |
| Resolve the 1 No ADRs found finding(s) in ADR Quality. | +3.3 pts | Low | ADR Quality |
| Add a SAST step to CI running what this repository's stack ships: CodeQL's csharp pack, or a .NET security analyzer package — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing. | +6.0 pts | Medium | Security & performance tooling |
| Protect endpoints by default-deny: [Authorize] + role/policy authorization, or imperative guard methods (throw-on-violation) called from every handler. | +5.3 pts | Medium | Access Controls |
| Resolve the 1 Documentation finding(s) in Documentation Quality — start with README.md. | +2.3 pts | Low | Documentation Quality |
| Resolve the 9 Low coverage finding(s) in Code Coverage — start with FemaleGenderPolicy.cs, MaleGenderPolicy.cs, SampleEntityFactory.cs. | +2.0 pts | Low | Code Coverage |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 2.1 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.2 | Mixed | Dependency Vulnerabilities: High CVE: REDACTED |
| REDACTED | 5.8 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| CleanArchitectureCQRS.Domain/Policies/Gender/FemaleGenderPolicy.cs | 6.7 | Mixed | Explicit Debt: Dead code: FemaleGenderPolicy |
| CleanArchitectureCQRS.Domain/Policies/Gender/MaleGenderPolicy.cs | 6.7 | Mixed | Explicit Debt: Dead code: MaleGenderPolicy |
| CleanArchitectureCQRS.Application/Commands/Handlers/AddSampleEntityItemHandler.cs | 6.7 | Mixed | Explicit Debt: Dead code: AddSampleEntityItemHandler |
| CleanArchitectureCQRS.Application/Commands/Handlers/RemoveSampleEntityHandler.cs | 6.7 | Mixed | Explicit Debt: Dead code: RemoveSampleEntityHandler |
| CleanArchitectureCQRS.Application/Commands/Handlers/RemoveSampleEntityItemHandler.cs | 6.7 | Mixed | Explicit Debt: Dead code: RemoveSampleEntityItemHandler |
| CleanArchitectureCQRS.Application/Commands/Handlers/TakeItemHandler.cs | 6.7 | Mixed | Explicit Debt: Dead code: TakeItemHandler |
| REDACTED | 7.2 | Mixed | Secret Scanning: Leaked secret: REDACTED |
| REDACTED | 7.2 | Mixed | Secret Scanning: Leaked secret: REDACTED |
| CleanArchitectureCQRS.Api/CleanArchitectureCQRS.Api.csproj | 8.0 | Near-clean | Code Coverage: No test project references CleanArchitectureCQRS.Api |
| CleanArchitecture.CQRS.UnitTest/CleanArchitecture.CQRS.UnitTest.csproj | 8.0 | Near-clean | Dependency Hygiene: Deprecated: xunit |
| CleanArchitectureCQRS.Infrastructure/EF/Queries/Handlers/GetSampleEntityHandler.cs | 8.2 | Near-clean | Explicit Debt: Dead code: GetSampleEntityHandler |
| CleanArchitectureCQRS.Infrastructure/EF/Queries/Handlers/SearchSampleEntityHandler.cs | 8.2 | Near-clean | Explicit Debt: Dead code: SearchSampleEntityHandler |
| CleanArchitectureCQRS.Infrastructure/Services/ExternalService.cs | 8.2 | Near-clean | Explicit Debt: Dead code: ExternalService |
| CleanArchitectureCQRS.Domain/Factories/SampleEntityFactory.cs | 8.5 | Near-clean | Code Coverage: Low coverage: CleanArchitectureCQRS.Domain/Factories/SampleEntityFactory.cs |
| CleanArchitectureCQRS.Domain/Entities/SampleEntity.cs | 8.5 | Near-clean | Code Coverage: Low coverage: CleanArchitectureCQRS.Domain/Entities/SampleEntity.cs |
| CleanArchitectureCQRS.Application/Extensions.cs | 8.5 | Near-clean | Code Coverage: Low coverage: CleanArchitectureCQRS.Application/Extensions.cs |
| CleanArchitectureCQRS.Infrastructure/CleanArchitectureCQRS.Infrastructure.csproj | 8.5 | Near-clean | Code Coverage: No test project references CleanArchitectureCQRS.Infrastructure |
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 84 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 1.0, the weighted average across measured dimensions.
What we checked — 84 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, 78 of 113 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. Single-contributor repository — bus factor is not applicable (1 contributor(s) across 40 commit(s) sampled, automation and bot accounts excluded). Concentration needs a team to concentrate: with one contributor there is nobody to spread the knowledge to, so there is nothing here for the owner to act on.
- 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.
- D34 Knowledge Freshness — 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. Too few commits to judge knowledge freshness (40 commit(s) sampled).
- AXR1 Runtime accessibility — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via ToolchainServer (CleanArchitectureCQRS.Api). the service exited before it opened a port — `ASPNETCORE_URLS=http://127.0.0.1:0 ASPNETCORE_ENVIRONMENT=Development dotnet run --no-build --no-launch-profile --project 'CleanArchitectureCQRS.Api.csproj'`: Microsoft.Extensions.Hosting.Internal.Host.StartAsync(CancellationToken cancellationToken) at Microsoft.Extensions.Hosting.HostingAbstractionsHostExtensions.RunAsync(IHost host, CancellationToken…; runtime evidence skipped (launch chosen because CleanArchitectureCQRS.Api/CleanArchitectureCQRS.Api.csproj is a Microsoft.NET.Sdk.Web project).
- DM8 Value-object opportunities — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check finds primitive parameters that travel together through several signatures of the domain (a missing value object). Its deterministic rule has not yet shown 95 % precision on adjudicated rows, so the clumps it finds are counted here and not published as findings, and the card carries no score. That is a limit of the analyzer, not a finding about your code.
- 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.
- M4 Documentation accuracy — 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. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
- D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- D8 Code Coverage: Coverage is measured by building and running the test suite inside our isolated image — the target repo is never modified, and nothing on your systems runs. So coverage exists only when the suite builds and runs within the inline time budget; one that needs external services, can't build, or exceeds the budget yields no coverage (D8 then degrades to not-measured, not a low score). Line coverage also says nothing about assertion quality.
- D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
- D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
- D11 Test Reliability: Flakiness is inferred from history/markers — we run the suite once (for coverage), not the repeated runs under varied conditions that reveal nondeterminism, so a flaky test never recorded as failing is invisible here.
- D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
- D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D18 Solution Shape: Build integrity reflects whether the solution compiled in this environment — a build that needs a private feed, a specific SDK, or a generated file absent from the repo can read as broken when it is merely unreproducible here.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
- D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
- D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- AX9 CQS / query purity: Handlers are found by interface/name convention — a query handler using neither is not seen. Mutation is a resolved write/publish invocation (SaveChanges/repository/bus), so a write hidden behind a hand-rolled wrapper, reflection, or a string-keyed service locator resolves to a non-persistence type and isn't flagged; it detects that a query writes state, not whether the write is a legitimate read-side cache update. Clean means "no resolved write/publish in a query body", not a proof of CQS purity.
- DM4 Rich vs anemic model: Behaviour is detected as state mutation inside a method body — a method that enforces an invariant by validating-and-throwing without mutating reads as a query, and mutation delegated through an interface the scan can't resolve isn't credited; entities with zero public properties still drop out of the population. It detects that state changes, not whether the rule is correct.
- DM6 Domain ↔ infrastructure boundary: Infrastructure reached through a hand-rolled wrapper, a domain-named facade, reflection, or a string-keyed service locator resolves to a non-infra type and isn't seen; the body scan is symbol resolution over syntax, not full dataflow. A clean result means "no resolved infra reference in a domain body", not a proof of purity.
- M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
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
7 projects, 0 dependency cycle(s), 0 unstable depended-on project(s).
D6 · Cohesion (LCOM4)
0 of 7 classes have LCOM4 above 3.
D8 · Code Coverage
Line coverage 42.0% — 9 file(s) below 50%.
What to do
- Resolve the 9 Low coverage finding(s) in Code Coverage — start with FemaleGenderPolicy.cs, MaleGenderPolicy.cs, SampleEntityFactory.cs. — One of this dimension's main actionable groups (9 warning-level).
- Resolve the 1 No test project references CleanArchitectureCQRS.Infrastructure finding(s) in Code Coverage — start with CleanArchitectureCQRS.Infrastructure.csproj. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 No test project references CleanArchitectureCQRS.Api finding(s) in Code Coverage — start with CleanArchitectureCQRS.Api.csproj. — One of this dimension's main actionable groups (1 warning-level).
- Enforce Code Coverage in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D9 · Test Distribution
4 test methods: 4 unit, 0 integration, 0 BDD, 0 e2e.
D10 · Test Quality
0 skipped, 0 zero-assertion, 1 mock references across 4 tests.
D11 · Test Reliability
0 flaky across 1 measured tier(s). other: measured (0 flaky).
D12 · Dependency Hygiene
25 outdated, 0 vulnerable, 2 deprecated, 1 prerelease packages.
What to do
- Resolve the 3 Outdated finding(s) in Dependency Hygiene — start with REDACTED, CleanArchitectureCQRS.Api.csproj, CleanArchitecture.CQRS.UnitTest.csproj. — One of this dimension's main actionable groups (3 recommendation-level).
- Resolve the 2 Deprecated finding(s) in Dependency Hygiene — start with REDACTED, CleanArchitecture.CQRS.UnitTest.csproj. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 Prerelease dependency finding(s) in Dependency Hygiene. — One of this dimension's main actionable groups (1 warning-level).
- Enforce Dependency Hygiene in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D13 · Secret Scanning
2 secret(s) detected.
What to do
- Resolve the 2 Leaked secret finding(s) in Secret Scanning — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 issue-level).
- Enforce Secret Scanning in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D14 · License Compliance
0 of 240 packages use a banned license. ★ DEPTH: this repository's MSBuild projects declare 25 direct `PackageReference`(s), and 213 further package(s) were reached beyond them by closing the graph over nuget.org's own nuspec dependency graph — so a banned licence pulled in only by a dependency's OWN dependencies is inside this verdict. A package whose licence nuget.org could not be asked for is not graded, and version ranges are taken at their lower bound, so this is the closure as that graph states it rather than a restored consumer's exact resolution.
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window.
D17 · Explicit Debt
0 deducted debt markers + 9 dead symbols across 1132 LoC in the .NET projects (0.7/KLoC) → score 8.6.
What to do
- Resolve the 9 Dead code finding(s) in Explicit Debt — start with FemaleGenderPolicy.cs, MaleGenderPolicy.cs, AddSampleEntityItemHandler.cs. — One of this dimension's main actionable groups (9 warning-level).
- Enforce Explicit Debt in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D18 · Solution Shape
7 projects, 78 source files, 1237 hand-written lines of code (1132 production / 105 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), 12 inter-project edges.
D19 · Documentation Quality
1 of 2 documentation facets pass in full; short on: F4 map. 1 document(s) read across 7 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).
D26 · Project Cohesion
0 of 7 projects flagged as possibly oversized/incoherent.
D27 · Navigability
95 % of calls cross a namespace and 19 % go through an interface, but 100 % of collaborators are co-located — so a call's collaborators sit together and tracing stays easy. Baseline: small — navigation cost is tolerated.
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
11 finding(s): 0 critical, 2 high, 9 medium, 0 low. 2 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens.
What to do
- Resolve the 7 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (7). — One of this dimension's main actionable groups (7 warning-level).
- Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2). — One of this dimension's main actionable groups (2 warning-level).
- No action in Static Analysis (SAST) — all 2 REDACTED finding(s) are reported here at file:line but scored by D36 (supply-chain provenance), so none is charged to this dimension. — One of this dimension's main actionable groups (2 issue-level, 0 of them charged here).
D30 · Dependency Vulnerabilities
1 finding(s): 0 critical, 1 high, 0 medium, 0 low.
What to do
- Resolve the 1 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
D35 · Change Coupling
No strong hidden change-coupling between production files.
D39 · IL Efficiency
0 of 122 first-party methods have an oversized IL body.
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 7 platform declaration(s) and 0 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
Frontend & cross-cutting dimensions
AX1 · Captive dependencies
AX10 · Code composition
AX2 · Stateful singletons
AX3 · Project dependency cycles
AX4 · Dependency direction
AX5 · Architecture & structure
AX6 · Interface segregation
AX8 · Test isolation
AX9 · CQS / query purity
C2 · Access Controls
- No [Authorize]/policies and no imperative guard methods (throw-on-violation) were found — endpoints may be unprotected.
- `SampleEntityController.Get` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. (×2) — REDACTED:23, REDACTED:30
- `SampleEntityController.Post` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. — REDACTED:37
- `SampleEntityController.Put` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. (×2) — REDACTED:44, REDACTED:51
- `SampleEntityController.Delete` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. (×2) — REDACTED:58, REDACTED:65
What to do
- Protect endpoints by default-deny: [Authorize] + role/policy authorization, or imperative guard methods (throw-on-violation) called from every handler.
DM1 · Aggregate boundaries
DM10 · One transaction, one aggregate
DM11 · Constructible invalid state
DM12 · Ambient inputs in the domain
DM4 · Rich vs anemic model
DM5 · Encapsulated state
DM6 · Domain ↔ infrastructure boundary
DM7 · Repository granularity
DM9 · Scattered domain decisions
GD1 · Unfinished & placeholder code
IC1 · Incompleteness & stubs
- A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers). (×2) — CleanArchitectureCQRS.Infrastructure/Extensions.cs:18, CleanArchitectureCQRS.Shared/Services/AppInitializer.cs:28
What to do
- Clear the softer debt: remove commented-out code and dead branches, re-enable or delete skipped tests, and replace blanket warning suppressions with targeted ones.
M1 · Documentation (README)
What to do
- Add a README to the 6 of 6 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
- Production code isn't grouped under a src/ folder — it's spread across several top-level directories, so there's no one place that says 'this is the product'.
- Tests aren't grouped in a dedicated test folder — the test surface isn't separable from production code at a glance.
What to do
- Group production code under src/ (or split deliberately, e.g. backend/ + frontend/) so production and tooling code aren't mixed at the root.
- Group tests in the folder your build system expects (tests/, test/, spec/, or your module's test source set) so the test surface is discoverable and CI can scope it.
M4 · Documentation accuracy
- README.md links to `License.md`, but `License.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — README.md:64
What to do
- Reconcile the README with reality: README.md links to `License.md`, but `License.md` does not exist.
P1 · CI/CD gates
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) as a CI step. What was searched, so you can tell an absence from a miss: the 507 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:8
- `CleanArchitecture.CQRS.UnitTest/CleanArchitecture.CQRS.UnitTest.csproj` 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`. — CleanArchitecture.CQRS.UnitTest/CleanArchitecture.CQRS.UnitTest.csproj:11
What to do
- Add a SAST step to CI running what this repository's stack ships: CodeQL's csharp pack, or a .NET security analyzer package — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing.
- Enable Dependabot/Renovate or a dependency-review gate.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P8 · Schema migrations
- This repository evolves its schema with versioned migrations, but `EnsureCreated()` here builds a schema straight from the model instead — with no migrations-history row, so a database it creates can't be upgraded by `Migrate()` afterwards and the two paths can disagree about the shape. Apply the migrations here (`Migrate()` / a migrations bundle) rather than creating the schema. — CleanArchitectureCQRS.Shared/Services/AppInitializer.cs:29
What to do
- Replace each EnsureCreated() in production code with the migrations the rest of the repository already uses (`Database.Migrate()` or a migrations bundle), so every database gets its schema from the one versioned path.
P9 · Domain vs controller coverage
- Domain coverage is 44%, against a bar of 50% for this row — the layer carrying the business rules is the least covered part of the codebase that matters most. Measured over the types this analyzer classifies as domain (aggregates, value objects, domain services), so code the classifier does not place in the domain is neither counted for nor against this figure.
What to do
- Raise unit-test coverage of the domain (aggregates, value objects, domain services) — that's where correctness matters most.
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. — CleanArchitectureCQRS.Api/Program.cs:6
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.
X1 · Async correctness
X12 · Unreachable branch
X13 · Undrained process stream
X14 · Bypassable address classification
X15 · Unvalidated length from an untrusted reader
X16 · Unfloored truncation loop
X17 · Uncapped recursion over a caller-supplied document
X18 · Disposal-pattern correctness
X19 · Unrestored process-global state
X2 · Cancellation propagation
- Only 1/21 async methods accept a CancellationToken, so in-flight work can't be stopped early when the caller gives up — whatever ends it in your host (shutdown signal, timeout, abandoned request, user cancel). Thread a token through the call chain and honour it at each await and loop; where a method genuinely cannot be interrupted, omitting it is a deliberate choice — judge against your hosting model.
- No CancellationToken parameter — this work can't be stopped early once started. (×19) — CleanArchitectureCQRS.Shared/Commands/InMemoryCommandDispatcher.cs:13, CleanArchitectureCQRS.Application/Commands/Handlers/AddSampleEntityItemHandler.cs:15, CleanArchitectureCQRS.Application/Commands/Handlers/CreateSampleEntityWithItemHandler.cs:26, …
- 1 async method(s) await work their caller's cancellation cannot reach: a CancellationToken they hold (a parameter, or the one a framework-fixed signature carries) is never passed on, or the call is handed CancellationToken.None, default or an already-cancelled token. Forward the caller's token to that call.
- Its signature is fixed by the framework, and the token it carries (`context.RequestAborted`) reaches none of the calls here that take one — so an aborted request or a stopping host still waits for that work. Pass `context.RequestAborted` to them. — CleanArchitectureCQRS.Shared/Exceptions/ExceptionMiddleware.cs:9
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. (×3) — CleanArchitectureCQRS.Infrastructure/Logging/LoggingCommandHandlerDecorator.cs:24, CleanArchitectureCQRS.Infrastructure/Logging/LoggingCommandHandlerDecorator.cs:26, CleanArchitectureCQRS.Infrastructure/Logging/LoggingCommandHandlerDecorator.cs:31
What to do
- Interpolated log message defeats structured logging
X5 · Nullable reference types
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 64% | Adequate — gated by X4 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 89% | Strong | Solid. |
| Maturity | 57% | Adequate — gated by M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 39% | Weak — gated by D13, P3, P8 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 47% | Weak — gated by C2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Domain Modelling | 100% | Exemplary | Strongest area. |
| Performance | 100% | Exemplary | Solid. |
Unscored — 2 check(s) recorded observations but carry no score
- D36 Supply-chain Provenance & Signing — 1 observation(s) recorded · The CI pipeline builds and tests but publishes no released artifact — no package publish, container push, GitHub release or deployment step. Supply-chain provenance, signing and SBOM attest RELEASED artifacts, so there is nothing to attest here. Add them to the release pipeline when this repo starts shipping artifacts (a published package, a container image, a deployed service or a tagged release). Build integrity and workflow-token hygiene are reported below: they describe what the CI runs and the token it runs with, neither of which is affected by whether the pipeline ships an artifact.
- 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 — 3 control(s) we could not find positive evidence for
- 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 — 42 check(s) not relevant to this codebase
- AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
- AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
- AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
- AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
- AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
- AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
- AC7 A11y enforcement — No web markup found — accessibility is not applicable to this repository.
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXR1 Runtime accessibility — the service exited before it opened a port — `ASPNETCORE_URLS=http://127.0.0.1:0 ASPNETCORE_ENVIRONMENT=Development dotnet run --no-build --no-launch-profile --project 'CleanArchitectureCQRS.Api.csproj'`: Microsoft.Extensions.Hosting.Internal.Host.StartAsync(CancellationToken cancellationToken) at Microsoft.Extensions.Hosting.HostingAbstractionsHostExtensions.RunAsync(IHost host, CancellationToken…; runtime evidence skipped (launch chosen because CleanArchitectureCQRS.Api/CleanArchitectureCQRS.Api.csproj is a Microsoft.NET.Sdk.Web project) This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
- C1 Data Protection — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
- C3 Audit Trail — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
- C4 Data Retention — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
- C5 Data-Subject Rights — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
- D16 Bus Factor — single-contributor repository — bus factor is not applicable
- D21 Naming Consistency — N/A — too few peers to establish a naming convention (326 declarations, no unit with a dominant convention).
- D22 Internal API Consistency — No intentionally-exposed public API to evaluate for consistency.
- D23 Boundary Type-Coupling — small single-context codebase (1,132 production LoC in the .NET projects) — bounded contexts are not needed at this size No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Aggregate roots were found in only one source directory (CleanArchitectureCQRS.Domain), which is a layered codebase, not two contexts. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D24 Comment Value — Too few judgeable comments (3 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.
- D34 Knowledge Freshness — too few commits to judge knowledge freshness
- 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
- DM2 Strongly-typed ids — no id-bearing domain types detected — strongly-typed-id adoption not assessable
- DM3 Integration-event coupling — no integration events detected — coupling check not applicable
- DM8 Value-object opportunities — not scored — the deterministic rule found 0 candidate clump(s); its rows are withheld until it has a measured precision of 95 % (a sample of fewer than 10 rows cannot show one)
- ED1 Event-Driven — not scored — this repository shows only 1 of the 3 signals this lens looks for (10 CQRS handler(s))
- ED5 Idempotency — not scored — 3 of 5 retry-prone mutations could not be classified (no visible guard and no positive evidence of a double-applied effect)
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
- P7 Outbound HTTP resilience — no outbound HTTP usage detected — no HttpClient/IHttpClientFactory/AddHttpClient in source, and no Refit/RestSharp/Flurl.Http namespace or package reference
- 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 — 5 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
Serious — 64 finding(s)
- Async method without CancellationToken: DispatchAsync CleanArchitectureCQRS.Shared/Commands/InMemoryCommandDispatcher.cs:13
- Async method without CancellationToken: HandleAsync CleanArchitectureCQRS.Application/Commands/Handlers/AddSampleEntityItemHandler.cs:15
- Async method without CancellationToken: HandleAsync CleanArchitectureCQRS.Application/Commands/Handlers/CreateSampleEntityWithItemHandler.cs:26
- Async method without CancellationToken: HandleAsync CleanArchitectureCQRS.Application/Commands/Handlers/RemoveSampleEntityHandler.cs:14
- Async method without CancellationToken: HandleAsync CleanArchitectureCQRS.Application/Commands/Handlers/RemoveSampleEntityItemHandler.cs:14
- Async method without CancellationToken: HandleAsync CleanArchitectureCQRS.Application/Commands/Handlers/TakeItemHandler.cs:14
- Async method without CancellationToken: HandleAsync CleanArchitectureCQRS.Infrastructure/EF/Queries/Handlers/GetSampleEntityHandler.cs:18
- Async method without CancellationToken: HandleAsync CleanArchitectureCQRS.Infrastructure/EF/Queries/Handlers/SearchSampleEntityHandler.cs:17
- Async method without CancellationToken: GetAsync CleanArchitectureCQRS.Infrastructure/EF/Repositories/SampleEntityRepository.cs:20
- Async method without CancellationToken: AddAsync CleanArchitectureCQRS.Infrastructure/EF/Repositories/SampleEntityRepository.cs:23
- Async method without CancellationToken: UpdateAsync CleanArchitectureCQRS.Infrastructure/EF/Repositories/SampleEntityRepository.cs:29
- Async method without CancellationToken: DeleteAsync CleanArchitectureCQRS.Infrastructure/EF/Repositories/SampleEntityRepository.cs:35
- Async method without CancellationToken: ExistsByNameAsync CleanArchitectureCQRS.Infrastructure/EF/Services/SampleEntityReadService.cs:15
- Async method without CancellationToken: HandleAsync CleanArchitectureCQRS.Infrastructure/Logging/LoggingCommandHandlerDecorator.cs:18
- Async method without CancellationToken: Post REDACTED:37
- Async method without CancellationToken: Put REDACTED:44
- Async method without CancellationToken: Put REDACTED:51
- Async method without CancellationToken: Delete REDACTED:58
- Async method without CancellationToken: Delete REDACTED:65
- Dead code: FemaleGenderPolicy CleanArchitectureCQRS.Domain/Policies/Gender/FemaleGenderPolicy.cs:5
- Dead code: MaleGenderPolicy CleanArchitectureCQRS.Domain/Policies/Gender/MaleGenderPolicy.cs:5
- Dead code: AddSampleEntityItemHandler CleanArchitectureCQRS.Application/Commands/Handlers/AddSampleEntityItemHandler.cs:8
- Dead code: RemoveSampleEntityHandler CleanArchitectureCQRS.Application/Commands/Handlers/RemoveSampleEntityHandler.cs:7
- Dead code: RemoveSampleEntityItemHandler CleanArchitectureCQRS.Application/Commands/Handlers/RemoveSampleEntityItemHandler.cs:7
- Dead code: TakeItemHandler CleanArchitectureCQRS.Application/Commands/Handlers/TakeItemHandler.cs:7
- Dead code: GetSampleEntityHandler CleanArchitectureCQRS.Infrastructure/EF/Queries/Handlers/GetSampleEntityHandler.cs:11
- Dead code: SearchSampleEntityHandler CleanArchitectureCQRS.Infrastructure/EF/Queries/Handlers/SearchSampleEntityHandler.cs:10
- Dead code: ExternalService CleanArchitectureCQRS.Infrastructure/Services/ExternalService.cs:3
- Low coverage: CleanArchitectureCQRS.Domain/Policies/Gender/FemaleGenderPolicy.cs CleanArchitectureCQRS.Domain/Policies/Gender/FemaleGenderPolicy.cs:1
- Low coverage: CleanArchitectureCQRS.Domain/Policies/Gender/MaleGenderPolicy.cs CleanArchitectureCQRS.Domain/Policies/Gender/MaleGenderPolicy.cs:1
- Low coverage: CleanArchitectureCQRS.Domain/Factories/SampleEntityFactory.cs CleanArchitectureCQRS.Domain/Factories/SampleEntityFactory.cs:1
- Low coverage: CleanArchitectureCQRS.Domain/Entities/SampleEntity.cs CleanArchitectureCQRS.Domain/Entities/SampleEntity.cs:1
- Low coverage: CleanArchitectureCQRS.Application/Extensions.cs CleanArchitectureCQRS.Application/Extensions.cs:1
- Low coverage: CleanArchitectureCQRS.Application/Commands/Handlers/AddSampleEntityItemHandler.cs CleanArchitectureCQRS.Application/Commands/Handlers/AddSampleEntityItemHandler.cs:1
- Low coverage: CleanArchitectureCQRS.Application/Commands/Handlers/RemoveSampleEntityHandler.cs CleanArchitectureCQRS.Application/Commands/Handlers/RemoveSampleEntityHandler.cs:1
- Low coverage: CleanArchitectureCQRS.Application/Commands/Handlers/RemoveSampleEntityItemHandler.cs CleanArchitectureCQRS.Application/Commands/Handlers/RemoveSampleEntityItemHandler.cs:1
- Low coverage: CleanArchitectureCQRS.Application/Commands/Handlers/TakeItemHandler.cs CleanArchitectureCQRS.Application/Commands/Handlers/TakeItemHandler.cs:1
- No authorization
- No authorization REDACTED:23
- No authorization REDACTED:30
- No authorization REDACTED:37
- No authorization REDACTED:44
- No authorization REDACTED:51
- No authorization REDACTED:58
- No authorization REDACTED:65
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Deprecated: Microsoft.AspNetCore.Http.Abstractions REDACTED:9
- Deprecated: xunit CleanArchitecture.CQRS.UnitTest/CleanArchitecture.CQRS.UnitTest.csproj:14
- REDACTED
- REDACTED
- Prerelease dependency: Microsoft.NET.Test.Sdk
- REDACTED
- No test project references CleanArchitectureCQRS.Infrastructure CleanArchitectureCQRS.Infrastructure/CleanArchitectureCQRS.Infrastructure.csproj
- No test project references CleanArchitectureCQRS.Api CleanArchitectureCQRS.Api/CleanArchitectureCQRS.Api.csproj
- Schema created with EnsureCreated() outside the migrations CleanArchitectureCQRS.Shared/Services/AppInitializer.cs:29
- Low domain coverage
- NuGet dependencies are not locked
- Async method drops its ambient CancellationToken: InvokeAsync CleanArchitectureCQRS.Shared/Exceptions/ExceptionMiddleware.cs:9
Minor — 21 finding(s)
- Outdated: Scrutor REDACTED:14
- Outdated: Swashbuckle.AspNetCore CleanArchitectureCQRS.Api/CleanArchitectureCQRS.Api.csproj:16
- Outdated: coverlet.collector CleanArchitecture.CQRS.UnitTest/CleanArchitecture.CQRS.UnitTest.csproj:19
- Interpolated log message defeats structured logging CleanArchitectureCQRS.Infrastructure/Logging/LoggingCommandHandlerDecorator.cs:24
- Interpolated log message defeats structured logging CleanArchitectureCQRS.Infrastructure/Logging/LoggingCommandHandlerDecorator.cs:26
- Interpolated log message defeats structured logging CleanArchitectureCQRS.Infrastructure/Logging/LoggingCommandHandlerDecorator.cs:31
- Commented-out code CleanArchitectureCQRS.Infrastructure/Extensions.cs:18
- Commented-out code CleanArchitectureCQRS.Shared/Services/AppInitializer.cs:28
- No security response headers detected
- No security response headers detected CleanArchitectureCQRS.Api/Program.cs:6
- Documentation: no map of the repository's parts README.md:1
- No ADRs found
- REDACTED
- No ADRs
- No src/ separation
- No tests/ separation
- README/code drift README.md:64
- No SAST REDACTED:8
- No dependency-update automation CleanArchitecture.CQRS.UnitTest/CleanArchitecture.CQRS.UnitTest.csproj:11
- Not all async methods take a CancellationToken
- Some async methods drop the CancellationToken they accept
Minor — 23 finding(s)
- Outdated: Microsoft.AspNetCore.Http.Abstractions
- Outdated: Microsoft.EntityFrameworkCore
- Outdated: Microsoft.Extensions.Configuration.Binder
- Outdated: Microsoft.Extensions.DependencyInjection
- Outdated: Microsoft.Extensions.Hosting.Abstractions
- Outdated: Microsoft.Extensions.DependencyInjection.Abstractions
- Outdated: Microsoft.EntityFrameworkCore.Design
- Outdated: Microsoft.EntityFrameworkCore.SqlServer
- Outdated: Microsoft.EntityFrameworkCore.Tools
- Outdated: Serilog
- Outdated: Serilog.AspNetCore
- Outdated: Serilog.Enrichers.Environment
- Outdated: Serilog.Extensions.Hosting
- Outdated: Serilog.Settings.Configuration
- Outdated: Serilog.Sinks.Console
- Outdated: Serilog.Sinks.Debug
- Outdated: Microsoft.AspNetCore.OpenApi
- Outdated: Microsoft.NET.Test.Sdk
- Outdated: NSubstitute
- Outdated: Shouldly
- Outdated: xunit
- Outdated: xunit.runner.visualstudio
- Mock framework: NSubstitute
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-6f47e9f2267c4f4ca21c5e89a4b8af76/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-6f47e9f2267c4f4ca21c5e89a4b8af76/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 . | 11 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | dotnet | — | dotnet list CleanArchitectureCQRS.sln package --vulnerable --include-transitive --format json | 1 | artifacts/raw/dotnet-vulnerable.json |
| D31 · IaC & Container Security | trivy | — | trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan. | 0 | — |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. | 0 | — |
| D37 · Vulnerability-disclosure Policy | disclosure | — | disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . /tmp/codehealth-osv-sbom-b0a1fd7ad1bb46d98cc993f5a9c15615 | 0 | artifacts/raw/osv-scanner.json |