Executive summary
SSWConsulting/SSW.VerticalSliceArchitecture meets our standard for a template or a sample. It scores 62 out of 100 and is rated Strong, and none of its six critical findings concern security.
Performance, at 52, is the weakest lens and counts most in the score. The best first step is removing the blocking calls, worth about 7 points. Adding benchmarks comes next, worth about 5 points. Raising Performance to 58 would lift the score to about 64.
The three sets of compiler warnings switched off in projects need turning back on in the build file.
The product code is 2,339 lines, about €8,200 to rebuild.
If Performance rose from 52 to 58, the lowest score rated Strong, the score would rise from 62 to about 64.
Fixed since the last survey: 43 findings
- Code Coverage · Coverage not measured — no coverage collector is wired up
- Static Analysis (SAST) · High: dependabot-missing-cooldown .github/dependabot.yml
- Static Analysis (SAST) · High: github-actions-mutable-action-tag .github/workflows/deploy.yml
- Static Analysis (SAST) · High: github-actions-mutable-action-tag .github/workflows/deploy.yml
- Static Analysis (SAST) · High: watchdog-unpinned-package-install-in-run .github/workflows/deploy.yml
- Static Analysis (SAST) · High: github-actions-mutable-action-tag .github/workflows/deploy.yml
- Static Analysis (SAST) · High: github-actions-mutable-action-tag .github/workflows/deploy.yml
- Static Analysis (SAST) · High: github-actions-mutable-action-tag .github/workflows/dotnet.yml
- Static Analysis (SAST) · High: github-actions-mutable-action-tag .github/workflows/dotnet.yml
- Static Analysis (SAST) · High: github-actions-mutable-action-tag .github/workflows/dotnet.yml
- Static Analysis (SAST) · High: github-actions-mutable-action-tag .github/workflows/dotnet.yml
- Static Analysis (SAST) · High: github-actions-mutable-action-tag .github/workflows/meta-test.yml
- Static Analysis (SAST) · High: github-actions-mutable-action-tag .github/workflows/meta-test.yml
- Static Analysis (SAST) · High: github-actions-mutable-action-tag .github/workflows/meta-test.yml
- Static Analysis (SAST) · High: github-actions-mutable-action-tag .github/workflows/package.yml
- Static Analysis (SAST) · High: github-actions-mutable-action-tag .github/workflows/package.yml
- Static Analysis (SAST) · High: watchdog-secret-interpolated-into-run .github/workflows/package.yml
- Static Analysis (SAST) · High: github-actions-mutable-action-tag .github/workflows/package.yml
- Static Analysis (SAST) · High: watchdog-secret-interpolated-into-run .github/workflows/package.yml
- Static Analysis (SAST) · High: github-actions-mutable-action-tag .github/workflows/package.yml
- Static Analysis (SAST) · High: watchdog-secret-into-unpinned-action .github/workflows/package.yml
- Static Analysis (SAST) · Medium: watchdog-eol-node-runtime-in-workflow .github/workflows/deploy.yml
- Dependency Vulnerabilities · High CVE: System.Security.Cryptography.Pkcs 10.0.12 src/WebApi/WebApi.csproj
- Dependency Vulnerabilities · Medium CVE: MessagePack 2.5.302 Directory.Packages.props
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/WebApi/Features/Teams/GetTeam/GetTeamEndpoint.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/WebApi/Features/Teams/GetTeam/GetTeamEndpoint.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/WebApi/Features/Teams/GetTeam/GetTeamEndpoint.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/WebApi/Features/Teams/PowerLevelUpdated/PowerLevelUpdatedEventHandler.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/WebApi/Features/Teams/PowerLevelUpdated/PowerLevelUpdatedEventHandler.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) tools/AppHost/Commands/SqlServerCommandExt.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) tools/AppHost/Commands/SqlServerCommandExt.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) tools/Seeder/Initializers/ApplicationDbContextInitializer.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) tools/Seeder/Initializers/ApplicationDbContextInitializer.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) tools/Seeder/Initializers/ApplicationDbContextInitializer.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) tools/Seeder/Initializers/ApplicationDbContextInitializer.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) tools/Seeder/Initializers/ApplicationDbContextInitializer.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) tools/Seeder/Initializers/ApplicationDbContextInitializer.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) tools/Seeder/Initializers/ApplicationDbContextInitializer.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) tools/Seeder/Initializers/ApplicationDbContextInitializer.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) tools/Seeder/Initializers/ApplicationDbContextInitializer.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) tools/Seeder/Initializers/ApplicationDbContextInitializer.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) tools/Seeder/Program.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) tools/Seeder/Worker.cs
Rebuild cost: about €8,200 · Estimate
| Cost to rebuild | €2,700 to €14,000, for 45 to 143 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.8 at a score of 62. 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,339 lines of product code, of which 45% is declarations and boilerplate, 43% straight logic and 12% logic with branches |
| What it is not | Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one. |
Top priorities
Diagnosis: what the measurements show together
Architecture — module dependency graph
Architecture: which parts of the code depend on which
| uses → | 1 (global) | 2 AppHost.Commands | 3 Aspire.Hosting | 4 Microsoft.Extensions.Hosting | 5 SSW.VerticalSliceArchitecture | 6 SSW.VerticalSliceArchitecture.Common.Domain.Base.EventualConsistency | 7 SSW.VerticalSliceArchitecture.Common.Domain.Base.Interfaces | 8 SSW.VerticalSliceArchitecture.Common.FastEndpoints | 9 SSW.VerticalSliceArchitecture.Common.Features | 10 SSW.VerticalSliceArchitecture.Common.Interfaces | 11 SSW.VerticalSliceArchitecture.Common.Pagination | 12 SSW.VerticalSliceArchitecture.Host | 13 SSW.VerticalSliceArchitecture.Host.Extensions | 14 SSW.VerticalSliceArchitecture.Common.Domain.Base | 15 SSW.VerticalSliceArchitecture.Common.Persistence.Interceptors | 16 SSW.VerticalSliceArchitecture.Common.Services | 17 SSW.VerticalSliceArchitecture.Features.Heroes | 18 SSW.VerticalSliceArchitecture.Features.Teams | 19 Seeder | 20 SSW.VerticalSliceArchitecture.Common.Domain.Teams | 21 SSW.VerticalSliceArchitecture.Common.Domain.Heroes | 22 SSW.VerticalSliceArchitecture.Common.Persistence | 23 SSW.VerticalSliceArchitecture.Features.Teams.PowerLevelUpdated | 24 SSW.VerticalSliceArchitecture.Common.Middleware | 25 SSW.VerticalSliceArchitecture.Common.Persistence.Heroes | 26 SSW.VerticalSliceArchitecture.Common.Persistence.Teams | 27 SSW.VerticalSliceArchitecture.Features.Heroes.CreateHero | 28 SSW.VerticalSliceArchitecture.Features.Heroes.GetAllHeroes | 29 SSW.VerticalSliceArchitecture.Features.Heroes.UpdateHero | 30 SSW.VerticalSliceArchitecture.Features.Teams.AddHeroToTeam | 31 SSW.VerticalSliceArchitecture.Features.Teams.CompleteMission | 32 SSW.VerticalSliceArchitecture.Features.Teams.CreateTeam | 33 SSW.VerticalSliceArchitecture.Features.Teams.ExecuteMission | 34 SSW.VerticalSliceArchitecture.Features.Teams.GetAllTeams | 35 SSW.VerticalSliceArchitecture.Features.Teams.GetTeam | 36 Seeder.Initializers |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 (global) | ||||||||||||||||||||||||||||||||||||
| 2 AppHost.Commands | ||||||||||||||||||||||||||||||||||||
| 3 Aspire.Hosting | ||||||||||||||||||||||||||||||||||||
| 4 Microsoft.Extensions.Hosting | ||||||||||||||||||||||||||||||||||||
| 5 SSW.VerticalSliceArchitecture | ||||||||||||||||||||||||||||||||||||
| 6 SSW.VerticalSliceArchitecture.Common.Domain.Base.EventualConsistency | ||||||||||||||||||||||||||||||||||||
| 7 SSW.VerticalSliceArchitecture.Common.Domain.Base.Interfaces | ||||||||||||||||||||||||||||||||||||
| 8 SSW.VerticalSliceArchitecture.Common.FastEndpoints | ||||||||||||||||||||||||||||||||||||
| 9 SSW.VerticalSliceArchitecture.Common.Features | ||||||||||||||||||||||||||||||||||||
| 10 SSW.VerticalSliceArchitecture.Common.Interfaces | ||||||||||||||||||||||||||||||||||||
| 11 SSW.VerticalSliceArchitecture.Common.Pagination | ||||||||||||||||||||||||||||||||||||
| 12 SSW.VerticalSliceArchitecture.Host | ||||||||||||||||||||||||||||||||||||
| 13 SSW.VerticalSliceArchitecture.Host.Extensions | ||||||||||||||||||||||||||||||||||||
| 14 SSW.VerticalSliceArchitecture.Common.Domain.Base | 2 | |||||||||||||||||||||||||||||||||||
| 15 SSW.VerticalSliceArchitecture.Common.Persistence.Interceptors | 1 | |||||||||||||||||||||||||||||||||||
| 16 SSW.VerticalSliceArchitecture.Common.Services | 1 | |||||||||||||||||||||||||||||||||||
| 17 SSW.VerticalSliceArchitecture.Features.Heroes | 1 | |||||||||||||||||||||||||||||||||||
| 18 SSW.VerticalSliceArchitecture.Features.Teams | 1 | |||||||||||||||||||||||||||||||||||
| 19 Seeder | 1 | |||||||||||||||||||||||||||||||||||
| 20 SSW.VerticalSliceArchitecture.Common.Domain.Teams | 3 | 2 | 1 | |||||||||||||||||||||||||||||||||
| 21 SSW.VerticalSliceArchitecture.Common.Domain.Heroes | 1 | 3 | 1 | 1 | ||||||||||||||||||||||||||||||||
| 22 SSW.VerticalSliceArchitecture.Common.Persistence | 1 | 1 | ||||||||||||||||||||||||||||||||||
| 23 SSW.VerticalSliceArchitecture.Features.Teams.PowerLevelUpdated | 1 | |||||||||||||||||||||||||||||||||||
| 24 SSW.VerticalSliceArchitecture.Common.Middleware | 1 | |||||||||||||||||||||||||||||||||||
| 25 SSW.VerticalSliceArchitecture.Common.Persistence.Heroes | 1 | 1 | ||||||||||||||||||||||||||||||||||
| 26 SSW.VerticalSliceArchitecture.Common.Persistence.Teams | 2 | 2 | ||||||||||||||||||||||||||||||||||
| 27 SSW.VerticalSliceArchitecture.Features.Heroes.CreateHero | 1 | |||||||||||||||||||||||||||||||||||
| 28 SSW.VerticalSliceArchitecture.Features.Heroes.GetAllHeroes | 2 | 1 | ||||||||||||||||||||||||||||||||||
| 29 SSW.VerticalSliceArchitecture.Features.Heroes.UpdateHero | 1 | |||||||||||||||||||||||||||||||||||
| 30 SSW.VerticalSliceArchitecture.Features.Teams.AddHeroToTeam | 1 | |||||||||||||||||||||||||||||||||||
| 31 SSW.VerticalSliceArchitecture.Features.Teams.CompleteMission | 1 | |||||||||||||||||||||||||||||||||||
| 32 SSW.VerticalSliceArchitecture.Features.Teams.CreateTeam | 1 | |||||||||||||||||||||||||||||||||||
| 33 SSW.VerticalSliceArchitecture.Features.Teams.ExecuteMission | 1 | |||||||||||||||||||||||||||||||||||
| 34 SSW.VerticalSliceArchitecture.Features.Teams.GetAllTeams | 2 | 1 | ||||||||||||||||||||||||||||||||||
| 35 SSW.VerticalSliceArchitecture.Features.Teams.GetTeam | 1 | |||||||||||||||||||||||||||||||||||
| 36 Seeder.Initializers | 1 | 1 |
14→7 SSW.VerticalSliceArchitecture.Common.Domain.Base uses SSW.VerticalSliceArchitecture.Common.Domain.Base.Interfaces✕
- Connections
- 2 pairs of types, where a type in SSW.VerticalSliceArchitecture.Common.Domain.Base uses a type in SSW.VerticalSliceArchitecture.Common.Domain.Base.Interfaces.
- The types involved
SSW.VerticalSliceArchitecture.Common.Domain.Base.AggregateRoot→SSW.VerticalSliceArchitecture.Common.Domain.Base.Interfaces.IAggregateRootSSW.VerticalSliceArchitecture.Common.Domain.Base.Auditable→SSW.VerticalSliceArchitecture.Common.Domain.Base.Interfaces.IAuditable
- Direction
- SSW.VerticalSliceArchitecture.Common.Domain.Base uses SSW.VerticalSliceArchitecture.Common.Domain.Base.Interfaces, so a change to SSW.VerticalSliceArchitecture.Common.Domain.Base.Interfaces can break SSW.VerticalSliceArchitecture.Common.Domain.Base, while a change to SSW.VerticalSliceArchitecture.Common.Domain.Base can't break SSW.VerticalSliceArchitecture.Common.Domain.Base.Interfaces.
- Position
- Below the diagonal: SSW.VerticalSliceArchitecture.Common.Domain.Base uses a module listed above it, which is the healthy direction.
15→10 SSW.VerticalSliceArchitecture.Common.Persistence.Interceptors uses SSW.VerticalSliceArchitecture.Common.Interfaces✕
- Connections
- 1 pair of types, where a type in SSW.VerticalSliceArchitecture.Common.Persistence.Interceptors uses a type in SSW.VerticalSliceArchitecture.Common.Interfaces.
- The types involved
SSW.VerticalSliceArchitecture.Common.Persistence.Interceptors.EntitySaveChangesInterceptor→SSW.VerticalSliceArchitecture.Common.Interfaces.ICurrentUserService
- Direction
- SSW.VerticalSliceArchitecture.Common.Persistence.Interceptors uses SSW.VerticalSliceArchitecture.Common.Interfaces, so a change to SSW.VerticalSliceArchitecture.Common.Interfaces can break SSW.VerticalSliceArchitecture.Common.Persistence.Interceptors, while a change to SSW.VerticalSliceArchitecture.Common.Persistence.Interceptors can't break SSW.VerticalSliceArchitecture.Common.Interfaces.
- Position
- Below the diagonal: SSW.VerticalSliceArchitecture.Common.Persistence.Interceptors uses a module listed above it, which is the healthy direction.
16→10 SSW.VerticalSliceArchitecture.Common.Services uses SSW.VerticalSliceArchitecture.Common.Interfaces✕
- Connections
- 1 pair of types, where a type in SSW.VerticalSliceArchitecture.Common.Services uses a type in SSW.VerticalSliceArchitecture.Common.Interfaces.
- The types involved
SSW.VerticalSliceArchitecture.Common.Services.CurrentUserService→SSW.VerticalSliceArchitecture.Common.Interfaces.ICurrentUserService
- Direction
- SSW.VerticalSliceArchitecture.Common.Services uses SSW.VerticalSliceArchitecture.Common.Interfaces, so a change to SSW.VerticalSliceArchitecture.Common.Interfaces can break SSW.VerticalSliceArchitecture.Common.Services, while a change to SSW.VerticalSliceArchitecture.Common.Services can't break SSW.VerticalSliceArchitecture.Common.Interfaces.
- Position
- Below the diagonal: SSW.VerticalSliceArchitecture.Common.Services uses a module listed above it, which is the healthy direction.
17→10 SSW.VerticalSliceArchitecture.Features.Heroes uses SSW.VerticalSliceArchitecture.Common.Interfaces✕
- Connections
- 1 pair of types, where a type in SSW.VerticalSliceArchitecture.Features.Heroes uses a type in SSW.VerticalSliceArchitecture.Common.Interfaces.
- The types involved
SSW.VerticalSliceArchitecture.Features.Heroes.HeroesFeature→SSW.VerticalSliceArchitecture.Common.Interfaces.IFeature
- Direction
- SSW.VerticalSliceArchitecture.Features.Heroes uses SSW.VerticalSliceArchitecture.Common.Interfaces, so a change to SSW.VerticalSliceArchitecture.Common.Interfaces can break SSW.VerticalSliceArchitecture.Features.Heroes, while a change to SSW.VerticalSliceArchitecture.Features.Heroes can't break SSW.VerticalSliceArchitecture.Common.Interfaces.
- Position
- Below the diagonal: SSW.VerticalSliceArchitecture.Features.Heroes uses a module listed above it, which is the healthy direction.
18→10 SSW.VerticalSliceArchitecture.Features.Teams uses SSW.VerticalSliceArchitecture.Common.Interfaces✕
- Connections
- 1 pair of types, where a type in SSW.VerticalSliceArchitecture.Features.Teams uses a type in SSW.VerticalSliceArchitecture.Common.Interfaces.
- The types involved
SSW.VerticalSliceArchitecture.Features.Teams.TeamsFeature→SSW.VerticalSliceArchitecture.Common.Interfaces.IFeature
- Direction
- SSW.VerticalSliceArchitecture.Features.Teams uses SSW.VerticalSliceArchitecture.Common.Interfaces, so a change to SSW.VerticalSliceArchitecture.Common.Interfaces can break SSW.VerticalSliceArchitecture.Features.Teams, while a change to SSW.VerticalSliceArchitecture.Features.Teams can't break SSW.VerticalSliceArchitecture.Common.Interfaces.
- Position
- Below the diagonal: SSW.VerticalSliceArchitecture.Features.Teams uses a module listed above it, which is the healthy direction.
19→10 Seeder uses SSW.VerticalSliceArchitecture.Common.Interfaces✕
- Connections
- 1 pair of types, where a type in Seeder uses a type in SSW.VerticalSliceArchitecture.Common.Interfaces.
- The types involved
Seeder.SeederUserService→SSW.VerticalSliceArchitecture.Common.Interfaces.ICurrentUserService
- Direction
- Seeder uses SSW.VerticalSliceArchitecture.Common.Interfaces, so a change to SSW.VerticalSliceArchitecture.Common.Interfaces can break Seeder, while a change to Seeder can't break SSW.VerticalSliceArchitecture.Common.Interfaces.
- Position
- Below the diagonal: Seeder uses a module listed above it, which is the healthy direction.
20→11 SSW.VerticalSliceArchitecture.Common.Domain.Teams uses SSW.VerticalSliceArchitecture.Common.Pagination✕
- Connections
- 3 pairs of types, where a type in SSW.VerticalSliceArchitecture.Common.Domain.Teams uses a type in SSW.VerticalSliceArchitecture.Common.Pagination.
- The types involved
SSW.VerticalSliceArchitecture.Common.Domain.Teams.TeamSpec→SSW.VerticalSliceArchitecture.Common.Pagination.PagingParamsSSW.VerticalSliceArchitecture.Common.Domain.Teams.TeamSpec→SSW.VerticalSliceArchitecture.Common.Pagination.SortColumnMapSSW.VerticalSliceArchitecture.Common.Domain.Teams.TeamSpec→SSW.VerticalSliceArchitecture.Common.Pagination.SortDirection
- Direction
- SSW.VerticalSliceArchitecture.Common.Domain.Teams uses SSW.VerticalSliceArchitecture.Common.Pagination, so a change to SSW.VerticalSliceArchitecture.Common.Pagination can break SSW.VerticalSliceArchitecture.Common.Domain.Teams, while a change to SSW.VerticalSliceArchitecture.Common.Domain.Teams can't break SSW.VerticalSliceArchitecture.Common.Pagination.
- Position
- Below the diagonal: SSW.VerticalSliceArchitecture.Common.Domain.Teams uses a module listed above it, which is the healthy direction.
20→14 SSW.VerticalSliceArchitecture.Common.Domain.Teams uses SSW.VerticalSliceArchitecture.Common.Domain.Base✕
- Connections
- 2 pairs of types, where a type in SSW.VerticalSliceArchitecture.Common.Domain.Teams uses a type in SSW.VerticalSliceArchitecture.Common.Domain.Base.
- The types involved
SSW.VerticalSliceArchitecture.Common.Domain.Teams.Mission→SSW.VerticalSliceArchitecture.Common.Domain.Base.EntitySSW.VerticalSliceArchitecture.Common.Domain.Teams.Team→SSW.VerticalSliceArchitecture.Common.Domain.Base.AggregateRoot
- Direction
- SSW.VerticalSliceArchitecture.Common.Domain.Teams uses SSW.VerticalSliceArchitecture.Common.Domain.Base, so a change to SSW.VerticalSliceArchitecture.Common.Domain.Base can break SSW.VerticalSliceArchitecture.Common.Domain.Teams, while a change to SSW.VerticalSliceArchitecture.Common.Domain.Teams can't break SSW.VerticalSliceArchitecture.Common.Domain.Base.
- Position
- Below the diagonal: SSW.VerticalSliceArchitecture.Common.Domain.Teams uses a module listed above it, which is the healthy direction.
20→21 SSW.VerticalSliceArchitecture.Common.Domain.Teams uses SSW.VerticalSliceArchitecture.Common.Domain.Heroes part of a loop✕
- Connections
- 1 pair of types, where a type in SSW.VerticalSliceArchitecture.Common.Domain.Teams uses a type in SSW.VerticalSliceArchitecture.Common.Domain.Heroes.
- The types involved
SSW.VerticalSliceArchitecture.Common.Domain.Teams.Team→SSW.VerticalSliceArchitecture.Common.Domain.Heroes.Hero
- Direction
- SSW.VerticalSliceArchitecture.Common.Domain.Teams uses SSW.VerticalSliceArchitecture.Common.Domain.Heroes, so a change to SSW.VerticalSliceArchitecture.Common.Domain.Heroes can break SSW.VerticalSliceArchitecture.Common.Domain.Teams, while a change to SSW.VerticalSliceArchitecture.Common.Domain.Teams can't break SSW.VerticalSliceArchitecture.Common.Domain.Heroes.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
21→7 SSW.VerticalSliceArchitecture.Common.Domain.Heroes uses SSW.VerticalSliceArchitecture.Common.Domain.Base.Interfaces✕
- Connections
- 1 pair of types, where a type in SSW.VerticalSliceArchitecture.Common.Domain.Heroes uses a type in SSW.VerticalSliceArchitecture.Common.Domain.Base.Interfaces.
- The types involved
SSW.VerticalSliceArchitecture.Common.Domain.Heroes.Power→SSW.VerticalSliceArchitecture.Common.Domain.Base.Interfaces.IValueObject
- Direction
- SSW.VerticalSliceArchitecture.Common.Domain.Heroes uses SSW.VerticalSliceArchitecture.Common.Domain.Base.Interfaces, so a change to SSW.VerticalSliceArchitecture.Common.Domain.Base.Interfaces can break SSW.VerticalSliceArchitecture.Common.Domain.Heroes, while a change to SSW.VerticalSliceArchitecture.Common.Domain.Heroes can't break SSW.VerticalSliceArchitecture.Common.Domain.Base.Interfaces.
- Position
- Below the diagonal: SSW.VerticalSliceArchitecture.Common.Domain.Heroes uses a module listed above it, which is the healthy direction.
21→11 SSW.VerticalSliceArchitecture.Common.Domain.Heroes uses SSW.VerticalSliceArchitecture.Common.Pagination✕
- Connections
- 3 pairs of types, where a type in SSW.VerticalSliceArchitecture.Common.Domain.Heroes uses a type in SSW.VerticalSliceArchitecture.Common.Pagination.
- The types involved
SSW.VerticalSliceArchitecture.Common.Domain.Heroes.HeroSpec→SSW.VerticalSliceArchitecture.Common.Pagination.PagingParamsSSW.VerticalSliceArchitecture.Common.Domain.Heroes.HeroSpec→SSW.VerticalSliceArchitecture.Common.Pagination.SortColumnMapSSW.VerticalSliceArchitecture.Common.Domain.Heroes.HeroSpec→SSW.VerticalSliceArchitecture.Common.Pagination.SortDirection
- Direction
- SSW.VerticalSliceArchitecture.Common.Domain.Heroes uses SSW.VerticalSliceArchitecture.Common.Pagination, so a change to SSW.VerticalSliceArchitecture.Common.Pagination can break SSW.VerticalSliceArchitecture.Common.Domain.Heroes, while a change to SSW.VerticalSliceArchitecture.Common.Domain.Heroes can't break SSW.VerticalSliceArchitecture.Common.Pagination.
- Position
- Below the diagonal: SSW.VerticalSliceArchitecture.Common.Domain.Heroes uses a module listed above it, which is the healthy direction.
21→14 SSW.VerticalSliceArchitecture.Common.Domain.Heroes uses SSW.VerticalSliceArchitecture.Common.Domain.Base✕
- Connections
- 1 pair of types, where a type in SSW.VerticalSliceArchitecture.Common.Domain.Heroes uses a type in SSW.VerticalSliceArchitecture.Common.Domain.Base.
- The types involved
SSW.VerticalSliceArchitecture.Common.Domain.Heroes.Hero→SSW.VerticalSliceArchitecture.Common.Domain.Base.AggregateRoot
- Direction
- SSW.VerticalSliceArchitecture.Common.Domain.Heroes uses SSW.VerticalSliceArchitecture.Common.Domain.Base, so a change to SSW.VerticalSliceArchitecture.Common.Domain.Base can break SSW.VerticalSliceArchitecture.Common.Domain.Heroes, while a change to SSW.VerticalSliceArchitecture.Common.Domain.Heroes can't break SSW.VerticalSliceArchitecture.Common.Domain.Base.
- Position
- Below the diagonal: SSW.VerticalSliceArchitecture.Common.Domain.Heroes uses a module listed above it, which is the healthy direction.
21→20 SSW.VerticalSliceArchitecture.Common.Domain.Heroes uses SSW.VerticalSliceArchitecture.Common.Domain.Teams✕
- Connections
- 1 pair of types, where a type in SSW.VerticalSliceArchitecture.Common.Domain.Heroes uses a type in SSW.VerticalSliceArchitecture.Common.Domain.Teams.
- The types involved
SSW.VerticalSliceArchitecture.Common.Domain.Heroes.Hero→SSW.VerticalSliceArchitecture.Common.Domain.Teams.TeamId
- Direction
- SSW.VerticalSliceArchitecture.Common.Domain.Heroes uses SSW.VerticalSliceArchitecture.Common.Domain.Teams, so a change to SSW.VerticalSliceArchitecture.Common.Domain.Teams can break SSW.VerticalSliceArchitecture.Common.Domain.Heroes, while a change to SSW.VerticalSliceArchitecture.Common.Domain.Heroes can't break SSW.VerticalSliceArchitecture.Common.Domain.Teams.
- Position
- Below the diagonal: SSW.VerticalSliceArchitecture.Common.Domain.Heroes uses a module listed above it, which is the healthy direction.
22→20 SSW.VerticalSliceArchitecture.Common.Persistence uses SSW.VerticalSliceArchitecture.Common.Domain.Teams✕
- Connections
- 1 pair of types, where a type in SSW.VerticalSliceArchitecture.Common.Persistence uses a type in SSW.VerticalSliceArchitecture.Common.Domain.Teams.
- The types involved
SSW.VerticalSliceArchitecture.Common.Persistence.ApplicationDbContext→SSW.VerticalSliceArchitecture.Common.Domain.Teams.Team
- Direction
- SSW.VerticalSliceArchitecture.Common.Persistence uses SSW.VerticalSliceArchitecture.Common.Domain.Teams, so a change to SSW.VerticalSliceArchitecture.Common.Domain.Teams can break SSW.VerticalSliceArchitecture.Common.Persistence, while a change to SSW.VerticalSliceArchitecture.Common.Persistence can't break SSW.VerticalSliceArchitecture.Common.Domain.Teams.
- Position
- Below the diagonal: SSW.VerticalSliceArchitecture.Common.Persistence uses a module listed above it, which is the healthy direction.
22→21 SSW.VerticalSliceArchitecture.Common.Persistence uses SSW.VerticalSliceArchitecture.Common.Domain.Heroes✕
- Connections
- 1 pair of types, where a type in SSW.VerticalSliceArchitecture.Common.Persistence uses a type in SSW.VerticalSliceArchitecture.Common.Domain.Heroes.
- The types involved
SSW.VerticalSliceArchitecture.Common.Persistence.ApplicationDbContext→SSW.VerticalSliceArchitecture.Common.Domain.Heroes.Hero
- Direction
- SSW.VerticalSliceArchitecture.Common.Persistence uses SSW.VerticalSliceArchitecture.Common.Domain.Heroes, so a change to SSW.VerticalSliceArchitecture.Common.Domain.Heroes can break SSW.VerticalSliceArchitecture.Common.Persistence, while a change to SSW.VerticalSliceArchitecture.Common.Persistence can't break SSW.VerticalSliceArchitecture.Common.Domain.Heroes.
- Position
- Below the diagonal: SSW.VerticalSliceArchitecture.Common.Persistence uses a module listed above it, which is the healthy direction.
23→21 SSW.VerticalSliceArchitecture.Features.Teams.PowerLevelUpdated uses SSW.VerticalSliceArchitecture.Common.Domain.Heroes✕
- Connections
- 1 pair of types, where a type in SSW.VerticalSliceArchitecture.Features.Teams.PowerLevelUpdated uses a type in SSW.VerticalSliceArchitecture.Common.Domain.Heroes.
- The types involved
SSW.VerticalSliceArchitecture.Features.Teams.PowerLevelUpdated.PowerLevelUpdatedEventHandler→SSW.VerticalSliceArchitecture.Common.Domain.Heroes.PowerLevelUpdatedEvent
- Direction
- SSW.VerticalSliceArchitecture.Features.Teams.PowerLevelUpdated uses SSW.VerticalSliceArchitecture.Common.Domain.Heroes, so a change to SSW.VerticalSliceArchitecture.Common.Domain.Heroes can break SSW.VerticalSliceArchitecture.Features.Teams.PowerLevelUpdated, while a change to SSW.VerticalSliceArchitecture.Features.Teams.PowerLevelUpdated can't break SSW.VerticalSliceArchitecture.Common.Domain.Heroes.
- Position
- Below the diagonal: SSW.VerticalSliceArchitecture.Features.Teams.PowerLevelUpdated uses a module listed above it, which is the healthy direction.
24→22 SSW.VerticalSliceArchitecture.Common.Middleware uses SSW.VerticalSliceArchitecture.Common.Persistence✕
- Connections
- 1 pair of types, where a type in SSW.VerticalSliceArchitecture.Common.Middleware uses a type in SSW.VerticalSliceArchitecture.Common.Persistence.
- The types involved
SSW.VerticalSliceArchitecture.Common.Middleware.EventualConsistencyMiddleware→SSW.VerticalSliceArchitecture.Common.Persistence.ApplicationDbContext
- Direction
- SSW.VerticalSliceArchitecture.Common.Middleware uses SSW.VerticalSliceArchitecture.Common.Persistence, so a change to SSW.VerticalSliceArchitecture.Common.Persistence can break SSW.VerticalSliceArchitecture.Common.Middleware, while a change to SSW.VerticalSliceArchitecture.Common.Middleware can't break SSW.VerticalSliceArchitecture.Common.Persistence.
- Position
- Below the diagonal: SSW.VerticalSliceArchitecture.Common.Middleware uses a module listed above it, which is the healthy direction.
25→21 SSW.VerticalSliceArchitecture.Common.Persistence.Heroes uses SSW.VerticalSliceArchitecture.Common.Domain.Heroes✕
- Connections
- 1 pair of types, where a type in SSW.VerticalSliceArchitecture.Common.Persistence.Heroes uses a type in SSW.VerticalSliceArchitecture.Common.Domain.Heroes.
- The types involved
SSW.VerticalSliceArchitecture.Common.Persistence.Heroes.HeroConfiguration→SSW.VerticalSliceArchitecture.Common.Domain.Heroes.Hero
- Direction
- SSW.VerticalSliceArchitecture.Common.Persistence.Heroes uses SSW.VerticalSliceArchitecture.Common.Domain.Heroes, so a change to SSW.VerticalSliceArchitecture.Common.Domain.Heroes can break SSW.VerticalSliceArchitecture.Common.Persistence.Heroes, while a change to SSW.VerticalSliceArchitecture.Common.Persistence.Heroes can't break SSW.VerticalSliceArchitecture.Common.Domain.Heroes.
- Position
- Below the diagonal: SSW.VerticalSliceArchitecture.Common.Persistence.Heroes uses a module listed above it, which is the healthy direction.
25→22 SSW.VerticalSliceArchitecture.Common.Persistence.Heroes uses SSW.VerticalSliceArchitecture.Common.Persistence✕
- Connections
- 1 pair of types, where a type in SSW.VerticalSliceArchitecture.Common.Persistence.Heroes uses a type in SSW.VerticalSliceArchitecture.Common.Persistence.
- The types involved
SSW.VerticalSliceArchitecture.Common.Persistence.Heroes.HeroConfiguration→SSW.VerticalSliceArchitecture.Common.Persistence.AuditableConfiguration
- Direction
- SSW.VerticalSliceArchitecture.Common.Persistence.Heroes uses SSW.VerticalSliceArchitecture.Common.Persistence, so a change to SSW.VerticalSliceArchitecture.Common.Persistence can break SSW.VerticalSliceArchitecture.Common.Persistence.Heroes, while a change to SSW.VerticalSliceArchitecture.Common.Persistence.Heroes can't break SSW.VerticalSliceArchitecture.Common.Persistence.
- Position
- Below the diagonal: SSW.VerticalSliceArchitecture.Common.Persistence.Heroes uses a module listed above it, which is the healthy direction.
26→20 SSW.VerticalSliceArchitecture.Common.Persistence.Teams uses SSW.VerticalSliceArchitecture.Common.Domain.Teams✕
- Connections
- 2 pairs of types, where a type in SSW.VerticalSliceArchitecture.Common.Persistence.Teams uses a type in SSW.VerticalSliceArchitecture.Common.Domain.Teams.
- The types involved
SSW.VerticalSliceArchitecture.Common.Persistence.Teams.MissionConfiguration→SSW.VerticalSliceArchitecture.Common.Domain.Teams.MissionSSW.VerticalSliceArchitecture.Common.Persistence.Teams.TeamConfiguration→SSW.VerticalSliceArchitecture.Common.Domain.Teams.Team
- Direction
- SSW.VerticalSliceArchitecture.Common.Persistence.Teams uses SSW.VerticalSliceArchitecture.Common.Domain.Teams, so a change to SSW.VerticalSliceArchitecture.Common.Domain.Teams can break SSW.VerticalSliceArchitecture.Common.Persistence.Teams, while a change to SSW.VerticalSliceArchitecture.Common.Persistence.Teams can't break SSW.VerticalSliceArchitecture.Common.Domain.Teams.
- Position
- Below the diagonal: SSW.VerticalSliceArchitecture.Common.Persistence.Teams uses a module listed above it, which is the healthy direction.
26→22 SSW.VerticalSliceArchitecture.Common.Persistence.Teams uses SSW.VerticalSliceArchitecture.Common.Persistence✕
- Connections
- 2 pairs of types, where a type in SSW.VerticalSliceArchitecture.Common.Persistence.Teams uses a type in SSW.VerticalSliceArchitecture.Common.Persistence.
- The types involved
SSW.VerticalSliceArchitecture.Common.Persistence.Teams.MissionConfiguration→SSW.VerticalSliceArchitecture.Common.Persistence.AuditableConfigurationSSW.VerticalSliceArchitecture.Common.Persistence.Teams.TeamConfiguration→SSW.VerticalSliceArchitecture.Common.Persistence.AuditableConfiguration
- Direction
- SSW.VerticalSliceArchitecture.Common.Persistence.Teams uses SSW.VerticalSliceArchitecture.Common.Persistence, so a change to SSW.VerticalSliceArchitecture.Common.Persistence can break SSW.VerticalSliceArchitecture.Common.Persistence.Teams, while a change to SSW.VerticalSliceArchitecture.Common.Persistence.Teams can't break SSW.VerticalSliceArchitecture.Common.Persistence.
- Position
- Below the diagonal: SSW.VerticalSliceArchitecture.Common.Persistence.Teams uses a module listed above it, which is the healthy direction.
27→22 SSW.VerticalSliceArchitecture.Features.Heroes.CreateHero uses SSW.VerticalSliceArchitecture.Common.Persistence✕
- Connections
- 1 pair of types, where a type in SSW.VerticalSliceArchitecture.Features.Heroes.CreateHero uses a type in SSW.VerticalSliceArchitecture.Common.Persistence.
- The types involved
SSW.VerticalSliceArchitecture.Features.Heroes.CreateHero.CreateHeroEndpoint→SSW.VerticalSliceArchitecture.Common.Persistence.ApplicationDbContext
- Direction
- SSW.VerticalSliceArchitecture.Features.Heroes.CreateHero uses SSW.VerticalSliceArchitecture.Common.Persistence, so a change to SSW.VerticalSliceArchitecture.Common.Persistence can break SSW.VerticalSliceArchitecture.Features.Heroes.CreateHero, while a change to SSW.VerticalSliceArchitecture.Features.Heroes.CreateHero can't break SSW.VerticalSliceArchitecture.Common.Persistence.
- Position
- Below the diagonal: SSW.VerticalSliceArchitecture.Features.Heroes.CreateHero uses a module listed above it, which is the healthy direction.
28→11 SSW.VerticalSliceArchitecture.Features.Heroes.GetAllHeroes uses SSW.VerticalSliceArchitecture.Common.Pagination✕
- Connections
- 2 pairs of types, where a type in SSW.VerticalSliceArchitecture.Features.Heroes.GetAllHeroes uses a type in SSW.VerticalSliceArchitecture.Common.Pagination.
- The types involved
SSW.VerticalSliceArchitecture.Features.Heroes.GetAllHeroes.GetAllHeroesRequest→SSW.VerticalSliceArchitecture.Common.Pagination.PagedRequestSSW.VerticalSliceArchitecture.Features.Heroes.GetAllHeroes.GetAllHeroesRequestValidator→SSW.VerticalSliceArchitecture.Common.Pagination.PagedRequestValidator
- Direction
- SSW.VerticalSliceArchitecture.Features.Heroes.GetAllHeroes uses SSW.VerticalSliceArchitecture.Common.Pagination, so a change to SSW.VerticalSliceArchitecture.Common.Pagination can break SSW.VerticalSliceArchitecture.Features.Heroes.GetAllHeroes, while a change to SSW.VerticalSliceArchitecture.Features.Heroes.GetAllHeroes can't break SSW.VerticalSliceArchitecture.Common.Pagination.
- Position
- Below the diagonal: SSW.VerticalSliceArchitecture.Features.Heroes.GetAllHeroes uses a module listed above it, which is the healthy direction.
28→22 SSW.VerticalSliceArchitecture.Features.Heroes.GetAllHeroes uses SSW.VerticalSliceArchitecture.Common.Persistence✕
- Connections
- 1 pair of types, where a type in SSW.VerticalSliceArchitecture.Features.Heroes.GetAllHeroes uses a type in SSW.VerticalSliceArchitecture.Common.Persistence.
- The types involved
SSW.VerticalSliceArchitecture.Features.Heroes.GetAllHeroes.GetAllHeroesEndpoint→SSW.VerticalSliceArchitecture.Common.Persistence.ApplicationDbContext
- Direction
- SSW.VerticalSliceArchitecture.Features.Heroes.GetAllHeroes uses SSW.VerticalSliceArchitecture.Common.Persistence, so a change to SSW.VerticalSliceArchitecture.Common.Persistence can break SSW.VerticalSliceArchitecture.Features.Heroes.GetAllHeroes, while a change to SSW.VerticalSliceArchitecture.Features.Heroes.GetAllHeroes can't break SSW.VerticalSliceArchitecture.Common.Persistence.
- Position
- Below the diagonal: SSW.VerticalSliceArchitecture.Features.Heroes.GetAllHeroes uses a module listed above it, which is the healthy direction.
29→22 SSW.VerticalSliceArchitecture.Features.Heroes.UpdateHero uses SSW.VerticalSliceArchitecture.Common.Persistence✕
- Connections
- 1 pair of types, where a type in SSW.VerticalSliceArchitecture.Features.Heroes.UpdateHero uses a type in SSW.VerticalSliceArchitecture.Common.Persistence.
- The types involved
SSW.VerticalSliceArchitecture.Features.Heroes.UpdateHero.UpdateHeroEndpoint→SSW.VerticalSliceArchitecture.Common.Persistence.ApplicationDbContext
- Direction
- SSW.VerticalSliceArchitecture.Features.Heroes.UpdateHero uses SSW.VerticalSliceArchitecture.Common.Persistence, so a change to SSW.VerticalSliceArchitecture.Common.Persistence can break SSW.VerticalSliceArchitecture.Features.Heroes.UpdateHero, while a change to SSW.VerticalSliceArchitecture.Features.Heroes.UpdateHero can't break SSW.VerticalSliceArchitecture.Common.Persistence.
- Position
- Below the diagonal: SSW.VerticalSliceArchitecture.Features.Heroes.UpdateHero uses a module listed above it, which is the healthy direction.
30→22 SSW.VerticalSliceArchitecture.Features.Teams.AddHeroToTeam uses SSW.VerticalSliceArchitecture.Common.Persistence✕
- Connections
- 1 pair of types, where a type in SSW.VerticalSliceArchitecture.Features.Teams.AddHeroToTeam uses a type in SSW.VerticalSliceArchitecture.Common.Persistence.
- The types involved
SSW.VerticalSliceArchitecture.Features.Teams.AddHeroToTeam.AddHeroToTeamEndpoint→SSW.VerticalSliceArchitecture.Common.Persistence.ApplicationDbContext
- Direction
- SSW.VerticalSliceArchitecture.Features.Teams.AddHeroToTeam uses SSW.VerticalSliceArchitecture.Common.Persistence, so a change to SSW.VerticalSliceArchitecture.Common.Persistence can break SSW.VerticalSliceArchitecture.Features.Teams.AddHeroToTeam, while a change to SSW.VerticalSliceArchitecture.Features.Teams.AddHeroToTeam can't break SSW.VerticalSliceArchitecture.Common.Persistence.
- Position
- Below the diagonal: SSW.VerticalSliceArchitecture.Features.Teams.AddHeroToTeam uses a module listed above it, which is the healthy direction.
31→22 SSW.VerticalSliceArchitecture.Features.Teams.CompleteMission uses SSW.VerticalSliceArchitecture.Common.Persistence✕
- Connections
- 1 pair of types, where a type in SSW.VerticalSliceArchitecture.Features.Teams.CompleteMission uses a type in SSW.VerticalSliceArchitecture.Common.Persistence.
- The types involved
SSW.VerticalSliceArchitecture.Features.Teams.CompleteMission.CompleteMissionEndpoint→SSW.VerticalSliceArchitecture.Common.Persistence.ApplicationDbContext
- Direction
- SSW.VerticalSliceArchitecture.Features.Teams.CompleteMission uses SSW.VerticalSliceArchitecture.Common.Persistence, so a change to SSW.VerticalSliceArchitecture.Common.Persistence can break SSW.VerticalSliceArchitecture.Features.Teams.CompleteMission, while a change to SSW.VerticalSliceArchitecture.Features.Teams.CompleteMission can't break SSW.VerticalSliceArchitecture.Common.Persistence.
- Position
- Below the diagonal: SSW.VerticalSliceArchitecture.Features.Teams.CompleteMission uses a module listed above it, which is the healthy direction.
32→22 SSW.VerticalSliceArchitecture.Features.Teams.CreateTeam uses SSW.VerticalSliceArchitecture.Common.Persistence✕
- Connections
- 1 pair of types, where a type in SSW.VerticalSliceArchitecture.Features.Teams.CreateTeam uses a type in SSW.VerticalSliceArchitecture.Common.Persistence.
- The types involved
SSW.VerticalSliceArchitecture.Features.Teams.CreateTeam.CreateTeamEndpoint→SSW.VerticalSliceArchitecture.Common.Persistence.ApplicationDbContext
- Direction
- SSW.VerticalSliceArchitecture.Features.Teams.CreateTeam uses SSW.VerticalSliceArchitecture.Common.Persistence, so a change to SSW.VerticalSliceArchitecture.Common.Persistence can break SSW.VerticalSliceArchitecture.Features.Teams.CreateTeam, while a change to SSW.VerticalSliceArchitecture.Features.Teams.CreateTeam can't break SSW.VerticalSliceArchitecture.Common.Persistence.
- Position
- Below the diagonal: SSW.VerticalSliceArchitecture.Features.Teams.CreateTeam uses a module listed above it, which is the healthy direction.
33→22 SSW.VerticalSliceArchitecture.Features.Teams.ExecuteMission uses SSW.VerticalSliceArchitecture.Common.Persistence✕
- Connections
- 1 pair of types, where a type in SSW.VerticalSliceArchitecture.Features.Teams.ExecuteMission uses a type in SSW.VerticalSliceArchitecture.Common.Persistence.
- The types involved
SSW.VerticalSliceArchitecture.Features.Teams.ExecuteMission.ExecuteMissionEndpoint→SSW.VerticalSliceArchitecture.Common.Persistence.ApplicationDbContext
- Direction
- SSW.VerticalSliceArchitecture.Features.Teams.ExecuteMission uses SSW.VerticalSliceArchitecture.Common.Persistence, so a change to SSW.VerticalSliceArchitecture.Common.Persistence can break SSW.VerticalSliceArchitecture.Features.Teams.ExecuteMission, while a change to SSW.VerticalSliceArchitecture.Features.Teams.ExecuteMission can't break SSW.VerticalSliceArchitecture.Common.Persistence.
- Position
- Below the diagonal: SSW.VerticalSliceArchitecture.Features.Teams.ExecuteMission uses a module listed above it, which is the healthy direction.
34→11 SSW.VerticalSliceArchitecture.Features.Teams.GetAllTeams uses SSW.VerticalSliceArchitecture.Common.Pagination✕
- Connections
- 2 pairs of types, where a type in SSW.VerticalSliceArchitecture.Features.Teams.GetAllTeams uses a type in SSW.VerticalSliceArchitecture.Common.Pagination.
- The types involved
SSW.VerticalSliceArchitecture.Features.Teams.GetAllTeams.GetAllTeamsRequest→SSW.VerticalSliceArchitecture.Common.Pagination.PagedRequestSSW.VerticalSliceArchitecture.Features.Teams.GetAllTeams.GetAllTeamsRequestValidator→SSW.VerticalSliceArchitecture.Common.Pagination.PagedRequestValidator
- Direction
- SSW.VerticalSliceArchitecture.Features.Teams.GetAllTeams uses SSW.VerticalSliceArchitecture.Common.Pagination, so a change to SSW.VerticalSliceArchitecture.Common.Pagination can break SSW.VerticalSliceArchitecture.Features.Teams.GetAllTeams, while a change to SSW.VerticalSliceArchitecture.Features.Teams.GetAllTeams can't break SSW.VerticalSliceArchitecture.Common.Pagination.
- Position
- Below the diagonal: SSW.VerticalSliceArchitecture.Features.Teams.GetAllTeams uses a module listed above it, which is the healthy direction.
34→22 SSW.VerticalSliceArchitecture.Features.Teams.GetAllTeams uses SSW.VerticalSliceArchitecture.Common.Persistence✕
- Connections
- 1 pair of types, where a type in SSW.VerticalSliceArchitecture.Features.Teams.GetAllTeams uses a type in SSW.VerticalSliceArchitecture.Common.Persistence.
- The types involved
SSW.VerticalSliceArchitecture.Features.Teams.GetAllTeams.GetAllTeamsEndpoint→SSW.VerticalSliceArchitecture.Common.Persistence.ApplicationDbContext
- Direction
- SSW.VerticalSliceArchitecture.Features.Teams.GetAllTeams uses SSW.VerticalSliceArchitecture.Common.Persistence, so a change to SSW.VerticalSliceArchitecture.Common.Persistence can break SSW.VerticalSliceArchitecture.Features.Teams.GetAllTeams, while a change to SSW.VerticalSliceArchitecture.Features.Teams.GetAllTeams can't break SSW.VerticalSliceArchitecture.Common.Persistence.
- Position
- Below the diagonal: SSW.VerticalSliceArchitecture.Features.Teams.GetAllTeams uses a module listed above it, which is the healthy direction.
35→22 SSW.VerticalSliceArchitecture.Features.Teams.GetTeam uses SSW.VerticalSliceArchitecture.Common.Persistence✕
- Connections
- 1 pair of types, where a type in SSW.VerticalSliceArchitecture.Features.Teams.GetTeam uses a type in SSW.VerticalSliceArchitecture.Common.Persistence.
- The types involved
SSW.VerticalSliceArchitecture.Features.Teams.GetTeam.GetTeamEndpoint→SSW.VerticalSliceArchitecture.Common.Persistence.ApplicationDbContext
- Direction
- SSW.VerticalSliceArchitecture.Features.Teams.GetTeam uses SSW.VerticalSliceArchitecture.Common.Persistence, so a change to SSW.VerticalSliceArchitecture.Common.Persistence can break SSW.VerticalSliceArchitecture.Features.Teams.GetTeam, while a change to SSW.VerticalSliceArchitecture.Features.Teams.GetTeam can't break SSW.VerticalSliceArchitecture.Common.Persistence.
- Position
- Below the diagonal: SSW.VerticalSliceArchitecture.Features.Teams.GetTeam uses a module listed above it, which is the healthy direction.
36→21 Seeder.Initializers uses SSW.VerticalSliceArchitecture.Common.Domain.Heroes✕
- Connections
- 1 pair of types, where a type in Seeder.Initializers uses a type in SSW.VerticalSliceArchitecture.Common.Domain.Heroes.
- The types involved
Seeder.Initializers.ApplicationDbContextInitializer→SSW.VerticalSliceArchitecture.Common.Domain.Heroes.Hero
- Direction
- Seeder.Initializers uses SSW.VerticalSliceArchitecture.Common.Domain.Heroes, so a change to SSW.VerticalSliceArchitecture.Common.Domain.Heroes can break Seeder.Initializers, while a change to Seeder.Initializers can't break SSW.VerticalSliceArchitecture.Common.Domain.Heroes.
- Position
- Below the diagonal: Seeder.Initializers uses a module listed above it, which is the healthy direction.
36→22 Seeder.Initializers uses SSW.VerticalSliceArchitecture.Common.Persistence✕
- Connections
- 1 pair of types, where a type in Seeder.Initializers uses a type in SSW.VerticalSliceArchitecture.Common.Persistence.
- The types involved
Seeder.Initializers.ApplicationDbContextInitializer→SSW.VerticalSliceArchitecture.Common.Persistence.ApplicationDbContext
- Direction
- Seeder.Initializers uses SSW.VerticalSliceArchitecture.Common.Persistence, so a change to SSW.VerticalSliceArchitecture.Common.Persistence can break Seeder.Initializers, while a change to Seeder.Initializers can't break SSW.VerticalSliceArchitecture.Common.Persistence.
- Position
- Below the diagonal: Seeder.Initializers uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
At a glance — Domain Modelling
At a glance — Performance
Roadmap
Top priorities: Make the call chain async end-to-end and await it — never block on a Task with .Wait()/.GetAwaiter().GetResult(); Add a benchmarking harness for the hot paths and run it in CI to catch regressions (for .NET, a BenchmarkDotNet project with [MemoryDiagnoser] to track allocations); Make types internal by default; expose only the deliberate public API so internals can change without breaking consumers.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Make the call chain async end-to-end and await it — never block on a Task with .Wait()/.GetAwaiter().GetResult(). | +7.2 pts | Medium | Async & latency hygiene |
| Add a benchmarking harness for the hot paths and run it in CI to catch regressions (for .NET, a BenchmarkDotNet project with [MemoryDiagnoser] to track allocations). | +5.2 pts | Medium | Benchmark discipline |
| Make types internal by default; expose only the deliberate public API so internals can change without breaking consumers. | +3.4 pts | Medium | Library API & versioning |
| Make sure a person approves each release. The release job names an environment, but its approval rules live in the code host's settings, where we can't see them. Check that a reviewer must approve each release, or publish releases as drafts first, so a bad build can be stopped before anyone downloads it. | +1.4 pts | Medium | Deployment & Rollback |
| Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release. | +1.4 pts | Medium | Release Hygiene |
| The .NET analyzers are running but not blocking — tighten them (set <AnalysisMode>All</AnalysisMode>, or treat analyzer warnings as errors on CI) so a security/quality regression fails the build rather than scrolling past as a warning. | +1.1 pts | Medium | Security & performance tooling |
| Reference other aggregates by their strongly-typed id, never by object reference, so each aggregate stays an independent consistency boundary. | +1.1 pts | Medium | Aggregate boundaries |
| Resolve the 3 NoWarnInCsproj finding(s) in Explicit Debt — start with Directory.Build.props (3). | +0.4 pts | Low | Explicit Debt |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| Directory.Build.props | 5.8 | Mixed | Explicit Debt: NoWarnInCsproj |
| src/ServiceDefaults/Extensions.cs | 8.2 | Near-clean | Explicit Debt: CommentedOutCode |
| src/WebApi/Common/Middleware/EventualConsistencyMiddleware.cs | 8.2 | Near-clean | Explicit Debt: TodoComment |
| src/WebApi/Common/Persistence/VogenEfCoreConverters.cs | 8.2 | Near-clean | Explicit Debt: TodoComment |
| src/WebApi/Features/Heroes/HeroesFeature.cs | 8.2 | Near-clean | Explicit Debt: TodoComment |
| src/WebApi/Features/Teams/TeamsFeature.cs | 8.2 | Near-clean | Explicit Debt: TodoComment |
| src/WebApi/Host/Extensions/FastEndpointsExt.cs | 8.2 | Near-clean | Explicit Debt: TodoComment |
| src/WebApi/Host/FeatureDiscovery.cs | 8.2 | Near-clean | Explicit Debt: TodoComment |
| tests/WebApi.IntegrationTests/Common/Infrastructure/Web/WebApiTestFactory.cs | 8.2 | Near-clean | Explicit Debt: TodoComment |
| src/WebApi/Features/Heroes/CreateHero/CreateHeroRequestValidator.cs | 8.5 | Near-clean | Code Duplication: Duplicated block (24 lines × 2) |
| src/WebApi/Common/Domain/Heroes/Hero.cs | 8.5 | Near-clean | Code Duplication: Duplicated block (5 lines × 3) |
| tests/WebApi.UnitTests/Features/Heroes/HeroTests.cs | 8.5 | Near-clean | Test Quality: No assertions: Create_WithSameNameAndAlias_ShouldSucceed |
| docs/adr/20240513-use-log4brains-to-manage-the-adrs.md | 9.0 | Near-clean | Architectural Integrity: Classify ADR enforcement: Use Log4brains to manage the ADRs |
| docs/adr/20251018-api-use-fastendpoints-instead-of-minimal-apis.md | 9.5 | Near-clean | Architectural Integrity: Classify ADR enforcement: API - Use FastEndpoints instead of Minimal APIs |
| docs/adr/20260515-vertical-slices-use-a-folder-per-slice.md | 9.5 | Near-clean | Architectural Integrity: Classify ADR enforcement: Vertical Slices - Use a folder per slice |
| docs/adr/20260612-use-aggregate-specification-classes-with-factory-methods.md | 9.5 | Near-clean | Architectural Integrity: Classify ADR enforcement: Use Aggregate Specification Classes with Factory Methods |
| docs/adr/20260802-use-aspire-addefmigrations-for-database-migrations.md | 9.5 | Near-clean | Architectural Integrity: Classify ADR enforcement: Use Aspire's AddEFMigrations for Database Migrations |
| tools/AppHost/AppHost.cs | 9.5 | Near-clean | Comment Value: redundant comment |
How the grades work
A definite problem that already costs you something and drags the score down: a missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here tends to cause failures elsewhere.
Likely wrong, but not failing yet. It degrades the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to carry for two years either.
Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.
Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.
Methodology & how to trust this report
This survey is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. All 88 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 1.0, the weighted average across measured dimensions.
What we checked — 88 dimensions across the health lenses
- Can you open the finding? Real findings cite a repo-relative file and line you can open at the cited line — never an absolute scratch path. Here, 77 of 93 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Canine Code Analyzer duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 | ✓ deterministic |
Run transparency — what happened this run
- D8 Code Coverage — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Coverage NOT MEASURED: `--collect:"XPlat Code Coverage"` names a data collector that ships in the `coverlet.collector` package, and this repository wires up none — no test project references it and no runsettings declares one. The absence of coverage here is therefore not evidence about the suite or about our analyzer environment: without a collector, `--collect` produces nothing even from a suite that builds and passes. Add a `coverlet.collector` PackageReference to the test project(s) (or commit the Cobertura/OpenCover/lcov report your CI produces) and real coverage will be measured. It is excluded from the score rather than counted as a near-zero defect. You can widen what we reach: add the `coverlet.collector` package to the test projects to enable coverage (or commit the Cobertura/OpenCover/lcov report your CI produces).
- 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: `dotnet list package` exited 1 with no output.
- 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: solution references project 'src\ServiceDefaults\ServiceDefaults.csproj' but the on-disk path is 'src/ServiceDefaults/ServiceDefaults.csproj' (separator/casing mismatch); on a case-sensitive file system MSBuildWorkspace would load 0 of these projects. Loading a corrected copy of the solution.
- D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This kind did not reach the 95 % precision gate in three adjudicated runs (docs/plans/deterministic-engine/adjudication/D19-sample3-v3.md), so by the pre-registered fallback it publishes no row until a re-measurement shows it does. The candidates are counted here, not reported as findings, and the score does not include them.
- D22 Internal API Consistency — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. The loaded project set declares no packable project and no `.Contracts` project, so there is no intentionally-exposed surface for API consistency to be judged over.
- D29 Static Analysis (SAST) — 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. Semgrep reported an error with no file attached, so its rules did not run: File not found: AGENTS.md. The scanner (semgrep) ran but its output could not be parsed into the expected shape, so this run is a measurement gap rather than a clean pass.
- D44 Platform End-of-Life — 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 dimension reads a project's own statement about the platform it runs on: a TargetFramework in a .NET project file, a .nvmrc or .python-version, a capped requires-python, a Rust toolchain file or Cargo.toml rust-version, a .go-version, .java-version, .ruby-version, .tool-versions or .sdkmanrc, a go.mod go directive, a Maven or Gradle Java level or toolchain, a Gemfile's ruby directive, a mix.exs elixir requirement, a rebar.config minimum_otp_vsn, a pubspec.yaml SDK constraint, a build.sbt scalaVersion, or a framework major pinned by a dependency constraint. This repository carries none of them, so nothing about its platform was established. That is a gap in this analyzer's coverage, NOT a finding that the platform is supported — a language whose runtime is declared elsewhere (Package.swift, a Dockerfile) is simply not read here yet.
- AXR1 Runtime accessibility — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via ToolchainServer (src/WebApi). the service exited before it opened a port — `ASPNETCORE_URLS=http://127.0.0.1:0 ASPNETCORE_ENVIRONMENT=Development dotnet run --no-build --no-launch-profile --project 'WebApi.csproj'`: dpointRouteMapper.Map(IEndpointRouteBuilder app) at FastEndpoints.MainExtensions.MapFastEndpoints(IEndpointRouteBuilder app, Action`1 configAction) at FastEndpoints.MainExtensions.UseFastEndpoin…; runtime evidence skipped (launch chosen because src/WebApi/WebApi.csproj is a Microsoft.NET.Sdk.Web project).
- DM8 Value-object opportunities — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check finds primitive parameters that travel together through several signatures of the domain (a missing value object). Its deterministic rule has not yet shown 95 % precision on adjudicated rows, so the clumps it finds are counted here and not published as findings, and the card carries no score. That is a limit of the analyzer, not a finding about your code.
- 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.
- PF3 Async & latency hygiene — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 19 further occurrence(s) are not listed individually; the score already reflects all 59.
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.
- D7 Architectural Integrity: Layering is checked against detected/declared rules — an architecture whose boundaries live in convention or in code review, not in a rule a scanner can read, is not enforced here.
- 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.
- D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D18 Solution Shape: Build integrity reflects whether the solution compiled in this environment — a build that needs a private feed, a specific SDK, or a generated file absent from the repo can read as broken when it is merely unreproducible here.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
- D24 Comment Value: Comment value is measured as redundancy only: a comment that repeats its code's words is found, but a paraphrase in other words, a vague comment, or one the code contradicts is not, and whether a comment is valuable is not claimed. Comments in other scripts or languages, and outside C#, are not judged.
- D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
- D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- 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.
- DM4 Rich vs anemic model: Behaviour is detected as state mutation inside a method body — a method that enforces an invariant by validating-and-throwing without mutating reads as a query, and mutation delegated through an interface the scan can't resolve isn't credited; entities with zero public properties still drop out of the population. It detects that state changes, not whether the rule is correct.
- DM6 Domain ↔ infrastructure boundary: Infrastructure reached through a hand-rolled wrapper, a domain-named facade, reflection, or a string-keyed service locator resolves to a non-infra type and isn't seen; the body scan is symbol resolution over syntax, not full dataflow. A clean result means "no resolved infra reference in a domain body", not a proof of purity.
- ED5 Idempotency: Idempotency is read from the handler body and one hop below: a mutation is flagged only on structural double-apply evidence (a fresh-identity insert, an accumulation, a growing list, an unkeyed POST/send/charge), so a duplicate effect through a home-grown gateway two hops down, or an insert keyed on the message with no unique constraint, is not flagged but counted as not classified; a guard enforced by a database constraint or a broker's exactly-once delivery is invisible either way. It flags the at-least-once double-apply SHAPE, not a runtime proof of a duplicate effect.
- M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
- P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
- P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
Dimensions
D1 · Cyclomatic Complexity
0 method(s) exceeded the cyclomatic complexity threshold of 15.
D2 · Cognitive Complexity
0 method(s) exceeded the cognitive complexity threshold of 15.
D3 · God Classes
0 god class(es) detected.
D4 · Code Duplication
2 duplicated block group(s) detected.
What to do
- Resolve the 1 Duplicated block (24 lines × 2) finding(s) in Code Duplication — start with CreateHeroRequestValidator.cs. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Duplicated block (5 lines × 3) finding(s) in Code Duplication — start with Hero.cs. — One of this dimension's main actionable groups (1 warning-level).
- Enforce Code Duplication in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D5 · Coupling
7 projects, 0 dependency cycle(s), 0 unstable depended-on project(s).
D6 · Cohesion (LCOM4)
0 of 9 classes have LCOM4 above 3.
D7 · Architectural Integrity
No mechanizable ADR was identified, so enforcement is not measured. Cycles found: 0.
What to do
- Resolve the 5 Classify ADR enforcement finding(s) in Architectural Integrity — start with 20240513-use-log4brains-to-manage-the-adrs.md, 20251018-api-use-fastendpoints-instead-of-minimal-apis.md, 20260515-vertical-slices-use-a-folder-per-slice.md. — One of this dimension's main actionable groups (5 recommendation-level).
- Enforce Architectural Integrity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D9 · Test Distribution
95 test methods: 70 unit, 25 integration, 0 BDD, 0 e2e.
D10 · Test Quality
0 skipped, 1 zero-assertion, 2 mock references across 95 tests.
What to do
- Resolve the 1 No assertions finding(s) in Test Quality — start with HeroTests.cs. — One of this dimension's main actionable groups (1 warning-level).
- Enforce Test Quality in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D11 · Test Reliability
0 flaky across 2 measured tier(s). unit: measured (0 flaky); integration: measured (0 flaky).
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D14 · License Compliance
0 of 250 packages use a banned license. ★ DEPTH: this repository's MSBuild projects declare 34 direct `PackageReference`(s), and 216 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.
D16 · Bus Factor
1 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is tools/AppHost/AppHost.cs. Counted over 9 of the 106 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
What to do
- Resolve the 1 Off-boarding risk finding(s) in Bus Factor. — One of this dimension's main actionable groups (1 recommendation-level).
D17 · Explicit Debt
11 deducted debt markers + unmeasured dead symbols across 2339 LoC in the .NET projects (0.9/KLoC) → score 8.2. Dead code not measured: the solution did not load cleanly, so the reference search was skipped.
What to do
- Resolve the 3 NoWarnInCsproj finding(s) in Explicit Debt — start with Directory.Build.props (3). — One of this dimension's main actionable groups (3 issue-level).
- Resolve the 7 TodoComment finding(s) in Explicit Debt — start with EventualConsistencyMiddleware.cs, VogenEfCoreConverters.cs, HeroesFeature.cs. — One of this dimension's main actionable groups (7 warning-level).
- Resolve the 1 CommentedOutCode finding(s) in Explicit Debt — start with Extensions.cs. — One of this dimension's main actionable groups (1 warning-level).
- Enforce Explicit Debt in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D18 · Solution Shape
7 projects, 152 source files, 4669 hand-written lines of code (2339 production / 2330 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 396 generated (machine-written code — designer, scaffolded and tool-emitted files — excluded from quality), 6 inter-project edges.
D19 · Documentation Quality
2 of 2 documentation facets pass in full. 5 document(s) read across 5 unit(s).
D20 · ADR Quality
1 of 5 evaluated ADRs have a defect readable from the log itself (a missing or empty section, no title, a single option, consequences with no cost, no status, a missing enforcement field, a status the log contradicts, a dangling link, an unlinked second decision on one question, a date that is no calendar day). How well each record argues its case is not measured.
D24 · Comment Value
1 of 62 judged comments only repeat the code they sit on (1.6 %).
What to do
- Resolve the 1 redundant comment finding(s) in Comment Value — start with AppHost.cs. — One of this dimension's main actionable groups (1 recommendation-level).
D26 · Project Cohesion
0 of 7 projects flagged as possibly oversized/incoherent.
D27 · Navigability
89 % of calls cross a namespace and 1 % go through an interface, but 100 % of collaborators are co-located — so a call's collaborators sit together and tracing stays easy. Baseline: small — navigation cost is tolerated.
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D30 · Dependency Vulnerabilities
No known-vulnerable dependencies in any ecosystem this repository declares.
D34 · Knowledge Freshness
3 of 9 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is src/ServiceDefaults/Extensions.cs. Counted over 9 of the 106 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
What to do
- Resolve the 3 Orphaned file finding(s) in Knowledge Freshness — start with Extensions.cs, DispatchDomainEventsInterceptor.cs, Team.cs. — One of this dimension's main actionable groups (3 recommendation-level).
- Resolve the 1 Orphaned files with no living knowledge finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
D35 · Change Coupling
No strong hidden change-coupling between production files.
D37 · Vulnerability-disclosure Policy
A vulnerability-disclosure policy (SECURITY.md) is published with a reporting contact.
D39 · IL Efficiency
0 of 210 first-party methods have an oversized IL body.
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
Frontend & cross-cutting dimensions
AX1 · Captive dependencies
AX10 · Code composition
AX2 · Stateful singletons
AX3 · Project dependency cycles
- The namespaces SSW.VerticalSliceArchitecture.Common.Domain.Heroes ↔ SSW.VerticalSliceArchitecture.Common.Domain.Teams depend on each other. The lightest dependency in the cycle is SSW.VerticalSliceArchitecture.Common.Domain.Heroes → SSW.VerticalSliceArchitecture.Common.Domain.Teams (SSW.VerticalSliceArchitecture.Common.Domain.Heroes.Hero → SSW.VerticalSliceArchitecture.Common.Domain.Teams.TeamId, 1 type pair(s)); cut that one first, e.g. by moving the shared type to a namespace both can use or inverting it behind an interface. — src/WebApi/Common/Domain/Heroes/Hero.cs:2
What to do
- Break namespace cycles inside a project by moving the shared type to a namespace both sides can use, or by inverting the back edge behind an interface.
AX4 · Dependency direction
AX5 · Architecture & structure
AX6 · Interface segregation
AX8 · Test isolation
DM1 · Aggregate boundaries
- `Team` references the aggregate root `Hero` directly (via `_heroes`) — hold its `HeroId` instead. — src/WebApi/Common/Domain/Teams/Team.cs:15
- `Team` references the aggregate root `Hero` directly (via `Heroes`) — hold its `HeroId` instead. — src/WebApi/Common/Domain/Teams/Team.cs:33
What to do
- Reference other aggregates by their strongly-typed id, never by object reference, so each aggregate stays an independent consistency boundary.
DM10 · One transaction, one aggregate
DM11 · Constructible invalid state
DM12 · Ambient inputs in the domain
DM2 · Strongly-typed ids
DM4 · Rich vs anemic model
DM5 · Encapsulated state
- `Hero` exposes publicly writable state (Name, Alias). — src/WebApi/Common/Domain/Heroes/Hero.cs:11
What to do
- Make entity setters private/init-only and hand collections out as IReadOnlyList/IReadOnlyCollection over a private backing field; change state only through methods that enforce the invariants (Marten/EF can bind via constructor or private setters).
DM6 · Domain ↔ infrastructure boundary
DM9 · Scattered domain decisions
ED5 · Idempotency
GD1 · Unfinished & placeholder code
IC1 · Incompleteness & stubs
- A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers). (×2) — tools/AppHost/AppHost.cs:35, tools/Seeder/Initializers/ApplicationDbContextInitializer.cs:75
What to do
- Clear the softer debt: remove commented-out code and dead branches, re-enable or delete skipped tests, and replace blanket warning suppressions with targeted ones.
M1 · Documentation (README)
What to do
- Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
- Add a README to the 4 of 4 project(s) that lack one — worth up to 2 pts.
M2 · Architecture documentation
What to do
- Grow the ADR log (currently 8) — reach 20 to raise the maturity tier; document significant decisions as they're made.
M3 · Folder & project structure
- Only 4/7 projects share a common root namespace — the code's module identity is inconsistent.
What to do
- Adopt a consistent root-namespace convention (a shared prefix, e.g. Acme.*); short project-file/directory names are fine as long as the RootNamespace is uniform.
M4 · Documentation accuracy
P1 · CI/CD gates
P10 · Library API & versioning
- 117/145 types (81%) are public. For a library, every public type is a stability contract — make internal-by-default and expose only the intended API.
- No explicit version was found by any of the six routes this check reads: a `<Version>` or `<VersionPrefix>` property; a `GitVersion` or `MinVer` reference; the split Arcade spelling (`<MajorVersion>` AND `<MinorVersion>` together); a hand-written `[assembly: AssemblyVersion]` in source, with `bin/` and `obj/` excluded so the SDK's generated AssemblyInfo cannot satisfy it; or a version handed to MSBuild by the pipeline, as `-p:Version=` / `-p:PackageVersion=` on a `dotnet build` or `dotnet pack` line. Only project files, first-party source and CI files are read, so a version computed somewhere none of those can see is invisible here. A published library needs explicit semantic versioning so consumers can reason about breaking changes.
What to do
- Make types internal by default; expose only the deliberate public API so internals can change without breaking consumers.
- Stamp a semantic version (csproj <Version> or GitVersion/MinVer) and follow semver for breaking changes.
P2 · Observability
- Only 3/4 service-like projects use logging (pure contract/DTO projects are excluded — they have nothing to log). Of those 4, 3 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.
P3 · Security & performance tooling
What to do
- The .NET analyzers are running but not blocking — tighten them (set <AnalysisMode>All</AnalysisMode>, or treat analyzer warnings as errors on CI) so a security/quality regression fails the build rather than scrolling past as a warning.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
What to do
- Make sure a person approves each release. The release job names an environment, but its approval rules live in the code host's settings, where we can't see them. Check that a reviewer must approve each release, or publish releases as drafts first, so a bad build can be stopped before anyone downloads it.
P6 · Release Hygiene
- No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
What to do
- Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.
P7 · Outbound HTTP resilience
P8 · Schema migrations
PF1 · Benchmark discipline
- No benchmark suite was found by the two searches this check runs. FIRST, a BenchmarkDotNet package reference in any project file — every project the workspace loaded, plus a walk of project files on disk that never loaded, because a benchmark suite is exactly the project a partial load drops. SECOND, a script harness: a file whose name contains `benchmark` and ends `.py`, `.sh`, `.ps1`, `.bash`, `.rb`, `.js` or `.mjs`, credited ONLY when this repository's CI text also mentions benchmarks — a harness no pipeline runs is read as a fixture, deliberately. Neither search can see a benchmark suite in another ecosystem's idiom (a Go `testing.B` file, a JMH or criterion project, a pytest-benchmark run), so this is 'no benchmark found by those two searches', not a verdict that the repository has none. Where code is performance-sensitive, a benchmark guards against silent regressions — but it's a bonus here, not a deduction.
What to do
- Add a benchmarking harness for the hot paths and run it in CI to catch regressions (for .NET, a BenchmarkDotNet project with [MemoryDiagnoser] to track allocations).
PF3 · Async & latency hygiene
- 1 blocking call(s) on async work (.Wait()/.GetAwaiter().GetResult()) — these waste a thread and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
- `.GetAwaiter().GetResult()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one). — src/WebApi/Common/Persistence/Interceptors/DispatchDomainEventsInterceptor.cs:30
- Only 1/56 awaits in library code use ConfigureAwait(false). A library that captures the caller's context can stall or deadlock its host — the classic way a dependency drags an app down.
- `await Task.CompletedTask` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. (×3) — src/WebApi/Common/FastEndpoints/LoggingPreProcessor.cs:23, src/WebApi/Common/FastEndpoints/PerformancePostProcessor.cs:37, src/WebApi/Common/FastEndpoints/PerformancePreProcessor.cs:13
- `await strategy.ExecuteInTransactionAsync(async () => { await PublishEvents(context)...` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/WebApi/Common/Middleware/EventualConsistencyMiddleware.cs:21
- `await PublishEvents(context)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/WebApi/Common/Middleware/EventualConsistencyMiddleware.cs:23
- `await _next(context)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/WebApi/Common/Middleware/EventualConsistencyMiddleware.cs:27
- `await nextEvent.PublishAsync()` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/WebApi/Common/Middleware/EventualConsistencyMiddleware.cs:38
- `await SpecificationEvaluator.Default .GetQuery(source, specification, evaluateCrite...` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/WebApi/Common/Pagination/PagedQueryableExtensions.cs:41
- `await SpecificationEvaluator.Default .GetQuery(source, specification) .Select(proje...` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/WebApi/Common/Pagination/PagedQueryableExtensions.cs:45
- `await DispatchDomainEvents(eventData.Context)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/WebApi/Common/Persistence/Interceptors/DispatchDomainEventsInterceptor.cs:39
- `await base.SavedChangesAsync(eventData, result, cancellationToken)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/WebApi/Common/Persistence/Interceptors/DispatchDomainEventsInterceptor.cs:40
- `await PublishDomainEvents(domainEvents)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/WebApi/Common/Persistence/Interceptors/DispatchDomainEventsInterceptor.cs:62
- `await domainEvent.PublishAsync()` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/WebApi/Common/Persistence/Interceptors/DispatchDomainEventsInterceptor.cs:71
- `await dbContext.SaveChangesAsync(ct)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. (×6) — src/WebApi/Features/Heroes/CreateHero/CreateHeroEndpoint.cs:22, src/WebApi/Features/Heroes/UpdateHero/UpdateHeroEndpoint.cs:35, src/WebApi/Features/Teams/AddHeroToTeam/AddHeroToTeamEndpoint.cs:45, …
- `await Send.OkAsync(new CreateHeroResponse(hero.Id.Value), ct)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/WebApi/Features/Heroes/CreateHero/CreateHeroEndpoint.cs:24
- `await dbContext.Heroes.ToPagedListAsync( spec, h => new GetAllHeroesResponse( h.Id....` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/WebApi/Features/Heroes/GetAllHeroes/GetAllHeroesEndpoint.cs:21
- `await Send.OkAsync(heroes, ct)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/WebApi/Features/Heroes/GetAllHeroes/GetAllHeroesEndpoint.cs:31
- `await dbContext.Heroes .Include(h => h.Powers) .FirstOrDefaultAsync(h => h.Id == he...` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/WebApi/Features/Heroes/UpdateHero/UpdateHeroEndpoint.cs:20
- `await Send.NotFoundAsync(ct)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. (×5) — src/WebApi/Features/Heroes/UpdateHero/UpdateHeroEndpoint.cs:26, src/WebApi/Features/Teams/AddHeroToTeam/AddHeroToTeamEndpoint.cs:30, src/WebApi/Features/Teams/AddHeroToTeam/AddHeroToTeamEndpoint.cs:40, …
- `await Send.NoContentAsync(ct)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. (×5) — src/WebApi/Features/Heroes/UpdateHero/UpdateHeroEndpoint.cs:37, src/WebApi/Features/Teams/AddHeroToTeam/AddHeroToTeamEndpoint.cs:47, src/WebApi/Features/Teams/CompleteMission/CompleteMissionEndpoint.cs:41, …
- `await Send.ErrorsAsync(cancellation: ct)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. (×2) — src/WebApi/Features/Teams/CompleteMission/CompleteMissionEndpoint.cs:35, src/WebApi/Features/Teams/ExecuteMission/ExecuteMissionEndpoint.cs:35
- `await dbContext.Teams.ToPagedListAsync( spec, t => new GetAllTeamsResponse(t.Id.Val...` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/WebApi/Features/Teams/GetAllTeams/GetAllTeamsEndpoint.cs:21
- `await Send.OkAsync(teams, ct)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/WebApi/Features/Teams/GetAllTeams/GetAllTeamsEndpoint.cs:26
What to do
- Make the call chain async end-to-end and await it — never block on a Task with .Wait()/.GetAwaiter().GetResult().
- In library code, append .ConfigureAwait(false) to every await (or set <ConfigureAwait>false</ConfigureAwait> / use the analyzer CA2007) so the library never captures the host's context.
S1 · Web-Security Posture
- None of the 11 security response headers the OWASP Secure Headers Project recommends (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options, …) is configured — defense in depth, even when a reverse proxy could set them. (−2.0 on this card.)
- This web host's pipeline is composed here and adds no security response header (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, a frame policy) to what it serves. — src/WebApi/Program.cs:7
What to do
- Add security response headers (Content-Security-Policy first, then Strict-Transport-Security, X-Content-Type-Options and a frame policy) — defense in depth, even when a reverse proxy could set them.
X1 · Async correctness
- Blocking on a Task with `.Wait()`/`.GetAwaiter().GetResult()` can deadlock (and wastes a thread). Prefer awaiting it: make the caller `async` and `await` instead. Where a synchronous entry point must stay — a public sync API you cannot break, or a process entry point that must not return until the work finishes — the block belongs in ONE documented bridge and never inside code that is already async; and where it already is that bridge, give the wait a TIMEOUT so a hung task fails the call instead of hanging the process. — src/WebApi/Common/Persistence/Interceptors/DispatchDomainEventsInterceptor.cs:30
What to do
- Sync-over-async (deadlock risk)
X12 · Unreachable branch
X13 · Undrained process stream
X14 · Bypassable address classification
X15 · Unvalidated length from an untrusted reader
X16 · Unfloored truncation loop
X17 · Uncapped recursion over a caller-supplied document
X18 · Disposal-pattern correctness
X19 · Unrestored process-global state
X2 · Cancellation propagation
- Only 17/23 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, and the token `context.RequestAborted` carries reaches none of the calls here that take one — this work can't be stopped early once started. Pass `context.RequestAborted` on, or take a CancellationToken. — src/WebApi/Common/Middleware/EventualConsistencyMiddleware.cs:30
- No CancellationToken parameter — this work can't be stopped early once started. (×4) — src/WebApi/Common/Persistence/Interceptors/DispatchDomainEventsInterceptor.cs:43, src/WebApi/Common/Persistence/Interceptors/DispatchDomainEventsInterceptor.cs:68, tools/Seeder/Initializers/ApplicationDbContextInitializer.cs:80, …
- 1 async method(s) await work their caller's cancellation cannot reach: a CancellationToken they hold (a parameter, or the one a framework-fixed signature carries) is never passed on, or the call is handed CancellationToken.None, default or an already-cancelled token. Forward the caller's token to that call.
- Its signature is fixed by the framework, and the token it carries (`context.RequestAborted`) reaches none of the calls here that take one — so an aborted request or a stopping host still waits for that work. Pass `context.RequestAborted` to them. — src/WebApi/Common/Middleware/EventualConsistencyMiddleware.cs:16
What to do
- Thread a CancellationToken through async methods so work stops promptly on cancellation.
X20 · Mistyped argument guard
X21 · Side-effecting pattern guard
X22 · Contradicted release guard
X23 · Unguarded diagnostic materialisation
X24 · Document value interpolated into markup unescaped
X25 · Inert configuration knob
X26 · Unsynchronised callback handoff
X27 · Collection changed while being enumerated
X28 · Index access outside its own emptiness guard
X29 · Per-element action decided by a fixed element
X3 · Exception handling
X30 · Support guard that admits what it rejects
X32 · Type resolved by simple name across every loaded assembly
X4 · Structured logging
X5 · Nullable reference types
- ~0.7 `!` suppressions per 1k syntax nodes — 9 suppression(s) across the 13735 syntax node(s) in code where nullable warnings are ENABLED, which is the only code a `!` can suppress anything in (a `!` under `#nullable disable` is inert and is not counted, and its file's nodes are not in the denominator). Each one tells the compiler to trust you about null, suppressing the very safety NRTs provide.
What to do
- Enable <Nullable>enable</Nullable> across all projects and resolve warnings rather than suppressing with `!`.
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 83% | Exemplary | Solid. |
| Architecture | 94% | Exemplary | Strongest area. |
| Maturity | 81% | Exemplary | Solid. |
| Readiness | 56% | Adequate — gated by P10 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 89% | Exemplary | Solid. |
| Domain Modelling | 78% | Adequate — gated by DM1 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Performance | 52% | Adequate | Largest drag on the score — prioritise here. |
Not evidenced — 1 control(s) we could not find positive evidence for
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 43 check(s) not relevant to this codebase
- AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
- AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
- AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
- AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
- AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
- AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
- AC7 A11y enforcement — No web markup found — accessibility is not applicable to this repository.
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXR1 Runtime accessibility — the service exited before it opened a port — `ASPNETCORE_URLS=http://127.0.0.1:0 ASPNETCORE_ENVIRONMENT=Development dotnet run --no-build --no-launch-profile --project 'WebApi.csproj'`: dpointRouteMapper.Map(IEndpointRouteBuilder app) at FastEndpoints.MainExtensions.MapFastEndpoints(IEndpointRouteBuilder app, Action`1 configAction) at FastEndpoints.MainExtensions.UseFastEndpoin…; runtime evidence skipped (launch chosen because src/WebApi/WebApi.csproj is a Microsoft.NET.Sdk.Web project) This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
- C1 Data Protection — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
- 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
- D21 Naming Consistency — N/A — too few peers to establish a naming convention (496 declarations, no unit with a dominant convention).
- D22 Internal API Consistency — No intentionally-exposed public API to evaluate for consistency.
- D23 Boundary Type-Coupling — small single-context codebase (2,339 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 (WebApi), 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"]`.
- D25 ADR Conformance — None of 5 binding record(s) states a rule in checkable form (a backticked element with a prohibition, or an `adr-rules` block), so conformance cannot be read from the code. Write the rule as an `adr-rules` block (`forbid:` a symbol, a package or a dependency) to make it checkable.
- D29 Static Analysis (SAST) — Scanner output unparseable — not a clean result
- D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
- D32 Data Compliance (PII/GDPR) — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
- D36 Supply-chain Provenance & Signing — 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).
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D44 Platform End-of-Life — Platform end-of-life not assessed — this repository declares no platform this pass reads
- D8 Code Coverage — Coverage not measured — no coverage collector is wired up
- DM3 Integration-event coupling — no integration events detected — coupling check not applicable
- DM7 Repository granularity — no repository abstraction detected (e.g. uses a document session)
- DM8 Value-object opportunities — not scored — the deterministic rule found 0 candidate clump(s); its rows are withheld until it has a measured precision of 95 % (a sample of fewer than 10 rows cannot show one)
- ED1 Event-Driven — applicable but not scored (2 of 3 signals for this style — below the bar we score at): 2 event handler(s); 1 CQRS handler(s)
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
- P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (Cobertura — `dotnet test --collect:"XPlat Code Coverage"` with a `coverlet.collector` PackageReference) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures, or wire coverage collection into CI, to enable this cross-layer check
- PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
- SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X10 Duplicated predicate — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X7 Silent fallback defaults — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
Critical — 6 finding(s)
- NoWarnInCsproj Directory.Build.props:15
- NoWarnInCsproj Directory.Build.props:18
- NoWarnInCsproj Directory.Build.props:21
- Aggregate holds a reference to another aggregate: Team._heroes src/WebApi/Common/Domain/Teams/Team.cs:15
- Aggregate holds a reference to another aggregate: Team.Heroes src/WebApi/Common/Domain/Teams/Team.cs:33
- Namespace dependency cycle src/WebApi/Common/Domain/Heroes/Hero.cs:2
Serious — 58 finding(s)
- Awaits without ConfigureAwait(false)
- Awaits without ConfigureAwait(false) src/WebApi/Common/FastEndpoints/LoggingPreProcessor.cs:23
- Awaits without ConfigureAwait(false) src/WebApi/Common/FastEndpoints/PerformancePostProcessor.cs:37
- Awaits without ConfigureAwait(false) src/WebApi/Common/FastEndpoints/PerformancePreProcessor.cs:13
- Awaits without ConfigureAwait(false) src/WebApi/Common/Middleware/EventualConsistencyMiddleware.cs:21
- Awaits without ConfigureAwait(false) src/WebApi/Common/Middleware/EventualConsistencyMiddleware.cs:23
- Awaits without ConfigureAwait(false) src/WebApi/Common/Middleware/EventualConsistencyMiddleware.cs:27
- Awaits without ConfigureAwait(false) src/WebApi/Common/Middleware/EventualConsistencyMiddleware.cs:38
- Awaits without ConfigureAwait(false) src/WebApi/Common/Pagination/PagedQueryableExtensions.cs:41
- Awaits without ConfigureAwait(false) src/WebApi/Common/Pagination/PagedQueryableExtensions.cs:45
- Awaits without ConfigureAwait(false) src/WebApi/Common/Persistence/Interceptors/DispatchDomainEventsInterceptor.cs:39
- Awaits without ConfigureAwait(false) src/WebApi/Common/Persistence/Interceptors/DispatchDomainEventsInterceptor.cs:40
- Awaits without ConfigureAwait(false) src/WebApi/Common/Persistence/Interceptors/DispatchDomainEventsInterceptor.cs:62
- Awaits without ConfigureAwait(false) src/WebApi/Common/Persistence/Interceptors/DispatchDomainEventsInterceptor.cs:71
- Awaits without ConfigureAwait(false) src/WebApi/Features/Heroes/CreateHero/CreateHeroEndpoint.cs:22
- Awaits without ConfigureAwait(false) src/WebApi/Features/Heroes/CreateHero/CreateHeroEndpoint.cs:24
- Awaits without ConfigureAwait(false) src/WebApi/Features/Heroes/GetAllHeroes/GetAllHeroesEndpoint.cs:21
- Awaits without ConfigureAwait(false) src/WebApi/Features/Heroes/GetAllHeroes/GetAllHeroesEndpoint.cs:31
- Awaits without ConfigureAwait(false) src/WebApi/Features/Heroes/UpdateHero/UpdateHeroEndpoint.cs:20
- Awaits without ConfigureAwait(false) src/WebApi/Features/Heroes/UpdateHero/UpdateHeroEndpoint.cs:26
- Awaits without ConfigureAwait(false) src/WebApi/Features/Heroes/UpdateHero/UpdateHeroEndpoint.cs:35
- Awaits without ConfigureAwait(false) src/WebApi/Features/Heroes/UpdateHero/UpdateHeroEndpoint.cs:37
- Awaits without ConfigureAwait(false) src/WebApi/Features/Teams/AddHeroToTeam/AddHeroToTeamEndpoint.cs:30
- Awaits without ConfigureAwait(false) src/WebApi/Features/Teams/AddHeroToTeam/AddHeroToTeamEndpoint.cs:40
- Awaits without ConfigureAwait(false) src/WebApi/Features/Teams/AddHeroToTeam/AddHeroToTeamEndpoint.cs:45
- TodoComment src/WebApi/Common/Middleware/EventualConsistencyMiddleware.cs:44
- TodoComment src/WebApi/Common/Persistence/VogenEfCoreConverters.cs:6
- TodoComment src/WebApi/Features/Heroes/HeroesFeature.cs:9
- TodoComment src/WebApi/Features/Teams/TeamsFeature.cs:9
- TodoComment src/WebApi/Host/Extensions/FastEndpointsExt.cs:21
- TodoComment src/WebApi/Host/FeatureDiscovery.cs:6
- TodoComment tests/WebApi.IntegrationTests/Common/Infrastructure/Web/WebApiTestFactory.cs:27
- Async method without CancellationToken: PublishEvents src/WebApi/Common/Middleware/EventualConsistencyMiddleware.cs:30
- Async method without CancellationToken: DispatchDomainEvents src/WebApi/Common/Persistence/Interceptors/DispatchDomainEventsInterceptor.cs:43
- Async method without CancellationToken: PublishDomainEvents src/WebApi/Common/Persistence/Interceptors/DispatchDomainEventsInterceptor.cs:68
- Async method without CancellationToken: SeedHeroes tools/Seeder/Initializers/ApplicationDbContextInitializer.cs:80
- Async method without CancellationToken: SeedTeams tools/Seeder/Initializers/ApplicationDbContextInitializer.cs:103
- Sync-over-async blocking
- Sync-over-async blocking src/WebApi/Common/Persistence/Interceptors/DispatchDomainEventsInterceptor.cs:30
- No assertions: Create_WithSameNameAndAlias_ShouldSucceed tests/WebApi.UnitTests/Features/Heroes/HeroTests.cs:43
- CommentedOutCode src/ServiceDefaults/Extensions.cs:93
- Duplicated block (24 lines × 2) src/WebApi/Features/Heroes/CreateHero/CreateHeroRequestValidator.cs:9
- Duplicated block (5 lines × 3) src/WebApi/Common/Domain/Heroes/Hero.cs:22
- Sync-over-async (deadlock risk) src/WebApi/Common/Persistence/Interceptors/DispatchDomainEventsInterceptor.cs:30
- Async method drops its ambient CancellationToken: InvokeAsync src/WebApi/Common/Middleware/EventualConsistencyMiddleware.cs:16
Minor — 26 finding(s)
- Classify ADR enforcement: Use Log4brains to manage the ADRs docs/adr/20240513-use-log4brains-to-manage-the-adrs.md
- Classify ADR enforcement: API - Use FastEndpoints instead of Minimal APIs docs/adr/20251018-api-use-fastendpoints-instead-of-minimal-apis.md
- Classify ADR enforcement: Vertical Slices - Use a folder per slice docs/adr/20260515-vertical-slices-use-a-folder-per-slice.md
- Classify ADR enforcement: Use Aggregate Specification Classes with Factory Methods docs/adr/20260612-use-aggregate-specification-classes-with-factory-methods.md
- Classify ADR enforcement: Use Aspire's AddEFMigrations for Database Migrations docs/adr/20260802-use-aspire-addefmigrations-for-database-migrations.md
- Orphaned file src/ServiceDefaults/Extensions.cs:1
- Orphaned file src/WebApi/Common/Persistence/Interceptors/DispatchDomainEventsInterceptor.cs:1
- Orphaned file src/WebApi/Common/Domain/Teams/Team.cs:1
- Commented-out code tools/AppHost/AppHost.cs:35
- Commented-out code tools/Seeder/Initializers/ApplicationDbContextInitializer.cs:75
- No security response headers detected
- No security response headers detected src/WebApi/Program.cs:7
- Off-boarding risk: anonymized user #1
- ADR has no Consequences section docs/adr/20240513-use-log4brains-to-manage-the-adrs.md:1
- redundant comment tools/AppHost/AppHost.cs:8
- Orphaned files with no living knowledge
- Mutable entity: Hero src/WebApi/Common/Domain/Heroes/Hero.cs:11
- Inconsistent root namespaces
- Large public API surface
- No explicit versioning
- Logging is not universal
- No changelog
- No performance benchmarks
- Not all async methods take a CancellationToken
- Some async methods drop the CancellationToken they accept
- Null-forgiving operator (`!`) suppressions reduce the NRT score
Minor — 3 finding(s)
- Mock framework: NSubstitute
- Mock framework: NSubstitute
- doc comments repeat the names tests/WebApi.IntegrationTests/Common/TestingDatabaseFixture.cs:27
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-8e8cdd23d82044d5813bdaa56165ffd9/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-8e8cdd23d82044d5813bdaa56165ffd9/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/WebApi/Common/Persistence/Migrations .aspire .claude .config .editorconfig .github .gitignore .log4brains.yml .template.config .worktreeinclude AGENTS.md CLAUDE.md CODE_OF_CONDUCT.md CONTEXT.md CONTRIBUTING.md Directory.Build.props Directory.Packages.props LICENSE README.md SECURITY.md SSW.VerticalSliceArchitecture.slnx VerticalSliceArchitecture.nuspec aspire.config.json docs global.json src tests tools | 0 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | dotnet | — | dotnet list SSW.VerticalSliceArchitecture.slnx package --vulnerable --include-transitive --format json | 0 | artifacts/raw/dotnet-vulnerable.json |
| D31 · IaC & Container Security | trivy | — | trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan. | 0 | — |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. | 0 | — |
| D36 · Supply-chain Provenance & Signing | provenance | — | provenance: not applicable — 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 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . /tmp/codehealth-osv-sbom-59d5c02264be49b780f4ff856aedd89f | 0 | artifacts/raw/osv-scanner.json |