Executive summary
onebeyond/monaco falls short of our standard for a template or a sample, in part because it has business objects holding another business object directly. It scores 52 out of 100 and is rated Adequate, and nine of its 25 critical findings are security problems.
Domain Modelling, at 47, is the weakest lens and counts most in the score. The best first steps are making business objects refer to each other by id and validating new business objects, each worth about 4 points. Raising Domain Modelling to 58 would lift the score to about 56.
Three known security holes in the packages the code depends on can be used by attackers. Three pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with, and two passwords or keys are open to anyone who can read the repository. Updating the vulnerable packages, pinning each tool to an exact version and replacing each exposed password or key would close these risks. Limiting each secret to its own step would fix the secret exposed to more of the pipeline than needed. Referring to the other business object by its identifier would take care of the six business objects holding another business object directly.
The product code is 5,537 lines, about €26,000 to rebuild.
If Domain Modelling rose from 47 to 58, the lowest score rated Strong, the score would rise from 52 to about 56.
New since the last survey: 9 findings
- Cyclomatic Complexity · FilterExtensions.ValidateDataType (cyclomatic 23) src/Content/Backend/Solution/Monaco.Template.Backend.Common.Infrastructure/Context/Extensions/FilterExtensions.cs
- Code Duplication · Duplicated block (11–19 lines × 2) src/Content/Backend/Solution/Monaco.Template.Backend.Api/Program.cs
- Event/command shape · Command with 3 handlers: Command src/Content/Backend/Solution/Monaco.Template.Backend.Application/Features/Company/CreateCompany.cs
- Event/command shape · Command with 4 handlers: Command src/Content/Backend/Solution/Monaco.Template.Backend.Application/Features/Product/CreateProduct.cs
- CQS / query purity · Query handler writes persistent state one call away, in .Map: Company.Handler src/Content/Backend/Solution/Monaco.Template.Backend.Application/Features/Company/GetCompanyById.cs
- CQS / query purity · Query handler writes persistent state one call away, in .Map: Company.Handler src/Content/Backend/Solution/Monaco.Template.Backend.Application/Features/Company/GetCompanyPage.cs
- CQS / query purity · Query handler writes persistent state 2 calls away, in .Map: Product.Handler src/Content/Backend/Solution/Monaco.Template.Backend.Application/Features/Product/GetProductById.cs
- CQS / query purity · Query handler writes persistent state 2 calls away, in .Map: Product.Handler src/Content/Backend/Solution/Monaco.Template.Backend.Application/Features/Product/GetProductPage.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/Content/Backend/Solution/Monaco.Template.Backend.Common.Infrastructure/Context/BaseDbContext.cs
Fixed since the last survey: 16 findings
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/Content/Backend/Solution/Monaco.Template.Backend.Common.Infrastructure/Context/BaseDbContext.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/Content/Backend/Solution/Monaco.Template.Backend.Common.Infrastructure/Context/BaseDbContext.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/Content/Backend/Solution/Monaco.Template.Backend.Common.Infrastructure/Context/Extensions/MediatorExtension.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/Content/Backend/Solution/Monaco.Template.Backend.Common.Infrastructure/Context/Extensions/OperationsExtensions.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/Content/Backend/Solution/Monaco.Template.Backend.Common.Infrastructure/Context/Extensions/OperationsExtensions.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/Content/Backend/Solution/Monaco.Template.Backend.Common.Infrastructure/Context/Extensions/OperationsExtensions.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/Content/Backend/Solution/Monaco.Template.Backend.Common.Infrastructure/Context/Extensions/PagingExtensions.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/Content/Backend/Solution/Monaco.Template.Backend.Common.Infrastructure/Context/Extensions/PagingExtensions.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/Content/Backend/Solution/Monaco.Template.Backend.Common.Infrastructure/Context/Extensions/PagingExtensions.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/Content/Backend/Solution/Monaco.Template.Backend.Common.Infrastructure/Context/Extensions/SelectMapExtensions.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/Content/Backend/Solution/Monaco.Template.Backend.Common.Infrastructure/Context/Extensions/SelectMapExtensions.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/Content/Backend/Solution/Monaco.Template.Backend.Common.Infrastructure/Context/Extensions/SelectMapExtensions.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/Content/Backend/Solution/Monaco.Template.Backend.Common.Infrastructure/Context/Extensions/SelectMapExtensions.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/Content/Backend/Solution/Monaco.Template.Backend.Common.Infrastructure/Context/Extensions/SelectMapExtensions.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/Content/Backend/Solution/Monaco.Template.Backend.Common.Infrastructure/Context/Extensions/SelectMapExtensions.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/Content/Backend/Solution/Monaco.Template.Backend.Common.Infrastructure/Context/Extensions/SelectMapExtensions.cs
Rebuild cost: about €26,000 · Estimate
| Cost to rebuild | €8,500 to €43,000, for 141 to 449 hours of work, about 0.2 person-years for one engineer |
|---|---|
| Difficulty of the problem | Very high, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.7 at a score of 52. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it. |
| Size | Small: 5,537 lines of product code, of which 33% is declarations and boilerplate, 56% straight logic and 11% logic with branches |
| What it is not | Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one. |
Top priorities
Diagnosis: what the measurements show together
Architecture — bounded-context dependency graph
Architecture: which parts of the code depend on which
| uses → | 1 (global) | 2 Monaco.Template.Backend.Api | 3 Monaco.Template.Backend.Api.DTOs | 4 Monaco.Template.Backend.Application.Features.Country.DTOs | 5 Monaco.Template.Backend.Application.Features.File.DTOs | 6 Monaco.Template.Backend.Common.Application.Commands | 7 Monaco.Template.Backend.Common.Application.DTOs | 8 Monaco.Template.Backend.Common.Domain.Model | 9 Monaco.Template.Backend.Common.Domain.Model.Contracts | 10 Monaco.Template.Backend.Common.Infrastructure.Context.AuditTrail | 11 Monaco.Template.Backend.Common.Infrastructure.Context.Contracts | 12 Monaco.Template.Backend.Messages.V1 | 13 Monaco.Template.Backend.Application.Features.Company.DTOs | 14 Monaco.Template.Backend.Common.Application.Queries | 15 Monaco.Template.Backend.Common.BlobStorage | 16 Monaco.Template.Backend.Common.Infrastructure.Context | 17 Monaco.Template.Backend.Common.Infrastructure.Context.Extensions | 18 Monaco.Template.Backend.Domain.Model.ValueObjects | 19 Monaco.Template.Backend.Worker.Consumers | 20 Monaco.Template.Backend.Application.Features.Product.DTOs | 21 Monaco.Template.Backend.Application.Persistence | 22 Monaco.Template.Backend.Common.Api.Application | 23 Monaco.Template.Backend.Common.Application.Commands.Behaviors | 24 Monaco.Template.Backend.Common.Application.Queries.Extensions | 25 Monaco.Template.Backend.Common.Application.Validators.Extensions | 26 Monaco.Template.Backend.Common.BlobStorage.Contracts | 27 Monaco.Template.Backend.Common.BlobStorage.Extensions | 28 Monaco.Template.Backend.Domain.Model.Entities | 29 Monaco.Template.Backend.Application.Features.Company | 30 Monaco.Template.Backend.Application.Features.Country | 31 Monaco.Template.Backend.Application.Features.Country.Extensions | 32 Monaco.Template.Backend.Application.Features.File.Extensions | 33 Monaco.Template.Backend.Application.Features.Product | 34 Monaco.Template.Backend.Application.Features.Product.Extensions | 35 Monaco.Template.Backend.Application.Persistence.EntityConfigurations | 36 Monaco.Template.Backend.Application.Services.Contracts | 37 Monaco.Template.Backend.Api.DTOs.Extensions | 38 Monaco.Template.Backend.Application.Features.Company.Extensions | 39 Monaco.Template.Backend.Application.Features.File | 40 Monaco.Template.Backend.Application.Services |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 (global) | ||||||||||||||||||||||||||||||||||||||||
| 2 Monaco.Template.Backend.Api | ||||||||||||||||||||||||||||||||||||||||
| 3 Monaco.Template.Backend.Api.DTOs | ||||||||||||||||||||||||||||||||||||||||
| 4 Monaco.Template.Backend.Application.Features.Country.DTOs | ||||||||||||||||||||||||||||||||||||||||
| 5 Monaco.Template.Backend.Application.Features.File.DTOs | ||||||||||||||||||||||||||||||||||||||||
| 6 Monaco.Template.Backend.Common.Application.Commands | ||||||||||||||||||||||||||||||||||||||||
| 7 Monaco.Template.Backend.Common.Application.DTOs | ||||||||||||||||||||||||||||||||||||||||
| 8 Monaco.Template.Backend.Common.Domain.Model | ||||||||||||||||||||||||||||||||||||||||
| 9 Monaco.Template.Backend.Common.Domain.Model.Contracts | ||||||||||||||||||||||||||||||||||||||||
| 10 Monaco.Template.Backend.Common.Infrastructure.Context.AuditTrail | ||||||||||||||||||||||||||||||||||||||||
| 11 Monaco.Template.Backend.Common.Infrastructure.Context.Contracts | ||||||||||||||||||||||||||||||||||||||||
| 12 Monaco.Template.Backend.Messages.V1 | ||||||||||||||||||||||||||||||||||||||||
| 13 Monaco.Template.Backend.Application.Features.Company.DTOs | 1 | |||||||||||||||||||||||||||||||||||||||
| 14 Monaco.Template.Backend.Common.Application.Queries | 1 | |||||||||||||||||||||||||||||||||||||||
| 15 Monaco.Template.Backend.Common.BlobStorage | 1 | |||||||||||||||||||||||||||||||||||||||
| 16 Monaco.Template.Backend.Common.Infrastructure.Context | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 17 Monaco.Template.Backend.Common.Infrastructure.Context.Extensions | 1 | |||||||||||||||||||||||||||||||||||||||
| 18 Monaco.Template.Backend.Domain.Model.ValueObjects | 3 | 1 | ||||||||||||||||||||||||||||||||||||||
| 19 Monaco.Template.Backend.Worker.Consumers | 1 | |||||||||||||||||||||||||||||||||||||||
| 20 Monaco.Template.Backend.Application.Features.Product.DTOs | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 21 Monaco.Template.Backend.Application.Persistence | 1 | |||||||||||||||||||||||||||||||||||||||
| 22 Monaco.Template.Backend.Common.Api.Application | 2 | 2 | 8 | |||||||||||||||||||||||||||||||||||||
| 23 Monaco.Template.Backend.Common.Application.Commands.Behaviors | 3 | 1 | ||||||||||||||||||||||||||||||||||||||
| 24 Monaco.Template.Backend.Common.Application.Queries.Extensions | 1 | 4 | 2 | |||||||||||||||||||||||||||||||||||||
| 25 Monaco.Template.Backend.Common.Application.Validators.Extensions | 2 | |||||||||||||||||||||||||||||||||||||||
| 26 Monaco.Template.Backend.Common.BlobStorage.Contracts | 1 | |||||||||||||||||||||||||||||||||||||||
| 27 Monaco.Template.Backend.Common.BlobStorage.Extensions | 2 | |||||||||||||||||||||||||||||||||||||||
| 28 Monaco.Template.Backend.Domain.Model.Entities | 4 | 1 | 3 | |||||||||||||||||||||||||||||||||||||
| 29 Monaco.Template.Backend.Application.Features.Company | 2 | 1 | 1 | 2 | ||||||||||||||||||||||||||||||||||||
| 30 Monaco.Template.Backend.Application.Features.Country | 2 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 31 Monaco.Template.Backend.Application.Features.Country.Extensions | 2 | 1 | ||||||||||||||||||||||||||||||||||||||
| 32 Monaco.Template.Backend.Application.Features.File.Extensions | 2 | 1 | ||||||||||||||||||||||||||||||||||||||
| 33 Monaco.Template.Backend.Application.Features.Product | 2 | 1 | 1 | 2 | ||||||||||||||||||||||||||||||||||||
| 34 Monaco.Template.Backend.Application.Features.Product.Extensions | 1 | 2 | 1 | 3 | ||||||||||||||||||||||||||||||||||||
| 35 Monaco.Template.Backend.Application.Persistence.EntityConfigurations | 6 | |||||||||||||||||||||||||||||||||||||||
| 36 Monaco.Template.Backend.Application.Services.Contracts | 1 | 3 | ||||||||||||||||||||||||||||||||||||||
| 37 Monaco.Template.Backend.Api.DTOs.Extensions | 2 | 2 | 1 | |||||||||||||||||||||||||||||||||||||
| 38 Monaco.Template.Backend.Application.Features.Company.Extensions | 2 | 2 | 1 | |||||||||||||||||||||||||||||||||||||
| 39 Monaco.Template.Backend.Application.Features.File | 2 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 40 Monaco.Template.Backend.Application.Services | 1 | 1 | 3 | 1 |
13→4 Monaco.Template.Backend.Application.Features.Company.DTOs uses Monaco.Template.Backend.Application.Features.Country.DTOs✕
- Connections
- 1 pair of types, where a type in Monaco.Template.Backend.Application.Features.Company.DTOs uses a type in Monaco.Template.Backend.Application.Features.Country.DTOs.
- The types involved
Monaco.Template.Backend.Application.Features.Company.DTOs.CompanyDto→Monaco.Template.Backend.Application.Features.Country.DTOs.CountryDto
- Direction
- Monaco.Template.Backend.Application.Features.Company.DTOs uses Monaco.Template.Backend.Application.Features.Country.DTOs, so a change to Monaco.Template.Backend.Application.Features.Country.DTOs can break Monaco.Template.Backend.Application.Features.Company.DTOs, while a change to Monaco.Template.Backend.Application.Features.Company.DTOs can't break Monaco.Template.Backend.Application.Features.Country.DTOs.
- Position
- Below the diagonal: Monaco.Template.Backend.Application.Features.Company.DTOs uses a module listed above it, which is the healthy direction.
14→8 Monaco.Template.Backend.Common.Application.Queries uses Monaco.Template.Backend.Common.Domain.Model✕
- Connections
- 1 pair of types, where a type in Monaco.Template.Backend.Common.Application.Queries uses a type in Monaco.Template.Backend.Common.Domain.Model.
- The types involved
Monaco.Template.Backend.Common.Application.Queries.QueryPagedBase→Monaco.Template.Backend.Common.Domain.Model.Page
- Direction
- Monaco.Template.Backend.Common.Application.Queries uses Monaco.Template.Backend.Common.Domain.Model, so a change to Monaco.Template.Backend.Common.Domain.Model can break Monaco.Template.Backend.Common.Application.Queries, while a change to Monaco.Template.Backend.Common.Application.Queries can't break Monaco.Template.Backend.Common.Domain.Model.
- Position
- Below the diagonal: Monaco.Template.Backend.Common.Application.Queries uses a module listed above it, which is the healthy direction.
15→26 Monaco.Template.Backend.Common.BlobStorage uses Monaco.Template.Backend.Common.BlobStorage.Contracts part of a loop✕
- Connections
- 1 pair of types, where a type in Monaco.Template.Backend.Common.BlobStorage uses a type in Monaco.Template.Backend.Common.BlobStorage.Contracts.
- The types involved
Monaco.Template.Backend.Common.BlobStorage.BlobStorageService→Monaco.Template.Backend.Common.BlobStorage.Contracts.IBlobStorageService
- Direction
- Monaco.Template.Backend.Common.BlobStorage uses Monaco.Template.Backend.Common.BlobStorage.Contracts, so a change to Monaco.Template.Backend.Common.BlobStorage.Contracts can break Monaco.Template.Backend.Common.BlobStorage, while a change to Monaco.Template.Backend.Common.BlobStorage can't break Monaco.Template.Backend.Common.BlobStorage.Contracts.
- 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.
16→10 Monaco.Template.Backend.Common.Infrastructure.Context uses Monaco.Template.Backend.Common.Infrastructure.Context.AuditTrail✕
- Connections
- 1 pair of types, where a type in Monaco.Template.Backend.Common.Infrastructure.Context uses a type in Monaco.Template.Backend.Common.Infrastructure.Context.AuditTrail.
- The types involved
Monaco.Template.Backend.Common.Infrastructure.Context.BaseDbContext→Monaco.Template.Backend.Common.Infrastructure.Context.AuditTrail.AuditEntry
- Direction
- Monaco.Template.Backend.Common.Infrastructure.Context uses Monaco.Template.Backend.Common.Infrastructure.Context.AuditTrail, so a change to Monaco.Template.Backend.Common.Infrastructure.Context.AuditTrail can break Monaco.Template.Backend.Common.Infrastructure.Context, while a change to Monaco.Template.Backend.Common.Infrastructure.Context can't break Monaco.Template.Backend.Common.Infrastructure.Context.AuditTrail.
- Position
- Below the diagonal: Monaco.Template.Backend.Common.Infrastructure.Context uses a module listed above it, which is the healthy direction.
16→11 Monaco.Template.Backend.Common.Infrastructure.Context uses Monaco.Template.Backend.Common.Infrastructure.Context.Contracts✕
- Connections
- 1 pair of types, where a type in Monaco.Template.Backend.Common.Infrastructure.Context uses a type in Monaco.Template.Backend.Common.Infrastructure.Context.Contracts.
- The types involved
Monaco.Template.Backend.Common.Infrastructure.Context.BaseDbContext→Monaco.Template.Backend.Common.Infrastructure.Context.Contracts.IUnitOfWork
- Direction
- Monaco.Template.Backend.Common.Infrastructure.Context uses Monaco.Template.Backend.Common.Infrastructure.Context.Contracts, so a change to Monaco.Template.Backend.Common.Infrastructure.Context.Contracts can break Monaco.Template.Backend.Common.Infrastructure.Context, while a change to Monaco.Template.Backend.Common.Infrastructure.Context can't break Monaco.Template.Backend.Common.Infrastructure.Context.Contracts.
- Position
- Below the diagonal: Monaco.Template.Backend.Common.Infrastructure.Context uses a module listed above it, which is the healthy direction.
17→8 Monaco.Template.Backend.Common.Infrastructure.Context.Extensions uses Monaco.Template.Backend.Common.Domain.Model✕
- Connections
- 1 pair of types, where a type in Monaco.Template.Backend.Common.Infrastructure.Context.Extensions uses a type in Monaco.Template.Backend.Common.Domain.Model.
- The types involved
Monaco.Template.Backend.Common.Infrastructure.Context.Extensions.PagingExtensions→Monaco.Template.Backend.Common.Domain.Model.Page
- Direction
- Monaco.Template.Backend.Common.Infrastructure.Context.Extensions uses Monaco.Template.Backend.Common.Domain.Model, so a change to Monaco.Template.Backend.Common.Domain.Model can break Monaco.Template.Backend.Common.Infrastructure.Context.Extensions, while a change to Monaco.Template.Backend.Common.Infrastructure.Context.Extensions can't break Monaco.Template.Backend.Common.Domain.Model.
- Position
- Below the diagonal: Monaco.Template.Backend.Common.Infrastructure.Context.Extensions uses a module listed above it, which is the healthy direction.
18→8 Monaco.Template.Backend.Domain.Model.ValueObjects uses Monaco.Template.Backend.Common.Domain.Model✕
- Connections
- 3 pairs of types, where a type in Monaco.Template.Backend.Domain.Model.ValueObjects uses a type in Monaco.Template.Backend.Common.Domain.Model.
- The types involved
Monaco.Template.Backend.Domain.Model.ValueObjects.Address→Monaco.Template.Backend.Common.Domain.Model.ValueObjectMonaco.Template.Backend.Domain.Model.ValueObjects.GpsPosition→Monaco.Template.Backend.Common.Domain.Model.ValueObjectMonaco.Template.Backend.Domain.Model.ValueObjects.ImageDimensions→Monaco.Template.Backend.Common.Domain.Model.ValueObject
- Direction
- Monaco.Template.Backend.Domain.Model.ValueObjects uses Monaco.Template.Backend.Common.Domain.Model, so a change to Monaco.Template.Backend.Common.Domain.Model can break Monaco.Template.Backend.Domain.Model.ValueObjects, while a change to Monaco.Template.Backend.Domain.Model.ValueObjects can't break Monaco.Template.Backend.Common.Domain.Model.
- Position
- Below the diagonal: Monaco.Template.Backend.Domain.Model.ValueObjects uses a module listed above it, which is the healthy direction.
18→28 Monaco.Template.Backend.Domain.Model.ValueObjects uses Monaco.Template.Backend.Domain.Model.Entities part of a loop✕
- Connections
- 1 pair of types, where a type in Monaco.Template.Backend.Domain.Model.ValueObjects uses a type in Monaco.Template.Backend.Domain.Model.Entities.
- The types involved
Monaco.Template.Backend.Domain.Model.ValueObjects.Address→Monaco.Template.Backend.Domain.Model.Entities.Country
- Direction
- Monaco.Template.Backend.Domain.Model.ValueObjects uses Monaco.Template.Backend.Domain.Model.Entities, so a change to Monaco.Template.Backend.Domain.Model.Entities can break Monaco.Template.Backend.Domain.Model.ValueObjects, while a change to Monaco.Template.Backend.Domain.Model.ValueObjects can't break Monaco.Template.Backend.Domain.Model.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.
19→12 Monaco.Template.Backend.Worker.Consumers uses Monaco.Template.Backend.Messages.V1✕
- Connections
- 1 pair of types, where a type in Monaco.Template.Backend.Worker.Consumers uses a type in Monaco.Template.Backend.Messages.V1.
- The types involved
Monaco.Template.Backend.Worker.Consumers.OnProductCreatedThenLongRunningProcess→Monaco.Template.Backend.Messages.V1.ProductCreated
- Direction
- Monaco.Template.Backend.Worker.Consumers uses Monaco.Template.Backend.Messages.V1, so a change to Monaco.Template.Backend.Messages.V1 can break Monaco.Template.Backend.Worker.Consumers, while a change to Monaco.Template.Backend.Worker.Consumers can't break Monaco.Template.Backend.Messages.V1.
- Position
- Below the diagonal: Monaco.Template.Backend.Worker.Consumers uses a module listed above it, which is the healthy direction.
20→5 Monaco.Template.Backend.Application.Features.Product.DTOs uses Monaco.Template.Backend.Application.Features.File.DTOs✕
- Connections
- 1 pair of types, where a type in Monaco.Template.Backend.Application.Features.Product.DTOs uses a type in Monaco.Template.Backend.Application.Features.File.DTOs.
- The types involved
Monaco.Template.Backend.Application.Features.Product.DTOs.ProductDto→Monaco.Template.Backend.Application.Features.File.DTOs.ImageDto
- Direction
- Monaco.Template.Backend.Application.Features.Product.DTOs uses Monaco.Template.Backend.Application.Features.File.DTOs, so a change to Monaco.Template.Backend.Application.Features.File.DTOs can break Monaco.Template.Backend.Application.Features.Product.DTOs, while a change to Monaco.Template.Backend.Application.Features.Product.DTOs can't break Monaco.Template.Backend.Application.Features.File.DTOs.
- Position
- Below the diagonal: Monaco.Template.Backend.Application.Features.Product.DTOs uses a module listed above it, which is the healthy direction.
20→13 Monaco.Template.Backend.Application.Features.Product.DTOs uses Monaco.Template.Backend.Application.Features.Company.DTOs✕
- Connections
- 1 pair of types, where a type in Monaco.Template.Backend.Application.Features.Product.DTOs uses a type in Monaco.Template.Backend.Application.Features.Company.DTOs.
- The types involved
Monaco.Template.Backend.Application.Features.Product.DTOs.ProductDto→Monaco.Template.Backend.Application.Features.Company.DTOs.CompanyDto
- Direction
- Monaco.Template.Backend.Application.Features.Product.DTOs uses Monaco.Template.Backend.Application.Features.Company.DTOs, so a change to Monaco.Template.Backend.Application.Features.Company.DTOs can break Monaco.Template.Backend.Application.Features.Product.DTOs, while a change to Monaco.Template.Backend.Application.Features.Product.DTOs can't break Monaco.Template.Backend.Application.Features.Company.DTOs.
- Position
- Below the diagonal: Monaco.Template.Backend.Application.Features.Product.DTOs uses a module listed above it, which is the healthy direction.
21→16 Monaco.Template.Backend.Application.Persistence uses Monaco.Template.Backend.Common.Infrastructure.Context✕
- Connections
- 1 pair of types, where a type in Monaco.Template.Backend.Application.Persistence uses a type in Monaco.Template.Backend.Common.Infrastructure.Context.
- The types involved
Monaco.Template.Backend.Application.Persistence.AppDbContext→Monaco.Template.Backend.Common.Infrastructure.Context.BaseDbContext
- Direction
- Monaco.Template.Backend.Application.Persistence uses Monaco.Template.Backend.Common.Infrastructure.Context, so a change to Monaco.Template.Backend.Common.Infrastructure.Context can break Monaco.Template.Backend.Application.Persistence, while a change to Monaco.Template.Backend.Application.Persistence can't break Monaco.Template.Backend.Common.Infrastructure.Context.
- Position
- Below the diagonal: Monaco.Template.Backend.Application.Persistence uses a module listed above it, which is the healthy direction.
22→6 Monaco.Template.Backend.Common.Api.Application uses Monaco.Template.Backend.Common.Application.Commands✕
- Connections
- 2 pairs of types, where a type in Monaco.Template.Backend.Common.Api.Application uses a type in Monaco.Template.Backend.Common.Application.Commands.
- The types involved
Monaco.Template.Backend.Common.Api.Application.→Monaco.Template.Backend.Common.Application.Commands.CommandBaseMonaco.Template.Backend.Common.Api.Application.MediatorExtensions→Monaco.Template.Backend.Common.Application.Commands.CommandBase
- Direction
- Monaco.Template.Backend.Common.Api.Application uses Monaco.Template.Backend.Common.Application.Commands, so a change to Monaco.Template.Backend.Common.Application.Commands can break Monaco.Template.Backend.Common.Api.Application, while a change to Monaco.Template.Backend.Common.Api.Application can't break Monaco.Template.Backend.Common.Application.Commands.
- Position
- Below the diagonal: Monaco.Template.Backend.Common.Api.Application uses a module listed above it, which is the healthy direction.
22→8 Monaco.Template.Backend.Common.Api.Application uses Monaco.Template.Backend.Common.Domain.Model✕
- Connections
- 2 pairs of types, where a type in Monaco.Template.Backend.Common.Api.Application uses a type in Monaco.Template.Backend.Common.Domain.Model.
- The types involved
Monaco.Template.Backend.Common.Api.Application.→Monaco.Template.Backend.Common.Domain.Model.PageMonaco.Template.Backend.Common.Api.Application.MediatorExtensions→Monaco.Template.Backend.Common.Domain.Model.Page
- Direction
- Monaco.Template.Backend.Common.Api.Application uses Monaco.Template.Backend.Common.Domain.Model, so a change to Monaco.Template.Backend.Common.Domain.Model can break Monaco.Template.Backend.Common.Api.Application, while a change to Monaco.Template.Backend.Common.Api.Application can't break Monaco.Template.Backend.Common.Domain.Model.
- Position
- Below the diagonal: Monaco.Template.Backend.Common.Api.Application uses a module listed above it, which is the healthy direction.
22→14 Monaco.Template.Backend.Common.Api.Application uses Monaco.Template.Backend.Common.Application.Queries✕
- Connections
- 8 pairs of types, where a type in Monaco.Template.Backend.Common.Api.Application uses a type in Monaco.Template.Backend.Common.Application.Queries.
- The types involved
Monaco.Template.Backend.Common.Api.Application.→Monaco.Template.Backend.Common.Application.Queries.QueryBaseMonaco.Template.Backend.Common.Api.Application.→Monaco.Template.Backend.Common.Application.Queries.QueryByIdBaseMonaco.Template.Backend.Common.Api.Application.→Monaco.Template.Backend.Common.Application.Queries.QueryByKeyBaseMonaco.Template.Backend.Common.Api.Application.→Monaco.Template.Backend.Common.Application.Queries.QueryPagedBaseMonaco.Template.Backend.Common.Api.Application.MediatorExtensions→Monaco.Template.Backend.Common.Application.Queries.QueryBaseMonaco.Template.Backend.Common.Api.Application.MediatorExtensions→Monaco.Template.Backend.Common.Application.Queries.QueryByIdBaseMonaco.Template.Backend.Common.Api.Application.MediatorExtensions→Monaco.Template.Backend.Common.Application.Queries.QueryByKeyBaseMonaco.Template.Backend.Common.Api.Application.MediatorExtensions→Monaco.Template.Backend.Common.Application.Queries.QueryPagedBase
- Direction
- Monaco.Template.Backend.Common.Api.Application uses Monaco.Template.Backend.Common.Application.Queries, so a change to Monaco.Template.Backend.Common.Application.Queries can break Monaco.Template.Backend.Common.Api.Application, while a change to Monaco.Template.Backend.Common.Api.Application can't break Monaco.Template.Backend.Common.Application.Queries.
- Position
- Below the diagonal: Monaco.Template.Backend.Common.Api.Application uses a module listed above it, which is the healthy direction.
23→6 Monaco.Template.Backend.Common.Application.Commands.Behaviors uses Monaco.Template.Backend.Common.Application.Commands✕
- Connections
- 3 pairs of types, where a type in Monaco.Template.Backend.Common.Application.Commands.Behaviors uses a type in Monaco.Template.Backend.Common.Application.Commands.
- The types involved
Monaco.Template.Backend.Common.Application.Commands.Behaviors.CommandValidationBehavior→Monaco.Template.Backend.Common.Application.Commands.CommandResultMonaco.Template.Backend.Common.Application.Commands.Behaviors.CommandValidationExistsBehavior→Monaco.Template.Backend.Common.Application.Commands.CommandResultMonaco.Template.Backend.Common.Application.Commands.Behaviors.ConcurrencyExceptionBehavior→Monaco.Template.Backend.Common.Application.Commands.CommandResult
- Direction
- Monaco.Template.Backend.Common.Application.Commands.Behaviors uses Monaco.Template.Backend.Common.Application.Commands, so a change to Monaco.Template.Backend.Common.Application.Commands can break Monaco.Template.Backend.Common.Application.Commands.Behaviors, while a change to Monaco.Template.Backend.Common.Application.Commands.Behaviors can't break Monaco.Template.Backend.Common.Application.Commands.
- Position
- Below the diagonal: Monaco.Template.Backend.Common.Application.Commands.Behaviors uses a module listed above it, which is the healthy direction.
23→16 Monaco.Template.Backend.Common.Application.Commands.Behaviors uses Monaco.Template.Backend.Common.Infrastructure.Context✕
- Connections
- 1 pair of types, where a type in Monaco.Template.Backend.Common.Application.Commands.Behaviors uses a type in Monaco.Template.Backend.Common.Infrastructure.Context.
- The types involved
Monaco.Template.Backend.Common.Application.Commands.Behaviors.ConcurrencyExceptionBehavior→Monaco.Template.Backend.Common.Infrastructure.Context.BaseDbContext
- Direction
- Monaco.Template.Backend.Common.Application.Commands.Behaviors uses Monaco.Template.Backend.Common.Infrastructure.Context, so a change to Monaco.Template.Backend.Common.Infrastructure.Context can break Monaco.Template.Backend.Common.Application.Commands.Behaviors, while a change to Monaco.Template.Backend.Common.Application.Commands.Behaviors can't break Monaco.Template.Backend.Common.Infrastructure.Context.
- Position
- Below the diagonal: Monaco.Template.Backend.Common.Application.Commands.Behaviors uses a module listed above it, which is the healthy direction.
24→8 Monaco.Template.Backend.Common.Application.Queries.Extensions uses Monaco.Template.Backend.Common.Domain.Model✕
- Connections
- 1 pair of types, where a type in Monaco.Template.Backend.Common.Application.Queries.Extensions uses a type in Monaco.Template.Backend.Common.Domain.Model.
- The types involved
Monaco.Template.Backend.Common.Application.Queries.Extensions.QueryExtensions→Monaco.Template.Backend.Common.Domain.Model.Page
- Direction
- Monaco.Template.Backend.Common.Application.Queries.Extensions uses Monaco.Template.Backend.Common.Domain.Model, so a change to Monaco.Template.Backend.Common.Domain.Model can break Monaco.Template.Backend.Common.Application.Queries.Extensions, while a change to Monaco.Template.Backend.Common.Application.Queries.Extensions can't break Monaco.Template.Backend.Common.Domain.Model.
- Position
- Below the diagonal: Monaco.Template.Backend.Common.Application.Queries.Extensions uses a module listed above it, which is the healthy direction.
24→14 Monaco.Template.Backend.Common.Application.Queries.Extensions uses Monaco.Template.Backend.Common.Application.Queries✕
- Connections
- 4 pairs of types, where a type in Monaco.Template.Backend.Common.Application.Queries.Extensions uses a type in Monaco.Template.Backend.Common.Application.Queries.
- The types involved
Monaco.Template.Backend.Common.Application.Queries.Extensions.→Monaco.Template.Backend.Common.Application.Queries.QueryBaseMonaco.Template.Backend.Common.Application.Queries.Extensions.QueryExtensions→Monaco.Template.Backend.Common.Application.Queries.QueryBaseMonaco.Template.Backend.Common.Application.Queries.Extensions.QueryExtensions→Monaco.Template.Backend.Common.Application.Queries.QueryByIdBaseMonaco.Template.Backend.Common.Application.Queries.Extensions.QueryExtensions→Monaco.Template.Backend.Common.Application.Queries.QueryPagedBase
- Direction
- Monaco.Template.Backend.Common.Application.Queries.Extensions uses Monaco.Template.Backend.Common.Application.Queries, so a change to Monaco.Template.Backend.Common.Application.Queries can break Monaco.Template.Backend.Common.Application.Queries.Extensions, while a change to Monaco.Template.Backend.Common.Application.Queries.Extensions can't break Monaco.Template.Backend.Common.Application.Queries.
- Position
- Below the diagonal: Monaco.Template.Backend.Common.Application.Queries.Extensions uses a module listed above it, which is the healthy direction.
24→16 Monaco.Template.Backend.Common.Application.Queries.Extensions uses Monaco.Template.Backend.Common.Infrastructure.Context✕
- Connections
- 2 pairs of types, where a type in Monaco.Template.Backend.Common.Application.Queries.Extensions uses a type in Monaco.Template.Backend.Common.Infrastructure.Context.
- The types involved
Monaco.Template.Backend.Common.Application.Queries.Extensions.→Monaco.Template.Backend.Common.Infrastructure.Context.BaseDbContextMonaco.Template.Backend.Common.Application.Queries.Extensions.QueryExtensions→Monaco.Template.Backend.Common.Infrastructure.Context.BaseDbContext
- Direction
- Monaco.Template.Backend.Common.Application.Queries.Extensions uses Monaco.Template.Backend.Common.Infrastructure.Context, so a change to Monaco.Template.Backend.Common.Infrastructure.Context can break Monaco.Template.Backend.Common.Application.Queries.Extensions, while a change to Monaco.Template.Backend.Common.Application.Queries.Extensions can't break Monaco.Template.Backend.Common.Infrastructure.Context.
- Position
- Below the diagonal: Monaco.Template.Backend.Common.Application.Queries.Extensions uses a module listed above it, which is the healthy direction.
25→16 Monaco.Template.Backend.Common.Application.Validators.Extensions uses Monaco.Template.Backend.Common.Infrastructure.Context✕
- Connections
- 2 pairs of types, where a type in Monaco.Template.Backend.Common.Application.Validators.Extensions uses a type in Monaco.Template.Backend.Common.Infrastructure.Context.
- The types involved
Monaco.Template.Backend.Common.Application.Validators.Extensions.→Monaco.Template.Backend.Common.Infrastructure.Context.BaseDbContextMonaco.Template.Backend.Common.Application.Validators.Extensions.ValidatorsExtensions→Monaco.Template.Backend.Common.Infrastructure.Context.BaseDbContext
- Direction
- Monaco.Template.Backend.Common.Application.Validators.Extensions uses Monaco.Template.Backend.Common.Infrastructure.Context, so a change to Monaco.Template.Backend.Common.Infrastructure.Context can break Monaco.Template.Backend.Common.Application.Validators.Extensions, while a change to Monaco.Template.Backend.Common.Application.Validators.Extensions can't break Monaco.Template.Backend.Common.Infrastructure.Context.
- Position
- Below the diagonal: Monaco.Template.Backend.Common.Application.Validators.Extensions uses a module listed above it, which is the healthy direction.
26→15 Monaco.Template.Backend.Common.BlobStorage.Contracts uses Monaco.Template.Backend.Common.BlobStorage✕
- Connections
- 1 pair of types, where a type in Monaco.Template.Backend.Common.BlobStorage.Contracts uses a type in Monaco.Template.Backend.Common.BlobStorage.
- The types involved
Monaco.Template.Backend.Common.BlobStorage.Contracts.IBlobStorageService→Monaco.Template.Backend.Common.BlobStorage.FileTypeEnum
- Direction
- Monaco.Template.Backend.Common.BlobStorage.Contracts uses Monaco.Template.Backend.Common.BlobStorage, so a change to Monaco.Template.Backend.Common.BlobStorage can break Monaco.Template.Backend.Common.BlobStorage.Contracts, while a change to Monaco.Template.Backend.Common.BlobStorage.Contracts can't break Monaco.Template.Backend.Common.BlobStorage.
- Position
- Below the diagonal: Monaco.Template.Backend.Common.BlobStorage.Contracts uses a module listed above it, which is the healthy direction.
27→15 Monaco.Template.Backend.Common.BlobStorage.Extensions uses Monaco.Template.Backend.Common.BlobStorage✕
- Connections
- 2 pairs of types, where a type in Monaco.Template.Backend.Common.BlobStorage.Extensions uses a type in Monaco.Template.Backend.Common.BlobStorage.
- The types involved
Monaco.Template.Backend.Common.BlobStorage.Extensions.→Monaco.Template.Backend.Common.BlobStorage.BlobStorageServiceOptionsMonaco.Template.Backend.Common.BlobStorage.Extensions.ServiceCollectionExtensions→Monaco.Template.Backend.Common.BlobStorage.BlobStorageServiceOptions
- Direction
- Monaco.Template.Backend.Common.BlobStorage.Extensions uses Monaco.Template.Backend.Common.BlobStorage, so a change to Monaco.Template.Backend.Common.BlobStorage can break Monaco.Template.Backend.Common.BlobStorage.Extensions, while a change to Monaco.Template.Backend.Common.BlobStorage.Extensions can't break Monaco.Template.Backend.Common.BlobStorage.
- Position
- Below the diagonal: Monaco.Template.Backend.Common.BlobStorage.Extensions uses a module listed above it, which is the healthy direction.
28→8 Monaco.Template.Backend.Domain.Model.Entities uses Monaco.Template.Backend.Common.Domain.Model✕
- Connections
- 4 pairs of types, where a type in Monaco.Template.Backend.Domain.Model.Entities uses a type in Monaco.Template.Backend.Common.Domain.Model.
- The types involved
Monaco.Template.Backend.Domain.Model.Entities.Company→Monaco.Template.Backend.Common.Domain.Model.AggregateRootMonaco.Template.Backend.Domain.Model.Entities.Country→Monaco.Template.Backend.Common.Domain.Model.AggregateRootMonaco.Template.Backend.Domain.Model.Entities.File→Monaco.Template.Backend.Common.Domain.Model.AggregateRootMonaco.Template.Backend.Domain.Model.Entities.Product→Monaco.Template.Backend.Common.Domain.Model.AggregateRoot
- Direction
- Monaco.Template.Backend.Domain.Model.Entities uses Monaco.Template.Backend.Common.Domain.Model, so a change to Monaco.Template.Backend.Common.Domain.Model can break Monaco.Template.Backend.Domain.Model.Entities, while a change to Monaco.Template.Backend.Domain.Model.Entities can't break Monaco.Template.Backend.Common.Domain.Model.
- Position
- Below the diagonal: Monaco.Template.Backend.Domain.Model.Entities uses a module listed above it, which is the healthy direction.
28→9 Monaco.Template.Backend.Domain.Model.Entities uses Monaco.Template.Backend.Common.Domain.Model.Contracts✕
- Connections
- 1 pair of types, where a type in Monaco.Template.Backend.Domain.Model.Entities uses a type in Monaco.Template.Backend.Common.Domain.Model.Contracts.
- The types involved
Monaco.Template.Backend.Domain.Model.Entities.Country→Monaco.Template.Backend.Common.Domain.Model.Contracts.IReferential
- Direction
- Monaco.Template.Backend.Domain.Model.Entities uses Monaco.Template.Backend.Common.Domain.Model.Contracts, so a change to Monaco.Template.Backend.Common.Domain.Model.Contracts can break Monaco.Template.Backend.Domain.Model.Entities, while a change to Monaco.Template.Backend.Domain.Model.Entities can't break Monaco.Template.Backend.Common.Domain.Model.Contracts.
- Position
- Below the diagonal: Monaco.Template.Backend.Domain.Model.Entities uses a module listed above it, which is the healthy direction.
28→18 Monaco.Template.Backend.Domain.Model.Entities uses Monaco.Template.Backend.Domain.Model.ValueObjects✕
- Connections
- 3 pairs of types, where a type in Monaco.Template.Backend.Domain.Model.Entities uses a type in Monaco.Template.Backend.Domain.Model.ValueObjects.
- The types involved
Monaco.Template.Backend.Domain.Model.Entities.Company→Monaco.Template.Backend.Domain.Model.ValueObjects.AddressMonaco.Template.Backend.Domain.Model.Entities.Image→Monaco.Template.Backend.Domain.Model.ValueObjects.GpsPositionMonaco.Template.Backend.Domain.Model.Entities.Image→Monaco.Template.Backend.Domain.Model.ValueObjects.ImageDimensions
- Direction
- Monaco.Template.Backend.Domain.Model.Entities uses Monaco.Template.Backend.Domain.Model.ValueObjects, so a change to Monaco.Template.Backend.Domain.Model.ValueObjects can break Monaco.Template.Backend.Domain.Model.Entities, while a change to Monaco.Template.Backend.Domain.Model.Entities can't break Monaco.Template.Backend.Domain.Model.ValueObjects.
- Position
- Below the diagonal: Monaco.Template.Backend.Domain.Model.Entities uses a module listed above it, which is the healthy direction.
29→6 Monaco.Template.Backend.Application.Features.Company uses Monaco.Template.Backend.Common.Application.Commands✕
- Connections
- 2 pairs of types, where a type in Monaco.Template.Backend.Application.Features.Company uses a type in Monaco.Template.Backend.Common.Application.Commands.
- The types involved
Monaco.Template.Backend.Application.Features.Company.Command→Monaco.Template.Backend.Common.Application.Commands.CommandBaseMonaco.Template.Backend.Application.Features.Company.Handler→Monaco.Template.Backend.Common.Application.Commands.CommandResult
- Direction
- Monaco.Template.Backend.Application.Features.Company uses Monaco.Template.Backend.Common.Application.Commands, so a change to Monaco.Template.Backend.Common.Application.Commands can break Monaco.Template.Backend.Application.Features.Company, while a change to Monaco.Template.Backend.Application.Features.Company can't break Monaco.Template.Backend.Common.Application.Commands.
- Position
- Below the diagonal: Monaco.Template.Backend.Application.Features.Company uses a module listed above it, which is the healthy direction.
29→13 Monaco.Template.Backend.Application.Features.Company uses Monaco.Template.Backend.Application.Features.Company.DTOs✕
- Connections
- 1 pair of types, where a type in Monaco.Template.Backend.Application.Features.Company uses a type in Monaco.Template.Backend.Application.Features.Company.DTOs.
- The types involved
Monaco.Template.Backend.Application.Features.Company.Query→Monaco.Template.Backend.Application.Features.Company.DTOs.CompanyDto
- Direction
- Monaco.Template.Backend.Application.Features.Company uses Monaco.Template.Backend.Application.Features.Company.DTOs, so a change to Monaco.Template.Backend.Application.Features.Company.DTOs can break Monaco.Template.Backend.Application.Features.Company, while a change to Monaco.Template.Backend.Application.Features.Company can't break Monaco.Template.Backend.Application.Features.Company.DTOs.
- Position
- Below the diagonal: Monaco.Template.Backend.Application.Features.Company uses a module listed above it, which is the healthy direction.
29→14 Monaco.Template.Backend.Application.Features.Company uses Monaco.Template.Backend.Common.Application.Queries✕
- Connections
- 1 pair of types, where a type in Monaco.Template.Backend.Application.Features.Company uses a type in Monaco.Template.Backend.Common.Application.Queries.
- The types involved
Monaco.Template.Backend.Application.Features.Company.Query→Monaco.Template.Backend.Common.Application.Queries.QueryByIdBase
- Direction
- Monaco.Template.Backend.Application.Features.Company uses Monaco.Template.Backend.Common.Application.Queries, so a change to Monaco.Template.Backend.Common.Application.Queries can break Monaco.Template.Backend.Application.Features.Company, while a change to Monaco.Template.Backend.Application.Features.Company can't break Monaco.Template.Backend.Common.Application.Queries.
- Position
- Below the diagonal: Monaco.Template.Backend.Application.Features.Company uses a module listed above it, which is the healthy direction.
29→21 Monaco.Template.Backend.Application.Features.Company uses Monaco.Template.Backend.Application.Persistence✕
- Connections
- 2 pairs of types, where a type in Monaco.Template.Backend.Application.Features.Company uses a type in Monaco.Template.Backend.Application.Persistence.
- The types involved
Monaco.Template.Backend.Application.Features.Company.Handler→Monaco.Template.Backend.Application.Persistence.AppDbContextMonaco.Template.Backend.Application.Features.Company.Validator→Monaco.Template.Backend.Application.Persistence.AppDbContext
- Direction
- Monaco.Template.Backend.Application.Features.Company uses Monaco.Template.Backend.Application.Persistence, so a change to Monaco.Template.Backend.Application.Persistence can break Monaco.Template.Backend.Application.Features.Company, while a change to Monaco.Template.Backend.Application.Features.Company can't break Monaco.Template.Backend.Application.Persistence.
- Position
- Below the diagonal: Monaco.Template.Backend.Application.Features.Company uses a module listed above it, which is the healthy direction.
30→4 Monaco.Template.Backend.Application.Features.Country uses Monaco.Template.Backend.Application.Features.Country.DTOs✕
- Connections
- 2 pairs of types, where a type in Monaco.Template.Backend.Application.Features.Country uses a type in Monaco.Template.Backend.Application.Features.Country.DTOs.
- The types involved
Monaco.Template.Backend.Application.Features.Country.Handler→Monaco.Template.Backend.Application.Features.Country.DTOs.CountryDtoMonaco.Template.Backend.Application.Features.Country.Query→Monaco.Template.Backend.Application.Features.Country.DTOs.CountryDto
- Direction
- Monaco.Template.Backend.Application.Features.Country uses Monaco.Template.Backend.Application.Features.Country.DTOs, so a change to Monaco.Template.Backend.Application.Features.Country.DTOs can break Monaco.Template.Backend.Application.Features.Country, while a change to Monaco.Template.Backend.Application.Features.Country can't break Monaco.Template.Backend.Application.Features.Country.DTOs.
- Position
- Below the diagonal: Monaco.Template.Backend.Application.Features.Country uses a module listed above it, which is the healthy direction.
30→14 Monaco.Template.Backend.Application.Features.Country uses Monaco.Template.Backend.Common.Application.Queries✕
- Connections
- 1 pair of types, where a type in Monaco.Template.Backend.Application.Features.Country uses a type in Monaco.Template.Backend.Common.Application.Queries.
- The types involved
Monaco.Template.Backend.Application.Features.Country.Query→Monaco.Template.Backend.Common.Application.Queries.QueryByIdBase
- Direction
- Monaco.Template.Backend.Application.Features.Country uses Monaco.Template.Backend.Common.Application.Queries, so a change to Monaco.Template.Backend.Common.Application.Queries can break Monaco.Template.Backend.Application.Features.Country, while a change to Monaco.Template.Backend.Application.Features.Country can't break Monaco.Template.Backend.Common.Application.Queries.
- Position
- Below the diagonal: Monaco.Template.Backend.Application.Features.Country uses a module listed above it, which is the healthy direction.
30→21 Monaco.Template.Backend.Application.Features.Country uses Monaco.Template.Backend.Application.Persistence✕
- Connections
- 1 pair of types, where a type in Monaco.Template.Backend.Application.Features.Country uses a type in Monaco.Template.Backend.Application.Persistence.
- The types involved
Monaco.Template.Backend.Application.Features.Country.Handler→Monaco.Template.Backend.Application.Persistence.AppDbContext
- Direction
- Monaco.Template.Backend.Application.Features.Country uses Monaco.Template.Backend.Application.Persistence, so a change to Monaco.Template.Backend.Application.Persistence can break Monaco.Template.Backend.Application.Features.Country, while a change to Monaco.Template.Backend.Application.Features.Country can't break Monaco.Template.Backend.Application.Persistence.
- Position
- Below the diagonal: Monaco.Template.Backend.Application.Features.Country uses a module listed above it, which is the healthy direction.
31→4 Monaco.Template.Backend.Application.Features.Country.Extensions uses Monaco.Template.Backend.Application.Features.Country.DTOs✕
- Connections
- 2 pairs of types, where a type in Monaco.Template.Backend.Application.Features.Country.Extensions uses a type in Monaco.Template.Backend.Application.Features.Country.DTOs.
- The types involved
Monaco.Template.Backend.Application.Features.Country.Extensions.→Monaco.Template.Backend.Application.Features.Country.DTOs.CountryDtoMonaco.Template.Backend.Application.Features.Country.Extensions.CountryExtensions→Monaco.Template.Backend.Application.Features.Country.DTOs.CountryDto
- Direction
- Monaco.Template.Backend.Application.Features.Country.Extensions uses Monaco.Template.Backend.Application.Features.Country.DTOs, so a change to Monaco.Template.Backend.Application.Features.Country.DTOs can break Monaco.Template.Backend.Application.Features.Country.Extensions, while a change to Monaco.Template.Backend.Application.Features.Country.Extensions can't break Monaco.Template.Backend.Application.Features.Country.DTOs.
- Position
- Below the diagonal: Monaco.Template.Backend.Application.Features.Country.Extensions uses a module listed above it, which is the healthy direction.
31→28 Monaco.Template.Backend.Application.Features.Country.Extensions uses Monaco.Template.Backend.Domain.Model.Entities✕
- Connections
- 1 pair of types, where a type in Monaco.Template.Backend.Application.Features.Country.Extensions uses a type in Monaco.Template.Backend.Domain.Model.Entities.
- The types involved
Monaco.Template.Backend.Application.Features.Country.Extensions.CountryExtensions→Monaco.Template.Backend.Domain.Model.Entities.Country
- Direction
- Monaco.Template.Backend.Application.Features.Country.Extensions uses Monaco.Template.Backend.Domain.Model.Entities, so a change to Monaco.Template.Backend.Domain.Model.Entities can break Monaco.Template.Backend.Application.Features.Country.Extensions, while a change to Monaco.Template.Backend.Application.Features.Country.Extensions can't break Monaco.Template.Backend.Domain.Model.Entities.
- Position
- Below the diagonal: Monaco.Template.Backend.Application.Features.Country.Extensions uses a module listed above it, which is the healthy direction.
32→5 Monaco.Template.Backend.Application.Features.File.Extensions uses Monaco.Template.Backend.Application.Features.File.DTOs✕
- Connections
- 2 pairs of types, where a type in Monaco.Template.Backend.Application.Features.File.Extensions uses a type in Monaco.Template.Backend.Application.Features.File.DTOs.
- The types involved
Monaco.Template.Backend.Application.Features.File.Extensions.→Monaco.Template.Backend.Application.Features.File.DTOs.ImageDtoMonaco.Template.Backend.Application.Features.File.Extensions.FileExtensions→Monaco.Template.Backend.Application.Features.File.DTOs.ImageDto
- Direction
- Monaco.Template.Backend.Application.Features.File.Extensions uses Monaco.Template.Backend.Application.Features.File.DTOs, so a change to Monaco.Template.Backend.Application.Features.File.DTOs can break Monaco.Template.Backend.Application.Features.File.Extensions, while a change to Monaco.Template.Backend.Application.Features.File.Extensions can't break Monaco.Template.Backend.Application.Features.File.DTOs.
- Position
- Below the diagonal: Monaco.Template.Backend.Application.Features.File.Extensions uses a module listed above it, which is the healthy direction.
32→28 Monaco.Template.Backend.Application.Features.File.Extensions uses Monaco.Template.Backend.Domain.Model.Entities✕
- Connections
- 1 pair of types, where a type in Monaco.Template.Backend.Application.Features.File.Extensions uses a type in Monaco.Template.Backend.Domain.Model.Entities.
- The types involved
Monaco.Template.Backend.Application.Features.File.Extensions.FileExtensions→Monaco.Template.Backend.Domain.Model.Entities.Image
- Direction
- Monaco.Template.Backend.Application.Features.File.Extensions uses Monaco.Template.Backend.Domain.Model.Entities, so a change to Monaco.Template.Backend.Domain.Model.Entities can break Monaco.Template.Backend.Application.Features.File.Extensions, while a change to Monaco.Template.Backend.Application.Features.File.Extensions can't break Monaco.Template.Backend.Domain.Model.Entities.
- Position
- Below the diagonal: Monaco.Template.Backend.Application.Features.File.Extensions uses a module listed above it, which is the healthy direction.
33→6 Monaco.Template.Backend.Application.Features.Product uses Monaco.Template.Backend.Common.Application.Commands✕
- Connections
- 2 pairs of types, where a type in Monaco.Template.Backend.Application.Features.Product uses a type in Monaco.Template.Backend.Common.Application.Commands.
- The types involved
Monaco.Template.Backend.Application.Features.Product.Command→Monaco.Template.Backend.Common.Application.Commands.CommandBaseMonaco.Template.Backend.Application.Features.Product.Handler→Monaco.Template.Backend.Common.Application.Commands.CommandResult
- Direction
- Monaco.Template.Backend.Application.Features.Product uses Monaco.Template.Backend.Common.Application.Commands, so a change to Monaco.Template.Backend.Common.Application.Commands can break Monaco.Template.Backend.Application.Features.Product, while a change to Monaco.Template.Backend.Application.Features.Product can't break Monaco.Template.Backend.Common.Application.Commands.
- Position
- Below the diagonal: Monaco.Template.Backend.Application.Features.Product uses a module listed above it, which is the healthy direction.
33→7 Monaco.Template.Backend.Application.Features.Product uses Monaco.Template.Backend.Common.Application.DTOs✕
- Connections
- 1 pair of types, where a type in Monaco.Template.Backend.Application.Features.Product uses a type in Monaco.Template.Backend.Common.Application.DTOs.
- The types involved
Monaco.Template.Backend.Application.Features.Product.Query→Monaco.Template.Backend.Common.Application.DTOs.FileDownloadDto
- Direction
- Monaco.Template.Backend.Application.Features.Product uses Monaco.Template.Backend.Common.Application.DTOs, so a change to Monaco.Template.Backend.Common.Application.DTOs can break Monaco.Template.Backend.Application.Features.Product, while a change to Monaco.Template.Backend.Application.Features.Product can't break Monaco.Template.Backend.Common.Application.DTOs.
- Position
- Below the diagonal: Monaco.Template.Backend.Application.Features.Product uses a module listed above it, which is the healthy direction.
33→14 Monaco.Template.Backend.Application.Features.Product uses Monaco.Template.Backend.Common.Application.Queries✕
- Connections
- 1 pair of types, where a type in Monaco.Template.Backend.Application.Features.Product uses a type in Monaco.Template.Backend.Common.Application.Queries.
- The types involved
Monaco.Template.Backend.Application.Features.Product.Query→Monaco.Template.Backend.Common.Application.Queries.QueryBase
- Direction
- Monaco.Template.Backend.Application.Features.Product uses Monaco.Template.Backend.Common.Application.Queries, so a change to Monaco.Template.Backend.Common.Application.Queries can break Monaco.Template.Backend.Application.Features.Product, while a change to Monaco.Template.Backend.Application.Features.Product can't break Monaco.Template.Backend.Common.Application.Queries.
- Position
- Below the diagonal: Monaco.Template.Backend.Application.Features.Product uses a module listed above it, which is the healthy direction.
33→21 Monaco.Template.Backend.Application.Features.Product uses Monaco.Template.Backend.Application.Persistence✕
- Connections
- 2 pairs of types, where a type in Monaco.Template.Backend.Application.Features.Product uses a type in Monaco.Template.Backend.Application.Persistence.
- The types involved
Monaco.Template.Backend.Application.Features.Product.Handler→Monaco.Template.Backend.Application.Persistence.AppDbContextMonaco.Template.Backend.Application.Features.Product.Validator→Monaco.Template.Backend.Application.Persistence.AppDbContext
- Direction
- Monaco.Template.Backend.Application.Features.Product uses Monaco.Template.Backend.Application.Persistence, so a change to Monaco.Template.Backend.Application.Persistence can break Monaco.Template.Backend.Application.Features.Product, while a change to Monaco.Template.Backend.Application.Features.Product can't break Monaco.Template.Backend.Application.Persistence.
- Position
- Below the diagonal: Monaco.Template.Backend.Application.Features.Product uses a module listed above it, which is the healthy direction.
34→12 Monaco.Template.Backend.Application.Features.Product.Extensions uses Monaco.Template.Backend.Messages.V1✕
- Connections
- 1 pair of types, where a type in Monaco.Template.Backend.Application.Features.Product.Extensions uses a type in Monaco.Template.Backend.Messages.V1.
- The types involved
Monaco.Template.Backend.Application.Features.Product.Extensions.ProductExtensions→Monaco.Template.Backend.Messages.V1.ProductCreated
- Direction
- Monaco.Template.Backend.Application.Features.Product.Extensions uses Monaco.Template.Backend.Messages.V1, so a change to Monaco.Template.Backend.Messages.V1 can break Monaco.Template.Backend.Application.Features.Product.Extensions, while a change to Monaco.Template.Backend.Application.Features.Product.Extensions can't break Monaco.Template.Backend.Messages.V1.
- Position
- Below the diagonal: Monaco.Template.Backend.Application.Features.Product.Extensions uses a module listed above it, which is the healthy direction.
34→20 Monaco.Template.Backend.Application.Features.Product.Extensions uses Monaco.Template.Backend.Application.Features.Product.DTOs✕
- Connections
- 2 pairs of types, where a type in Monaco.Template.Backend.Application.Features.Product.Extensions uses a type in Monaco.Template.Backend.Application.Features.Product.DTOs.
- The types involved
Monaco.Template.Backend.Application.Features.Product.Extensions.→Monaco.Template.Backend.Application.Features.Product.DTOs.ProductDtoMonaco.Template.Backend.Application.Features.Product.Extensions.ProductExtensions→Monaco.Template.Backend.Application.Features.Product.DTOs.ProductDto
- Direction
- Monaco.Template.Backend.Application.Features.Product.Extensions uses Monaco.Template.Backend.Application.Features.Product.DTOs, so a change to Monaco.Template.Backend.Application.Features.Product.DTOs can break Monaco.Template.Backend.Application.Features.Product.Extensions, while a change to Monaco.Template.Backend.Application.Features.Product.Extensions can't break Monaco.Template.Backend.Application.Features.Product.DTOs.
- Position
- Below the diagonal: Monaco.Template.Backend.Application.Features.Product.Extensions uses a module listed above it, which is the healthy direction.
34→21 Monaco.Template.Backend.Application.Features.Product.Extensions uses Monaco.Template.Backend.Application.Persistence✕
- Connections
- 1 pair of types, where a type in Monaco.Template.Backend.Application.Features.Product.Extensions uses a type in Monaco.Template.Backend.Application.Persistence.
- The types involved
Monaco.Template.Backend.Application.Features.Product.Extensions.ProductExtensions→Monaco.Template.Backend.Application.Persistence.AppDbContext
- Direction
- Monaco.Template.Backend.Application.Features.Product.Extensions uses Monaco.Template.Backend.Application.Persistence, so a change to Monaco.Template.Backend.Application.Persistence can break Monaco.Template.Backend.Application.Features.Product.Extensions, while a change to Monaco.Template.Backend.Application.Features.Product.Extensions can't break Monaco.Template.Backend.Application.Persistence.
- Position
- Below the diagonal: Monaco.Template.Backend.Application.Features.Product.Extensions uses a module listed above it, which is the healthy direction.
34→28 Monaco.Template.Backend.Application.Features.Product.Extensions uses Monaco.Template.Backend.Domain.Model.Entities✕
- Connections
- 3 pairs of types, where a type in Monaco.Template.Backend.Application.Features.Product.Extensions uses a type in Monaco.Template.Backend.Domain.Model.Entities.
- The types involved
Monaco.Template.Backend.Application.Features.Product.Extensions.ProductExtensions→Monaco.Template.Backend.Domain.Model.Entities.CompanyMonaco.Template.Backend.Application.Features.Product.Extensions.ProductExtensions→Monaco.Template.Backend.Domain.Model.Entities.ImageMonaco.Template.Backend.Application.Features.Product.Extensions.ProductExtensions→Monaco.Template.Backend.Domain.Model.Entities.Product
- Direction
- Monaco.Template.Backend.Application.Features.Product.Extensions uses Monaco.Template.Backend.Domain.Model.Entities, so a change to Monaco.Template.Backend.Domain.Model.Entities can break Monaco.Template.Backend.Application.Features.Product.Extensions, while a change to Monaco.Template.Backend.Application.Features.Product.Extensions can't break Monaco.Template.Backend.Domain.Model.Entities.
- Position
- Below the diagonal: Monaco.Template.Backend.Application.Features.Product.Extensions uses a module listed above it, which is the healthy direction.
35→28 Monaco.Template.Backend.Application.Persistence.EntityConfigurations uses Monaco.Template.Backend.Domain.Model.Entities✕
- Connections
- 6 pairs of types, where a type in Monaco.Template.Backend.Application.Persistence.EntityConfigurations uses a type in Monaco.Template.Backend.Domain.Model.Entities.
- The types involved
Monaco.Template.Backend.Application.Persistence.EntityConfigurations.CompanyEntityConfiguration→Monaco.Template.Backend.Domain.Model.Entities.CompanyMonaco.Template.Backend.Application.Persistence.EntityConfigurations.CountryEntityConfiguration→Monaco.Template.Backend.Domain.Model.Entities.CountryMonaco.Template.Backend.Application.Persistence.EntityConfigurations.DocumentEntityConfiguration→Monaco.Template.Backend.Domain.Model.Entities.DocumentMonaco.Template.Backend.Application.Persistence.EntityConfigurations.FileEntityConfiguration→Monaco.Template.Backend.Domain.Model.Entities.FileMonaco.Template.Backend.Application.Persistence.EntityConfigurations.ImageEntityConfiguration→Monaco.Template.Backend.Domain.Model.Entities.ImageMonaco.Template.Backend.Application.Persistence.EntityConfigurations.ProductEntityConfiguration→Monaco.Template.Backend.Domain.Model.Entities.Product
- Direction
- Monaco.Template.Backend.Application.Persistence.EntityConfigurations uses Monaco.Template.Backend.Domain.Model.Entities, so a change to Monaco.Template.Backend.Domain.Model.Entities can break Monaco.Template.Backend.Application.Persistence.EntityConfigurations, while a change to Monaco.Template.Backend.Application.Persistence.EntityConfigurations can't break Monaco.Template.Backend.Domain.Model.Entities.
- Position
- Below the diagonal: Monaco.Template.Backend.Application.Persistence.EntityConfigurations uses a module listed above it, which is the healthy direction.
36→7 Monaco.Template.Backend.Application.Services.Contracts uses Monaco.Template.Backend.Common.Application.DTOs✕
- Connections
- 1 pair of types, where a type in Monaco.Template.Backend.Application.Services.Contracts uses a type in Monaco.Template.Backend.Common.Application.DTOs.
- The types involved
Monaco.Template.Backend.Application.Services.Contracts.IFileService→Monaco.Template.Backend.Common.Application.DTOs.FileDownloadDto
- Direction
- Monaco.Template.Backend.Application.Services.Contracts uses Monaco.Template.Backend.Common.Application.DTOs, so a change to Monaco.Template.Backend.Common.Application.DTOs can break Monaco.Template.Backend.Application.Services.Contracts, while a change to Monaco.Template.Backend.Application.Services.Contracts can't break Monaco.Template.Backend.Common.Application.DTOs.
- Position
- Below the diagonal: Monaco.Template.Backend.Application.Services.Contracts uses a module listed above it, which is the healthy direction.
36→28 Monaco.Template.Backend.Application.Services.Contracts uses Monaco.Template.Backend.Domain.Model.Entities✕
- Connections
- 3 pairs of types, where a type in Monaco.Template.Backend.Application.Services.Contracts uses a type in Monaco.Template.Backend.Domain.Model.Entities.
- The types involved
Monaco.Template.Backend.Application.Services.Contracts.IFileService→Monaco.Template.Backend.Domain.Model.Entities.DocumentMonaco.Template.Backend.Application.Services.Contracts.IFileService→Monaco.Template.Backend.Domain.Model.Entities.FileMonaco.Template.Backend.Application.Services.Contracts.IFileService→Monaco.Template.Backend.Domain.Model.Entities.Image
- Direction
- Monaco.Template.Backend.Application.Services.Contracts uses Monaco.Template.Backend.Domain.Model.Entities, so a change to Monaco.Template.Backend.Domain.Model.Entities can break Monaco.Template.Backend.Application.Services.Contracts, while a change to Monaco.Template.Backend.Application.Services.Contracts can't break Monaco.Template.Backend.Domain.Model.Entities.
- Position
- Below the diagonal: Monaco.Template.Backend.Application.Services.Contracts uses a module listed above it, which is the healthy direction.
37→3 Monaco.Template.Backend.Api.DTOs.Extensions uses Monaco.Template.Backend.Api.DTOs✕
- Connections
- 2 pairs of types, where a type in Monaco.Template.Backend.Api.DTOs.Extensions uses a type in Monaco.Template.Backend.Api.DTOs.
- The types involved
Monaco.Template.Backend.Api.DTOs.Extensions.CompanyExtensions→Monaco.Template.Backend.Api.DTOs.CompanyCreateEditDtoMonaco.Template.Backend.Api.DTOs.Extensions.ProductExtensions→Monaco.Template.Backend.Api.DTOs.ProductCreateEditDto
- Direction
- Monaco.Template.Backend.Api.DTOs.Extensions uses Monaco.Template.Backend.Api.DTOs, so a change to Monaco.Template.Backend.Api.DTOs can break Monaco.Template.Backend.Api.DTOs.Extensions, while a change to Monaco.Template.Backend.Api.DTOs.Extensions can't break Monaco.Template.Backend.Api.DTOs.
- Position
- Below the diagonal: Monaco.Template.Backend.Api.DTOs.Extensions uses a module listed above it, which is the healthy direction.
37→29 Monaco.Template.Backend.Api.DTOs.Extensions uses Monaco.Template.Backend.Application.Features.Company✕
- Connections
- 2 pairs of types, where a type in Monaco.Template.Backend.Api.DTOs.Extensions uses a type in Monaco.Template.Backend.Application.Features.Company.
- The types involved
Monaco.Template.Backend.Api.DTOs.Extensions.→Monaco.Template.Backend.Application.Features.Company.CommandMonaco.Template.Backend.Api.DTOs.Extensions.CompanyExtensions→Monaco.Template.Backend.Application.Features.Company.Command
- Direction
- Monaco.Template.Backend.Api.DTOs.Extensions uses Monaco.Template.Backend.Application.Features.Company, so a change to Monaco.Template.Backend.Application.Features.Company can break Monaco.Template.Backend.Api.DTOs.Extensions, while a change to Monaco.Template.Backend.Api.DTOs.Extensions can't break Monaco.Template.Backend.Application.Features.Company.
- Position
- Below the diagonal: Monaco.Template.Backend.Api.DTOs.Extensions uses a module listed above it, which is the healthy direction.
37→33 Monaco.Template.Backend.Api.DTOs.Extensions uses Monaco.Template.Backend.Application.Features.Product✕
- Connections
- 1 pair of types, where a type in Monaco.Template.Backend.Api.DTOs.Extensions uses a type in Monaco.Template.Backend.Application.Features.Product.
- The types involved
Monaco.Template.Backend.Api.DTOs.Extensions.ProductExtensions→Monaco.Template.Backend.Application.Features.Product.Command
- Direction
- Monaco.Template.Backend.Api.DTOs.Extensions uses Monaco.Template.Backend.Application.Features.Product, so a change to Monaco.Template.Backend.Application.Features.Product can break Monaco.Template.Backend.Api.DTOs.Extensions, while a change to Monaco.Template.Backend.Api.DTOs.Extensions can't break Monaco.Template.Backend.Application.Features.Product.
- Position
- Below the diagonal: Monaco.Template.Backend.Api.DTOs.Extensions uses a module listed above it, which is the healthy direction.
38→13 Monaco.Template.Backend.Application.Features.Company.Extensions uses Monaco.Template.Backend.Application.Features.Company.DTOs✕
- Connections
- 2 pairs of types, where a type in Monaco.Template.Backend.Application.Features.Company.Extensions uses a type in Monaco.Template.Backend.Application.Features.Company.DTOs.
- The types involved
Monaco.Template.Backend.Application.Features.Company.Extensions.→Monaco.Template.Backend.Application.Features.Company.DTOs.CompanyDtoMonaco.Template.Backend.Application.Features.Company.Extensions.CompanyExtensions→Monaco.Template.Backend.Application.Features.Company.DTOs.CompanyDto
- Direction
- Monaco.Template.Backend.Application.Features.Company.Extensions uses Monaco.Template.Backend.Application.Features.Company.DTOs, so a change to Monaco.Template.Backend.Application.Features.Company.DTOs can break Monaco.Template.Backend.Application.Features.Company.Extensions, while a change to Monaco.Template.Backend.Application.Features.Company.Extensions can't break Monaco.Template.Backend.Application.Features.Company.DTOs.
- Position
- Below the diagonal: Monaco.Template.Backend.Application.Features.Company.Extensions uses a module listed above it, which is the healthy direction.
38→28 Monaco.Template.Backend.Application.Features.Company.Extensions uses Monaco.Template.Backend.Domain.Model.Entities✕
- Connections
- 2 pairs of types, where a type in Monaco.Template.Backend.Application.Features.Company.Extensions uses a type in Monaco.Template.Backend.Domain.Model.Entities.
- The types involved
Monaco.Template.Backend.Application.Features.Company.Extensions.CompanyExtensions→Monaco.Template.Backend.Domain.Model.Entities.CompanyMonaco.Template.Backend.Application.Features.Company.Extensions.CompanyExtensions→Monaco.Template.Backend.Domain.Model.Entities.Country
- Direction
- Monaco.Template.Backend.Application.Features.Company.Extensions uses Monaco.Template.Backend.Domain.Model.Entities, so a change to Monaco.Template.Backend.Domain.Model.Entities can break Monaco.Template.Backend.Application.Features.Company.Extensions, while a change to Monaco.Template.Backend.Application.Features.Company.Extensions can't break Monaco.Template.Backend.Domain.Model.Entities.
- Position
- Below the diagonal: Monaco.Template.Backend.Application.Features.Company.Extensions uses a module listed above it, which is the healthy direction.
38→29 Monaco.Template.Backend.Application.Features.Company.Extensions uses Monaco.Template.Backend.Application.Features.Company✕
- Connections
- 1 pair of types, where a type in Monaco.Template.Backend.Application.Features.Company.Extensions uses a type in Monaco.Template.Backend.Application.Features.Company.
- The types involved
Monaco.Template.Backend.Application.Features.Company.Extensions.CompanyExtensions→Monaco.Template.Backend.Application.Features.Company.Command
- Direction
- Monaco.Template.Backend.Application.Features.Company.Extensions uses Monaco.Template.Backend.Application.Features.Company, so a change to Monaco.Template.Backend.Application.Features.Company can break Monaco.Template.Backend.Application.Features.Company.Extensions, while a change to Monaco.Template.Backend.Application.Features.Company.Extensions can't break Monaco.Template.Backend.Application.Features.Company.
- Position
- Below the diagonal: Monaco.Template.Backend.Application.Features.Company.Extensions uses a module listed above it, which is the healthy direction.
39→6 Monaco.Template.Backend.Application.Features.File uses Monaco.Template.Backend.Common.Application.Commands✕
- Connections
- 2 pairs of types, where a type in Monaco.Template.Backend.Application.Features.File uses a type in Monaco.Template.Backend.Common.Application.Commands.
- The types involved
Monaco.Template.Backend.Application.Features.File.Command→Monaco.Template.Backend.Common.Application.Commands.CommandBaseMonaco.Template.Backend.Application.Features.File.Handler→Monaco.Template.Backend.Common.Application.Commands.CommandResult
- Direction
- Monaco.Template.Backend.Application.Features.File uses Monaco.Template.Backend.Common.Application.Commands, so a change to Monaco.Template.Backend.Common.Application.Commands can break Monaco.Template.Backend.Application.Features.File, while a change to Monaco.Template.Backend.Application.Features.File can't break Monaco.Template.Backend.Common.Application.Commands.
- Position
- Below the diagonal: Monaco.Template.Backend.Application.Features.File uses a module listed above it, which is the healthy direction.
39→21 Monaco.Template.Backend.Application.Features.File uses Monaco.Template.Backend.Application.Persistence✕
- Connections
- 1 pair of types, where a type in Monaco.Template.Backend.Application.Features.File uses a type in Monaco.Template.Backend.Application.Persistence.
- The types involved
Monaco.Template.Backend.Application.Features.File.Handler→Monaco.Template.Backend.Application.Persistence.AppDbContext
- Direction
- Monaco.Template.Backend.Application.Features.File uses Monaco.Template.Backend.Application.Persistence, so a change to Monaco.Template.Backend.Application.Persistence can break Monaco.Template.Backend.Application.Features.File, while a change to Monaco.Template.Backend.Application.Features.File can't break Monaco.Template.Backend.Application.Persistence.
- Position
- Below the diagonal: Monaco.Template.Backend.Application.Features.File uses a module listed above it, which is the healthy direction.
39→36 Monaco.Template.Backend.Application.Features.File uses Monaco.Template.Backend.Application.Services.Contracts✕
- Connections
- 1 pair of types, where a type in Monaco.Template.Backend.Application.Features.File uses a type in Monaco.Template.Backend.Application.Services.Contracts.
- The types involved
Monaco.Template.Backend.Application.Features.File.Handler→Monaco.Template.Backend.Application.Services.Contracts.IFileService
- Direction
- Monaco.Template.Backend.Application.Features.File uses Monaco.Template.Backend.Application.Services.Contracts, so a change to Monaco.Template.Backend.Application.Services.Contracts can break Monaco.Template.Backend.Application.Features.File, while a change to Monaco.Template.Backend.Application.Features.File can't break Monaco.Template.Backend.Application.Services.Contracts.
- Position
- Below the diagonal: Monaco.Template.Backend.Application.Features.File uses a module listed above it, which is the healthy direction.
40→7 Monaco.Template.Backend.Application.Services uses Monaco.Template.Backend.Common.Application.DTOs✕
- Connections
- 1 pair of types, where a type in Monaco.Template.Backend.Application.Services uses a type in Monaco.Template.Backend.Common.Application.DTOs.
- The types involved
Monaco.Template.Backend.Application.Services.FileService→Monaco.Template.Backend.Common.Application.DTOs.FileDownloadDto
- Direction
- Monaco.Template.Backend.Application.Services uses Monaco.Template.Backend.Common.Application.DTOs, so a change to Monaco.Template.Backend.Common.Application.DTOs can break Monaco.Template.Backend.Application.Services, while a change to Monaco.Template.Backend.Application.Services can't break Monaco.Template.Backend.Common.Application.DTOs.
- Position
- Below the diagonal: Monaco.Template.Backend.Application.Services uses a module listed above it, which is the healthy direction.
40→26 Monaco.Template.Backend.Application.Services uses Monaco.Template.Backend.Common.BlobStorage.Contracts✕
- Connections
- 1 pair of types, where a type in Monaco.Template.Backend.Application.Services uses a type in Monaco.Template.Backend.Common.BlobStorage.Contracts.
- The types involved
Monaco.Template.Backend.Application.Services.FileService→Monaco.Template.Backend.Common.BlobStorage.Contracts.IBlobStorageService
- Direction
- Monaco.Template.Backend.Application.Services uses Monaco.Template.Backend.Common.BlobStorage.Contracts, so a change to Monaco.Template.Backend.Common.BlobStorage.Contracts can break Monaco.Template.Backend.Application.Services, while a change to Monaco.Template.Backend.Application.Services can't break Monaco.Template.Backend.Common.BlobStorage.Contracts.
- Position
- Below the diagonal: Monaco.Template.Backend.Application.Services uses a module listed above it, which is the healthy direction.
40→28 Monaco.Template.Backend.Application.Services uses Monaco.Template.Backend.Domain.Model.Entities✕
- Connections
- 3 pairs of types, where a type in Monaco.Template.Backend.Application.Services uses a type in Monaco.Template.Backend.Domain.Model.Entities.
- The types involved
Monaco.Template.Backend.Application.Services.FileService→Monaco.Template.Backend.Domain.Model.Entities.DocumentMonaco.Template.Backend.Application.Services.FileService→Monaco.Template.Backend.Domain.Model.Entities.FileMonaco.Template.Backend.Application.Services.FileService→Monaco.Template.Backend.Domain.Model.Entities.Image
- Direction
- Monaco.Template.Backend.Application.Services uses Monaco.Template.Backend.Domain.Model.Entities, so a change to Monaco.Template.Backend.Domain.Model.Entities can break Monaco.Template.Backend.Application.Services, while a change to Monaco.Template.Backend.Application.Services can't break Monaco.Template.Backend.Domain.Model.Entities.
- Position
- Below the diagonal: Monaco.Template.Backend.Application.Services uses a module listed above it, which is the healthy direction.
40→36 Monaco.Template.Backend.Application.Services uses Monaco.Template.Backend.Application.Services.Contracts✕
- Connections
- 1 pair of types, where a type in Monaco.Template.Backend.Application.Services uses a type in Monaco.Template.Backend.Application.Services.Contracts.
- The types involved
Monaco.Template.Backend.Application.Services.FileService→Monaco.Template.Backend.Application.Services.Contracts.IFileService
- Direction
- Monaco.Template.Backend.Application.Services uses Monaco.Template.Backend.Application.Services.Contracts, so a change to Monaco.Template.Backend.Application.Services.Contracts can break Monaco.Template.Backend.Application.Services, while a change to Monaco.Template.Backend.Application.Services can't break Monaco.Template.Backend.Application.Services.Contracts.
- Position
- Below the diagonal: Monaco.Template.Backend.Application.Services uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
At a glance — Domain Modelling
At a glance — Event-Driven
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A05:2025 — Injection | 15 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 3 | High / Critical |
| A07:2025 — Authentication Failures | 2 | High / Critical |
| A01:2025 — Broken Access Control | 1 | Medium |
Roadmap
Top priorities: Reference other aggregates by their strongly-typed id, never by object reference, so each aggregate stays an independent consistency boundary; Give each aggregate one way in that can refuse — a guarded constructor, value-object parameters that validate themselves, or a private constructor behind a factory that returns a failure; Adopt strongly-typed ids across the domain — finish the migration or document the boundary; primitive ids invite transposed-argument bugs.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Reference other aggregates by their strongly-typed id, never by object reference, so each aggregate stays an independent consistency boundary. | +4.0 pts | Medium | Aggregate boundaries |
| Give each aggregate one way in that can refuse — a guarded constructor, value-object parameters that validate themselves, or a private constructor behind a factory that returns a failure. | +3.7 pts | Medium | Constructible invalid state |
| Adopt strongly-typed ids across the domain — finish the migration or document the boundary; primitive ids invite transposed-argument bugs. | +3.7 pts | Medium | Strongly-typed ids |
| Resolve the 8 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (8). | +1.0 pts | Low | Static Analysis (SAST) |
| Move business rules onto the aggregates/entities they govern so invariants are enforced at the source, not in anemic services. | +1.9 pts | Medium | Rich vs anemic model |
| Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. | +0.8 pts | Low | Static Analysis (SAST) |
| Resolve the 3 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (3). | +0.8 pts | Low | Static Analysis (SAST) |
| Resolve the 3 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED, REDACTED, REDACTED. | +0.8 pts | Low | Dependency Vulnerabilities |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 2.7 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.8 | Mixed | Secret Scanning: Leaked secret: REDACTED |
| REDACTED | 5.8 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| src/Content/Backend/Solution/Monaco.Template.Backend.Common.Infrastructure/Context/Extensions/FilterExtensions.cs | 7.2 | Near-clean | Cyclomatic Complexity: FilterExtensions.ValidateDataType (cyclomatic 23) |
| REDACTED | 7.2 | Near-clean | Dependency Vulnerabilities: High CVE: REDACTED |
| REDACTED | 7.2 | Near-clean | Dependency Vulnerabilities: High CVE: REDACTED |
| REDACTED | 7.2 | Near-clean | Dependency Vulnerabilities: High CVE: REDACTED |
| REDACTED | 7.4 | Near-clean | Data Compliance (PII/GDPR): REDACTED |
| src/Content/Backend/Solution/Monaco.Template.Backend.Application.Tests/Features/Product/CreateProductHandlerTests.cs | 7.6 | Near-clean | Explicit Debt: WriteOnlyPrivateField |
| src/Content/Backend/Solution/Monaco.Template.Backend.Api/Program.cs | 7.8 | Near-clean | Code Duplication: Duplicated block (11–19 lines × 2) |
| src/Content/Backend/Solution/Monaco.Template.Backend.Application/Features/Product/CreateProduct.cs | 7.8 | Near-clean | Code Duplication: Duplicated block (10 lines × 2) |
| src/Content/Backend/Solution/Monaco.Template.Backend.Common.Serilog/ApplicationInsights/TelemetryConverters/AuditEventTelemetryConverter.cs | 7.8 | Near-clean | Code Duplication: Duplicated block (11 lines × 2) |
| REDACTED | 7.9 | Near-clean | Static Analysis (SAST): Medium: REDACTED |
| REDACTED | 7.9 | Near-clean | Static Analysis (SAST): Medium: REDACTED |
| src/Content/Backend/Solution/Monaco.Template.Backend.Application/Monaco.Template.Backend.Application.csproj | 8.0 | Near-clean | Coupling: Layer violation: Application → Infrastructure |
| src/Content/Backend/Solution/Monaco.Template.Backend.Common.Application/Monaco.Template.Backend.Common.Application.csproj | 8.0 | Near-clean | Coupling: Layer violation: Application → Infrastructure |
| src/Content/Backend/Solution/Monaco.Template.Backend.Common.Tests/DbContextMockExtensions.cs | 8.2 | Near-clean | Explicit Debt: Dead code: SetupDbSetMock |
| src/Content/Backend/Solution/Monaco.Template.Backend.ArchitectureTests/Extensions/ArchUnitExtensions.cs | 8.2 | Near-clean | Explicit Debt: Dead code: HavePropertySetterWithVisibility |
| src/Content/Backend/Solution/Monaco.Template.Backend.Domain.Tests/Factories/Entities/AddressFactory.cs | 8.2 | Near-clean | Explicit Debt: Dead code: AddressFactory |
| src/Content/Backend/Solution/Monaco.Template.Backend.Domain.Tests/Factories/Entities/CompanyFactory.cs | 8.2 | Near-clean | Explicit Debt: Dead code: Mock |
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 89 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 — 89 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, 126 of 140 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Canine Code Analyzer duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 | ✓ deterministic |
Run transparency — what happened this run
- D8 Code Coverage — not measured this run — 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. Coverage NOT MEASURED: the analyzer environment could not build/run the test suite (a target framework / SDK band or targeting pack the analyzer image doesn't carry). This is OUR limitation, not a defect in the repo — coverage is excluded from the score rather than counted as a near-zero. We track the analyzer-image gap so it can be closed; in the meantime, 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, and real coverage will be read. 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, and the real number is read on the next scan.
- D11 Test Reliability — 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. Test reliability is scored on the 1 tier(s) that produced comparable repeat runs; 1 tier(s) did not, and are excluded from the measurement rather than counted (unit: measured (0 flaky); integration: not included — too large to re-run within its budget). This is OUR limitation, not a defect in the repository.
- D12 Dependency Hygiene — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `dotnet list package` did not return usable output (restore or query failed); no outdated/vulnerable/deprecated data to assess. The tool said: `dotnet list package` exited 1 with no output.
- 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 (6 contributor(s) across 105 commit(s) sampled, automation and bot accounts excluded). One of them holds 84% of the history; the other 5 hold 3.2% 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.
- 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) — 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. `src/Content/Backend/Solution/Monaco.Template.Backend.Api/Endpoints/Companies.cs`, `src/Content/Backend/Solution/Monaco.Template.Backend.Api/Endpoints/Extensions/EndpointsExtensions.cs`, `src/Content/Backend/Solution/Monaco.Template.Backend.Api/Endpoints/Files.cs`, `src/Content/Backend/Solution/Monaco.Template.Backend.Api/Endpoints/Products.cs`, `src/Content/Backend/Solution/Monaco.Template.Backend.Api/Program.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 own build of this repository failed for an ENVIRONMENT reason (exit 1) — MSBuild's engine or the CLR gave up, or our image does not carry the SDK band/targeting pack this repository needs. This is OUR limitation, not a defect in the repo, and it is not a statement that this repository fails to build. D18 owns the question of whether this repository builds; it was not answered here.
- D44 Platform End-of-Life — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This dimension reads a project's own statement about the platform it runs on: a TargetFramework in a .NET project file, a .nvmrc or .python-version, a capped requires-python, a Rust toolchain file or Cargo.toml rust-version, a .go-version, .java-version, .ruby-version, .tool-versions or .sdkmanrc, a go.mod go directive, a Maven or Gradle Java level or toolchain, a Gemfile's ruby directive, a mix.exs elixir requirement, a rebar.config minimum_otp_vsn, a pubspec.yaml SDK constraint, a build.sbt scalaVersion, or a framework major pinned by a dependency constraint. This repository carries none of them, so nothing about its platform was established. That is a gap in this analyzer's coverage, NOT a finding that the platform is supported — a language whose runtime is declared elsewhere (Package.swift, a Dockerfile) is simply not read here yet.
- DM8 Value-object opportunities — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check finds primitive parameters that travel together through several signatures of the domain (a missing value object). Its deterministic rule has not yet shown 95 % precision on adjudicated rows, so the clumps it finds are counted here and not published as findings, and the card carries no score. That is a limit of the analyzer, not a finding about your code.
- ED5 Idempotency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check classifies a mutation as idempotent when a guard is visible (an exists check, an upsert, an idempotency key or inbox, a versioned or fixed-value write) and as at risk only on positive evidence that a re-run double-applies it (a fresh-identity insert, an accumulation, a growing collection, an unkeyed outbound send or charge). The rest show neither, and they are the majority here, so a score over the classified minority would not describe this repository. That is a limit of the analyzer, not a finding about your code.
- P1 CI/CD gates — 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. A CI pipeline exists and the word "test" appears, but no explicit test-runner invocation (your stack's test command, or a test job) was matched — so either the gate runs tests through a step this pass could not recognise, or "test" is incidental here (a path, "latest", a reporter). Which of the two it is cannot be settled from this dimension's evidence; the coverage dimensions report whether a suite exists at all. You can widen what we reach: name the test runner explicitly in the pipeline step (your stack's test command, or a job named for the suite) so the gate is unambiguous to a reader and to this pass.
- PF3 Async & latency hygiene — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 15 further occurrence(s) are not listed individually; the score already reflects all 55.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
- D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
- D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
- D11 Test Reliability: Flakiness is inferred from history/markers — we run the suite once (for coverage), not the repeated runs under varied conditions that reveal nondeterminism, so a flaky test never recorded as failing is invisible here.
- D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D18 Solution Shape: Build integrity reflects whether the solution compiled in this environment — a build that needs a private feed, a specific SDK, or a generated file absent from the repo can read as broken when it is merely unreproducible here.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- D24 Comment Value: Comment value is measured as redundancy only: a comment that repeats its code's words is found, but a paraphrase in other words, a vague comment, or one the code contradicts is not, and whether a comment is valuable is not claimed. Comments in other scripts or languages, and outside C#, are not judged.
- D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
- D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- D32 Data Compliance (PII/GDPR): PII/GDPR signals are heuristic pattern matches in code — they flag likely handling concerns, not legal compliance, and cannot trace where data actually flows at runtime.
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- AX9 CQS / query purity: Handlers are found by interface/name convention — a query handler using neither is not seen. Mutation is a resolved write/publish invocation (SaveChanges/repository/bus), so a write hidden behind a hand-rolled wrapper, reflection, or a string-keyed service locator resolves to a non-persistence type and isn't flagged; it detects that a query writes state, not whether the write is a legitimate read-side cache update. Clean means "no resolved write/publish in a query body", not a proof of CQS purity.
- DM4 Rich vs anemic model: Behaviour is detected as state mutation inside a method body — a method that enforces an invariant by validating-and-throwing without mutating reads as a query, and mutation delegated through an interface the scan can't resolve isn't credited; entities with zero public properties still drop out of the population. It detects that state changes, not whether the rule is correct.
- DM6 Domain ↔ infrastructure boundary: Infrastructure reached through a hand-rolled wrapper, a domain-named facade, reflection, or a string-keyed service locator resolves to a non-infra type and isn't seen; the body scan is symbol resolution over syntax, not full dataflow. A clean result means "no resolved infra reference in a domain body", not a proof of purity.
- M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
- P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
- 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
2 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was FilterExtensions.ValidateDataType at 23.
What to do
- Bring the 2 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with FilterExtensions.ValidateDataType (cyclomatic 23), FilterExtensions.GetOperationExpression (cyclomatic 20). — 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 2 together lifts Cyclomatic Complexity from 9.4 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
- 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
1 method(s) exceeded the cognitive complexity threshold of 15; the worst was FilterExtensions.GetOperationExpression at 30.
What to do
- Bring the 1 body over 15 down to 15 or less in Cognitive Complexity — start with FilterExtensions.GetOperationExpression (cognitive 30). — Refactoring it lifts Cognitive Complexity from 9.2 to about 10.0/10.
- 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
1 over-large unit(s) detected — types, modules or files that carry too much.
What to do
- Resolve the 1 MethodTooLong finding(s) in God Classes — start with CountrySeed.cs. — One of this dimension's main actionable groups (1 warning-level).
- Enforce God Classes in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D4 · Code Duplication
7 duplicated block group(s) detected.
What to do
- Resolve the 1 Duplicated block (23 lines × 2) finding(s) in Code Duplication — start with CreateCompany.cs. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Duplicated block (11–19 lines × 2) finding(s) in Code Duplication — start with Program.cs. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Duplicated block (10 lines × 2) finding(s) in Code Duplication — start with CreateProduct.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
20 projects, 0 dependency cycle(s), 0 unstable depended-on project(s).
What to do
- Resolve the 2 Layer violation finding(s) in Coupling — start with Monaco.Template.Backend.Application.csproj, Monaco.Template.Backend.Common.Application.csproj. — One of this dimension's main actionable groups (2 issue-level).
- Enforce Coupling in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D6 · Cohesion (LCOM4)
0 of 8 classes have LCOM4 above 3.
D9 · Test Distribution
266 test methods: 251 unit, 15 integration, 0 BDD, 0 e2e.
D10 · Test Quality
0 skipped, 0 zero-assertion, 2 mock references across 266 tests.
D11 · Test Reliability
Only 1 of 2 test tiers measured — the score covers those alone. 0 flaky across 1 measured tier(s). unit: measured (0 flaky); integration: not included — too large to re-run within its budget.
D13 · Secret Scanning
1 secret(s) detected.
What to do
- Resolve the 2 Leaked secret finding(s) in Secret Scanning — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
- Enforce Secret Scanning in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D14 · License Compliance
0 of 250 packages use a banned license. ★ DEPTH: this repository's MSBuild projects declare 60 direct `PackageReference`(s), and 190 further package(s) were reached beyond them by closing the graph over nuget.org's own nuspec dependency graph — so a banned licence pulled in only by a dependency's OWN dependencies is inside this verdict. A package whose licence nuget.org could not be asked for is not graded, and version ranges are taken at their lower bound, so this is the closure as that graph states it rather than a restored consumer's exact resolution.
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window.
D17 · Explicit Debt
1 deducted debt markers + 4 dead symbols across 5537 LoC in the .NET projects (0.3/KLoC) → score 9.5.
What to do
- Resolve the 1 WriteOnlyPrivateField finding(s) in Explicit Debt — start with CreateProductHandlerTests.cs. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 4 Dead code finding(s) in Explicit Debt — start with DbContextMockExtensions.cs, ArchUnitExtensions.cs, AddressFactory.cs. — One of this dimension's main actionable groups (4 warning-level).
- Enforce Explicit Debt in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D18 · Solution Shape
20 projects, 197 source files, 11775 hand-written lines of code (5537 production / 6238 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 3207 generated (machine-written code — designer, scaffolded and tool-emitted files — excluded from quality), 33 inter-project edges.
D19 · Documentation Quality
1 of 1 documentation facets pass in full. 1 document(s) read across 1 unit(s).
D24 · Comment Value
5 of 56 judged comments only repeat the code they sit on (8.9 %).
What to do
- Resolve the 5 redundant comment finding(s) in Comment Value — start with Program.cs (4), REDACTED. — One of this dimension's main actionable groups (5 recommendation-level).
D26 · Project Cohesion
0 of 20 projects flagged as possibly oversized/incoherent.
D27 · Navigability
94 % of calls cross a namespace and 3 % go through an interface, but 100 % of collaborators are co-located — so a call's collaborators sit together and tracing stays easy. Baseline: small — navigation cost is tolerated.
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
15 finding(s): 0 critical, 4 high, 11 medium, 0 low. semgrep hit a parse error in 27 file(s) — `src/Content/Backend/Solution/Monaco.Template.Backend.Api/Endpoints/Companies.cs` (line 37, line 51, line 68, …), `src/Content/Backend/Solution/Monaco.Template.Backend.Api/Endpoints/Extensions/EndpointsExtensions.cs` (line 23), `src/Content/Backend/Solution/Monaco.Template.Backend.Api/Endpoints/Files.cs` (line 39), `src/Content/Backend/Solution/Monaco.Template.Backend.Api/Endpoints/Products.cs` (line 37, line 51, line 68, …), `src/Content/Backend/Solution/Monaco.Template.Backend.Api/Program.cs` (line 139), … (+22 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 4 of those file(s) — `src/Content/Backend/Solution/Monaco.Template.Backend.Common.Domain.Tests/EnumerationTests.cs`, `src/Content/Backend/Solution/Monaco.Template.Backend.Common.Domain.Tests/Factories/AutoDomainDataAttribute.cs`, `src/Content/Backend/Solution/Monaco.Template.Backend.Domain.Tests/Factories/AutoDomainDataAttribute.cs`, `src/Content/Backend/Solution/Monaco.Template.Backend.IntegrationTests/IntegrationTest.cs` — 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. In 10 of those file(s) — `src/Content/Backend/Solution/Monaco.Template.Backend.Common.Application/Queries/Extensions/QueryExtensions.cs`, `src/Content/Backend/Solution/Monaco.Template.Backend.Common.Application/Validators/Extensions/ValidatorsExtensions.cs`, `src/Content/Backend/Solution/Monaco.Template.Backend.Common.Domain.Tests/Factories/AutoDomainDataAttribute.cs`, `src/Content/Backend/Solution/Monaco.Template.Backend.Common.Infrastructure/Context/Extensions/FilterExtensions.cs`, `src/Content/Backend/Solution/Monaco.Template.Backend.Common.Infrastructure/Context/Extensions/PagingExtensions.cs`, … (+5 more) — the break is at a TYPE DECLARATION (a C# primary constructor semgrep's grammar cannot parse), so the loss is wider than the named lines: rules scoped to that type see no type to scope to and are blind over its whole body, while rules matching statements keep working there. Absence of a type-scoped finding in those types is not evidence of anything. 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 8 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (8). — One of this dimension's main actionable groups (8 warning-level).
- Resolve the 3 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (3). — One of this dimension's main actionable groups (3 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).
D30 · Dependency Vulnerabilities
3 finding(s): 0 critical, 3 high, 0 medium, 0 low.
What to do
- Resolve the 3 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (3 issue-level).
D32 · Data Compliance (PII/GDPR)
1 finding(s): 0 critical, 0 high, 1 medium, 0 low. semgrep could not parse 19 file(s) — `src/Content/Backend/Solution/Monaco.Template.Backend.Api/Endpoints/Companies.cs`, `src/Content/Backend/Solution/Monaco.Template.Backend.Api/Endpoints/Extensions/EndpointsExtensions.cs`, `src/Content/Backend/Solution/Monaco.Template.Backend.Api/Endpoints/Files.cs`, `src/Content/Backend/Solution/Monaco.Template.Backend.Api/Endpoints/Products.cs`, `src/Content/Backend/Solution/Monaco.Template.Backend.Api/Program.cs`, … (+14 more) — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real.
What to do
- Resolve the 1 REDACTED finding(s) in Data Compliance (PII/GDPR) — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
D34 · Knowledge Freshness
Every significant source file has living knowledge — recently and meaningfully worked. Counted over 27 of the 122 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.
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
Frontend & cross-cutting dimensions
AX1 · Captive dependencies
AX10 · Code composition
AX2 · Stateful singletons
AX3 · Project dependency cycles
- The namespaces Monaco.Template.Backend.Domain.Model.Entities ↔ Monaco.Template.Backend.Domain.Model.ValueObjects depend on each other. The lightest dependency in the cycle is Monaco.Template.Backend.Domain.Model.ValueObjects → Monaco.Template.Backend.Domain.Model.Entities (Monaco.Template.Backend.Domain.Model.ValueObjects.Address → Monaco.Template.Backend.Domain.Model.Entities.Country, 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/Content/Backend/Solution/Monaco.Template.Backend.Domain/Model/ValueObjects/Address.cs:2
- The namespaces Monaco.Template.Backend.Common.BlobStorage ↔ Monaco.Template.Backend.Common.BlobStorage.Contracts depend on each other. The lightest dependency in the cycle is Monaco.Template.Backend.Common.BlobStorage → Monaco.Template.Backend.Common.BlobStorage.Contracts (Monaco.Template.Backend.Common.BlobStorage.BlobStorageService → Monaco.Template.Backend.Common.BlobStorage.Contracts.IBlobStorageService, 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/Content/Backend/Solution/Monaco.Template.Backend.Common.BlobStorage/BlobStorageService.cs:3
What to do
- Break namespace cycles inside a project by moving the shared type to a namespace both sides can use, or by inverting the back edge behind an interface.
AX4 · Dependency direction
AX5 · Architecture & structure
AX6 · Interface segregation
AX7 · Slice cohesion
- `CompanyDto` (slice 'Company') depends on `CountryDto` from slice 'Country'. — src/Content/Backend/Solution/Monaco.Template.Backend.Application/Features/Company/DTOs/CompanyDto.cs:14
- `CompanyExtensions` (slice 'Company') depends on `CountryDto` from slice 'Country'. — src/Content/Backend/Solution/Monaco.Template.Backend.Application/Features/Company/Extensions/CompanyExtensions.cs:69
- `ProductDto` (slice 'Product') depends on `CompanyDto` from slice 'Company'. — src/Content/Backend/Solution/Monaco.Template.Backend.Application/Features/Product/DTOs/ProductDto.cs:11
- `ProductDto` (slice 'Product') depends on `ImageDto` from slice 'File'. — src/Content/Backend/Solution/Monaco.Template.Backend.Application/Features/Product/DTOs/ProductDto.cs:12
- `ProductExtensions` (slice 'Product') depends on `CompanyDto` from slice 'Company'. — src/Content/Backend/Solution/Monaco.Template.Backend.Application/Features/Product/Extensions/ProductExtensions.cs:81
What to do
- Keep slices independent: share cross-slice needs via an explicit contract/shared-kernel, not direct references between slices.
AX8 · Test isolation
AX9 · CQS / query purity
- `Company.Handler` is a read (query) handler but its body writes persistent state one call away, in .Map — a query must stay side-effect-free so reads are safe to retry, cache, and route to a read replica. (×2) — src/Content/Backend/Solution/Monaco.Template.Backend.Application/Features/Company/GetCompanyById.cs:14, src/Content/Backend/Solution/Monaco.Template.Backend.Application/Features/Company/GetCompanyPage.cs:20
- `Product.Handler` is a read (query) handler but its body writes persistent state 2 calls away, in .Map — a query must stay side-effect-free so reads are safe to retry, cache, and route to a read replica. (×2) — src/Content/Backend/Solution/Monaco.Template.Backend.Application/Features/Product/GetProductById.cs:15, src/Content/Backend/Solution/Monaco.Template.Backend.Application/Features/Product/GetProductPage.cs:24
What to do
- Keep query handlers read-only — move the writes/event-publishes into a command handler so reads stay safe to retry, cache, and route to a read replica.
DM1 · Aggregate boundaries
- `Company` references the aggregate root `Product` directly (via `_products`) — hold its `ProductId` instead. — src/Content/Backend/Solution/Monaco.Template.Backend.Domain/Model/Entities/Company.cs:36
- `Company` references the aggregate root `Product` directly (via `Products`) — hold its `ProductId` instead. — src/Content/Backend/Solution/Monaco.Template.Backend.Domain/Model/Entities/Company.cs:37
- `Product` references the aggregate root `Company` directly (via `Company`) — hold its `CompanyId` instead. — src/Content/Backend/Solution/Monaco.Template.Backend.Domain/Model/Entities/Product.cs:42
- `Product` references the aggregate root `Image` directly (via `_pictures`) — hold its `ImageId` instead. — src/Content/Backend/Solution/Monaco.Template.Backend.Domain/Model/Entities/Product.cs:44
- `Product` references the aggregate root `Image` directly (via `Pictures`) — hold its `ImageId` instead. — src/Content/Backend/Solution/Monaco.Template.Backend.Domain/Model/Entities/Product.cs:45
- `Product` references the aggregate root `Image` directly (via `DefaultPicture`) — hold its `ImageId` instead. — src/Content/Backend/Solution/Monaco.Template.Backend.Domain/Model/Entities/Product.cs:48
What to do
- Reference other aggregates by their strongly-typed id, never by object reference, so each aggregate stays an independent consistency boundary.
DM10 · One transaction, one aggregate
DM11 · Constructible invalid state
- `Company`'s public constructor takes `name`, `email`, `webSiteUrl` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `Company` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. — src/Content/Backend/Solution/Monaco.Template.Backend.Domain/Model/Entities/Company.cs:17
- `Country`'s public constructor takes `name` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `Country` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. — src/Content/Backend/Solution/Monaco.Template.Backend.Domain/Model/Entities/Country.cs:13
- `Document`'s public constructor takes `name`, `extension`, `size`, `contentType` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `Document` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. — src/Content/Backend/Solution/Monaco.Template.Backend.Domain/Model/Entities/Document.cs:9
- `Image`'s public constructor takes `name`, `extension`, `size`, `contentType` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `Image` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. — src/Content/Backend/Solution/Monaco.Template.Backend.Domain/Model/Entities/Image.cs:10
- `Product`'s public constructor takes `title`, `description`, `price` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `Product` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. — src/Content/Backend/Solution/Monaco.Template.Backend.Domain/Model/Entities/Product.cs:15
What to do
- Give each aggregate one way in that can refuse — a guarded constructor, value-object parameters that validate themselves, or a private constructor behind a factory that returns a failure.
DM12 · Ambient inputs in the domain
DM2 · Strongly-typed ids
- `Image.ThumbnailId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that. — src/Content/Backend/Solution/Monaco.Template.Backend.Domain/Model/Entities/Image.cs:50
- `Product.CompanyId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that. — src/Content/Backend/Solution/Monaco.Template.Backend.Domain/Model/Entities/Product.cs:41
- `Product.DefaultPictureId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that. — src/Content/Backend/Solution/Monaco.Template.Backend.Domain/Model/Entities/Product.cs:47
What to do
- Adopt strongly-typed ids across the domain — finish the migration or document the boundary; primitive ids invite transposed-argument bugs.
DM4 · Rich vs anemic model
- `Country` is an aggregate/entity with 1 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — src/Content/Backend/Solution/Monaco.Template.Backend.Domain/Model/Entities/Country.cs:7
- `Image` is an aggregate/entity with 5 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — src/Content/Backend/Solution/Monaco.Template.Backend.Domain/Model/Entities/Image.cs:5
What to do
- Move business rules onto the aggregates/entities they govern so invariants are enforced at the source, not in anemic services.
DM5 · Encapsulated state
DM6 · Domain ↔ infrastructure boundary
DM9 · Scattered domain decisions
ED1 · Handler temporal coupling
ED2 · Event/command shape
- `Command` is shaped like a command (one imperative intent) but has 3 handlers. A command should have exactly one handler that owns the decision; multiple handlers means hidden fan-out and unclear ownership. If several things should react, raise an EVENT after the command succeeds and let them subscribe. — src/Content/Backend/Solution/Monaco.Template.Backend.Application/Features/Company/CreateCompany.cs:13
- `Command` is shaped like a command (one imperative intent) but has 4 handlers. A command should have exactly one handler that owns the decision; multiple handlers means hidden fan-out and unclear ownership. If several things should react, raise an EVENT after the command succeeds and let them subscribe. — src/Content/Backend/Solution/Monaco.Template.Backend.Application/Features/Product/CreateProduct.cs:17
What to do
- Keep one handler per command (single owner); use events for the fan-out where many subscribers react.
ED3 · Event naming
- `DomainEvent` reads as an instruction, not a fact that happened. Events describe something that already occurred — name them in the past tense (e.g. `OrderPlaced`, `PaymentCaptured`) so the ubiquitous language stays clear. — src/Content/Backend/Solution/Monaco.Template.Backend.Common.Domain/Model/DomainEvent.cs:11
What to do
- Name events in the past tense — they record facts that already happened.
ED4 · Outbox / dual-write
- `Handler.Handle` writes to the database AND publishes to the message bus in the same flow, with no outbox referenced in this path. These two writes aren't atomic — a crash between them either loses the message (DB committed, publish failed) or emits a phantom event (publish succeeded, DB rolled back). Use the transactional outbox pattern — write the message to an outbox table in the SAME transaction as the state change, and dispatch it from there afterwards — or your platform's equivalent (a broker transaction, or an outbox library from your own ecosystem). — src/Content/Backend/Solution/Monaco.Template.Backend.Application/Features/Product/CreateProduct.cs:83
What to do
- Adopt the transactional outbox pattern so DB writes and message publishes commit atomically — no lost or phantom events on a crash.
GD1 · Unfinished & placeholder code
IC1 · Incompleteness & stubs
M1 · Documentation (README)
What to do
- Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
- Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
- Add a README to the 13 of 13 project(s) that lack one — worth up to 2 pts.
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
M3 · Folder & project structure
- Tests aren't grouped in a dedicated test folder — the test surface isn't separable from production code at a glance.
What to do
- Group tests in the folder your build system expects (tests/, test/, spec/, or your module's test source set) so the test surface is discoverable and CI can scope it.
M4 · Documentation accuracy
P1 · CI/CD gates
What to do
- Run the test suite in CI via an explicit runner step (`dotnet test` for the toolchain this pipeline already uses) and gate merges on it.
P10 · Library API & versioning
- 115/125 types (92%) are public. For a library, every public type is a stability contract — make internal-by-default and expose only the intended API.
- No explicit version was found by any of the six routes this check reads: a `<Version>` or `<VersionPrefix>` property; a `GitVersion` or `MinVer` reference; the split Arcade spelling (`<MajorVersion>` AND `<MinorVersion>` together); a hand-written `[assembly: AssemblyVersion]` in source, with `bin/` and `obj/` excluded so the SDK's generated AssemblyInfo cannot satisfy it; or a version handed to MSBuild by the pipeline, as `-p:Version=` / `-p:PackageVersion=` on a `dotnet build` or `dotnet pack` line. Only project files, first-party source and CI files are read, so a version computed somewhere none of those can see is invisible here. A published library needs explicit semantic versioning so consumers can reason about breaking changes.
What to do
- Make types internal by default; expose only the deliberate public API so internals can change without breaking consumers.
- Stamp a semantic version (csproj <Version> or GitVersion/MinVer) and follow semver for breaking changes.
P2 · Observability
What to do
- Add OpenTelemetry tracing/metrics (ActivitySource / AddMetrics) so requests are traceable across the system, not just health-probable.
P4 · Deployment & Rollback
P6 · Release Hygiene
- No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
What to do
- Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.
P7 · Outbound HTTP resilience
P8 · Schema migrations
PF1 · Benchmark discipline
- No benchmark suite was found by the two searches this check runs. FIRST, a BenchmarkDotNet package reference in any project file — every project the workspace loaded, plus a walk of project files on disk that never loaded, because a benchmark suite is exactly the project a partial load drops. SECOND, a script harness: a file whose name contains `benchmark` and ends `.py`, `.sh`, `.ps1`, `.bash`, `.rb`, `.js` or `.mjs`, credited ONLY when this repository's CI text also mentions benchmarks — a harness no pipeline runs is read as a fixture, deliberately. Neither search can see a benchmark suite in another ecosystem's idiom (a Go `testing.B` file, a JMH or criterion project, a pytest-benchmark run), so this is 'no benchmark found by those two searches', not a verdict that the repository has none. Where code is performance-sensitive, a benchmark guards against silent regressions — but it's a bonus here, not a deduction.
What to do
- Add a benchmarking harness for the hot paths and run it in CI to catch regressions (for .NET, a BenchmarkDotNet project with [MemoryDiagnoser] to track allocations).
PF3 · Async & latency hygiene
- Only 0/54 awaits in library code use ConfigureAwait(false). A library that captures the caller's context can stall or deadlock its host — the classic way a dependency drags an app down.
- `await sender.Send(query, cancellationToken)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. (×6) — src/Content/Backend/Solution/Monaco.Template.Backend.Common.Api.Application/MediatorExtensions.cs:25, src/Content/Backend/Solution/Monaco.Template.Backend.Common.Api.Application/MediatorExtensions.cs:36, src/Content/Backend/Solution/Monaco.Template.Backend.Common.Api.Application/MediatorExtensions.cs:47, …
- `await sender.ExecuteCommandAsync(command, result => TypedResults.Created(string.For...` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/Content/Backend/Solution/Monaco.Template.Backend.Common.Api.Application/MediatorExtensions.cs:95
- `await sender.ExecuteCommandAsync(command, TypedResults.NoContent(), cancellationToken)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/Content/Backend/Solution/Monaco.Template.Backend.Common.Api.Application/MediatorExtensions.cs:108
- `await sender.ExecuteCommandAsync(command, TypedResults.Ok(), cancellationToken)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/Content/Backend/Solution/Monaco.Template.Backend.Common.Api.Application/MediatorExtensions.cs:118
- `await sender.Send(command, cancellationToken)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. (×2) — src/Content/Backend/Solution/Monaco.Template.Backend.Common.Api.Application/MediatorExtensions.cs:133, src/Content/Backend/Solution/Monaco.Template.Backend.Common.Api.Application/MediatorExtensions.cs:159
- `await Validator.ValidateAsync(request, cancellationToken)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. (×2) — src/Content/Backend/Solution/Monaco.Template.Backend.Common.Application/Commands/Behaviors/CommandValidationBehavior.cs:31, src/Content/Backend/Solution/Monaco.Template.Backend.Common.Application/Commands/Behaviors/CommandValidationBehavior.cs:66
- `await next(cancellationToken)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. (×6) — src/Content/Backend/Solution/Monaco.Template.Backend.Common.Application/Commands/Behaviors/CommandValidationBehavior.cs:35, src/Content/Backend/Solution/Monaco.Template.Backend.Common.Application/Commands/Behaviors/CommandValidationBehavior.cs:70, src/Content/Backend/Solution/Monaco.Template.Backend.Common.Application/Commands/Behaviors/CommandValidationBehavior.cs:103, …
- `await Validator.ValidateAsync(request, options => options.IncludeRuleSets(Validator...` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. (×2) — src/Content/Backend/Solution/Monaco.Template.Backend.Common.Application/Commands/Behaviors/CommandValidationBehavior.cs:99, src/Content/Backend/Solution/Monaco.Template.Backend.Common.Application/Commands/Behaviors/CommandValidationBehavior.cs:134
- `await _dbConcurrentRetryPipeline.ExecuteAsync(async ct => { try { return await next...` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. (×2) — src/Content/Backend/Solution/Monaco.Template.Backend.Common.Application/Commands/Behaviors/ConcurrencyExceptionBehavior.cs:49, src/Content/Backend/Solution/Monaco.Template.Backend.Common.Application/Commands/Behaviors/ConcurrencyExceptionBehavior.cs:120
- `await next(ct)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. (×2) — src/Content/Backend/Solution/Monaco.Template.Backend.Common.Application/Commands/Behaviors/ConcurrencyExceptionBehavior.cs:53, src/Content/Backend/Solution/Monaco.Template.Backend.Common.Application/Commands/Behaviors/ConcurrencyExceptionBehavior.cs:124
- `await dbContext.Set<T>() .AsNoTracking() .ApplyFilter(request.QueryParams, mappedFi...` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/Content/Backend/Solution/Monaco.Template.Backend.Common.Application/Queries/Extensions/QueryExtensions.cs:20
- `await query.ApplyFilter(request.QueryParams, mappedFieldsFilter) .ApplySort(request...` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/Content/Backend/Solution/Monaco.Template.Backend.Common.Application/Queries/Extensions/QueryExtensions.cs:51
- `await dbContext.Set<T>() .AsNoTracking() .Where(expression.Invoke(request)) .ApplyF...` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. (×2) — src/Content/Backend/Solution/Monaco.Template.Backend.Common.Application/Queries/Extensions/QueryExtensions.cs:79, src/Content/Backend/Solution/Monaco.Template.Backend.Common.Application/Queries/Extensions/QueryExtensions.cs:113
- `await dbContext.Set<T>() .AsNoTracking() .SingleOrDefaultAsync(x => x.Id == request...` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/Content/Backend/Solution/Monaco.Template.Backend.Common.Application/Queries/Extensions/QueryExtensions.cs:198
- `await dbContext.Set<T>() .AsNoTracking() .Where(expression.Invoke(request)) .Single...` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/Content/Backend/Solution/Monaco.Template.Backend.Common.Application/Queries/Extensions/QueryExtensions.cs:212
- `await dbContext.ExistsAsync<TEntity>(x => x.Id == id.Value, ct)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. (×2) — src/Content/Backend/Solution/Monaco.Template.Backend.Common.Application/Validators/Extensions/ValidatorsExtensions.cs:90, src/Content/Backend/Solution/Monaco.Template.Backend.Common.Application/Validators/Extensions/ValidatorsExtensions.cs:100
- `await blobClient.UploadAsync(stream, null, metadata, cancellationToken: cancellatio...` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/Content/Backend/Solution/Monaco.Template.Backend.Common.BlobStorage/BlobStorageService.cs:23
- `await client.OpenReadAsync(false, cancellationToken: cancellationToken)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/Content/Backend/Solution/Monaco.Template.Backend.Common.BlobStorage/BlobStorageService.cs:31
- `await client.DeleteIfExistsAsync(cancellationToken: cancellationToken)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/Content/Backend/Solution/Monaco.Template.Backend.Common.BlobStorage/BlobStorageService.cs:39
- `await destClient.StartCopyFromUriAsync(sourceClient.Uri, cancellationToken: cancell...` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/Content/Backend/Solution/Monaco.Template.Backend.Common.BlobStorage/BlobStorageService.cs:49
- `await copyOperation.WaitForCompletionAsync(cancellationToken)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/Content/Backend/Solution/Monaco.Template.Backend.Common.BlobStorage/BlobStorageService.cs:50
- `await Publisher.DispatchDomainEventsAsync(this)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/Content/Backend/Solution/Monaco.Template.Backend.Common.Infrastructure/Context/BaseDbContext.cs:56
What to do
- In library code, append .ConfigureAwait(false) to every await (or set <ConfigureAwait>false</ConfigureAwait> / use the analyzer CA2007) so the library never captures the host's context.
S1 · Web-Security Posture
- None of the 11 security response headers the OWASP Secure Headers Project recommends (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options, …) is configured — defense in depth, even when a reverse proxy could set them. (−2.0 on this card.)
- No UseHttpsRedirection/UseHsts and no reverse-proxy signal — transport security is unverified at the app layer. (−2.0 on this card.)
- No ModelState/[ApiController]/FluentValidation signal — inbound payloads reach handlers unvalidated. (−2.0 on this card.)
What to do
- Add security response headers (Content-Security-Policy first, then Strict-Transport-Security, X-Content-Type-Options and a frame policy) — defense in depth, even when a reverse proxy could set them.
- Enforce HTTPS at the app layer (UseHttpsRedirection / UseHsts) — only skip this if a reverse proxy demonstrably terminates TLS.
- Validate inbound models (ModelState/[ApiController]/FluentValidation) to reduce injection and bad-data risk.
X1 · Async correctness
X12 · Unreachable branch
X13 · Undrained process stream
X14 · Bypassable address classification
X15 · Unvalidated length from an untrusted reader
X16 · Unfloored truncation loop
X17 · Uncapped recursion over a caller-supplied document
X18 · Disposal-pattern correctness
X19 · Unrestored process-global state
X2 · Cancellation propagation
- Only 61/62 async methods accept a CancellationToken, so in-flight work can't be stopped early when the caller gives up — whatever ends it in your host (shutdown signal, timeout, abandoned request, user cancel). Thread a token through the call chain and honour it at each await and loop; where a method genuinely cannot be interrupted, omitting it is a deliberate choice — judge against your hosting model.
- No CancellationToken parameter — this work can't be stopped early once started. — src/Content/Backend/Solution/Monaco.Template.Backend.Common.Infrastructure/Context/Extensions/MediatorExtension.cs:11
What to do
- Thread a CancellationToken through async methods so work stops promptly on cancellation.
X20 · Mistyped argument guard
X21 · Side-effecting pattern guard
X22 · Contradicted release guard
X23 · Unguarded diagnostic materialisation
X24 · Document value interpolated into markup unescaped
X25 · Inert configuration knob
X26 · Unsynchronised callback handoff
X27 · Collection changed while being enumerated
X28 · Index access outside its own emptiness guard
X29 · Per-element action decided by a fixed element
X3 · Exception handling
X30 · Support guard that admits what it rejects
X32 · Type resolved by simple name across every loaded assembly
X4 · Structured logging
X5 · Nullable reference types
- ~2.4 `!` suppressions per 1k syntax nodes — 114 suppression(s) across the 47331 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 | 93% | Exemplary | Strongest area. |
| Architecture | 62% | Adequate — gated by AX7 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Maturity | 62% | Adequate — gated by M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 58% | Adequate — gated by P10 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 54% | Adequate — gated by D29 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Domain Modelling | 47% | Adequate — gated by DM1, DM2, DM11 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Event-Driven | 57% | Adequate — gated by ED2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Performance | 60% | Strong | Solid. |
Unscored — 2 check(s) recorded observations but carry no score
- X10 Duplicated predicate — 2 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
- X7 Silent fallback defaults — 2 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 1 control(s) we could not find positive evidence for
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 44 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.
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXR1 Runtime accessibility — This repository has no user interface to render — no markup (HTML, Razor, JSX, Vue, Svelte or server templates), no UI framework dependency, no UI component source and no native UI project — so WCAG's runtime success criteria have nothing to apply to here. Not applicable: this is neither a gap in the scan nor a finding about your code.
- AXS1 Runtime exposed surface — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- C1 Data Protection — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
- C2 Access Controls — This is a dotnet-new template — authorization is deferred to the application you build from it. Add [Authorize]/policies (or imperative guards) when you wire up real users; until then there are no real endpoints to protect.
- C3 Audit Trail — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
- C4 Data Retention — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
- C5 Data-Subject Rights — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
- D12 Dependency Hygiene — Dependency hygiene not measured
- D16 Bus Factor — single-maintainer repository — bus factor is not applicable
- D20 ADR Quality — N/A — this repo declares itself a template / kata / sample / demo; a formal ADR log is deferred to a real application built from it.
- D21 Naming Consistency — N/A — too few peers to establish a naming convention (896 declarations, no unit with a dominant convention).
- D22 Internal API Consistency — No intentionally-exposed public API to evaluate for consistency.
- D23 Boundary Type-Coupling — small single-context codebase (5,537 production LoC in the .NET projects) — bounded contexts are not needed at this size No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Aggregate roots were found in only one source directory (Content), which is a layered codebase, not two contexts. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D25 ADR Conformance — no ADRs to check
- D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
- D36 Supply-chain Provenance & Signing — This is a dotnet-new template — it produces no released artifact to attest. Supply-chain provenance, signing and SBOM are deferred to the application you build from it (add SLSA provenance / cosign signing / an SBOM in your app's release pipeline).
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- D39 IL Efficiency — IL not measured — the 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.
- D44 Platform End-of-Life — Platform end-of-life not assessed — this repository declares no platform this pass reads
- D7 Architectural Integrity — no checkable ADRs and no dependency cycles — architectural integrity not assessed
- D8 Code Coverage — Coverage not measured — analyzer environment
- DM3 Integration-event coupling — no integration events detected — coupling check not applicable
- DM7 Repository granularity — no repository abstraction detected (e.g. uses a document session)
- DM8 Value-object opportunities — not scored — the deterministic rule found 0 candidate clump(s); its rows are withheld until it has a measured precision of 95 % (a sample of fewer than 10 rows cannot show one)
- ED5 Idempotency — not scored — 5 of 6 retry-prone mutations could not be classified (no visible guard and no positive evidence of a double-applied effect)
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
- P3 Security & performance tooling — This repo declares itself a template / kata / sample / demo — code meant to be read or copied, not operated. SAST, secret/dependency scanning and performance benchmarks are deferred to the application you build from it, so their absence is not a defect here. The dimension reactivates once the repo becomes a real app.
- 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.
- 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 — 25 finding(s)
- Aggregate holds a reference to another aggregate: Company._products src/Content/Backend/Solution/Monaco.Template.Backend.Domain/Model/Entities/Company.cs:36
- Aggregate holds a reference to another aggregate: Company.Products src/Content/Backend/Solution/Monaco.Template.Backend.Domain/Model/Entities/Company.cs:37
- Aggregate holds a reference to another aggregate: Product.Company src/Content/Backend/Solution/Monaco.Template.Backend.Domain/Model/Entities/Product.cs:42
- Aggregate holds a reference to another aggregate: Product._pictures src/Content/Backend/Solution/Monaco.Template.Backend.Domain/Model/Entities/Product.cs:44
- Aggregate holds a reference to another aggregate: Product.Pictures src/Content/Backend/Solution/Monaco.Template.Backend.Domain/Model/Entities/Product.cs:45
- Aggregate holds a reference to another aggregate: Product.DefaultPicture src/Content/Backend/Solution/Monaco.Template.Backend.Domain/Model/Entities/Product.cs:48
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Namespace dependency cycle src/Content/Backend/Solution/Monaco.Template.Backend.Domain/Model/ValueObjects/Address.cs:2
- Namespace dependency cycle src/Content/Backend/Solution/Monaco.Template.Backend.Common.BlobStorage/BlobStorageService.cs:3
- Query handler writes persistent state one call away, in .Map: Company.Handler src/Content/Backend/Solution/Monaco.Template.Backend.Application/Features/Company/GetCompanyById.cs:14
- Query handler writes persistent state one call away, in .Map: Company.Handler src/Content/Backend/Solution/Monaco.Template.Backend.Application/Features/Company/GetCompanyPage.cs:20
- Query handler writes persistent state 2 calls away, in .Map: Product.Handler src/Content/Backend/Solution/Monaco.Template.Backend.Application/Features/Product/GetProductById.cs:15
- Query handler writes persistent state 2 calls away, in .Map: Product.Handler src/Content/Backend/Solution/Monaco.Template.Backend.Application/Features/Product/GetProductPage.cs:24
- REDACTED
- REDACTED
- Layer violation: Application → Infrastructure src/Content/Backend/Solution/Monaco.Template.Backend.Application/Monaco.Template.Backend.Application.csproj:21
- Layer violation: Application → Infrastructure src/Content/Backend/Solution/Monaco.Template.Backend.Common.Application/Monaco.Template.Backend.Common.Application.csproj:24
- WriteOnlyPrivateField src/Content/Backend/Solution/Monaco.Template.Backend.Application.Tests/Features/Product/CreateProductHandlerTests.cs:30
- REDACTED
- Dual write (no outbox): Handler.Handle src/Content/Backend/Solution/Monaco.Template.Backend.Application/Features/Product/CreateProduct.cs:83
Serious — 82 finding(s)
- Awaits without ConfigureAwait(false)
- Awaits without ConfigureAwait(false) src/Content/Backend/Solution/Monaco.Template.Backend.Common.Api.Application/MediatorExtensions.cs:25
- Awaits without ConfigureAwait(false) src/Content/Backend/Solution/Monaco.Template.Backend.Common.Api.Application/MediatorExtensions.cs:36
- Awaits without ConfigureAwait(false) src/Content/Backend/Solution/Monaco.Template.Backend.Common.Api.Application/MediatorExtensions.cs:47
- Awaits without ConfigureAwait(false) src/Content/Backend/Solution/Monaco.Template.Backend.Common.Api.Application/MediatorExtensions.cs:59
- Awaits without ConfigureAwait(false) src/Content/Backend/Solution/Monaco.Template.Backend.Common.Api.Application/MediatorExtensions.cs:70
- Awaits without ConfigureAwait(false) src/Content/Backend/Solution/Monaco.Template.Backend.Common.Api.Application/MediatorExtensions.cs:81
- Awaits without ConfigureAwait(false) src/Content/Backend/Solution/Monaco.Template.Backend.Common.Api.Application/MediatorExtensions.cs:95
- Awaits without ConfigureAwait(false) src/Content/Backend/Solution/Monaco.Template.Backend.Common.Api.Application/MediatorExtensions.cs:108
- Awaits without ConfigureAwait(false) src/Content/Backend/Solution/Monaco.Template.Backend.Common.Api.Application/MediatorExtensions.cs:118
- Awaits without ConfigureAwait(false) src/Content/Backend/Solution/Monaco.Template.Backend.Common.Api.Application/MediatorExtensions.cs:133
- Awaits without ConfigureAwait(false) src/Content/Backend/Solution/Monaco.Template.Backend.Common.Api.Application/MediatorExtensions.cs:159
- Awaits without ConfigureAwait(false) src/Content/Backend/Solution/Monaco.Template.Backend.Common.Application/Commands/Behaviors/CommandValidationBehavior.cs:31
- Awaits without ConfigureAwait(false) src/Content/Backend/Solution/Monaco.Template.Backend.Common.Application/Commands/Behaviors/CommandValidationBehavior.cs:35
- Awaits without ConfigureAwait(false) src/Content/Backend/Solution/Monaco.Template.Backend.Common.Application/Commands/Behaviors/CommandValidationBehavior.cs:66
- Awaits without ConfigureAwait(false) src/Content/Backend/Solution/Monaco.Template.Backend.Common.Application/Commands/Behaviors/CommandValidationBehavior.cs:70
- Awaits without ConfigureAwait(false) src/Content/Backend/Solution/Monaco.Template.Backend.Common.Application/Commands/Behaviors/CommandValidationBehavior.cs:99
- Awaits without ConfigureAwait(false) src/Content/Backend/Solution/Monaco.Template.Backend.Common.Application/Commands/Behaviors/CommandValidationBehavior.cs:103
- Awaits without ConfigureAwait(false) src/Content/Backend/Solution/Monaco.Template.Backend.Common.Application/Commands/Behaviors/CommandValidationBehavior.cs:134
- Awaits without ConfigureAwait(false) src/Content/Backend/Solution/Monaco.Template.Backend.Common.Application/Commands/Behaviors/CommandValidationBehavior.cs:140
- Awaits without ConfigureAwait(false) src/Content/Backend/Solution/Monaco.Template.Backend.Common.Application/Commands/Behaviors/ConcurrencyExceptionBehavior.cs:49
- Awaits without ConfigureAwait(false) src/Content/Backend/Solution/Monaco.Template.Backend.Common.Application/Commands/Behaviors/ConcurrencyExceptionBehavior.cs:53
- Awaits without ConfigureAwait(false) src/Content/Backend/Solution/Monaco.Template.Backend.Common.Application/Commands/Behaviors/ConcurrencyExceptionBehavior.cs:70
- Awaits without ConfigureAwait(false) src/Content/Backend/Solution/Monaco.Template.Backend.Common.Application/Commands/Behaviors/ConcurrencyExceptionBehavior.cs:120
- Awaits without ConfigureAwait(false) src/Content/Backend/Solution/Monaco.Template.Backend.Common.Application/Commands/Behaviors/ConcurrencyExceptionBehavior.cs:124
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Cross-slice coupling: Company → Country src/Content/Backend/Solution/Monaco.Template.Backend.Application/Features/Company/DTOs/CompanyDto.cs:14
- Cross-slice coupling: Company → Country src/Content/Backend/Solution/Monaco.Template.Backend.Application/Features/Company/Extensions/CompanyExtensions.cs:69
- Cross-slice coupling: Product → Company src/Content/Backend/Solution/Monaco.Template.Backend.Application/Features/Product/DTOs/ProductDto.cs:11
- Cross-slice coupling: Product → File src/Content/Backend/Solution/Monaco.Template.Backend.Application/Features/Product/DTOs/ProductDto.cs:12
- Cross-slice coupling: Product → Company src/Content/Backend/Solution/Monaco.Template.Backend.Application/Features/Product/Extensions/ProductExtensions.cs:81
- Constructible in an invalid state: Company src/Content/Backend/Solution/Monaco.Template.Backend.Domain/Model/Entities/Company.cs:17
- Constructible in an invalid state: Country src/Content/Backend/Solution/Monaco.Template.Backend.Domain/Model/Entities/Country.cs:13
- Constructible in an invalid state: Document src/Content/Backend/Solution/Monaco.Template.Backend.Domain/Model/Entities/Document.cs:9
- Constructible in an invalid state: Image src/Content/Backend/Solution/Monaco.Template.Backend.Domain/Model/Entities/Image.cs:10
- Constructible in an invalid state: Product src/Content/Backend/Solution/Monaco.Template.Backend.Domain/Model/Entities/Product.cs:15
- Dead code: SetupDbSetMock src/Content/Backend/Solution/Monaco.Template.Backend.Common.Tests/DbContextMockExtensions.cs:12
- Dead code: HavePropertySetterWithVisibility src/Content/Backend/Solution/Monaco.Template.Backend.ArchitectureTests/Extensions/ArchUnitExtensions.cs:19
- Dead code: AddressFactory src/Content/Backend/Solution/Monaco.Template.Backend.Domain.Tests/Factories/Entities/AddressFactory.cs:9
- Dead code: Mock src/Content/Backend/Solution/Monaco.Template.Backend.Domain.Tests/Factories/Entities/CompanyFactory.cs:21
- REDACTED
- REDACTED
- Anemic entity: Country src/Content/Backend/Solution/Monaco.Template.Backend.Domain/Model/Entities/Country.cs:7
- Anemic entity: Image src/Content/Backend/Solution/Monaco.Template.Backend.Domain/Model/Entities/Image.cs:5
- FilterExtensions.ValidateDataType (cyclomatic 23) src/Content/Backend/Solution/Monaco.Template.Backend.Common.Infrastructure/Context/Extensions/FilterExtensions.cs:156
- FilterExtensions.GetOperationExpression (cyclomatic 20) src/Content/Backend/Solution/Monaco.Template.Backend.Common.Infrastructure/Context/Extensions/FilterExtensions.cs:95
- FilterExtensions.GetOperationExpression (cognitive 30) src/Content/Backend/Solution/Monaco.Template.Backend.Common.Infrastructure/Context/Extensions/FilterExtensions.cs:95
- REDACTED
- MethodTooLong: CountrySeed.GetCountries src/Content/Backend/Solution/Monaco.Template.Backend.Application/Persistence/EntityConfigurations/Seeds/CountrySeed.cs:5
- REDACTED
- Duplicated block (23 lines × 2) src/Content/Backend/Solution/Monaco.Template.Backend.Application/Features/Company/CreateCompany.cs:34
- Duplicated block (11–19 lines × 2) src/Content/Backend/Solution/Monaco.Template.Backend.Api/Program.cs:51
- Duplicated block (10 lines × 2) src/Content/Backend/Solution/Monaco.Template.Backend.Application/Features/Product/CreateProduct.cs:36
- Duplicated block (11 lines × 2) src/Content/Backend/Solution/Monaco.Template.Backend.Common.Serilog/ApplicationInsights/TelemetryConverters/AuditEventTelemetryConverter.cs:38
- Duplicated block (8–9 lines × 2) src/Content/Backend/Solution/Monaco.Template.Backend.Common.Infrastructure/Context/Extensions/FilterExtensions.cs:25
- Duplicated block (8 lines × 2) src/Content/Backend/Solution/Monaco.Template.Backend.Application/Features/Product/CreateProduct.cs:54
- Duplicated block (7 lines × 2) src/Content/Backend/Solution/Monaco.Template.Backend.Common.Serilog/ApplicationInsights/TelemetryConverters/AuditEventTelemetryConverter.cs:52
- Command with 3 handlers: Command src/Content/Backend/Solution/Monaco.Template.Backend.Application/Features/Company/CreateCompany.cs:13
- Command with 4 handlers: Command src/Content/Backend/Solution/Monaco.Template.Backend.Application/Features/Product/CreateProduct.cs:17
- Async method without CancellationToken: DispatchDomainEventsAsync src/Content/Backend/Solution/Monaco.Template.Backend.Common.Infrastructure/Context/Extensions/MediatorExtension.cs:11
Minor — 24 finding(s)
- redundant comment src/Content/Backend/Solution/Monaco.Template.Backend.Api/Program.cs:38
- redundant comment src/Content/Backend/Solution/Monaco.Template.Backend.Api/Program.cs:105
- redundant comment REDACTED:18
- redundant comment src/Content/Backend/Solution/Monaco.Template.Backend.Common.ApiGateway/Program.cs:11
- redundant comment src/Content/Backend/Solution/Monaco.Template.Backend.Common.ApiGateway/Program.cs:25
- Primitive id on a domain type: Image.ThumbnailId src/Content/Backend/Solution/Monaco.Template.Backend.Domain/Model/Entities/Image.cs:50
- Primitive id on a domain type: Product.CompanyId src/Content/Backend/Solution/Monaco.Template.Backend.Domain/Model/Entities/Product.cs:41
- Primitive id on a domain type: Product.DefaultPictureId src/Content/Backend/Solution/Monaco.Template.Backend.Domain/Model/Entities/Product.cs:47
- Duplicated predicate src/Content/Backend/Solution/Monaco.Template.Backend.Common.Serilog/ApplicationInsights/TelemetryConverters/AuditEventTelemetryConverter.cs:52
- Duplicated predicate src/Content/Backend/Solution/Monaco.Template.Backend.Application/Features/Company/CreateCompany.cs:56
- Silent fallback default on parse failure src/Content/Backend/Solution/Monaco.Template.Backend.Common.Application/Queries/QueryPagedBase.cs:10
- Silent fallback default on parse failure src/Content/Backend/Solution/Monaco.Template.Backend.Common.Application/Queries/QueryPagedBase.cs:17
- Event not named in past tense: DomainEvent src/Content/Backend/Solution/Monaco.Template.Backend.Common.Domain/Model/DomainEvent.cs:11
- No ADRs
- No tests/ separation
- Large public API surface
- No explicit versioning
- No changelog
- No performance benchmarks
- No security response headers detected
- No app-layer HTTPS enforcement detected
- No inbound model validation detected
- Not all async methods take a CancellationToken
- Null-forgiving operator (`!`) suppressions reduce the NRT score
Minor — 9 finding(s)
- doc comments repeat the names src/Content/Backend/Solution/Monaco.Template.Backend.Application/DependencyInjection/ServiceCollectionExtensions.cs:27
- doc comments repeat the names src/Content/Backend/Solution/Monaco.Template.Backend.Common.Api/Auth/AuthExtensions.cs:49
- doc comments repeat the names src/Content/Backend/Solution/Monaco.Template.Backend.Common.Api.Application/MediatorExtensions.cs:20
- doc comments repeat the names src/Content/Backend/Solution/Monaco.Template.Backend.Common.Application/Commands/CommandBase.cs:11
- Off the main sequence: Monaco.Template.Backend.Common.Api REDACTED:1
- Off the main sequence: Monaco.Template.Backend.Common.Serilog src/Content/Backend/Solution/Monaco.Template.Backend.Common.Serilog/Monaco.Template.Backend.Common.Serilog.csproj:1
- Off the main sequence: Monaco.Template.Backend.Common.BlobStorage src/Content/Backend/Solution/Monaco.Template.Backend.Common.BlobStorage/Monaco.Template.Backend.Common.BlobStorage.csproj:1
- Mock framework: Moq
- Mock framework: Moq
Appendix B — Reproduction & audit trail
| Dimension | Tool | Version | Command | Findings | Raw output |
|---|---|---|---|---|---|
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-9741838fe09a46e8b6c5b8c2eff9c58e/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-9741838fe09a46e8b6c5b8c2eff9c58e/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/Content/Backend/Solution/Monaco.Template.Backend.Application/Persistence/Migrations . | 15 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | dotnet | — | dotnet list src/Content/Backend/Solution/Monaco.Template.Backend.slnx package --vulnerable --include-transitive --format json | 3 | artifacts/raw/dotnet-vulnerable.json |
| D31 · IaC & Container Security | trivy | — | trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan. | 0 | — |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep --config /opt/semgrep-rules/gdpr.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/Content/Backend/Solution/Monaco.Template.Backend.Application/Persistence/Migrations . | 1 | artifacts/raw/semgrep-gdpr.json |
| D36 · Supply-chain Provenance & Signing | provenance | — | provenance: not applicable — This is a dotnet-new template — it produces no released artifact to attest. Supply-chain provenance, signing and SBOM are deferred to the application you build from it (add SLSA provenance / cosign signing / an SBOM in your app's release pipeline). | 0 | — |
| D37 · Vulnerability-disclosure Policy | disclosure | — | disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed. | 0 | — |
| 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-e9030dfa4bf94e42a7eea0852890a74f | 0 | artifacts/raw/osv-scanner.json |
Appendix C — Personal-data map
Email — 5 field(s)
- CompanyCreateEditDto.Email src/Content/Backend/Solution/Monaco.Template.Backend.Api/DTOs/CompanyCreateEditDto.cs:4
- Command.Email src/Content/Backend/Solution/Monaco.Template.Backend.Application/Features/Company/CreateCompany.cs:14
- CompanyDto.Email src/Content/Backend/Solution/Monaco.Template.Backend.Application/Features/Company/DTOs/CompanyDto.cs:7
- Command.Email src/Content/Backend/Solution/Monaco.Template.Backend.Application/Features/Company/EditCompany.cs:17
- Company.Email src/Content/Backend/Solution/Monaco.Template.Backend.Domain/Model/Entities/Company.cs:29