Executive summary
stphnwlsh/CleanMinimalApi meets our standard for a template or a sample. It scores 62 out of 100 and is rated Strong, and 25 of its 32 critical findings are security problems in the build pipeline and in its automatic dependency updates.
Production Readiness, at 49, is the weakest lens and counts most in the score. The best first step is documenting the recovery plan, worth about 8 points. Protecting outgoing calls with timeouts comes next, worth about 5 points. Raising Production Readiness to 52 would lift the score to about 63.
Twenty-four pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. One automatic update takes new releases before a bad one can be spotted. Pinning each tool to an exact version and setting a waiting period for automatic updates would close both risks. The four sets of compiler warnings switched off in projects need turning back on in the build file.
The product code is 2,493 lines, about €8,500 to rebuild.
If Production Readiness rose from 49 to 52, the lowest score rated Strong, the score would rise from 62 to about 63.
New since the last survey: 36 findings
- Cyclomatic Complexity · report.command_summary (cyclomatic 33) REDACTED
- Cognitive Complexity · report.command_summary (cognitive 34) REDACTED
- Cognitive Complexity · report.render_tests (cognitive 22) REDACTED
- Cognitive Complexity · report.parse_coverage (cognitive 17) REDACTED
- Code Duplication · Duplicated block (8 lines × 2) src/Infrastructure/Databases/MovieReviews/Extensions/MovieReviewsDbContextExtensions.cs
- Code Duplication · Duplicated block (5 lines × 2) src/Application/Authors/Queries/GetAuthors/GetAuthorsValidator.cs
- Explicit Debt · CoverageExclusion src/Infrastructure/Databases/MovieReviews/MovieReviewsDbContextFactory.cs
- Explicit Debt · NoWarnInCsproj Directory.Build.props
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- IaC & Container Security · REDACTED
- IaC & Container Security · REDACTED
- DR & Backup · No DR/backup evidence
- Stateful singletons · Stateful singleton: MovieReviewsDatabase src/Infrastructure/Databases/MovieReviews/MovieReviewsDatabase.cs
- Outbound HTTP resilience · Outbound HTTP without resilience
Fixed since the last survey: 53 findings
- Code Duplication · Duplicated block (5 lines × 2) src/Infrastructure/Databases/MovieReviews/Mapping/AuthorMappingProfile.cs
- Code Coverage · Coverage not measured — no coverage collector is wired up
- Dependency Hygiene · Deprecated: MediatR.Extensions.Microsoft.DependencyInjection src/Application/Application.csproj
- Dependency Hygiene · Deprecated: AutoMapper.Extensions.Microsoft.DependencyInjection src/Infrastructure/Infrastructure.csproj
- Dependency Hygiene · Deprecated: xunit tests/Infrastructure.Tests.Integration/Infrastructure.Tests.Integration.csproj
- Dependency Hygiene · Deprecated: xunit tests/Application.Tests.Unit/Application.Tests.Unit.csproj
- Dependency Hygiene · Deprecated: xunit tests/Presentation.Tests.Integration/Presentation.Tests.Integration.csproj
- Dependency Hygiene · Deprecated: xunit tests/Presentation.Tests.Unit/Presentation.Tests.Unit.csproj
- Static Analysis (SAST) · High: REDACTED REDACTED
- Static Analysis (SAST) · High: REDACTED REDACTED
- Static Analysis (SAST) · High: watchdog-secret-into-unpinned-action REDACTED
- Static Analysis (SAST) · High: REDACTED REDACTED
- Static Analysis (SAST) · High: watchdog-secret-into-unpinned-action REDACTED
- Static Analysis (SAST) · High: watchdog-secret-into-unpinned-action REDACTED
- Static Analysis (SAST) · High: REDACTED REDACTED
- Static Analysis (SAST) · High: watchdog-secret-interpolated-into-run REDACTED
- Static Analysis (SAST) · High: REDACTED .github/workflows/dependecy-updates.yml
- Static Analysis (SAST) · High: REDACTED .github/workflows/dependecy-updates.yml
- Static Analysis (SAST) · High: REDACTED .github/workflows/dependecy-updates.yml
- Static Analysis (SAST) · High: REDACTED .github/workflows/dependecy-updates.yml
- Static Analysis (SAST) · Medium: watchdog-eol-action-major-in-workflow REDACTED
- Dependency Vulnerabilities · High CVE: AutoMapper 12.0.1 src/Infrastructure/Infrastructure.csproj
- IaC & Container Security · High IaC: DS-0002 REDACTED
- IaC & Container Security · High IaC: REDACTED REDACTED
- Supply-chain Provenance & Signing · Unpinned build actions
- Supply-chain Provenance & Signing · Workflow holding a long-lived secret is unscoped REDACTED
- Supply-chain Provenance & Signing · Workflow holding a long-lived secret is unscoped .github/workflows/dependecy-updates.yml
- Supply-chain Provenance & Signing · Secret passed as a command-line argument
- Data Protection · No data-protection/encryption
- Access Controls · No authorization
- Access Controls · No authorization src/Presentation/Endpoints/AuthorEndpoints.cs
- Access Controls · No authorization src/Presentation/Endpoints/AuthorEndpoints.cs
- Access Controls · No authorization src/Presentation/Endpoints/MovieEndpoints.cs
- Access Controls · No authorization src/Presentation/Endpoints/MovieEndpoints.cs
- Access Controls · No authorization src/Presentation/Endpoints/ReviewEndpoints.cs
- Access Controls · No authorization src/Presentation/Endpoints/ReviewEndpoints.cs
- Access Controls · No authorization src/Presentation/Endpoints/ReviewEndpoints.cs
- Access Controls · No authorization src/Presentation/Endpoints/ReviewEndpoints.cs
- Access Controls · No authorization src/Presentation/Endpoints/ReviewEndpoints.cs
- Access Controls · No authorization src/Presentation/Endpoints/VersionEndpoints.cs
- Cancellation propagation · Async method without CancellationToken: GetAuthors src/Presentation/Endpoints/AuthorEndpoints.cs
- Cancellation propagation · Async method without CancellationToken: GetAuthorById src/Presentation/Endpoints/AuthorEndpoints.cs
- Cancellation propagation · Async method without CancellationToken: GetMovies src/Presentation/Endpoints/MovieEndpoints.cs
- Cancellation propagation · Async method without CancellationToken: GetMovieById src/Presentation/Endpoints/MovieEndpoints.cs
- Cancellation propagation · Async method without CancellationToken: GetReviews src/Presentation/Endpoints/ReviewEndpoints.cs
- Cancellation propagation · Async method without CancellationToken: GetReviewById src/Presentation/Endpoints/ReviewEndpoints.cs
- Cancellation propagation · Async method without CancellationToken: CreateReview src/Presentation/Endpoints/ReviewEndpoints.cs
- Cancellation propagation · Async method without CancellationToken: UpdateReview src/Presentation/Endpoints/ReviewEndpoints.cs
- Cancellation propagation · Async method without CancellationToken: DeleteReview src/Presentation/Endpoints/ReviewEndpoints.cs
- Cancellation propagation · Async method without CancellationToken: GetVersion src/Presentation/Endpoints/VersionEndpoints.cs
- Cancellation propagation · Async method without CancellationToken: Validate src/Presentation/Filters/ValidationFilter.cs
- Captive dependencies · Captive dependency: singleton EntityFrameworkMovieReviewsRepository captures scoped MovieReviewsDbContext src/Infrastructure/Databases/MovieReviews/EntityFrameworkMovieReviewsRepository.cs
- Schema migrations · Schema created with EnsureCreated() (no migration path) src/Infrastructure/Databases/MovieReviews/EntityFrameworkMovieReviewsRepository.cs
Rebuild cost: about €8,500 · Estimate
| Cost to rebuild | €2,800 to €14,000, for 47 to 150 hours of work, under 0.1 person-years for one engineer |
|---|---|
| Difficulty of the problem | Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.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,493 lines of product code, of which 49% is declarations and boilerplate, 37% straight logic and 15% logic with branches |
| Comment lines | The estimate prices 2,319 lines. Comment lines count towards the size of 2,493 lines but aren't priced as work. |
| What it is not | Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one. |
Top priorities
Diagnosis: what the measurements show together
Architecture — module dependency graph
Architecture: which parts of the code depend on which
| uses → | 1 (global) | 2 .github.actions.pipeline-report.report | 3 CleanMinimalApi.Application | 4 CleanMinimalApi.Application.Common.Behaviours | 5 CleanMinimalApi.Application.Common.Enums | 6 CleanMinimalApi.Application.Common.Paging | 7 CleanMinimalApi.Application.Common.Telemetry | 8 CleanMinimalApi.Application.Versions.Entities | 9 CleanMinimalApi.Infrastructure | 10 CleanMinimalApi.Infrastructure.Databases.MovieReviews.Models | 11 CleanMinimalApi.Presentation.Authentication | 12 CleanMinimalApi.Presentation.Errors | 13 CleanMinimalApi.Presentation.Extensions | 14 CleanMinimalApi.Presentation.Requests | 15 .github.actions.pipeline-report | 16 CleanMinimalApi.Application.Common.Exceptions | 17 CleanMinimalApi.Application.Movies.Entities | 18 CleanMinimalApi.Application.Versions.Queries.GetVersion | 19 CleanMinimalApi.Infrastructure.Databases.MovieReviews.Configuration | 20 CleanMinimalApi.Application.Movies | 21 CleanMinimalApi.Application.Reviews.Entities | 22 CleanMinimalApi.Application.Authors.Entities | 23 CleanMinimalApi.Application.Movies.Queries.GetMovieById | 24 CleanMinimalApi.Application.Movies.Queries.GetMovies | 25 CleanMinimalApi.Application.Reviews | 26 CleanMinimalApi.Application.Authors | 27 CleanMinimalApi.Application.Reviews.Commands.DeleteReview | 28 CleanMinimalApi.Application.Reviews.Commands.UpdateReview | 29 CleanMinimalApi.Application.Reviews.Queries.GetReviewById | 30 CleanMinimalApi.Application.Reviews.Queries.GetReviews | 31 CleanMinimalApi.Application.Reviews.Queries.GetReviewsForAuthors | 32 CleanMinimalApi.Application.Reviews.Queries.GetReviewsForMovies | 33 CleanMinimalApi.Infrastructure.Databases.MovieReviews.Mapping | 34 CleanMinimalApi.Presentation.Endpoints | 35 CleanMinimalApi.Presentation.Serialization | 36 CleanMinimalApi.Application.Authors.Queries.GetAuthorById | 37 CleanMinimalApi.Application.Authors.Queries.GetAuthors | 38 CleanMinimalApi.Application.Reviews.Commands.CreateReview | 39 CleanMinimalApi.Infrastructure.Databases.MovieReviews | 40 CleanMinimalApi.Infrastructure.Databases.MovieReviews.Extensions |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 (global) | ||||||||||||||||||||||||||||||||||||||||
| 2 .github.actions.pipeline-report.report | ||||||||||||||||||||||||||||||||||||||||
| 3 CleanMinimalApi.Application | ||||||||||||||||||||||||||||||||||||||||
| 4 CleanMinimalApi.Application.Common.Behaviours | ||||||||||||||||||||||||||||||||||||||||
| 5 CleanMinimalApi.Application.Common.Enums | ||||||||||||||||||||||||||||||||||||||||
| 6 CleanMinimalApi.Application.Common.Paging | ||||||||||||||||||||||||||||||||||||||||
| 7 CleanMinimalApi.Application.Common.Telemetry | ||||||||||||||||||||||||||||||||||||||||
| 8 CleanMinimalApi.Application.Versions.Entities | ||||||||||||||||||||||||||||||||||||||||
| 9 CleanMinimalApi.Infrastructure | ||||||||||||||||||||||||||||||||||||||||
| 10 CleanMinimalApi.Infrastructure.Databases.MovieReviews.Models | ||||||||||||||||||||||||||||||||||||||||
| 11 CleanMinimalApi.Presentation.Authentication | ||||||||||||||||||||||||||||||||||||||||
| 12 CleanMinimalApi.Presentation.Errors | ||||||||||||||||||||||||||||||||||||||||
| 13 CleanMinimalApi.Presentation.Extensions | ||||||||||||||||||||||||||||||||||||||||
| 14 CleanMinimalApi.Presentation.Requests | ||||||||||||||||||||||||||||||||||||||||
| 15 .github.actions.pipeline-report | 3 | |||||||||||||||||||||||||||||||||||||||
| 16 CleanMinimalApi.Application.Common.Exceptions | 1 | |||||||||||||||||||||||||||||||||||||||
| 17 CleanMinimalApi.Application.Movies.Entities | 1 | |||||||||||||||||||||||||||||||||||||||
| 18 CleanMinimalApi.Application.Versions.Queries.GetVersion | 1 | |||||||||||||||||||||||||||||||||||||||
| 19 CleanMinimalApi.Infrastructure.Databases.MovieReviews.Configuration | 3 | |||||||||||||||||||||||||||||||||||||||
| 20 CleanMinimalApi.Application.Movies | 2 | 2 | ||||||||||||||||||||||||||||||||||||||
| 21 CleanMinimalApi.Application.Reviews.Entities | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 22 CleanMinimalApi.Application.Authors.Entities | 1 | |||||||||||||||||||||||||||||||||||||||
| 23 CleanMinimalApi.Application.Movies.Queries.GetMovieById | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 24 CleanMinimalApi.Application.Movies.Queries.GetMovies | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 25 CleanMinimalApi.Application.Reviews | 2 | 1 | ||||||||||||||||||||||||||||||||||||||
| 26 CleanMinimalApi.Application.Authors | 2 | 2 | ||||||||||||||||||||||||||||||||||||||
| 27 CleanMinimalApi.Application.Reviews.Commands.DeleteReview | 1 | |||||||||||||||||||||||||||||||||||||||
| 28 CleanMinimalApi.Application.Reviews.Commands.UpdateReview | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 29 CleanMinimalApi.Application.Reviews.Queries.GetReviewById | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 30 CleanMinimalApi.Application.Reviews.Queries.GetReviews | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 31 CleanMinimalApi.Application.Reviews.Queries.GetReviewsForAuthors | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 32 CleanMinimalApi.Application.Reviews.Queries.GetReviewsForMovies | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 33 CleanMinimalApi.Infrastructure.Databases.MovieReviews.Mapping | 3 | 2 | 1 | 2 | ||||||||||||||||||||||||||||||||||||
| 34 CleanMinimalApi.Presentation.Endpoints | 3 | 1 | 2 | 2 | 1 | 2 | ||||||||||||||||||||||||||||||||||
| 35 CleanMinimalApi.Presentation.Serialization | 1 | 1 | 2 | 3 | 1 | 3 | ||||||||||||||||||||||||||||||||||
| 36 CleanMinimalApi.Application.Authors.Queries.GetAuthorById | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 37 CleanMinimalApi.Application.Authors.Queries.GetAuthors | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 38 CleanMinimalApi.Application.Reviews.Commands.CreateReview | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 39 CleanMinimalApi.Infrastructure.Databases.MovieReviews | 2 | 3 | 2 | 1 | 1 | 2 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||
| 40 CleanMinimalApi.Infrastructure.Databases.MovieReviews.Extensions | 1 |
15→2 .github.actions.pipeline-report uses .github.actions.pipeline-report.report✕
- Connections
- 3 pairs of types, where a type in .github.actions.pipeline-report uses a type in .github.actions.pipeline-report.report.
- The types involved
.github.actions.pipeline-report.report→.github.actions.pipeline-report.report.Coverage.github.actions.pipeline-report.report→.github.actions.pipeline-report.report.Stage.github.actions.pipeline-report.report→.github.actions.pipeline-report.report.TestResults
- Direction
- .github.actions.pipeline-report uses .github.actions.pipeline-report.report, so a change to .github.actions.pipeline-report.report can break .github.actions.pipeline-report, while a change to .github.actions.pipeline-report can't break .github.actions.pipeline-report.report.
- Position
- Below the diagonal: .github.actions.pipeline-report uses a module listed above it, which is the healthy direction.
16→5 CleanMinimalApi.Application.Common.Exceptions uses CleanMinimalApi.Application.Common.Enums✕
- Connections
- 1 pair of types, where a type in CleanMinimalApi.Application.Common.Exceptions uses a type in CleanMinimalApi.Application.Common.Enums.
- The types involved
CleanMinimalApi.Application.Common.Exceptions.NotFoundException→CleanMinimalApi.Application.Common.Enums.EntityType
- Direction
- CleanMinimalApi.Application.Common.Exceptions uses CleanMinimalApi.Application.Common.Enums, so a change to CleanMinimalApi.Application.Common.Enums can break CleanMinimalApi.Application.Common.Exceptions, while a change to CleanMinimalApi.Application.Common.Exceptions can't break CleanMinimalApi.Application.Common.Enums.
- Position
- Below the diagonal: CleanMinimalApi.Application.Common.Exceptions uses a module listed above it, which is the healthy direction.
17→21 CleanMinimalApi.Application.Movies.Entities uses CleanMinimalApi.Application.Reviews.Entities part of a loop✕
- Connections
- 1 pair of types, where a type in CleanMinimalApi.Application.Movies.Entities uses a type in CleanMinimalApi.Application.Reviews.Entities.
- The types involved
CleanMinimalApi.Application.Movies.Entities.Movie→CleanMinimalApi.Application.Reviews.Entities.Review
- Direction
- CleanMinimalApi.Application.Movies.Entities uses CleanMinimalApi.Application.Reviews.Entities, so a change to CleanMinimalApi.Application.Reviews.Entities can break CleanMinimalApi.Application.Movies.Entities, while a change to CleanMinimalApi.Application.Movies.Entities can't break CleanMinimalApi.Application.Reviews.Entities.
- 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.
18→8 CleanMinimalApi.Application.Versions.Queries.GetVersion uses CleanMinimalApi.Application.Versions.Entities✕
- Connections
- 1 pair of types, where a type in CleanMinimalApi.Application.Versions.Queries.GetVersion uses a type in CleanMinimalApi.Application.Versions.Entities.
- The types involved
CleanMinimalApi.Application.Versions.Queries.GetVersion.GetVersionHandler→CleanMinimalApi.Application.Versions.Entities.VersionInfo
- Direction
- CleanMinimalApi.Application.Versions.Queries.GetVersion uses CleanMinimalApi.Application.Versions.Entities, so a change to CleanMinimalApi.Application.Versions.Entities can break CleanMinimalApi.Application.Versions.Queries.GetVersion, while a change to CleanMinimalApi.Application.Versions.Queries.GetVersion can't break CleanMinimalApi.Application.Versions.Entities.
- Position
- Below the diagonal: CleanMinimalApi.Application.Versions.Queries.GetVersion uses a module listed above it, which is the healthy direction.
19→10 CleanMinimalApi.Infrastructure.Databases.MovieReviews.Configuration uses CleanMinimalApi.Infrastructure.Databases.MovieReviews.Models✕
- Connections
- 3 pairs of types, where a type in CleanMinimalApi.Infrastructure.Databases.MovieReviews.Configuration uses a type in CleanMinimalApi.Infrastructure.Databases.MovieReviews.Models.
- The types involved
CleanMinimalApi.Infrastructure.Databases.MovieReviews.Configuration.AuthorConfiguration→CleanMinimalApi.Infrastructure.Databases.MovieReviews.Models.AuthorCleanMinimalApi.Infrastructure.Databases.MovieReviews.Configuration.MovieConfiguration→CleanMinimalApi.Infrastructure.Databases.MovieReviews.Models.MovieCleanMinimalApi.Infrastructure.Databases.MovieReviews.Configuration.ReviewConfiguration→CleanMinimalApi.Infrastructure.Databases.MovieReviews.Models.Review
- Direction
- CleanMinimalApi.Infrastructure.Databases.MovieReviews.Configuration uses CleanMinimalApi.Infrastructure.Databases.MovieReviews.Models, so a change to CleanMinimalApi.Infrastructure.Databases.MovieReviews.Models can break CleanMinimalApi.Infrastructure.Databases.MovieReviews.Configuration, while a change to CleanMinimalApi.Infrastructure.Databases.MovieReviews.Configuration can't break CleanMinimalApi.Infrastructure.Databases.MovieReviews.Models.
- Position
- Below the diagonal: CleanMinimalApi.Infrastructure.Databases.MovieReviews.Configuration uses a module listed above it, which is the healthy direction.
20→6 CleanMinimalApi.Application.Movies uses CleanMinimalApi.Application.Common.Paging✕
- Connections
- 2 pairs of types, where a type in CleanMinimalApi.Application.Movies uses a type in CleanMinimalApi.Application.Common.Paging.
- The types involved
CleanMinimalApi.Application.Movies.IMoviesRepository→CleanMinimalApi.Application.Common.Paging.PageCleanMinimalApi.Application.Movies.IMoviesRepository→CleanMinimalApi.Application.Common.Paging.PageRequest
- Direction
- CleanMinimalApi.Application.Movies uses CleanMinimalApi.Application.Common.Paging, so a change to CleanMinimalApi.Application.Common.Paging can break CleanMinimalApi.Application.Movies, while a change to CleanMinimalApi.Application.Movies can't break CleanMinimalApi.Application.Common.Paging.
- Position
- Below the diagonal: CleanMinimalApi.Application.Movies uses a module listed above it, which is the healthy direction.
20→17 CleanMinimalApi.Application.Movies uses CleanMinimalApi.Application.Movies.Entities✕
- Connections
- 2 pairs of types, where a type in CleanMinimalApi.Application.Movies uses a type in CleanMinimalApi.Application.Movies.Entities.
- The types involved
CleanMinimalApi.Application.Movies.IMoviesRepository→CleanMinimalApi.Application.Movies.Entities.MovieCleanMinimalApi.Application.Movies.IMoviesRepository→CleanMinimalApi.Application.Movies.Entities.MovieSummary
- Direction
- CleanMinimalApi.Application.Movies uses CleanMinimalApi.Application.Movies.Entities, so a change to CleanMinimalApi.Application.Movies.Entities can break CleanMinimalApi.Application.Movies, while a change to CleanMinimalApi.Application.Movies can't break CleanMinimalApi.Application.Movies.Entities.
- Position
- Below the diagonal: CleanMinimalApi.Application.Movies uses a module listed above it, which is the healthy direction.
21→17 CleanMinimalApi.Application.Reviews.Entities uses CleanMinimalApi.Application.Movies.Entities✕
- Connections
- 1 pair of types, where a type in CleanMinimalApi.Application.Reviews.Entities uses a type in CleanMinimalApi.Application.Movies.Entities.
- The types involved
CleanMinimalApi.Application.Reviews.Entities.Review→CleanMinimalApi.Application.Movies.Entities.ReviewedMovie
- Direction
- CleanMinimalApi.Application.Reviews.Entities uses CleanMinimalApi.Application.Movies.Entities, so a change to CleanMinimalApi.Application.Movies.Entities can break CleanMinimalApi.Application.Reviews.Entities, while a change to CleanMinimalApi.Application.Reviews.Entities can't break CleanMinimalApi.Application.Movies.Entities.
- Position
- Below the diagonal: CleanMinimalApi.Application.Reviews.Entities uses a module listed above it, which is the healthy direction.
21→22 CleanMinimalApi.Application.Reviews.Entities uses CleanMinimalApi.Application.Authors.Entities part of a loop✕
- Connections
- 1 pair of types, where a type in CleanMinimalApi.Application.Reviews.Entities uses a type in CleanMinimalApi.Application.Authors.Entities.
- The types involved
CleanMinimalApi.Application.Reviews.Entities.Review→CleanMinimalApi.Application.Authors.Entities.ReviewAuthor
- Direction
- CleanMinimalApi.Application.Reviews.Entities uses CleanMinimalApi.Application.Authors.Entities, so a change to CleanMinimalApi.Application.Authors.Entities can break CleanMinimalApi.Application.Reviews.Entities, while a change to CleanMinimalApi.Application.Reviews.Entities can't break CleanMinimalApi.Application.Authors.Entities.
- 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.
22→21 CleanMinimalApi.Application.Authors.Entities uses CleanMinimalApi.Application.Reviews.Entities✕
- Connections
- 1 pair of types, where a type in CleanMinimalApi.Application.Authors.Entities uses a type in CleanMinimalApi.Application.Reviews.Entities.
- The types involved
CleanMinimalApi.Application.Authors.Entities.Author→CleanMinimalApi.Application.Reviews.Entities.Review
- Direction
- CleanMinimalApi.Application.Authors.Entities uses CleanMinimalApi.Application.Reviews.Entities, so a change to CleanMinimalApi.Application.Reviews.Entities can break CleanMinimalApi.Application.Authors.Entities, while a change to CleanMinimalApi.Application.Authors.Entities can't break CleanMinimalApi.Application.Reviews.Entities.
- Position
- Below the diagonal: CleanMinimalApi.Application.Authors.Entities uses a module listed above it, which is the healthy direction.
23→17 CleanMinimalApi.Application.Movies.Queries.GetMovieById uses CleanMinimalApi.Application.Movies.Entities✕
- Connections
- 1 pair of types, where a type in CleanMinimalApi.Application.Movies.Queries.GetMovieById uses a type in CleanMinimalApi.Application.Movies.Entities.
- The types involved
CleanMinimalApi.Application.Movies.Queries.GetMovieById.GetMovieByIdHandler→CleanMinimalApi.Application.Movies.Entities.Movie
- Direction
- CleanMinimalApi.Application.Movies.Queries.GetMovieById uses CleanMinimalApi.Application.Movies.Entities, so a change to CleanMinimalApi.Application.Movies.Entities can break CleanMinimalApi.Application.Movies.Queries.GetMovieById, while a change to CleanMinimalApi.Application.Movies.Queries.GetMovieById can't break CleanMinimalApi.Application.Movies.Entities.
- Position
- Below the diagonal: CleanMinimalApi.Application.Movies.Queries.GetMovieById uses a module listed above it, which is the healthy direction.
23→20 CleanMinimalApi.Application.Movies.Queries.GetMovieById uses CleanMinimalApi.Application.Movies✕
- Connections
- 1 pair of types, where a type in CleanMinimalApi.Application.Movies.Queries.GetMovieById uses a type in CleanMinimalApi.Application.Movies.
- The types involved
CleanMinimalApi.Application.Movies.Queries.GetMovieById.GetMovieByIdHandler→CleanMinimalApi.Application.Movies.IMoviesRepository
- Direction
- CleanMinimalApi.Application.Movies.Queries.GetMovieById uses CleanMinimalApi.Application.Movies, so a change to CleanMinimalApi.Application.Movies can break CleanMinimalApi.Application.Movies.Queries.GetMovieById, while a change to CleanMinimalApi.Application.Movies.Queries.GetMovieById can't break CleanMinimalApi.Application.Movies.
- Position
- Below the diagonal: CleanMinimalApi.Application.Movies.Queries.GetMovieById uses a module listed above it, which is the healthy direction.
24→6 CleanMinimalApi.Application.Movies.Queries.GetMovies uses CleanMinimalApi.Application.Common.Paging✕
- Connections
- 1 pair of types, where a type in CleanMinimalApi.Application.Movies.Queries.GetMovies uses a type in CleanMinimalApi.Application.Common.Paging.
- The types involved
CleanMinimalApi.Application.Movies.Queries.GetMovies.GetMoviesHandler→CleanMinimalApi.Application.Common.Paging.Page
- Direction
- CleanMinimalApi.Application.Movies.Queries.GetMovies uses CleanMinimalApi.Application.Common.Paging, so a change to CleanMinimalApi.Application.Common.Paging can break CleanMinimalApi.Application.Movies.Queries.GetMovies, while a change to CleanMinimalApi.Application.Movies.Queries.GetMovies can't break CleanMinimalApi.Application.Common.Paging.
- Position
- Below the diagonal: CleanMinimalApi.Application.Movies.Queries.GetMovies uses a module listed above it, which is the healthy direction.
24→17 CleanMinimalApi.Application.Movies.Queries.GetMovies uses CleanMinimalApi.Application.Movies.Entities✕
- Connections
- 1 pair of types, where a type in CleanMinimalApi.Application.Movies.Queries.GetMovies uses a type in CleanMinimalApi.Application.Movies.Entities.
- The types involved
CleanMinimalApi.Application.Movies.Queries.GetMovies.GetMoviesHandler→CleanMinimalApi.Application.Movies.Entities.MovieSummary
- Direction
- CleanMinimalApi.Application.Movies.Queries.GetMovies uses CleanMinimalApi.Application.Movies.Entities, so a change to CleanMinimalApi.Application.Movies.Entities can break CleanMinimalApi.Application.Movies.Queries.GetMovies, while a change to CleanMinimalApi.Application.Movies.Queries.GetMovies can't break CleanMinimalApi.Application.Movies.Entities.
- Position
- Below the diagonal: CleanMinimalApi.Application.Movies.Queries.GetMovies uses a module listed above it, which is the healthy direction.
24→20 CleanMinimalApi.Application.Movies.Queries.GetMovies uses CleanMinimalApi.Application.Movies✕
- Connections
- 1 pair of types, where a type in CleanMinimalApi.Application.Movies.Queries.GetMovies uses a type in CleanMinimalApi.Application.Movies.
- The types involved
CleanMinimalApi.Application.Movies.Queries.GetMovies.GetMoviesHandler→CleanMinimalApi.Application.Movies.IMoviesRepository
- Direction
- CleanMinimalApi.Application.Movies.Queries.GetMovies uses CleanMinimalApi.Application.Movies, so a change to CleanMinimalApi.Application.Movies can break CleanMinimalApi.Application.Movies.Queries.GetMovies, while a change to CleanMinimalApi.Application.Movies.Queries.GetMovies can't break CleanMinimalApi.Application.Movies.
- Position
- Below the diagonal: CleanMinimalApi.Application.Movies.Queries.GetMovies uses a module listed above it, which is the healthy direction.
25→6 CleanMinimalApi.Application.Reviews uses CleanMinimalApi.Application.Common.Paging✕
- Connections
- 2 pairs of types, where a type in CleanMinimalApi.Application.Reviews uses a type in CleanMinimalApi.Application.Common.Paging.
- The types involved
CleanMinimalApi.Application.Reviews.IReviewsRepository→CleanMinimalApi.Application.Common.Paging.PageCleanMinimalApi.Application.Reviews.IReviewsRepository→CleanMinimalApi.Application.Common.Paging.PageRequest
- Direction
- CleanMinimalApi.Application.Reviews uses CleanMinimalApi.Application.Common.Paging, so a change to CleanMinimalApi.Application.Common.Paging can break CleanMinimalApi.Application.Reviews, while a change to CleanMinimalApi.Application.Reviews can't break CleanMinimalApi.Application.Common.Paging.
- Position
- Below the diagonal: CleanMinimalApi.Application.Reviews uses a module listed above it, which is the healthy direction.
25→21 CleanMinimalApi.Application.Reviews uses CleanMinimalApi.Application.Reviews.Entities✕
- Connections
- 1 pair of types, where a type in CleanMinimalApi.Application.Reviews uses a type in CleanMinimalApi.Application.Reviews.Entities.
- The types involved
CleanMinimalApi.Application.Reviews.IReviewsRepository→CleanMinimalApi.Application.Reviews.Entities.Review
- Direction
- CleanMinimalApi.Application.Reviews uses CleanMinimalApi.Application.Reviews.Entities, so a change to CleanMinimalApi.Application.Reviews.Entities can break CleanMinimalApi.Application.Reviews, while a change to CleanMinimalApi.Application.Reviews can't break CleanMinimalApi.Application.Reviews.Entities.
- Position
- Below the diagonal: CleanMinimalApi.Application.Reviews uses a module listed above it, which is the healthy direction.
26→6 CleanMinimalApi.Application.Authors uses CleanMinimalApi.Application.Common.Paging✕
- Connections
- 2 pairs of types, where a type in CleanMinimalApi.Application.Authors uses a type in CleanMinimalApi.Application.Common.Paging.
- The types involved
CleanMinimalApi.Application.Authors.IAuthorsRepository→CleanMinimalApi.Application.Common.Paging.PageCleanMinimalApi.Application.Authors.IAuthorsRepository→CleanMinimalApi.Application.Common.Paging.PageRequest
- Direction
- CleanMinimalApi.Application.Authors uses CleanMinimalApi.Application.Common.Paging, so a change to CleanMinimalApi.Application.Common.Paging can break CleanMinimalApi.Application.Authors, while a change to CleanMinimalApi.Application.Authors can't break CleanMinimalApi.Application.Common.Paging.
- Position
- Below the diagonal: CleanMinimalApi.Application.Authors uses a module listed above it, which is the healthy direction.
26→22 CleanMinimalApi.Application.Authors uses CleanMinimalApi.Application.Authors.Entities✕
- Connections
- 2 pairs of types, where a type in CleanMinimalApi.Application.Authors uses a type in CleanMinimalApi.Application.Authors.Entities.
- The types involved
CleanMinimalApi.Application.Authors.IAuthorsRepository→CleanMinimalApi.Application.Authors.Entities.AuthorCleanMinimalApi.Application.Authors.IAuthorsRepository→CleanMinimalApi.Application.Authors.Entities.AuthorSummary
- Direction
- CleanMinimalApi.Application.Authors uses CleanMinimalApi.Application.Authors.Entities, so a change to CleanMinimalApi.Application.Authors.Entities can break CleanMinimalApi.Application.Authors, while a change to CleanMinimalApi.Application.Authors can't break CleanMinimalApi.Application.Authors.Entities.
- Position
- Below the diagonal: CleanMinimalApi.Application.Authors uses a module listed above it, which is the healthy direction.
27→25 CleanMinimalApi.Application.Reviews.Commands.DeleteReview uses CleanMinimalApi.Application.Reviews✕
- Connections
- 1 pair of types, where a type in CleanMinimalApi.Application.Reviews.Commands.DeleteReview uses a type in CleanMinimalApi.Application.Reviews.
- The types involved
CleanMinimalApi.Application.Reviews.Commands.DeleteReview.DeleteReviewHandler→CleanMinimalApi.Application.Reviews.IReviewsRepository
- Direction
- CleanMinimalApi.Application.Reviews.Commands.DeleteReview uses CleanMinimalApi.Application.Reviews, so a change to CleanMinimalApi.Application.Reviews can break CleanMinimalApi.Application.Reviews.Commands.DeleteReview, while a change to CleanMinimalApi.Application.Reviews.Commands.DeleteReview can't break CleanMinimalApi.Application.Reviews.
- Position
- Below the diagonal: CleanMinimalApi.Application.Reviews.Commands.DeleteReview uses a module listed above it, which is the healthy direction.
28→21 CleanMinimalApi.Application.Reviews.Commands.UpdateReview uses CleanMinimalApi.Application.Reviews.Entities✕
- Connections
- 1 pair of types, where a type in CleanMinimalApi.Application.Reviews.Commands.UpdateReview uses a type in CleanMinimalApi.Application.Reviews.Entities.
- The types involved
CleanMinimalApi.Application.Reviews.Commands.UpdateReview.UpdateReviewHandler→CleanMinimalApi.Application.Reviews.Entities.Review
- Direction
- CleanMinimalApi.Application.Reviews.Commands.UpdateReview uses CleanMinimalApi.Application.Reviews.Entities, so a change to CleanMinimalApi.Application.Reviews.Entities can break CleanMinimalApi.Application.Reviews.Commands.UpdateReview, while a change to CleanMinimalApi.Application.Reviews.Commands.UpdateReview can't break CleanMinimalApi.Application.Reviews.Entities.
- Position
- Below the diagonal: CleanMinimalApi.Application.Reviews.Commands.UpdateReview uses a module listed above it, which is the healthy direction.
28→25 CleanMinimalApi.Application.Reviews.Commands.UpdateReview uses CleanMinimalApi.Application.Reviews✕
- Connections
- 1 pair of types, where a type in CleanMinimalApi.Application.Reviews.Commands.UpdateReview uses a type in CleanMinimalApi.Application.Reviews.
- The types involved
CleanMinimalApi.Application.Reviews.Commands.UpdateReview.UpdateReviewHandler→CleanMinimalApi.Application.Reviews.IReviewsRepository
- Direction
- CleanMinimalApi.Application.Reviews.Commands.UpdateReview uses CleanMinimalApi.Application.Reviews, so a change to CleanMinimalApi.Application.Reviews can break CleanMinimalApi.Application.Reviews.Commands.UpdateReview, while a change to CleanMinimalApi.Application.Reviews.Commands.UpdateReview can't break CleanMinimalApi.Application.Reviews.
- Position
- Below the diagonal: CleanMinimalApi.Application.Reviews.Commands.UpdateReview uses a module listed above it, which is the healthy direction.
29→21 CleanMinimalApi.Application.Reviews.Queries.GetReviewById uses CleanMinimalApi.Application.Reviews.Entities✕
- Connections
- 1 pair of types, where a type in CleanMinimalApi.Application.Reviews.Queries.GetReviewById uses a type in CleanMinimalApi.Application.Reviews.Entities.
- The types involved
CleanMinimalApi.Application.Reviews.Queries.GetReviewById.GetReviewByIdHandler→CleanMinimalApi.Application.Reviews.Entities.Review
- Direction
- CleanMinimalApi.Application.Reviews.Queries.GetReviewById uses CleanMinimalApi.Application.Reviews.Entities, so a change to CleanMinimalApi.Application.Reviews.Entities can break CleanMinimalApi.Application.Reviews.Queries.GetReviewById, while a change to CleanMinimalApi.Application.Reviews.Queries.GetReviewById can't break CleanMinimalApi.Application.Reviews.Entities.
- Position
- Below the diagonal: CleanMinimalApi.Application.Reviews.Queries.GetReviewById uses a module listed above it, which is the healthy direction.
29→25 CleanMinimalApi.Application.Reviews.Queries.GetReviewById uses CleanMinimalApi.Application.Reviews✕
- Connections
- 1 pair of types, where a type in CleanMinimalApi.Application.Reviews.Queries.GetReviewById uses a type in CleanMinimalApi.Application.Reviews.
- The types involved
CleanMinimalApi.Application.Reviews.Queries.GetReviewById.GetReviewByIdHandler→CleanMinimalApi.Application.Reviews.IReviewsRepository
- Direction
- CleanMinimalApi.Application.Reviews.Queries.GetReviewById uses CleanMinimalApi.Application.Reviews, so a change to CleanMinimalApi.Application.Reviews can break CleanMinimalApi.Application.Reviews.Queries.GetReviewById, while a change to CleanMinimalApi.Application.Reviews.Queries.GetReviewById can't break CleanMinimalApi.Application.Reviews.
- Position
- Below the diagonal: CleanMinimalApi.Application.Reviews.Queries.GetReviewById uses a module listed above it, which is the healthy direction.
30→6 CleanMinimalApi.Application.Reviews.Queries.GetReviews uses CleanMinimalApi.Application.Common.Paging✕
- Connections
- 1 pair of types, where a type in CleanMinimalApi.Application.Reviews.Queries.GetReviews uses a type in CleanMinimalApi.Application.Common.Paging.
- The types involved
CleanMinimalApi.Application.Reviews.Queries.GetReviews.GetReviewsHandler→CleanMinimalApi.Application.Common.Paging.Page
- Direction
- CleanMinimalApi.Application.Reviews.Queries.GetReviews uses CleanMinimalApi.Application.Common.Paging, so a change to CleanMinimalApi.Application.Common.Paging can break CleanMinimalApi.Application.Reviews.Queries.GetReviews, while a change to CleanMinimalApi.Application.Reviews.Queries.GetReviews can't break CleanMinimalApi.Application.Common.Paging.
- Position
- Below the diagonal: CleanMinimalApi.Application.Reviews.Queries.GetReviews uses a module listed above it, which is the healthy direction.
30→21 CleanMinimalApi.Application.Reviews.Queries.GetReviews uses CleanMinimalApi.Application.Reviews.Entities✕
- Connections
- 1 pair of types, where a type in CleanMinimalApi.Application.Reviews.Queries.GetReviews uses a type in CleanMinimalApi.Application.Reviews.Entities.
- The types involved
CleanMinimalApi.Application.Reviews.Queries.GetReviews.GetReviewsHandler→CleanMinimalApi.Application.Reviews.Entities.Review
- Direction
- CleanMinimalApi.Application.Reviews.Queries.GetReviews uses CleanMinimalApi.Application.Reviews.Entities, so a change to CleanMinimalApi.Application.Reviews.Entities can break CleanMinimalApi.Application.Reviews.Queries.GetReviews, while a change to CleanMinimalApi.Application.Reviews.Queries.GetReviews can't break CleanMinimalApi.Application.Reviews.Entities.
- Position
- Below the diagonal: CleanMinimalApi.Application.Reviews.Queries.GetReviews uses a module listed above it, which is the healthy direction.
30→25 CleanMinimalApi.Application.Reviews.Queries.GetReviews uses CleanMinimalApi.Application.Reviews✕
- Connections
- 1 pair of types, where a type in CleanMinimalApi.Application.Reviews.Queries.GetReviews uses a type in CleanMinimalApi.Application.Reviews.
- The types involved
CleanMinimalApi.Application.Reviews.Queries.GetReviews.GetReviewsHandler→CleanMinimalApi.Application.Reviews.IReviewsRepository
- Direction
- CleanMinimalApi.Application.Reviews.Queries.GetReviews uses CleanMinimalApi.Application.Reviews, so a change to CleanMinimalApi.Application.Reviews can break CleanMinimalApi.Application.Reviews.Queries.GetReviews, while a change to CleanMinimalApi.Application.Reviews.Queries.GetReviews can't break CleanMinimalApi.Application.Reviews.
- Position
- Below the diagonal: CleanMinimalApi.Application.Reviews.Queries.GetReviews uses a module listed above it, which is the healthy direction.
31→21 CleanMinimalApi.Application.Reviews.Queries.GetReviewsForAuthors uses CleanMinimalApi.Application.Reviews.Entities✕
- Connections
- 1 pair of types, where a type in CleanMinimalApi.Application.Reviews.Queries.GetReviewsForAuthors uses a type in CleanMinimalApi.Application.Reviews.Entities.
- The types involved
CleanMinimalApi.Application.Reviews.Queries.GetReviewsForAuthors.GetReviewsForAuthorsHandler→CleanMinimalApi.Application.Reviews.Entities.Review
- Direction
- CleanMinimalApi.Application.Reviews.Queries.GetReviewsForAuthors uses CleanMinimalApi.Application.Reviews.Entities, so a change to CleanMinimalApi.Application.Reviews.Entities can break CleanMinimalApi.Application.Reviews.Queries.GetReviewsForAuthors, while a change to CleanMinimalApi.Application.Reviews.Queries.GetReviewsForAuthors can't break CleanMinimalApi.Application.Reviews.Entities.
- Position
- Below the diagonal: CleanMinimalApi.Application.Reviews.Queries.GetReviewsForAuthors uses a module listed above it, which is the healthy direction.
31→25 CleanMinimalApi.Application.Reviews.Queries.GetReviewsForAuthors uses CleanMinimalApi.Application.Reviews✕
- Connections
- 1 pair of types, where a type in CleanMinimalApi.Application.Reviews.Queries.GetReviewsForAuthors uses a type in CleanMinimalApi.Application.Reviews.
- The types involved
CleanMinimalApi.Application.Reviews.Queries.GetReviewsForAuthors.GetReviewsForAuthorsHandler→CleanMinimalApi.Application.Reviews.IReviewsRepository
- Direction
- CleanMinimalApi.Application.Reviews.Queries.GetReviewsForAuthors uses CleanMinimalApi.Application.Reviews, so a change to CleanMinimalApi.Application.Reviews can break CleanMinimalApi.Application.Reviews.Queries.GetReviewsForAuthors, while a change to CleanMinimalApi.Application.Reviews.Queries.GetReviewsForAuthors can't break CleanMinimalApi.Application.Reviews.
- Position
- Below the diagonal: CleanMinimalApi.Application.Reviews.Queries.GetReviewsForAuthors uses a module listed above it, which is the healthy direction.
32→21 CleanMinimalApi.Application.Reviews.Queries.GetReviewsForMovies uses CleanMinimalApi.Application.Reviews.Entities✕
- Connections
- 1 pair of types, where a type in CleanMinimalApi.Application.Reviews.Queries.GetReviewsForMovies uses a type in CleanMinimalApi.Application.Reviews.Entities.
- The types involved
CleanMinimalApi.Application.Reviews.Queries.GetReviewsForMovies.GetReviewsForMoviesHandler→CleanMinimalApi.Application.Reviews.Entities.Review
- Direction
- CleanMinimalApi.Application.Reviews.Queries.GetReviewsForMovies uses CleanMinimalApi.Application.Reviews.Entities, so a change to CleanMinimalApi.Application.Reviews.Entities can break CleanMinimalApi.Application.Reviews.Queries.GetReviewsForMovies, while a change to CleanMinimalApi.Application.Reviews.Queries.GetReviewsForMovies can't break CleanMinimalApi.Application.Reviews.Entities.
- Position
- Below the diagonal: CleanMinimalApi.Application.Reviews.Queries.GetReviewsForMovies uses a module listed above it, which is the healthy direction.
32→25 CleanMinimalApi.Application.Reviews.Queries.GetReviewsForMovies uses CleanMinimalApi.Application.Reviews✕
- Connections
- 1 pair of types, where a type in CleanMinimalApi.Application.Reviews.Queries.GetReviewsForMovies uses a type in CleanMinimalApi.Application.Reviews.
- The types involved
CleanMinimalApi.Application.Reviews.Queries.GetReviewsForMovies.GetReviewsForMoviesHandler→CleanMinimalApi.Application.Reviews.IReviewsRepository
- Direction
- CleanMinimalApi.Application.Reviews.Queries.GetReviewsForMovies uses CleanMinimalApi.Application.Reviews, so a change to CleanMinimalApi.Application.Reviews can break CleanMinimalApi.Application.Reviews.Queries.GetReviewsForMovies, while a change to CleanMinimalApi.Application.Reviews.Queries.GetReviewsForMovies can't break CleanMinimalApi.Application.Reviews.
- Position
- Below the diagonal: CleanMinimalApi.Application.Reviews.Queries.GetReviewsForMovies uses a module listed above it, which is the healthy direction.
33→10 CleanMinimalApi.Infrastructure.Databases.MovieReviews.Mapping uses CleanMinimalApi.Infrastructure.Databases.MovieReviews.Models✕
- Connections
- 3 pairs of types, where a type in CleanMinimalApi.Infrastructure.Databases.MovieReviews.Mapping uses a type in CleanMinimalApi.Infrastructure.Databases.MovieReviews.Models.
- The types involved
CleanMinimalApi.Infrastructure.Databases.MovieReviews.Mapping.MovieReviewsMapper→CleanMinimalApi.Infrastructure.Databases.MovieReviews.Models.AuthorCleanMinimalApi.Infrastructure.Databases.MovieReviews.Mapping.MovieReviewsMapper→CleanMinimalApi.Infrastructure.Databases.MovieReviews.Models.MovieCleanMinimalApi.Infrastructure.Databases.MovieReviews.Mapping.MovieReviewsMapper→CleanMinimalApi.Infrastructure.Databases.MovieReviews.Models.Review
- Direction
- CleanMinimalApi.Infrastructure.Databases.MovieReviews.Mapping uses CleanMinimalApi.Infrastructure.Databases.MovieReviews.Models, so a change to CleanMinimalApi.Infrastructure.Databases.MovieReviews.Models can break CleanMinimalApi.Infrastructure.Databases.MovieReviews.Mapping, while a change to CleanMinimalApi.Infrastructure.Databases.MovieReviews.Mapping can't break CleanMinimalApi.Infrastructure.Databases.MovieReviews.Models.
- Position
- Below the diagonal: CleanMinimalApi.Infrastructure.Databases.MovieReviews.Mapping uses a module listed above it, which is the healthy direction.
33→17 CleanMinimalApi.Infrastructure.Databases.MovieReviews.Mapping uses CleanMinimalApi.Application.Movies.Entities✕
- Connections
- 2 pairs of types, where a type in CleanMinimalApi.Infrastructure.Databases.MovieReviews.Mapping uses a type in CleanMinimalApi.Application.Movies.Entities.
- The types involved
CleanMinimalApi.Infrastructure.Databases.MovieReviews.Mapping.MovieReviewsMapper→CleanMinimalApi.Application.Movies.Entities.MovieCleanMinimalApi.Infrastructure.Databases.MovieReviews.Mapping.MovieReviewsMapper→CleanMinimalApi.Application.Movies.Entities.ReviewedMovie
- Direction
- CleanMinimalApi.Infrastructure.Databases.MovieReviews.Mapping uses CleanMinimalApi.Application.Movies.Entities, so a change to CleanMinimalApi.Application.Movies.Entities can break CleanMinimalApi.Infrastructure.Databases.MovieReviews.Mapping, while a change to CleanMinimalApi.Infrastructure.Databases.MovieReviews.Mapping can't break CleanMinimalApi.Application.Movies.Entities.
- Position
- Below the diagonal: CleanMinimalApi.Infrastructure.Databases.MovieReviews.Mapping uses a module listed above it, which is the healthy direction.
33→21 CleanMinimalApi.Infrastructure.Databases.MovieReviews.Mapping uses CleanMinimalApi.Application.Reviews.Entities✕
- Connections
- 1 pair of types, where a type in CleanMinimalApi.Infrastructure.Databases.MovieReviews.Mapping uses a type in CleanMinimalApi.Application.Reviews.Entities.
- The types involved
CleanMinimalApi.Infrastructure.Databases.MovieReviews.Mapping.MovieReviewsMapper→CleanMinimalApi.Application.Reviews.Entities.Review
- Direction
- CleanMinimalApi.Infrastructure.Databases.MovieReviews.Mapping uses CleanMinimalApi.Application.Reviews.Entities, so a change to CleanMinimalApi.Application.Reviews.Entities can break CleanMinimalApi.Infrastructure.Databases.MovieReviews.Mapping, while a change to CleanMinimalApi.Infrastructure.Databases.MovieReviews.Mapping can't break CleanMinimalApi.Application.Reviews.Entities.
- Position
- Below the diagonal: CleanMinimalApi.Infrastructure.Databases.MovieReviews.Mapping uses a module listed above it, which is the healthy direction.
33→22 CleanMinimalApi.Infrastructure.Databases.MovieReviews.Mapping uses CleanMinimalApi.Application.Authors.Entities✕
- Connections
- 2 pairs of types, where a type in CleanMinimalApi.Infrastructure.Databases.MovieReviews.Mapping uses a type in CleanMinimalApi.Application.Authors.Entities.
- The types involved
CleanMinimalApi.Infrastructure.Databases.MovieReviews.Mapping.MovieReviewsMapper→CleanMinimalApi.Application.Authors.Entities.AuthorCleanMinimalApi.Infrastructure.Databases.MovieReviews.Mapping.MovieReviewsMapper→CleanMinimalApi.Application.Authors.Entities.ReviewAuthor
- Direction
- CleanMinimalApi.Infrastructure.Databases.MovieReviews.Mapping uses CleanMinimalApi.Application.Authors.Entities, so a change to CleanMinimalApi.Application.Authors.Entities can break CleanMinimalApi.Infrastructure.Databases.MovieReviews.Mapping, while a change to CleanMinimalApi.Infrastructure.Databases.MovieReviews.Mapping can't break CleanMinimalApi.Application.Authors.Entities.
- Position
- Below the diagonal: CleanMinimalApi.Infrastructure.Databases.MovieReviews.Mapping uses a module listed above it, which is the healthy direction.
34→6 CleanMinimalApi.Presentation.Endpoints uses CleanMinimalApi.Application.Common.Paging✕
- Connections
- 3 pairs of types, where a type in CleanMinimalApi.Presentation.Endpoints uses a type in CleanMinimalApi.Application.Common.Paging.
- The types involved
CleanMinimalApi.Presentation.Endpoints.AuthorEndpoints→CleanMinimalApi.Application.Common.Paging.PageCleanMinimalApi.Presentation.Endpoints.MovieEndpoints→CleanMinimalApi.Application.Common.Paging.PageCleanMinimalApi.Presentation.Endpoints.ReviewEndpoints→CleanMinimalApi.Application.Common.Paging.Page
- Direction
- CleanMinimalApi.Presentation.Endpoints uses CleanMinimalApi.Application.Common.Paging, so a change to CleanMinimalApi.Application.Common.Paging can break CleanMinimalApi.Presentation.Endpoints, while a change to CleanMinimalApi.Presentation.Endpoints can't break CleanMinimalApi.Application.Common.Paging.
- Position
- Below the diagonal: CleanMinimalApi.Presentation.Endpoints uses a module listed above it, which is the healthy direction.
34→8 CleanMinimalApi.Presentation.Endpoints uses CleanMinimalApi.Application.Versions.Entities✕
- Connections
- 1 pair of types, where a type in CleanMinimalApi.Presentation.Endpoints uses a type in CleanMinimalApi.Application.Versions.Entities.
- The types involved
CleanMinimalApi.Presentation.Endpoints.VersionEndpoints→CleanMinimalApi.Application.Versions.Entities.VersionInfo
- Direction
- CleanMinimalApi.Presentation.Endpoints uses CleanMinimalApi.Application.Versions.Entities, so a change to CleanMinimalApi.Application.Versions.Entities can break CleanMinimalApi.Presentation.Endpoints, while a change to CleanMinimalApi.Presentation.Endpoints can't break CleanMinimalApi.Application.Versions.Entities.
- Position
- Below the diagonal: CleanMinimalApi.Presentation.Endpoints uses a module listed above it, which is the healthy direction.
34→14 CleanMinimalApi.Presentation.Endpoints uses CleanMinimalApi.Presentation.Requests✕
- Connections
- 2 pairs of types, where a type in CleanMinimalApi.Presentation.Endpoints uses a type in CleanMinimalApi.Presentation.Requests.
- The types involved
CleanMinimalApi.Presentation.Endpoints.ReviewEndpoints→CleanMinimalApi.Presentation.Requests.CreateReviewRequestCleanMinimalApi.Presentation.Endpoints.ReviewEndpoints→CleanMinimalApi.Presentation.Requests.UpdateReviewRequest
- Direction
- CleanMinimalApi.Presentation.Endpoints uses CleanMinimalApi.Presentation.Requests, so a change to CleanMinimalApi.Presentation.Requests can break CleanMinimalApi.Presentation.Endpoints, while a change to CleanMinimalApi.Presentation.Endpoints can't break CleanMinimalApi.Presentation.Requests.
- Position
- Below the diagonal: CleanMinimalApi.Presentation.Endpoints uses a module listed above it, which is the healthy direction.
34→17 CleanMinimalApi.Presentation.Endpoints uses CleanMinimalApi.Application.Movies.Entities✕
- Connections
- 2 pairs of types, where a type in CleanMinimalApi.Presentation.Endpoints uses a type in CleanMinimalApi.Application.Movies.Entities.
- The types involved
CleanMinimalApi.Presentation.Endpoints.MovieEndpoints→CleanMinimalApi.Application.Movies.Entities.MovieCleanMinimalApi.Presentation.Endpoints.MovieEndpoints→CleanMinimalApi.Application.Movies.Entities.MovieSummary
- Direction
- CleanMinimalApi.Presentation.Endpoints uses CleanMinimalApi.Application.Movies.Entities, so a change to CleanMinimalApi.Application.Movies.Entities can break CleanMinimalApi.Presentation.Endpoints, while a change to CleanMinimalApi.Presentation.Endpoints can't break CleanMinimalApi.Application.Movies.Entities.
- Position
- Below the diagonal: CleanMinimalApi.Presentation.Endpoints uses a module listed above it, which is the healthy direction.
34→21 CleanMinimalApi.Presentation.Endpoints uses CleanMinimalApi.Application.Reviews.Entities✕
- Connections
- 1 pair of types, where a type in CleanMinimalApi.Presentation.Endpoints uses a type in CleanMinimalApi.Application.Reviews.Entities.
- The types involved
CleanMinimalApi.Presentation.Endpoints.ReviewEndpoints→CleanMinimalApi.Application.Reviews.Entities.Review
- Direction
- CleanMinimalApi.Presentation.Endpoints uses CleanMinimalApi.Application.Reviews.Entities, so a change to CleanMinimalApi.Application.Reviews.Entities can break CleanMinimalApi.Presentation.Endpoints, while a change to CleanMinimalApi.Presentation.Endpoints can't break CleanMinimalApi.Application.Reviews.Entities.
- Position
- Below the diagonal: CleanMinimalApi.Presentation.Endpoints uses a module listed above it, which is the healthy direction.
34→22 CleanMinimalApi.Presentation.Endpoints uses CleanMinimalApi.Application.Authors.Entities✕
- Connections
- 2 pairs of types, where a type in CleanMinimalApi.Presentation.Endpoints uses a type in CleanMinimalApi.Application.Authors.Entities.
- The types involved
CleanMinimalApi.Presentation.Endpoints.AuthorEndpoints→CleanMinimalApi.Application.Authors.Entities.AuthorCleanMinimalApi.Presentation.Endpoints.AuthorEndpoints→CleanMinimalApi.Application.Authors.Entities.AuthorSummary
- Direction
- CleanMinimalApi.Presentation.Endpoints uses CleanMinimalApi.Application.Authors.Entities, so a change to CleanMinimalApi.Application.Authors.Entities can break CleanMinimalApi.Presentation.Endpoints, while a change to CleanMinimalApi.Presentation.Endpoints can't break CleanMinimalApi.Application.Authors.Entities.
- Position
- Below the diagonal: CleanMinimalApi.Presentation.Endpoints uses a module listed above it, which is the healthy direction.
35→6 CleanMinimalApi.Presentation.Serialization uses CleanMinimalApi.Application.Common.Paging✕
- Connections
- 1 pair of types, where a type in CleanMinimalApi.Presentation.Serialization uses a type in CleanMinimalApi.Application.Common.Paging.
- The types involved
CleanMinimalApi.Presentation.Serialization.AppJsonSerializerContext→CleanMinimalApi.Application.Common.Paging.Page
- Direction
- CleanMinimalApi.Presentation.Serialization uses CleanMinimalApi.Application.Common.Paging, so a change to CleanMinimalApi.Application.Common.Paging can break CleanMinimalApi.Presentation.Serialization, while a change to CleanMinimalApi.Presentation.Serialization can't break CleanMinimalApi.Application.Common.Paging.
- Position
- Below the diagonal: CleanMinimalApi.Presentation.Serialization uses a module listed above it, which is the healthy direction.
35→8 CleanMinimalApi.Presentation.Serialization uses CleanMinimalApi.Application.Versions.Entities✕
- Connections
- 1 pair of types, where a type in CleanMinimalApi.Presentation.Serialization uses a type in CleanMinimalApi.Application.Versions.Entities.
- The types involved
CleanMinimalApi.Presentation.Serialization.AppJsonSerializerContext→CleanMinimalApi.Application.Versions.Entities.VersionInfo
- Direction
- CleanMinimalApi.Presentation.Serialization uses CleanMinimalApi.Application.Versions.Entities, so a change to CleanMinimalApi.Application.Versions.Entities can break CleanMinimalApi.Presentation.Serialization, while a change to CleanMinimalApi.Presentation.Serialization can't break CleanMinimalApi.Application.Versions.Entities.
- Position
- Below the diagonal: CleanMinimalApi.Presentation.Serialization uses a module listed above it, which is the healthy direction.
35→14 CleanMinimalApi.Presentation.Serialization uses CleanMinimalApi.Presentation.Requests✕
- Connections
- 2 pairs of types, where a type in CleanMinimalApi.Presentation.Serialization uses a type in CleanMinimalApi.Presentation.Requests.
- The types involved
CleanMinimalApi.Presentation.Serialization.AppJsonSerializerContext→CleanMinimalApi.Presentation.Requests.CreateReviewRequestCleanMinimalApi.Presentation.Serialization.AppJsonSerializerContext→CleanMinimalApi.Presentation.Requests.UpdateReviewRequest
- Direction
- CleanMinimalApi.Presentation.Serialization uses CleanMinimalApi.Presentation.Requests, so a change to CleanMinimalApi.Presentation.Requests can break CleanMinimalApi.Presentation.Serialization, while a change to CleanMinimalApi.Presentation.Serialization can't break CleanMinimalApi.Presentation.Requests.
- Position
- Below the diagonal: CleanMinimalApi.Presentation.Serialization uses a module listed above it, which is the healthy direction.
35→17 CleanMinimalApi.Presentation.Serialization uses CleanMinimalApi.Application.Movies.Entities✕
- Connections
- 3 pairs of types, where a type in CleanMinimalApi.Presentation.Serialization uses a type in CleanMinimalApi.Application.Movies.Entities.
- The types involved
CleanMinimalApi.Presentation.Serialization.AppJsonSerializerContext→CleanMinimalApi.Application.Movies.Entities.MovieCleanMinimalApi.Presentation.Serialization.AppJsonSerializerContext→CleanMinimalApi.Application.Movies.Entities.MovieSummaryCleanMinimalApi.Presentation.Serialization.AppJsonSerializerContext→CleanMinimalApi.Application.Movies.Entities.ReviewedMovie
- Direction
- CleanMinimalApi.Presentation.Serialization uses CleanMinimalApi.Application.Movies.Entities, so a change to CleanMinimalApi.Application.Movies.Entities can break CleanMinimalApi.Presentation.Serialization, while a change to CleanMinimalApi.Presentation.Serialization can't break CleanMinimalApi.Application.Movies.Entities.
- Position
- Below the diagonal: CleanMinimalApi.Presentation.Serialization uses a module listed above it, which is the healthy direction.
35→21 CleanMinimalApi.Presentation.Serialization uses CleanMinimalApi.Application.Reviews.Entities✕
- Connections
- 1 pair of types, where a type in CleanMinimalApi.Presentation.Serialization uses a type in CleanMinimalApi.Application.Reviews.Entities.
- The types involved
CleanMinimalApi.Presentation.Serialization.AppJsonSerializerContext→CleanMinimalApi.Application.Reviews.Entities.Review
- Direction
- CleanMinimalApi.Presentation.Serialization uses CleanMinimalApi.Application.Reviews.Entities, so a change to CleanMinimalApi.Application.Reviews.Entities can break CleanMinimalApi.Presentation.Serialization, while a change to CleanMinimalApi.Presentation.Serialization can't break CleanMinimalApi.Application.Reviews.Entities.
- Position
- Below the diagonal: CleanMinimalApi.Presentation.Serialization uses a module listed above it, which is the healthy direction.
35→22 CleanMinimalApi.Presentation.Serialization uses CleanMinimalApi.Application.Authors.Entities✕
- Connections
- 3 pairs of types, where a type in CleanMinimalApi.Presentation.Serialization uses a type in CleanMinimalApi.Application.Authors.Entities.
- The types involved
CleanMinimalApi.Presentation.Serialization.AppJsonSerializerContext→CleanMinimalApi.Application.Authors.Entities.AuthorCleanMinimalApi.Presentation.Serialization.AppJsonSerializerContext→CleanMinimalApi.Application.Authors.Entities.AuthorSummaryCleanMinimalApi.Presentation.Serialization.AppJsonSerializerContext→CleanMinimalApi.Application.Authors.Entities.ReviewAuthor
- Direction
- CleanMinimalApi.Presentation.Serialization uses CleanMinimalApi.Application.Authors.Entities, so a change to CleanMinimalApi.Application.Authors.Entities can break CleanMinimalApi.Presentation.Serialization, while a change to CleanMinimalApi.Presentation.Serialization can't break CleanMinimalApi.Application.Authors.Entities.
- Position
- Below the diagonal: CleanMinimalApi.Presentation.Serialization uses a module listed above it, which is the healthy direction.
36→22 CleanMinimalApi.Application.Authors.Queries.GetAuthorById uses CleanMinimalApi.Application.Authors.Entities✕
- Connections
- 1 pair of types, where a type in CleanMinimalApi.Application.Authors.Queries.GetAuthorById uses a type in CleanMinimalApi.Application.Authors.Entities.
- The types involved
CleanMinimalApi.Application.Authors.Queries.GetAuthorById.GetAuthorByIdHandler→CleanMinimalApi.Application.Authors.Entities.Author
- Direction
- CleanMinimalApi.Application.Authors.Queries.GetAuthorById uses CleanMinimalApi.Application.Authors.Entities, so a change to CleanMinimalApi.Application.Authors.Entities can break CleanMinimalApi.Application.Authors.Queries.GetAuthorById, while a change to CleanMinimalApi.Application.Authors.Queries.GetAuthorById can't break CleanMinimalApi.Application.Authors.Entities.
- Position
- Below the diagonal: CleanMinimalApi.Application.Authors.Queries.GetAuthorById uses a module listed above it, which is the healthy direction.
36→26 CleanMinimalApi.Application.Authors.Queries.GetAuthorById uses CleanMinimalApi.Application.Authors✕
- Connections
- 1 pair of types, where a type in CleanMinimalApi.Application.Authors.Queries.GetAuthorById uses a type in CleanMinimalApi.Application.Authors.
- The types involved
CleanMinimalApi.Application.Authors.Queries.GetAuthorById.GetAuthorByIdHandler→CleanMinimalApi.Application.Authors.IAuthorsRepository
- Direction
- CleanMinimalApi.Application.Authors.Queries.GetAuthorById uses CleanMinimalApi.Application.Authors, so a change to CleanMinimalApi.Application.Authors can break CleanMinimalApi.Application.Authors.Queries.GetAuthorById, while a change to CleanMinimalApi.Application.Authors.Queries.GetAuthorById can't break CleanMinimalApi.Application.Authors.
- Position
- Below the diagonal: CleanMinimalApi.Application.Authors.Queries.GetAuthorById uses a module listed above it, which is the healthy direction.
37→6 CleanMinimalApi.Application.Authors.Queries.GetAuthors uses CleanMinimalApi.Application.Common.Paging✕
- Connections
- 1 pair of types, where a type in CleanMinimalApi.Application.Authors.Queries.GetAuthors uses a type in CleanMinimalApi.Application.Common.Paging.
- The types involved
CleanMinimalApi.Application.Authors.Queries.GetAuthors.GetAuthorsHandler→CleanMinimalApi.Application.Common.Paging.Page
- Direction
- CleanMinimalApi.Application.Authors.Queries.GetAuthors uses CleanMinimalApi.Application.Common.Paging, so a change to CleanMinimalApi.Application.Common.Paging can break CleanMinimalApi.Application.Authors.Queries.GetAuthors, while a change to CleanMinimalApi.Application.Authors.Queries.GetAuthors can't break CleanMinimalApi.Application.Common.Paging.
- Position
- Below the diagonal: CleanMinimalApi.Application.Authors.Queries.GetAuthors uses a module listed above it, which is the healthy direction.
37→22 CleanMinimalApi.Application.Authors.Queries.GetAuthors uses CleanMinimalApi.Application.Authors.Entities✕
- Connections
- 1 pair of types, where a type in CleanMinimalApi.Application.Authors.Queries.GetAuthors uses a type in CleanMinimalApi.Application.Authors.Entities.
- The types involved
CleanMinimalApi.Application.Authors.Queries.GetAuthors.GetAuthorsHandler→CleanMinimalApi.Application.Authors.Entities.AuthorSummary
- Direction
- CleanMinimalApi.Application.Authors.Queries.GetAuthors uses CleanMinimalApi.Application.Authors.Entities, so a change to CleanMinimalApi.Application.Authors.Entities can break CleanMinimalApi.Application.Authors.Queries.GetAuthors, while a change to CleanMinimalApi.Application.Authors.Queries.GetAuthors can't break CleanMinimalApi.Application.Authors.Entities.
- Position
- Below the diagonal: CleanMinimalApi.Application.Authors.Queries.GetAuthors uses a module listed above it, which is the healthy direction.
37→26 CleanMinimalApi.Application.Authors.Queries.GetAuthors uses CleanMinimalApi.Application.Authors✕
- Connections
- 1 pair of types, where a type in CleanMinimalApi.Application.Authors.Queries.GetAuthors uses a type in CleanMinimalApi.Application.Authors.
- The types involved
CleanMinimalApi.Application.Authors.Queries.GetAuthors.GetAuthorsHandler→CleanMinimalApi.Application.Authors.IAuthorsRepository
- Direction
- CleanMinimalApi.Application.Authors.Queries.GetAuthors uses CleanMinimalApi.Application.Authors, so a change to CleanMinimalApi.Application.Authors can break CleanMinimalApi.Application.Authors.Queries.GetAuthors, while a change to CleanMinimalApi.Application.Authors.Queries.GetAuthors can't break CleanMinimalApi.Application.Authors.
- Position
- Below the diagonal: CleanMinimalApi.Application.Authors.Queries.GetAuthors uses a module listed above it, which is the healthy direction.
38→20 CleanMinimalApi.Application.Reviews.Commands.CreateReview uses CleanMinimalApi.Application.Movies✕
- Connections
- 1 pair of types, where a type in CleanMinimalApi.Application.Reviews.Commands.CreateReview uses a type in CleanMinimalApi.Application.Movies.
- The types involved
CleanMinimalApi.Application.Reviews.Commands.CreateReview.CreateReviewHandler→CleanMinimalApi.Application.Movies.IMoviesRepository
- Direction
- CleanMinimalApi.Application.Reviews.Commands.CreateReview uses CleanMinimalApi.Application.Movies, so a change to CleanMinimalApi.Application.Movies can break CleanMinimalApi.Application.Reviews.Commands.CreateReview, while a change to CleanMinimalApi.Application.Reviews.Commands.CreateReview can't break CleanMinimalApi.Application.Movies.
- Position
- Below the diagonal: CleanMinimalApi.Application.Reviews.Commands.CreateReview uses a module listed above it, which is the healthy direction.
38→21 CleanMinimalApi.Application.Reviews.Commands.CreateReview uses CleanMinimalApi.Application.Reviews.Entities✕
- Connections
- 1 pair of types, where a type in CleanMinimalApi.Application.Reviews.Commands.CreateReview uses a type in CleanMinimalApi.Application.Reviews.Entities.
- The types involved
CleanMinimalApi.Application.Reviews.Commands.CreateReview.CreateReviewHandler→CleanMinimalApi.Application.Reviews.Entities.Review
- Direction
- CleanMinimalApi.Application.Reviews.Commands.CreateReview uses CleanMinimalApi.Application.Reviews.Entities, so a change to CleanMinimalApi.Application.Reviews.Entities can break CleanMinimalApi.Application.Reviews.Commands.CreateReview, while a change to CleanMinimalApi.Application.Reviews.Commands.CreateReview can't break CleanMinimalApi.Application.Reviews.Entities.
- Position
- Below the diagonal: CleanMinimalApi.Application.Reviews.Commands.CreateReview uses a module listed above it, which is the healthy direction.
38→25 CleanMinimalApi.Application.Reviews.Commands.CreateReview uses CleanMinimalApi.Application.Reviews✕
- Connections
- 1 pair of types, where a type in CleanMinimalApi.Application.Reviews.Commands.CreateReview uses a type in CleanMinimalApi.Application.Reviews.
- The types involved
CleanMinimalApi.Application.Reviews.Commands.CreateReview.CreateReviewHandler→CleanMinimalApi.Application.Reviews.IReviewsRepository
- Direction
- CleanMinimalApi.Application.Reviews.Commands.CreateReview uses CleanMinimalApi.Application.Reviews, so a change to CleanMinimalApi.Application.Reviews can break CleanMinimalApi.Application.Reviews.Commands.CreateReview, while a change to CleanMinimalApi.Application.Reviews.Commands.CreateReview can't break CleanMinimalApi.Application.Reviews.
- Position
- Below the diagonal: CleanMinimalApi.Application.Reviews.Commands.CreateReview uses a module listed above it, which is the healthy direction.
38→26 CleanMinimalApi.Application.Reviews.Commands.CreateReview uses CleanMinimalApi.Application.Authors✕
- Connections
- 1 pair of types, where a type in CleanMinimalApi.Application.Reviews.Commands.CreateReview uses a type in CleanMinimalApi.Application.Authors.
- The types involved
CleanMinimalApi.Application.Reviews.Commands.CreateReview.CreateReviewHandler→CleanMinimalApi.Application.Authors.IAuthorsRepository
- Direction
- CleanMinimalApi.Application.Reviews.Commands.CreateReview uses CleanMinimalApi.Application.Authors, so a change to CleanMinimalApi.Application.Authors can break CleanMinimalApi.Application.Reviews.Commands.CreateReview, while a change to CleanMinimalApi.Application.Reviews.Commands.CreateReview can't break CleanMinimalApi.Application.Authors.
- Position
- Below the diagonal: CleanMinimalApi.Application.Reviews.Commands.CreateReview uses a module listed above it, which is the healthy direction.
39→6 CleanMinimalApi.Infrastructure.Databases.MovieReviews uses CleanMinimalApi.Application.Common.Paging✕
- Connections
- 2 pairs of types, where a type in CleanMinimalApi.Infrastructure.Databases.MovieReviews uses a type in CleanMinimalApi.Application.Common.Paging.
- The types involved
CleanMinimalApi.Infrastructure.Databases.MovieReviews.EntityFrameworkMovieReviewsRepository→CleanMinimalApi.Application.Common.Paging.PageCleanMinimalApi.Infrastructure.Databases.MovieReviews.EntityFrameworkMovieReviewsRepository→CleanMinimalApi.Application.Common.Paging.PageRequest
- Direction
- CleanMinimalApi.Infrastructure.Databases.MovieReviews uses CleanMinimalApi.Application.Common.Paging, so a change to CleanMinimalApi.Application.Common.Paging can break CleanMinimalApi.Infrastructure.Databases.MovieReviews, while a change to CleanMinimalApi.Infrastructure.Databases.MovieReviews can't break CleanMinimalApi.Application.Common.Paging.
- Position
- Below the diagonal: CleanMinimalApi.Infrastructure.Databases.MovieReviews uses a module listed above it, which is the healthy direction.
39→10 CleanMinimalApi.Infrastructure.Databases.MovieReviews uses CleanMinimalApi.Infrastructure.Databases.MovieReviews.Models✕
- Connections
- 3 pairs of types, where a type in CleanMinimalApi.Infrastructure.Databases.MovieReviews uses a type in CleanMinimalApi.Infrastructure.Databases.MovieReviews.Models.
- The types involved
CleanMinimalApi.Infrastructure.Databases.MovieReviews.MovieReviewsDbContext→CleanMinimalApi.Infrastructure.Databases.MovieReviews.Models.AuthorCleanMinimalApi.Infrastructure.Databases.MovieReviews.MovieReviewsDbContext→CleanMinimalApi.Infrastructure.Databases.MovieReviews.Models.MovieCleanMinimalApi.Infrastructure.Databases.MovieReviews.MovieReviewsDbContext→CleanMinimalApi.Infrastructure.Databases.MovieReviews.Models.Review
- Direction
- CleanMinimalApi.Infrastructure.Databases.MovieReviews uses CleanMinimalApi.Infrastructure.Databases.MovieReviews.Models, so a change to CleanMinimalApi.Infrastructure.Databases.MovieReviews.Models can break CleanMinimalApi.Infrastructure.Databases.MovieReviews, while a change to CleanMinimalApi.Infrastructure.Databases.MovieReviews can't break CleanMinimalApi.Infrastructure.Databases.MovieReviews.Models.
- Position
- Below the diagonal: CleanMinimalApi.Infrastructure.Databases.MovieReviews uses a module listed above it, which is the healthy direction.
39→17 CleanMinimalApi.Infrastructure.Databases.MovieReviews uses CleanMinimalApi.Application.Movies.Entities✕
- Connections
- 2 pairs of types, where a type in CleanMinimalApi.Infrastructure.Databases.MovieReviews uses a type in CleanMinimalApi.Application.Movies.Entities.
- The types involved
CleanMinimalApi.Infrastructure.Databases.MovieReviews.EntityFrameworkMovieReviewsRepository→CleanMinimalApi.Application.Movies.Entities.MovieCleanMinimalApi.Infrastructure.Databases.MovieReviews.EntityFrameworkMovieReviewsRepository→CleanMinimalApi.Application.Movies.Entities.MovieSummary
- Direction
- CleanMinimalApi.Infrastructure.Databases.MovieReviews uses CleanMinimalApi.Application.Movies.Entities, so a change to CleanMinimalApi.Application.Movies.Entities can break CleanMinimalApi.Infrastructure.Databases.MovieReviews, while a change to CleanMinimalApi.Infrastructure.Databases.MovieReviews can't break CleanMinimalApi.Application.Movies.Entities.
- Position
- Below the diagonal: CleanMinimalApi.Infrastructure.Databases.MovieReviews uses a module listed above it, which is the healthy direction.
39→20 CleanMinimalApi.Infrastructure.Databases.MovieReviews uses CleanMinimalApi.Application.Movies✕
- Connections
- 1 pair of types, where a type in CleanMinimalApi.Infrastructure.Databases.MovieReviews uses a type in CleanMinimalApi.Application.Movies.
- The types involved
CleanMinimalApi.Infrastructure.Databases.MovieReviews.EntityFrameworkMovieReviewsRepository→CleanMinimalApi.Application.Movies.IMoviesRepository
- Direction
- CleanMinimalApi.Infrastructure.Databases.MovieReviews uses CleanMinimalApi.Application.Movies, so a change to CleanMinimalApi.Application.Movies can break CleanMinimalApi.Infrastructure.Databases.MovieReviews, while a change to CleanMinimalApi.Infrastructure.Databases.MovieReviews can't break CleanMinimalApi.Application.Movies.
- Position
- Below the diagonal: CleanMinimalApi.Infrastructure.Databases.MovieReviews uses a module listed above it, which is the healthy direction.
39→21 CleanMinimalApi.Infrastructure.Databases.MovieReviews uses CleanMinimalApi.Application.Reviews.Entities✕
- Connections
- 1 pair of types, where a type in CleanMinimalApi.Infrastructure.Databases.MovieReviews uses a type in CleanMinimalApi.Application.Reviews.Entities.
- The types involved
CleanMinimalApi.Infrastructure.Databases.MovieReviews.EntityFrameworkMovieReviewsRepository→CleanMinimalApi.Application.Reviews.Entities.Review
- Direction
- CleanMinimalApi.Infrastructure.Databases.MovieReviews uses CleanMinimalApi.Application.Reviews.Entities, so a change to CleanMinimalApi.Application.Reviews.Entities can break CleanMinimalApi.Infrastructure.Databases.MovieReviews, while a change to CleanMinimalApi.Infrastructure.Databases.MovieReviews can't break CleanMinimalApi.Application.Reviews.Entities.
- Position
- Below the diagonal: CleanMinimalApi.Infrastructure.Databases.MovieReviews uses a module listed above it, which is the healthy direction.
39→22 CleanMinimalApi.Infrastructure.Databases.MovieReviews uses CleanMinimalApi.Application.Authors.Entities✕
- Connections
- 2 pairs of types, where a type in CleanMinimalApi.Infrastructure.Databases.MovieReviews uses a type in CleanMinimalApi.Application.Authors.Entities.
- The types involved
CleanMinimalApi.Infrastructure.Databases.MovieReviews.EntityFrameworkMovieReviewsRepository→CleanMinimalApi.Application.Authors.Entities.AuthorCleanMinimalApi.Infrastructure.Databases.MovieReviews.EntityFrameworkMovieReviewsRepository→CleanMinimalApi.Application.Authors.Entities.AuthorSummary
- Direction
- CleanMinimalApi.Infrastructure.Databases.MovieReviews uses CleanMinimalApi.Application.Authors.Entities, so a change to CleanMinimalApi.Application.Authors.Entities can break CleanMinimalApi.Infrastructure.Databases.MovieReviews, while a change to CleanMinimalApi.Infrastructure.Databases.MovieReviews can't break CleanMinimalApi.Application.Authors.Entities.
- Position
- Below the diagonal: CleanMinimalApi.Infrastructure.Databases.MovieReviews uses a module listed above it, which is the healthy direction.
39→25 CleanMinimalApi.Infrastructure.Databases.MovieReviews uses CleanMinimalApi.Application.Reviews✕
- Connections
- 1 pair of types, where a type in CleanMinimalApi.Infrastructure.Databases.MovieReviews uses a type in CleanMinimalApi.Application.Reviews.
- The types involved
CleanMinimalApi.Infrastructure.Databases.MovieReviews.EntityFrameworkMovieReviewsRepository→CleanMinimalApi.Application.Reviews.IReviewsRepository
- Direction
- CleanMinimalApi.Infrastructure.Databases.MovieReviews uses CleanMinimalApi.Application.Reviews, so a change to CleanMinimalApi.Application.Reviews can break CleanMinimalApi.Infrastructure.Databases.MovieReviews, while a change to CleanMinimalApi.Infrastructure.Databases.MovieReviews can't break CleanMinimalApi.Application.Reviews.
- Position
- Below the diagonal: CleanMinimalApi.Infrastructure.Databases.MovieReviews uses a module listed above it, which is the healthy direction.
39→26 CleanMinimalApi.Infrastructure.Databases.MovieReviews uses CleanMinimalApi.Application.Authors✕
- Connections
- 1 pair of types, where a type in CleanMinimalApi.Infrastructure.Databases.MovieReviews uses a type in CleanMinimalApi.Application.Authors.
- The types involved
CleanMinimalApi.Infrastructure.Databases.MovieReviews.EntityFrameworkMovieReviewsRepository→CleanMinimalApi.Application.Authors.IAuthorsRepository
- Direction
- CleanMinimalApi.Infrastructure.Databases.MovieReviews uses CleanMinimalApi.Application.Authors, so a change to CleanMinimalApi.Application.Authors can break CleanMinimalApi.Infrastructure.Databases.MovieReviews, while a change to CleanMinimalApi.Infrastructure.Databases.MovieReviews can't break CleanMinimalApi.Application.Authors.
- Position
- Below the diagonal: CleanMinimalApi.Infrastructure.Databases.MovieReviews uses a module listed above it, which is the healthy direction.
39→33 CleanMinimalApi.Infrastructure.Databases.MovieReviews uses CleanMinimalApi.Infrastructure.Databases.MovieReviews.Mapping✕
- Connections
- 1 pair of types, where a type in CleanMinimalApi.Infrastructure.Databases.MovieReviews uses a type in CleanMinimalApi.Infrastructure.Databases.MovieReviews.Mapping.
- The types involved
CleanMinimalApi.Infrastructure.Databases.MovieReviews.EntityFrameworkMovieReviewsRepository→CleanMinimalApi.Infrastructure.Databases.MovieReviews.Mapping.MovieReviewsMapper
- Direction
- CleanMinimalApi.Infrastructure.Databases.MovieReviews uses CleanMinimalApi.Infrastructure.Databases.MovieReviews.Mapping, so a change to CleanMinimalApi.Infrastructure.Databases.MovieReviews.Mapping can break CleanMinimalApi.Infrastructure.Databases.MovieReviews, while a change to CleanMinimalApi.Infrastructure.Databases.MovieReviews can't break CleanMinimalApi.Infrastructure.Databases.MovieReviews.Mapping.
- Position
- Below the diagonal: CleanMinimalApi.Infrastructure.Databases.MovieReviews uses a module listed above it, which is the healthy direction.
40→39 CleanMinimalApi.Infrastructure.Databases.MovieReviews.Extensions uses CleanMinimalApi.Infrastructure.Databases.MovieReviews✕
- Connections
- 1 pair of types, where a type in CleanMinimalApi.Infrastructure.Databases.MovieReviews.Extensions uses a type in CleanMinimalApi.Infrastructure.Databases.MovieReviews.
- The types involved
CleanMinimalApi.Infrastructure.Databases.MovieReviews.Extensions.MovieReviewsDbContextExtensions→CleanMinimalApi.Infrastructure.Databases.MovieReviews.MovieReviewsDbContext
- Direction
- CleanMinimalApi.Infrastructure.Databases.MovieReviews.Extensions uses CleanMinimalApi.Infrastructure.Databases.MovieReviews, so a change to CleanMinimalApi.Infrastructure.Databases.MovieReviews can break CleanMinimalApi.Infrastructure.Databases.MovieReviews.Extensions, while a change to CleanMinimalApi.Infrastructure.Databases.MovieReviews.Extensions can't break CleanMinimalApi.Infrastructure.Databases.MovieReviews.
- Position
- Below the diagonal: CleanMinimalApi.Infrastructure.Databases.MovieReviews.Extensions uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A05:2025 — Injection | 29 | High / Critical |
| A02:2025 — Security Misconfiguration | 4 | Medium |
Roadmap
Top priorities: Codify backups + geo-recovery in IaC and document RTO/RPO and the restore procedure — a persistence guard alone is not disaster recovery; Add `AddStandardResilienceHandler()` (or Polly policies) to your HttpClient registrations so a flaky dependency can't take the app down; Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Codify backups + geo-recovery in IaC and document RTO/RPO and the restore procedure — a persistence guard alone is not disaster recovery. | +8.2 pts | Medium | DR & Backup |
| Add `AddStandardResilienceHandler()` (or Polly policies) to your HttpClient registrations so a flaky dependency can't take the app down. | +4.6 pts | Medium | Outbound HTTP resilience |
| Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release. | +2.8 pts | Medium | Release Hygiene |
| Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them. | +2.7 pts | Medium | Architecture documentation |
| Add an 'Architecture' / 'How it works' section to the root README — the high-level shape. | +1.4 pts | Medium | Documentation (README) |
| Keep singletons stateless or back their state with thread-safe types (Concurrent*/Immutable*); otherwise concurrent callers race. | +1.0 pts | Medium | Stateful singletons |
| 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). | +1.0 pts | Medium | Benchmark discipline |
| The domain core is a small share of production code — check that business logic isn't leaking into the application/infrastructure layers (a thin domain is the anemic-domain smell). | +0.9 pts | Medium | Code composition |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 4.0 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| REDACTED | 4.4 | Mixed | Static Analysis (SAST): High: REDACTED |
| template/template.csproj | 6.4 | Near-clean | Explicit Debt: NoWarnInCsproj |
| .editorconfig | 6.4 | Near-clean | Explicit Debt: AnalyzerSeverityNone |
| REDACTED | 6.9 | Near-clean | IaC & Container Security: Medium IaC: REDACTED |
| REDACTED | 6.9 | Near-clean | IaC & Container Security: Medium IaC: REDACTED |
| REDACTED | 7.2 | Near-clean | Static Analysis (SAST): High: REDACTED |
| REDACTED | 7.2 | Near-clean | Static Analysis (SAST): High: REDACTED |
| src/Presentation/Presentation.csproj | 7.6 | Near-clean | Explicit Debt: NoWarnInCsproj |
| Directory.Build.props | 7.6 | Near-clean | Explicit Debt: NoWarnInCsproj |
| src/Application/DependencyInjection.cs | 8.2 | Near-clean | Explicit Debt: CoverageExclusion |
| src/Infrastructure/Databases/MovieReviews/Models/Author.cs | 8.2 | Near-clean | Explicit Debt: CoverageExclusion |
| src/Infrastructure/Databases/MovieReviews/Models/Entity.cs | 8.2 | Near-clean | Explicit Debt: CoverageExclusion |
| src/Infrastructure/Databases/MovieReviews/Models/Movie.cs | 8.2 | Near-clean | Explicit Debt: CoverageExclusion |
| src/Infrastructure/Databases/MovieReviews/Models/Review.cs | 8.2 | Near-clean | Explicit Debt: CoverageExclusion |
| src/Infrastructure/Databases/MovieReviews/MovieReviewsDbContextFactory.cs | 8.2 | Near-clean | Explicit Debt: CoverageExclusion |
| src/Presentation/Extensions/WebApplicationBuilderExtensions.cs | 8.2 | Near-clean | Explicit Debt: CoverageExclusion |
| src/Presentation/Extensions/WebApplicationExtensions.cs | 8.2 | Near-clean | Explicit Debt: CoverageExclusion |
| src/Infrastructure/Databases/MovieReviews/Extensions/MovieReviewsDbContextExtensions.cs | 8.5 | Near-clean | Code Duplication: Duplicated block (8 lines × 2) |
| src/Application/Authors/Queries/GetAuthors/GetAuthorsValidator.cs | 8.5 | Near-clean | Code Duplication: Duplicated block (5 lines × 2) |
How the grades work
A definite problem that already costs you something and drags the score down: a missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here tends to cause failures elsewhere.
Likely wrong, but not failing yet. It degrades the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to carry for two years either.
Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.
Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.
Methodology & how to trust this report
This survey is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. All 77 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.9, the weighted average across measured dimensions.
What we checked — 77 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, 57 of 66 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Canine Code Analyzer duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy · checkov | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 · 3.2.533 | ✓ deterministic |
Run transparency — what happened this run
- D8 Code Coverage — not measured this run — 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. The test suite couldn't be built/run in-image and no coverage report is committed, so line coverage was not measured — and it is EXCLUDED from the score rather than scored on a LoC-ratio proxy. Your test projects already reference a coverage collector, but no CI step we found runs the tests with it, so there is no report to hand us — run them with `--collect:"XPlat Code Coverage"` and commit (or publish into the working tree) the coverage.cobertura.xml it writes. You can widen what we reach: optional: your test projects already reference a coverage collector, but no CI step we found runs the tests with it, so there is no report to hand us — run them with `--collect:"XPlat Code Coverage"` and commit (or publish into the working tree) the coverage.cobertura.xml it writes, or make the suite runnable in-image, and real coverage will be measured.
- D11 Test Reliability — 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. Test reliability NOT MEASURED: the test run produced no results for any test tier, so no test ever ran and flakiness could not be exercised. The cause could not be attributed, so it is excluded from the score rather than read as an absence of tests.
- 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: src/Presentation/Presentation.csproj : error NU1507: Warning As Error: There are 2 package sources defined in your configuration. When using central package management, map your package sources with package source mapping (https://aka.ms/nuget-pac….
- D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Single-maintainer repository — bus factor is not applicable (4 contributor(s) across 185 commit(s) sampled, automation and bot accounts excluded). One of them holds 98% of the history; the other 3 hold 0.7% each on average, below the 5% at which there is somebody to hand the work to. That is a single maintainer with drive-by contributors, not a team whose knowledge has concentrated — so the bus factor is not applicable and there is nothing here for the owner to act on.
- D17 Explicit Debt — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. The C# workspace loaded this repository's projects but reported a load failure, and the dead-code reference search is unreliable over a graph that did not load cleanly, so it was skipped. The other debt markers on this row were read; dead symbols were not, and their absence from the score is not a finding that the code has none. First load diagnostic: Failure: Msbuild failed when processing the file 'src/Application/Application.csproj' with message: There are 2 package sources defined in your configuration. When using central package management, map your package sources with package source mapping (https://aka.ms/nuget-package-source-mapping) or specify a single package source. The following ….
- D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This kind did not reach the 95 % precision gate in three adjudicated runs (docs/plans/deterministic-engine/adjudication/D19-sample3-v3.md), so by the pre-registered fallback it publishes no row until a re-measurement shows it does. The candidates are counted here, not reported as findings, and the score does not include them.
- D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D21's deterministic naming rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. Until then its declarations carry no naming verdict this run — this says nothing about whether its names are consistent.
- D22 Internal API Consistency — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. The loaded project set declares no packable project and no `.Contracts` project, so there is no intentionally-exposed surface for API consistency to be judged over.
- D32 Data Compliance (PII/GDPR) — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `src/Application/Authors/Queries/GetAuthorById/GetAuthorByIdHandler.cs`, `src/Application/Authors/Queries/GetAuthors/GetAuthorsHandler.cs`, `src/Application/Common/Behaviours/LoggingBehaviour.cs`, `src/Application/Common/Behaviours/ValidationBehaviour.cs`, `src/Application/Common/Exceptions/NotFoundException.cs`, … (+14 more) produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
- D39 IL Efficiency — 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. IL NOT MEASURED: the analyzer's build of this repository exited 1 and the cause could not be attributed, so no assemblies were produced and there was no IL to read. We do not read it as a defect in the repository: an unattributed failure leans OURS. D18 owns the question of whether this repository builds; it was not answered here.
- AXR1 Runtime accessibility — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via DockerCompose (REDACTED). compose up failed (exit 1 — a container did not start, exited, or never became healthy) — api Built container .-api-1 is unhealthy; runtime evidence skipped.
- M4 Documentation accuracy — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
- D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
- D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
- D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D18 Solution Shape: Build integrity reflects whether the solution compiled in this environment — a build that needs a private feed, a specific SDK, or a generated file absent from the repo can read as broken when it is merely unreproducible here.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
- D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a REDACTED (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- AX9 CQS / query purity: Handlers are found by interface/name convention — a query handler using neither is not seen. Mutation is a resolved write/publish invocation (SaveChanges/repository/bus), so a write hidden behind a hand-rolled wrapper, reflection, or a string-keyed service locator resolves to a non-persistence type and isn't flagged; it detects that a query writes state, not whether the write is a legitimate read-side cache update. Clean means "no resolved write/publish in a query body", not a proof of CQS purity.
- ED5 Idempotency: Idempotency is read from the handler body and one hop below: a mutation is flagged only on structural double-apply evidence (a fresh-identity insert, an accumulation, a growing list, an unkeyed POST/send/charge), so a duplicate effect through a home-grown gateway two hops down, or an insert keyed on the message with no unique constraint, is not flagged but counted as not classified; a guard enforced by a database constraint or a broker's exactly-once delivery is invisible either way. It flags the at-least-once double-apply SHAPE, not a runtime proof of a duplicate effect.
- M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
- P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
- P5 DR & Backup: Backup/restore and disaster-recovery readiness is judged from in-repo evidence — a config that exists is not a tested restore, so the absence of positive evidence is reported as "not evidenced", never scored as present.
- P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
Dimensions
D1 · Cyclomatic Complexity
1 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was report.command_summary at 33.
What to do
- Bring the 1 body over 15 down to 15 or less in Cyclomatic Complexity — start with report.command_summary (cyclomatic 33). — Refactoring it lifts Cyclomatic Complexity from 9.1 to about 10.0/10.
- Enforce Cyclomatic Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D2 · Cognitive Complexity
3 method(s) exceeded the cognitive complexity threshold of 15; the worst was report.command_summary at 34.
What to do
- Bring the 3 bodies over 15 down to 15 or less in Cognitive Complexity — start with report.command_summary (cognitive 34), report.render_tests (cognitive 22), report.parse_coverage (cognitive 17). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 3 together lifts Cognitive Complexity from 8.9 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
- Enforce Cognitive Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
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 (8 lines × 2) finding(s) in Code Duplication — start with MovieReviewsDbContextExtensions.cs. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Duplicated block (5 lines × 2) finding(s) in Code Duplication — start with GetAuthorsValidator.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
8 projects, 0 dependency cycle(s), 0 unstable depended-on project(s).
D6 · Cohesion (LCOM4)
0 of 5 classes have LCOM4 above 3.
D9 · Test Distribution
214 test methods: 115 unit, 99 integration, 0 BDD, 0 e2e.
D10 · Test Quality
0 skipped, 0 zero-assertion, 2 mock references across 214 tests.
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 32 direct `PackageReference`(s), and 218 further package(s) were reached beyond them by closing the graph over nuget.org's own nuspec dependency graph — so a banned licence pulled in only by a dependency's OWN dependencies is inside this verdict. A package whose licence nuget.org could not be asked for is not graded, and version ranges are taken at their lower bound, so this is the closure as that graph states it rather than a restored consumer's exact resolution.
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window.
D17 · Explicit Debt
14 deducted debt markers + unmeasured dead symbols across 2493 LoC in the .NET projects (2.2/KLoC) → score 5.5. Dead code not measured: the solution did not load cleanly, so the reference search was skipped.
What to do
- Resolve the 8 CoverageExclusion finding(s) in Explicit Debt — start with DependencyInjection.cs, Author.cs, Entity.cs. — One of this dimension's main actionable groups (8 warning-level).
- Resolve the 4 NoWarnInCsproj finding(s) in Explicit Debt — start with template.csproj (2), Presentation.csproj, Directory.Build.props. — One of this dimension's main actionable groups (4 issue-level).
- Resolve the 2 AnalyzerSeverityNone finding(s) in Explicit Debt — start with .editorconfig (2). — One of this dimension's main actionable groups (2 issue-level).
- Enforce Explicit Debt in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D18 · Solution Shape
7 projects, 144 source files, 6896 hand-written lines of code (2493 production / 4403 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 608 generated (machine-written code — designer, scaffolded and tool-emitted files — excluded from quality), 7 inter-project edges.
D19 · Documentation Quality
2 of 2 documentation facets pass in full. 3 document(s) read across 4 unit(s).
D26 · Project Cohesion
0 of 8 projects flagged as possibly oversized/incoherent.
D27 · Navigability
94 % of calls cross a namespace and 4 % go through an interface, but 90 % of collaborators are co-located — so a call's collaborators sit together and tracing stays easy. Baseline: small — navigation cost is tolerated.
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
29 finding(s): 0 critical, 25 high, 3 medium, 1 low. semgrep hit a parse error in 19 file(s) — `src/Application/Authors/Queries/GetAuthorById/GetAuthorByIdHandler.cs` (line 8), `src/Application/Authors/Queries/GetAuthors/GetAuthorsHandler.cs` (line 7), `src/Application/Common/Behaviours/LoggingBehaviour.cs` (line 19), `src/Application/Common/Behaviours/ValidationBehaviour.cs` (line 6), `src/Application/Common/Exceptions/NotFoundException.cs` (line 6), … (+14 more) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them. In 19 of those file(s) — `src/Application/Authors/Queries/GetAuthorById/GetAuthorByIdHandler.cs`, `src/Application/Authors/Queries/GetAuthors/GetAuthorsHandler.cs`, `src/Application/Common/Behaviours/LoggingBehaviour.cs`, `src/Application/Common/Behaviours/ValidationBehaviour.cs`, `src/Application/Common/Exceptions/NotFoundException.cs`, … (+14 more) — the break is a C# primary constructor, which semgrep's grammar cannot parse and which hides the type from every rule scoped to it; those files were re-scanned from a shadow copy with the constructor's parameter list blanked (line and column preserving), which restores the type to the rules, and 0 additional row(s) came from that pass. Only the header's own parameter list is unread in them. Separately, one or more rules could not re-parse an embedded snippet in 1 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.
What to do
- Resolve the 24 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (23), REDACTED. — One of this dimension's main actionable groups (24 issue-level).
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2). — One of this dimension's main actionable groups (2 warning-level).
D31 · IaC & Container Security
4 finding(s): 0 critical, 0 high, 4 medium, 0 low.
What to do
- Resolve the 4 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (2), REDACTED (2). — One of this dimension's main actionable groups (4 warning-level).
D34 · Knowledge Freshness
Every significant source file has living knowledge — recently and meaningfully worked. Counted over 11 of the 89 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
D35 · Change Coupling
No strong hidden change-coupling between production files.
D37 · Vulnerability-disclosure Policy
A vulnerability-disclosure policy (SECURITY.md) is published with a reporting contact.
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 1 platform declaration(s) and 0 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
Frontend & cross-cutting dimensions
AX1 · Captive dependencies
AX10 · Code composition
What to do
- The domain core is a small share of production code — check that business logic isn't leaking into the application/infrastructure layers (a thin domain is the anemic-domain smell).
AX2 · Stateful singletons
- `MovieReviewsDatabase` is a singleton (one shared instance) but mutates instance state outside any lock (keepAlive; e.g. `keepAlive` at line 24). — src/Infrastructure/Databases/MovieReviews/MovieReviewsDatabase.cs:12
What to do
- Keep singletons stateless or back their state with thread-safe types (Concurrent*/Immutable*); otherwise concurrent callers race.
AX3 · Project dependency cycles
- The namespaces CleanMinimalApi.Application.Authors.Entities ↔ CleanMinimalApi.Application.Movies.Entities ↔ CleanMinimalApi.Application.Reviews.Entities depend on each other. The lightest dependency in the cycle is CleanMinimalApi.Application.Authors.Entities → CleanMinimalApi.Application.Reviews.Entities (CleanMinimalApi.Application.Authors.Entities.Author → CleanMinimalApi.Application.Reviews.Entities.Review, 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/Application/Authors/Entities/Author.cs:12
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.
AX5 · Architecture & structure
AX6 · Interface segregation
AX8 · Test isolation
AX9 · CQS / query purity
C2 · Access Controls
ED5 · Idempotency
GD1 · Unfinished & placeholder code
IC1 · Incompleteness & stubs
M1 · Documentation (README)
What to do
- Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
- Add a README to the 3 of 4 project(s) that lack one — worth up to 1.5 pts.
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
M3 · Folder & project structure
M4 · Documentation accuracy
P1 · CI/CD gates
P10 · Library API & versioning
P2 · Observability
P3 · Security & performance tooling
What to do
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
P5 · DR & Backup
- A persistence guard (data volume / purge-protection) was found, but no backup, geo-recovery or RTO/RPO controls were evidenced — a volume that survives a container recreate is not a tested restore from catastrophic loss.
What to do
- Codify backups + geo-recovery in IaC and document RTO/RPO and the restore procedure — a persistence guard alone is not disaster recovery.
P6 · Release Hygiene
- No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
What to do
- Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.
P7 · Outbound HTTP resilience
- The app makes outbound HTTP calls but no resilience handler was detected (Polly / AddStandardResilienceHandler / circuit-breaker). A slow or failing dependency will cascade — add timeouts, retries with back-off, and a circuit breaker.
What to do
- Add `AddStandardResilienceHandler()` (or Polly policies) to your HttpClient registrations so a flaky dependency can't take the app down.
P8 · Schema migrations
PF1 · Benchmark discipline
- No benchmark suite was found by the two searches this check runs. FIRST, a BenchmarkDotNet package reference in any project file — every project the workspace loaded, plus a walk of project files on disk that never loaded, because a benchmark suite is exactly the project a partial load drops. SECOND, a script harness: a file whose name contains `benchmark` and ends `.py`, `.sh`, `.ps1`, `.bash`, `.rb`, `.js` or `.mjs`, credited ONLY when this repository's CI text also mentions benchmarks — a harness no pipeline runs is read as a fixture, deliberately. Neither search can see a benchmark suite in another ecosystem's idiom (a Go `testing.B` file, a JMH or criterion project, a pytest-benchmark run), so this is 'no benchmark found by those two searches', not a verdict that the repository has none. Where code is performance-sensitive, a benchmark guards against silent regressions — but it's a bonus here, not a deduction.
What to do
- Add a benchmarking harness for the hot paths and run it in CI to catch regressions (for .NET, a BenchmarkDotNet project with [MemoryDiagnoser] to track allocations).
PF3 · Async & latency hygiene
S1 · Web-Security Posture
- None of the 11 security response headers the OWASP Secure Headers Project recommends (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options, …) is configured — defense in depth, even when a reverse proxy could set them. (−2.0 on this card.)
- 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/Presentation/Program.cs:4
What to do
- Add security response headers (Content-Security-Policy first, then Strict-Transport-Security, X-Content-Type-Options and a frame policy) — defense in depth, even when a reverse proxy could set them.
X1 · Async correctness
X12 · Unreachable branch
X13 · Undrained process stream
X14 · Bypassable address classification
X15 · Unvalidated length from an untrusted reader
X16 · Unfloored truncation loop
X17 · Uncapped recursion over a caller-supplied document
X18 · Disposal-pattern correctness
X19 · Unrestored process-global state
X2 · Cancellation propagation
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.2 `!` suppressions per 1k syntax nodes — 3 suppression(s) across the 15033 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 | 86% | Exemplary | Strongest area. |
| Architecture | 75% | Strong | Solid. |
| Maturity | 68% | Adequate — gated by M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 49% | Adequate — gated by P5, P7 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 85% | Adequate — gated by D29 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Performance | 77% | Strong | Solid. |
Unscored — 1 check(s) recorded observations but carry no score
- X7 Silent fallback defaults — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 3 control(s) we could not find positive evidence for
- C3 Audit Trail — Repo shows no audit-logging mechanism (IAuditable, an immutable audit log, an EF SaveChanges interceptor) for sensitive changes — absence of evidence is not evidence of a working control. Record an audit trail in code (or document where it lives) so this dimension can be scored.
- C4 Data Retention — Repo shows no data-retention / TTL / cleanup mechanism for personal data — absence of evidence is not evidence of a working control. Define retention periods and a purge/cleanup job (or TTL) in code, or document where retention is enforced, so this dimension can be scored.
- C5 Data-Subject Rights — Repo shows no corroborated data-subject-rights mechanism (erasure / export-portability / consent) tied to a subject id or GDPR vocabulary — absence of evidence is not evidence of a working control. Implement erasure, data export/portability and consent tracking over the subject's records.
Not included — 40 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.
- AX4 Dependency direction — not applicable to a CQRS architecture (the inward-dependency rule is for layered/clean styles)
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXR1 Runtime accessibility — compose up failed (exit 1 — a container did not start, exited, or never became healthy) — api Built container .-api-1 is unhealthy; runtime evidence skipped This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
- C1 Data Protection — This is a dotnet-new template — at-rest encryption and key-vaulting are deferred to the application you build from it. Add ASP.NET Data Protection / column encryption + a key vault for your real data store when you productionise.
- D11 Test Reliability — Test reliability not measured — no test run produced results
- D12 Dependency Hygiene — Dependency hygiene not measured
- D16 Bus Factor — single-maintainer repository — bus factor is not applicable
- D20 ADR Quality — N/A — this repo declares itself a template / kata / sample / demo; a formal ADR log is deferred to a real application built from it.
- D21 Naming Consistency — Naming consistency is measured on C# and TypeScript only; Python not measured.
- D22 Internal API Consistency — No intentionally-exposed public API to evaluate for consistency.
- D23 Boundary Type-Coupling — small single-context codebase (2,493 production LoC in the .NET projects) — bounded contexts are not needed at this size No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D24 Comment Value — Too few judgeable comments (27 of at least 30); comment value is not applicable here.
- D25 ADR Conformance — no ADRs to check
- D30 Dependency Vulnerabilities — nuget: the solution did not restore on the analyzer's .NET SDK (an SDK/target-framework/restore mismatch, common for an older codebase), so there was no restored dependency graph to scan
- D32 Data Compliance (PII/GDPR) — 19 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
- D36 Supply-chain Provenance & Signing — This is a dotnet-new template — it produces no released artifact to attest. Supply-chain provenance, signing and SBOM are deferred to the application you build from it (add SLSA provenance / cosign signing / an SBOM in your app's release pipeline).
- D39 IL Efficiency — IL not measured — the analyzer's build of the target did not succeed
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D7 Architectural Integrity — no checkable ADRs and no dependency cycles — architectural integrity not assessed
- D8 Code Coverage — Coverage not measured
- DM1 Domain Modelling — applicable but not scored (2 of 3 signals for this style — below the bar we score at): 5 value object(s); 4 repository port(s) loading or saving an aggregate/entity
- ED1 Event-Driven — not scored — this repository shows only 1 of the 3 signals this lens looks for (12 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 — this card publishes what the CI gate does with the test inventory rather than grading it. The findings above are its output.
- 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.
- 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 — 32 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- NoWarnInCsproj template/template.csproj:19
- NoWarnInCsproj template/template.csproj:19
- NoWarnInCsproj src/Presentation/Presentation.csproj:12
- NoWarnInCsproj Directory.Build.props:20
- AnalyzerSeverityNone .editorconfig:417
- AnalyzerSeverityNone .editorconfig:418
- Namespace dependency cycle src/Application/Authors/Entities/Author.cs:12
- REDACTED
Serious — 24 finding(s)
- CoverageExclusion src/Application/DependencyInjection.cs:10
- CoverageExclusion src/Infrastructure/Databases/MovieReviews/Models/Author.cs:5
- CoverageExclusion src/Infrastructure/Databases/MovieReviews/Models/Entity.cs:5
- CoverageExclusion src/Infrastructure/Databases/MovieReviews/Models/Movie.cs:5
- CoverageExclusion src/Infrastructure/Databases/MovieReviews/Models/Review.cs:5
- CoverageExclusion src/Infrastructure/Databases/MovieReviews/MovieReviewsDbContextFactory.cs:11
- CoverageExclusion src/Presentation/Extensions/WebApplicationBuilderExtensions.cs:30
- CoverageExclusion src/Presentation/Extensions/WebApplicationExtensions.cs:16
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Stateful singleton: MovieReviewsDatabase src/Infrastructure/Databases/MovieReviews/MovieReviewsDatabase.cs:12
- report.command_summary (cyclomatic 33) REDACTED:468
- report.command_summary (cognitive 34) REDACTED:468
- report.render_tests (cognitive 22) REDACTED:140
- report.parse_coverage (cognitive 17) REDACTED:94
- REDACTED
- Duplicated block (8 lines × 2) src/Infrastructure/Databases/MovieReviews/Extensions/MovieReviewsDbContextExtensions.cs:143
- Duplicated block (5 lines × 2) src/Application/Authors/Queries/GetAuthors/GetAuthorsValidator.cs:9
- No DR/backup evidence
- Outbound HTTP without resilience
Minor — 8 finding(s)
- No security response headers detected
- No security response headers detected src/Presentation/Program.cs:4
- REDACTED
- No ADRs
- No changelog
- No performance benchmarks
- Null-forgiving operator (`!`) suppressions reduce the NRT score
- Silent fallback default on configuration miss src/Presentation/Authentication/AuthenticationSettings.cs:22
Minor — 2 finding(s)
- Mock framework: NSubstitute
- Mock framework: NSubstitute
Appendix B — Reproduction & audit trail
| Dimension | Tool | Version | Command | Findings | Raw output |
|---|---|---|---|---|---|
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-7e41bf51c73e4fd586a115af0dbfbab9/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-7e41bf51c73e4fd586a115af0dbfbab9/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/Infrastructure/Databases/MovieReviews/Migrations . | 29 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | nuget | — | nuget: not applicable — nuget: the solution did not restore on the analyzer's .NET SDK (an SDK/target-framework/restore mismatch, common for an older codebase), so there was no restored dependency graph to scan | 0 | — |
| D31 · IaC & Container Security | trivy | — | trivy config --format json --quiet . | 4 | artifacts/raw/trivy-config.json |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. semgrep could not parse 19 file(s) — `src/Application/Authors/Queries/GetAuthorById/GetAuthorByIdHandler.cs`, `src/Application/Authors/Queries/GetAuthors/GetAuthorsHandler.cs`, `src/Application/Common/Behaviours/LoggingBehaviour.cs`, `src/Application/Common/Behaviours/ValidationBehaviour.cs`, `src/Application/Common/Exceptions/NotFoundException.cs`, … (+14 more) — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real. | 0 | — |
| D36 · Supply-chain Provenance & Signing | provenance | — | provenance: not applicable — This is a dotnet-new template — it produces no released artifact to attest. Supply-chain provenance, signing and SBOM are deferred to the application you build from it (add SLSA provenance / cosign signing / an SBOM in your app's release pipeline). | 0 | — |
| 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-2e2162a53d474cc6af4613e0943a067b | 0 | artifacts/raw/osv-scanner.json |
Appendix C — Personal-data map
Name — 8 field(s)
- Author.FirstName src/Application/Authors/Entities/Author.cs:12
- Author.LastName src/Application/Authors/Entities/Author.cs:12
- AuthorSummary.FirstName src/Application/Authors/Entities/AuthorSummary.cs:11
- AuthorSummary.LastName src/Application/Authors/Entities/AuthorSummary.cs:11
- ReviewAuthor.FirstName src/Application/Authors/Entities/ReviewAuthor.cs:9
- ReviewAuthor.LastName src/Application/Authors/Entities/ReviewAuthor.cs:9
- Author.FirstName src/Infrastructure/Databases/MovieReviews/Models/Author.cs:8
- Author.LastName src/Infrastructure/Databases/MovieReviews/Models/Author.cs:10