Executive summary
EdwinVW/cloud-native-net is rated At risk because critical security findings are open, all of them in the packages it uses. Its score is held back because we found no working pipeline that builds or tests changes to the code and no automated security scanning of the code, its secrets or its dependencies. It scores 44 out of 100, which the At risk rating leaves unchanged.
Production Readiness, at 34, is the weakest lens and counts most in the score. The best first step is adding access checks, worth about 6 points. Adding an automated build and test pipeline would lift Production Readiness itself, worth about 5 points. Raising Production Readiness to 70 would lift the score to about 52.
Nine known security holes in the packages the code depends on can be used by attackers. Updating the vulnerable packages would close this risk. The three data fields that are written but never read need removing.
The product code is 3,532 lines, about €6,500 to rebuild.
If Production Readiness rose from 34 to 70, the lowest score rated Strong, the score would rise from 44 to about 52.
New since the last survey: 11 findings
- Platform End-of-Life · End-of-life runtime: .NET net6.0 REDACTED
- Platform End-of-Life · End-of-life runtime: .NET net6.0 REDACTED
- Platform End-of-Life · End-of-life runtime: .NET net6.0 src/Common/Domain.Common/Domain.Common.csproj
- Platform End-of-Life · End-of-life runtime: .NET net6.0 REDACTED
- Platform End-of-Life · End-of-life runtime: .NET net6.0 src/ContractManagement/Application/Application.csproj
- Platform End-of-Life · End-of-life runtime: .NET net6.0 REDACTED
- Platform End-of-Life · End-of-life runtime: .NET net6.0 src/ContractManagement/Domain/Domain.csproj
- Platform End-of-Life · End-of-life runtime: .NET net6.0 src/ContractManagement/Infrastructure/Infrastructure.csproj
- Platform End-of-Life · End-of-life runtime: .NET net6.0 src/ContractManagement/Interface/MessageReceiver/MessageReceiver.csproj
- Platform End-of-Life · End-of-life runtime: .NET net6.0 src/ContractManagement/Interface/WebAPI/WebAPI.csproj
- Platform End-of-Life · End-of-life runtime: .NET net6.0 src/OutputManagement/OutputManagementService/OutputManagementService.csproj
Fixed since the last survey: 24 findings
- Platform End-of-Life · End-of-life runtime: .NET net6.0 src/OutputManagement/OutputManagementService/OutputManagementService.csproj
- Cancellation propagation · Async method without CancellationToken: AddProductAsync src/ContractManagement/Infrastructure/Persistence/EFCore/ReadModel/EFProductReadModelRepository.cs
- Cancellation propagation · Async method without CancellationToken: SaveChangeAsync src/ContractManagement/Infrastructure/Persistence/EFCore/ReadModel/EFProductReadModelRepository.cs
- Cancellation propagation · Async method without CancellationToken: HandleRegisterContractV2 REDACTED
- Cancellation propagation · Async method without CancellationToken: ChangeContractAmount REDACTED
- Cancellation propagation · Async method without CancellationToken: ChangeContractTerm REDACTED
- Cancellation propagation · Async method without CancellationToken: CancelContract REDACTED
- Cancellation propagation · Async method without CancellationToken: AddDocument REDACTED
- Cancellation propagation · Async method without CancellationToken: HandleCommand REDACTED
- Cancellation propagation · Async method without CancellationToken: ConsumeMessage src/OutputManagement/OutputManagementService/Consumers/ContractAmountChangedConsumer.cs
- Cancellation propagation · Async method without CancellationToken: ConsumeMessage src/OutputManagement/OutputManagementService/Consumers/ContractCancelledConsumer.cs
- Cancellation propagation · Async method without CancellationToken: ConsumeMessage src/OutputManagement/OutputManagementService/Consumers/ContractRegisteredConsumer.cs
- Cancellation propagation · Async method without CancellationToken: ConsumeMessage src/OutputManagement/OutputManagementService/Consumers/ContractTermChangedConsumer.cs
- Cancellation propagation · Async method without CancellationToken: ConsumeMessage src/OutputManagement/OutputManagementService/Consumers/CustomerRegisteredConsumer.cs
- Cancellation propagation · Async method without CancellationToken: ConsumeMessage src/OutputManagement/OutputManagementService/Consumers/DayHasPassedConsumer.cs
- Cancellation propagation · Async method without CancellationToken: ConsumeMessage src/OutputManagement/OutputManagementService/Consumers/ProductRegisteredConsumer.cs
- Cancellation propagation · Async method without CancellationToken: PublishDayHasPassed src/!Support/MessageSender/MessageSender.cs
- Cancellation propagation · Async method without CancellationToken: PublishCustomerRegistered src/!Support/MessageSender/MessageSender.cs
- Cancellation propagation · Async method without CancellationToken: PublishProductRegistered src/!Support/MessageSender/MessageSender.cs
- Cancellation propagation · Async method without CancellationToken: RegisterContract src/!Support/MessageSender/MessageSender.cs
- Cancellation propagation · Async method without CancellationToken: ChangeContractAmount src/!Support/MessageSender/MessageSender.cs
- Cancellation propagation · Async method without CancellationToken: ChangeContractTerm src/!Support/MessageSender/MessageSender.cs
- Cancellation propagation · Async method without CancellationToken: CancelContract src/!Support/MessageSender/MessageSender.cs
- Cancellation propagation · Async method without CancellationToken: CallAPI src/!Support/MessageSender/MessageSender.cs
Rebuild cost: about €6,500 · Estimate
| Cost to rebuild | €2,200 to €11,000, for 36 to 113 hours of work, under 0.1 person-years for one engineer |
|---|---|
| Difficulty of the problem | Very high, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.7 at a score of 44. 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: 3,532 lines of product code, of which 41% is declarations and boilerplate, 49% straight logic and 10% 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 Application.Common.Exceptions | 3 ContractManagement.Domain.Aggregates.Contract.Enums | 4 ContractManagement.Domain.Aggregates.Portfolio.Enums | 5 ContractManagement.Domain.Services | 6 ContractManagement.Domain.ValueObjects | 7 Domain.Common | 8 Generic.IntegrationEvents | 9 OutputManagementService.EmailService | 10 Application.Common.Interfaces | 11 ContractManagement.Application.ReadModels | 12 ContractManagement.Domain.Aggregates.Contract.Commands | 13 ContractManagement.Domain.Aggregates.Portfolio.Commands | 14 CustomerManagement.Application.IntegrationEvents | 15 OutputManagementService.ReadModels | 16 ProductManagement.Application.IntegrationEvents | 17 Application.Common.Services | 18 ContractManagement.Application.Interfaces | 19 ContractManagement.Domain.Aggregates.Contract.DomainEvents | 20 ContractManagement.Domain.Aggregates.Portfolio | 21 ContractManagement.Domain.Aggregates.Portfolio.DomainEvents | 22 ContractManagement.Infrastructure.Persistence.EFCore.ReadModel.Configurations | 23 Infrastructure.Common.Messaging.MassTransit | 24 Infrastructure.Common.Persistence.EFCore.Repositories.Aggregate | 25 Infrastructure.Common.UnitOfWork | 26 OutputManagementService.Repositories | 27 ContractManagement.Application.EventHandlers.IntegrationEvents | 28 ContractManagement.Application.IntegrationEvents | 29 ContractManagement.Application.Services | 30 ContractManagement.Domain.Aggregates.Contract | 31 ContractManagement.Infrastructure.Persistence.EFCore | 32 ContractManagement.Infrastructure.Persistence.EFCore.Configurations | 33 Contractmanagement.Features.Documents | 34 Infrastructure.Common.Persistence.EFCore.Configurations | 35 ContractManagement.Infrastructure.Persistence.EFCore.Repositories | 36 ContractManagement.WebAPI.Controllers | 37 Contractmanagement.Features.ContractCancellation | 38 Contractmanagement.Features.ContractMaintenance | 39 Contractmanagement.Features.ContractRegistration | 40 OutputManagementService.Consumers |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 (global) | ||||||||||||||||||||||||||||||||||||||||
| 2 Application.Common.Exceptions | ||||||||||||||||||||||||||||||||||||||||
| 3 ContractManagement.Domain.Aggregates.Contract.Enums | ||||||||||||||||||||||||||||||||||||||||
| 4 ContractManagement.Domain.Aggregates.Portfolio.Enums | ||||||||||||||||||||||||||||||||||||||||
| 5 ContractManagement.Domain.Services | ||||||||||||||||||||||||||||||||||||||||
| 6 ContractManagement.Domain.ValueObjects | ||||||||||||||||||||||||||||||||||||||||
| 7 Domain.Common | ||||||||||||||||||||||||||||||||||||||||
| 8 Generic.IntegrationEvents | ||||||||||||||||||||||||||||||||||||||||
| 9 OutputManagementService.EmailService | ||||||||||||||||||||||||||||||||||||||||
| 10 Application.Common.Interfaces | 3 | |||||||||||||||||||||||||||||||||||||||
| 11 ContractManagement.Application.ReadModels | 1 | |||||||||||||||||||||||||||||||||||||||
| 12 ContractManagement.Domain.Aggregates.Contract.Commands | 1 | 5 | ||||||||||||||||||||||||||||||||||||||
| 13 ContractManagement.Domain.Aggregates.Portfolio.Commands | 2 | |||||||||||||||||||||||||||||||||||||||
| 14 CustomerManagement.Application.IntegrationEvents | 1 | |||||||||||||||||||||||||||||||||||||||
| 15 OutputManagementService.ReadModels | 1 | |||||||||||||||||||||||||||||||||||||||
| 16 ProductManagement.Application.IntegrationEvents | 1 | |||||||||||||||||||||||||||||||||||||||
| 17 Application.Common.Services | 1 | 7 | ||||||||||||||||||||||||||||||||||||||
| 18 ContractManagement.Application.Interfaces | 3 | |||||||||||||||||||||||||||||||||||||||
| 19 ContractManagement.Domain.Aggregates.Contract.DomainEvents | 1 | 5 | 5 | |||||||||||||||||||||||||||||||||||||
| 20 ContractManagement.Domain.Aggregates.Portfolio | 1 | 2 | 2 | |||||||||||||||||||||||||||||||||||||
| 21 ContractManagement.Domain.Aggregates.Portfolio.DomainEvents | 2 | 2 | ||||||||||||||||||||||||||||||||||||||
| 22 ContractManagement.Infrastructure.Persistence.EFCore.ReadModel.Configurations | 2 | |||||||||||||||||||||||||||||||||||||||
| 23 Infrastructure.Common.Messaging.MassTransit | 1 | 3 | ||||||||||||||||||||||||||||||||||||||
| 24 Infrastructure.Common.Persistence.EFCore.Repositories.Aggregate | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 25 Infrastructure.Common.UnitOfWork | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 26 OutputManagementService.Repositories | 6 | |||||||||||||||||||||||||||||||||||||||
| 27 ContractManagement.Application.EventHandlers.IntegrationEvents | 2 | 1 | 1 | 2 | ||||||||||||||||||||||||||||||||||||
| 28 ContractManagement.Application.IntegrationEvents | 1 | 4 | 4 | |||||||||||||||||||||||||||||||||||||
| 29 ContractManagement.Application.Services | 2 | 2 | 2 | |||||||||||||||||||||||||||||||||||||
| 30 ContractManagement.Domain.Aggregates.Contract | 1 | 2 | 5 | 2 | 4 | 4 | ||||||||||||||||||||||||||||||||||
| 31 ContractManagement.Infrastructure.Persistence.EFCore | 3 | 2 | ||||||||||||||||||||||||||||||||||||||
| 32 ContractManagement.Infrastructure.Persistence.EFCore.Configurations | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 33 Contractmanagement.Features.Documents | 4 | 2 | 2 | |||||||||||||||||||||||||||||||||||||
| 34 Infrastructure.Common.Persistence.EFCore.Configurations | 2 | |||||||||||||||||||||||||||||||||||||||
| 35 ContractManagement.Infrastructure.Persistence.EFCore.Repositories | 3 | 3 | 3 | |||||||||||||||||||||||||||||||||||||
| 36 ContractManagement.WebAPI.Controllers | 1 | 2 | 5 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 37 Contractmanagement.Features.ContractCancellation | 5 | 1 | 1 | 2 | 1 | |||||||||||||||||||||||||||||||||||
| 38 Contractmanagement.Features.ContractMaintenance | 10 | 2 | 2 | 2 | 2 | |||||||||||||||||||||||||||||||||||
| 39 Contractmanagement.Features.ContractRegistration | 2 | 6 | 1 | 1 | 1 | 3 | 1 | |||||||||||||||||||||||||||||||||
| 40 OutputManagementService.Consumers | 1 | 1 | 1 | 1 | 9 | 4 |
10→7 Application.Common.Interfaces uses Domain.Common✕
- Connections
- 3 pairs of types, where a type in Application.Common.Interfaces uses a type in Domain.Common.
- The types involved
Application.Common.Interfaces.IEventPublisher→Domain.Common.EventApplication.Common.Interfaces.IProjectionEngine→Domain.Common.EventApplication.Common.Interfaces.IUnitOfWork→Domain.Common.Event
- Direction
- Application.Common.Interfaces uses Domain.Common, so a change to Domain.Common can break Application.Common.Interfaces, while a change to Application.Common.Interfaces can't break Domain.Common.
- Position
- Below the diagonal: Application.Common.Interfaces uses a module listed above it, which is the healthy direction.
11→3 ContractManagement.Application.ReadModels uses ContractManagement.Domain.Aggregates.Contract.Enums✕
- Connections
- 1 pair of types, where a type in ContractManagement.Application.ReadModels uses a type in ContractManagement.Domain.Aggregates.Contract.Enums.
- The types involved
ContractManagement.Application.ReadModels.Contract→ContractManagement.Domain.Aggregates.Contract.Enums.PaymentPeriod
- Direction
- ContractManagement.Application.ReadModels uses ContractManagement.Domain.Aggregates.Contract.Enums, so a change to ContractManagement.Domain.Aggregates.Contract.Enums can break ContractManagement.Application.ReadModels, while a change to ContractManagement.Application.ReadModels can't break ContractManagement.Domain.Aggregates.Contract.Enums.
- Position
- Below the diagonal: ContractManagement.Application.ReadModels uses a module listed above it, which is the healthy direction.
12→3 ContractManagement.Domain.Aggregates.Contract.Commands uses ContractManagement.Domain.Aggregates.Contract.Enums✕
- Connections
- 1 pair of types, where a type in ContractManagement.Domain.Aggregates.Contract.Commands uses a type in ContractManagement.Domain.Aggregates.Contract.Enums.
- The types involved
ContractManagement.Domain.Aggregates.Contract.Commands.RegisterContractV2→ContractManagement.Domain.Aggregates.Contract.Enums.PaymentPeriod
- Direction
- ContractManagement.Domain.Aggregates.Contract.Commands uses ContractManagement.Domain.Aggregates.Contract.Enums, so a change to ContractManagement.Domain.Aggregates.Contract.Enums can break ContractManagement.Domain.Aggregates.Contract.Commands, while a change to ContractManagement.Domain.Aggregates.Contract.Commands can't break ContractManagement.Domain.Aggregates.Contract.Enums.
- Position
- Below the diagonal: ContractManagement.Domain.Aggregates.Contract.Commands uses a module listed above it, which is the healthy direction.
12→7 ContractManagement.Domain.Aggregates.Contract.Commands uses Domain.Common✕
- Connections
- 5 pairs of types, where a type in ContractManagement.Domain.Aggregates.Contract.Commands uses a type in Domain.Common.
- The types involved
ContractManagement.Domain.Aggregates.Contract.Commands.CancelContract→Domain.Common.CommandContractManagement.Domain.Aggregates.Contract.Commands.ChangeContractAmount→Domain.Common.CommandContractManagement.Domain.Aggregates.Contract.Commands.ChangeContractTerm→Domain.Common.CommandContractManagement.Domain.Aggregates.Contract.Commands.RegisterContract→Domain.Common.CommandContractManagement.Domain.Aggregates.Contract.Commands.RegisterContractV2→Domain.Common.Command
- Direction
- ContractManagement.Domain.Aggregates.Contract.Commands uses Domain.Common, so a change to Domain.Common can break ContractManagement.Domain.Aggregates.Contract.Commands, while a change to ContractManagement.Domain.Aggregates.Contract.Commands can't break Domain.Common.
- Position
- Below the diagonal: ContractManagement.Domain.Aggregates.Contract.Commands uses a module listed above it, which is the healthy direction.
13→7 ContractManagement.Domain.Aggregates.Portfolio.Commands uses Domain.Common✕
- Connections
- 2 pairs of types, where a type in ContractManagement.Domain.Aggregates.Portfolio.Commands uses a type in Domain.Common.
- The types involved
ContractManagement.Domain.Aggregates.Portfolio.Commands.AddDocument→Domain.Common.CommandContractManagement.Domain.Aggregates.Portfolio.Commands.CreatePortfolio→Domain.Common.Command
- Direction
- ContractManagement.Domain.Aggregates.Portfolio.Commands uses Domain.Common, so a change to Domain.Common can break ContractManagement.Domain.Aggregates.Portfolio.Commands, while a change to ContractManagement.Domain.Aggregates.Portfolio.Commands can't break Domain.Common.
- Position
- Below the diagonal: ContractManagement.Domain.Aggregates.Portfolio.Commands uses a module listed above it, which is the healthy direction.
14→7 CustomerManagement.Application.IntegrationEvents uses Domain.Common✕
- Connections
- 1 pair of types, where a type in CustomerManagement.Application.IntegrationEvents uses a type in Domain.Common.
- The types involved
CustomerManagement.Application.IntegrationEvents.CustomerRegistered→Domain.Common.Event
- Direction
- CustomerManagement.Application.IntegrationEvents uses Domain.Common, so a change to Domain.Common can break CustomerManagement.Application.IntegrationEvents, while a change to CustomerManagement.Application.IntegrationEvents can't break Domain.Common.
- Position
- Below the diagonal: CustomerManagement.Application.IntegrationEvents uses a module listed above it, which is the healthy direction.
15→3 OutputManagementService.ReadModels uses ContractManagement.Domain.Aggregates.Contract.Enums✕
- Connections
- 1 pair of types, where a type in OutputManagementService.ReadModels uses a type in ContractManagement.Domain.Aggregates.Contract.Enums.
- The types involved
OutputManagementService.ReadModels.Contract→ContractManagement.Domain.Aggregates.Contract.Enums.PaymentPeriod
- Direction
- OutputManagementService.ReadModels uses ContractManagement.Domain.Aggregates.Contract.Enums, so a change to ContractManagement.Domain.Aggregates.Contract.Enums can break OutputManagementService.ReadModels, while a change to OutputManagementService.ReadModels can't break ContractManagement.Domain.Aggregates.Contract.Enums.
- Position
- Below the diagonal: OutputManagementService.ReadModels uses a module listed above it, which is the healthy direction.
16→7 ProductManagement.Application.IntegrationEvents uses Domain.Common✕
- Connections
- 1 pair of types, where a type in ProductManagement.Application.IntegrationEvents uses a type in Domain.Common.
- The types involved
ProductManagement.Application.IntegrationEvents.ProductRegistered→Domain.Common.Event
- Direction
- ProductManagement.Application.IntegrationEvents uses Domain.Common, so a change to Domain.Common can break ProductManagement.Application.IntegrationEvents, while a change to ProductManagement.Application.IntegrationEvents can't break Domain.Common.
- Position
- Below the diagonal: ProductManagement.Application.IntegrationEvents uses a module listed above it, which is the healthy direction.
17→7 Application.Common.Services uses Domain.Common✕
- Connections
- 1 pair of types, where a type in Application.Common.Services uses a type in Domain.Common.
- The types involved
Application.Common.Services.ProjectionEngine→Domain.Common.Event
- Direction
- Application.Common.Services uses Domain.Common, so a change to Domain.Common can break Application.Common.Services, while a change to Application.Common.Services can't break Domain.Common.
- Position
- Below the diagonal: Application.Common.Services uses a module listed above it, which is the healthy direction.
17→10 Application.Common.Services uses Application.Common.Interfaces✕
- Connections
- 7 pairs of types, where a type in Application.Common.Services uses a type in Application.Common.Interfaces.
- The types involved
Application.Common.Services.AggregateService→Application.Common.Interfaces.IAggregateRepositoryApplication.Common.Services.AggregateService→Application.Common.Interfaces.IAggregateServiceApplication.Common.Services.AggregateService→Application.Common.Interfaces.IEventPublisherApplication.Common.Services.AggregateService→Application.Common.Interfaces.IProjectionEngineApplication.Common.Services.AggregateService→Application.Common.Interfaces.IUnitOfWorkApplication.Common.Services.ProjectionEngine→Application.Common.Interfaces.IApplicationServiceApplication.Common.Services.ProjectionEngine→Application.Common.Interfaces.IProjectionEngine
- Direction
- Application.Common.Services uses Application.Common.Interfaces, so a change to Application.Common.Interfaces can break Application.Common.Services, while a change to Application.Common.Services can't break Application.Common.Interfaces.
- Position
- Below the diagonal: Application.Common.Services uses a module listed above it, which is the healthy direction.
18→11 ContractManagement.Application.Interfaces uses ContractManagement.Application.ReadModels✕
- Connections
- 3 pairs of types, where a type in ContractManagement.Application.Interfaces uses a type in ContractManagement.Application.ReadModels.
- The types involved
ContractManagement.Application.Interfaces.IContractReadModelRepository→ContractManagement.Application.ReadModels.ContractContractManagement.Application.Interfaces.ICustomerReadModelRepository→ContractManagement.Application.ReadModels.CustomerContractManagement.Application.Interfaces.IProductReadModelRepository→ContractManagement.Application.ReadModels.Product
- Direction
- ContractManagement.Application.Interfaces uses ContractManagement.Application.ReadModels, so a change to ContractManagement.Application.ReadModels can break ContractManagement.Application.Interfaces, while a change to ContractManagement.Application.Interfaces can't break ContractManagement.Application.ReadModels.
- Position
- Below the diagonal: ContractManagement.Application.Interfaces uses a module listed above it, which is the healthy direction.
19→3 ContractManagement.Domain.Aggregates.Contract.DomainEvents uses ContractManagement.Domain.Aggregates.Contract.Enums✕
- Connections
- 1 pair of types, where a type in ContractManagement.Domain.Aggregates.Contract.DomainEvents uses a type in ContractManagement.Domain.Aggregates.Contract.Enums.
- The types involved
ContractManagement.Domain.Aggregates.Contract.DomainEvents.ContractRegisteredV2→ContractManagement.Domain.Aggregates.Contract.Enums.PaymentPeriod
- Direction
- ContractManagement.Domain.Aggregates.Contract.DomainEvents uses ContractManagement.Domain.Aggregates.Contract.Enums, so a change to ContractManagement.Domain.Aggregates.Contract.Enums can break ContractManagement.Domain.Aggregates.Contract.DomainEvents, while a change to ContractManagement.Domain.Aggregates.Contract.DomainEvents can't break ContractManagement.Domain.Aggregates.Contract.Enums.
- Position
- Below the diagonal: ContractManagement.Domain.Aggregates.Contract.DomainEvents uses a module listed above it, which is the healthy direction.
19→7 ContractManagement.Domain.Aggregates.Contract.DomainEvents uses Domain.Common✕
- Connections
- 5 pairs of types, where a type in ContractManagement.Domain.Aggregates.Contract.DomainEvents uses a type in Domain.Common.
- The types involved
ContractManagement.Domain.Aggregates.Contract.DomainEvents.ContractAmountChanged→Domain.Common.EventContractManagement.Domain.Aggregates.Contract.DomainEvents.ContractCancelled→Domain.Common.EventContractManagement.Domain.Aggregates.Contract.DomainEvents.ContractRegistered→Domain.Common.EventContractManagement.Domain.Aggregates.Contract.DomainEvents.ContractRegisteredV2→Domain.Common.EventContractManagement.Domain.Aggregates.Contract.DomainEvents.ContractTermChanged→Domain.Common.Event
- Direction
- ContractManagement.Domain.Aggregates.Contract.DomainEvents uses Domain.Common, so a change to Domain.Common can break ContractManagement.Domain.Aggregates.Contract.DomainEvents, while a change to ContractManagement.Domain.Aggregates.Contract.DomainEvents can't break Domain.Common.
- Position
- Below the diagonal: ContractManagement.Domain.Aggregates.Contract.DomainEvents uses a module listed above it, which is the healthy direction.
19→12 ContractManagement.Domain.Aggregates.Contract.DomainEvents uses ContractManagement.Domain.Aggregates.Contract.Commands✕
- Connections
- 5 pairs of types, where a type in ContractManagement.Domain.Aggregates.Contract.DomainEvents uses a type in ContractManagement.Domain.Aggregates.Contract.Commands.
- The types involved
ContractManagement.Domain.Aggregates.Contract.DomainEvents.ContractAmountChanged→ContractManagement.Domain.Aggregates.Contract.Commands.ChangeContractAmountContractManagement.Domain.Aggregates.Contract.DomainEvents.ContractCancelled→ContractManagement.Domain.Aggregates.Contract.Commands.CancelContractContractManagement.Domain.Aggregates.Contract.DomainEvents.ContractRegisteredV2→ContractManagement.Domain.Aggregates.Contract.Commands.RegisterContractContractManagement.Domain.Aggregates.Contract.DomainEvents.ContractRegisteredV2→ContractManagement.Domain.Aggregates.Contract.Commands.RegisterContractV2ContractManagement.Domain.Aggregates.Contract.DomainEvents.ContractTermChanged→ContractManagement.Domain.Aggregates.Contract.Commands.ChangeContractTerm
- Direction
- ContractManagement.Domain.Aggregates.Contract.DomainEvents uses ContractManagement.Domain.Aggregates.Contract.Commands, so a change to ContractManagement.Domain.Aggregates.Contract.Commands can break ContractManagement.Domain.Aggregates.Contract.DomainEvents, while a change to ContractManagement.Domain.Aggregates.Contract.DomainEvents can't break ContractManagement.Domain.Aggregates.Contract.Commands.
- Position
- Below the diagonal: ContractManagement.Domain.Aggregates.Contract.DomainEvents uses a module listed above it, which is the healthy direction.
20→4 ContractManagement.Domain.Aggregates.Portfolio uses ContractManagement.Domain.Aggregates.Portfolio.Enums✕
- Connections
- 1 pair of types, where a type in ContractManagement.Domain.Aggregates.Portfolio uses a type in ContractManagement.Domain.Aggregates.Portfolio.Enums.
- The types involved
ContractManagement.Domain.Aggregates.Portfolio.Document→ContractManagement.Domain.Aggregates.Portfolio.Enums.DocumentType
- Direction
- ContractManagement.Domain.Aggregates.Portfolio uses ContractManagement.Domain.Aggregates.Portfolio.Enums, so a change to ContractManagement.Domain.Aggregates.Portfolio.Enums can break ContractManagement.Domain.Aggregates.Portfolio, while a change to ContractManagement.Domain.Aggregates.Portfolio can't break ContractManagement.Domain.Aggregates.Portfolio.Enums.
- Position
- Below the diagonal: ContractManagement.Domain.Aggregates.Portfolio uses a module listed above it, which is the healthy direction.
20→7 ContractManagement.Domain.Aggregates.Portfolio uses Domain.Common✕
- Connections
- 2 pairs of types, where a type in ContractManagement.Domain.Aggregates.Portfolio uses a type in Domain.Common.
- The types involved
ContractManagement.Domain.Aggregates.Portfolio.Document→Domain.Common.EntityContractManagement.Domain.Aggregates.Portfolio.Portfolio→Domain.Common.AggregateRoot
- Direction
- ContractManagement.Domain.Aggregates.Portfolio uses Domain.Common, so a change to Domain.Common can break ContractManagement.Domain.Aggregates.Portfolio, while a change to ContractManagement.Domain.Aggregates.Portfolio can't break Domain.Common.
- Position
- Below the diagonal: ContractManagement.Domain.Aggregates.Portfolio uses a module listed above it, which is the healthy direction.
20→13 ContractManagement.Domain.Aggregates.Portfolio uses ContractManagement.Domain.Aggregates.Portfolio.Commands✕
- Connections
- 2 pairs of types, where a type in ContractManagement.Domain.Aggregates.Portfolio uses a type in ContractManagement.Domain.Aggregates.Portfolio.Commands.
- The types involved
ContractManagement.Domain.Aggregates.Portfolio.Portfolio→ContractManagement.Domain.Aggregates.Portfolio.Commands.AddDocumentContractManagement.Domain.Aggregates.Portfolio.Portfolio→ContractManagement.Domain.Aggregates.Portfolio.Commands.CreatePortfolio
- Direction
- ContractManagement.Domain.Aggregates.Portfolio uses ContractManagement.Domain.Aggregates.Portfolio.Commands, so a change to ContractManagement.Domain.Aggregates.Portfolio.Commands can break ContractManagement.Domain.Aggregates.Portfolio, while a change to ContractManagement.Domain.Aggregates.Portfolio can't break ContractManagement.Domain.Aggregates.Portfolio.Commands.
- Position
- Below the diagonal: ContractManagement.Domain.Aggregates.Portfolio uses a module listed above it, which is the healthy direction.
21→7 ContractManagement.Domain.Aggregates.Portfolio.DomainEvents uses Domain.Common✕
- Connections
- 2 pairs of types, where a type in ContractManagement.Domain.Aggregates.Portfolio.DomainEvents uses a type in Domain.Common.
- The types involved
ContractManagement.Domain.Aggregates.Portfolio.DomainEvents.DocumentAdded→Domain.Common.EventContractManagement.Domain.Aggregates.Portfolio.DomainEvents.PortfolioCreated→Domain.Common.Event
- Direction
- ContractManagement.Domain.Aggregates.Portfolio.DomainEvents uses Domain.Common, so a change to Domain.Common can break ContractManagement.Domain.Aggregates.Portfolio.DomainEvents, while a change to ContractManagement.Domain.Aggregates.Portfolio.DomainEvents can't break Domain.Common.
- Position
- Below the diagonal: ContractManagement.Domain.Aggregates.Portfolio.DomainEvents uses a module listed above it, which is the healthy direction.
21→13 ContractManagement.Domain.Aggregates.Portfolio.DomainEvents uses ContractManagement.Domain.Aggregates.Portfolio.Commands✕
- Connections
- 2 pairs of types, where a type in ContractManagement.Domain.Aggregates.Portfolio.DomainEvents uses a type in ContractManagement.Domain.Aggregates.Portfolio.Commands.
- The types involved
ContractManagement.Domain.Aggregates.Portfolio.DomainEvents.DocumentAdded→ContractManagement.Domain.Aggregates.Portfolio.Commands.AddDocumentContractManagement.Domain.Aggregates.Portfolio.DomainEvents.PortfolioCreated→ContractManagement.Domain.Aggregates.Portfolio.Commands.CreatePortfolio
- Direction
- ContractManagement.Domain.Aggregates.Portfolio.DomainEvents uses ContractManagement.Domain.Aggregates.Portfolio.Commands, so a change to ContractManagement.Domain.Aggregates.Portfolio.Commands can break ContractManagement.Domain.Aggregates.Portfolio.DomainEvents, while a change to ContractManagement.Domain.Aggregates.Portfolio.DomainEvents can't break ContractManagement.Domain.Aggregates.Portfolio.Commands.
- Position
- Below the diagonal: ContractManagement.Domain.Aggregates.Portfolio.DomainEvents uses a module listed above it, which is the healthy direction.
22→11 ContractManagement.Infrastructure.Persistence.EFCore.ReadModel.Configurations uses ContractManagement.Application.ReadModels✕
- Connections
- 2 pairs of types, where a type in ContractManagement.Infrastructure.Persistence.EFCore.ReadModel.Configurations uses a type in ContractManagement.Application.ReadModels.
- The types involved
ContractManagement.Infrastructure.Persistence.EFCore.ReadModel.Configurations.ContractConfiguration→ContractManagement.Application.ReadModels.ContractContractManagement.Infrastructure.Persistence.EFCore.ReadModel.Configurations.ProductConfiguration→ContractManagement.Application.ReadModels.Product
- Direction
- ContractManagement.Infrastructure.Persistence.EFCore.ReadModel.Configurations uses ContractManagement.Application.ReadModels, so a change to ContractManagement.Application.ReadModels can break ContractManagement.Infrastructure.Persistence.EFCore.ReadModel.Configurations, while a change to ContractManagement.Infrastructure.Persistence.EFCore.ReadModel.Configurations can't break ContractManagement.Application.ReadModels.
- Position
- Below the diagonal: ContractManagement.Infrastructure.Persistence.EFCore.ReadModel.Configurations uses a module listed above it, which is the healthy direction.
23→7 Infrastructure.Common.Messaging.MassTransit uses Domain.Common✕
- Connections
- 1 pair of types, where a type in Infrastructure.Common.Messaging.MassTransit uses a type in Domain.Common.
- The types involved
Infrastructure.Common.Messaging.MassTransit.MassTransitEventPublisher→Domain.Common.Event
- Direction
- Infrastructure.Common.Messaging.MassTransit uses Domain.Common, so a change to Domain.Common can break Infrastructure.Common.Messaging.MassTransit, while a change to Infrastructure.Common.Messaging.MassTransit can't break Domain.Common.
- Position
- Below the diagonal: Infrastructure.Common.Messaging.MassTransit uses a module listed above it, which is the healthy direction.
23→10 Infrastructure.Common.Messaging.MassTransit uses Application.Common.Interfaces✕
- Connections
- 3 pairs of types, where a type in Infrastructure.Common.Messaging.MassTransit uses a type in Application.Common.Interfaces.
- The types involved
Infrastructure.Common.Messaging.MassTransit.EventConsumer→Application.Common.Interfaces.IEventHandlerInfrastructure.Common.Messaging.MassTransit.EventConsumer→Application.Common.Interfaces.IUnitOfWorkInfrastructure.Common.Messaging.MassTransit.MassTransitEventPublisher→Application.Common.Interfaces.IEventPublisher
- Direction
- Infrastructure.Common.Messaging.MassTransit uses Application.Common.Interfaces, so a change to Application.Common.Interfaces can break Infrastructure.Common.Messaging.MassTransit, while a change to Infrastructure.Common.Messaging.MassTransit can't break Application.Common.Interfaces.
- Position
- Below the diagonal: Infrastructure.Common.Messaging.MassTransit uses a module listed above it, which is the healthy direction.
24→7 Infrastructure.Common.Persistence.EFCore.Repositories.Aggregate uses Domain.Common✕
- Connections
- 1 pair of types, where a type in Infrastructure.Common.Persistence.EFCore.Repositories.Aggregate uses a type in Domain.Common.
- The types involved
Infrastructure.Common.Persistence.EFCore.Repositories.Aggregate.EFEventSourcedAggregateRepository→Domain.Common.Event
- Direction
- Infrastructure.Common.Persistence.EFCore.Repositories.Aggregate uses Domain.Common, so a change to Domain.Common can break Infrastructure.Common.Persistence.EFCore.Repositories.Aggregate, while a change to Infrastructure.Common.Persistence.EFCore.Repositories.Aggregate can't break Domain.Common.
- Position
- Below the diagonal: Infrastructure.Common.Persistence.EFCore.Repositories.Aggregate uses a module listed above it, which is the healthy direction.
24→10 Infrastructure.Common.Persistence.EFCore.Repositories.Aggregate uses Application.Common.Interfaces✕
- Connections
- 2 pairs of types, where a type in Infrastructure.Common.Persistence.EFCore.Repositories.Aggregate uses a type in Application.Common.Interfaces.
- The types involved
Infrastructure.Common.Persistence.EFCore.Repositories.Aggregate.EFAggregateRepository→Application.Common.Interfaces.IAggregateRepositoryInfrastructure.Common.Persistence.EFCore.Repositories.Aggregate.EFEventSourcedAggregateRepository→Application.Common.Interfaces.IAggregateRepository
- Direction
- Infrastructure.Common.Persistence.EFCore.Repositories.Aggregate uses Application.Common.Interfaces, so a change to Application.Common.Interfaces can break Infrastructure.Common.Persistence.EFCore.Repositories.Aggregate, while a change to Infrastructure.Common.Persistence.EFCore.Repositories.Aggregate can't break Application.Common.Interfaces.
- Position
- Below the diagonal: Infrastructure.Common.Persistence.EFCore.Repositories.Aggregate uses a module listed above it, which is the healthy direction.
25→7 Infrastructure.Common.UnitOfWork uses Domain.Common✕
- Connections
- 1 pair of types, where a type in Infrastructure.Common.UnitOfWork uses a type in Domain.Common.
- The types involved
Infrastructure.Common.UnitOfWork.PersistenceAndMessagingUnitOfWork→Domain.Common.Event
- Direction
- Infrastructure.Common.UnitOfWork uses Domain.Common, so a change to Domain.Common can break Infrastructure.Common.UnitOfWork, while a change to Infrastructure.Common.UnitOfWork can't break Domain.Common.
- Position
- Below the diagonal: Infrastructure.Common.UnitOfWork uses a module listed above it, which is the healthy direction.
25→10 Infrastructure.Common.UnitOfWork uses Application.Common.Interfaces✕
- Connections
- 2 pairs of types, where a type in Infrastructure.Common.UnitOfWork uses a type in Application.Common.Interfaces.
- The types involved
Infrastructure.Common.UnitOfWork.PersistenceAndMessagingUnitOfWork→Application.Common.Interfaces.IEventPublisherInfrastructure.Common.UnitOfWork.PersistenceAndMessagingUnitOfWork→Application.Common.Interfaces.IUnitOfWork
- Direction
- Infrastructure.Common.UnitOfWork uses Application.Common.Interfaces, so a change to Application.Common.Interfaces can break Infrastructure.Common.UnitOfWork, while a change to Infrastructure.Common.UnitOfWork can't break Application.Common.Interfaces.
- Position
- Below the diagonal: Infrastructure.Common.UnitOfWork uses a module listed above it, which is the healthy direction.
26→15 OutputManagementService.Repositories uses OutputManagementService.ReadModels✕
- Connections
- 6 pairs of types, where a type in OutputManagementService.Repositories uses a type in OutputManagementService.ReadModels.
- The types involved
OutputManagementService.Repositories.IContractRepository→OutputManagementService.ReadModels.ContractOutputManagementService.Repositories.ICustomerRepository→OutputManagementService.ReadModels.CustomerOutputManagementService.Repositories.IProductRepository→OutputManagementService.ReadModels.ProductOutputManagementService.Repositories.InMemoryContractRepository→OutputManagementService.ReadModels.ContractOutputManagementService.Repositories.InMemoryCustomerRepository→OutputManagementService.ReadModels.CustomerOutputManagementService.Repositories.InMemoryProductRepository→OutputManagementService.ReadModels.Product
- Direction
- OutputManagementService.Repositories uses OutputManagementService.ReadModels, so a change to OutputManagementService.ReadModels can break OutputManagementService.Repositories, while a change to OutputManagementService.Repositories can't break OutputManagementService.ReadModels.
- Position
- Below the diagonal: OutputManagementService.Repositories uses a module listed above it, which is the healthy direction.
27→10 ContractManagement.Application.EventHandlers.IntegrationEvents uses Application.Common.Interfaces✕
- Connections
- 2 pairs of types, where a type in ContractManagement.Application.EventHandlers.IntegrationEvents uses a type in Application.Common.Interfaces.
- The types involved
ContractManagement.Application.EventHandlers.IntegrationEvents.CustomerRegisteredHandler→Application.Common.Interfaces.IEventHandlerContractManagement.Application.EventHandlers.IntegrationEvents.ProductRegisteredHandler→Application.Common.Interfaces.IEventHandler
- Direction
- ContractManagement.Application.EventHandlers.IntegrationEvents uses Application.Common.Interfaces, so a change to Application.Common.Interfaces can break ContractManagement.Application.EventHandlers.IntegrationEvents, while a change to ContractManagement.Application.EventHandlers.IntegrationEvents can't break Application.Common.Interfaces.
- Position
- Below the diagonal: ContractManagement.Application.EventHandlers.IntegrationEvents uses a module listed above it, which is the healthy direction.
27→14 ContractManagement.Application.EventHandlers.IntegrationEvents uses CustomerManagement.Application.IntegrationEvents✕
- Connections
- 1 pair of types, where a type in ContractManagement.Application.EventHandlers.IntegrationEvents uses a type in CustomerManagement.Application.IntegrationEvents.
- The types involved
ContractManagement.Application.EventHandlers.IntegrationEvents.CustomerRegisteredHandler→CustomerManagement.Application.IntegrationEvents.CustomerRegistered
- Direction
- ContractManagement.Application.EventHandlers.IntegrationEvents uses CustomerManagement.Application.IntegrationEvents, so a change to CustomerManagement.Application.IntegrationEvents can break ContractManagement.Application.EventHandlers.IntegrationEvents, while a change to ContractManagement.Application.EventHandlers.IntegrationEvents can't break CustomerManagement.Application.IntegrationEvents.
- Position
- Below the diagonal: ContractManagement.Application.EventHandlers.IntegrationEvents uses a module listed above it, which is the healthy direction.
27→16 ContractManagement.Application.EventHandlers.IntegrationEvents uses ProductManagement.Application.IntegrationEvents✕
- Connections
- 1 pair of types, where a type in ContractManagement.Application.EventHandlers.IntegrationEvents uses a type in ProductManagement.Application.IntegrationEvents.
- The types involved
ContractManagement.Application.EventHandlers.IntegrationEvents.ProductRegisteredHandler→ProductManagement.Application.IntegrationEvents.ProductRegistered
- Direction
- ContractManagement.Application.EventHandlers.IntegrationEvents uses ProductManagement.Application.IntegrationEvents, so a change to ProductManagement.Application.IntegrationEvents can break ContractManagement.Application.EventHandlers.IntegrationEvents, while a change to ContractManagement.Application.EventHandlers.IntegrationEvents can't break ProductManagement.Application.IntegrationEvents.
- Position
- Below the diagonal: ContractManagement.Application.EventHandlers.IntegrationEvents uses a module listed above it, which is the healthy direction.
27→18 ContractManagement.Application.EventHandlers.IntegrationEvents uses ContractManagement.Application.Interfaces✕
- Connections
- 2 pairs of types, where a type in ContractManagement.Application.EventHandlers.IntegrationEvents uses a type in ContractManagement.Application.Interfaces.
- The types involved
ContractManagement.Application.EventHandlers.IntegrationEvents.CustomerRegisteredHandler→ContractManagement.Application.Interfaces.ICustomerReadModelRepositoryContractManagement.Application.EventHandlers.IntegrationEvents.ProductRegisteredHandler→ContractManagement.Application.Interfaces.IProductReadModelRepository
- Direction
- ContractManagement.Application.EventHandlers.IntegrationEvents uses ContractManagement.Application.Interfaces, so a change to ContractManagement.Application.Interfaces can break ContractManagement.Application.EventHandlers.IntegrationEvents, while a change to ContractManagement.Application.EventHandlers.IntegrationEvents can't break ContractManagement.Application.Interfaces.
- Position
- Below the diagonal: ContractManagement.Application.EventHandlers.IntegrationEvents uses a module listed above it, which is the healthy direction.
28→3 ContractManagement.Application.IntegrationEvents uses ContractManagement.Domain.Aggregates.Contract.Enums✕
- Connections
- 1 pair of types, where a type in ContractManagement.Application.IntegrationEvents uses a type in ContractManagement.Domain.Aggregates.Contract.Enums.
- The types involved
ContractManagement.Application.IntegrationEvents.ContractRegistered→ContractManagement.Domain.Aggregates.Contract.Enums.PaymentPeriod
- Direction
- ContractManagement.Application.IntegrationEvents uses ContractManagement.Domain.Aggregates.Contract.Enums, so a change to ContractManagement.Domain.Aggregates.Contract.Enums can break ContractManagement.Application.IntegrationEvents, while a change to ContractManagement.Application.IntegrationEvents can't break ContractManagement.Domain.Aggregates.Contract.Enums.
- Position
- Below the diagonal: ContractManagement.Application.IntegrationEvents uses a module listed above it, which is the healthy direction.
28→7 ContractManagement.Application.IntegrationEvents uses Domain.Common✕
- Connections
- 4 pairs of types, where a type in ContractManagement.Application.IntegrationEvents uses a type in Domain.Common.
- The types involved
ContractManagement.Application.IntegrationEvents.ContractAmountChanged→Domain.Common.EventContractManagement.Application.IntegrationEvents.ContractCancelled→Domain.Common.EventContractManagement.Application.IntegrationEvents.ContractRegistered→Domain.Common.EventContractManagement.Application.IntegrationEvents.ContractTermChanged→Domain.Common.Event
- Direction
- ContractManagement.Application.IntegrationEvents uses Domain.Common, so a change to Domain.Common can break ContractManagement.Application.IntegrationEvents, while a change to ContractManagement.Application.IntegrationEvents can't break Domain.Common.
- Position
- Below the diagonal: ContractManagement.Application.IntegrationEvents uses a module listed above it, which is the healthy direction.
28→19 ContractManagement.Application.IntegrationEvents uses ContractManagement.Domain.Aggregates.Contract.DomainEvents✕
- Connections
- 4 pairs of types, where a type in ContractManagement.Application.IntegrationEvents uses a type in ContractManagement.Domain.Aggregates.Contract.DomainEvents.
- The types involved
ContractManagement.Application.IntegrationEvents.ContractAmountChanged→ContractManagement.Domain.Aggregates.Contract.DomainEvents.ContractAmountChangedContractManagement.Application.IntegrationEvents.ContractCancelled→ContractManagement.Domain.Aggregates.Contract.DomainEvents.ContractCancelledContractManagement.Application.IntegrationEvents.ContractRegistered→ContractManagement.Domain.Aggregates.Contract.DomainEvents.ContractRegisteredV2ContractManagement.Application.IntegrationEvents.ContractTermChanged→ContractManagement.Domain.Aggregates.Contract.DomainEvents.ContractTermChanged
- Direction
- ContractManagement.Application.IntegrationEvents uses ContractManagement.Domain.Aggregates.Contract.DomainEvents, so a change to ContractManagement.Domain.Aggregates.Contract.DomainEvents can break ContractManagement.Application.IntegrationEvents, while a change to ContractManagement.Application.IntegrationEvents can't break ContractManagement.Domain.Aggregates.Contract.DomainEvents.
- Position
- Below the diagonal: ContractManagement.Application.IntegrationEvents uses a module listed above it, which is the healthy direction.
29→5 ContractManagement.Application.Services uses ContractManagement.Domain.Services✕
- Connections
- 2 pairs of types, where a type in ContractManagement.Application.Services uses a type in ContractManagement.Domain.Services.
- The types involved
ContractManagement.Application.Services.CustomerService→ContractManagement.Domain.Services.ICustomerServiceContractManagement.Application.Services.ProductService→ContractManagement.Domain.Services.IProductService
- Direction
- ContractManagement.Application.Services uses ContractManagement.Domain.Services, so a change to ContractManagement.Domain.Services can break ContractManagement.Application.Services, while a change to ContractManagement.Application.Services can't break ContractManagement.Domain.Services.
- Position
- Below the diagonal: ContractManagement.Application.Services uses a module listed above it, which is the healthy direction.
29→10 ContractManagement.Application.Services uses Application.Common.Interfaces✕
- Connections
- 2 pairs of types, where a type in ContractManagement.Application.Services uses a type in Application.Common.Interfaces.
- The types involved
ContractManagement.Application.Services.CustomerService→Application.Common.Interfaces.IDomainServiceContractManagement.Application.Services.ProductService→Application.Common.Interfaces.IDomainService
- Direction
- ContractManagement.Application.Services uses Application.Common.Interfaces, so a change to Application.Common.Interfaces can break ContractManagement.Application.Services, while a change to ContractManagement.Application.Services can't break Application.Common.Interfaces.
- Position
- Below the diagonal: ContractManagement.Application.Services uses a module listed above it, which is the healthy direction.
29→18 ContractManagement.Application.Services uses ContractManagement.Application.Interfaces✕
- Connections
- 2 pairs of types, where a type in ContractManagement.Application.Services uses a type in ContractManagement.Application.Interfaces.
- The types involved
ContractManagement.Application.Services.CustomerService→ContractManagement.Application.Interfaces.ICustomerReadModelRepositoryContractManagement.Application.Services.ProductService→ContractManagement.Application.Interfaces.IProductReadModelRepository
- Direction
- ContractManagement.Application.Services uses ContractManagement.Application.Interfaces, so a change to ContractManagement.Application.Interfaces can break ContractManagement.Application.Services, while a change to ContractManagement.Application.Services can't break ContractManagement.Application.Interfaces.
- Position
- Below the diagonal: ContractManagement.Application.Services uses a module listed above it, which is the healthy direction.
30→3 ContractManagement.Domain.Aggregates.Contract uses ContractManagement.Domain.Aggregates.Contract.Enums✕
- Connections
- 1 pair of types, where a type in ContractManagement.Domain.Aggregates.Contract uses a type in ContractManagement.Domain.Aggregates.Contract.Enums.
- The types involved
ContractManagement.Domain.Aggregates.Contract.Contract→ContractManagement.Domain.Aggregates.Contract.Enums.PaymentPeriod
- Direction
- ContractManagement.Domain.Aggregates.Contract uses ContractManagement.Domain.Aggregates.Contract.Enums, so a change to ContractManagement.Domain.Aggregates.Contract.Enums can break ContractManagement.Domain.Aggregates.Contract, while a change to ContractManagement.Domain.Aggregates.Contract can't break ContractManagement.Domain.Aggregates.Contract.Enums.
- Position
- Below the diagonal: ContractManagement.Domain.Aggregates.Contract uses a module listed above it, which is the healthy direction.
30→5 ContractManagement.Domain.Aggregates.Contract uses ContractManagement.Domain.Services✕
- Connections
- 2 pairs of types, where a type in ContractManagement.Domain.Aggregates.Contract uses a type in ContractManagement.Domain.Services.
- The types involved
ContractManagement.Domain.Aggregates.Contract.Contract→ContractManagement.Domain.Services.ICustomerServiceContractManagement.Domain.Aggregates.Contract.Contract→ContractManagement.Domain.Services.IProductService
- Direction
- ContractManagement.Domain.Aggregates.Contract uses ContractManagement.Domain.Services, so a change to ContractManagement.Domain.Services can break ContractManagement.Domain.Aggregates.Contract, while a change to ContractManagement.Domain.Aggregates.Contract can't break ContractManagement.Domain.Services.
- Position
- Below the diagonal: ContractManagement.Domain.Aggregates.Contract uses a module listed above it, which is the healthy direction.
30→6 ContractManagement.Domain.Aggregates.Contract uses ContractManagement.Domain.ValueObjects✕
- Connections
- 5 pairs of types, where a type in ContractManagement.Domain.Aggregates.Contract uses a type in ContractManagement.Domain.ValueObjects.
- The types involved
ContractManagement.Domain.Aggregates.Contract.Contract→ContractManagement.Domain.ValueObjects.ContractNumberContractManagement.Domain.Aggregates.Contract.Contract→ContractManagement.Domain.ValueObjects.CustomerNumberContractManagement.Domain.Aggregates.Contract.Contract→ContractManagement.Domain.ValueObjects.DurationContractManagement.Domain.Aggregates.Contract.Contract→ContractManagement.Domain.ValueObjects.MoneyAmountContractManagement.Domain.Aggregates.Contract.Contract→ContractManagement.Domain.ValueObjects.ProductNumber
- Direction
- ContractManagement.Domain.Aggregates.Contract uses ContractManagement.Domain.ValueObjects, so a change to ContractManagement.Domain.ValueObjects can break ContractManagement.Domain.Aggregates.Contract, while a change to ContractManagement.Domain.Aggregates.Contract can't break ContractManagement.Domain.ValueObjects.
- Position
- Below the diagonal: ContractManagement.Domain.Aggregates.Contract uses a module listed above it, which is the healthy direction.
30→7 ContractManagement.Domain.Aggregates.Contract uses Domain.Common✕
- Connections
- 2 pairs of types, where a type in ContractManagement.Domain.Aggregates.Contract uses a type in Domain.Common.
- The types involved
ContractManagement.Domain.Aggregates.Contract.Contract→Domain.Common.AggregateRootContractManagement.Domain.Aggregates.Contract.Contract→Domain.Common.Event
- Direction
- ContractManagement.Domain.Aggregates.Contract uses Domain.Common, so a change to Domain.Common can break ContractManagement.Domain.Aggregates.Contract, while a change to ContractManagement.Domain.Aggregates.Contract can't break Domain.Common.
- Position
- Below the diagonal: ContractManagement.Domain.Aggregates.Contract uses a module listed above it, which is the healthy direction.
30→12 ContractManagement.Domain.Aggregates.Contract uses ContractManagement.Domain.Aggregates.Contract.Commands✕
- Connections
- 4 pairs of types, where a type in ContractManagement.Domain.Aggregates.Contract uses a type in ContractManagement.Domain.Aggregates.Contract.Commands.
- The types involved
ContractManagement.Domain.Aggregates.Contract.Contract→ContractManagement.Domain.Aggregates.Contract.Commands.CancelContractContractManagement.Domain.Aggregates.Contract.Contract→ContractManagement.Domain.Aggregates.Contract.Commands.ChangeContractAmountContractManagement.Domain.Aggregates.Contract.Contract→ContractManagement.Domain.Aggregates.Contract.Commands.ChangeContractTermContractManagement.Domain.Aggregates.Contract.Contract→ContractManagement.Domain.Aggregates.Contract.Commands.RegisterContractV2
- Direction
- ContractManagement.Domain.Aggregates.Contract uses ContractManagement.Domain.Aggregates.Contract.Commands, so a change to ContractManagement.Domain.Aggregates.Contract.Commands can break ContractManagement.Domain.Aggregates.Contract, while a change to ContractManagement.Domain.Aggregates.Contract can't break ContractManagement.Domain.Aggregates.Contract.Commands.
- Position
- Below the diagonal: ContractManagement.Domain.Aggregates.Contract uses a module listed above it, which is the healthy direction.
30→19 ContractManagement.Domain.Aggregates.Contract uses ContractManagement.Domain.Aggregates.Contract.DomainEvents✕
- Connections
- 4 pairs of types, where a type in ContractManagement.Domain.Aggregates.Contract uses a type in ContractManagement.Domain.Aggregates.Contract.DomainEvents.
- The types involved
ContractManagement.Domain.Aggregates.Contract.Contract→ContractManagement.Domain.Aggregates.Contract.DomainEvents.ContractAmountChangedContractManagement.Domain.Aggregates.Contract.Contract→ContractManagement.Domain.Aggregates.Contract.DomainEvents.ContractCancelledContractManagement.Domain.Aggregates.Contract.Contract→ContractManagement.Domain.Aggregates.Contract.DomainEvents.ContractRegisteredV2ContractManagement.Domain.Aggregates.Contract.Contract→ContractManagement.Domain.Aggregates.Contract.DomainEvents.ContractTermChanged
- Direction
- ContractManagement.Domain.Aggregates.Contract uses ContractManagement.Domain.Aggregates.Contract.DomainEvents, so a change to ContractManagement.Domain.Aggregates.Contract.DomainEvents can break ContractManagement.Domain.Aggregates.Contract, while a change to ContractManagement.Domain.Aggregates.Contract can't break ContractManagement.Domain.Aggregates.Contract.DomainEvents.
- Position
- Below the diagonal: ContractManagement.Domain.Aggregates.Contract uses a module listed above it, which is the healthy direction.
31→11 ContractManagement.Infrastructure.Persistence.EFCore uses ContractManagement.Application.ReadModels✕
- Connections
- 3 pairs of types, where a type in ContractManagement.Infrastructure.Persistence.EFCore uses a type in ContractManagement.Application.ReadModels.
- The types involved
ContractManagement.Infrastructure.Persistence.EFCore.ServiceDbContext→ContractManagement.Application.ReadModels.ContractContractManagement.Infrastructure.Persistence.EFCore.ServiceDbContext→ContractManagement.Application.ReadModels.CustomerContractManagement.Infrastructure.Persistence.EFCore.ServiceDbContext→ContractManagement.Application.ReadModels.Product
- Direction
- ContractManagement.Infrastructure.Persistence.EFCore uses ContractManagement.Application.ReadModels, so a change to ContractManagement.Application.ReadModels can break ContractManagement.Infrastructure.Persistence.EFCore, while a change to ContractManagement.Infrastructure.Persistence.EFCore can't break ContractManagement.Application.ReadModels.
- Position
- Below the diagonal: ContractManagement.Infrastructure.Persistence.EFCore uses a module listed above it, which is the healthy direction.
31→20 ContractManagement.Infrastructure.Persistence.EFCore uses ContractManagement.Domain.Aggregates.Portfolio✕
- Connections
- 2 pairs of types, where a type in ContractManagement.Infrastructure.Persistence.EFCore uses a type in ContractManagement.Domain.Aggregates.Portfolio.
- The types involved
ContractManagement.Infrastructure.Persistence.EFCore.ServiceDbContext→ContractManagement.Domain.Aggregates.Portfolio.DocumentContractManagement.Infrastructure.Persistence.EFCore.ServiceDbContext→ContractManagement.Domain.Aggregates.Portfolio.Portfolio
- Direction
- ContractManagement.Infrastructure.Persistence.EFCore uses ContractManagement.Domain.Aggregates.Portfolio, so a change to ContractManagement.Domain.Aggregates.Portfolio can break ContractManagement.Infrastructure.Persistence.EFCore, while a change to ContractManagement.Infrastructure.Persistence.EFCore can't break ContractManagement.Domain.Aggregates.Portfolio.
- Position
- Below the diagonal: ContractManagement.Infrastructure.Persistence.EFCore uses a module listed above it, which is the healthy direction.
32→11 ContractManagement.Infrastructure.Persistence.EFCore.Configurations uses ContractManagement.Application.ReadModels✕
- Connections
- 1 pair of types, where a type in ContractManagement.Infrastructure.Persistence.EFCore.Configurations uses a type in ContractManagement.Application.ReadModels.
- The types involved
ContractManagement.Infrastructure.Persistence.EFCore.Configurations.CustomerConfiguration→ContractManagement.Application.ReadModels.Customer
- Direction
- ContractManagement.Infrastructure.Persistence.EFCore.Configurations uses ContractManagement.Application.ReadModels, so a change to ContractManagement.Application.ReadModels can break ContractManagement.Infrastructure.Persistence.EFCore.Configurations, while a change to ContractManagement.Infrastructure.Persistence.EFCore.Configurations can't break ContractManagement.Application.ReadModels.
- Position
- Below the diagonal: ContractManagement.Infrastructure.Persistence.EFCore.Configurations uses a module listed above it, which is the healthy direction.
32→20 ContractManagement.Infrastructure.Persistence.EFCore.Configurations uses ContractManagement.Domain.Aggregates.Portfolio✕
- Connections
- 2 pairs of types, where a type in ContractManagement.Infrastructure.Persistence.EFCore.Configurations uses a type in ContractManagement.Domain.Aggregates.Portfolio.
- The types involved
ContractManagement.Infrastructure.Persistence.EFCore.Configurations.DocumentConfiguration→ContractManagement.Domain.Aggregates.Portfolio.DocumentContractManagement.Infrastructure.Persistence.EFCore.Configurations.PortfolioConfiguration→ContractManagement.Domain.Aggregates.Portfolio.Portfolio
- Direction
- ContractManagement.Infrastructure.Persistence.EFCore.Configurations uses ContractManagement.Domain.Aggregates.Portfolio, so a change to ContractManagement.Domain.Aggregates.Portfolio can break ContractManagement.Infrastructure.Persistence.EFCore.Configurations, while a change to ContractManagement.Infrastructure.Persistence.EFCore.Configurations can't break ContractManagement.Domain.Aggregates.Portfolio.
- Position
- Below the diagonal: ContractManagement.Infrastructure.Persistence.EFCore.Configurations uses a module listed above it, which is the healthy direction.
33→10 Contractmanagement.Features.Documents uses Application.Common.Interfaces✕
- Connections
- 4 pairs of types, where a type in Contractmanagement.Features.Documents uses a type in Application.Common.Interfaces.
- The types involved
Contractmanagement.Features.Documents.AddDocumentHandler→Application.Common.Interfaces.IAggregateServiceContractmanagement.Features.Documents.AddDocumentHandler→Application.Common.Interfaces.ICommandHandlerContractmanagement.Features.Documents.CreatePortfolioHandler→Application.Common.Interfaces.IAggregateServiceContractmanagement.Features.Documents.CreatePortfolioHandler→Application.Common.Interfaces.ICommandHandler
- Direction
- Contractmanagement.Features.Documents uses Application.Common.Interfaces, so a change to Application.Common.Interfaces can break Contractmanagement.Features.Documents, while a change to Contractmanagement.Features.Documents can't break Application.Common.Interfaces.
- Position
- Below the diagonal: Contractmanagement.Features.Documents uses a module listed above it, which is the healthy direction.
33→13 Contractmanagement.Features.Documents uses ContractManagement.Domain.Aggregates.Portfolio.Commands✕
- Connections
- 2 pairs of types, where a type in Contractmanagement.Features.Documents uses a type in ContractManagement.Domain.Aggregates.Portfolio.Commands.
- The types involved
Contractmanagement.Features.Documents.AddDocumentHandler→ContractManagement.Domain.Aggregates.Portfolio.Commands.AddDocumentContractmanagement.Features.Documents.CreatePortfolioHandler→ContractManagement.Domain.Aggregates.Portfolio.Commands.CreatePortfolio
- Direction
- Contractmanagement.Features.Documents uses ContractManagement.Domain.Aggregates.Portfolio.Commands, so a change to ContractManagement.Domain.Aggregates.Portfolio.Commands can break Contractmanagement.Features.Documents, while a change to Contractmanagement.Features.Documents can't break ContractManagement.Domain.Aggregates.Portfolio.Commands.
- Position
- Below the diagonal: Contractmanagement.Features.Documents uses a module listed above it, which is the healthy direction.
33→20 Contractmanagement.Features.Documents uses ContractManagement.Domain.Aggregates.Portfolio✕
- Connections
- 2 pairs of types, where a type in Contractmanagement.Features.Documents uses a type in ContractManagement.Domain.Aggregates.Portfolio.
- The types involved
Contractmanagement.Features.Documents.AddDocumentHandler→ContractManagement.Domain.Aggregates.Portfolio.PortfolioContractmanagement.Features.Documents.CreatePortfolioHandler→ContractManagement.Domain.Aggregates.Portfolio.Portfolio
- Direction
- Contractmanagement.Features.Documents uses ContractManagement.Domain.Aggregates.Portfolio, so a change to ContractManagement.Domain.Aggregates.Portfolio can break Contractmanagement.Features.Documents, while a change to Contractmanagement.Features.Documents can't break ContractManagement.Domain.Aggregates.Portfolio.
- Position
- Below the diagonal: Contractmanagement.Features.Documents uses a module listed above it, which is the healthy direction.
34→24 Infrastructure.Common.Persistence.EFCore.Configurations uses Infrastructure.Common.Persistence.EFCore.Repositories.Aggregate✕
- Connections
- 2 pairs of types, where a type in Infrastructure.Common.Persistence.EFCore.Configurations uses a type in Infrastructure.Common.Persistence.EFCore.Repositories.Aggregate.
- The types involved
Infrastructure.Common.Persistence.EFCore.Configurations.EventSourcedAggregateConfiguration→Infrastructure.Common.Persistence.EFCore.Repositories.Aggregate.AggregateEntityInfrastructure.Common.Persistence.EFCore.Configurations.EventSourcedAggregateConfiguration→Infrastructure.Common.Persistence.EFCore.Repositories.Aggregate.EventEntity
- Direction
- Infrastructure.Common.Persistence.EFCore.Configurations uses Infrastructure.Common.Persistence.EFCore.Repositories.Aggregate, so a change to Infrastructure.Common.Persistence.EFCore.Repositories.Aggregate can break Infrastructure.Common.Persistence.EFCore.Configurations, while a change to Infrastructure.Common.Persistence.EFCore.Configurations can't break Infrastructure.Common.Persistence.EFCore.Repositories.Aggregate.
- Position
- Below the diagonal: Infrastructure.Common.Persistence.EFCore.Configurations uses a module listed above it, which is the healthy direction.
35→11 ContractManagement.Infrastructure.Persistence.EFCore.Repositories uses ContractManagement.Application.ReadModels✕
- Connections
- 3 pairs of types, where a type in ContractManagement.Infrastructure.Persistence.EFCore.Repositories uses a type in ContractManagement.Application.ReadModels.
- The types involved
ContractManagement.Infrastructure.Persistence.EFCore.Repositories.EFContractReadModelRepository→ContractManagement.Application.ReadModels.ContractContractManagement.Infrastructure.Persistence.EFCore.Repositories.EFCustomerReadModelRepository→ContractManagement.Application.ReadModels.CustomerContractManagement.Infrastructure.Persistence.EFCore.Repositories.EFProductReadModelRepository→ContractManagement.Application.ReadModels.Product
- Direction
- ContractManagement.Infrastructure.Persistence.EFCore.Repositories uses ContractManagement.Application.ReadModels, so a change to ContractManagement.Application.ReadModels can break ContractManagement.Infrastructure.Persistence.EFCore.Repositories, while a change to ContractManagement.Infrastructure.Persistence.EFCore.Repositories can't break ContractManagement.Application.ReadModels.
- Position
- Below the diagonal: ContractManagement.Infrastructure.Persistence.EFCore.Repositories uses a module listed above it, which is the healthy direction.
35→18 ContractManagement.Infrastructure.Persistence.EFCore.Repositories uses ContractManagement.Application.Interfaces✕
- Connections
- 3 pairs of types, where a type in ContractManagement.Infrastructure.Persistence.EFCore.Repositories uses a type in ContractManagement.Application.Interfaces.
- The types involved
ContractManagement.Infrastructure.Persistence.EFCore.Repositories.EFContractReadModelRepository→ContractManagement.Application.Interfaces.IContractReadModelRepositoryContractManagement.Infrastructure.Persistence.EFCore.Repositories.EFCustomerReadModelRepository→ContractManagement.Application.Interfaces.ICustomerReadModelRepositoryContractManagement.Infrastructure.Persistence.EFCore.Repositories.EFProductReadModelRepository→ContractManagement.Application.Interfaces.IProductReadModelRepository
- Direction
- ContractManagement.Infrastructure.Persistence.EFCore.Repositories uses ContractManagement.Application.Interfaces, so a change to ContractManagement.Application.Interfaces can break ContractManagement.Infrastructure.Persistence.EFCore.Repositories, while a change to ContractManagement.Infrastructure.Persistence.EFCore.Repositories can't break ContractManagement.Application.Interfaces.
- Position
- Below the diagonal: ContractManagement.Infrastructure.Persistence.EFCore.Repositories uses a module listed above it, which is the healthy direction.
35→31 ContractManagement.Infrastructure.Persistence.EFCore.Repositories uses ContractManagement.Infrastructure.Persistence.EFCore✕
- Connections
- 3 pairs of types, where a type in ContractManagement.Infrastructure.Persistence.EFCore.Repositories uses a type in ContractManagement.Infrastructure.Persistence.EFCore.
- The types involved
ContractManagement.Infrastructure.Persistence.EFCore.Repositories.EFContractReadModelRepository→ContractManagement.Infrastructure.Persistence.EFCore.ServiceDbContextContractManagement.Infrastructure.Persistence.EFCore.Repositories.EFCustomerReadModelRepository→ContractManagement.Infrastructure.Persistence.EFCore.ServiceDbContextContractManagement.Infrastructure.Persistence.EFCore.Repositories.EFProductReadModelRepository→ContractManagement.Infrastructure.Persistence.EFCore.ServiceDbContext
- Direction
- ContractManagement.Infrastructure.Persistence.EFCore.Repositories uses ContractManagement.Infrastructure.Persistence.EFCore, so a change to ContractManagement.Infrastructure.Persistence.EFCore can break ContractManagement.Infrastructure.Persistence.EFCore.Repositories, while a change to ContractManagement.Infrastructure.Persistence.EFCore.Repositories can't break ContractManagement.Infrastructure.Persistence.EFCore.
- Position
- Below the diagonal: ContractManagement.Infrastructure.Persistence.EFCore.Repositories uses a module listed above it, which is the healthy direction.
36→7 ContractManagement.WebAPI.Controllers uses Domain.Common✕
- Connections
- 1 pair of types, where a type in ContractManagement.WebAPI.Controllers uses a type in Domain.Common.
- The types involved
ContractManagement.WebAPI.Controllers.CommandController→Domain.Common.Command
- Direction
- ContractManagement.WebAPI.Controllers uses Domain.Common, so a change to Domain.Common can break ContractManagement.WebAPI.Controllers, while a change to ContractManagement.WebAPI.Controllers can't break Domain.Common.
- Position
- Below the diagonal: ContractManagement.WebAPI.Controllers uses a module listed above it, which is the healthy direction.
36→10 ContractManagement.WebAPI.Controllers uses Application.Common.Interfaces✕
- Connections
- 2 pairs of types, where a type in ContractManagement.WebAPI.Controllers uses a type in Application.Common.Interfaces.
- The types involved
ContractManagement.WebAPI.Controllers.CommandController→Application.Common.Interfaces.ICommandHandlerContractManagement.WebAPI.Controllers.CommandController→Application.Common.Interfaces.IUnitOfWork
- Direction
- ContractManagement.WebAPI.Controllers uses Application.Common.Interfaces, so a change to Application.Common.Interfaces can break ContractManagement.WebAPI.Controllers, while a change to ContractManagement.WebAPI.Controllers can't break Application.Common.Interfaces.
- Position
- Below the diagonal: ContractManagement.WebAPI.Controllers uses a module listed above it, which is the healthy direction.
36→12 ContractManagement.WebAPI.Controllers uses ContractManagement.Domain.Aggregates.Contract.Commands✕
- Connections
- 5 pairs of types, where a type in ContractManagement.WebAPI.Controllers uses a type in ContractManagement.Domain.Aggregates.Contract.Commands.
- The types involved
ContractManagement.WebAPI.Controllers.CommandController→ContractManagement.Domain.Aggregates.Contract.Commands.CancelContractContractManagement.WebAPI.Controllers.CommandController→ContractManagement.Domain.Aggregates.Contract.Commands.ChangeContractAmountContractManagement.WebAPI.Controllers.CommandController→ContractManagement.Domain.Aggregates.Contract.Commands.ChangeContractTermContractManagement.WebAPI.Controllers.CommandController→ContractManagement.Domain.Aggregates.Contract.Commands.RegisterContractContractManagement.WebAPI.Controllers.CommandController→ContractManagement.Domain.Aggregates.Contract.Commands.RegisterContractV2
- Direction
- ContractManagement.WebAPI.Controllers uses ContractManagement.Domain.Aggregates.Contract.Commands, so a change to ContractManagement.Domain.Aggregates.Contract.Commands can break ContractManagement.WebAPI.Controllers, while a change to ContractManagement.WebAPI.Controllers can't break ContractManagement.Domain.Aggregates.Contract.Commands.
- Position
- Below the diagonal: ContractManagement.WebAPI.Controllers uses a module listed above it, which is the healthy direction.
36→13 ContractManagement.WebAPI.Controllers uses ContractManagement.Domain.Aggregates.Portfolio.Commands✕
- Connections
- 1 pair of types, where a type in ContractManagement.WebAPI.Controllers uses a type in ContractManagement.Domain.Aggregates.Portfolio.Commands.
- The types involved
ContractManagement.WebAPI.Controllers.CommandController→ContractManagement.Domain.Aggregates.Portfolio.Commands.AddDocument
- Direction
- ContractManagement.WebAPI.Controllers uses ContractManagement.Domain.Aggregates.Portfolio.Commands, so a change to ContractManagement.Domain.Aggregates.Portfolio.Commands can break ContractManagement.WebAPI.Controllers, while a change to ContractManagement.WebAPI.Controllers can't break ContractManagement.Domain.Aggregates.Portfolio.Commands.
- Position
- Below the diagonal: ContractManagement.WebAPI.Controllers uses a module listed above it, which is the healthy direction.
36→31 ContractManagement.WebAPI.Controllers uses ContractManagement.Infrastructure.Persistence.EFCore✕
- Connections
- 1 pair of types, where a type in ContractManagement.WebAPI.Controllers uses a type in ContractManagement.Infrastructure.Persistence.EFCore.
- The types involved
ContractManagement.WebAPI.Controllers.QueryController→ContractManagement.Infrastructure.Persistence.EFCore.ServiceDbContext
- Direction
- ContractManagement.WebAPI.Controllers uses ContractManagement.Infrastructure.Persistence.EFCore, so a change to ContractManagement.Infrastructure.Persistence.EFCore can break ContractManagement.WebAPI.Controllers, while a change to ContractManagement.WebAPI.Controllers can't break ContractManagement.Infrastructure.Persistence.EFCore.
- Position
- Below the diagonal: ContractManagement.WebAPI.Controllers uses a module listed above it, which is the healthy direction.
37→10 Contractmanagement.Features.ContractCancellation uses Application.Common.Interfaces✕
- Connections
- 5 pairs of types, where a type in Contractmanagement.Features.ContractCancellation uses a type in Application.Common.Interfaces.
- The types involved
Contractmanagement.Features.ContractCancellation.CancelContractHandler→Application.Common.Interfaces.IAggregateServiceContractmanagement.Features.ContractCancellation.CancelContractHandler→Application.Common.Interfaces.ICommandHandlerContractmanagement.Features.ContractCancellation.ContractCancelledHandler→Application.Common.Interfaces.IEventHandlerContractmanagement.Features.ContractCancellation.ContractCancelledHandler→Application.Common.Interfaces.IUnitOfWorkContractmanagement.Features.ContractCancellation.ContractCancelledProjection→Application.Common.Interfaces.IProjection
- Direction
- Contractmanagement.Features.ContractCancellation uses Application.Common.Interfaces, so a change to Application.Common.Interfaces can break Contractmanagement.Features.ContractCancellation, while a change to Contractmanagement.Features.ContractCancellation can't break Application.Common.Interfaces.
- Position
- Below the diagonal: Contractmanagement.Features.ContractCancellation uses a module listed above it, which is the healthy direction.
37→12 Contractmanagement.Features.ContractCancellation uses ContractManagement.Domain.Aggregates.Contract.Commands✕
- Connections
- 1 pair of types, where a type in Contractmanagement.Features.ContractCancellation uses a type in ContractManagement.Domain.Aggregates.Contract.Commands.
- The types involved
Contractmanagement.Features.ContractCancellation.CancelContractHandler→ContractManagement.Domain.Aggregates.Contract.Commands.CancelContract
- Direction
- Contractmanagement.Features.ContractCancellation uses ContractManagement.Domain.Aggregates.Contract.Commands, so a change to ContractManagement.Domain.Aggregates.Contract.Commands can break Contractmanagement.Features.ContractCancellation, while a change to Contractmanagement.Features.ContractCancellation can't break ContractManagement.Domain.Aggregates.Contract.Commands.
- Position
- Below the diagonal: Contractmanagement.Features.ContractCancellation uses a module listed above it, which is the healthy direction.
37→18 Contractmanagement.Features.ContractCancellation uses ContractManagement.Application.Interfaces✕
- Connections
- 1 pair of types, where a type in Contractmanagement.Features.ContractCancellation uses a type in ContractManagement.Application.Interfaces.
- The types involved
Contractmanagement.Features.ContractCancellation.ContractCancelledProjection→ContractManagement.Application.Interfaces.IContractReadModelRepository
- Direction
- Contractmanagement.Features.ContractCancellation uses ContractManagement.Application.Interfaces, so a change to ContractManagement.Application.Interfaces can break Contractmanagement.Features.ContractCancellation, while a change to Contractmanagement.Features.ContractCancellation can't break ContractManagement.Application.Interfaces.
- Position
- Below the diagonal: Contractmanagement.Features.ContractCancellation uses a module listed above it, which is the healthy direction.
37→19 Contractmanagement.Features.ContractCancellation uses ContractManagement.Domain.Aggregates.Contract.DomainEvents✕
- Connections
- 2 pairs of types, where a type in Contractmanagement.Features.ContractCancellation uses a type in ContractManagement.Domain.Aggregates.Contract.DomainEvents.
- The types involved
Contractmanagement.Features.ContractCancellation.ContractCancelledHandler→ContractManagement.Domain.Aggregates.Contract.DomainEvents.ContractCancelledContractmanagement.Features.ContractCancellation.ContractCancelledProjection→ContractManagement.Domain.Aggregates.Contract.DomainEvents.ContractCancelled
- Direction
- Contractmanagement.Features.ContractCancellation uses ContractManagement.Domain.Aggregates.Contract.DomainEvents, so a change to ContractManagement.Domain.Aggregates.Contract.DomainEvents can break Contractmanagement.Features.ContractCancellation, while a change to Contractmanagement.Features.ContractCancellation can't break ContractManagement.Domain.Aggregates.Contract.DomainEvents.
- Position
- Below the diagonal: Contractmanagement.Features.ContractCancellation uses a module listed above it, which is the healthy direction.
37→30 Contractmanagement.Features.ContractCancellation uses ContractManagement.Domain.Aggregates.Contract✕
- Connections
- 1 pair of types, where a type in Contractmanagement.Features.ContractCancellation uses a type in ContractManagement.Domain.Aggregates.Contract.
- The types involved
Contractmanagement.Features.ContractCancellation.CancelContractHandler→ContractManagement.Domain.Aggregates.Contract.Contract
- Direction
- Contractmanagement.Features.ContractCancellation uses ContractManagement.Domain.Aggregates.Contract, so a change to ContractManagement.Domain.Aggregates.Contract can break Contractmanagement.Features.ContractCancellation, while a change to Contractmanagement.Features.ContractCancellation can't break ContractManagement.Domain.Aggregates.Contract.
- Position
- Below the diagonal: Contractmanagement.Features.ContractCancellation uses a module listed above it, which is the healthy direction.
38→10 Contractmanagement.Features.ContractMaintenance uses Application.Common.Interfaces✕
- Connections
- 10 pairs of types, where a type in Contractmanagement.Features.ContractMaintenance uses a type in Application.Common.Interfaces.
- The types involved
Contractmanagement.Features.ContractMaintenance.ChangeContractAmountFeature→Application.Common.Interfaces.IAggregateServiceContractmanagement.Features.ContractMaintenance.ChangeContractAmountFeature→Application.Common.Interfaces.ICommandHandlerContractmanagement.Features.ContractMaintenance.ChangeContractAmountFeature→Application.Common.Interfaces.IEventHandlerContractmanagement.Features.ContractMaintenance.ChangeContractAmountFeature→Application.Common.Interfaces.IProjectionContractmanagement.Features.ContractMaintenance.ChangeContractAmountFeature→Application.Common.Interfaces.IUnitOfWorkContractmanagement.Features.ContractMaintenance.ChangeContractTermFeature→Application.Common.Interfaces.IAggregateServiceContractmanagement.Features.ContractMaintenance.ChangeContractTermFeature→Application.Common.Interfaces.ICommandHandlerContractmanagement.Features.ContractMaintenance.ChangeContractTermFeature→Application.Common.Interfaces.IEventHandlerContractmanagement.Features.ContractMaintenance.ChangeContractTermFeature→Application.Common.Interfaces.IProjectionContractmanagement.Features.ContractMaintenance.ChangeContractTermFeature→Application.Common.Interfaces.IUnitOfWork
- Direction
- Contractmanagement.Features.ContractMaintenance uses Application.Common.Interfaces, so a change to Application.Common.Interfaces can break Contractmanagement.Features.ContractMaintenance, while a change to Contractmanagement.Features.ContractMaintenance can't break Application.Common.Interfaces.
- Position
- Below the diagonal: Contractmanagement.Features.ContractMaintenance uses a module listed above it, which is the healthy direction.
38→12 Contractmanagement.Features.ContractMaintenance uses ContractManagement.Domain.Aggregates.Contract.Commands✕
- Connections
- 2 pairs of types, where a type in Contractmanagement.Features.ContractMaintenance uses a type in ContractManagement.Domain.Aggregates.Contract.Commands.
- The types involved
Contractmanagement.Features.ContractMaintenance.ChangeContractAmountFeature→ContractManagement.Domain.Aggregates.Contract.Commands.ChangeContractAmountContractmanagement.Features.ContractMaintenance.ChangeContractTermFeature→ContractManagement.Domain.Aggregates.Contract.Commands.ChangeContractTerm
- Direction
- Contractmanagement.Features.ContractMaintenance uses ContractManagement.Domain.Aggregates.Contract.Commands, so a change to ContractManagement.Domain.Aggregates.Contract.Commands can break Contractmanagement.Features.ContractMaintenance, while a change to Contractmanagement.Features.ContractMaintenance can't break ContractManagement.Domain.Aggregates.Contract.Commands.
- Position
- Below the diagonal: Contractmanagement.Features.ContractMaintenance uses a module listed above it, which is the healthy direction.
38→18 Contractmanagement.Features.ContractMaintenance uses ContractManagement.Application.Interfaces✕
- Connections
- 2 pairs of types, where a type in Contractmanagement.Features.ContractMaintenance uses a type in ContractManagement.Application.Interfaces.
- The types involved
Contractmanagement.Features.ContractMaintenance.ChangeContractAmountFeature→ContractManagement.Application.Interfaces.IContractReadModelRepositoryContractmanagement.Features.ContractMaintenance.ChangeContractTermFeature→ContractManagement.Application.Interfaces.IContractReadModelRepository
- Direction
- Contractmanagement.Features.ContractMaintenance uses ContractManagement.Application.Interfaces, so a change to ContractManagement.Application.Interfaces can break Contractmanagement.Features.ContractMaintenance, while a change to Contractmanagement.Features.ContractMaintenance can't break ContractManagement.Application.Interfaces.
- Position
- Below the diagonal: Contractmanagement.Features.ContractMaintenance uses a module listed above it, which is the healthy direction.
38→19 Contractmanagement.Features.ContractMaintenance uses ContractManagement.Domain.Aggregates.Contract.DomainEvents✕
- Connections
- 2 pairs of types, where a type in Contractmanagement.Features.ContractMaintenance uses a type in ContractManagement.Domain.Aggregates.Contract.DomainEvents.
- The types involved
Contractmanagement.Features.ContractMaintenance.ChangeContractAmountFeature→ContractManagement.Domain.Aggregates.Contract.DomainEvents.ContractAmountChangedContractmanagement.Features.ContractMaintenance.ChangeContractTermFeature→ContractManagement.Domain.Aggregates.Contract.DomainEvents.ContractTermChanged
- Direction
- Contractmanagement.Features.ContractMaintenance uses ContractManagement.Domain.Aggregates.Contract.DomainEvents, so a change to ContractManagement.Domain.Aggregates.Contract.DomainEvents can break Contractmanagement.Features.ContractMaintenance, while a change to Contractmanagement.Features.ContractMaintenance can't break ContractManagement.Domain.Aggregates.Contract.DomainEvents.
- Position
- Below the diagonal: Contractmanagement.Features.ContractMaintenance uses a module listed above it, which is the healthy direction.
38→30 Contractmanagement.Features.ContractMaintenance uses ContractManagement.Domain.Aggregates.Contract✕
- Connections
- 2 pairs of types, where a type in Contractmanagement.Features.ContractMaintenance uses a type in ContractManagement.Domain.Aggregates.Contract.
- The types involved
Contractmanagement.Features.ContractMaintenance.ChangeContractAmountFeature→ContractManagement.Domain.Aggregates.Contract.ContractContractmanagement.Features.ContractMaintenance.ChangeContractTermFeature→ContractManagement.Domain.Aggregates.Contract.Contract
- Direction
- Contractmanagement.Features.ContractMaintenance uses ContractManagement.Domain.Aggregates.Contract, so a change to ContractManagement.Domain.Aggregates.Contract can break Contractmanagement.Features.ContractMaintenance, while a change to Contractmanagement.Features.ContractMaintenance can't break ContractManagement.Domain.Aggregates.Contract.
- Position
- Below the diagonal: Contractmanagement.Features.ContractMaintenance uses a module listed above it, which is the healthy direction.
39→5 Contractmanagement.Features.ContractRegistration uses ContractManagement.Domain.Services✕
- Connections
- 2 pairs of types, where a type in Contractmanagement.Features.ContractRegistration uses a type in ContractManagement.Domain.Services.
- The types involved
Contractmanagement.Features.ContractRegistration.RegisterContractHandler→ContractManagement.Domain.Services.ICustomerServiceContractmanagement.Features.ContractRegistration.RegisterContractHandler→ContractManagement.Domain.Services.IProductService
- Direction
- Contractmanagement.Features.ContractRegistration uses ContractManagement.Domain.Services, so a change to ContractManagement.Domain.Services can break Contractmanagement.Features.ContractRegistration, while a change to Contractmanagement.Features.ContractRegistration can't break ContractManagement.Domain.Services.
- Position
- Below the diagonal: Contractmanagement.Features.ContractRegistration uses a module listed above it, which is the healthy direction.
39→10 Contractmanagement.Features.ContractRegistration uses Application.Common.Interfaces✕
- Connections
- 6 pairs of types, where a type in Contractmanagement.Features.ContractRegistration uses a type in Application.Common.Interfaces.
- The types involved
Contractmanagement.Features.ContractRegistration.ContractRegisteredHandler→Application.Common.Interfaces.ICommandHandlerContractmanagement.Features.ContractRegistration.ContractRegisteredHandler→Application.Common.Interfaces.IEventHandlerContractmanagement.Features.ContractRegistration.ContractRegisteredHandler→Application.Common.Interfaces.IUnitOfWorkContractmanagement.Features.ContractRegistration.ContractRegisteredProjection→Application.Common.Interfaces.IProjectionContractmanagement.Features.ContractRegistration.RegisterContractHandler→Application.Common.Interfaces.IAggregateServiceContractmanagement.Features.ContractRegistration.RegisterContractHandler→Application.Common.Interfaces.ICommandHandler
- Direction
- Contractmanagement.Features.ContractRegistration uses Application.Common.Interfaces, so a change to Application.Common.Interfaces can break Contractmanagement.Features.ContractRegistration, while a change to Contractmanagement.Features.ContractRegistration can't break Application.Common.Interfaces.
- Position
- Below the diagonal: Contractmanagement.Features.ContractRegistration uses a module listed above it, which is the healthy direction.
39→12 Contractmanagement.Features.ContractRegistration uses ContractManagement.Domain.Aggregates.Contract.Commands✕
- Connections
- 1 pair of types, where a type in Contractmanagement.Features.ContractRegistration uses a type in ContractManagement.Domain.Aggregates.Contract.Commands.
- The types involved
Contractmanagement.Features.ContractRegistration.RegisterContractHandler→ContractManagement.Domain.Aggregates.Contract.Commands.RegisterContractV2
- Direction
- Contractmanagement.Features.ContractRegistration uses ContractManagement.Domain.Aggregates.Contract.Commands, so a change to ContractManagement.Domain.Aggregates.Contract.Commands can break Contractmanagement.Features.ContractRegistration, while a change to Contractmanagement.Features.ContractRegistration can't break ContractManagement.Domain.Aggregates.Contract.Commands.
- Position
- Below the diagonal: Contractmanagement.Features.ContractRegistration uses a module listed above it, which is the healthy direction.
39→13 Contractmanagement.Features.ContractRegistration uses ContractManagement.Domain.Aggregates.Portfolio.Commands✕
- Connections
- 1 pair of types, where a type in Contractmanagement.Features.ContractRegistration uses a type in ContractManagement.Domain.Aggregates.Portfolio.Commands.
- The types involved
Contractmanagement.Features.ContractRegistration.ContractRegisteredHandler→ContractManagement.Domain.Aggregates.Portfolio.Commands.CreatePortfolio
- Direction
- Contractmanagement.Features.ContractRegistration uses ContractManagement.Domain.Aggregates.Portfolio.Commands, so a change to ContractManagement.Domain.Aggregates.Portfolio.Commands can break Contractmanagement.Features.ContractRegistration, while a change to Contractmanagement.Features.ContractRegistration can't break ContractManagement.Domain.Aggregates.Portfolio.Commands.
- Position
- Below the diagonal: Contractmanagement.Features.ContractRegistration uses a module listed above it, which is the healthy direction.
39→18 Contractmanagement.Features.ContractRegistration uses ContractManagement.Application.Interfaces✕
- Connections
- 1 pair of types, where a type in Contractmanagement.Features.ContractRegistration uses a type in ContractManagement.Application.Interfaces.
- The types involved
Contractmanagement.Features.ContractRegistration.ContractRegisteredProjection→ContractManagement.Application.Interfaces.IContractReadModelRepository
- Direction
- Contractmanagement.Features.ContractRegistration uses ContractManagement.Application.Interfaces, so a change to ContractManagement.Application.Interfaces can break Contractmanagement.Features.ContractRegistration, while a change to Contractmanagement.Features.ContractRegistration can't break ContractManagement.Application.Interfaces.
- Position
- Below the diagonal: Contractmanagement.Features.ContractRegistration uses a module listed above it, which is the healthy direction.
39→19 Contractmanagement.Features.ContractRegistration uses ContractManagement.Domain.Aggregates.Contract.DomainEvents✕
- Connections
- 3 pairs of types, where a type in Contractmanagement.Features.ContractRegistration uses a type in ContractManagement.Domain.Aggregates.Contract.DomainEvents.
- The types involved
Contractmanagement.Features.ContractRegistration.ContractRegisteredHandler→ContractManagement.Domain.Aggregates.Contract.DomainEvents.ContractRegisteredV2Contractmanagement.Features.ContractRegistration.ContractRegisteredProjection→ContractManagement.Domain.Aggregates.Contract.DomainEvents.ContractRegisteredContractmanagement.Features.ContractRegistration.ContractRegisteredProjection→ContractManagement.Domain.Aggregates.Contract.DomainEvents.ContractRegisteredV2
- Direction
- Contractmanagement.Features.ContractRegistration uses ContractManagement.Domain.Aggregates.Contract.DomainEvents, so a change to ContractManagement.Domain.Aggregates.Contract.DomainEvents can break Contractmanagement.Features.ContractRegistration, while a change to Contractmanagement.Features.ContractRegistration can't break ContractManagement.Domain.Aggregates.Contract.DomainEvents.
- Position
- Below the diagonal: Contractmanagement.Features.ContractRegistration uses a module listed above it, which is the healthy direction.
39→30 Contractmanagement.Features.ContractRegistration uses ContractManagement.Domain.Aggregates.Contract✕
- Connections
- 1 pair of types, where a type in Contractmanagement.Features.ContractRegistration uses a type in ContractManagement.Domain.Aggregates.Contract.
- The types involved
Contractmanagement.Features.ContractRegistration.RegisterContractHandler→ContractManagement.Domain.Aggregates.Contract.Contract
- Direction
- Contractmanagement.Features.ContractRegistration uses ContractManagement.Domain.Aggregates.Contract, so a change to ContractManagement.Domain.Aggregates.Contract can break Contractmanagement.Features.ContractRegistration, while a change to Contractmanagement.Features.ContractRegistration can't break ContractManagement.Domain.Aggregates.Contract.
- Position
- Below the diagonal: Contractmanagement.Features.ContractRegistration uses a module listed above it, which is the healthy direction.
40→8 OutputManagementService.Consumers uses Generic.IntegrationEvents✕
- Connections
- 1 pair of types, where a type in OutputManagementService.Consumers uses a type in Generic.IntegrationEvents.
- The types involved
OutputManagementService.Consumers.OutputManagement_DayHasPassedConsumer→Generic.IntegrationEvents.DayHasPassed
- Direction
- OutputManagementService.Consumers uses Generic.IntegrationEvents, so a change to Generic.IntegrationEvents can break OutputManagementService.Consumers, while a change to OutputManagementService.Consumers can't break Generic.IntegrationEvents.
- Position
- Below the diagonal: OutputManagementService.Consumers uses a module listed above it, which is the healthy direction.
40→9 OutputManagementService.Consumers uses OutputManagementService.EmailService✕
- Connections
- 1 pair of types, where a type in OutputManagementService.Consumers uses a type in OutputManagementService.EmailService.
- The types involved
OutputManagementService.Consumers.OutputManagement_DayHasPassedConsumer→OutputManagementService.EmailService.IEmailService
- Direction
- OutputManagementService.Consumers uses OutputManagementService.EmailService, so a change to OutputManagementService.EmailService can break OutputManagementService.Consumers, while a change to OutputManagementService.Consumers can't break OutputManagementService.EmailService.
- Position
- Below the diagonal: OutputManagementService.Consumers uses a module listed above it, which is the healthy direction.
40→14 OutputManagementService.Consumers uses CustomerManagement.Application.IntegrationEvents✕
- Connections
- 1 pair of types, where a type in OutputManagementService.Consumers uses a type in CustomerManagement.Application.IntegrationEvents.
- The types involved
OutputManagementService.Consumers.OutputManagement_CustomerRegisteredConsumer→CustomerManagement.Application.IntegrationEvents.CustomerRegistered
- Direction
- OutputManagementService.Consumers uses CustomerManagement.Application.IntegrationEvents, so a change to CustomerManagement.Application.IntegrationEvents can break OutputManagementService.Consumers, while a change to OutputManagementService.Consumers can't break CustomerManagement.Application.IntegrationEvents.
- Position
- Below the diagonal: OutputManagementService.Consumers uses a module listed above it, which is the healthy direction.
40→16 OutputManagementService.Consumers uses ProductManagement.Application.IntegrationEvents✕
- Connections
- 1 pair of types, where a type in OutputManagementService.Consumers uses a type in ProductManagement.Application.IntegrationEvents.
- The types involved
OutputManagementService.Consumers.OutputManagement_ProductRegisteredConsumer→ProductManagement.Application.IntegrationEvents.ProductRegistered
- Direction
- OutputManagementService.Consumers uses ProductManagement.Application.IntegrationEvents, so a change to ProductManagement.Application.IntegrationEvents can break OutputManagementService.Consumers, while a change to OutputManagementService.Consumers can't break ProductManagement.Application.IntegrationEvents.
- Position
- Below the diagonal: OutputManagementService.Consumers uses a module listed above it, which is the healthy direction.
40→26 OutputManagementService.Consumers uses OutputManagementService.Repositories✕
- Connections
- 9 pairs of types, where a type in OutputManagementService.Consumers uses a type in OutputManagementService.Repositories.
- The types involved
OutputManagementService.Consumers.OutputManagement_ContractAmountChangedConsumer→OutputManagementService.Repositories.IContractRepositoryOutputManagementService.Consumers.OutputManagement_ContractCancelledConsumer→OutputManagementService.Repositories.IContractRepositoryOutputManagementService.Consumers.OutputManagement_ContractRegisteredConsumer→OutputManagementService.Repositories.IContractRepositoryOutputManagementService.Consumers.OutputManagement_ContractTermChangedConsumer→OutputManagementService.Repositories.IContractRepositoryOutputManagementService.Consumers.OutputManagement_CustomerRegisteredConsumer→OutputManagementService.Repositories.ICustomerRepositoryOutputManagementService.Consumers.OutputManagement_DayHasPassedConsumer→OutputManagementService.Repositories.IContractRepositoryOutputManagementService.Consumers.OutputManagement_DayHasPassedConsumer→OutputManagementService.Repositories.ICustomerRepositoryOutputManagementService.Consumers.OutputManagement_DayHasPassedConsumer→OutputManagementService.Repositories.IProductRepositoryOutputManagementService.Consumers.OutputManagement_ProductRegisteredConsumer→OutputManagementService.Repositories.IProductRepository
- Direction
- OutputManagementService.Consumers uses OutputManagementService.Repositories, so a change to OutputManagementService.Repositories can break OutputManagementService.Consumers, while a change to OutputManagementService.Consumers can't break OutputManagementService.Repositories.
- Position
- Below the diagonal: OutputManagementService.Consumers uses a module listed above it, which is the healthy direction.
40→28 OutputManagementService.Consumers uses ContractManagement.Application.IntegrationEvents✕
- Connections
- 4 pairs of types, where a type in OutputManagementService.Consumers uses a type in ContractManagement.Application.IntegrationEvents.
- The types involved
OutputManagementService.Consumers.OutputManagement_ContractAmountChangedConsumer→ContractManagement.Application.IntegrationEvents.ContractAmountChangedOutputManagementService.Consumers.OutputManagement_ContractCancelledConsumer→ContractManagement.Application.IntegrationEvents.ContractCancelledOutputManagementService.Consumers.OutputManagement_ContractRegisteredConsumer→ContractManagement.Application.IntegrationEvents.ContractRegisteredOutputManagementService.Consumers.OutputManagement_ContractTermChangedConsumer→ContractManagement.Application.IntegrationEvents.ContractTermChanged
- Direction
- OutputManagementService.Consumers uses ContractManagement.Application.IntegrationEvents, so a change to ContractManagement.Application.IntegrationEvents can break OutputManagementService.Consumers, while a change to OutputManagementService.Consumers can't break ContractManagement.Application.IntegrationEvents.
- Position
- Below the diagonal: OutputManagementService.Consumers 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 |
|---|---|---|
| A03:2025 — Software Supply Chain Failures | 11 | High / Critical |
| A05:2025 — Injection | 8 | Medium |
| A01:2025 — Broken Access Control | 3 | Medium |
Roadmap
Top priorities: Protect endpoints by default-deny: [Authorize] + role/policy authorization, or imperative guard methods (throw-on-violation) called from every handler; Add a CI workflow that builds and runs the test suite on every push/PR; Run what this repository's stack ships: CodeQL's csharp pack, or a .NET security analyzer package — or `semgrep --config=auto`, which runs on any language — locally for now, since there is no CI pipeline here yet, and as a step of the first workflow you add so a security regression fails the build instead of landing.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Protect endpoints by default-deny: [Authorize] + role/policy authorization, or imperative guard methods (throw-on-violation) called from every handler. | +6.5 pts | Medium | Access Controls |
| Add a CI workflow that builds and runs the test suite on every push/PR. | +4.5 pts | Medium | CI/CD gates |
| Run what this repository's stack ships: CodeQL's csharp pack, or a .NET security analyzer package — or `semgrep --config=auto`, which runs on any language — locally for now, since there is no CI pipeline here yet, and as a step of the first workflow you add so a security regression fails the build instead of landing. | +4.5 pts | Medium | Security & performance tooling |
| Encrypt sensitive data at rest (ASP.NET Core Data Protection / column encryption) and manage keys in a vault. Skip if delegated to infra (Postgres TDE, KMS, etc.). | +4.1 pts | Medium | Data Protection |
| Resolve the 8 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (3), REDACTED (2), REDACTED (2). | +2.0 pts | Low | Dependency Vulnerabilities |
| Resolve the 1 No ADRs found finding(s) in ADR Quality. | +1.5 pts | Low | ADR Quality |
| Resolve the 6 redundant comment finding(s) in Comment Value — start with Program.cs (3), AggregateRoot.cs, ContractRegisteredHandler.cs. | +1.5 pts | Low | Comment Value |
| Add `AddStandardResilienceHandler()` (or a Polly policy and an explicit timeout) to each client registration flagged here, so a flaky dependency can't take the app down. | +2.9 pts | Medium | Outbound HTTP resilience |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 1.4 | Slop | Dependency Vulnerabilities: Critical CVE: REDACTED |
| REDACTED | 3.0 | Slop | Dependency Vulnerabilities: High CVE: REDACTED |
| REDACTED | 3.7 | Slop | Dependency Vulnerabilities: High CVE: REDACTED |
| REDACTED | 4.5 | Mixed | Explicit Debt: WriteOnlyPrivateField |
| REDACTED | 5.1 | Mixed | Dependency Vulnerabilities: High CVE: REDACTED |
| REDACTED | 5.3 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| src/Common/Application.Common/Services/AggregateService.cs | 6.4 | Mixed | Explicit Debt: WriteOnlyPrivateField |
| REDACTED | 6.9 | Mixed | Data Compliance (PII/GDPR): REDACTED |
| src/ContractManagement/Infrastructure/DependencyInjection/IServiceCollectionExtensions.cs | 7.3 | Mixed | Explicit Debt: TodoComment |
| src/Common/Application.Common/Interfaces/IEventPublisher.cs | 7.3 | Mixed | Explicit Debt: Dead code: PublishDomainEventsAsync |
| src/Common/Application.Common/Interfaces/IUnitOfWork.cs | 7.3 | Mixed | Explicit Debt: Dead code: AddDomainEventToPublish |
| REDACTED | 7.9 | Mixed | Data Compliance (PII/GDPR): Medium: REDACTED |
| src/Common/Domain.Common/Domain.Common.csproj | 7.9 | Mixed | Platform End-of-Life: End-of-life runtime: .NET net6.0 |
| src/ContractManagement/Application/Application.csproj | 7.9 | Mixed | Platform End-of-Life: End-of-life runtime: .NET net6.0 |
| src/ContractManagement/Domain/Domain.csproj | 7.9 | Mixed | Platform End-of-Life: End-of-life runtime: .NET net6.0 |
| src/ContractManagement/Infrastructure/Infrastructure.csproj | 7.9 | Mixed | Platform End-of-Life: End-of-life runtime: .NET net6.0 |
| src/ContractManagement/Interface/MessageReceiver/MessageReceiver.csproj | 7.9 | Mixed | Platform End-of-Life: End-of-life runtime: .NET net6.0 |
| src/ContractManagement/Interface/WebAPI/WebAPI.csproj | 7.9 | Mixed | Platform End-of-Life: End-of-life runtime: .NET net6.0 |
| src/OutputManagement/OutputManagementService/OutputManagementService.csproj | 7.9 | Mixed | Platform End-of-Life: End-of-life runtime: .NET net6.0 |
| src/Common/Infrastructure.Common/UnitOfWork/PersistenceAndMessagingUnitOfWork.cs | 8.2 | Near-clean | Explicit Debt: TodoComment |
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, 179 of 193 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.
- 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-contributor repository — bus factor is not applicable (1 contributor(s) across 50 commit(s) sampled, automation and bot accounts excluded). Concentration needs a team to concentrate: with one contributor there is nobody to spread the knowledge to, so there is nothing here for the owner to act on.
- D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This kind did not reach the 95 % precision gate in three adjudicated runs (docs/plans/deterministic-engine/adjudication/D19-sample3-v3.md), so by the pre-registered fallback it publishes no row until a re-measurement shows it does. The candidates are counted here, not reported as findings, and the score does not include them.
- D21 Naming Consistency — 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. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
- D22 Internal API Consistency — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. The loaded project set declares no packable project and no `.Contracts` project, so there is no intentionally-exposed surface for API consistency to be judged over.
- 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.
- AXR1 Runtime accessibility — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via ToolchainServer (src/ContractManagement/Interface/WebAPI). the service did not build — `dotnet build 'WebAPI.csproj'` exited 1: ; runtime evidence skipped (launch chosen because src/ContractManagement/Interface/WebAPI/WebAPI.csproj is a Microsoft.NET.Sdk.Web project).
- DM8 Value-object opportunities — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check finds primitive parameters that travel together through several signatures of the domain (a missing value object). Its deterministic rule has not yet shown 95 % precision on adjudicated rows, so the clumps it finds are counted here and not published as findings, and the card carries no score. That is a limit of the analyzer, not a finding about your code.
- 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.
- P2 Observability — 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. 26 further occurrence(s) are not listed individually; the score already reflects all 66.
- X2 Cancellation propagation — 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. 16 further occurrence(s) are not listed individually; the score already reflects all 56.
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.
- D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
- D21 Naming Consistency: Naming consistency compares each name with the convention its structural peers follow in this repository: it cannot tell whether a consistently used name is a good one, and languages other than C# and TypeScript are not measured.
- 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.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- DM4 Rich vs anemic model: Behaviour is detected as state mutation inside a method body — a method that enforces an invariant by validating-and-throwing without mutating reads as a query, and mutation delegated through an interface the scan can't resolve isn't credited; entities with zero public properties still drop out of the population. It detects that state changes, not whether the rule is correct.
- DM6 Domain ↔ infrastructure boundary: Infrastructure reached through a hand-rolled wrapper, a domain-named facade, reflection, or a string-keyed service locator resolves to a non-infra type and isn't seen; the body scan is symbol resolution over syntax, not full dataflow. A clean result means "no resolved infra reference in a domain body", not a proof of purity.
- M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
Dimensions
D1 · Cyclomatic Complexity
0 method(s) exceeded the cyclomatic complexity threshold of 15.
D2 · Cognitive Complexity
0 method(s) exceeded the cognitive complexity threshold of 15.
D3 · God Classes
0 god class(es) detected.
D4 · Code Duplication
0 duplicated block group(s) detected.
D5 · Coupling
11 projects, 0 dependency cycle(s), 0 unstable depended-on project(s).
D6 · Cohesion (LCOM4)
0 of 16 classes have LCOM4 above 3.
D9 · Test Distribution
17 test methods: 17 unit, 0 integration, 0 BDD, 0 e2e.
D10 · Test Quality
0 skipped, 0 zero-assertion, 1 mock references across 17 tests.
D11 · Test Reliability
0 flaky across 1 measured tier(s). unit: measured (0 flaky).
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D14 · License Compliance
0 of 250 packages use a banned license. ★ DEPTH: this repository's MSBuild projects declare 23 direct `PackageReference`(s), and 227 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
7 deducted debt markers + 13 dead symbols across 3532 LoC in the .NET projects (1.2/KLoC) → score 7.5.
What to do
- Resolve the 3 WriteOnlyPrivateField finding(s) in Explicit Debt — start with AggregateService.cs (2), REDACTED. — One of this dimension's main actionable groups (3 issue-level).
- Resolve the 13 Dead code finding(s) in Explicit Debt — start with IEventPublisher.cs (2), IUnitOfWork.cs (2), CancelContractHandler.cs. — One of this dimension's main actionable groups (13 warning-level).
- Resolve the 3 TodoComment finding(s) in Explicit Debt — start with IServiceCollectionExtensions.cs (2), PersistenceAndMessagingUnitOfWork.cs. — One of this dimension's main actionable groups (3 warning-level).
- Stand up a CI pipeline, then gate Explicit Debt in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D18 · Solution Shape
11 projects, 167 source files, 4093 hand-written lines of code (3532 production / 561 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 591 generated (machine-written code — designer, scaffolded and tool-emitted files — excluded from quality), 15 inter-project edges.
D19 · Documentation Quality
1 of 2 documentation facets pass in full; short on: F2 example. 3 document(s) read across 11 unit(s).
What to do
- Resolve the 1 Documentation finding(s) in Documentation Quality — start with README.md. — One of this dimension's main actionable groups (1 recommendation-level).
D20 · ADR Quality
No architecture decision records were found.
What to do
- Resolve the 1 No ADRs found finding(s) in ADR Quality. — One of this dimension's main actionable groups (1 recommendation-level).
D21 · Naming Consistency
0 naming inconsistencies among 15 declarations measured against a convention their peers follow.
D24 · Comment Value
6 of 43 judged comments only repeat the code they sit on (14.0 %). 3 comment(s) in another language or script were not judged.
What to do
- Resolve the 6 redundant comment finding(s) in Comment Value — start with Program.cs (3), AggregateRoot.cs, ContractRegisteredHandler.cs. — One of this dimension's main actionable groups (6 recommendation-level).
D26 · Project Cohesion
0 of 11 projects flagged as possibly oversized/incoherent.
D27 · Navigability
92 % of calls cross a namespace and 8 % go through an interface, but 89 % 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)
8 finding(s): 0 critical, 0 high, 8 medium, 0 low.
What to do
- Resolve the 8 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (6), REDACTED (2). — One of this dimension's main actionable groups (8 warning-level).
D30 · Dependency Vulnerabilities
11 finding(s): 1 critical, 8 high, 2 medium, 0 low.
What to do
- Resolve the 8 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (3), REDACTED (2), REDACTED (2). — One of this dimension's main actionable groups (8 issue-level).
- Resolve the 1 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 2 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (2). — One of this dimension's main actionable groups (2 warning-level).
D32 · Data Compliance (PII/GDPR)
3 finding(s): 0 critical, 0 high, 3 medium, 0 low.
What to do
- Resolve the 2 REDACTED finding(s) in Data Compliance (PII/GDPR) — start with REDACTED (2). — One of this dimension's main actionable groups (2 warning-level).
- 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
10 of 10 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is src/!Support/MessageSender/MessageSender.cs. Counted over 10 of the 149 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
What to do
- Resolve the 10 Orphaned file finding(s) in Knowledge Freshness — start with IServiceCollectionExtensions.cs (2), MessageSender.cs, Contract.cs. — One of this dimension's main actionable groups (10 recommendation-level).
- Resolve the 1 Orphaned files with no living knowledge finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
D35 · Change Coupling
No strong hidden change-coupling between production files.
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
D44 · Platform End-of-Life
1 end-of-life runtime(s) and 0 end-of-life framework(s), read from 11 platform declaration(s) and 0 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
What to do
- Resolve the 11 End-of-life runtime finding(s) in Platform End-of-Life — start with REDACTED, REDACTED, Domain.Common.csproj. — One of this dimension's main actionable groups (11 warning-level).
Frontend & cross-cutting dimensions
AX1 · Captive dependencies
AX10 · Code composition
AX2 · Stateful singletons
- `BusObserver` is a singleton (one shared instance) but mutates instance state outside any lock (BusHasStarted; e.g. `BusHasStarted` at line 22). — src/!Support/MessageSender/BusObserver.cs:3
What to do
- Keep singletons stateless or back their state with thread-safe types (Concurrent*/Immutable*); otherwise concurrent callers race.
AX3 · Project dependency cycles
AX4 · Dependency direction
AX5 · Architecture & structure
AX6 · Interface segregation
AX8 · Test isolation
C1 · Data Protection
- No data-protection or encryption usage (ASP.NET Data Protection, AES, column encryption, PBKDF2) was found — sensitive data at rest may be unprotected. If TDE/KMS/vault is delegated to infrastructure, ignore.
What to do
- Encrypt sensitive data at rest (ASP.NET Core Data Protection / column encryption) and manage keys in a vault. Skip if delegated to infra (Postgres TDE, KMS, etc.).
C2 · Access Controls
- No [Authorize]/policies and no imperative guard methods (throw-on-violation) were found — endpoints may be unprotected.
- `CommandController.HandleRegisterContractV2` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. — REDACTED:21
- `CommandController.ChangeContractAmount` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. — REDACTED:27
- `CommandController.ChangeContractTerm` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. — REDACTED:33
- `CommandController.CancelContract` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. — REDACTED:39
- `CommandController.HandleRegisterContract` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. — REDACTED:51
- `CommandController.AddDocument` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. — REDACTED:65
- `QueryController.GetContracts` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. (×2) — REDACTED:18, REDACTED:24
What to do
- Protect endpoints by default-deny: [Authorize] + role/policy authorization, or imperative guard methods (throw-on-violation) called from every handler.
DM1 · Aggregate boundaries
DM10 · One transaction, one aggregate
DM11 · Constructible invalid state
DM12 · Ambient inputs in the domain
- `Contract` reads `DateTime.Now` inside `EnsureValidTermForCancellation`. The rule this feeds is not a function of its inputs: it cannot be tested at the instant that matters without moving the machine clock, and two reads inside one operation can observe different times. Pass the instant in as a parameter, or inject `TimeProvider`. — src/ContractManagement/Domain/Aggregates/Contract/Contract.cs:245
What to do
- Pass the instant into the domain method that needs it, or inject `TimeProvider` (BCL, .NET 8+) and read it there — then a test can choose the moment a rule is evaluated at.
DM2 · Strongly-typed ids
- `Document.DocumentId` is a raw `String` — give it a strongly-typed id: a dedicated single-field type wrapping the `String`, in whatever form your language spells that. — src/ContractManagement/Domain/Aggregates/Portfolio/Document.cs:7
- `Document.PortfolioId` is a raw `String` — give it a strongly-typed id: a dedicated single-field type wrapping the `String`, in whatever form your language spells that. — src/ContractManagement/Domain/Aggregates/Portfolio/Document.cs:9
- `Portfolio.PortfolioId` is a raw `String` — give it a strongly-typed id: a dedicated single-field type wrapping the `String`, in whatever form your language spells that. — src/ContractManagement/Domain/Aggregates/Portfolio/Portfolio.cs:7
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
- `Contract` is an aggregate/entity with 8 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — src/ContractManagement/Domain/Aggregates/Contract/Contract.cs:3
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
- `AggregateRoot` exposes publicly writable state (Version). — src/Common/Domain.Common/Aggregate/AggregateRoot.cs:6
- `Document` exposes publicly writable state (DocumentId, PortfolioId, DocumentType, DocumentUrl). — src/ContractManagement/Domain/Aggregates/Portfolio/Document.cs:3
- `Portfolio` exposes publicly writable state (PortfolioId, Documents). — src/ContractManagement/Domain/Aggregates/Portfolio/Portfolio.cs:3
What to do
- Make entity setters private/init-only and hand collections out as IReadOnlyList/IReadOnlyCollection over a private backing field; change state only through methods that enforce the invariants (Marten/EF can bind via constructor or private setters).
DM6 · Domain ↔ infrastructure boundary
DM9 · Scattered domain decisions
ED1 · Handler temporal coupling
ED2 · Event/command shape
ED4 · Outbox / dual-write
GD1 · Unfinished & placeholder code
IC1 · Incompleteness & stubs
- `SendContract` looks like it should compute a result but its body just returns a constant — a placeholder return that was never filled in. — REDACTED:12
- A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers). — src/ContractManagement/Domain/Aggregates/Contract/Contract.cs:153
- A placeholder value ("John Doe") is still in shipped code — sample/mock data that was never replaced with the real thing. — src/ContractManagement/Infrastructure/Persistence/EFCore/ReadModel/Configurations/CustomerConfiguration.cs:37
- A placeholder e-mail address ("jd@example.com") is still in shipped code — its domain is reserved for documentation, so anything sent here is undeliverable by construction. Replace it with the real address, or take it from configuration. (×2) — src/ContractManagement/Infrastructure/Persistence/EFCore/ReadModel/Configurations/CustomerConfiguration.cs:39, src/OutputManagement/OutputManagementService/Repositories/InMemoryCustomerRepository.cs:14
- A placeholder e-mail address ("eric.dewitt@example.com") is still in shipped code — its domain is reserved for documentation, so anything sent here is undeliverable by construction. Replace it with the real address, or take it from configuration. (×2) — src/ContractManagement/Infrastructure/Persistence/EFCore/ReadModel/Configurations/CustomerConfiguration.cs:46, src/OutputManagement/OutputManagementService/Repositories/InMemoryCustomerRepository.cs:15
What to do
- Finish or delete the unfinished stubs (NotImplementedException / empty / constant-returning bodies) — they are dead surface that looks live.
- Clear the softer debt: remove commented-out code and dead branches, re-enable or delete skipped tests, and replace blanket warning suppressions with targeted ones.
M1 · Documentation (README)
What to do
- Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
- Add a README to the 10 of 10 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.
- Only 3/11 projects share a common root namespace — the code's module identity is inconsistent.
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.
- Adopt a consistent root-namespace convention (a shared prefix, e.g. Acme.*); short project-file/directory names are fine as long as the RootNamespace is uniform.
M4 · Documentation accuracy
P1 · CI/CD gates
- No CI workflow found (.github/workflows, azure-pipelines.yml, .gitlab-ci.yml, …) — changes aren't gated by an automated build/test.
What to do
- Add a CI workflow that builds and runs the test suite on every push/PR.
P2 · Observability
- `src/!Support/MessageSender/MessageSender.cs` reports through `Console.Write…` at line 31 although other files in its project log through a logger. Console lines carry no level, category or structured properties and never reach the log pipeline or its exporters. — src/!Support/MessageSender/MessageSender.cs:31
- `src/!Support/MessageSender/MessageSender.cs` reports through `Console.Write…` at line 38 although other files in its project log through a logger. Console lines carry no level, category or structured properties and never reach the log pipeline or its exporters. — src/!Support/MessageSender/MessageSender.cs:38
- `src/!Support/MessageSender/MessageSender.cs` reports through `Console.Write…` at line 39 although other files in its project log through a logger. Console lines carry no level, category or structured properties and never reach the log pipeline or its exporters. — src/!Support/MessageSender/MessageSender.cs:39
- `src/!Support/MessageSender/MessageSender.cs` reports through `Console.Write…` at line 40 although other files in its project log through a logger. Console lines carry no level, category or structured properties and never reach the log pipeline or its exporters. — src/!Support/MessageSender/MessageSender.cs:40
- `src/!Support/MessageSender/MessageSender.cs` reports through `Console.Write…` at line 41 although other files in its project log through a logger. Console lines carry no level, category or structured properties and never reach the log pipeline or its exporters. — src/!Support/MessageSender/MessageSender.cs:41
- `src/!Support/MessageSender/MessageSender.cs` reports through `Console.Write…` at line 42 although other files in its project log through a logger. Console lines carry no level, category or structured properties and never reach the log pipeline or its exporters. — src/!Support/MessageSender/MessageSender.cs:42
- `src/!Support/MessageSender/MessageSender.cs` reports through `Console.Write…` at line 43 although other files in its project log through a logger. Console lines carry no level, category or structured properties and never reach the log pipeline or its exporters. — src/!Support/MessageSender/MessageSender.cs:43
- `src/!Support/MessageSender/MessageSender.cs` reports through `Console.Write…` at line 44 although other files in its project log through a logger. Console lines carry no level, category or structured properties and never reach the log pipeline or its exporters. — src/!Support/MessageSender/MessageSender.cs:44
- `src/!Support/MessageSender/MessageSender.cs` reports through `Console.Write…` at line 45 although other files in its project log through a logger. Console lines carry no level, category or structured properties and never reach the log pipeline or its exporters. — src/!Support/MessageSender/MessageSender.cs:45
- `src/!Support/MessageSender/MessageSender.cs` reports through `Console.Write…` at line 46 although other files in its project log through a logger. Console lines carry no level, category or structured properties and never reach the log pipeline or its exporters. — src/!Support/MessageSender/MessageSender.cs:46
- `src/!Support/MessageSender/MessageSender.cs` reports through `Console.Write…` at line 47 although other files in its project log through a logger. Console lines carry no level, category or structured properties and never reach the log pipeline or its exporters. — src/!Support/MessageSender/MessageSender.cs:47
- `src/!Support/MessageSender/MessageSender.cs` reports through `Console.Write…` at line 48 although other files in its project log through a logger. Console lines carry no level, category or structured properties and never reach the log pipeline or its exporters. — src/!Support/MessageSender/MessageSender.cs:48
- `src/!Support/MessageSender/MessageSender.cs` reports through `Console.Write…` at line 49 although other files in its project log through a logger. Console lines carry no level, category or structured properties and never reach the log pipeline or its exporters. — src/!Support/MessageSender/MessageSender.cs:49
- `src/!Support/MessageSender/MessageSender.cs` reports through `Console.Write…` at line 50 although other files in its project log through a logger. Console lines carry no level, category or structured properties and never reach the log pipeline or its exporters. — src/!Support/MessageSender/MessageSender.cs:50
- `src/!Support/MessageSender/MessageSender.cs` reports through `Console.Write…` at line 51 although other files in its project log through a logger. Console lines carry no level, category or structured properties and never reach the log pipeline or its exporters. — src/!Support/MessageSender/MessageSender.cs:51
- `src/!Support/MessageSender/MessageSender.cs` reports through `Console.Write…` at line 89 although other files in its project log through a logger. Console lines carry no level, category or structured properties and never reach the log pipeline or its exporters. — src/!Support/MessageSender/MessageSender.cs:89
- `src/!Support/MessageSender/MessageSender.cs` reports through `Console.Write…` at line 93 although other files in its project log through a logger. Console lines carry no level, category or structured properties and never reach the log pipeline or its exporters. — src/!Support/MessageSender/MessageSender.cs:93
- `src/!Support/MessageSender/MessageSender.cs` reports through `Console.Write…` at line 100 although other files in its project log through a logger. Console lines carry no level, category or structured properties and never reach the log pipeline or its exporters. — src/!Support/MessageSender/MessageSender.cs:100
- `src/!Support/MessageSender/MessageSender.cs` reports through `Console.Write…` at line 101 although other files in its project log through a logger. Console lines carry no level, category or structured properties and never reach the log pipeline or its exporters. — src/!Support/MessageSender/MessageSender.cs:101
- `src/!Support/MessageSender/MessageSender.cs` reports through `Console.Write…` at line 102 although other files in its project log through a logger. Console lines carry no level, category or structured properties and never reach the log pipeline or its exporters. — src/!Support/MessageSender/MessageSender.cs:102
- `src/!Support/MessageSender/MessageSender.cs` reports through `Console.Write…` at line 108 although other files in its project log through a logger. Console lines carry no level, category or structured properties and never reach the log pipeline or its exporters. — src/!Support/MessageSender/MessageSender.cs:108
- `src/!Support/MessageSender/MessageSender.cs` reports through `Console.Write…` at line 113 although other files in its project log through a logger. Console lines carry no level, category or structured properties and never reach the log pipeline or its exporters. — src/!Support/MessageSender/MessageSender.cs:113
- `src/!Support/MessageSender/MessageSender.cs` reports through `Console.Write…` at line 114 although other files in its project log through a logger. Console lines carry no level, category or structured properties and never reach the log pipeline or its exporters. — src/!Support/MessageSender/MessageSender.cs:114
- `src/!Support/MessageSender/MessageSender.cs` reports through `Console.Write…` at line 115 although other files in its project log through a logger. Console lines carry no level, category or structured properties and never reach the log pipeline or its exporters. — src/!Support/MessageSender/MessageSender.cs:115
- `src/!Support/MessageSender/MessageSender.cs` reports through `Console.Write…` at line 117 although other files in its project log through a logger. Console lines carry no level, category or structured properties and never reach the log pipeline or its exporters. — src/!Support/MessageSender/MessageSender.cs:117
- `src/!Support/MessageSender/MessageSender.cs` reports through `Console.Write…` at line 119 although other files in its project log through a logger. Console lines carry no level, category or structured properties and never reach the log pipeline or its exporters. — src/!Support/MessageSender/MessageSender.cs:119
- `src/!Support/MessageSender/MessageSender.cs` reports through `Console.Write…` at line 121 although other files in its project log through a logger. Console lines carry no level, category or structured properties and never reach the log pipeline or its exporters. — src/!Support/MessageSender/MessageSender.cs:121
- `src/!Support/MessageSender/MessageSender.cs` reports through `Console.Write…` at line 123 although other files in its project log through a logger. Console lines carry no level, category or structured properties and never reach the log pipeline or its exporters. — src/!Support/MessageSender/MessageSender.cs:123
- `src/!Support/MessageSender/MessageSender.cs` reports through `Console.Write…` at line 126 although other files in its project log through a logger. Console lines carry no level, category or structured properties and never reach the log pipeline or its exporters. — src/!Support/MessageSender/MessageSender.cs:126
- `src/!Support/MessageSender/MessageSender.cs` reports through `Console.Write…` at line 132 although other files in its project log through a logger. Console lines carry no level, category or structured properties and never reach the log pipeline or its exporters. — src/!Support/MessageSender/MessageSender.cs:132
- `src/!Support/MessageSender/MessageSender.cs` reports through `Console.Write…` at line 137 although other files in its project log through a logger. Console lines carry no level, category or structured properties and never reach the log pipeline or its exporters. — src/!Support/MessageSender/MessageSender.cs:137
- `src/!Support/MessageSender/MessageSender.cs` reports through `Console.Write…` at line 138 although other files in its project log through a logger. Console lines carry no level, category or structured properties and never reach the log pipeline or its exporters. — src/!Support/MessageSender/MessageSender.cs:138
- `src/!Support/MessageSender/MessageSender.cs` reports through `Console.Write…` at line 139 although other files in its project log through a logger. Console lines carry no level, category or structured properties and never reach the log pipeline or its exporters. — src/!Support/MessageSender/MessageSender.cs:139
- `src/!Support/MessageSender/MessageSender.cs` reports through `Console.Write…` at line 141 although other files in its project log through a logger. Console lines carry no level, category or structured properties and never reach the log pipeline or its exporters. — src/!Support/MessageSender/MessageSender.cs:141
- `src/!Support/MessageSender/MessageSender.cs` reports through `Console.Write…` at line 144 although other files in its project log through a logger. Console lines carry no level, category or structured properties and never reach the log pipeline or its exporters. — src/!Support/MessageSender/MessageSender.cs:144
- `src/!Support/MessageSender/MessageSender.cs` reports through `Console.Write…` at line 150 although other files in its project log through a logger. Console lines carry no level, category or structured properties and never reach the log pipeline or its exporters. — src/!Support/MessageSender/MessageSender.cs:150
- `src/!Support/MessageSender/MessageSender.cs` reports through `Console.Write…` at line 155 although other files in its project log through a logger. Console lines carry no level, category or structured properties and never reach the log pipeline or its exporters. — src/!Support/MessageSender/MessageSender.cs:155
- `src/!Support/MessageSender/MessageSender.cs` reports through `Console.Write…` at line 156 although other files in its project log through a logger. Console lines carry no level, category or structured properties and never reach the log pipeline or its exporters. — src/!Support/MessageSender/MessageSender.cs:156
- `src/!Support/MessageSender/MessageSender.cs` reports through `Console.Write…` at line 157 although other files in its project log through a logger. Console lines carry no level, category or structured properties and never reach the log pipeline or its exporters. — src/!Support/MessageSender/MessageSender.cs:157
- `src/!Support/MessageSender/MessageSender.cs` reports through `Console.Write…` at line 159 although other files in its project log through a logger. Console lines carry no level, category or structured properties and never reach the log pipeline or its exporters. — src/!Support/MessageSender/MessageSender.cs:159
What to do
- Replace `Console.Write…` in service code with the project's injected `ILogger<T>` (message templates with named properties), so delivery outcomes and failures reach the log pipeline with a level and a category.
- Consider OpenTelemetry tracing/metrics and a health-check endpoint for operability.
P3 · Security & performance tooling
- No static application security testing detected. For this repository's stack, add CodeQL's csharp pack, or a .NET security analyzer package (or `semgrep --config=auto`, which runs on any language) — this repository has no CI pipeline yet, so run it locally to clear the existing findings, then make it a step of the first workflow you add so a regression fails the build. What was searched, so you can tell an absence from a miss: the 0 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.
- `src/Directory.Packages.props` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`. — src/Directory.Packages.props:3
What to do
- Run what this repository's stack ships: CodeQL's csharp pack, or a .NET security analyzer package — or `semgrep --config=auto`, which runs on any language — locally for now, since there is no CI pipeline here yet, and as a step of the first workflow you add so a security regression fails the build instead of landing.
- Enable Dependabot/Renovate or a dependency-review gate.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P7 · Outbound HTTP resilience
- `new HttpClient()` builds an outbound HTTP client and nothing bounds it: no timeout is set on it and no retry or resilience policy wraps its calls in the type that owns it. A slow or failing dependency will hold this service's request, thread or connection — and cascade — until the call gives up on its own (100 s for HttpClient's default). — src/!Support/MessageSender/MessageSender.cs:250
What to do
- Add `AddStandardResilienceHandler()` (or a Polly policy and an explicit timeout) to each client registration flagged here, so a flaky dependency can't take the app down.
P8 · Schema migrations
PF1 · Benchmark discipline
- No benchmark suite was found by the two searches this check runs. FIRST, a BenchmarkDotNet package reference in any project file — every project the workspace loaded, plus a walk of project files on disk that never loaded, because a benchmark suite is exactly the project a partial load drops. SECOND, a script harness: a file whose name contains `benchmark` and ends `.py`, `.sh`, `.ps1`, `.bash`, `.rb`, `.js` or `.mjs`, credited ONLY when this repository's CI text also mentions benchmarks — a harness no pipeline runs is read as a fixture, deliberately. Neither search can see a benchmark suite in another ecosystem's idiom (a Go `testing.B` file, a JMH or criterion project, a pytest-benchmark run), so this is 'no benchmark found by those two searches', not a verdict that the repository has none. Where code is performance-sensitive, a benchmark guards against silent regressions — but it's a bonus here, not a deduction.
What to do
- Add a benchmarking harness for the hot paths and run it in CI to catch regressions (for .NET, a BenchmarkDotNet project with [MemoryDiagnoser] to track allocations).
PF3 · Async & latency hygiene
S1 · Web-Security Posture
- None of the 11 security response headers the OWASP Secure Headers Project recommends (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options, …) is configured — defense in depth, even when a reverse proxy could set them. (−2.0 on this card.)
- This web host's pipeline is composed here and adds no security response header (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, a frame policy) to what it serves. — src/ContractManagement/Interface/WebAPI/Program.cs:4
What to do
- Add security response headers (Content-Security-Policy first, then Strict-Transport-Security, X-Content-Type-Options and a frame policy) — defense in depth, even when a reverse proxy could set them.
X1 · Async correctness
- Reading `.Result` of a task that has not completed blocks this thread until it does — the same block as `.Wait()`: under a synchronization context (Blazor, a UI thread, classic ASP.NET) it deadlocks, and on the thread pool it parks a thread for as long as the work runs. `await` the task instead (make the caller `async`); where a synchronous entry point must stay, keep the block in ONE documented bridge with a timeout. — src/!Support/MessageSender/MessageSender.cs:255
What to do
- Sync-over-async (deadlock risk) through `.Result`
X12 · Unreachable branch
X13 · Undrained process stream
X14 · Bypassable address classification
X15 · Unvalidated length from an untrusted reader
X16 · Unfloored truncation loop
X17 · Uncapped recursion over a caller-supplied document
X18 · Disposal-pattern correctness
X19 · Unrestored process-global state
X2 · Cancellation propagation
- Only 1/56 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. (×39) — src/Common/Application.Common/Services/AggregateService.cs:28, src/Common/Application.Common/Services/AggregateService.cs:41, src/Common/Application.Common/Services/AggregateService.cs:59, …
What to do
- Thread a CancellationToken through async methods so work stops promptly on cancellation.
X20 · Mistyped argument guard
X21 · Side-effecting pattern guard
X22 · Contradicted release guard
X23 · Unguarded diagnostic materialisation
X24 · Document value interpolated into markup unescaped
X25 · Inert configuration knob
X26 · Unsynchronised callback handoff
X27 · Collection changed while being enumerated
X28 · Index access outside its own emptiness guard
X29 · Per-element action decided by a fixed element
X3 · Exception handling
X30 · Support guard that admits what it rejects
X32 · Type resolved by simple name across every loaded assembly
X4 · Structured logging
- Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it. (×2) — src/OutputManagement/OutputManagementService/Consumers/DayHasPassedConsumer.cs:36, src/OutputManagement/OutputManagementService/Consumers/DayHasPassedConsumer.cs:45
What to do
- Interpolated log message defeats structured logging
X5 · Nullable reference types
- ~1.9 `!` suppressions per 1k syntax nodes — 35 suppression(s) across the 18556 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 | 66% | Adequate | Acceptable, with room to improve. |
| Architecture | 80% | Strong | Solid. |
| Maturity | 60% | Adequate — gated by D34 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 34% | Weak — gated by P1, P3, P7 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 36% | Weak — gated by C1, C2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Domain Modelling | 70% | Adequate — gated by DM2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Event-Driven | 100% | Exemplary | Strongest area. |
| Performance | 77% | Strong | Solid. |
Not evidenced — 6 control(s) we could not find positive evidence for
- C3 Audit Trail — Repo shows no audit-logging mechanism (IAuditable, an immutable audit log, an EF SaveChanges interceptor) for sensitive changes — absence of evidence is not evidence of a working control. Record an audit trail in code (or document where it lives) so this dimension can be scored.
- C4 Data Retention — Repo shows no data-retention / TTL / cleanup mechanism for personal data (event-sourced storage — lifecycle is stream archival / event TTL, not row CASCADE) — absence of evidence is not evidence of a working control. Define retention periods and a purge/cleanup job (or TTL) in code, or document where retention is enforced, so this dimension can be scored.
- C5 Data-Subject Rights — Repo shows no corroborated data-subject-rights mechanism (erasure / export-portability / consent) tied to a subject id or GDPR vocabulary — absence of evidence is not evidence of a working control. Implement erasure, data export/portability and consent tracking over the subject's records.
- P4 Deployment & Rollback — not evidenced — no deploy/rollback/approval signal in the repo; absence of evidence is not evidence of a manual release
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
- P6 Release Hygiene — not evidenced — no changelog, version stamp or semver release tag in the repo
Not included — 39 check(s) not relevant to this codebase
- AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
- AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
- AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
- AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
- AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
- AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
- AC7 A11y enforcement — No web markup found — accessibility is not applicable to this repository.
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXR1 Runtime accessibility — the service did not build — `dotnet build 'WebAPI.csproj'` exited 1: ; runtime evidence skipped (launch chosen because src/ContractManagement/Interface/WebAPI/WebAPI.csproj is a Microsoft.NET.Sdk.Web project) This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
- D12 Dependency Hygiene — Dependency hygiene not measured
- D16 Bus Factor — single-contributor repository — bus factor is not applicable
- D22 Internal API Consistency — No intentionally-exposed public API to evaluate for consistency.
- D23 Boundary Type-Coupling — small single-context codebase (3,532 production LoC in the .NET projects) — bounded contexts are not needed at this size No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- 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 — No CI/build pipeline found (.github/.forgejo/.gitea workflows, .circleci, .buildkite, .woodpecker, .teamcity, .gitlab-ci.yml, .travis.yml, bitbucket-pipelines.yml, .drone.yml, .cirrus.yml, .woodpecker.yml, appveyor.yml, azure-pipelines*.yml, .pipelines/, .vsts-ci/, .azuredevops/, Jenkinsfile); there is no build to attest provenance for.
- 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.
- 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)
- ED3 Event naming — no domain or integration events detected — event-naming check not applicable
- ED5 Idempotency — not scored — 8 of 11 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 only 1 of the 3 signals this lens looks for (4 projection(s))
- P12 CI test-gate honesty — no CI workflow found
- P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (Cobertura — `dotnet test --collect:"XPlat Code Coverage"` with a `coverlet.collector` PackageReference) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures, or wire coverage collection into CI, to enable this cross-layer check
- PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
- SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X10 Duplicated predicate — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X7 Silent fallback defaults — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
Critical — 12 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- WriteOnlyPrivateField src/Common/Application.Common/Services/AggregateService.cs:10
- WriteOnlyPrivateField src/Common/Application.Common/Services/AggregateService.cs:12
- WriteOnlyPrivateField REDACTED:8
- REDACTED
Serious — 96 finding(s)
- Async method without CancellationToken: RehydrateAsync src/Common/Application.Common/Services/AggregateService.cs:28
- Async method without CancellationToken: TryRehydrateAsync src/Common/Application.Common/Services/AggregateService.cs:41
- Async method without CancellationToken: ProcessChangesAsync src/Common/Application.Common/Services/AggregateService.cs:59
- Async method without CancellationToken: PublishDomainEventsAsync REDACTED:16
- Async method without CancellationToken: PublishIntegrationEventsAsync REDACTED:24
- Async method without CancellationToken: PublishDomainEventAsync REDACTED:32
- Async method without CancellationToken: PublishIntegrationEventAsync REDACTED:43
- Async method without CancellationToken: GetAggregateAsync src/Common/Infrastructure.Common/Persistence/EFCore/WriteModel/EventSourced/EFEventSourcedAggregateRepository.cs:25
- Async method without CancellationToken: UpdateAggregateAsync src/Common/Infrastructure.Common/Persistence/EFCore/WriteModel/EventSourced/EFEventSourcedAggregateRepository.cs:54
- Async method without CancellationToken: UpdateAggregateEntityAsync src/Common/Infrastructure.Common/Persistence/EFCore/WriteModel/EventSourced/EFEventSourcedAggregateRepository.cs:79
- Async method without CancellationToken: GetAggregateAsync src/Common/Infrastructure.Common/Persistence/EFCore/WriteModel/Relational/EFAggregateRepository.cs:15
- Async method without CancellationToken: CommitAsync src/Common/Infrastructure.Common/UnitOfWork/PersistenceAndMessagingUnitOfWork.cs:40
- Async method without CancellationToken: HandleAsync src/ContractManagement/Application/Features/ContractCancellation/CancelContractHandler.cs:12
- Async method without CancellationToken: ProjectAsync src/ContractManagement/Application/Features/ContractCancellation/ContractCancelledProjection.cs:12
- Async method without CancellationToken: HandleAsync src/ContractManagement/Application/Features/ContractMaintenance/ChangeContractAmountFeature.cs:25
- Async method without CancellationToken: HandleAsync src/ContractManagement/Application/Features/ContractMaintenance/ChangeContractAmountFeature.cs:32
- Async method without CancellationToken: ProjectAsync src/ContractManagement/Application/Features/ContractMaintenance/ChangeContractAmountFeature.cs:39
- Async method without CancellationToken: HandleAsync src/ContractManagement/Application/Features/ContractMaintenance/ChangeContractTermFeature.cs:25
- Async method without CancellationToken: HandleAsync src/ContractManagement/Application/Features/ContractMaintenance/ChangeContractTermFeature.cs:32
- Async method without CancellationToken: ProjectAsync src/ContractManagement/Application/Features/ContractMaintenance/ChangeContractTermFeature.cs:39
- Async method without CancellationToken: HandleAsync src/ContractManagement/Application/Features/ContractRegistration/ContractRegisteredHandler.cs:17
- Async method without CancellationToken: ProjectAsync src/ContractManagement/Application/Features/ContractRegistration/ContractRegisteredProjection.cs:16
- Async method without CancellationToken: ProjectAsync src/ContractManagement/Application/Features/ContractRegistration/ContractRegisteredProjection.cs:22
- Async method without CancellationToken: HandleAsync src/ContractManagement/Application/Features/ContractRegistration/RegisterContractHandler.cs:19
- Async method without CancellationToken: HandleAsync src/ContractManagement/Application/Features/Documents/AddDocumentHandler.cs:12
- Dead code: PublishDomainEventsAsync src/Common/Application.Common/Interfaces/IEventPublisher.cs:7
- Dead code: PublishIntegrationEventsAsync src/Common/Application.Common/Interfaces/IEventPublisher.cs:11
- Dead code: AddDomainEventToPublish src/Common/Application.Common/Interfaces/IUnitOfWork.cs:5
- Dead code: AddIntegrationEventsToPublish src/Common/Application.Common/Interfaces/IUnitOfWork.cs:8
- Dead code: CancelContractHandler src/ContractManagement/Application/Features/ContractCancellation/CancelContractHandler.cs:3
- Dead code: ContractCancelledProjection src/ContractManagement/Application/Features/ContractCancellation/ContractCancelledProjection.cs:3
- Dead code: ContractRegisteredProjection src/ContractManagement/Application/Features/ContractRegistration/ContractRegisteredProjection.cs:5
- Dead code: RegisterContractHandler src/ContractManagement/Application/Features/ContractRegistration/RegisterContractHandler.cs:3
- Dead code: AddDocumentHandler src/ContractManagement/Application/Features/Documents/AddDocumentHandler.cs:3
- Dead code: CreatePortfolioHandler src/ContractManagement/Application/Features/Documents/CreatePortfolioHandler.cs:3
- Dead code: CeateFrom src/ContractManagement/Domain/Aggregates/Portfolio/DomainEvents/DocumentAdded.cs:5
- Dead code: CancelContract_Of_Cancelled_Contract_ShouldYieldViolation src/ContractManagement/Domain.UnitTests/Contract/ContractCancellationTests.cs:36
- Dead code: SQL_ERROR_KEY_CONSTRAINT_VIOLATION src/ContractManagement/Infrastructure/Persistence/EFCore/ServiceDbContext.cs:7
- End-of-life runtime: .NET net6.0 REDACTED:4
- End-of-life runtime: .NET net6.0 REDACTED:4
- End-of-life runtime: .NET net6.0 src/Common/Domain.Common/Domain.Common.csproj:4
- End-of-life runtime: .NET net6.0 REDACTED:4
- End-of-life runtime: .NET net6.0 src/ContractManagement/Application/Application.csproj:4
- End-of-life runtime: .NET net6.0 REDACTED:4
- End-of-life runtime: .NET net6.0 src/ContractManagement/Domain/Domain.csproj:4
- End-of-life runtime: .NET net6.0 src/ContractManagement/Infrastructure/Infrastructure.csproj:4
- End-of-life runtime: .NET net6.0 src/ContractManagement/Interface/MessageReceiver/MessageReceiver.csproj:4
- End-of-life runtime: .NET net6.0 src/ContractManagement/Interface/WebAPI/WebAPI.csproj:4
- End-of-life runtime: .NET net6.0 src/OutputManagement/OutputManagementService/OutputManagementService.csproj:4
- No authorization
- No authorization REDACTED:21
- No authorization REDACTED:27
- No authorization REDACTED:33
- No authorization REDACTED:39
- No authorization REDACTED:51
- No authorization REDACTED:65
- No authorization REDACTED:18
- No authorization REDACTED:24
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- TodoComment src/Common/Infrastructure.Common/UnitOfWork/PersistenceAndMessagingUnitOfWork.cs:50
- TodoComment src/ContractManagement/Infrastructure/DependencyInjection/IServiceCollectionExtensions.cs:13
- TodoComment src/ContractManagement/Infrastructure/DependencyInjection/IServiceCollectionExtensions.cs:41
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Stateful singleton: BusObserver src/!Support/MessageSender/BusObserver.cs:3
- No data-protection/encryption
- REDACTED
- Domain type reads the wall clock: Contract src/ContractManagement/Domain/Aggregates/Contract/Contract.cs:245
- Anemic entity: Contract src/ContractManagement/Domain/Aggregates/Contract/Contract.cs:3
- Hollow method — returns a constant without doing the work REDACTED:12
- No CI pipeline
- Outbound HTTP without resilience src/!Support/MessageSender/MessageSender.cs:250
- Sync-over-async (deadlock risk) through `.Result` src/!Support/MessageSender/MessageSender.cs:255
Minor — 84 finding(s)
- Console output used as the logging channel src/!Support/MessageSender/MessageSender.cs:31
- Console output used as the logging channel src/!Support/MessageSender/MessageSender.cs:38
- Console output used as the logging channel src/!Support/MessageSender/MessageSender.cs:39
- Console output used as the logging channel src/!Support/MessageSender/MessageSender.cs:40
- Console output used as the logging channel src/!Support/MessageSender/MessageSender.cs:41
- Console output used as the logging channel src/!Support/MessageSender/MessageSender.cs:42
- Console output used as the logging channel src/!Support/MessageSender/MessageSender.cs:43
- Console output used as the logging channel src/!Support/MessageSender/MessageSender.cs:44
- Console output used as the logging channel src/!Support/MessageSender/MessageSender.cs:45
- Console output used as the logging channel src/!Support/MessageSender/MessageSender.cs:46
- Console output used as the logging channel src/!Support/MessageSender/MessageSender.cs:47
- Console output used as the logging channel src/!Support/MessageSender/MessageSender.cs:48
- Console output used as the logging channel src/!Support/MessageSender/MessageSender.cs:49
- Console output used as the logging channel src/!Support/MessageSender/MessageSender.cs:50
- Console output used as the logging channel src/!Support/MessageSender/MessageSender.cs:51
- Console output used as the logging channel src/!Support/MessageSender/MessageSender.cs:89
- Console output used as the logging channel src/!Support/MessageSender/MessageSender.cs:93
- Console output used as the logging channel src/!Support/MessageSender/MessageSender.cs:100
- Console output used as the logging channel src/!Support/MessageSender/MessageSender.cs:101
- Console output used as the logging channel src/!Support/MessageSender/MessageSender.cs:102
- Console output used as the logging channel src/!Support/MessageSender/MessageSender.cs:108
- Console output used as the logging channel src/!Support/MessageSender/MessageSender.cs:113
- Console output used as the logging channel src/!Support/MessageSender/MessageSender.cs:114
- Console output used as the logging channel src/!Support/MessageSender/MessageSender.cs:115
- Console output used as the logging channel src/!Support/MessageSender/MessageSender.cs:117
- Orphaned file src/!Support/MessageSender/MessageSender.cs:1
- Orphaned file src/ContractManagement/Domain/Aggregates/Contract/Contract.cs:1
- Orphaned file src/Common/Infrastructure.Common/Persistence/EFCore/WriteModel/EventSourced/EFEventSourcedAggregateRepository.cs:1
- Orphaned file src/ContractManagement/Infrastructure/DependencyInjection/IServiceCollectionExtensions.cs:1
- Orphaned file src/Common/Domain.Common/Aggregate/AggregateRoot.cs:1
- Orphaned file src/OutputManagement/OutputManagementService/Repositories/InMemoryContractRepository.cs:1
- Orphaned file REDACTED:1
- Orphaned file src/Common/Application.Common/Services/AggregateService.cs:1
- Orphaned file src/Common/Application.Common/DependencyInjection/IServiceCollectionExtensions.cs:1
- Orphaned file src/OutputManagement/OutputManagementService/Consumers/DayHasPassedConsumer.cs:1
- redundant comment src/Common/Domain.Common/Aggregate/AggregateRoot.cs:108
- redundant comment src/ContractManagement/Application/Features/ContractRegistration/ContractRegisteredHandler.cs:19
- redundant comment src/ContractManagement/Interface/WebAPI/Program.cs:12
- redundant comment src/ContractManagement/Interface/WebAPI/Program.cs:31
- redundant comment src/ContractManagement/Interface/WebAPI/Program.cs:51
- redundant comment src/OutputManagement/OutputManagementService/Consumers/DayHasPassedConsumer.cs:56
- Placeholder data left in code src/ContractManagement/Infrastructure/Persistence/EFCore/ReadModel/Configurations/CustomerConfiguration.cs:37
- Placeholder data left in code src/ContractManagement/Infrastructure/Persistence/EFCore/ReadModel/Configurations/CustomerConfiguration.cs:39
- Placeholder data left in code src/ContractManagement/Infrastructure/Persistence/EFCore/ReadModel/Configurations/CustomerConfiguration.cs:46
- Placeholder data left in code src/OutputManagement/OutputManagementService/Repositories/InMemoryCustomerRepository.cs:14
- Placeholder data left in code src/OutputManagement/OutputManagementService/Repositories/InMemoryCustomerRepository.cs:15
- Primitive id on a domain type: Document.DocumentId src/ContractManagement/Domain/Aggregates/Portfolio/Document.cs:7
- Primitive id on a domain type: Document.PortfolioId src/ContractManagement/Domain/Aggregates/Portfolio/Document.cs:9
- Primitive id on a domain type: Portfolio.PortfolioId src/ContractManagement/Domain/Aggregates/Portfolio/Portfolio.cs:7
- Mutable entity: AggregateRoot src/Common/Domain.Common/Aggregate/AggregateRoot.cs:6
- Mutable entity: Document src/ContractManagement/Domain/Aggregates/Portfolio/Document.cs:3
- Mutable entity: Portfolio src/ContractManagement/Domain/Aggregates/Portfolio/Portfolio.cs:3
- No security response headers detected
- No security response headers detected src/ContractManagement/Interface/WebAPI/Program.cs:4
- Interpolated log message defeats structured logging src/OutputManagement/OutputManagementService/Consumers/DayHasPassedConsumer.cs:36
- Interpolated log message defeats structured logging src/OutputManagement/OutputManagementService/Consumers/DayHasPassedConsumer.cs:45
- ObsoleteWithoutCallers REDACTED:49
- Documentation: no build, run or usage example README.md:1
- No ADRs found
- Orphaned files with no living knowledge
- Commented-out code src/ContractManagement/Domain/Aggregates/Contract/Contract.cs:153
- No ADRs
- No tests/ separation
- Inconsistent root namespaces
- No SAST
- No dependency-update automation src/Directory.Packages.props:3
- No performance benchmarks
- Not all async methods take a CancellationToken
- Null-forgiving operator (`!`) suppressions reduce the NRT score
Minor — 1 finding(s)
- Mock framework: Moq
Appendix B — Reproduction & audit trail
| Dimension | Tool | Version | Command | Findings | Raw output |
|---|---|---|---|---|---|
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-dad3c016886d4fc2a80d7786ca4c3cb6/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-dad3c016886d4fc2a80d7786ca4c3cb6/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/ContractManagement/Infrastructure/Persistence/EFCore/Migrations . | 8 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | dotnet | — | dotnet list src/CloudNativeNet.sln package --vulnerable --include-transitive --format json | 11 | 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/ContractManagement/Infrastructure/Persistence/EFCore/Migrations . | 3 | artifacts/raw/semgrep-gdpr.json |
| D36 · Supply-chain Provenance & Signing | provenance | — | provenance: not applicable — No CI/build pipeline found (.github/.forgejo/.gitea workflows, .circleci, .buildkite, .woodpecker, .teamcity, .gitlab-ci.yml, .travis.yml, bitbucket-pipelines.yml, .drone.yml, .cirrus.yml, .woodpecker.yml, appveyor.yml, azure-pipelines*.yml, .pipelines/, .vsts-ci/, .azuredevops/, Jenkinsfile); there is no build to attest provenance for. | 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-a74e04d33fd6458a826c29c9febd6f3b | 0 | artifacts/raw/osv-scanner.json |
Appendix C — Personal-data map
Email — 6 field(s)
- CustomerRegistered.Email src/!Support/MessageSender/IntegrationEvents/CustomerManagement/CustomerRegistered.cs:9
- CustomerRegistered.Email src/ContractManagement/Application/Integration/CustomerManagement/CustomerRegistered.cs:8
- Customer.EmailAddress src/ContractManagement/Application/ReadModels/Customer.cs:8
- ContractInfo.CustomerEmail src/OutputManagement/OutputManagementService/EmailService/ContractInfo.cs:7
- CustomerRegistered.Email src/OutputManagement/OutputManagementService/IntegrationEvents/CustomerManagement/CustomerRegistered.cs:6
- Customer.EmailAddress src/OutputManagement/OutputManagementService/ReadModels/Customer.cs:5
Name — 4 field(s)
- CustomerRegistered.FirstName src/!Support/MessageSender/IntegrationEvents/CustomerManagement/CustomerRegistered.cs:6
- CustomerRegistered.LastName src/!Support/MessageSender/IntegrationEvents/CustomerManagement/CustomerRegistered.cs:7
- CustomerRegistered.FirstName src/ContractManagement/Application/Integration/CustomerManagement/CustomerRegistered.cs:5
- CustomerRegistered.LastName src/ContractManagement/Application/Integration/CustomerManagement/CustomerRegistered.cs:6