Executive summary
iblazhko/cqrs-fsharp falls short of our standard for production, in part because we found no automated security scanning of the code, its secrets or its dependencies. It scores 58 out of 100 and is rated Adequate, and all 13 of its critical findings are security problems.
Production Readiness, at 35, is the weakest lens and counts most in the score. The best first step is documenting the recovery plan, worth about 7 points. Adding tests for untested code comes next, worth about 6 points. Raising Production Readiness to 70 would lift the score to about 74.
Five passwords or keys are open to anyone who can read the repository. Three pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with, and three settings leave the servers or containers unsafe. Replacing each exposed password or key, pinning each tool to an exact version and correcting the unsafe settings would close these risks. Passing outside input through environment variables would fix the pipeline step that puts outside input straight into a shell command, and the pipeline step that runs a download without checking it needs each download checked against a known checksum first.
The product code is 3,266 lines, about €6,600 to rebuild.
If Production Readiness rose from 35 to 70, the lowest score rated Strong, the score would rise from 58 to about 74.
Fixed since the last survey: 1 finding
- Boundary Type-Coupling · Cross-context type InventoryId (CQRS.Domain → CQRS.Projections) src/CQRS.Projections/InventoryProjectionDocumentId.fs
Rebuild cost: about €6,600 · Estimate
| Cost to rebuild | €2,200 to €11,000, for 37 to 116 hours of work, under 0.1 person-years for one engineer |
|---|---|
| Difficulty of the problem | High, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.8 at a score of 58. 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,266 lines of product code |
| What it is not | Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one. |
Top priorities
Diagnosis: what the measurements show together
Architecture — module dependency graph
Architecture: which parts of the code depend on which
| uses → | 1 API | 2 CLI.Settings | 3 Configuration | 4 DTO | 5 Domain.Moon | 6 EntityIds | 7 Infrastructure | 8 Ports.Messaging | 9 Ports.ProjectionStore | 10 Projections | 11 API.AcceptedResponseModule | 12 Application.CommandProcessingStatusRecording | 13 DTO.V1 | 14 Domain.ValueTypes | 15 Projections.Repositories.InventoryViewModelQueryRepository | 16 API.MessageBusHandlers | 17 API.ProjectionHandlers | 18 Application.CommandProcessingStatusRecording.GetCommandProcessingStatusQueryRepository | 19 Domain.Inventory | 20 Domain.ValueTypes.ServiceIdModule | 21 Projections.WolverineConsumers | 22 API.ApiHandlers | 23 Application | 24 Domain.Inventory.InventoryIdModule | 25 Domain.Inventory.InventoryNameModule | 26 Domain.Inventory.StockQuantityModule | 27 Domain.InventoryAggregate | 28 Mapping.AddItemsToInventory' | 29 Mapping.CreateInventory' | 30 Mapping.DeactivateInventory' | 31 Mapping.InventoryCommand' | 32 Mapping.InventoryCreated' | 33 Mapping.InventoryDeactivated' | 34 Mapping.InventoryEvent' | 35 Mapping.InventoryRenamed' | 36 Projections.InventoryViewModelProjection | 37 API.ApiHandlers.CommandApiHandlers | 38 API.ApiHandlers.QueryApiHandlers | 39 Application.InventoryCommandDtoHandler | 40 Application.WolverineConsumers |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 API | ||||||||||||||||||||||||||||||||||||||||
| 2 CLI.Settings | ||||||||||||||||||||||||||||||||||||||||
| 3 Configuration | ||||||||||||||||||||||||||||||||||||||||
| 4 DTO | ||||||||||||||||||||||||||||||||||||||||
| 5 Domain.Moon | ||||||||||||||||||||||||||||||||||||||||
| 6 EntityIds | ||||||||||||||||||||||||||||||||||||||||
| 7 Infrastructure | ||||||||||||||||||||||||||||||||||||||||
| 8 Ports.Messaging | ||||||||||||||||||||||||||||||||||||||||
| 9 Ports.ProjectionStore | ||||||||||||||||||||||||||||||||||||||||
| 10 Projections | ||||||||||||||||||||||||||||||||||||||||
| 11 API.AcceptedResponseModule | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 12 Application.CommandProcessingStatusRecording | 1 | |||||||||||||||||||||||||||||||||||||||
| 13 DTO.V1 | 13 | |||||||||||||||||||||||||||||||||||||||
| 14 Domain.ValueTypes | 1 | |||||||||||||||||||||||||||||||||||||||
| 15 Projections.Repositories.InventoryViewModelQueryRepository | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 16 API.MessageBusHandlers | 1 | 1 | 5 | |||||||||||||||||||||||||||||||||||||
| 17 API.ProjectionHandlers | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 18 Application.CommandProcessingStatusRecording.GetCommandProcessingStatusQueryRepository | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 19 Domain.Inventory | 1 | 6 | ||||||||||||||||||||||||||||||||||||||
| 20 Domain.ValueTypes.ServiceIdModule | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 21 Projections.WolverineConsumers | 1 | 1 | 5 | |||||||||||||||||||||||||||||||||||||
| 22 API.ApiHandlers | 1 | 4 | 1 | |||||||||||||||||||||||||||||||||||||
| 23 Application | 2 | 1 | 1 | 4 | ||||||||||||||||||||||||||||||||||||
| 24 Domain.Inventory.InventoryIdModule | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 25 Domain.Inventory.InventoryNameModule | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 26 Domain.Inventory.StockQuantityModule | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 27 Domain.InventoryAggregate | 1 | 8 | ||||||||||||||||||||||||||||||||||||||
| 28 Mapping.AddItemsToInventory' | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 29 Mapping.CreateInventory' | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 30 Mapping.DeactivateInventory' | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 31 Mapping.InventoryCommand' | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 32 Mapping.InventoryCreated' | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 33 Mapping.InventoryDeactivated' | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 34 Mapping.InventoryEvent' | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 35 Mapping.InventoryRenamed' | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 36 Projections.InventoryViewModelProjection | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 37 API.ApiHandlers.CommandApiHandlers | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 38 API.ApiHandlers.QueryApiHandlers | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 39 Application.InventoryCommandDtoHandler | 9 | 4 | ||||||||||||||||||||||||||||||||||||||
| 40 Application.WolverineConsumers | 5 | 5 |
11→1 API.AcceptedResponseModule uses API✕
- Connections
- 1 pair of types, where a type in API.AcceptedResponseModule uses a type in API.
- The types involved
CQRS.API.AcceptedResponseModule.AcceptedResponseModule→CQRS.API.AcceptedResponse
- Direction
- API.AcceptedResponseModule uses API, so a change to API can break API.AcceptedResponseModule, while a change to API.AcceptedResponseModule can't break API.
- Position
- Below the diagonal: API.AcceptedResponseModule uses a module listed above it, which is the healthy direction.
11→8 API.AcceptedResponseModule uses Ports.Messaging✕
- Connections
- 1 pair of types, where a type in API.AcceptedResponseModule uses a type in Ports.Messaging.
- The types involved
CQRS.API.AcceptedResponseModule.AcceptedResponseModule→CQRS.Ports.Messaging.Context
- Direction
- API.AcceptedResponseModule uses Ports.Messaging, so a change to Ports.Messaging can break API.AcceptedResponseModule, while a change to API.AcceptedResponseModule can't break Ports.Messaging.
- Position
- Below the diagonal: API.AcceptedResponseModule uses a module listed above it, which is the healthy direction.
12→9 Application.CommandProcessingStatusRecording uses Ports.ProjectionStore✕
- Connections
- 1 pair of types, where a type in Application.CommandProcessingStatusRecording uses a type in Ports.ProjectionStore.
- The types involved
CQRS.Application.CommandProcessingStatusRecording.CommandProcessingStatusRecordingService→CQRS.Ports.ProjectionStore.IProjectionStore`1
- Direction
- Application.CommandProcessingStatusRecording uses Ports.ProjectionStore, so a change to Ports.ProjectionStore can break Application.CommandProcessingStatusRecording, while a change to Application.CommandProcessingStatusRecording can't break Ports.ProjectionStore.
- Position
- Below the diagonal: Application.CommandProcessingStatusRecording uses a module listed above it, which is the healthy direction.
13→4 DTO.V1 uses DTO✕
- Connections
- 13 pairs of types, where a type in DTO.V1 uses a type in DTO.
- The types involved
CQRS.DTO.V1.AddItemsToInventoryCommand→CQRS.DTO.CqrsCommandDtoCQRS.DTO.V1.CreateInventoryCommand→CQRS.DTO.CqrsCommandDtoCQRS.DTO.V1.DeactivateInventoryCommand→CQRS.DTO.CqrsCommandDtoCQRS.DTO.V1.Inventory→CQRS.DTO.CqrsStateDtoCQRS.DTO.V1.InventoryCreatedEvent→CQRS.DTO.CqrsEventDtoCQRS.DTO.V1.InventoryDeactivatedEvent→CQRS.DTO.CqrsEventDtoCQRS.DTO.V1.InventoryRenamedEvent→CQRS.DTO.CqrsEventDtoCQRS.DTO.V1.ItemInStockEvent→CQRS.DTO.CqrsEventDtoCQRS.DTO.V1.ItemWentOutOfStockEvent→CQRS.DTO.CqrsEventDtoCQRS.DTO.V1.ItemsAddedToInventoryEvent→CQRS.DTO.CqrsEventDtoCQRS.DTO.V1.ItemsRemovedFromInventoryEvent→CQRS.DTO.CqrsEventDtoCQRS.DTO.V1.RemoveItemsFromInventoryCommand→CQRS.DTO.CqrsCommandDtoCQRS.DTO.V1.RenameInventoryCommand→CQRS.DTO.CqrsCommandDto
- Direction
- DTO.V1 uses DTO, so a change to DTO can break DTO.V1, while a change to DTO.V1 can't break DTO.
- Position
- Below the diagonal: DTO.V1 uses a module listed above it, which is the healthy direction.
14→6 Domain.ValueTypes uses EntityIds✕
- Connections
- 1 pair of types, where a type in Domain.ValueTypes uses a type in EntityIds.
- The types involved
CQRS.Domain.ValueTypes.ServiceId→CQRS.EntityIds.EntityId
- Direction
- Domain.ValueTypes uses EntityIds, so a change to EntityIds can break Domain.ValueTypes, while a change to Domain.ValueTypes can't break EntityIds.
- Position
- Below the diagonal: Domain.ValueTypes uses a module listed above it, which is the healthy direction.
15→6 Projections.Repositories.InventoryViewModelQueryRepository uses EntityIds✕
- Connections
- 1 pair of types, where a type in Projections.Repositories.InventoryViewModelQueryRepository uses a type in EntityIds.
- The types involved
CQRS.Projections.Repositories.InventoryViewModelQueryRepository.InventoryViewModelQueryRepository→CQRS.EntityIds.EntityId
- Direction
- Projections.Repositories.InventoryViewModelQueryRepository uses EntityIds, so a change to EntityIds can break Projections.Repositories.InventoryViewModelQueryRepository, while a change to Projections.Repositories.InventoryViewModelQueryRepository can't break EntityIds.
- Position
- Below the diagonal: Projections.Repositories.InventoryViewModelQueryRepository uses a module listed above it, which is the healthy direction.
15→9 Projections.Repositories.InventoryViewModelQueryRepository uses Ports.ProjectionStore✕
- Connections
- 1 pair of types, where a type in Projections.Repositories.InventoryViewModelQueryRepository uses a type in Ports.ProjectionStore.
- The types involved
CQRS.Projections.Repositories.InventoryViewModelQueryRepository.InventoryViewModelQueryRepository→CQRS.Ports.ProjectionStore.IProjectionStore`1
- Direction
- Projections.Repositories.InventoryViewModelQueryRepository uses Ports.ProjectionStore, so a change to Ports.ProjectionStore can break Projections.Repositories.InventoryViewModelQueryRepository, while a change to Projections.Repositories.InventoryViewModelQueryRepository can't break Ports.ProjectionStore.
- Position
- Below the diagonal: Projections.Repositories.InventoryViewModelQueryRepository uses a module listed above it, which is the healthy direction.
15→10 Projections.Repositories.InventoryViewModelQueryRepository uses Projections✕
- Connections
- 1 pair of types, where a type in Projections.Repositories.InventoryViewModelQueryRepository uses a type in Projections.
- The types involved
CQRS.Projections.Repositories.InventoryViewModelQueryRepository.InventoryViewModelQueryRepository→CQRS.Projections.InventoryViewModel
- Direction
- Projections.Repositories.InventoryViewModelQueryRepository uses Projections, so a change to Projections can break Projections.Repositories.InventoryViewModelQueryRepository, while a change to Projections.Repositories.InventoryViewModelQueryRepository can't break Projections.
- Position
- Below the diagonal: Projections.Repositories.InventoryViewModelQueryRepository uses a module listed above it, which is the healthy direction.
16→1 API.MessageBusHandlers uses API✕
- Connections
- 1 pair of types, where a type in API.MessageBusHandlers uses a type in API.
- The types involved
CQRS.API.MessageBusHandlers.MessageBusHandlers→CQRS.API.AcceptedResponse
- Direction
- API.MessageBusHandlers uses API, so a change to API can break API.MessageBusHandlers, while a change to API.MessageBusHandlers can't break API.
- Position
- Below the diagonal: API.MessageBusHandlers uses a module listed above it, which is the healthy direction.
16→8 API.MessageBusHandlers uses Ports.Messaging✕
- Connections
- 1 pair of types, where a type in API.MessageBusHandlers uses a type in Ports.Messaging.
- The types involved
CQRS.API.MessageBusHandlers.MessageBusHandlers→CQRS.Ports.Messaging.IMessageBus
- Direction
- API.MessageBusHandlers uses Ports.Messaging, so a change to Ports.Messaging can break API.MessageBusHandlers, while a change to API.MessageBusHandlers can't break Ports.Messaging.
- Position
- Below the diagonal: API.MessageBusHandlers uses a module listed above it, which is the healthy direction.
16→13 API.MessageBusHandlers uses DTO.V1✕
- Connections
- 5 pairs of types, where a type in API.MessageBusHandlers uses a type in DTO.V1.
- The types involved
CQRS.API.MessageBusHandlers.MessageBusHandlers→CQRS.DTO.V1.AddItemsToInventoryCommandCQRS.API.MessageBusHandlers.MessageBusHandlers→CQRS.DTO.V1.CreateInventoryCommandCQRS.API.MessageBusHandlers.MessageBusHandlers→CQRS.DTO.V1.DeactivateInventoryCommandCQRS.API.MessageBusHandlers.MessageBusHandlers→CQRS.DTO.V1.RemoveItemsFromInventoryCommandCQRS.API.MessageBusHandlers.MessageBusHandlers→CQRS.DTO.V1.RenameInventoryCommand
- Direction
- API.MessageBusHandlers uses DTO.V1, so a change to DTO.V1 can break API.MessageBusHandlers, while a change to API.MessageBusHandlers can't break DTO.V1.
- Position
- Below the diagonal: API.MessageBusHandlers uses a module listed above it, which is the healthy direction.
17→6 API.ProjectionHandlers uses EntityIds✕
- Connections
- 1 pair of types, where a type in API.ProjectionHandlers uses a type in EntityIds.
- The types involved
CQRS.API.ProjectionHandlers.ProjectionHandlers→CQRS.EntityIds.EntityId
- Direction
- API.ProjectionHandlers uses EntityIds, so a change to EntityIds can break API.ProjectionHandlers, while a change to API.ProjectionHandlers can't break EntityIds.
- Position
- Below the diagonal: API.ProjectionHandlers uses a module listed above it, which is the healthy direction.
17→9 API.ProjectionHandlers uses Ports.ProjectionStore✕
- Connections
- 1 pair of types, where a type in API.ProjectionHandlers uses a type in Ports.ProjectionStore.
- The types involved
CQRS.API.ProjectionHandlers.ProjectionHandlers→CQRS.Ports.ProjectionStore.IProjectionStore`1
- Direction
- API.ProjectionHandlers uses Ports.ProjectionStore, so a change to Ports.ProjectionStore can break API.ProjectionHandlers, while a change to API.ProjectionHandlers can't break Ports.ProjectionStore.
- Position
- Below the diagonal: API.ProjectionHandlers uses a module listed above it, which is the healthy direction.
17→10 API.ProjectionHandlers uses Projections✕
- Connections
- 1 pair of types, where a type in API.ProjectionHandlers uses a type in Projections.
- The types involved
CQRS.API.ProjectionHandlers.ProjectionHandlers→CQRS.Projections.InventoryViewModel
- Direction
- API.ProjectionHandlers uses Projections, so a change to Projections can break API.ProjectionHandlers, while a change to API.ProjectionHandlers can't break Projections.
- Position
- Below the diagonal: API.ProjectionHandlers uses a module listed above it, which is the healthy direction.
17→12 API.ProjectionHandlers uses Application.CommandProcessingStatusRecording✕
- Connections
- 1 pair of types, where a type in API.ProjectionHandlers uses a type in Application.CommandProcessingStatusRecording.
- The types involved
CQRS.API.ProjectionHandlers.ProjectionHandlers→CQRS.Application.CommandProcessingStatusRecording.CommandProcessingStatusViewModel
- Direction
- API.ProjectionHandlers uses Application.CommandProcessingStatusRecording, so a change to Application.CommandProcessingStatusRecording can break API.ProjectionHandlers, while a change to API.ProjectionHandlers can't break Application.CommandProcessingStatusRecording.
- Position
- Below the diagonal: API.ProjectionHandlers uses a module listed above it, which is the healthy direction.
18→9 Application.CommandProcessingStatusRecording.GetCommandProcessingStatusQueryRepository uses Ports.ProjectionStore✕
- Connections
- 1 pair of types, where a type in Application.CommandProcessingStatusRecording.GetCommandProcessingStatusQueryRepository uses a type in Ports.ProjectionStore.
- The types involved
CQRS.Application.CommandProcessingStatusRecording.GetCommandProcessingStatusQueryRepository.GetCommandProcessingStatusQueryRepository→CQRS.Ports.ProjectionStore.IProjectionStore`1
- Direction
- Application.CommandProcessingStatusRecording.GetCommandProcessingStatusQueryRepository uses Ports.ProjectionStore, so a change to Ports.ProjectionStore can break Application.CommandProcessingStatusRecording.GetCommandProcessingStatusQueryRepository, while a change to Application.CommandProcessingStatusRecording.GetCommandProcessingStatusQueryRepository can't break Ports.ProjectionStore.
- Position
- Below the diagonal: Application.CommandProcessingStatusRecording.GetCommandProcessingStatusQueryRepository uses a module listed above it, which is the healthy direction.
18→12 Application.CommandProcessingStatusRecording.GetCommandProcessingStatusQueryRepository uses Application.CommandProcessingStatusRecording✕
- Connections
- 1 pair of types, where a type in Application.CommandProcessingStatusRecording.GetCommandProcessingStatusQueryRepository uses a type in Application.CommandProcessingStatusRecording.
- The types involved
CQRS.Application.CommandProcessingStatusRecording.GetCommandProcessingStatusQueryRepository.GetCommandProcessingStatusQueryRepository→CQRS.Application.CommandProcessingStatusRecording.CommandProcessingStatusViewModel
- Direction
- Application.CommandProcessingStatusRecording.GetCommandProcessingStatusQueryRepository uses Application.CommandProcessingStatusRecording, so a change to Application.CommandProcessingStatusRecording can break Application.CommandProcessingStatusRecording.GetCommandProcessingStatusQueryRepository, while a change to Application.CommandProcessingStatusRecording.GetCommandProcessingStatusQueryRepository can't break Application.CommandProcessingStatusRecording.
- Position
- Below the diagonal: Application.CommandProcessingStatusRecording.GetCommandProcessingStatusQueryRepository uses a module listed above it, which is the healthy direction.
19→6 Domain.Inventory uses EntityIds✕
- Connections
- 1 pair of types, where a type in Domain.Inventory uses a type in EntityIds.
- The types involved
CQRS.Domain.Inventory.InventoryId→CQRS.EntityIds.EntityId
- Direction
- Domain.Inventory uses EntityIds, so a change to EntityIds can break Domain.Inventory, while a change to Domain.Inventory can't break EntityIds.
- Position
- Below the diagonal: Domain.Inventory uses a module listed above it, which is the healthy direction.
19→14 Domain.Inventory uses Domain.ValueTypes✕
- Connections
- 6 pairs of types, where a type in Domain.Inventory uses a type in Domain.ValueTypes.
- The types involved
CQRS.Domain.Inventory.AddItemsToInventory→CQRS.Domain.ValueTypes.PositiveIntegerCQRS.Domain.Inventory.InventoryName→CQRS.Domain.ValueTypes.MediumStringCQRS.Domain.Inventory.ItemsAddedToInventory→CQRS.Domain.ValueTypes.PositiveIntegerCQRS.Domain.Inventory.ItemsRemovedFromInventory→CQRS.Domain.ValueTypes.PositiveIntegerCQRS.Domain.Inventory.RemoveItemsFromInventory→CQRS.Domain.ValueTypes.PositiveIntegerCQRS.Domain.Inventory.StockQuantity→CQRS.Domain.ValueTypes.PositiveInteger
- Direction
- Domain.Inventory uses Domain.ValueTypes, so a change to Domain.ValueTypes can break Domain.Inventory, while a change to Domain.Inventory can't break Domain.ValueTypes.
- Position
- Below the diagonal: Domain.Inventory uses a module listed above it, which is the healthy direction.
20→6 Domain.ValueTypes.ServiceIdModule uses EntityIds✕
- Connections
- 1 pair of types, where a type in Domain.ValueTypes.ServiceIdModule uses a type in EntityIds.
- The types involved
CQRS.Domain.ValueTypes.ServiceIdModule.ServiceIdModule→CQRS.EntityIds.EntityId
- Direction
- Domain.ValueTypes.ServiceIdModule uses EntityIds, so a change to EntityIds can break Domain.ValueTypes.ServiceIdModule, while a change to Domain.ValueTypes.ServiceIdModule can't break EntityIds.
- Position
- Below the diagonal: Domain.ValueTypes.ServiceIdModule uses a module listed above it, which is the healthy direction.
20→14 Domain.ValueTypes.ServiceIdModule uses Domain.ValueTypes✕
- Connections
- 1 pair of types, where a type in Domain.ValueTypes.ServiceIdModule uses a type in Domain.ValueTypes.
- The types involved
CQRS.Domain.ValueTypes.ServiceIdModule.ServiceIdModule→CQRS.Domain.ValueTypes.ServiceId
- Direction
- Domain.ValueTypes.ServiceIdModule uses Domain.ValueTypes, so a change to Domain.ValueTypes can break Domain.ValueTypes.ServiceIdModule, while a change to Domain.ValueTypes.ServiceIdModule can't break Domain.ValueTypes.
- Position
- Below the diagonal: Domain.ValueTypes.ServiceIdModule uses a module listed above it, which is the healthy direction.
21→9 Projections.WolverineConsumers uses Ports.ProjectionStore✕
- Connections
- 1 pair of types, where a type in Projections.WolverineConsumers uses a type in Ports.ProjectionStore.
- The types involved
CQRS.Projections.WolverineConsumers.InventoryProjectionConsumer→CQRS.Ports.ProjectionStore.IProjectionStore`1
- Direction
- Projections.WolverineConsumers uses Ports.ProjectionStore, so a change to Ports.ProjectionStore can break Projections.WolverineConsumers, while a change to Projections.WolverineConsumers can't break Ports.ProjectionStore.
- Position
- Below the diagonal: Projections.WolverineConsumers uses a module listed above it, which is the healthy direction.
21→10 Projections.WolverineConsumers uses Projections✕
- Connections
- 1 pair of types, where a type in Projections.WolverineConsumers uses a type in Projections.
- The types involved
CQRS.Projections.WolverineConsumers.InventoryProjectionConsumer→CQRS.Projections.InventoryViewModel
- Direction
- Projections.WolverineConsumers uses Projections, so a change to Projections can break Projections.WolverineConsumers, while a change to Projections.WolverineConsumers can't break Projections.
- Position
- Below the diagonal: Projections.WolverineConsumers uses a module listed above it, which is the healthy direction.
21→13 Projections.WolverineConsumers uses DTO.V1✕
- Connections
- 5 pairs of types, where a type in Projections.WolverineConsumers uses a type in DTO.V1.
- The types involved
CQRS.Projections.WolverineConsumers.InventoryProjectionConsumer→CQRS.DTO.V1.InventoryCreatedEventCQRS.Projections.WolverineConsumers.InventoryProjectionConsumer→CQRS.DTO.V1.InventoryDeactivatedEventCQRS.Projections.WolverineConsumers.InventoryProjectionConsumer→CQRS.DTO.V1.InventoryRenamedEventCQRS.Projections.WolverineConsumers.InventoryProjectionConsumer→CQRS.DTO.V1.ItemsAddedToInventoryEventCQRS.Projections.WolverineConsumers.InventoryProjectionConsumer→CQRS.DTO.V1.ItemsRemovedFromInventoryEvent
- Direction
- Projections.WolverineConsumers uses DTO.V1, so a change to DTO.V1 can break Projections.WolverineConsumers, while a change to Projections.WolverineConsumers can't break DTO.V1.
- Position
- Below the diagonal: Projections.WolverineConsumers uses a module listed above it, which is the healthy direction.
22→6 API.ApiHandlers uses EntityIds✕
- Connections
- 1 pair of types, where a type in API.ApiHandlers uses a type in EntityIds.
- The types involved
CQRS.API.ApiHandlers.ApiHandlers→CQRS.EntityIds.EntityId
- Direction
- API.ApiHandlers uses EntityIds, so a change to EntityIds can break API.ApiHandlers, while a change to API.ApiHandlers can't break EntityIds.
- Position
- Below the diagonal: API.ApiHandlers uses a module listed above it, which is the healthy direction.
22→13 API.ApiHandlers uses DTO.V1✕
- Connections
- 4 pairs of types, where a type in API.ApiHandlers uses a type in DTO.V1.
- The types involved
CQRS.API.ApiHandlers.ApiHandlers→CQRS.DTO.V1.AddItemsToInventoryCommandCQRS.API.ApiHandlers.ApiHandlers→CQRS.DTO.V1.DeactivateInventoryCommandCQRS.API.ApiHandlers.ApiHandlers→CQRS.DTO.V1.RemoveItemsFromInventoryCommandCQRS.API.ApiHandlers.ApiHandlers→CQRS.DTO.V1.RenameInventoryCommand
- Direction
- API.ApiHandlers uses DTO.V1, so a change to DTO.V1 can break API.ApiHandlers, while a change to API.ApiHandlers can't break DTO.V1.
- Position
- Below the diagonal: API.ApiHandlers uses a module listed above it, which is the healthy direction.
22→17 API.ApiHandlers uses API.ProjectionHandlers✕
- Connections
- 1 pair of types, where a type in API.ApiHandlers uses a type in API.ProjectionHandlers.
- The types involved
CQRS.API.ApiHandlers.ApiHandlers→CQRS.API.ProjectionHandlers.DocumentQueryResult`1
- Direction
- API.ApiHandlers uses API.ProjectionHandlers, so a change to API.ProjectionHandlers can break API.ApiHandlers, while a change to API.ApiHandlers can't break API.ProjectionHandlers.
- Position
- Below the diagonal: API.ApiHandlers uses a module listed above it, which is the healthy direction.
23→5 Application uses Domain.Moon✕
- Connections
- 2 pairs of types, where a type in Application uses a type in Domain.Moon.
- The types involved
CQRS.Application.IMoonPhaseService→CQRS.Domain.Moon.MoonPhaseCQRS.Application.MoonPhaseServiceStub→CQRS.Domain.Moon.MoonPhase
- Direction
- Application uses Domain.Moon, so a change to Domain.Moon can break Application, while a change to Application can't break Domain.Moon.
- Position
- Below the diagonal: Application uses a module listed above it, which is the healthy direction.
23→8 Application uses Ports.Messaging✕
- Connections
- 1 pair of types, where a type in Application uses a type in Ports.Messaging.
- The types involved
CQRS.Application.EventStoreEventsPublisher→CQRS.Ports.Messaging.IMessageBus
- Direction
- Application uses Ports.Messaging, so a change to Ports.Messaging can break Application, while a change to Application can't break Ports.Messaging.
- Position
- Below the diagonal: Application uses a module listed above it, which is the healthy direction.
23→12 Application uses Application.CommandProcessingStatusRecording✕
- Connections
- 1 pair of types, where a type in Application uses a type in Application.CommandProcessingStatusRecording.
- The types involved
CQRS.Application.ApplicationEnvironment→CQRS.Application.CommandProcessingStatusRecording.ICommandProcessingStatusRecordingService
- Direction
- Application uses Application.CommandProcessingStatusRecording, so a change to Application.CommandProcessingStatusRecording can break Application, while a change to Application can't break Application.CommandProcessingStatusRecording.
- Position
- Below the diagonal: Application uses a module listed above it, which is the healthy direction.
23→19 Application uses Domain.Inventory✕
- Connections
- 4 pairs of types, where a type in Application uses a type in Domain.Inventory.
- The types involved
CQRS.Application.CommandHandlerFailure→CQRS.Domain.Inventory.InventoryFailureCQRS.Application.InventoryEventStreamDtoMapper→CQRS.Domain.Inventory.InventoryEventCQRS.Application.InventoryEventStreamProjection→CQRS.Domain.Inventory.InventoryEventCQRS.Application.InventoryEventStreamProjection→CQRS.Domain.Inventory.InventoryState
- Direction
- Application uses Domain.Inventory, so a change to Domain.Inventory can break Application, while a change to Application can't break Domain.Inventory.
- Position
- Below the diagonal: Application uses a module listed above it, which is the healthy direction.
24→6 Domain.Inventory.InventoryIdModule uses EntityIds✕
- Connections
- 1 pair of types, where a type in Domain.Inventory.InventoryIdModule uses a type in EntityIds.
- The types involved
CQRS.Domain.Inventory.InventoryIdModule.InventoryIdModule→CQRS.EntityIds.EntityId
- Direction
- Domain.Inventory.InventoryIdModule uses EntityIds, so a change to EntityIds can break Domain.Inventory.InventoryIdModule, while a change to Domain.Inventory.InventoryIdModule can't break EntityIds.
- Position
- Below the diagonal: Domain.Inventory.InventoryIdModule uses a module listed above it, which is the healthy direction.
24→19 Domain.Inventory.InventoryIdModule uses Domain.Inventory✕
- Connections
- 1 pair of types, where a type in Domain.Inventory.InventoryIdModule uses a type in Domain.Inventory.
- The types involved
CQRS.Domain.Inventory.InventoryIdModule.InventoryIdModule→CQRS.Domain.Inventory.InventoryId
- Direction
- Domain.Inventory.InventoryIdModule uses Domain.Inventory, so a change to Domain.Inventory can break Domain.Inventory.InventoryIdModule, while a change to Domain.Inventory.InventoryIdModule can't break Domain.Inventory.
- Position
- Below the diagonal: Domain.Inventory.InventoryIdModule uses a module listed above it, which is the healthy direction.
25→14 Domain.Inventory.InventoryNameModule uses Domain.ValueTypes✕
- Connections
- 1 pair of types, where a type in Domain.Inventory.InventoryNameModule uses a type in Domain.ValueTypes.
- The types involved
CQRS.Domain.Inventory.InventoryNameModule.InventoryNameModule→CQRS.Domain.ValueTypes.MediumString
- Direction
- Domain.Inventory.InventoryNameModule uses Domain.ValueTypes, so a change to Domain.ValueTypes can break Domain.Inventory.InventoryNameModule, while a change to Domain.Inventory.InventoryNameModule can't break Domain.ValueTypes.
- Position
- Below the diagonal: Domain.Inventory.InventoryNameModule uses a module listed above it, which is the healthy direction.
25→19 Domain.Inventory.InventoryNameModule uses Domain.Inventory✕
- Connections
- 1 pair of types, where a type in Domain.Inventory.InventoryNameModule uses a type in Domain.Inventory.
- The types involved
CQRS.Domain.Inventory.InventoryNameModule.InventoryNameModule→CQRS.Domain.Inventory.InventoryName
- Direction
- Domain.Inventory.InventoryNameModule uses Domain.Inventory, so a change to Domain.Inventory can break Domain.Inventory.InventoryNameModule, while a change to Domain.Inventory.InventoryNameModule can't break Domain.Inventory.
- Position
- Below the diagonal: Domain.Inventory.InventoryNameModule uses a module listed above it, which is the healthy direction.
26→14 Domain.Inventory.StockQuantityModule uses Domain.ValueTypes✕
- Connections
- 1 pair of types, where a type in Domain.Inventory.StockQuantityModule uses a type in Domain.ValueTypes.
- The types involved
CQRS.Domain.Inventory.StockQuantityModule.StockQuantityModule→CQRS.Domain.ValueTypes.PositiveInteger
- Direction
- Domain.Inventory.StockQuantityModule uses Domain.ValueTypes, so a change to Domain.ValueTypes can break Domain.Inventory.StockQuantityModule, while a change to Domain.Inventory.StockQuantityModule can't break Domain.ValueTypes.
- Position
- Below the diagonal: Domain.Inventory.StockQuantityModule uses a module listed above it, which is the healthy direction.
26→19 Domain.Inventory.StockQuantityModule uses Domain.Inventory✕
- Connections
- 2 pairs of types, where a type in Domain.Inventory.StockQuantityModule uses a type in Domain.Inventory.
- The types involved
CQRS.Domain.Inventory.StockQuantityModule.StockQuantityModule→CQRS.Domain.Inventory.StockQuantityCQRS.Domain.Inventory.StockQuantityModule.StockQuantityModule→CQRS.Domain.Inventory.SubtractFailure
- Direction
- Domain.Inventory.StockQuantityModule uses Domain.Inventory, so a change to Domain.Inventory can break Domain.Inventory.StockQuantityModule, while a change to Domain.Inventory.StockQuantityModule can't break Domain.Inventory.
- Position
- Below the diagonal: Domain.Inventory.StockQuantityModule uses a module listed above it, which is the healthy direction.
27→5 Domain.InventoryAggregate uses Domain.Moon✕
- Connections
- 1 pair of types, where a type in Domain.InventoryAggregate uses a type in Domain.Moon.
- The types involved
CQRS.Domain.InventoryAggregate.InventoryAggregate→CQRS.Domain.Moon.MoonPhase
- Direction
- Domain.InventoryAggregate uses Domain.Moon, so a change to Domain.Moon can break Domain.InventoryAggregate, while a change to Domain.InventoryAggregate can't break Domain.Moon.
- Position
- Below the diagonal: Domain.InventoryAggregate uses a module listed above it, which is the healthy direction.
27→19 Domain.InventoryAggregate uses Domain.Inventory✕
- Connections
- 8 pairs of types, where a type in Domain.InventoryAggregate uses a type in Domain.Inventory.
- The types involved
CQRS.Domain.InventoryAggregate.InventoryAggregate→CQRS.Domain.Inventory.AddItemsToInventoryCQRS.Domain.InventoryAggregate.InventoryAggregate→CQRS.Domain.Inventory.CreateInventoryCQRS.Domain.InventoryAggregate.InventoryAggregate→CQRS.Domain.Inventory.DeactivateInventoryCQRS.Domain.InventoryAggregate.InventoryAggregate→CQRS.Domain.Inventory.InventoryEventCQRS.Domain.InventoryAggregate.InventoryAggregate→CQRS.Domain.Inventory.InventoryFailureCQRS.Domain.InventoryAggregate.InventoryAggregate→CQRS.Domain.Inventory.InventoryStateCQRS.Domain.InventoryAggregate.InventoryAggregate→CQRS.Domain.Inventory.RemoveItemsFromInventoryCQRS.Domain.InventoryAggregate.InventoryAggregate→CQRS.Domain.Inventory.RenameInventory
- Direction
- Domain.InventoryAggregate uses Domain.Inventory, so a change to Domain.Inventory can break Domain.InventoryAggregate, while a change to Domain.InventoryAggregate can't break Domain.Inventory.
- Position
- Below the diagonal: Domain.InventoryAggregate uses a module listed above it, which is the healthy direction.
28→13 Mapping.AddItemsToInventory' uses DTO.V1✕
- Connections
- 1 pair of types, where a type in Mapping.AddItemsToInventory' uses a type in DTO.V1.
- The types involved
CQRS.Mapping.AddItemsToInventory'.AddItemsToInventory'→CQRS.DTO.V1.AddItemsToInventoryCommand
- Direction
- Mapping.AddItemsToInventory' uses DTO.V1, so a change to DTO.V1 can break Mapping.AddItemsToInventory', while a change to Mapping.AddItemsToInventory' can't break DTO.V1.
- Position
- Below the diagonal: Mapping.AddItemsToInventory' uses a module listed above it, which is the healthy direction.
28→19 Mapping.AddItemsToInventory' uses Domain.Inventory✕
- Connections
- 1 pair of types, where a type in Mapping.AddItemsToInventory' uses a type in Domain.Inventory.
- The types involved
CQRS.Mapping.AddItemsToInventory'.AddItemsToInventory'→CQRS.Domain.Inventory.AddItemsToInventory
- Direction
- Mapping.AddItemsToInventory' uses Domain.Inventory, so a change to Domain.Inventory can break Mapping.AddItemsToInventory', while a change to Mapping.AddItemsToInventory' can't break Domain.Inventory.
- Position
- Below the diagonal: Mapping.AddItemsToInventory' uses a module listed above it, which is the healthy direction.
29→13 Mapping.CreateInventory' uses DTO.V1✕
- Connections
- 1 pair of types, where a type in Mapping.CreateInventory' uses a type in DTO.V1.
- The types involved
CQRS.Mapping.CreateInventory'.CreateInventory'→CQRS.DTO.V1.CreateInventoryCommand
- Direction
- Mapping.CreateInventory' uses DTO.V1, so a change to DTO.V1 can break Mapping.CreateInventory', while a change to Mapping.CreateInventory' can't break DTO.V1.
- Position
- Below the diagonal: Mapping.CreateInventory' uses a module listed above it, which is the healthy direction.
29→19 Mapping.CreateInventory' uses Domain.Inventory✕
- Connections
- 1 pair of types, where a type in Mapping.CreateInventory' uses a type in Domain.Inventory.
- The types involved
CQRS.Mapping.CreateInventory'.CreateInventory'→CQRS.Domain.Inventory.CreateInventory
- Direction
- Mapping.CreateInventory' uses Domain.Inventory, so a change to Domain.Inventory can break Mapping.CreateInventory', while a change to Mapping.CreateInventory' can't break Domain.Inventory.
- Position
- Below the diagonal: Mapping.CreateInventory' uses a module listed above it, which is the healthy direction.
30→13 Mapping.DeactivateInventory' uses DTO.V1✕
- Connections
- 1 pair of types, where a type in Mapping.DeactivateInventory' uses a type in DTO.V1.
- The types involved
CQRS.Mapping.DeactivateInventory'.DeactivateInventory'→CQRS.DTO.V1.DeactivateInventoryCommand
- Direction
- Mapping.DeactivateInventory' uses DTO.V1, so a change to DTO.V1 can break Mapping.DeactivateInventory', while a change to Mapping.DeactivateInventory' can't break DTO.V1.
- Position
- Below the diagonal: Mapping.DeactivateInventory' uses a module listed above it, which is the healthy direction.
30→19 Mapping.DeactivateInventory' uses Domain.Inventory✕
- Connections
- 1 pair of types, where a type in Mapping.DeactivateInventory' uses a type in Domain.Inventory.
- The types involved
CQRS.Mapping.DeactivateInventory'.DeactivateInventory'→CQRS.Domain.Inventory.DeactivateInventory
- Direction
- Mapping.DeactivateInventory' uses Domain.Inventory, so a change to Domain.Inventory can break Mapping.DeactivateInventory', while a change to Mapping.DeactivateInventory' can't break Domain.Inventory.
- Position
- Below the diagonal: Mapping.DeactivateInventory' uses a module listed above it, which is the healthy direction.
31→4 Mapping.InventoryCommand' uses DTO✕
- Connections
- 1 pair of types, where a type in Mapping.InventoryCommand' uses a type in DTO.
- The types involved
CQRS.Mapping.InventoryCommand'.InventoryCommand'→CQRS.DTO.CqrsCommandDto
- Direction
- Mapping.InventoryCommand' uses DTO, so a change to DTO can break Mapping.InventoryCommand', while a change to Mapping.InventoryCommand' can't break DTO.
- Position
- Below the diagonal: Mapping.InventoryCommand' uses a module listed above it, which is the healthy direction.
31→19 Mapping.InventoryCommand' uses Domain.Inventory✕
- Connections
- 1 pair of types, where a type in Mapping.InventoryCommand' uses a type in Domain.Inventory.
- The types involved
CQRS.Mapping.InventoryCommand'.InventoryCommand'→CQRS.Domain.Inventory.InventoryCommand
- Direction
- Mapping.InventoryCommand' uses Domain.Inventory, so a change to Domain.Inventory can break Mapping.InventoryCommand', while a change to Mapping.InventoryCommand' can't break Domain.Inventory.
- Position
- Below the diagonal: Mapping.InventoryCommand' uses a module listed above it, which is the healthy direction.
32→13 Mapping.InventoryCreated' uses DTO.V1✕
- Connections
- 1 pair of types, where a type in Mapping.InventoryCreated' uses a type in DTO.V1.
- The types involved
CQRS.Mapping.InventoryCreated'.InventoryCreated'→CQRS.DTO.V1.InventoryCreatedEvent
- Direction
- Mapping.InventoryCreated' uses DTO.V1, so a change to DTO.V1 can break Mapping.InventoryCreated', while a change to Mapping.InventoryCreated' can't break DTO.V1.
- Position
- Below the diagonal: Mapping.InventoryCreated' uses a module listed above it, which is the healthy direction.
32→19 Mapping.InventoryCreated' uses Domain.Inventory✕
- Connections
- 1 pair of types, where a type in Mapping.InventoryCreated' uses a type in Domain.Inventory.
- The types involved
CQRS.Mapping.InventoryCreated'.InventoryCreated'→CQRS.Domain.Inventory.InventoryCreated
- Direction
- Mapping.InventoryCreated' uses Domain.Inventory, so a change to Domain.Inventory can break Mapping.InventoryCreated', while a change to Mapping.InventoryCreated' can't break Domain.Inventory.
- Position
- Below the diagonal: Mapping.InventoryCreated' uses a module listed above it, which is the healthy direction.
33→13 Mapping.InventoryDeactivated' uses DTO.V1✕
- Connections
- 1 pair of types, where a type in Mapping.InventoryDeactivated' uses a type in DTO.V1.
- The types involved
CQRS.Mapping.InventoryDeactivated'.InventoryDeactivated'→CQRS.DTO.V1.InventoryDeactivatedEvent
- Direction
- Mapping.InventoryDeactivated' uses DTO.V1, so a change to DTO.V1 can break Mapping.InventoryDeactivated', while a change to Mapping.InventoryDeactivated' can't break DTO.V1.
- Position
- Below the diagonal: Mapping.InventoryDeactivated' uses a module listed above it, which is the healthy direction.
33→19 Mapping.InventoryDeactivated' uses Domain.Inventory✕
- Connections
- 1 pair of types, where a type in Mapping.InventoryDeactivated' uses a type in Domain.Inventory.
- The types involved
CQRS.Mapping.InventoryDeactivated'.InventoryDeactivated'→CQRS.Domain.Inventory.InventoryDeactivated
- Direction
- Mapping.InventoryDeactivated' uses Domain.Inventory, so a change to Domain.Inventory can break Mapping.InventoryDeactivated', while a change to Mapping.InventoryDeactivated' can't break Domain.Inventory.
- Position
- Below the diagonal: Mapping.InventoryDeactivated' uses a module listed above it, which is the healthy direction.
34→4 Mapping.InventoryEvent' uses DTO✕
- Connections
- 1 pair of types, where a type in Mapping.InventoryEvent' uses a type in DTO.
- The types involved
CQRS.Mapping.InventoryEvent'.InventoryEvent'→CQRS.DTO.CqrsEventDto
- Direction
- Mapping.InventoryEvent' uses DTO, so a change to DTO can break Mapping.InventoryEvent', while a change to Mapping.InventoryEvent' can't break DTO.
- Position
- Below the diagonal: Mapping.InventoryEvent' uses a module listed above it, which is the healthy direction.
34→19 Mapping.InventoryEvent' uses Domain.Inventory✕
- Connections
- 1 pair of types, where a type in Mapping.InventoryEvent' uses a type in Domain.Inventory.
- The types involved
CQRS.Mapping.InventoryEvent'.InventoryEvent'→CQRS.Domain.Inventory.InventoryEvent
- Direction
- Mapping.InventoryEvent' uses Domain.Inventory, so a change to Domain.Inventory can break Mapping.InventoryEvent', while a change to Mapping.InventoryEvent' can't break Domain.Inventory.
- Position
- Below the diagonal: Mapping.InventoryEvent' uses a module listed above it, which is the healthy direction.
35→13 Mapping.InventoryRenamed' uses DTO.V1✕
- Connections
- 1 pair of types, where a type in Mapping.InventoryRenamed' uses a type in DTO.V1.
- The types involved
CQRS.Mapping.InventoryRenamed'.InventoryRenamed'→CQRS.DTO.V1.InventoryRenamedEvent
- Direction
- Mapping.InventoryRenamed' uses DTO.V1, so a change to DTO.V1 can break Mapping.InventoryRenamed', while a change to Mapping.InventoryRenamed' can't break DTO.V1.
- Position
- Below the diagonal: Mapping.InventoryRenamed' uses a module listed above it, which is the healthy direction.
35→19 Mapping.InventoryRenamed' uses Domain.Inventory✕
- Connections
- 1 pair of types, where a type in Mapping.InventoryRenamed' uses a type in Domain.Inventory.
- The types involved
CQRS.Mapping.InventoryRenamed'.InventoryRenamed'→CQRS.Domain.Inventory.InventoryRenamed
- Direction
- Mapping.InventoryRenamed' uses Domain.Inventory, so a change to Domain.Inventory can break Mapping.InventoryRenamed', while a change to Mapping.InventoryRenamed' can't break Domain.Inventory.
- Position
- Below the diagonal: Mapping.InventoryRenamed' uses a module listed above it, which is the healthy direction.
36→9 Projections.InventoryViewModelProjection uses Ports.ProjectionStore✕
- Connections
- 1 pair of types, where a type in Projections.InventoryViewModelProjection uses a type in Ports.ProjectionStore.
- The types involved
CQRS.Projections.InventoryViewModelProjection.InventoryViewModelProjection→CQRS.Ports.ProjectionStore.IProjectionStore`1
- Direction
- Projections.InventoryViewModelProjection uses Ports.ProjectionStore, so a change to Ports.ProjectionStore can break Projections.InventoryViewModelProjection, while a change to Projections.InventoryViewModelProjection can't break Ports.ProjectionStore.
- Position
- Below the diagonal: Projections.InventoryViewModelProjection uses a module listed above it, which is the healthy direction.
36→10 Projections.InventoryViewModelProjection uses Projections✕
- Connections
- 1 pair of types, where a type in Projections.InventoryViewModelProjection uses a type in Projections.
- The types involved
CQRS.Projections.InventoryViewModelProjection.InventoryViewModelProjection→CQRS.Projections.InventoryViewModel
- Direction
- Projections.InventoryViewModelProjection uses Projections, so a change to Projections can break Projections.InventoryViewModelProjection, while a change to Projections.InventoryViewModelProjection can't break Projections.
- Position
- Below the diagonal: Projections.InventoryViewModelProjection uses a module listed above it, which is the healthy direction.
36→19 Projections.InventoryViewModelProjection uses Domain.Inventory✕
- Connections
- 1 pair of types, where a type in Projections.InventoryViewModelProjection uses a type in Domain.Inventory.
- The types involved
CQRS.Projections.InventoryViewModelProjection.InventoryViewModelProjection→CQRS.Domain.Inventory.InventoryEvent
- Direction
- Projections.InventoryViewModelProjection uses Domain.Inventory, so a change to Domain.Inventory can break Projections.InventoryViewModelProjection, while a change to Projections.InventoryViewModelProjection can't break Domain.Inventory.
- Position
- Below the diagonal: Projections.InventoryViewModelProjection uses a module listed above it, which is the healthy direction.
37→1 API.ApiHandlers.CommandApiHandlers uses API✕
- Connections
- 1 pair of types, where a type in API.ApiHandlers.CommandApiHandlers uses a type in API.
- The types involved
CQRS.API.ApiHandlers.CommandApiHandlers.CommandApiHandlers→CQRS.API.AcceptedResponse
- Direction
- API.ApiHandlers.CommandApiHandlers uses API, so a change to API can break API.ApiHandlers.CommandApiHandlers, while a change to API.ApiHandlers.CommandApiHandlers can't break API.
- Position
- Below the diagonal: API.ApiHandlers.CommandApiHandlers uses a module listed above it, which is the healthy direction.
37→8 API.ApiHandlers.CommandApiHandlers uses Ports.Messaging✕
- Connections
- 1 pair of types, where a type in API.ApiHandlers.CommandApiHandlers uses a type in Ports.Messaging.
- The types involved
CQRS.API.ApiHandlers.CommandApiHandlers.CommandApiHandlers→CQRS.Ports.Messaging.IMessageBus
- Direction
- API.ApiHandlers.CommandApiHandlers uses Ports.Messaging, so a change to Ports.Messaging can break API.ApiHandlers.CommandApiHandlers, while a change to API.ApiHandlers.CommandApiHandlers can't break Ports.Messaging.
- Position
- Below the diagonal: API.ApiHandlers.CommandApiHandlers uses a module listed above it, which is the healthy direction.
37→13 API.ApiHandlers.CommandApiHandlers uses DTO.V1✕
- Connections
- 1 pair of types, where a type in API.ApiHandlers.CommandApiHandlers uses a type in DTO.V1.
- The types involved
CQRS.API.ApiHandlers.CommandApiHandlers.CommandApiHandlers→CQRS.DTO.V1.CreateInventoryCommand
- Direction
- API.ApiHandlers.CommandApiHandlers uses DTO.V1, so a change to DTO.V1 can break API.ApiHandlers.CommandApiHandlers, while a change to API.ApiHandlers.CommandApiHandlers can't break DTO.V1.
- Position
- Below the diagonal: API.ApiHandlers.CommandApiHandlers uses a module listed above it, which is the healthy direction.
37→22 API.ApiHandlers.CommandApiHandlers uses API.ApiHandlers✕
- Connections
- 1 pair of types, where a type in API.ApiHandlers.CommandApiHandlers uses a type in API.ApiHandlers.
- The types involved
CQRS.API.ApiHandlers.CommandApiHandlers.CommandApiHandlers→CQRS.API.ApiHandlers.ApiResult`1
- Direction
- API.ApiHandlers.CommandApiHandlers uses API.ApiHandlers, so a change to API.ApiHandlers can break API.ApiHandlers.CommandApiHandlers, while a change to API.ApiHandlers.CommandApiHandlers can't break API.ApiHandlers.
- Position
- Below the diagonal: API.ApiHandlers.CommandApiHandlers uses a module listed above it, which is the healthy direction.
38→9 API.ApiHandlers.QueryApiHandlers uses Ports.ProjectionStore✕
- Connections
- 1 pair of types, where a type in API.ApiHandlers.QueryApiHandlers uses a type in Ports.ProjectionStore.
- The types involved
CQRS.API.ApiHandlers.QueryApiHandlers.QueryApiHandlers→CQRS.Ports.ProjectionStore.IProjectionStore`1
- Direction
- API.ApiHandlers.QueryApiHandlers uses Ports.ProjectionStore, so a change to Ports.ProjectionStore can break API.ApiHandlers.QueryApiHandlers, while a change to API.ApiHandlers.QueryApiHandlers can't break Ports.ProjectionStore.
- Position
- Below the diagonal: API.ApiHandlers.QueryApiHandlers uses a module listed above it, which is the healthy direction.
38→10 API.ApiHandlers.QueryApiHandlers uses Projections✕
- Connections
- 1 pair of types, where a type in API.ApiHandlers.QueryApiHandlers uses a type in Projections.
- The types involved
CQRS.API.ApiHandlers.QueryApiHandlers.QueryApiHandlers→CQRS.Projections.InventoryViewModel
- Direction
- API.ApiHandlers.QueryApiHandlers uses Projections, so a change to Projections can break API.ApiHandlers.QueryApiHandlers, while a change to API.ApiHandlers.QueryApiHandlers can't break Projections.
- Position
- Below the diagonal: API.ApiHandlers.QueryApiHandlers uses a module listed above it, which is the healthy direction.
38→12 API.ApiHandlers.QueryApiHandlers uses Application.CommandProcessingStatusRecording✕
- Connections
- 1 pair of types, where a type in API.ApiHandlers.QueryApiHandlers uses a type in Application.CommandProcessingStatusRecording.
- The types involved
CQRS.API.ApiHandlers.QueryApiHandlers.QueryApiHandlers→CQRS.Application.CommandProcessingStatusRecording.CommandProcessingStatusViewModel
- Direction
- API.ApiHandlers.QueryApiHandlers uses Application.CommandProcessingStatusRecording, so a change to Application.CommandProcessingStatusRecording can break API.ApiHandlers.QueryApiHandlers, while a change to API.ApiHandlers.QueryApiHandlers can't break Application.CommandProcessingStatusRecording.
- Position
- Below the diagonal: API.ApiHandlers.QueryApiHandlers uses a module listed above it, which is the healthy direction.
38→22 API.ApiHandlers.QueryApiHandlers uses API.ApiHandlers✕
- Connections
- 1 pair of types, where a type in API.ApiHandlers.QueryApiHandlers uses a type in API.ApiHandlers.
- The types involved
CQRS.API.ApiHandlers.QueryApiHandlers.QueryApiHandlers→CQRS.API.ApiHandlers.ApiResult`1
- Direction
- API.ApiHandlers.QueryApiHandlers uses API.ApiHandlers, so a change to API.ApiHandlers can break API.ApiHandlers.QueryApiHandlers, while a change to API.ApiHandlers.QueryApiHandlers can't break API.ApiHandlers.
- Position
- Below the diagonal: API.ApiHandlers.QueryApiHandlers uses a module listed above it, which is the healthy direction.
39→19 Application.InventoryCommandDtoHandler uses Domain.Inventory✕
- Connections
- 9 pairs of types, where a type in Application.InventoryCommandDtoHandler uses a type in Domain.Inventory.
- The types involved
CQRS.Application.InventoryCommandDtoHandler.InventoryCommandDtoHandler→CQRS.Domain.Inventory.AddItemsToInventoryCQRS.Application.InventoryCommandDtoHandler.InventoryCommandDtoHandler→CQRS.Domain.Inventory.CreateInventoryCQRS.Application.InventoryCommandDtoHandler.InventoryCommandDtoHandler→CQRS.Domain.Inventory.DeactivateInventoryCQRS.Application.InventoryCommandDtoHandler.InventoryCommandDtoHandler→CQRS.Domain.Inventory.InventoryCommandCQRS.Application.InventoryCommandDtoHandler.InventoryCommandDtoHandler→CQRS.Domain.Inventory.InventoryEventCQRS.Application.InventoryCommandDtoHandler.InventoryCommandDtoHandler→CQRS.Domain.Inventory.InventoryFailureCQRS.Application.InventoryCommandDtoHandler.InventoryCommandDtoHandler→CQRS.Domain.Inventory.InventoryStateCQRS.Application.InventoryCommandDtoHandler.InventoryCommandDtoHandler→CQRS.Domain.Inventory.RemoveItemsFromInventoryCQRS.Application.InventoryCommandDtoHandler.InventoryCommandDtoHandler→CQRS.Domain.Inventory.RenameInventory
- Direction
- Application.InventoryCommandDtoHandler uses Domain.Inventory, so a change to Domain.Inventory can break Application.InventoryCommandDtoHandler, while a change to Application.InventoryCommandDtoHandler can't break Domain.Inventory.
- Position
- Below the diagonal: Application.InventoryCommandDtoHandler uses a module listed above it, which is the healthy direction.
39→23 Application.InventoryCommandDtoHandler uses Application✕
- Connections
- 4 pairs of types, where a type in Application.InventoryCommandDtoHandler uses a type in Application.
- The types involved
CQRS.Application.InventoryCommandDtoHandler.InventoryCommandDtoHandler→CQRS.Application.ApplicationEnvironmentCQRS.Application.InventoryCommandDtoHandler.InventoryCommandDtoHandler→CQRS.Application.CommandHandlerFailureCQRS.Application.InventoryCommandDtoHandler.InventoryCommandDtoHandler→CQRS.Application.InventoryEventStreamDtoMapperCQRS.Application.InventoryCommandDtoHandler.InventoryCommandDtoHandler→CQRS.Application.InventoryEventStreamProjection
- Direction
- Application.InventoryCommandDtoHandler uses Application, so a change to Application can break Application.InventoryCommandDtoHandler, while a change to Application.InventoryCommandDtoHandler can't break Application.
- Position
- Below the diagonal: Application.InventoryCommandDtoHandler uses a module listed above it, which is the healthy direction.
40→13 Application.WolverineConsumers uses DTO.V1✕
- Connections
- 5 pairs of types, where a type in Application.WolverineConsumers uses a type in DTO.V1.
- The types involved
CQRS.Application.WolverineConsumers.AddItemsToInventoryCommandConsumer→CQRS.DTO.V1.AddItemsToInventoryCommandCQRS.Application.WolverineConsumers.CreateInventoryCommandConsumer→CQRS.DTO.V1.CreateInventoryCommandCQRS.Application.WolverineConsumers.DeactivateInventoryCommandConsumer→CQRS.DTO.V1.DeactivateInventoryCommandCQRS.Application.WolverineConsumers.RemoveItemsFromInventoryCommandConsumer→CQRS.DTO.V1.RemoveItemsFromInventoryCommandCQRS.Application.WolverineConsumers.RenameInventoryCommandConsumer→CQRS.DTO.V1.RenameInventoryCommand
- Direction
- Application.WolverineConsumers uses DTO.V1, so a change to DTO.V1 can break Application.WolverineConsumers, while a change to Application.WolverineConsumers can't break DTO.V1.
- Position
- Below the diagonal: Application.WolverineConsumers uses a module listed above it, which is the healthy direction.
40→23 Application.WolverineConsumers uses Application✕
- Connections
- 5 pairs of types, where a type in Application.WolverineConsumers uses a type in Application.
- The types involved
CQRS.Application.WolverineConsumers.AddItemsToInventoryCommandConsumer→CQRS.Application.ApplicationEnvironmentCQRS.Application.WolverineConsumers.CreateInventoryCommandConsumer→CQRS.Application.ApplicationEnvironmentCQRS.Application.WolverineConsumers.DeactivateInventoryCommandConsumer→CQRS.Application.ApplicationEnvironmentCQRS.Application.WolverineConsumers.RemoveItemsFromInventoryCommandConsumer→CQRS.Application.ApplicationEnvironmentCQRS.Application.WolverineConsumers.RenameInventoryCommandConsumer→CQRS.Application.ApplicationEnvironment
- Direction
- Application.WolverineConsumers uses Application, so a change to Application can break Application.WolverineConsumers, while a change to Application.WolverineConsumers can't break Application.
- Position
- Below the diagonal: Application.WolverineConsumers 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 Sourcing
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A02:2025 — Security Misconfiguration | 10 | High / Critical |
| A07:2025 — Authentication Failures | 6 | High / Critical |
| A05:2025 — Injection | 5 | High / Critical |
Roadmap
Top priorities: Codify backups + geo-recovery in IaC and document RTO/RPO and the restore procedure — a persistence guard alone is not disaster recovery; Resolve the 28 Low coverage finding(s) in Code Coverage — start with EntityId.fs, Inventory.fs, ValueTypes.fs; Resolve the 1 No ADRs found finding(s) in ADR Quality.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Codify backups + geo-recovery in IaC and document RTO/RPO and the restore procedure — a persistence guard alone is not disaster recovery. | +6.9 pts | Medium | DR & Backup |
| Resolve the 28 Low coverage finding(s) in Code Coverage — start with EntityId.fs, Inventory.fs, ValueTypes.fs. | +6.0 pts | Medium | Code Coverage |
| Resolve the 1 No ADRs found finding(s) in ADR Quality. | +2.5 pts | Low | ADR Quality |
| Resolve the 4 High secret finding(s) in Secrets (history) — start with REDACTED (4). | +1.9 pts | Low | Secrets (history) |
| Resolve the 1 REDACTED finding(s) in Secrets (history) — start with REDACTED. | +1.2 pts | Low | Secrets (history) |
| Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. | +1.2 pts | Low | Static Analysis (SAST) |
| Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. | +1.2 pts | Low | Static Analysis (SAST) |
| Resolve the 3 High IaC finding(s) in IaC & Container Security — start with REDACTED, REDACTED, REDACTED. | +1.2 pts | Low | IaC & Container Security |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 1.4 | Slop | Secrets (history): High secret: REDACTED |
| REDACTED | 1.4 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.4 | Mixed | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 4.4 | Mixed | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 5.1 | Mixed | IaC & Container Security: High IaC: REDACTED |
| src/CQRS.Application.CommandProcessingStatusRecording/CommandProcessingStatusRecordingService.fs | 7.8 | Mixed | Code Duplication: Duplicated block (14 lines × 2) |
| src/CQRS.Adapters.InMemoryEventStore/InMemoryEventStoreAdapter.fs | 8.5 | Near-clean | Code Duplication: Duplicated block (40–44 lines × 2) |
| src/CQRS.Adapters.MartenDbProjectionStore/MartenDbProjectionStoreAdapter.fs | 8.5 | Near-clean | Code Duplication: Duplicated block (11–12 lines × 2) |
| src/CQRS.CLI/AddItemsToInventoryCommand.fs | 8.5 | Near-clean | Code Duplication: Duplicated block (12 lines × 2) |
| src/CQRS.CLI/DeactivateInventoryCommand.fs | 8.5 | Near-clean | Code Duplication: Duplicated block (8 lines × 2) |
| src/CQRS.Domain/InventoryAggregate.fs | 8.5 | Near-clean | Code Duplication: Duplicated block (6 lines × 2) |
| src/CQRS.API/ApiRoutes.fs | 8.5 | Near-clean | Code Duplication: Duplicated block (6 lines × 3) |
| src/CQRS.EntityIds/EntityId.fs | 8.5 | Near-clean | Code Coverage: Low coverage: src/CQRS.EntityIds/EntityId.fs |
| src/CQRS.Domain/Inventory.fs | 8.5 | Near-clean | Code Coverage: Low coverage: src/CQRS.Domain/Inventory.fs |
| src/CQRS.Domain/ValueTypes.fs | 8.5 | Near-clean | Code Coverage: Low coverage: src/CQRS.Domain/ValueTypes.fs |
| src/CQRS.DTO/V1/InventoryMessages.fs | 8.5 | Near-clean | Code Coverage: Low coverage: src/CQRS.DTO/V1/InventoryMessages.fs |
| src/CQRS.DTO/V1/InventoryState.fs | 8.5 | Near-clean | Code Coverage: Low coverage: src/CQRS.DTO/V1/InventoryState.fs |
| src/CQRS.DTO/Json.fs | 8.5 | Near-clean | Code Coverage: Low coverage: src/CQRS.DTO/Json.fs |
| src/CQRS.Mapping/InventoryState'.fs | 8.5 | Near-clean | Code Coverage: Low coverage: src/CQRS.Mapping/InventoryState'.fs |
| src/CQRS.Mapping/InventoryEvent'.fs | 8.5 | Near-clean | Code Coverage: Low coverage: src/CQRS.Mapping/InventoryEvent'.fs |
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 48 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 — 48 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, 61 of 70 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Canine Code Analyzer duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy · checkov | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 · 3.2.533 | ✓ deterministic |
Run transparency — what happened this run
- D12 Dependency Hygiene — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `dotnet list package` did not return usable output (restore or query failed); no outdated/vulnerable/deprecated data to assess. The tool said: `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 105 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.
- D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D21's deterministic naming rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. Until then its declarations carry no naming verdict this run — this says nothing about whether its names are consistent.
- D22 Internal API Consistency — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. This repository's source is written only in languages whose packages are published through a manifest, and no manifest in the tree makes a publication act: either there is no package manifest of any ecosystem (no package.json, pyproject.toml, setup.py, gemspec, Cargo.toml, pom.xml, build.gradle, composer.json, pubspec.yaml or mix.exs), or every one present declares in its package manager's own terms that it is not published (an npm package marked "private": true, a Cargo package with publish = false, a pubspec with publish_to: none, a Composer "project", a Poetry project with package-mode = false, or the "Private :: Do Not Upload" classifier). With no publication act there is no intentionally-exposed surface for API consistency to be judged over.
- D23 Boundary Type-Coupling — 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 measured 0/40 valid on a seeded held-out sample of its rows on 98 C# repositories (docs/plans/deterministic-engine/adjudication/P5c-D23-units.md, "Version 1 ON MAIN"): the noise rows were dependencies on layer folders, shared cores and grouping folders read as contexts. By the pre-registered fallback (PREREGISTRATION v37) it publishes no row until version 4 passes its gate. The candidates are counted here, not reported as findings, and the score does not include them.
- D24 Comment Value — 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's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
- D39 IL Efficiency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. IL NOT MEASURED: the analyzer's own build of this repository failed for an ENVIRONMENT reason (exit 1) — MSBuild's engine or the CLR gave up, or our image does not carry the SDK band/targeting pack this repository needs. This is OUR limitation, not a defect in the repo, and it is not a statement that this repository fails to build. D18 owns the question of whether this repository builds; it was not answered here.
- D44 Platform End-of-Life — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This dimension reads a project's own statement about the platform it runs on: a TargetFramework in a .NET project file, a .nvmrc or .python-version, a capped requires-python, a Rust toolchain file or Cargo.toml rust-version, a .go-version, .java-version, .ruby-version, .tool-versions or .sdkmanrc, a go.mod go directive, a Maven or Gradle Java level or toolchain, a Gemfile's ruby directive, a mix.exs elixir requirement, a rebar.config minimum_otp_vsn, a pubspec.yaml SDK constraint, a build.sbt scalaVersion, or a framework major pinned by a dependency constraint. This repository carries none of them, so nothing about its platform was established. That is a gap in this analyzer's coverage, NOT a finding that the platform is supported — a language whose runtime is declared elsewhere (Package.swift, a Dockerfile) is simply not read here yet.
- AX1 Captive dependencies — 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 reads Microsoft.Extensions.DependencyInjection registrations in C# and Spring beans in Java/Kotlin only, and this repository's container is Microsoft.Extensions.DependencyInjection registered from F#, whose lifetimes are not modelled yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- AX6 Interface segregation — 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 is computed over the public interfaces this run's compilations declare, and none was loaded, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- AXR1 Runtime accessibility — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via DockerCompose (REDACTED). compose up failed (exit 17 — an image could not be built) — time="2026-11-10T00:17:57Z" level=warning msg="The \"RABBITMQ_PASSWORD\" variable is not set. Defaulting to a blank string." failed to solve: failed to compute cache key: failed to calculate checksum of ref c9a3eea9-d0da-4c59-b734-93267cd43ed3::mbz2agz7puodrp3p8dponf5ru: "/bin/publish": not found; runtime evidence skipped.
- C1 Data Protection — 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. These personal data controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks personal data controls.
- C2 Access Controls — 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. These authorization controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks authorization controls.
- C3 Audit Trail — 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. These audit controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks audit controls.
- C4 Data Retention — 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. These retention controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks retention controls.
- C5 Data-Subject Rights — 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. These data-subject rights controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks data-subject rights controls.
- 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.
- DM9 Scattered domain decisions — 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. Not measured — scattered-decision detection needs expression-level symbol resolution: a comparison operand bound to the member it judges (arm one) and a construction bound to the type it produces (arm two). A Roslyn compilation carries both; arm two alone also runs on any frontend that declares whether a construction is produced or passed, and this target loaded neither.
- 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 decides whether a handler's mutation is safe to re-run by recognising its persistence writes (a database save, a repository write, an event publish) and its guards. Those markers are .NET member names, so in this repository's language a write such as `repository.save(order)` is not recognised and a same-named call on an unrelated library type could be. The handlers were found; their idempotency was neither confirmed nor ruled out.
- ES3 PII in the event store — 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 persisted events that carry personal data no crypto-shredding strategy covers. It measured 12 of 13 valid (92.3 %) on held-out repositories, below the 95 % it must show (docs/plans/deterministic-engine/adjudication/ES3-H3H4.md), so by the pre-registered fallback (PREREGISTRATION v21) the events it finds are counted here, not reported as findings, and the card carries no score. That is a limit of the analyzer, not a finding about your code.
- IC1 Incompleteness & stubs — 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 is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- M4 Documentation accuracy — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
- P8 Schema migrations — 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 reads EF Core usage in C# and the schema tooling its file scan recognises only, and no .NET project was loaded, and this repository's language is not one the scan models, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- S1 Web-Security Posture — 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. These web-security controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks web-security controls.
- X1 Async correctness — 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 is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X12 Unreachable branch — 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 is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X13 Undrained process stream — 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 is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X14 Bypassable address classification — 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 is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X15 Unvalidated length from an untrusted reader — 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 is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X16 Unfloored truncation loop — 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 is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X17 Uncapped recursion over a caller-supplied document — 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 is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X18 Disposal-pattern correctness — 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 is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X19 Unrestored process-global state — 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 is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X2 Cancellation propagation — 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 is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X21 Side-effecting pattern guard — 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 is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X22 Contradicted release guard — 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 is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X24 Document value interpolated into markup unescaped — 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 is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X25 Inert configuration knob — 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 is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X26 Unsynchronised callback handoff — 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 is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X29 Per-element action decided by a fixed element — 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 is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X3 Exception handling — 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 is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X30 Support guard that admits what it rejects — 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 is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X32 Type resolved by simple name across every loaded assembly — 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 is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X4 Structured logging — 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 is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X5 Nullable reference types — 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 is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X6 Hand-rolled structured-format parsing — 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 reads C# syntax, and Python, JavaScript/TypeScript, Go, Java/Kotlin/Scala, Ruby, PHP, Rust, Swift, Erlang, Elixir and Dart source only, and no C# was loaded and none of those languages was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X7 Silent fallback defaults — 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 reads C#, Python, TypeScript/JavaScript, Rust, Go, Java, Kotlin, Scala, PHP, Ruby, Swift and Dart syntax only, and no C#, Python, TypeScript/JavaScript, Rust, Go, Java, Kotlin, Scala, PHP, Ruby, Swift or Dart was loaded for this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
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.
- D8 Code Coverage: Coverage is measured by building and running the test suite inside our isolated image — the target repo is never modified, and nothing on your systems runs. So coverage exists only when the suite builds and runs within the inline time budget; one that needs external services, can't build, or exceeds the budget yields no coverage (D8 then degrades to not-measured, not a low score). Line coverage also says nothing about assertion quality.
- 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 REDACTED Scanning: REDACTED 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.
- 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.
- D23 Boundary Type-Coupling: Boundary leakage is detected from type references across detected contexts — leaks that flow through primitives, serialization or shared infrastructure may not surface as a typed reference.
- D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
- D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- 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.
- DM6 Domain ↔ infrastructure boundary: Infrastructure reached through a hand-rolled wrapper, a domain-named facade, reflection, or a string-keyed service locator resolves to a non-infra type and isn't seen; the body scan is symbol resolution over syntax, not full dataflow. A clean result means "no resolved infra reference in a domain body", not a proof of purity.
- M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
- P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
- P5 DR & Backup: Backup/restore and disaster-recovery readiness is judged from in-repo evidence — a config that exists is not a tested restore, so the absence of positive evidence is reported as "not evidenced", never scored as present.
- P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
Dimensions
D1 · Cyclomatic Complexity
0 method(s) exceeded the cyclomatic complexity threshold of 15.
D2 · Cognitive Complexity
0 method(s) exceeded the cognitive complexity threshold of 15.
D3 · God Classes
0 god class(es) detected.
D4 · Code Duplication
8 duplicated block group(s) detected.
What to do
- Resolve the 1 Duplicated block (40–44 lines × 2) finding(s) in Code Duplication — start with InMemoryEventStoreAdapter.fs. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Duplicated block (14 lines × 2) finding(s) in Code Duplication — start with CommandProcessingStatusRecordingService.fs. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Duplicated block (11–12 lines × 2) finding(s) in Code Duplication — start with MartenDbProjectionStoreAdapter.fs. — One of this dimension's main actionable groups (1 warning-level).
D5 · Coupling
31 projects, 0 dependency cycle(s), 0 unstable depended-on project(s).
D6 · Cohesion (LCOM4)
0 of 8 classes have LCOM4 above 3.
D8 · Code Coverage
Line coverage 37.1% — 28 file(s) below 50%.
What to do
- Resolve the 28 Low coverage finding(s) in Code Coverage — start with EntityId.fs, Inventory.fs, ValueTypes.fs. — One of this dimension's main actionable groups (28 warning-level).
D11 · Test Reliability
0 flaky across 1 measured tier(s). unit: measured (0 flaky).
D13 · REDACTED Scanning
REDACTED scan ran and found no leaked secrets.
D14 · License Compliance
0 of 238 packages use a banned license. ★ DEPTH: this repository's MSBuild projects declare 31 direct `PackageReference`(s), and 207 further package(s) were reached beyond them by closing the graph over nuget.org's own nuspec dependency graph — so a banned licence pulled in only by a dependency's OWN dependencies is inside this verdict. A package whose licence nuget.org could not be asked for is not graded, and version ranges are taken at their lower bound, so this is the closure as that graph states it rather than a restored consumer's exact resolution.
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window.
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).
D23 · Boundary Type-Coupling
1 domain type(s) cross context boundaries across 2 contexts; they are measured and withheld (not published, not scored). Contexts: CQRS.Domain, CQRS.Projections.
D26 · Project Cohesion
0 of 26 build units (MSBuild) flagged as possibly oversized/incoherent.
D27 · Navigability
90 % of calls cross a namespace and 4 % go through an interface, but 100 % of collaborators are co-located — so a call's collaborators sit together and tracing stays easy. Baseline: small — navigation cost is tolerated.
D28 · Secrets (history)
5 finding(s): 0 critical, 5 high, 0 medium, 0 low. Remediation for historically-committed secrets is credential rotation — they remain in history regardless of later deletion.
What to do
- Resolve the 4 High secret finding(s) in Secrets (history) — start with REDACTED (4). — One of this dimension's main actionable groups (4 issue-level).
- Resolve the 1 REDACTED finding(s) in Secrets (history) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 1 Rotate the exposed credentials finding(s) in Secrets (history). — One of this dimension's main actionable groups (1 recommendation-level).
D29 · Static Analysis (SAST)
5 finding(s): 0 critical, 5 high, 0 medium, 0 low. 3 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. semgrep hit a parse error in 1 file(s) — `build.ps1` — so no absence of findings in them is evidence of anything, and nothing in them was analysed. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them. Separately, one or more rules could not re-parse an embedded snippet in 1 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.
What to do
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- No action in Static Analysis (SAST) — all 3 REDACTED finding(s) are reported here at file:line but scored by D36 (supply-chain provenance), so none is charged to this dimension. — One of this dimension's main actionable groups (3 issue-level, 0 of them charged here).
D31 · IaC & Container Security
10 finding(s): 0 critical, 3 high, 5 medium, 2 low.
What to do
- Resolve the 3 High IaC finding(s) in IaC & Container Security — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (3 issue-level).
- Resolve the 5 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (2), REDACTED, REDACTED. — One of this dimension's main actionable groups (5 warning-level).
- Resolve the 2 Low IaC finding(s) in IaC & Container Security — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 recommendation-level).
D34 · Knowledge Freshness
Every significant source file has living knowledge — recently and meaningfully worked. Counted over 17 of the 92 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
D35 · Change Coupling
No strong hidden change-coupling between production files.
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
Frontend & cross-cutting dimensions
AX10 · Code composition
AX3 · Project dependency cycles
AX4 · Dependency direction
AX5 · Architecture & structure
AX8 · Test isolation
DM1 · Aggregate boundaries
DM10 · One transaction, one aggregate
DM12 · Ambient inputs in the domain
DM6 · Domain ↔ infrastructure boundary
ES1 · Fold determinism
ES2 · Immutable events
GD1 · Unfinished & placeholder code
M1 · Documentation (README)
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
M3 · Folder & project structure
M4 · Documentation accuracy
- doc/solution-structure.md names .NET 9, but the projects target .NET 10. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — doc/solution-structure.md:3
What to do
- Reconcile the README with reality: doc/solution-structure.md names .NET 9, but the projects target .NET 10.
P1 · CI/CD gates
P2 · Observability
- Only 9/11 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `src/CQRS.API.Host`, `src/CQRS.Application.Host`.
What to do
- Extend structured logging to the remaining runnable modules so everything you run is diagnosable in production.
- Add OpenTelemetry tracing/metrics (OpenTelemetry.Extensions.Hosting with the ASP.NET Core instrumentation) so requests are traceable across the system, not just health-probable.
P3 · Security & performance tooling
- No static application security testing detected. For this repository's stack, add `semgrep --config=auto` plus gitleaks for committed secrets (F# is not a CodeQL language and has no language-specific SAST engine) as a CI step. What was searched, so you can tell an absence from a miss: the 1 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:7
What to do
- Add a SAST step to CI running what this repository's stack ships: `semgrep --config=auto` plus gitleaks for committed secrets (F# is not a CodeQL language and has no language-specific SAST engine) — 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.
P4 · Deployment & Rollback
- Deployment is orchestrated by compose, but no service declares a `healthcheck:` and nothing pins a previous image to fall back to — the runtime can tell that the container is up, not that it is serving, so a bad release is harder to detect and reverse.
What to do
- Add a `healthcheck:` to the served compose service — probing the endpoint it already answers on where it has one — with `depends_on: condition: service_healthy` on whatever waits for it, and keep the deployed image tag immutable and recorded so rolling back is re-pointing at the previous tag rather than rebuilding.
- Add an approval/environment gate (required reviewers / protection rules) before production promotion.
P5 · DR & Backup
- A persistence guard (data volume / purge-protection) was found, but no backup, geo-recovery or RTO/RPO controls were evidenced — a volume that survives a container recreate is not a tested restore from catastrophic loss.
What to do
- Codify backups + geo-recovery in IaC and document RTO/RPO and the restore procedure — a persistence guard alone is not disaster recovery.
P6 · Release Hygiene
- No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
What to do
- Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.
PF3 · Async & latency hygiene
X20 · Mistyped argument guard
X23 · Unguarded diagnostic materialisation
X27 · Collection changed while being enumerated
X28 · Index access outside its own emptiness guard
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 98% | Checked 4 of 12 | Solid. |
| Architecture | 86% | Strong | Solid. |
| Maturity | 75% | Strong | Solid. |
| Readiness | 35% | Weak — gated by P3, P5 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 68% | Checked 4 of 11 | Acceptable, with room to improve. |
| Domain Modelling | 100% | Exemplary | Strongest area. |
| Event Sourcing | 100% | Exemplary | Solid. |
| Performance | 100% | Exemplary | Solid. |
Unscored — 2 check(s) recorded observations but carry no score
- D36 Supply-chain Provenance & Signing — 2 observation(s) recorded · The CI pipeline publishes no artifact — no package publish, container push or release with files to download. Supply-chain provenance, signing and an SBOM describe a PUBLISHED artifact for the people who obtain it, so there is nothing to attest here; a deployment of the service itself publishes nothing for anyone else to verify. Add them to the release pipeline when this repo starts publishing artifacts (a package, a container image, or a release with downloadable files). Build integrity and workflow-token hygiene are reported below: they describe what the CI runs and the token it runs with, neither of which is affected by whether the pipeline ships an artifact.
- X10 Duplicated predicate — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 3 control(s) we could not find positive evidence for
- C3 Audit Trail — Not assessed: these audit controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks audit controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- C4 Data Retention — Not assessed: these retention controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks retention controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- C5 Data-Subject Rights — Not assessed: these data-subject rights controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks data-subject rights controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
Not included — 80 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.
- AX1 Captive dependencies — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX2 Stateful singletons — No container singleton was found, so there is no shared instance for concurrent requests to race on. No F# function in this code takes an ASP.NET Core or Suave HttpContext (a Giraffe, Saturn, Falco, Oxpecker or Suave handler) and no F# class is an ASP.NET Core controller, so no request handler shares module state between request threads.
- AX6 Interface segregation — not assessed — interface segregation is computed over a type surface that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about 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 — compose up failed (exit 17 — an image could not be built) — time="2026-11-10T00:17:57Z" level=warning msg="The \"RABBITMQ_PASSWORD\" variable is not set. Defaulting to a blank string." failed to solve: failed to compute cache key: failed to calculate checksum of ref c9a3eea9-d0da-4c59-b734-93267cd43ed3::mbz2agz7puodrp3p8dponf5ru: "/bin/publish": not found; runtime evidence skipped This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
- C1 Data Protection — Not assessed: these personal data controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks personal data controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- C2 Access Controls — Not assessed: these authorization controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks authorization controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- D10 Test Quality — ~714 lines of test source are present (.fs) but no test cases reached the test census for this repository — no test root we could resolve declared them, or the files we read declare no cases in a test framework we recognise — so skipped/assertion-free tests couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
- D12 Dependency Hygiene — Dependency hygiene not measured
- D16 Bus Factor — single-contributor repository — bus factor is not applicable
- D17 Explicit Debt — the C# workspace loaded 0 projects, so explicit-debt density could not be measured
- D18 Solution Shape — D18 scores the shape of a C#/VB .NET solution; this repository's .NET projects are all F# (.fsproj), which the C#/VB workspace does not load, so the dimension does not apply.
- D19 Documentation Quality — No runnable or published unit to look for an example in, and no multi-project root README to look for a map in; the other documentation kinds are withheld (see the gaps), so documentation quality is not applicable here.
- D21 Naming Consistency — Naming consistency is measured on C# and TypeScript only; F# not measured.
- D22 Internal API Consistency — No intentionally-exposed public API to evaluate for consistency.
- D24 Comment Value — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only — this repository's production source is .fs, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D25 ADR Conformance — no ADRs to check
- D30 Dependency Vulnerabilities — nuget: the solution did not restore on the analyzer's .NET SDK (an SDK/target-framework/restore mismatch, common for an older codebase), so there was no restored dependency graph to scan
- D32 Data Compliance (PII/GDPR) — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- D39 IL Efficiency — IL not measured — the analyzer's build of the target did not succeed
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D44 Platform End-of-Life — Platform end-of-life not assessed — this repository declares no platform this pass reads
- D7 Architectural Integrity — no checkable ADRs and no dependency cycles — architectural integrity not assessed
- D9 Test Distribution — Test source is present (.fs) but no test cases reached the test census for this repository — no test root we could resolve declared them, or the files we read declare no cases in a test framework we recognise — so its unit/integration/BDD/E2E split couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
- DM11 Constructible invalid state — no entities detected — construction-time invariants not assessable
- DM2 Strongly-typed ids — no id-bearing domain types detected — strongly-typed-id adoption not assessable
- DM3 Integration-event coupling — no integration events detected — coupling check not applicable
- DM4 Rich vs anemic model — no data-bearing entities detected — rich-vs-anemic model not assessable
- DM5 Encapsulated state — no domain entities found — DM5 grades how entities protect their state, and this repository declares none
- 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)
- DM9 Scattered domain decisions — not measured — scattered-decision detection needs expression-level symbol resolution: a comparison operand bound to the member it judges (arm one) and a construction bound to the type it produces (arm two). A Roslyn compilation carries both; arm two alone also runs on any frontend that declares whether a construction is produced or passed, and this target loaded neither
- ED1 Event-Driven — applicable but not scored (2 of 3 signals for this style — below the bar we score at): 6 event handler(s); a message-bus package
- ED5 Idempotency — Not assessed, and this one is on us: 132 command handler(s) or message consumer(s) were found here, but this check does not yet recognise persistence writes in this repository's language. Idempotency was neither confirmed nor ruled out — this is a limit of the analyzer, not a finding about your code.
- ES3 PII in the event store — This check finds persisted events that carry personal data no crypto-shredding strategy covers. It measured 12 of 13 valid (92.3 %) on held-out repositories, below the 95 % it must show (docs/plans/deterministic-engine/adjudication/ES3-H3H4.md), so by the pre-registered fallback (PREREGISTRATION v21) the events it finds are counted here, not reported as findings, and the card carries no score. That is a limit of the analyzer, not a finding about your code.
- IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
- P7 Outbound HTTP resilience — not measured — the application kind could not be determined for this repo
- P8 Schema migrations — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (Cobertura — `dotnet test --collect:"XPlat Code Coverage"` with a `coverlet.collector` PackageReference) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures, or wire coverage collection into CI, to enable this cross-layer check
- PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for a BenchmarkDotNet reference in an .fsproj or .vbproj, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
- 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.
- S1 Web-Security Posture — Not assessed: these web-security controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks web-security controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X1 Async correctness — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X12 Unreachable branch — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X13 Undrained process stream — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X14 Bypassable address classification — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X15 Unvalidated length from an untrusted reader — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X16 Unfloored truncation loop — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X17 Uncapped recursion over a caller-supplied document — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X18 Disposal-pattern correctness — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X19 Unrestored process-global state — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X2 Cancellation propagation — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X21 Side-effecting pattern guard — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X22 Contradicted release guard — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X24 Document value interpolated into markup unescaped — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X25 Inert configuration knob — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X26 Unsynchronised callback handoff — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X29 Per-element action decided by a fixed element — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X3 Exception handling — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X30 Support guard that admits what it rejects — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X32 Type resolved by simple name across every loaded assembly — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X4 Structured logging — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X5 Nullable reference types — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X6 Hand-rolled structured-format parsing — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X7 Silent fallback defaults — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- 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 — 13 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
Serious — 44 finding(s)
- Low coverage: src/CQRS.EntityIds/EntityId.fs src/CQRS.EntityIds/EntityId.fs:1
- Low coverage: src/CQRS.Domain/Inventory.fs src/CQRS.Domain/Inventory.fs:1
- Low coverage: src/CQRS.Domain/ValueTypes.fs src/CQRS.Domain/ValueTypes.fs:1
- Low coverage: src/CQRS.DTO/V1/InventoryMessages.fs src/CQRS.DTO/V1/InventoryMessages.fs:1
- Low coverage: src/CQRS.DTO/V1/InventoryState.fs src/CQRS.DTO/V1/InventoryState.fs:1
- Low coverage: src/CQRS.DTO/Json.fs src/CQRS.DTO/Json.fs:1
- Low coverage: src/CQRS.Mapping/InventoryState'.fs src/CQRS.Mapping/InventoryState'.fs:1
- Low coverage: src/CQRS.Mapping/InventoryEvent'.fs src/CQRS.Mapping/InventoryEvent'.fs:1
- Low coverage: src/CQRS.Mapping/InventoryCommand'.fs src/CQRS.Mapping/InventoryCommand'.fs:1
- Low coverage: src/CQRS.Mapping/InventoryDeactivated'.fs src/CQRS.Mapping/InventoryDeactivated'.fs:1
- Low coverage: src/CQRS.Mapping/ItemWentOutOfStock'.fs src/CQRS.Mapping/ItemWentOutOfStock'.fs:1
- Low coverage: src/CQRS.Mapping/ItemInStock'.fs src/CQRS.Mapping/ItemInStock'.fs:1
- Low coverage: src/CQRS.Mapping/ItemsRemovedFromInventory'.fs src/CQRS.Mapping/ItemsRemovedFromInventory'.fs:1
- Low coverage: src/CQRS.Mapping/ItemsAddedToInventory'.fs src/CQRS.Mapping/ItemsAddedToInventory'.fs:1
- Low coverage: src/CQRS.Mapping/InventoryRenamed'.fs src/CQRS.Mapping/InventoryRenamed'.fs:1
- Low coverage: src/CQRS.Mapping/InventoryCreated'.fs src/CQRS.Mapping/InventoryCreated'.fs:1
- Low coverage: src/CQRS.Mapping/DeactivateInventory'.fs src/CQRS.Mapping/DeactivateInventory'.fs:1
- Low coverage: src/CQRS.Mapping/RemoveItemsFromInventory'.fs src/CQRS.Mapping/RemoveItemsFromInventory'.fs:1
- Low coverage: src/CQRS.Mapping/AddItemsToInventory'.fs src/CQRS.Mapping/AddItemsToInventory'.fs:1
- Low coverage: src/CQRS.Mapping/RenameInventory'.fs src/CQRS.Mapping/RenameInventory'.fs:1
- Low coverage: src/CQRS.Mapping/CreateInventory'.fs src/CQRS.Mapping/CreateInventory'.fs:1
- Low coverage: src/CQRS.Mapping/InventoryValueTypesMapper.fs src/CQRS.Mapping/InventoryValueTypesMapper.fs:1
- Low coverage: src/CQRS.Mapping/NullableDto'.fs src/CQRS.Mapping/NullableDto'.fs:1
- Low coverage: src/CQRS.Application/IMoonPhaseService.fs src/CQRS.Application/IMoonPhaseService.fs:1
- Low coverage: src/CQRS.Application/InventoryEventStreamDtoMapper.fs src/CQRS.Application/InventoryEventStreamDtoMapper.fs:1
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Duplicated block (40–44 lines × 2) src/CQRS.Adapters.InMemoryEventStore/InMemoryEventStoreAdapter.fs:50
- Duplicated block (14 lines × 2) src/CQRS.Application.CommandProcessingStatusRecording/CommandProcessingStatusRecordingService.fs:151
- Duplicated block (11–12 lines × 2) src/CQRS.Adapters.MartenDbProjectionStore/MartenDbProjectionStoreAdapter.fs:45
- Duplicated block (12 lines × 2) src/CQRS.CLI/AddItemsToInventoryCommand.fs:9
- Duplicated block (8 lines × 2) src/CQRS.CLI/DeactivateInventoryCommand.fs:9
- Duplicated block (6 lines × 2) src/CQRS.Domain/InventoryAggregate.fs:32
- Duplicated block (6 lines × 3) src/CQRS.API/ApiRoutes.fs:35
- Duplicated block (5 lines × 2) src/CQRS.Application.CommandProcessingStatusRecording/CommandProcessingStatusRecordingService.fs:28
- No DR/backup evidence
Minor — 13 finding(s)
- REDACTED
- REDACTED
- No ADRs found
- REDACTED
- REDACTED
- No ADRs
- README/code drift doc/solution-structure.md:3
- Logging is not universal
- No SAST
- No dependency-update automation src/Directory.Packages.props:7
- No rollback/health safety
- No changelog
- Duplicated predicate src/CQRS.CLI/AddItemsToInventoryCommand.fs:19
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-8bb2be7186084b67905e8147ec4ef534/history.json --exit-code 0 --source . | 2 | 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-8bb2be7186084b67905e8147ec4ef534/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 . | 5 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | nuget | — | nuget: not applicable — nuget: the solution did not restore on the analyzer's .NET SDK (an SDK/target-framework/restore mismatch, common for an older codebase), so there was no restored dependency graph to scan | 0 | — |
| D31 · IaC & Container Security | trivy | — | trivy config --format json --quiet . | 10 | artifacts/raw/trivy-config.json |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. | 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-b06ebbf5519f4d27b410524a84cfb6ca | 0 | artifacts/raw/osv-scanner.json |