Executive summary
matt-bentley/CleanArchitecture is rated At risk because critical security findings are open, most of them in the packages it uses. It scores 52 out of 100, which the At risk rating leaves unchanged. We judged it as a template or a sample, against a lower bar.
Production Readiness, at 36, is the weakest lens and counts most in the score. The best first step is fixing the password or key in the code, worth about 10 points. Documenting the recovery plan would lift Production Readiness itself, worth about 6 points. Raising Production Readiness to 52 would lift the score to about 59.
Fifty-one known security holes in the packages the code depends on can be used by attackers. Seven settings leave the servers or containers unsafe, and one password or key in the code and one in the code's history are open to anyone who can read the repository. Replacing each exposed password or key, updating the vulnerable packages and correcting the unsafe settings would close these risks. The analysis rule switched off in the settings needs switching back on in the settings file.
The product code is 2,065 lines, about €5,400 to rebuild.
If Production Readiness rose from 36 to 52, the lowest score rated Strong, the score would rise from 52 to about 59.
New since the last survey: 4 findings
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
Fixed since the last survey: 6 findings
- Dependency Vulnerabilities · High CVE: REDACTED REDACTED
- Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · High CVE: REDACTED REDACTED
- Dependency Vulnerabilities · High vulnerability: REDACTED REDACTED
- Dependency Vulnerabilities · Medium CVE: [GHSA redacted] REDACTED
Rebuild cost: about €5,400 · Estimate
| Cost to rebuild | €1,800 to €9,000, for 30 to 95 hours of work, under 0.1 person-years for one engineer |
|---|---|
| Difficulty of the problem | Very high, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.7 at a score of 52. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it. |
| Size | Small: 2,065 lines of product code |
| 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 CleanArchitecture.Api.Infrastructure.ActionResults | 3 CleanArchitecture.Api.Infrastructure.Filters | 4 CleanArchitecture.Application.Abstractions.DomainEventHandlers | 5 CleanArchitecture.Application.Abstractions.IntegrationEvents | 6 CleanArchitecture.Application.Abstractions.Queries | 7 CleanArchitecture.Application.Abstractions.Repositories | 8 CleanArchitecture.Application.AutofacModules | 9 CleanArchitecture.Application.Locations.MappingProfiles | 10 CleanArchitecture.Application.Locations.Models | 11 CleanArchitecture.Application.Weather.Models | 12 CleanArchitecture.Core.Abstractions.DomainEvents | 13 CleanArchitecture.Core.Abstractions.Services | 14 CleanArchitecture.Core.Locations.ValueObjects | 15 CleanArchitecture.Core.Weather.ValueObjects | 16 CleanArchitecture.Hosting | 17 src.CleanArchitecture_Web.ClientApp.src.app._shared.models.results_model | 18 src.CleanArchitecture_Web.ClientApp.src.app._shared.models.weather_model | 19 src.CleanArchitecture_Web.ClientApp.src.app._shared.services.locations_service | 20 CleanArchitecture.Api.Controllers | 21 CleanArchitecture.Application.Abstractions.Commands | 22 CleanArchitecture.Application.Weather.IntegrationEvents | 23 CleanArchitecture.Core.Abstractions.Entities | 24 CleanArchitecture.Core.Weather.DomainEvents | 25 CleanArchitecture.Infrastructure.Services | 26 src.CleanArchitecture_Web.ClientApp.src.app._shared.services.weather_service | 27 CleanArchitecture.Application.Weather.DomainEventHandlers | 28 CleanArchitecture.Core.Locations.Entities | 29 CleanArchitecture.Core.Weather.Entities | 30 src.CleanArchitecture_Web.ClientApp.src.app.weather-forecasts.weather-forecasts_component | 31 CleanArchitecture.Application.Locations.Queries | 32 CleanArchitecture.Application.Weather.Commands | 33 CleanArchitecture.Application.Weather.Queries | 34 CleanArchitecture.Infrastructure | 35 CleanArchitecture.Infrastructure.Configurations | 36 CleanArchitecture.Infrastructure.AutofacModules | 37 CleanArchitecture.Infrastructure.Repositories | 38 CleanArchitecture.Migrations | 39 CleanArchitecture.Migrations.Factories | 40 MediatR |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 (global) | ||||||||||||||||||||||||||||||||||||||||
| 2 CleanArchitecture.Api.Infrastructure.ActionResults | ||||||||||||||||||||||||||||||||||||||||
| 3 CleanArchitecture.Api.Infrastructure.Filters | ||||||||||||||||||||||||||||||||||||||||
| 4 CleanArchitecture.Application.Abstractions.DomainEventHandlers | ||||||||||||||||||||||||||||||||||||||||
| 5 CleanArchitecture.Application.Abstractions.IntegrationEvents | ||||||||||||||||||||||||||||||||||||||||
| 6 CleanArchitecture.Application.Abstractions.Queries | ||||||||||||||||||||||||||||||||||||||||
| 7 CleanArchitecture.Application.Abstractions.Repositories | ||||||||||||||||||||||||||||||||||||||||
| 8 CleanArchitecture.Application.AutofacModules | ||||||||||||||||||||||||||||||||||||||||
| 9 CleanArchitecture.Application.Locations.MappingProfiles | ||||||||||||||||||||||||||||||||||||||||
| 10 CleanArchitecture.Application.Locations.Models | ||||||||||||||||||||||||||||||||||||||||
| 11 CleanArchitecture.Application.Weather.Models | ||||||||||||||||||||||||||||||||||||||||
| 12 CleanArchitecture.Core.Abstractions.DomainEvents | ||||||||||||||||||||||||||||||||||||||||
| 13 CleanArchitecture.Core.Abstractions.Services | ||||||||||||||||||||||||||||||||||||||||
| 14 CleanArchitecture.Core.Locations.ValueObjects | ||||||||||||||||||||||||||||||||||||||||
| 15 CleanArchitecture.Core.Weather.ValueObjects | ||||||||||||||||||||||||||||||||||||||||
| 16 CleanArchitecture.Hosting | ||||||||||||||||||||||||||||||||||||||||
| 17 src.CleanArchitecture_Web.ClientApp.src.app._shared.models.results_model | ||||||||||||||||||||||||||||||||||||||||
| 18 src.CleanArchitecture_Web.ClientApp.src.app._shared.models.weather_model | ||||||||||||||||||||||||||||||||||||||||
| 19 src.CleanArchitecture_Web.ClientApp.src.app._shared.services.locations_service | ||||||||||||||||||||||||||||||||||||||||
| 20 CleanArchitecture.Api.Controllers | 2 | |||||||||||||||||||||||||||||||||||||||
| 21 CleanArchitecture.Application.Abstractions.Commands | 2 | |||||||||||||||||||||||||||||||||||||||
| 22 CleanArchitecture.Application.Weather.IntegrationEvents | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 23 CleanArchitecture.Core.Abstractions.Entities | 1 | |||||||||||||||||||||||||||||||||||||||
| 24 CleanArchitecture.Core.Weather.DomainEvents | 1 | |||||||||||||||||||||||||||||||||||||||
| 25 CleanArchitecture.Infrastructure.Services | 1 | |||||||||||||||||||||||||||||||||||||||
| 26 src.CleanArchitecture_Web.ClientApp.src.app._shared.services.weather_service | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 27 CleanArchitecture.Application.Weather.DomainEventHandlers | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 28 CleanArchitecture.Core.Locations.Entities | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 29 CleanArchitecture.Core.Weather.Entities | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 30 src.CleanArchitecture_Web.ClientApp.src.app.weather-forecasts.weather-forecasts_component | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 31 CleanArchitecture.Application.Locations.Queries | 2 | 1 | 2 | 1 | ||||||||||||||||||||||||||||||||||||
| 32 CleanArchitecture.Application.Weather.Commands | 6 | 6 | 1 | 3 | ||||||||||||||||||||||||||||||||||||
| 33 CleanArchitecture.Application.Weather.Queries | 4 | 2 | 4 | 2 | ||||||||||||||||||||||||||||||||||||
| 34 CleanArchitecture.Infrastructure | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 35 CleanArchitecture.Infrastructure.Configurations | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 36 CleanArchitecture.Infrastructure.AutofacModules | 1 | |||||||||||||||||||||||||||||||||||||||
| 37 CleanArchitecture.Infrastructure.Repositories | 2 | 1 | 1 | 2 | ||||||||||||||||||||||||||||||||||||
| 38 CleanArchitecture.Migrations | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 39 CleanArchitecture.Migrations.Factories | 2 | |||||||||||||||||||||||||||||||||||||||
| 40 MediatR | 1 | 1 | 1 |
20→11 CleanArchitecture.Api.Controllers uses CleanArchitecture.Application.Weather.Models✕
- Connections
- 2 pairs of types, where a type in CleanArchitecture.Api.Controllers uses a type in CleanArchitecture.Application.Weather.Models.
- The types involved
CleanArchitecture.Api.Controllers.WeatherForecastsController→CleanArchitecture.Application.Weather.Models.WeatherForecastCreateDtoCleanArchitecture.Api.Controllers.WeatherForecastsController→CleanArchitecture.Application.Weather.Models.WeatherForecastUpdateDto
- Direction
- CleanArchitecture.Api.Controllers uses CleanArchitecture.Application.Weather.Models, so a change to CleanArchitecture.Application.Weather.Models can break CleanArchitecture.Api.Controllers, while a change to CleanArchitecture.Api.Controllers can't break CleanArchitecture.Application.Weather.Models.
- Position
- Below the diagonal: CleanArchitecture.Api.Controllers uses a module listed above it, which is the healthy direction.
21→7 CleanArchitecture.Application.Abstractions.Commands uses CleanArchitecture.Application.Abstractions.Repositories✕
- Connections
- 2 pairs of types, where a type in CleanArchitecture.Application.Abstractions.Commands uses a type in CleanArchitecture.Application.Abstractions.Repositories.
- The types involved
CleanArchitecture.Application.Abstractions.Commands.CommandHandler→CleanArchitecture.Application.Abstractions.Repositories.IUnitOfWorkCleanArchitecture.Application.Abstractions.Commands.CreateCommandHandler→CleanArchitecture.Application.Abstractions.Repositories.IUnitOfWork
- Direction
- CleanArchitecture.Application.Abstractions.Commands uses CleanArchitecture.Application.Abstractions.Repositories, so a change to CleanArchitecture.Application.Abstractions.Repositories can break CleanArchitecture.Application.Abstractions.Commands, while a change to CleanArchitecture.Application.Abstractions.Commands can't break CleanArchitecture.Application.Abstractions.Repositories.
- Position
- Below the diagonal: CleanArchitecture.Application.Abstractions.Commands uses a module listed above it, which is the healthy direction.
22→5 CleanArchitecture.Application.Weather.IntegrationEvents uses CleanArchitecture.Application.Abstractions.IntegrationEvents✕
- Connections
- 1 pair of types, where a type in CleanArchitecture.Application.Weather.IntegrationEvents uses a type in CleanArchitecture.Application.Abstractions.IntegrationEvents.
- The types involved
CleanArchitecture.Application.Weather.IntegrationEvents.WeatherForecastCreatedEvent→CleanArchitecture.Application.Abstractions.IntegrationEvents.IntegrationEvent
- Direction
- CleanArchitecture.Application.Weather.IntegrationEvents uses CleanArchitecture.Application.Abstractions.IntegrationEvents, so a change to CleanArchitecture.Application.Abstractions.IntegrationEvents can break CleanArchitecture.Application.Weather.IntegrationEvents, while a change to CleanArchitecture.Application.Weather.IntegrationEvents can't break CleanArchitecture.Application.Abstractions.IntegrationEvents.
- Position
- Below the diagonal: CleanArchitecture.Application.Weather.IntegrationEvents uses a module listed above it, which is the healthy direction.
22→13 CleanArchitecture.Application.Weather.IntegrationEvents uses CleanArchitecture.Core.Abstractions.Services✕
- Connections
- 1 pair of types, where a type in CleanArchitecture.Application.Weather.IntegrationEvents uses a type in CleanArchitecture.Core.Abstractions.Services.
- The types involved
CleanArchitecture.Application.Weather.IntegrationEvents.WeatherForecastCreatedEventHandler→CleanArchitecture.Core.Abstractions.Services.INotificationsService
- Direction
- CleanArchitecture.Application.Weather.IntegrationEvents uses CleanArchitecture.Core.Abstractions.Services, so a change to CleanArchitecture.Core.Abstractions.Services can break CleanArchitecture.Application.Weather.IntegrationEvents, while a change to CleanArchitecture.Application.Weather.IntegrationEvents can't break CleanArchitecture.Core.Abstractions.Services.
- Position
- Below the diagonal: CleanArchitecture.Application.Weather.IntegrationEvents uses a module listed above it, which is the healthy direction.
23→12 CleanArchitecture.Core.Abstractions.Entities uses CleanArchitecture.Core.Abstractions.DomainEvents✕
- Connections
- 1 pair of types, where a type in CleanArchitecture.Core.Abstractions.Entities uses a type in CleanArchitecture.Core.Abstractions.DomainEvents.
- The types involved
CleanArchitecture.Core.Abstractions.Entities.AggregateRoot→CleanArchitecture.Core.Abstractions.DomainEvents.DomainEvent
- Direction
- CleanArchitecture.Core.Abstractions.Entities uses CleanArchitecture.Core.Abstractions.DomainEvents, so a change to CleanArchitecture.Core.Abstractions.DomainEvents can break CleanArchitecture.Core.Abstractions.Entities, while a change to CleanArchitecture.Core.Abstractions.Entities can't break CleanArchitecture.Core.Abstractions.DomainEvents.
- Position
- Below the diagonal: CleanArchitecture.Core.Abstractions.Entities uses a module listed above it, which is the healthy direction.
24→12 CleanArchitecture.Core.Weather.DomainEvents uses CleanArchitecture.Core.Abstractions.DomainEvents✕
- Connections
- 1 pair of types, where a type in CleanArchitecture.Core.Weather.DomainEvents uses a type in CleanArchitecture.Core.Abstractions.DomainEvents.
- The types involved
CleanArchitecture.Core.Weather.DomainEvents.WeatherForecastCreatedDomainEvent→CleanArchitecture.Core.Abstractions.DomainEvents.DomainEvent
- Direction
- CleanArchitecture.Core.Weather.DomainEvents uses CleanArchitecture.Core.Abstractions.DomainEvents, so a change to CleanArchitecture.Core.Abstractions.DomainEvents can break CleanArchitecture.Core.Weather.DomainEvents, while a change to CleanArchitecture.Core.Weather.DomainEvents can't break CleanArchitecture.Core.Abstractions.DomainEvents.
- Position
- Below the diagonal: CleanArchitecture.Core.Weather.DomainEvents uses a module listed above it, which is the healthy direction.
25→13 CleanArchitecture.Infrastructure.Services uses CleanArchitecture.Core.Abstractions.Services✕
- Connections
- 1 pair of types, where a type in CleanArchitecture.Infrastructure.Services uses a type in CleanArchitecture.Core.Abstractions.Services.
- The types involved
CleanArchitecture.Infrastructure.Services.NotificationsService→CleanArchitecture.Core.Abstractions.Services.INotificationsService
- Direction
- CleanArchitecture.Infrastructure.Services uses CleanArchitecture.Core.Abstractions.Services, so a change to CleanArchitecture.Core.Abstractions.Services can break CleanArchitecture.Infrastructure.Services, while a change to CleanArchitecture.Infrastructure.Services can't break CleanArchitecture.Core.Abstractions.Services.
- Position
- Below the diagonal: CleanArchitecture.Infrastructure.Services uses a module listed above it, which is the healthy direction.
26→17 src.CleanArchitecture_Web.ClientApp.src.app._shared.services.weather_service uses src.CleanArchitecture_Web.ClientApp.src.app._shared.models.results_model✕
- Connections
- 1 pair of types, where a type in src.CleanArchitecture_Web.ClientApp.src.app._shared.services.weather_service uses a type in src.CleanArchitecture_Web.ClientApp.src.app._shared.models.results_model.
- The types involved
src.CleanArchitecture_Web.ClientApp.src.app._shared.services.weather_service.WeatherService→src.CleanArchitecture_Web.ClientApp.src.app._shared.models.results_model.CreatedResult
- Direction
- src.CleanArchitecture_Web.ClientApp.src.app._shared.services.weather_service uses src.CleanArchitecture_Web.ClientApp.src.app._shared.models.results_model, so a change to src.CleanArchitecture_Web.ClientApp.src.app._shared.models.results_model can break src.CleanArchitecture_Web.ClientApp.src.app._shared.services.weather_service, while a change to src.CleanArchitecture_Web.ClientApp.src.app._shared.services.weather_service can't break src.CleanArchitecture_Web.ClientApp.src.app._shared.models.results_model.
- Position
- Below the diagonal: src.CleanArchitecture_Web.ClientApp.src.app._shared.services.weather_service uses a module listed above it, which is the healthy direction.
26→18 src.CleanArchitecture_Web.ClientApp.src.app._shared.services.weather_service uses src.CleanArchitecture_Web.ClientApp.src.app._shared.models.weather_model✕
- Connections
- 1 pair of types, where a type in src.CleanArchitecture_Web.ClientApp.src.app._shared.services.weather_service uses a type in src.CleanArchitecture_Web.ClientApp.src.app._shared.models.weather_model.
- The types involved
src.CleanArchitecture_Web.ClientApp.src.app._shared.services.weather_service.WeatherService→src.CleanArchitecture_Web.ClientApp.src.app._shared.models.weather_model.CreateWeatherForecast
- Direction
- src.CleanArchitecture_Web.ClientApp.src.app._shared.services.weather_service uses src.CleanArchitecture_Web.ClientApp.src.app._shared.models.weather_model, so a change to src.CleanArchitecture_Web.ClientApp.src.app._shared.models.weather_model can break src.CleanArchitecture_Web.ClientApp.src.app._shared.services.weather_service, while a change to src.CleanArchitecture_Web.ClientApp.src.app._shared.services.weather_service can't break src.CleanArchitecture_Web.ClientApp.src.app._shared.models.weather_model.
- Position
- Below the diagonal: src.CleanArchitecture_Web.ClientApp.src.app._shared.services.weather_service uses a module listed above it, which is the healthy direction.
27→4 CleanArchitecture.Application.Weather.DomainEventHandlers uses CleanArchitecture.Application.Abstractions.DomainEventHandlers✕
- Connections
- 1 pair of types, where a type in CleanArchitecture.Application.Weather.DomainEventHandlers uses a type in CleanArchitecture.Application.Abstractions.DomainEventHandlers.
- The types involved
CleanArchitecture.Application.Weather.DomainEventHandlers.WeatherForecastCreatedDomainEventHandler→CleanArchitecture.Application.Abstractions.DomainEventHandlers.DomainEventHandler
- Direction
- CleanArchitecture.Application.Weather.DomainEventHandlers uses CleanArchitecture.Application.Abstractions.DomainEventHandlers, so a change to CleanArchitecture.Application.Abstractions.DomainEventHandlers can break CleanArchitecture.Application.Weather.DomainEventHandlers, while a change to CleanArchitecture.Application.Weather.DomainEventHandlers can't break CleanArchitecture.Application.Abstractions.DomainEventHandlers.
- Position
- Below the diagonal: CleanArchitecture.Application.Weather.DomainEventHandlers uses a module listed above it, which is the healthy direction.
27→24 CleanArchitecture.Application.Weather.DomainEventHandlers uses CleanArchitecture.Core.Weather.DomainEvents✕
- Connections
- 1 pair of types, where a type in CleanArchitecture.Application.Weather.DomainEventHandlers uses a type in CleanArchitecture.Core.Weather.DomainEvents.
- The types involved
CleanArchitecture.Application.Weather.DomainEventHandlers.WeatherForecastCreatedDomainEventHandler→CleanArchitecture.Core.Weather.DomainEvents.WeatherForecastCreatedDomainEvent
- Direction
- CleanArchitecture.Application.Weather.DomainEventHandlers uses CleanArchitecture.Core.Weather.DomainEvents, so a change to CleanArchitecture.Core.Weather.DomainEvents can break CleanArchitecture.Application.Weather.DomainEventHandlers, while a change to CleanArchitecture.Application.Weather.DomainEventHandlers can't break CleanArchitecture.Core.Weather.DomainEvents.
- Position
- Below the diagonal: CleanArchitecture.Application.Weather.DomainEventHandlers uses a module listed above it, which is the healthy direction.
28→14 CleanArchitecture.Core.Locations.Entities uses CleanArchitecture.Core.Locations.ValueObjects✕
- Connections
- 1 pair of types, where a type in CleanArchitecture.Core.Locations.Entities uses a type in CleanArchitecture.Core.Locations.ValueObjects.
- The types involved
CleanArchitecture.Core.Locations.Entities.Location→CleanArchitecture.Core.Locations.ValueObjects.Coordinates
- Direction
- CleanArchitecture.Core.Locations.Entities uses CleanArchitecture.Core.Locations.ValueObjects, so a change to CleanArchitecture.Core.Locations.ValueObjects can break CleanArchitecture.Core.Locations.Entities, while a change to CleanArchitecture.Core.Locations.Entities can't break CleanArchitecture.Core.Locations.ValueObjects.
- Position
- Below the diagonal: CleanArchitecture.Core.Locations.Entities uses a module listed above it, which is the healthy direction.
28→23 CleanArchitecture.Core.Locations.Entities uses CleanArchitecture.Core.Abstractions.Entities✕
- Connections
- 1 pair of types, where a type in CleanArchitecture.Core.Locations.Entities uses a type in CleanArchitecture.Core.Abstractions.Entities.
- The types involved
CleanArchitecture.Core.Locations.Entities.Location→CleanArchitecture.Core.Abstractions.Entities.AggregateRoot
- Direction
- CleanArchitecture.Core.Locations.Entities uses CleanArchitecture.Core.Abstractions.Entities, so a change to CleanArchitecture.Core.Abstractions.Entities can break CleanArchitecture.Core.Locations.Entities, while a change to CleanArchitecture.Core.Locations.Entities can't break CleanArchitecture.Core.Abstractions.Entities.
- Position
- Below the diagonal: CleanArchitecture.Core.Locations.Entities uses a module listed above it, which is the healthy direction.
29→15 CleanArchitecture.Core.Weather.Entities uses CleanArchitecture.Core.Weather.ValueObjects✕
- Connections
- 1 pair of types, where a type in CleanArchitecture.Core.Weather.Entities uses a type in CleanArchitecture.Core.Weather.ValueObjects.
- The types involved
CleanArchitecture.Core.Weather.Entities.WeatherForecast→CleanArchitecture.Core.Weather.ValueObjects.Temperature
- Direction
- CleanArchitecture.Core.Weather.Entities uses CleanArchitecture.Core.Weather.ValueObjects, so a change to CleanArchitecture.Core.Weather.ValueObjects can break CleanArchitecture.Core.Weather.Entities, while a change to CleanArchitecture.Core.Weather.Entities can't break CleanArchitecture.Core.Weather.ValueObjects.
- Position
- Below the diagonal: CleanArchitecture.Core.Weather.Entities uses a module listed above it, which is the healthy direction.
29→23 CleanArchitecture.Core.Weather.Entities uses CleanArchitecture.Core.Abstractions.Entities✕
- Connections
- 1 pair of types, where a type in CleanArchitecture.Core.Weather.Entities uses a type in CleanArchitecture.Core.Abstractions.Entities.
- The types involved
CleanArchitecture.Core.Weather.Entities.WeatherForecast→CleanArchitecture.Core.Abstractions.Entities.AggregateRoot
- Direction
- CleanArchitecture.Core.Weather.Entities uses CleanArchitecture.Core.Abstractions.Entities, so a change to CleanArchitecture.Core.Abstractions.Entities can break CleanArchitecture.Core.Weather.Entities, while a change to CleanArchitecture.Core.Weather.Entities can't break CleanArchitecture.Core.Abstractions.Entities.
- Position
- Below the diagonal: CleanArchitecture.Core.Weather.Entities uses a module listed above it, which is the healthy direction.
30→19 src.CleanArchitecture_Web.ClientApp.src.app.weather-forecasts.weather-forecasts_component uses src.CleanArchitecture_Web.ClientApp.src.app._shared.services.locations_service✕
- Connections
- 1 pair of types, where a type in src.CleanArchitecture_Web.ClientApp.src.app.weather-forecasts.weather-forecasts_component uses a type in src.CleanArchitecture_Web.ClientApp.src.app._shared.services.locations_service.
- The types involved
src.CleanArchitecture_Web.ClientApp.src.app.weather-forecasts.weather-forecasts_component.WeatherForecastsComponent→src.CleanArchitecture_Web.ClientApp.src.app._shared.services.locations_service.LocationsService
- Direction
- src.CleanArchitecture_Web.ClientApp.src.app.weather-forecasts.weather-forecasts_component uses src.CleanArchitecture_Web.ClientApp.src.app._shared.services.locations_service, so a change to src.CleanArchitecture_Web.ClientApp.src.app._shared.services.locations_service can break src.CleanArchitecture_Web.ClientApp.src.app.weather-forecasts.weather-forecasts_component, while a change to src.CleanArchitecture_Web.ClientApp.src.app.weather-forecasts.weather-forecasts_component can't break src.CleanArchitecture_Web.ClientApp.src.app._shared.services.locations_service.
- Position
- Below the diagonal: src.CleanArchitecture_Web.ClientApp.src.app.weather-forecasts.weather-forecasts_component uses a module listed above it, which is the healthy direction.
30→26 src.CleanArchitecture_Web.ClientApp.src.app.weather-forecasts.weather-forecasts_component uses src.CleanArchitecture_Web.ClientApp.src.app._shared.services.weather_service✕
- Connections
- 1 pair of types, where a type in src.CleanArchitecture_Web.ClientApp.src.app.weather-forecasts.weather-forecasts_component uses a type in src.CleanArchitecture_Web.ClientApp.src.app._shared.services.weather_service.
- The types involved
src.CleanArchitecture_Web.ClientApp.src.app.weather-forecasts.weather-forecasts_component.WeatherForecastsComponent→src.CleanArchitecture_Web.ClientApp.src.app._shared.services.weather_service.WeatherService
- Direction
- src.CleanArchitecture_Web.ClientApp.src.app.weather-forecasts.weather-forecasts_component uses src.CleanArchitecture_Web.ClientApp.src.app._shared.services.weather_service, so a change to src.CleanArchitecture_Web.ClientApp.src.app._shared.services.weather_service can break src.CleanArchitecture_Web.ClientApp.src.app.weather-forecasts.weather-forecasts_component, while a change to src.CleanArchitecture_Web.ClientApp.src.app.weather-forecasts.weather-forecasts_component can't break src.CleanArchitecture_Web.ClientApp.src.app._shared.services.weather_service.
- Position
- Below the diagonal: src.CleanArchitecture_Web.ClientApp.src.app.weather-forecasts.weather-forecasts_component uses a module listed above it, which is the healthy direction.
31→6 CleanArchitecture.Application.Locations.Queries uses CleanArchitecture.Application.Abstractions.Queries✕
- Connections
- 2 pairs of types, where a type in CleanArchitecture.Application.Locations.Queries uses a type in CleanArchitecture.Application.Abstractions.Queries.
- The types involved
CleanArchitecture.Application.Locations.Queries.GetLocationsQuery→CleanArchitecture.Application.Abstractions.Queries.QueryCleanArchitecture.Application.Locations.Queries.GetLocationsQueryHandler→CleanArchitecture.Application.Abstractions.Queries.QueryHandler
- Direction
- CleanArchitecture.Application.Locations.Queries uses CleanArchitecture.Application.Abstractions.Queries, so a change to CleanArchitecture.Application.Abstractions.Queries can break CleanArchitecture.Application.Locations.Queries, while a change to CleanArchitecture.Application.Locations.Queries can't break CleanArchitecture.Application.Abstractions.Queries.
- Position
- Below the diagonal: CleanArchitecture.Application.Locations.Queries uses a module listed above it, which is the healthy direction.
31→7 CleanArchitecture.Application.Locations.Queries uses CleanArchitecture.Application.Abstractions.Repositories✕
- Connections
- 1 pair of types, where a type in CleanArchitecture.Application.Locations.Queries uses a type in CleanArchitecture.Application.Abstractions.Repositories.
- The types involved
CleanArchitecture.Application.Locations.Queries.GetLocationsQueryHandler→CleanArchitecture.Application.Abstractions.Repositories.IRepository
- Direction
- CleanArchitecture.Application.Locations.Queries uses CleanArchitecture.Application.Abstractions.Repositories, so a change to CleanArchitecture.Application.Abstractions.Repositories can break CleanArchitecture.Application.Locations.Queries, while a change to CleanArchitecture.Application.Locations.Queries can't break CleanArchitecture.Application.Abstractions.Repositories.
- Position
- Below the diagonal: CleanArchitecture.Application.Locations.Queries uses a module listed above it, which is the healthy direction.
31→10 CleanArchitecture.Application.Locations.Queries uses CleanArchitecture.Application.Locations.Models✕
- Connections
- 2 pairs of types, where a type in CleanArchitecture.Application.Locations.Queries uses a type in CleanArchitecture.Application.Locations.Models.
- The types involved
CleanArchitecture.Application.Locations.Queries.GetLocationsQuery→CleanArchitecture.Application.Locations.Models.LocationDtoCleanArchitecture.Application.Locations.Queries.GetLocationsQueryHandler→CleanArchitecture.Application.Locations.Models.LocationDto
- Direction
- CleanArchitecture.Application.Locations.Queries uses CleanArchitecture.Application.Locations.Models, so a change to CleanArchitecture.Application.Locations.Models can break CleanArchitecture.Application.Locations.Queries, while a change to CleanArchitecture.Application.Locations.Queries can't break CleanArchitecture.Application.Locations.Models.
- Position
- Below the diagonal: CleanArchitecture.Application.Locations.Queries uses a module listed above it, which is the healthy direction.
31→28 CleanArchitecture.Application.Locations.Queries uses CleanArchitecture.Core.Locations.Entities✕
- Connections
- 1 pair of types, where a type in CleanArchitecture.Application.Locations.Queries uses a type in CleanArchitecture.Core.Locations.Entities.
- The types involved
CleanArchitecture.Application.Locations.Queries.GetLocationsQueryHandler→CleanArchitecture.Core.Locations.Entities.Location
- Direction
- CleanArchitecture.Application.Locations.Queries uses CleanArchitecture.Core.Locations.Entities, so a change to CleanArchitecture.Core.Locations.Entities can break CleanArchitecture.Application.Locations.Queries, while a change to CleanArchitecture.Application.Locations.Queries can't break CleanArchitecture.Core.Locations.Entities.
- Position
- Below the diagonal: CleanArchitecture.Application.Locations.Queries uses a module listed above it, which is the healthy direction.
32→7 CleanArchitecture.Application.Weather.Commands uses CleanArchitecture.Application.Abstractions.Repositories✕
- Connections
- 6 pairs of types, where a type in CleanArchitecture.Application.Weather.Commands uses a type in CleanArchitecture.Application.Abstractions.Repositories.
- The types involved
CleanArchitecture.Application.Weather.Commands.CreateWeatherForecastCommandHandler→CleanArchitecture.Application.Abstractions.Repositories.IRepositoryCleanArchitecture.Application.Weather.Commands.CreateWeatherForecastCommandHandler→CleanArchitecture.Application.Abstractions.Repositories.IUnitOfWorkCleanArchitecture.Application.Weather.Commands.DeleteWeatherForecastCommandHandler→CleanArchitecture.Application.Abstractions.Repositories.IRepositoryCleanArchitecture.Application.Weather.Commands.DeleteWeatherForecastCommandHandler→CleanArchitecture.Application.Abstractions.Repositories.IUnitOfWorkCleanArchitecture.Application.Weather.Commands.UpdateWeatherForecastCommandHandler→CleanArchitecture.Application.Abstractions.Repositories.IRepositoryCleanArchitecture.Application.Weather.Commands.UpdateWeatherForecastCommandHandler→CleanArchitecture.Application.Abstractions.Repositories.IUnitOfWork
- Direction
- CleanArchitecture.Application.Weather.Commands uses CleanArchitecture.Application.Abstractions.Repositories, so a change to CleanArchitecture.Application.Abstractions.Repositories can break CleanArchitecture.Application.Weather.Commands, while a change to CleanArchitecture.Application.Weather.Commands can't break CleanArchitecture.Application.Abstractions.Repositories.
- Position
- Below the diagonal: CleanArchitecture.Application.Weather.Commands uses a module listed above it, which is the healthy direction.
32→21 CleanArchitecture.Application.Weather.Commands uses CleanArchitecture.Application.Abstractions.Commands✕
- Connections
- 6 pairs of types, where a type in CleanArchitecture.Application.Weather.Commands uses a type in CleanArchitecture.Application.Abstractions.Commands.
- The types involved
CleanArchitecture.Application.Weather.Commands.CreateWeatherForecastCommand→CleanArchitecture.Application.Abstractions.Commands.CreateCommandCleanArchitecture.Application.Weather.Commands.CreateWeatherForecastCommandHandler→CleanArchitecture.Application.Abstractions.Commands.CreateCommandHandlerCleanArchitecture.Application.Weather.Commands.DeleteWeatherForecastCommand→CleanArchitecture.Application.Abstractions.Commands.CommandCleanArchitecture.Application.Weather.Commands.DeleteWeatherForecastCommandHandler→CleanArchitecture.Application.Abstractions.Commands.CommandHandlerCleanArchitecture.Application.Weather.Commands.UpdateWeatherForecastCommand→CleanArchitecture.Application.Abstractions.Commands.CommandCleanArchitecture.Application.Weather.Commands.UpdateWeatherForecastCommandHandler→CleanArchitecture.Application.Abstractions.Commands.CommandHandler
- Direction
- CleanArchitecture.Application.Weather.Commands uses CleanArchitecture.Application.Abstractions.Commands, so a change to CleanArchitecture.Application.Abstractions.Commands can break CleanArchitecture.Application.Weather.Commands, while a change to CleanArchitecture.Application.Weather.Commands can't break CleanArchitecture.Application.Abstractions.Commands.
- Position
- Below the diagonal: CleanArchitecture.Application.Weather.Commands uses a module listed above it, which is the healthy direction.
32→28 CleanArchitecture.Application.Weather.Commands uses CleanArchitecture.Core.Locations.Entities✕
- Connections
- 1 pair of types, where a type in CleanArchitecture.Application.Weather.Commands uses a type in CleanArchitecture.Core.Locations.Entities.
- The types involved
CleanArchitecture.Application.Weather.Commands.CreateWeatherForecastCommandHandler→CleanArchitecture.Core.Locations.Entities.Location
- Direction
- CleanArchitecture.Application.Weather.Commands uses CleanArchitecture.Core.Locations.Entities, so a change to CleanArchitecture.Core.Locations.Entities can break CleanArchitecture.Application.Weather.Commands, while a change to CleanArchitecture.Application.Weather.Commands can't break CleanArchitecture.Core.Locations.Entities.
- Position
- Below the diagonal: CleanArchitecture.Application.Weather.Commands uses a module listed above it, which is the healthy direction.
32→29 CleanArchitecture.Application.Weather.Commands uses CleanArchitecture.Core.Weather.Entities✕
- Connections
- 3 pairs of types, where a type in CleanArchitecture.Application.Weather.Commands uses a type in CleanArchitecture.Core.Weather.Entities.
- The types involved
CleanArchitecture.Application.Weather.Commands.CreateWeatherForecastCommandHandler→CleanArchitecture.Core.Weather.Entities.WeatherForecastCleanArchitecture.Application.Weather.Commands.DeleteWeatherForecastCommandHandler→CleanArchitecture.Core.Weather.Entities.WeatherForecastCleanArchitecture.Application.Weather.Commands.UpdateWeatherForecastCommandHandler→CleanArchitecture.Core.Weather.Entities.WeatherForecast
- Direction
- CleanArchitecture.Application.Weather.Commands uses CleanArchitecture.Core.Weather.Entities, so a change to CleanArchitecture.Core.Weather.Entities can break CleanArchitecture.Application.Weather.Commands, while a change to CleanArchitecture.Application.Weather.Commands can't break CleanArchitecture.Core.Weather.Entities.
- Position
- Below the diagonal: CleanArchitecture.Application.Weather.Commands uses a module listed above it, which is the healthy direction.
33→6 CleanArchitecture.Application.Weather.Queries uses CleanArchitecture.Application.Abstractions.Queries✕
- Connections
- 4 pairs of types, where a type in CleanArchitecture.Application.Weather.Queries uses a type in CleanArchitecture.Application.Abstractions.Queries.
- The types involved
CleanArchitecture.Application.Weather.Queries.GetWeatherForecastQuery→CleanArchitecture.Application.Abstractions.Queries.QueryCleanArchitecture.Application.Weather.Queries.GetWeatherForecastQueryHandler→CleanArchitecture.Application.Abstractions.Queries.QueryHandlerCleanArchitecture.Application.Weather.Queries.GetWeatherForecastsQuery→CleanArchitecture.Application.Abstractions.Queries.QueryCleanArchitecture.Application.Weather.Queries.GetWeatherForecastsQueryHandler→CleanArchitecture.Application.Abstractions.Queries.QueryHandler
- Direction
- CleanArchitecture.Application.Weather.Queries uses CleanArchitecture.Application.Abstractions.Queries, so a change to CleanArchitecture.Application.Abstractions.Queries can break CleanArchitecture.Application.Weather.Queries, while a change to CleanArchitecture.Application.Weather.Queries can't break CleanArchitecture.Application.Abstractions.Queries.
- Position
- Below the diagonal: CleanArchitecture.Application.Weather.Queries uses a module listed above it, which is the healthy direction.
33→7 CleanArchitecture.Application.Weather.Queries uses CleanArchitecture.Application.Abstractions.Repositories✕
- Connections
- 2 pairs of types, where a type in CleanArchitecture.Application.Weather.Queries uses a type in CleanArchitecture.Application.Abstractions.Repositories.
- The types involved
CleanArchitecture.Application.Weather.Queries.GetWeatherForecastQueryHandler→CleanArchitecture.Application.Abstractions.Repositories.IRepositoryCleanArchitecture.Application.Weather.Queries.GetWeatherForecastsQueryHandler→CleanArchitecture.Application.Abstractions.Repositories.IRepository
- Direction
- CleanArchitecture.Application.Weather.Queries uses CleanArchitecture.Application.Abstractions.Repositories, so a change to CleanArchitecture.Application.Abstractions.Repositories can break CleanArchitecture.Application.Weather.Queries, while a change to CleanArchitecture.Application.Weather.Queries can't break CleanArchitecture.Application.Abstractions.Repositories.
- Position
- Below the diagonal: CleanArchitecture.Application.Weather.Queries uses a module listed above it, which is the healthy direction.
33→11 CleanArchitecture.Application.Weather.Queries uses CleanArchitecture.Application.Weather.Models✕
- Connections
- 4 pairs of types, where a type in CleanArchitecture.Application.Weather.Queries uses a type in CleanArchitecture.Application.Weather.Models.
- The types involved
CleanArchitecture.Application.Weather.Queries.GetWeatherForecastQuery→CleanArchitecture.Application.Weather.Models.WeatherForecastDtoCleanArchitecture.Application.Weather.Queries.GetWeatherForecastQueryHandler→CleanArchitecture.Application.Weather.Models.WeatherForecastDtoCleanArchitecture.Application.Weather.Queries.GetWeatherForecastsQuery→CleanArchitecture.Application.Weather.Models.WeatherForecastDtoCleanArchitecture.Application.Weather.Queries.GetWeatherForecastsQueryHandler→CleanArchitecture.Application.Weather.Models.WeatherForecastDto
- Direction
- CleanArchitecture.Application.Weather.Queries uses CleanArchitecture.Application.Weather.Models, so a change to CleanArchitecture.Application.Weather.Models can break CleanArchitecture.Application.Weather.Queries, while a change to CleanArchitecture.Application.Weather.Queries can't break CleanArchitecture.Application.Weather.Models.
- Position
- Below the diagonal: CleanArchitecture.Application.Weather.Queries uses a module listed above it, which is the healthy direction.
33→29 CleanArchitecture.Application.Weather.Queries uses CleanArchitecture.Core.Weather.Entities✕
- Connections
- 2 pairs of types, where a type in CleanArchitecture.Application.Weather.Queries uses a type in CleanArchitecture.Core.Weather.Entities.
- The types involved
CleanArchitecture.Application.Weather.Queries.GetWeatherForecastQueryHandler→CleanArchitecture.Core.Weather.Entities.WeatherForecastCleanArchitecture.Application.Weather.Queries.GetWeatherForecastsQueryHandler→CleanArchitecture.Core.Weather.Entities.WeatherForecast
- Direction
- CleanArchitecture.Application.Weather.Queries uses CleanArchitecture.Core.Weather.Entities, so a change to CleanArchitecture.Core.Weather.Entities can break CleanArchitecture.Application.Weather.Queries, while a change to CleanArchitecture.Application.Weather.Queries can't break CleanArchitecture.Core.Weather.Entities.
- Position
- Below the diagonal: CleanArchitecture.Application.Weather.Queries uses a module listed above it, which is the healthy direction.
34→28 CleanArchitecture.Infrastructure uses CleanArchitecture.Core.Locations.Entities✕
- Connections
- 1 pair of types, where a type in CleanArchitecture.Infrastructure uses a type in CleanArchitecture.Core.Locations.Entities.
- The types involved
CleanArchitecture.Infrastructure.WeatherContext→CleanArchitecture.Core.Locations.Entities.Location
- Direction
- CleanArchitecture.Infrastructure uses CleanArchitecture.Core.Locations.Entities, so a change to CleanArchitecture.Core.Locations.Entities can break CleanArchitecture.Infrastructure, while a change to CleanArchitecture.Infrastructure can't break CleanArchitecture.Core.Locations.Entities.
- Position
- Below the diagonal: CleanArchitecture.Infrastructure uses a module listed above it, which is the healthy direction.
34→29 CleanArchitecture.Infrastructure uses CleanArchitecture.Core.Weather.Entities✕
- Connections
- 1 pair of types, where a type in CleanArchitecture.Infrastructure uses a type in CleanArchitecture.Core.Weather.Entities.
- The types involved
CleanArchitecture.Infrastructure.WeatherContext→CleanArchitecture.Core.Weather.Entities.WeatherForecast
- Direction
- CleanArchitecture.Infrastructure uses CleanArchitecture.Core.Weather.Entities, so a change to CleanArchitecture.Core.Weather.Entities can break CleanArchitecture.Infrastructure, while a change to CleanArchitecture.Infrastructure can't break CleanArchitecture.Core.Weather.Entities.
- Position
- Below the diagonal: CleanArchitecture.Infrastructure uses a module listed above it, which is the healthy direction.
35→28 CleanArchitecture.Infrastructure.Configurations uses CleanArchitecture.Core.Locations.Entities✕
- Connections
- 1 pair of types, where a type in CleanArchitecture.Infrastructure.Configurations uses a type in CleanArchitecture.Core.Locations.Entities.
- The types involved
CleanArchitecture.Infrastructure.Configurations.LocationConfiguration→CleanArchitecture.Core.Locations.Entities.Location
- Direction
- CleanArchitecture.Infrastructure.Configurations uses CleanArchitecture.Core.Locations.Entities, so a change to CleanArchitecture.Core.Locations.Entities can break CleanArchitecture.Infrastructure.Configurations, while a change to CleanArchitecture.Infrastructure.Configurations can't break CleanArchitecture.Core.Locations.Entities.
- Position
- Below the diagonal: CleanArchitecture.Infrastructure.Configurations uses a module listed above it, which is the healthy direction.
35→29 CleanArchitecture.Infrastructure.Configurations uses CleanArchitecture.Core.Weather.Entities✕
- Connections
- 1 pair of types, where a type in CleanArchitecture.Infrastructure.Configurations uses a type in CleanArchitecture.Core.Weather.Entities.
- The types involved
CleanArchitecture.Infrastructure.Configurations.WeatherForecastConfiguration→CleanArchitecture.Core.Weather.Entities.WeatherForecast
- Direction
- CleanArchitecture.Infrastructure.Configurations uses CleanArchitecture.Core.Weather.Entities, so a change to CleanArchitecture.Core.Weather.Entities can break CleanArchitecture.Infrastructure.Configurations, while a change to CleanArchitecture.Infrastructure.Configurations can't break CleanArchitecture.Core.Weather.Entities.
- Position
- Below the diagonal: CleanArchitecture.Infrastructure.Configurations uses a module listed above it, which is the healthy direction.
36→34 CleanArchitecture.Infrastructure.AutofacModules uses CleanArchitecture.Infrastructure✕
- Connections
- 1 pair of types, where a type in CleanArchitecture.Infrastructure.AutofacModules uses a type in CleanArchitecture.Infrastructure.
- The types involved
CleanArchitecture.Infrastructure.AutofacModules.InfrastructureModule→CleanArchitecture.Infrastructure.WeatherContext
- Direction
- CleanArchitecture.Infrastructure.AutofacModules uses CleanArchitecture.Infrastructure, so a change to CleanArchitecture.Infrastructure can break CleanArchitecture.Infrastructure.AutofacModules, while a change to CleanArchitecture.Infrastructure.AutofacModules can't break CleanArchitecture.Infrastructure.
- Position
- Below the diagonal: CleanArchitecture.Infrastructure.AutofacModules uses a module listed above it, which is the healthy direction.
37→7 CleanArchitecture.Infrastructure.Repositories uses CleanArchitecture.Application.Abstractions.Repositories✕
- Connections
- 2 pairs of types, where a type in CleanArchitecture.Infrastructure.Repositories uses a type in CleanArchitecture.Application.Abstractions.Repositories.
- The types involved
CleanArchitecture.Infrastructure.Repositories.Repository→CleanArchitecture.Application.Abstractions.Repositories.IRepositoryCleanArchitecture.Infrastructure.Repositories.UnitOfWork→CleanArchitecture.Application.Abstractions.Repositories.IUnitOfWork
- Direction
- CleanArchitecture.Infrastructure.Repositories uses CleanArchitecture.Application.Abstractions.Repositories, so a change to CleanArchitecture.Application.Abstractions.Repositories can break CleanArchitecture.Infrastructure.Repositories, while a change to CleanArchitecture.Infrastructure.Repositories can't break CleanArchitecture.Application.Abstractions.Repositories.
- Position
- Below the diagonal: CleanArchitecture.Infrastructure.Repositories uses a module listed above it, which is the healthy direction.
37→12 CleanArchitecture.Infrastructure.Repositories uses CleanArchitecture.Core.Abstractions.DomainEvents✕
- Connections
- 1 pair of types, where a type in CleanArchitecture.Infrastructure.Repositories uses a type in CleanArchitecture.Core.Abstractions.DomainEvents.
- The types involved
CleanArchitecture.Infrastructure.Repositories.UnitOfWork→CleanArchitecture.Core.Abstractions.DomainEvents.DomainEvent
- Direction
- CleanArchitecture.Infrastructure.Repositories uses CleanArchitecture.Core.Abstractions.DomainEvents, so a change to CleanArchitecture.Core.Abstractions.DomainEvents can break CleanArchitecture.Infrastructure.Repositories, while a change to CleanArchitecture.Infrastructure.Repositories can't break CleanArchitecture.Core.Abstractions.DomainEvents.
- Position
- Below the diagonal: CleanArchitecture.Infrastructure.Repositories uses a module listed above it, which is the healthy direction.
37→23 CleanArchitecture.Infrastructure.Repositories uses CleanArchitecture.Core.Abstractions.Entities✕
- Connections
- 1 pair of types, where a type in CleanArchitecture.Infrastructure.Repositories uses a type in CleanArchitecture.Core.Abstractions.Entities.
- The types involved
CleanArchitecture.Infrastructure.Repositories.UnitOfWork→CleanArchitecture.Core.Abstractions.Entities.AggregateRoot
- Direction
- CleanArchitecture.Infrastructure.Repositories uses CleanArchitecture.Core.Abstractions.Entities, so a change to CleanArchitecture.Core.Abstractions.Entities can break CleanArchitecture.Infrastructure.Repositories, while a change to CleanArchitecture.Infrastructure.Repositories can't break CleanArchitecture.Core.Abstractions.Entities.
- Position
- Below the diagonal: CleanArchitecture.Infrastructure.Repositories uses a module listed above it, which is the healthy direction.
37→34 CleanArchitecture.Infrastructure.Repositories uses CleanArchitecture.Infrastructure✕
- Connections
- 2 pairs of types, where a type in CleanArchitecture.Infrastructure.Repositories uses a type in CleanArchitecture.Infrastructure.
- The types involved
CleanArchitecture.Infrastructure.Repositories.Repository→CleanArchitecture.Infrastructure.WeatherContextCleanArchitecture.Infrastructure.Repositories.UnitOfWork→CleanArchitecture.Infrastructure.WeatherContext
- Direction
- CleanArchitecture.Infrastructure.Repositories uses CleanArchitecture.Infrastructure, so a change to CleanArchitecture.Infrastructure can break CleanArchitecture.Infrastructure.Repositories, while a change to CleanArchitecture.Infrastructure.Repositories can't break CleanArchitecture.Infrastructure.
- Position
- Below the diagonal: CleanArchitecture.Infrastructure.Repositories uses a module listed above it, which is the healthy direction.
38→16 CleanArchitecture.Migrations uses CleanArchitecture.Hosting✕
- Connections
- 1 pair of types, where a type in CleanArchitecture.Migrations uses a type in CleanArchitecture.Hosting.
- The types involved
CleanArchitecture.Migrations.MigrationJob→CleanArchitecture.Hosting.Job
- Direction
- CleanArchitecture.Migrations uses CleanArchitecture.Hosting, so a change to CleanArchitecture.Hosting can break CleanArchitecture.Migrations, while a change to CleanArchitecture.Migrations can't break CleanArchitecture.Hosting.
- Position
- Below the diagonal: CleanArchitecture.Migrations uses a module listed above it, which is the healthy direction.
38→28 CleanArchitecture.Migrations uses CleanArchitecture.Core.Locations.Entities✕
- Connections
- 1 pair of types, where a type in CleanArchitecture.Migrations uses a type in CleanArchitecture.Core.Locations.Entities.
- The types involved
CleanArchitecture.Migrations.MigrationJob→CleanArchitecture.Core.Locations.Entities.Location
- Direction
- CleanArchitecture.Migrations uses CleanArchitecture.Core.Locations.Entities, so a change to CleanArchitecture.Core.Locations.Entities can break CleanArchitecture.Migrations, while a change to CleanArchitecture.Migrations can't break CleanArchitecture.Core.Locations.Entities.
- Position
- Below the diagonal: CleanArchitecture.Migrations uses a module listed above it, which is the healthy direction.
38→34 CleanArchitecture.Migrations uses CleanArchitecture.Infrastructure✕
- Connections
- 1 pair of types, where a type in CleanArchitecture.Migrations uses a type in CleanArchitecture.Infrastructure.
- The types involved
CleanArchitecture.Migrations.MigrationJob→CleanArchitecture.Infrastructure.WeatherContext
- Direction
- CleanArchitecture.Migrations uses CleanArchitecture.Infrastructure, so a change to CleanArchitecture.Infrastructure can break CleanArchitecture.Migrations, while a change to CleanArchitecture.Migrations can't break CleanArchitecture.Infrastructure.
- Position
- Below the diagonal: CleanArchitecture.Migrations uses a module listed above it, which is the healthy direction.
39→34 CleanArchitecture.Migrations.Factories uses CleanArchitecture.Infrastructure✕
- Connections
- 2 pairs of types, where a type in CleanArchitecture.Migrations.Factories uses a type in CleanArchitecture.Infrastructure.
- The types involved
CleanArchitecture.Migrations.Factories.DbContextOptionsFactory→CleanArchitecture.Infrastructure.WeatherContextCleanArchitecture.Migrations.Factories.WeatherContextFactory→CleanArchitecture.Infrastructure.WeatherContext
- Direction
- CleanArchitecture.Migrations.Factories uses CleanArchitecture.Infrastructure, so a change to CleanArchitecture.Infrastructure can break CleanArchitecture.Migrations.Factories, while a change to CleanArchitecture.Migrations.Factories can't break CleanArchitecture.Infrastructure.
- Position
- Below the diagonal: CleanArchitecture.Migrations.Factories uses a module listed above it, which is the healthy direction.
40→12 MediatR uses CleanArchitecture.Core.Abstractions.DomainEvents✕
- Connections
- 1 pair of types, where a type in MediatR uses a type in CleanArchitecture.Core.Abstractions.DomainEvents.
- The types involved
MediatR.MediatorExtensions→CleanArchitecture.Core.Abstractions.DomainEvents.DomainEvent
- Direction
- MediatR uses CleanArchitecture.Core.Abstractions.DomainEvents, so a change to CleanArchitecture.Core.Abstractions.DomainEvents can break MediatR, while a change to MediatR can't break CleanArchitecture.Core.Abstractions.DomainEvents.
- Position
- Below the diagonal: MediatR uses a module listed above it, which is the healthy direction.
40→23 MediatR uses CleanArchitecture.Core.Abstractions.Entities✕
- Connections
- 1 pair of types, where a type in MediatR uses a type in CleanArchitecture.Core.Abstractions.Entities.
- The types involved
MediatR.MediatorExtensions→CleanArchitecture.Core.Abstractions.Entities.AggregateRoot
- Direction
- MediatR uses CleanArchitecture.Core.Abstractions.Entities, so a change to CleanArchitecture.Core.Abstractions.Entities can break MediatR, while a change to MediatR can't break CleanArchitecture.Core.Abstractions.Entities.
- Position
- Below the diagonal: MediatR uses a module listed above it, which is the healthy direction.
40→34 MediatR uses CleanArchitecture.Infrastructure✕
- Connections
- 1 pair of types, where a type in MediatR uses a type in CleanArchitecture.Infrastructure.
- The types involved
MediatR.MediatorExtensions→CleanArchitecture.Infrastructure.WeatherContext
- Direction
- MediatR uses CleanArchitecture.Infrastructure, so a change to CleanArchitecture.Infrastructure can break MediatR, while a change to MediatR can't break CleanArchitecture.Infrastructure.
- Position
- Below the diagonal: MediatR uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
At a glance — Domain Modelling
At a glance — Event-Driven
At a glance — Accessibility
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A03:2025 — Software Supply Chain Failures | 63 | High / Critical |
| A02:2025 — Security Misconfiguration | 37 | High / Critical |
| A05:2025 — Injection | 8 | Medium |
| A07:2025 — Authentication Failures | 3 | High / Critical |
Roadmap
Top priorities: Resolve the 1 Leaked secret finding(s) in Secret Scanning — start with REDACTED; Codify backups + geo-recovery in IaC and document RTO/RPO and the restore procedure — a persistence guard alone is not disaster recovery; Add tests that import the unreached modules (directly or through their public entry).
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 1 Leaked secret finding(s) in Secret Scanning — start with REDACTED. | +10.4 pts | Low | Secret Scanning |
| Codify backups + geo-recovery in IaC and document RTO/RPO and the restore procedure — a persistence guard alone is not disaster recovery. | +6.1 pts | Medium | DR & Backup |
| Add tests that import the unreached modules (directly or through their public entry). | +6.1 pts | Medium | Test Coverage |
| Define repositories per aggregate root and keep the query handle inside them; reach child entities through their root so invariants can't be bypassed. | +3.4 pts | Medium | Repository granularity |
| Add eslint and `tsc --noEmit` as package.json scripts and run them in CI. | +3.1 pts | Medium | Tooling |
| Adopt strongly-typed ids across the domain — finish the migration or document the boundary; primitive ids invite transposed-argument bugs. | +3.0 pts | Medium | Strongly-typed ids |
| Move business rules onto the aggregates/entities they govern so invariants are enforced at the source, not in anemic services. | +1.3 pts | Medium | Rich vs anemic model |
| 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. | +0.9 pts | Medium | Architecture documentation |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 0.0 | Slop | Secret Scanning: Leaked secret: REDACTED |
| REDACTED | 1.4 | Slop | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 1.9 | Slop | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 1.9 | Slop | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 2.0 | Mixed | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 3.7 | Mixed | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 5.9 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| REDACTED | 6.2 | Near-clean | IaC & Container Security: Medium IaC: REDACTED |
| REDACTED | 6.9 | Near-clean | IaC & Container Security: Medium IaC: REDACTED |
| .editorconfig | 7.6 | Near-clean | Explicit Debt: AnalyzerSeverityNone |
| REDACTED | 7.9 | Near-clean | Static Analysis (SAST): Medium: REDACTED |
| REDACTED | 9.0 | Near-clean | Static Analysis (SAST): Low: REDACTED |
How the grades work
A definite problem that already costs you something and drags the score down: a missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here tends to cause failures elsewhere.
Likely wrong, but not failing yet. It degrades the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to carry for two years either.
Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.
Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.
Methodology & how to trust this report
This survey is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. All 103 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.9, the weighted average across measured dimensions.
What we checked — 103 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, 146 of 161 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Canine Code Analyzer duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy · checkov | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 · 3.2.533 | ✓ deterministic |
Run transparency — what happened this run
- D12 Dependency Hygiene — 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. `dotnet list package` did not return usable output (restore or query failed); no outdated/vulnerable/deprecated data to assess. The tool said: error: The imported file "$(MSBuildExtensionsPath32)/Microsoft/VisualStudio/v$(VisualStudioVersion)/CodeSharing/Microsoft.CodeSharing.Common.Default.props" does not exist and appears to be part of a Visual Studio component. This file may require MSBuild.exe in order to be imported successfully, and ….
- D15 Churn × Complexity Hotspots — measured, with a gap in what it reached — 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. Git history depth insufficient — this repository has 24 commit(s), too few for a reliable trend signal. The clone is complete, so there is no deeper history to fetch: the signal returns as the project accumulates history.
- D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Single-maintainer repository — bus factor is not applicable (2 contributor(s) across 24 commit(s) sampled, automation and bot accounts excluded). One of them holds 96% of the history; the other 1 hold 4% each on average, below the 5% at which there is somebody to hand the work to. That is a single maintainer with drive-by contributors, not a team whose knowledge has concentrated — so the bus factor is not applicable and there is nothing here for the owner to act on.
- D17 Explicit Debt — 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. The C# workspace loaded this repository's projects but reported a load failure, and the dead-code reference search is unreliable over a graph that did not load cleanly, so it was skipped. The other debt markers on this row were read; dead symbols were not, and their absence from the score is not a finding that the code has none. First load diagnostic: Failure: Cannot open project 'docker-compose.dcproj' because the file extension '.dcproj' is not associated with a language.
- D17 Explicit Debt — 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. The 1 deducted marker(s) and the 0.3/KLoC density on this row were taken over this repository's .NET projects ALONE: .ts (321 lines, 16% of production source) went unread, because every marker collector on this path is reached through a C# workspace. D17's marker collectors need a compiler we do not have for that language, so none of its nine marker kinds were read there. The debt in that source is UNMEASURED — its absence from the score above is a gap in this analyzer's language coverage, not a finding that the code carries none.
- D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This kind did not reach the 95 % precision gate in three adjudicated runs (docs/plans/deterministic-engine/adjudication/D19-sample3-v3.md), so by the pre-registered fallback it publishes no row until a re-measurement shows it does. The candidates are counted here, not reported as findings, and the score does not include them.
- D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This kind did not reach the 95 % precision gate in three adjudicated runs (docs/plans/deterministic-engine/adjudication/D19-sample3-v3.md), so by the pre-registered fallback it publishes no row until a re-measurement shows it does. The candidates are counted here, not reported as findings, and the score does not include them.
- D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D21's deterministic naming rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. Until then its declarations carry no naming verdict this run — this says nothing about whether its names are consistent.
- 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.
- D27 Navigability — 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. Tracing effort is measured over resolved call sites, and all 1029 sampled here came from .cs files. This repository's .ts source is a material share of its production lines and contributed none, so the score above is a verdict about the part that was read. Not a finding that the unread half navigates well — it is unmeasured.
- D30 Dependency Vulnerabilities — measured, with a gap in what it reached — 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 solution did not restore on the analyzer's .NET SDK (an SDK/target-framework/restore mismatch, common for an older codebase), so there was no restored dependency graph to scan. 2 of 3 declared ecosystem(s) (npm,osv) WERE scanned and every vulnerability they reported is included in this result; nuget was not, so this dimension's score covers less than the dependency surface this repository declares, and nothing here is evidence that nuget is free of known-vulnerable dependencies.
- D32 Data Compliance (PII/GDPR) — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `src/CleanArchitecture.Api/Program.cs` produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
- 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 (24 commit(s) sampled).
- D35 Change Coupling — measured, with a gap in what it reached — 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. Git history depth insufficient — this repository has 24 commit(s), too few for a reliable change-coupling signal. The clone is complete, so there is no deeper history to fetch: the signal returns as the project accumulates history.
- D39 IL Efficiency — 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. `dotnet build` exited 1 with a compiler/MSBuild diagnostic, so there were no assemblies to read IL from. The build itself is D18's row, with the ask; nothing further is charged here.
- AXR1 Runtime accessibility — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via DockerCompose (REDACTED). compose up failed (exit 1 — a container did not start, exited, or never became healthy) — time="2026-11-08T01:39:02Z" level=warning msg="The \"DOCKER_REGISTRY\" variable is not set. Defaulting to a blank string." time="2026-11-08T01:39:02Z" level=warning msg="The \"DOCKER_REGISTRY\" variable is not set. Defaulting to a blank string." time="2026-11-08T01:39:02Z" level=warning msg="The \"DOCKER_REGISTRY\" variable is not set. Defaulting to a blank string." no service selected; runtime evidence skipped.
- DM8 Value-object opportunities — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check finds primitive parameters that travel together through several signatures of the domain (a missing value object). Its deterministic rule has not yet shown 95 % precision on adjudicated rows, so the clumps it finds are counted here and not published as findings, and the card carries no score. That is a limit of the analyzer, not a finding about your code.
- 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.
- 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.
- D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D18 Solution Shape: Build integrity reflects whether the solution compiled in this environment — a build that needs a private feed, a specific SDK, or a generated file absent from the repo can read as broken when it is merely unreproducible here.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
- D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
- 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.
- D40 Network Egress Confinement: Egress confinement is read from committed Kubernetes manifests — a policy applied out-of-band (cluster-default deny, a service mesh, or a cloud firewall/security group off-repo) is invisible, and a present NetworkPolicy is declared config, not proof the cluster admission-controller actually enforces it at runtime.
- D41 Kernel & Syscall Confinement: Syscall/MAC confinement is read from committed manifests — a profile applied by a cluster-wide PodSecurity default or a mutating webhook off-repo isn't seen, and a declared seccomp/AppArmor profile is config presence, not proof the node's kernel actually loaded and enforced it.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a REDACTED (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- AC2 Forms & labels: Label association is read from static markup — a label wired up at runtime (JS-set aria-labelledby, framework-injected ids) reads as missing, a present label says nothing about whether its text is correct. A known UI-library field component (e.g. a JSX <TextField>) is now checked conservatively — flagged only when it carries NO label/aria-label/aria-labelledby/id/name — but wrapper/context-labelled libraries (Chakra/Radix FormControl+FormLabel) aren't statically visible (possible false positive) and non-JSX lowercased components are still skipped. A click handler on a plain element is now asked for a name too (it is a control the author declared), but the subtree test that answers it is deliberately generous: any DYNAMIC text expression in the subtree counts as a name, so an icon chosen by a ternary ({cond ? <IconA/> : <IconB/>}) reads as named, and a glyph component from a library the icon-import list does not know still names its parent. A clean result is "no unlabelled control found", not a labelling proof.
- AC3 Page structure: Page structure is read from the static markup tree — landmarks, headings and lang injected at runtime aren't seen, heading ORDER is checked structurally (not against the rendered visual hierarchy), and lang/title/main fire only on full documents, never partials, and the data-table check sees header-cell presence (a <th> exists), not whether each header correctly associates with its cells. Static readiness, not conformance.
- AC5 ARIA correctness: ARIA correctness is checked against the static role/attribute shape — roles/attributes set dynamically aren't seen, a valid role says nothing about whether it matches the element's real behaviour, and required-state checks are suppressed when a JSX spread could supply them. The two-branch toggle check (a control whose state is conveyed only by which of two mutually exclusive branches renders) reads CONDITIONALS THAT ARE ATTRIBUTES — Vue v-if/v-else/v-show and Alpine x-if/x-show — so the same toggle written as a Svelte {#if} block or a JSX ternary is control flow the markup model never projects as a branch and is not seen at all.
- AC6 Visual & motion safety: Contrast and motion safety are PARTIAL by construction — literal colours (hex/rgb/hsl/named) in inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS top-level declarations are read (same-rule/same-element colour+background pairs only); computed/runtime/theme colour, external-CDN stylesheets, CSS-in-JS dynamic (${…}) and nested-selector colours, cross-element pairs and image contrast stay out of reach, so a clean result is bounded by what the static CSS itself shows.
- AC7 A11y enforcement: Enforcement is scored from in-repo config/CI evidence only — an a11y gate enforced in external tooling with no in-repo trace can't be credited, and a configured linter is presence, not proof the rules actually run or block a merge.
- 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.
- P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
- P5 DR & Backup: Backup/restore and disaster-recovery readiness is judged from in-repo evidence — a config that exists is not a tested restore, so the absence of positive evidence is reported as "not evidenced", never scored as present.
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. Measured on part of this repository only: .ts (16% of production source) was not exposed to THIS dimension's token comparison and is not in this count; duplication there is measured by R10 Code Duplication, the frontend lens's card running the same clone algorithm over the JS/TS token stream.
D5 · Coupling
14 projects, 0 dependency cycle(s), 0 unstable depended-on project(s).
D6 · Cohesion (LCOM4)
0 of 9 classes have LCOM4 above 3.
D9 · Test Distribution
63 test methods: 60 unit, 0 integration, 0 BDD, 3 e2e.
D10 · Test Quality
0 skipped, 0 zero-assertion, 1 mock references across 63 tests.
D11 · Test Reliability
0 flaky across 3 measured tier(s). unit: measured (0 flaky); integration: measured (0 flaky); e2e: measured (0 flaky).
D13 · Secret Scanning
1 secret(s) detected.
What to do
- Resolve the 1 Leaked secret finding(s) in Secret Scanning — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- 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 270 packages use a banned license. ★ DEPTH: this repository's MSBuild projects declare 43 direct `PackageReference`(s), and 207 further package(s) were reached beyond them by closing the graph over nuget.org's own nuspec dependency graph — so a banned licence pulled in only by a dependency's OWN dependencies is inside this verdict. A package whose licence nuget.org could not be asked for is not graded, and version ranges are taken at their lower bound, so this is the closure as that graph states it rather than a restored consumer's exact resolution.
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window.
D17 · Explicit Debt
1 deducted debt markers + unmeasured dead symbols across 1647 LoC in the .NET projects (0.3/KLoC) → score 9.5. Dead code not measured: the solution did not load cleanly, so the reference search was skipped. Measured on the .NET source only: .ts (16% of production source) was not read, and carries at least 0 uncounted task marker(s) in 0 file(s).
What to do
- Resolve the 1 AnalyzerSeverityNone finding(s) in Explicit Debt — start with .editorconfig. — One of this dimension's main actionable groups (1 issue-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
14 projects, 105 source files, 3231 hand-written lines of code (1647 production / 1584 test — the split is derived per file: test is what its project, its own path, or a compile-guarded region marks as test, and a file carrying no test signal counts as production), plus 368 generated (machine-written code — designer, scaffolded and tool-emitted files — excluded from quality), 20 inter-project edges.
D19 · Documentation Quality
2 of 2 documentation facets pass in full. 3 document(s) read across 10 unit(s).
D26 · Project Cohesion
0 of 14 projects flagged as possibly oversized/incoherent.
D27 · Navigability
94 % of calls cross a namespace and 13 % go through an interface, but 98 % of collaborators are co-located — so a call's collaborators sit together and tracing stays easy. Baseline: small — navigation cost is tolerated. Measured over the .cs source only — this repository's .ts was not sampled for call sites, so this score covers part of the tree, not all of it.
D28 · Secrets (history)
1 finding(s): 0 critical, 1 high, 0 medium, 0 low. Remediation for historically-committed secrets is credential rotation — they remain in history regardless of later deletion.
What to do
- Resolve the 1 High secret finding(s) in Secrets (history) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 1 Rotate the exposed credentials finding(s) in Secrets (history). — One of this dimension's main actionable groups (1 recommendation-level).
D29 · Static Analysis (SAST)
8 finding(s): 0 critical, 0 high, 6 medium, 2 low. semgrep hit a parse error in 1 file(s) — `src/CleanArchitecture.Api/Program.cs` (line 38) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them.
What to do
- Resolve the 6 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (5), REDACTED. — One of this dimension's main actionable groups (6 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 recommendation-level).
D30 · Dependency Vulnerabilities
63 finding(s): 6 critical, 45 high, 8 medium, 4 low. Partial dependency scan: 2 of 3 declared ecosystem(s) were scanned (npm,osv), and the findings above are real and complete for them. nuget was not scanned (nuget: the solution did not restore on the analyzer's .NET SDK (an SDK/target-framework/restore mismatch, common for an older codebase), so there was no restored dependency graph to scan), so this is not the whole dependency surface and the result is reported at reduced confidence.
What to do
- Resolve the 43 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (43). — One of this dimension's main actionable groups (43 issue-level).
- Resolve the 6 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (6). — One of this dimension's main actionable groups (6 issue-level).
- Resolve the 2 High vulnerability finding(s) in Dependency Vulnerabilities — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
D31 · IaC & Container Security
37 finding(s): 0 critical, 7 high, 22 medium, 8 low.
What to do
- Resolve the 22 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (7), REDACTED (5), REDACTED (5). — One of this dimension's main actionable groups (22 warning-level).
- Resolve the 7 High IaC finding(s) in IaC & Container Security — start with REDACTED (2), REDACTED (2), REDACTED. — One of this dimension's main actionable groups (7 issue-level).
- Resolve the 8 Low IaC finding(s) in IaC & Container Security — start with REDACTED (2), REDACTED (2), REDACTED (2). — One of this dimension's main actionable groups (8 recommendation-level).
D35 · Change Coupling
No strong hidden change-coupling between production files.
D40 · Network Egress Confinement
0/2 network-egress controls present (network policy, egress restriction).
What to do
- Resolve the 1 No network policy finding(s) in Network Egress Confinement. — One of this dimension's main actionable groups (1 recommendation-level).
D41 · Kernel & Syscall Confinement
0/3 workload(s) run every container under a seccomp profile; 0/3 declare an AppArmor/SELinux profile.
What to do
- Resolve the 3 No seccomp profile finding(s) in Kernel & Syscall Confinement — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (3 recommendation-level).
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 14 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
AC2 · Forms & labels
AC3 · Page structure
- No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>. — src/CleanArchitecture.Web/ClientApp/src/index.html:2
What to do
- Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh.
AC5 · ARIA correctness
AC6 · Visual & motion safety
AC7 · A11y enforcement
- No accessibility enforcement found — no a11y linter (@angular-eslint/eslint-plugin-template (a11y rules)) and no axe/pa11y/Lighthouse in tests or CI. Start with the linter to catch issues at author time. What was searched, so you can tell an absence from a miss: the 5 markup file(s) this pass actually assessed, the linter configuration checked in beside them, and this repository's test and CI files — matched by name against the accessibility checkers this dimension carries. An audit run outside the repository, a hosted scanner, or a check whose name is not one of those, is not seen here. — src/CleanArchitecture.Web/ClientApp/package.json:34
What to do
- Enforce accessibility in the toolchain: add @angular-eslint/eslint-plugin-template (a11y rules), then assert with your test runner's axe binding (jest-axe, vitest-axe, cypress-axe or @axe-core/playwright) in tests, then gate axe/pa11y/Lighthouse in CI.
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
DM1 · Aggregate boundaries
DM10 · One transaction, one aggregate
DM11 · Constructible invalid state
DM12 · Ambient inputs in the domain
DM2 · Strongly-typed ids
- `WeatherForecast.LocationId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that. — src/CleanArchitecture.Core/Weather/Entities/WeatherForecast.cs:41
What to do
- Adopt strongly-typed ids across the domain — finish the migration or document the boundary; primitive ids invite transposed-argument bugs.
DM3 · Integration-event coupling
DM4 · Rich vs anemic model
- `Location` is an aggregate/entity with 3 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — src/CleanArchitecture.Core/Locations/Entities/Location.cs:7
What to do
- Move business rules onto the aggregates/entities they govern so invariants are enforced at the source, not in anemic services.
DM5 · Encapsulated state
DM6 · Domain ↔ infrastructure boundary
DM7 · Repository granularity
- `IRepository` returns `IQueryable` from `GetAll`. That hands the caller the persistence engine rather than an aggregate: query composition, and with it the shape of what gets loaded, moves out of the repository and out of the aggregate's reach — and the contract can no longer be implemented by anything that is not that ORM. Return the aggregate (or a list of them) from methods that name the question being asked. — src/CleanArchitecture.Application/Abstractions/Repositories/IRepository.cs:5
What to do
- Define repositories per aggregate root and keep the query handle inside them; reach child entities through their root so invariants can't be bypassed.
DM9 · Scattered domain decisions
ED1 · Handler temporal coupling
ED2 · Event/command shape
ED3 · Event naming
ED4 · Outbox / dual-write
GD1 · Unfinished & placeholder code
IC1 · Incompleteness & stubs
M1 · Documentation (README)
What to do
- Add a README to the 8 of 8 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
M4 · Documentation accuracy
P11 · BDD / executable specs
P2 · Observability
- Only 5/7 service-like projects use logging (pure contract/DTO projects are excluded — they have nothing to log). Of those 7, 4 ship a process this repository operates; the rest are libraries their consumer hosts, where the logging decision belongs to the host.
What to do
- Extend structured logging across the projects you operate, and give the library ones a diagnostics seam instead — an `EventSource`/`ActivitySource` the host can subscribe to, or an optional logger on your options object — rather than taking a logging dependency on your consumers' behalf.
- Add OpenTelemetry tracing/metrics (ActivitySource / AddMetrics) so requests are traceable across the system, not just health-probable.
P4 · Deployment & Rollback
What to do
- Add an approval/environment gate (required reviewers / protection rules) before production promotion.
P5 · DR & Backup
- A persistence guard (data volume / purge-protection) was found, but no backup, geo-recovery or RTO/RPO controls were evidenced — a volume that survives a container recreate is not a tested restore from catastrophic loss.
What to do
- Codify backups + geo-recovery in IaC and document RTO/RPO and the restore procedure — a persistence guard alone is not disaster recovery.
P8 · Schema migrations
PF3 · Async & latency hygiene
R1 · Type Safety
What to do
- Migrate the remaining .js/.jsx files to TypeScript.
R10 · Code Duplication
R2 · Cyclomatic Complexity
R3 · Large Files
R4 · Test Coverage
- 0% of 11 production file(s) reachable from 0 test file(s) via the import graph — 'production' here is the RESIDUE: every source file left once tests, tooling, generated output, config, declarations and declaration-only modules, fixture corpora, type fixtures, behaviour-free data modules, re-export barrels, registration/constant data modules and service workers are set aside, so the percentage is taken over a smaller denominator than the workspace's file count
What to do
- Add tests that import the unreached modules (directly or through their public entry).
R5 · Dependency Freshness
What to do
- Bump outdated dependencies to current versions to limit upgrade debt.
R6 · Tooling
- test ✓ · lint ✗ · typecheck ✗ — read from this repository's package.json scripts and corroborated against its CI workflows. A script counts when its name or command matches the step: `test` for the suite, `lint` or `prettier` for linting, `typecheck`/`type-check`/`tsc` for type checking. ✗ therefore means no script or CI step under those names was found, NOT that the step is absent from your pipeline — a task invoked by a runner this check does not read, or named something else entirely, is not seen and is worth confirming before acting on a cross. A ✓ means the wiring is DECLARED — a script or CI step under those names exists. It is not a statement that the step passes, or that it runs at all: nothing here installs a dependency or executes a suite.
What to do
- Add eslint and `tsc --noEmit` as package.json scripts and run them in CI.
R7 · Dead Code
- Unreachable from the 2 application, 5 tooling and 0 test entry point(s) detected in this repo. Gate removals on `npm run build` — an undetected custom entry would make these reachable.
- no import path from any entry point (2 application, 5 tooling, 0 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make (×2) — src/CleanArchitecture.Web/ClientApp/src/test.ts, src/CleanArchitecture.Web/ClientApp/src/app/app.server.module.ts
- Nothing imports this binding — it is safe to review for removal. — src/CleanArchitecture.Web/ClientApp/src/app/_shared/models/results.model.ts:5
What to do
- Delete the dead files and unused exports — every line is maintenance cost and rebuild-estimate inflation with zero runtime value.
R8 · Dependency Hygiene
- Declared in src/CleanArchitecture.Web/ClientApp/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it. (×3)
What to do
- Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.
R9 · Circular Imports
S1 · Web-Security Posture
- Set: X-Content-Type-Options, X-Frame-Options. Missing: Content-Security-Policy, Strict-Transport-Security — the four headers that carry the points of this card's security-headers term (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options), 0.5 each. (−1.0 on this card.) — src/CleanArchitecture.Api/Program.cs:79
What to do
- Add Content-Security-Policy, Strict-Transport-Security beside the headers already set; Content-Security-Policy is the one that pays for itself first, then Strict-Transport-Security, then nosniff and a frame policy.
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
- `_context` is never created by `UnitOfWork` — every assignment to it takes a constructor parameter — yet this type disposes it here (line 85). Its declared type `WeatherContext` is an abstract class, so the instance came from whoever chose and created it, and that owner decides when it ends. Disposing it from here reaches outside this object's lifetime: a dependency shared with the rest of the process is torn down when THIS instance goes away, and the real owner's later `Dispose()` runs a second time on an object already disposed. Drop the call — a type disposes what it constructed, and only that. If this dependency genuinely is exclusive to this instance, construct it here (or take an owned factory) so the ownership is stated in the code rather than assumed. — src/CleanArchitecture.Infrastructure/Repositories/UnitOfWork.cs:85
What to do
- Each finding names the value and the span that decides who owns it — the `new` that created it, or the constructor parameter that handed it over. Confirm ownership from that span, then make the disposal match it: release what this type created, leave what it was injected with to whoever created THAT, and drop a finalizer whose type holds nothing unmanaged to release.
X19 · Unrestored process-global state
X2 · Cancellation propagation
- Only 7/27 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. (×20) — src/CleanArchitecture.Infrastructure/Extensions/MediatorExtensions.cs:9, src/CleanArchitecture.Infrastructure/Extensions/MediatorExtensions.cs:26, src/CleanArchitecture.Infrastructure/Repositories/Repository.cs:28, …
What to do
- Thread a CancellationToken through async methods so work stops promptly on cancellation.
X20 · Mistyped argument guard
X21 · Side-effecting pattern guard
X22 · Contradicted release guard
X23 · Unguarded diagnostic materialisation
X24 · Document value interpolated into markup unescaped
X25 · Inert configuration knob
X26 · Unsynchronised callback handoff
X27 · Collection changed while being enumerated
X28 · Index access outside its own emptiness guard
X29 · Per-element action decided by a fixed element
X3 · Exception handling
X30 · Support guard that admits what it rejects
X32 · Type resolved by simple name across every loaded assembly
X4 · Structured logging
- Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it. — src/CleanArchitecture.Api/Infrastructure/Filters/HttpGlobalExceptionFilter.cs:21
What to do
- Interpolated log message defeats structured logging
X5 · Nullable reference types
- ~0.2 `!` suppressions per 1k syntax nodes — 2 suppression(s) across the 8999 syntax node(s) in code where nullable warnings are ENABLED, which is the only code a `!` can suppress anything in (a `!` under `#nullable disable` is inert and is not counted, and its file's nodes are not in the denominator). Each one tells the compiler to trust you about null, suppressing the very safety NRTs provide.
What to do
- Enable <Nullable>enable</Nullable> across all projects and resolve warnings rather than suppressing with `!`.
WCAG coverage — what static analysis assessed
| Dimension | WCAG 2.2 A/AA criteria | Coverage |
|---|---|---|
| AC2 · Forms & labels | 1.3.1, 3.3.2, 4.1.2 | Partial signal |
| AC3 · Page structure | 1.4.4, 2.2.1, 2.4.1, 2.4.2, 3.1.1, 4.1.2 | Partial signal |
| AC5 · ARIA correctness | 4.1.2 | Partial signal |
| AC6 · Visual & motion safety | 1.4.3, 2.4.7 | Partial — literal CSS only |
| AC7 · A11y enforcement | enforcement — no page criterion | Enforcement posture (process) |
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 75% | Strong | Solid. |
| Architecture | 86% | Exemplary | Solid. |
| Maturity | 69% | Adequate — gated by M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 36% | Adequate — gated by R4, R6, P5 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 80% | Strong | Solid. |
| Domain Modelling | 57% | Adequate — gated by DM2, DM7 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Event-Driven | 100% | Exemplary | Strongest area. |
| Accessibility | 69% | Strong | Solid. |
| Performance | 100% | Exemplary | Solid. |
Unscored — 2 check(s) recorded observations but carry no score
- SC1 Supply-chain hygiene — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X10 Duplicated predicate — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 1 control(s) we could not find positive evidence for
- P6 Release Hygiene — not evidenced — no changelog, version stamp or semver release tag in the repo
Not included — 40 check(s) not relevant to this codebase
- AC1 Text alternatives — No image/media element found in the parsed markup — AC1 not applicable here.
- AC4 Keyboard semantics — No interactive element found in the parsed markup — AC4 not applicable here.
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXR1 Runtime accessibility — compose up failed (exit 1 — a container did not start, exited, or never became healthy) — time="2026-11-08T01:39:02Z" level=warning msg="The \"DOCKER_REGISTRY\" variable is not set. Defaulting to a blank string." time="2026-11-08T01:39:02Z" level=warning msg="The \"DOCKER_REGISTRY\" variable is not set. Defaulting to a blank string." time="2026-11-08T01:39:02Z" level=warning msg="The \"DOCKER_REGISTRY\" variable is not set. Defaulting to a blank string." no service selected; runtime evidence skipped This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
- C1 Data Protection — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
- C2 Access Controls — This is a dotnet-new template — authorization is deferred to the application you build from it. Add [Authorize]/policies (or imperative guards) when you wire up real users; until then there are no real endpoints to protect.
- C3 Audit Trail — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
- C4 Data Retention — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
- C5 Data-Subject Rights — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
- D12 Dependency Hygiene — Dependency hygiene not measured
- D16 Bus Factor — single-maintainer repository — bus factor is not applicable
- D20 ADR Quality — N/A — this repo declares itself a template / kata / sample / demo; a formal ADR log is deferred to a real application built from it.
- D21 Naming Consistency — Naming consistency is measured on C# and TypeScript only; JavaScript not measured.
- D22 Internal API Consistency — No intentionally-exposed public API to evaluate for consistency.
- D23 Boundary Type-Coupling — small single-context codebase (1,647 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 (CleanArchitecture.Core), which is a layered codebase, not two contexts. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D24 Comment Value — Too few judgeable comments (24 of at least 30); comment value is not applicable here.
- D25 ADR Conformance — no ADRs to check
- D32 Data Compliance (PII/GDPR) — 1 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
- D34 Knowledge Freshness — too few commits to judge knowledge freshness
- D36 Supply-chain Provenance & Signing — This is a dotnet-new template — it produces no released artifact to attest. Supply-chain provenance, signing and SBOM are deferred to the application you build from it (add SLSA provenance / cosign signing / an SBOM in your app's release pipeline).
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- D39 IL Efficiency — IL not measured — the target did not build
- D42 Runtime Threat Enforcement — The repository ships application workloads but no cluster-governance resources (CRDs, admission webhooks, or a committed policy engine). Runtime threat-detection (Falco/Tetragon) and admission control (Kyverno/OPA-Gatekeeper/PodSecurity) are cluster-OPERATOR controls owned by the platform, not shipped by an application repo/chart — nothing for this repo to assess.
- D7 Architectural Integrity — no checkable ADRs and no dependency cycles — architectural integrity not assessed
- D8 Code Coverage — Coverage NOT MEASURED: the .NET half could not be measured — no coverage produced (collector absent, or test run exceeded the inline budget); the JavaScript/TypeScript half could not be measured — the JavaScript/TypeScript suite(s) run through a browser-driven runner the coverage collector does not drive — src/CleanArchitecture.Web/ClientApp/ (karma) — a gap in the analyzer, not something this repository is missing. This repository's production source spans both ecosystems, and no partial figure is published as if it were the whole: coverage is excluded from the score rather than counted as a near-zero. The named suite step is one the repository's maintainers can perform; once it passes, the real number is measured on the next scan. Alternatively, commit the lcov/Cobertura report your CI produces and it is read without a re-run.
- 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)
- ED5 Idempotency — not scored — 3 of 4 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
- P1 CI/CD gates — This repo declares itself a template / kata / sample / demo — code meant to be read or copied, not operated. Automated CI/CD gates are deferred to the application you build from it, so their absence is not a defect here. The dimension reactivates once the repo becomes a real app.
- P12 CI test-gate honesty — no CI workflow found
- P3 Security & performance tooling — This repo declares itself a template / kata / sample / demo — code meant to be read or copied, not operated. SAST, secret/dependency scanning and performance benchmarks are deferred to the application you build from it, so their absence is not a defect here. The dimension reactivates once the repo becomes a real app.
- P7 Outbound HTTP resilience — no outbound HTTP usage detected — no HttpClient/IHttpClientFactory/AddHttpClient in source, and no Refit/RestSharp/Flurl.Http namespace or package reference
- P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (Cobertura — `dotnet test --collect:"XPlat Code Coverage"` with a `coverlet.collector` PackageReference) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures, or wire coverage collection into CI, to enable this cross-layer check
- PF1 Benchmark discipline — Performance is assessed only for perf-relevant repos — a packaged library, one that ships benchmarks, or one already using allocation-aware APIs. This repo isn't one, so the Performance lens is not applicable and is excluded from the score.
- PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
- R11 Import Boundaries — No recognizable feature-sliced/layered src layout — boundary rules not applicable.
- 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 — 61 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- AnalyzerSeverityNone .editorconfig:83
- REDACTED
Serious — 71 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Async method without CancellationToken: DispatchEventsAsync src/CleanArchitecture.Infrastructure/Extensions/MediatorExtensions.cs:9
- Async method without CancellationToken: DispatchDomainEventsAsync src/CleanArchitecture.Infrastructure/Extensions/MediatorExtensions.cs:26
- Async method without CancellationToken: GetByIdAsync src/CleanArchitecture.Infrastructure/Repositories/Repository.cs:28
- Async method without CancellationToken: DispatchEventsAsync src/CleanArchitecture.Infrastructure/Repositories/UnitOfWork.cs:35
- Async method without CancellationToken: DispatchDomainEventsAsync src/CleanArchitecture.Infrastructure/Repositories/UnitOfWork.cs:69
- Async method without CancellationToken: HandleAsync src/CleanArchitecture.Application/Locations/Queries/GetLocationsQuery.cs:22
- Async method without CancellationToken: HandleAsync src/CleanArchitecture.Application/Weather/Commands/CreateWeatherForecastCommand.cs:25
- Async method without CancellationToken: HandleAsync src/CleanArchitecture.Application/Weather/Commands/DeleteWeatherForecastCommand.cs:20
- Async method without CancellationToken: HandleAsync src/CleanArchitecture.Application/Weather/Commands/UpdateWeatherForecastCommand.cs:20
- Async method without CancellationToken: HandleAsync src/CleanArchitecture.Application/Weather/Queries/GetWeatherForecastQuery.cs:22
- Async method without CancellationToken: HandleAsync src/CleanArchitecture.Application/Weather/Queries/GetWeatherForecastsQuery.cs:22
- Async method without CancellationToken: MigrateDatabaseAsync src/CleanArchitecture.Migrations/MigrationJob.cs:27
- Async method without CancellationToken: MigrateLocationsAsync src/CleanArchitecture.Migrations/MigrationJob.cs:35
- Async method without CancellationToken: BuildAndRunAsync src/CleanArchitecture.Hosting/HostBuilderExtensions.cs:9
- Async method without CancellationToken: Get REDACTED:22
- Async method without CancellationToken: Get REDACTED:25
- Async method without CancellationToken: Get REDACTED:33
- Async method without CancellationToken: Post REDACTED:43
- Async method without CancellationToken: Put REDACTED:53
- Async method without CancellationToken: Delete REDACTED:62
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Page without a main landmark src/CleanArchitecture.Web/ClientApp/src/index.html:2
- Accessibility enforcement below the top rung src/CleanArchitecture.Web/ClientApp/package.json:34
- Coverage not measured — .NET and JavaScript/TypeScript suite
- Anemic entity: Location src/CleanArchitecture.Core/Locations/Entities/Location.cs:7
- Repository contract exposes a live query handle: IRepository src/CleanArchitecture.Application/Abstractions/Repositories/IRepository.cs:5
- No DR/backup evidence
- Test Coverage
- No lint or typecheck script
- Dead file (~13 LoC) src/CleanArchitecture.Web/ClientApp/src/test.ts
- Dead file (~11 LoC) src/CleanArchitecture.Web/ClientApp/src/app/app.server.module.ts
- Unused dependency 'bootstrap'
- Unused dependency 'jquery'
- Unused dependency 'popper.js'
- NuGet dependencies are not locked
- Disposes a dependency it does not own src/CleanArchitecture.Infrastructure/Repositories/UnitOfWork.cs:85
Minor — 28 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- No seccomp profile REDACTED:2
- No seccomp profile REDACTED:2
- No seccomp profile REDACTED:2
- REDACTED
- REDACTED
- REDACTED
- No network policy
- Primitive id on a domain type: WeatherForecast.LocationId src/CleanArchitecture.Core/Weather/Entities/WeatherForecast.cs:41
- No ADRs
- Logging is not universal
- Unused export 'Envelope' src/CleanArchitecture.Web/ClientApp/src/app/_shared/models/results.model.ts:5
- Security headers incomplete src/CleanArchitecture.Api/Program.cs:79
- Duplicated predicate src/CleanArchitecture.Infrastructure/Extensions/MediatorExtensions.cs:13
- Not all async methods take a CancellationToken
- Interpolated log message defeats structured logging src/CleanArchitecture.Api/Infrastructure/Filters/HttpGlobalExceptionFilter.cs:21
- Null-forgiving operator (`!`) suppressions reduce the NRT score
Minor — 1 finding(s)
- Mock framework: Moq
Appendix B — Reproduction & audit trail
| Dimension | Tool | Version | Command | Findings | Raw output |
|---|---|---|---|---|---|
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-7d937e8a213046698a604e0be294a471/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-7d937e8a213046698a604e0be294a471/tree.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-tree.json |
| D29 · Static Analysis (SAST) | semgrep | — | semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/canine-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt --exclude src/CleanArchitecture.Migrations/Migrations . | 8 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | nuget | — | nuget: not applicable — nuget: the solution did not restore on the analyzer's .NET SDK (an SDK/target-framework/restore mismatch, common for an older codebase), so there was no restored dependency graph to scan | 0 | — |
| D30 · Dependency Vulnerabilities | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . --skip-db-update | 63 | artifacts/raw/trivy-fs.json |
| D31 · IaC & Container Security | trivy | — | trivy config --format json --quiet . | 37 | artifacts/raw/trivy-config.json |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. semgrep could not parse 1 file(s) — `src/CleanArchitecture.Api/Program.cs` — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real. | 0 | — |
| D36 · Supply-chain Provenance & Signing | provenance | — | provenance: not applicable — This is a dotnet-new template — it produces no released artifact to attest. Supply-chain provenance, signing and SBOM are deferred to the application you build from it (add SLSA provenance / cosign signing / an SBOM in your app's release pipeline). | 0 | — |
| D37 · Vulnerability-disclosure Policy | disclosure | — | disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — The repository ships application workloads but no cluster-governance resources (CRDs, admission webhooks, or a committed policy engine). Runtime threat-detection (Falco/Tetragon) and admission control (Kyverno/OPA-Gatekeeper/PodSecurity) are cluster-OPERATOR controls owned by the platform, not shipped by an application repo/chart — nothing for this repo to assess. | 0 | — |
| D43 · Malicious Dependencies | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . --skip-db-update | 0 | artifacts/raw/trivy-fs.json |