Executive summary
cloud.yantra.oss/microservice-patterns-cqrs falls short of our standard for production, in part because the project keeps no record of its design decisions. It scores 63 out of 100 and is rated Adequate, and none of its three critical findings concern security.
Maturity, at 58, is the weakest lens by a small margin, and the weakest lens counts most in the score. The best first step is recording design decisions, worth about 5 points. Completing the README is another step, worth about 3 points.
The three pieces of business logic tied to the database or web code need separating from the database and web code.
The product code is 3,158 lines, about €7,900 to rebuild.
The weakest lenses score close to each other, so improving any of them moves the score.
Rebuild cost: about €7,900 · Estimate
| Cost to rebuild | €2,600 to €13,000, for 44 to 139 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.9 at a score of 63. 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,158 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: which parts of the code depend on which
| uses → | 1 yantra | 2 yantra.patterns | 3 yantra.patterns.actors.commands.CommandHandlerActor | 4 yantra.patterns.actors.commands.CommandHandlerActor.Commands | 5 yantra.patterns.actors.commands.CommandProcessorManagerActor | 6 yantra.patterns.actors.entities.EntityManagerActor | 7 yantra.patterns.actors.entities.EntityManagerActor.Commands | 8 yantra.patterns.actors.entities.EntityPersistentActor | 9 yantra.patterns.actors.envelope | 10 yantra.patterns.cqrs.errors | 11 yantra.patterns.cqrs.errors.DomainError | 12 yantra.patterns.cqrs.stages | 13 yantra.patterns.javadsl.cqrs.domain | 14 yantra.patterns.javadsl.cqrs.errors | 15 yantra.patterns.actors.entities.EntityPersistentActor.Errors | 16 yantra.patterns.cqrs.stages.DomainProcessingStage | 17 yantra.patterns.es | 18 yantra.patterns.javadsl.cqrs.results | 19 yantra.patterns.actors.entities.EntityManagerActor.Events | 20 yantra.patterns.cqrs | 21 yantra.patterns.javadsl.cqrs.events | 22 yantra.patterns.actors.commands.CommandHandlerActor.Events | 23 yantra.patterns.actors.entities | 24 yantra.patterns.actors.entities.EntityPersistentActor.Commands | 25 yantra.patterns.actors.filters | 26 yantra.patterns.actors.serializer | 27 yantra.patterns.actors.serializer.CommandValidationJsonSerializer | 28 yantra.patterns.actors.validations | 29 yantra.patterns.actors.validations.CommandValidation | 30 yantra.patterns.actors.validations.ValidationRuleWorker | 31 yantra.patterns.cqrs.Version | 32 yantra.patterns.javadsl.cqrs | 33 yantra.patterns.actors.commands | 34 yantra.patterns.actors.errors |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 yantra | ||||||||||||||||||||||||||||||||||
| 2 yantra.patterns | ||||||||||||||||||||||||||||||||||
| 3 yantra.patterns.actors.commands.CommandHandlerActor | ||||||||||||||||||||||||||||||||||
| 4 yantra.patterns.actors.commands.CommandHandlerActor.Commands | ||||||||||||||||||||||||||||||||||
| 5 yantra.patterns.actors.commands.CommandProcessorManagerActor | ||||||||||||||||||||||||||||||||||
| 6 yantra.patterns.actors.entities.EntityManagerActor | ||||||||||||||||||||||||||||||||||
| 7 yantra.patterns.actors.entities.EntityManagerActor.Commands | ||||||||||||||||||||||||||||||||||
| 8 yantra.patterns.actors.entities.EntityPersistentActor | ||||||||||||||||||||||||||||||||||
| 9 yantra.patterns.actors.envelope | ||||||||||||||||||||||||||||||||||
| 10 yantra.patterns.cqrs.errors | ||||||||||||||||||||||||||||||||||
| 11 yantra.patterns.cqrs.errors.DomainError | ||||||||||||||||||||||||||||||||||
| 12 yantra.patterns.cqrs.stages | ||||||||||||||||||||||||||||||||||
| 13 yantra.patterns.javadsl.cqrs.domain | ||||||||||||||||||||||||||||||||||
| 14 yantra.patterns.javadsl.cqrs.errors | ||||||||||||||||||||||||||||||||||
| 15 yantra.patterns.actors.entities.EntityPersistentActor.Errors | 1 | |||||||||||||||||||||||||||||||||
| 16 yantra.patterns.cqrs.stages.DomainProcessingStage | 4 | |||||||||||||||||||||||||||||||||
| 17 yantra.patterns.es | 1 | 1 | ||||||||||||||||||||||||||||||||
| 18 yantra.patterns.javadsl.cqrs.results | 1 | |||||||||||||||||||||||||||||||||
| 19 yantra.patterns.actors.entities.EntityManagerActor.Events | 1 | |||||||||||||||||||||||||||||||||
| 20 yantra.patterns.cqrs | 1 | 2 | 4 | |||||||||||||||||||||||||||||||
| 21 yantra.patterns.javadsl.cqrs.events | 1 | 1 | 2 | |||||||||||||||||||||||||||||||
| 22 yantra.patterns.actors.commands.CommandHandlerActor.Events | 6 | 6 | 8 | |||||||||||||||||||||||||||||||
| 23 yantra.patterns.actors.entities | 3 | 3 | ||||||||||||||||||||||||||||||||
| 24 yantra.patterns.actors.entities.EntityPersistentActor.Commands | 4 | 6 | ||||||||||||||||||||||||||||||||
| 25 yantra.patterns.actors.filters | 3 | |||||||||||||||||||||||||||||||||
| 26 yantra.patterns.actors.serializer | 1 | 2 | ||||||||||||||||||||||||||||||||
| 27 yantra.patterns.actors.serializer.CommandValidationJsonSerializer | 6 | |||||||||||||||||||||||||||||||||
| 28 yantra.patterns.actors.validations | 3 | 4 | ||||||||||||||||||||||||||||||||
| 29 yantra.patterns.actors.validations.CommandValidation | 8 | 3 | 8 | |||||||||||||||||||||||||||||||
| 30 yantra.patterns.actors.validations.ValidationRuleWorker | 6 | |||||||||||||||||||||||||||||||||
| 31 yantra.patterns.cqrs.Version | 1 | |||||||||||||||||||||||||||||||||
| 32 yantra.patterns.javadsl.cqrs | 4 | 2 | ||||||||||||||||||||||||||||||||
| 33 yantra.patterns.actors.commands | 5 | 2 | 1 | |||||||||||||||||||||||||||||||
| 34 yantra.patterns.actors.errors | 3 | 1 | 1 |
15→10 yantra.patterns.actors.entities.EntityPersistentActor.Errors uses yantra.patterns.cqrs.errors✕
- Connections
- 1 pair of types, where a type in yantra.patterns.actors.entities.EntityPersistentActor.Errors uses a type in yantra.patterns.cqrs.errors.
- The types involved
cloud.yantra.patterns.actors.entities.EntityPersistentActor.Errors.PersistException→cloud.yantra.patterns.cqrs.errors.DomainError
- Direction
- yantra.patterns.actors.entities.EntityPersistentActor.Errors uses yantra.patterns.cqrs.errors, so a change to yantra.patterns.cqrs.errors can break yantra.patterns.actors.entities.EntityPersistentActor.Errors, while a change to yantra.patterns.actors.entities.EntityPersistentActor.Errors can't break yantra.patterns.cqrs.errors.
- Position
- Below the diagonal: yantra.patterns.actors.entities.EntityPersistentActor.Errors uses a module listed above it, which is the healthy direction.
16→12 yantra.patterns.cqrs.stages.DomainProcessingStage uses yantra.patterns.cqrs.stages✕
- Connections
- 4 pairs of types, where a type in yantra.patterns.cqrs.stages.DomainProcessingStage uses a type in yantra.patterns.cqrs.stages.
- The types involved
cloud.yantra.patterns.cqrs.stages.DomainProcessingStage.AggregateMutation→cloud.yantra.patterns.cqrs.stages.DomainProcessingStagecloud.yantra.patterns.cqrs.stages.DomainProcessingStage.BusinessValidation→cloud.yantra.patterns.cqrs.stages.DomainProcessingStagecloud.yantra.patterns.cqrs.stages.DomainProcessingStage.Received→cloud.yantra.patterns.cqrs.stages.DomainProcessingStagecloud.yantra.patterns.cqrs.stages.DomainProcessingStage.TechnicalValidation→cloud.yantra.patterns.cqrs.stages.DomainProcessingStage
- Direction
- yantra.patterns.cqrs.stages.DomainProcessingStage uses yantra.patterns.cqrs.stages, so a change to yantra.patterns.cqrs.stages can break yantra.patterns.cqrs.stages.DomainProcessingStage, while a change to yantra.patterns.cqrs.stages.DomainProcessingStage can't break yantra.patterns.cqrs.stages.
- Position
- Below the diagonal: yantra.patterns.cqrs.stages.DomainProcessingStage uses a module listed above it, which is the healthy direction.
17→10 yantra.patterns.es uses yantra.patterns.cqrs.errors✕
- Connections
- 1 pair of types, where a type in yantra.patterns.es uses a type in yantra.patterns.cqrs.errors.
- The types involved
cloud.yantra.patterns.es.ZeroEvent→cloud.yantra.patterns.cqrs.errors.DomainError
- Direction
- yantra.patterns.es uses yantra.patterns.cqrs.errors, so a change to yantra.patterns.cqrs.errors can break yantra.patterns.es, while a change to yantra.patterns.es can't break yantra.patterns.cqrs.errors.
- Position
- Below the diagonal: yantra.patterns.es uses a module listed above it, which is the healthy direction.
17→20 yantra.patterns.es uses yantra.patterns.cqrs part of a loop✕
- Connections
- 1 pair of types, where a type in yantra.patterns.es uses a type in yantra.patterns.cqrs.
- The types involved
cloud.yantra.patterns.es.Event→cloud.yantra.patterns.cqrs.Version
- Direction
- yantra.patterns.es uses yantra.patterns.cqrs, so a change to yantra.patterns.cqrs can break yantra.patterns.es, while a change to yantra.patterns.es can't break yantra.patterns.cqrs.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
18→14 yantra.patterns.javadsl.cqrs.results uses yantra.patterns.javadsl.cqrs.errors✕
- Connections
- 1 pair of types, where a type in yantra.patterns.javadsl.cqrs.results uses a type in yantra.patterns.javadsl.cqrs.errors.
- The types involved
cloud.yantra.patterns.javadsl.cqrs.results.Failure→cloud.yantra.patterns.javadsl.cqrs.errors.DomainError
- Direction
- yantra.patterns.javadsl.cqrs.results uses yantra.patterns.javadsl.cqrs.errors, so a change to yantra.patterns.javadsl.cqrs.errors can break yantra.patterns.javadsl.cqrs.results, while a change to yantra.patterns.javadsl.cqrs.results can't break yantra.patterns.javadsl.cqrs.errors.
- Position
- Below the diagonal: yantra.patterns.javadsl.cqrs.results uses a module listed above it, which is the healthy direction.
19→17 yantra.patterns.actors.entities.EntityManagerActor.Events uses yantra.patterns.es✕
- Connections
- 1 pair of types, where a type in yantra.patterns.actors.entities.EntityManagerActor.Events uses a type in yantra.patterns.es.
- The types involved
cloud.yantra.patterns.actors.entities.EntityManagerActor.Events.ObservedEvent→cloud.yantra.patterns.es.Event
- Direction
- yantra.patterns.actors.entities.EntityManagerActor.Events uses yantra.patterns.es, so a change to yantra.patterns.es can break yantra.patterns.actors.entities.EntityManagerActor.Events, while a change to yantra.patterns.actors.entities.EntityManagerActor.Events can't break yantra.patterns.es.
- Position
- Below the diagonal: yantra.patterns.actors.entities.EntityManagerActor.Events uses a module listed above it, which is the healthy direction.
20→10 yantra.patterns.cqrs uses yantra.patterns.cqrs.errors✕
- Connections
- 1 pair of types, where a type in yantra.patterns.cqrs uses a type in yantra.patterns.cqrs.errors.
- The types involved
cloud.yantra.patterns.cqrs.Failed→cloud.yantra.patterns.cqrs.errors.DomainError
- Direction
- yantra.patterns.cqrs uses yantra.patterns.cqrs.errors, so a change to yantra.patterns.cqrs.errors can break yantra.patterns.cqrs, while a change to yantra.patterns.cqrs can't break yantra.patterns.cqrs.errors.
- Position
- Below the diagonal: yantra.patterns.cqrs uses a module listed above it, which is the healthy direction.
20→12 yantra.patterns.cqrs uses yantra.patterns.cqrs.stages✕
- Connections
- 2 pairs of types, where a type in yantra.patterns.cqrs uses a type in yantra.patterns.cqrs.stages.
- The types involved
cloud.yantra.patterns.cqrs.CommandProcessor→cloud.yantra.patterns.cqrs.stages.DomainProcessingStagecloud.yantra.patterns.cqrs.CommandRepository→cloud.yantra.patterns.cqrs.stages.DomainProcessingStage
- Direction
- yantra.patterns.cqrs uses yantra.patterns.cqrs.stages, so a change to yantra.patterns.cqrs.stages can break yantra.patterns.cqrs, while a change to yantra.patterns.cqrs can't break yantra.patterns.cqrs.stages.
- Position
- Below the diagonal: yantra.patterns.cqrs uses a module listed above it, which is the healthy direction.
20→17 yantra.patterns.cqrs uses yantra.patterns.es✕
- Connections
- 4 pairs of types, where a type in yantra.patterns.cqrs uses a type in yantra.patterns.es.
- The types involved
cloud.yantra.patterns.cqrs.CommandValidationId→cloud.yantra.patterns.es.AggregateIdcloud.yantra.patterns.cqrs.EventCommand→cloud.yantra.patterns.es.Eventcloud.yantra.patterns.cqrs.QueryCommand→cloud.yantra.patterns.es.EntityIdcloud.yantra.patterns.cqrs.UpdateCommand→cloud.yantra.patterns.es.EntityId
- Direction
- yantra.patterns.cqrs uses yantra.patterns.es, so a change to yantra.patterns.es can break yantra.patterns.cqrs, while a change to yantra.patterns.cqrs can't break yantra.patterns.es.
- Position
- Below the diagonal: yantra.patterns.cqrs uses a module listed above it, which is the healthy direction.
21→13 yantra.patterns.javadsl.cqrs.events uses yantra.patterns.javadsl.cqrs.domain✕
- Connections
- 1 pair of types, where a type in yantra.patterns.javadsl.cqrs.events uses a type in yantra.patterns.javadsl.cqrs.domain.
- The types involved
cloud.yantra.patterns.javadsl.cqrs.events.DomainEvent→cloud.yantra.patterns.javadsl.cqrs.domain.AggregateId
- Direction
- yantra.patterns.javadsl.cqrs.events uses yantra.patterns.javadsl.cqrs.domain, so a change to yantra.patterns.javadsl.cqrs.domain can break yantra.patterns.javadsl.cqrs.events, while a change to yantra.patterns.javadsl.cqrs.events can't break yantra.patterns.javadsl.cqrs.domain.
- Position
- Below the diagonal: yantra.patterns.javadsl.cqrs.events uses a module listed above it, which is the healthy direction.
21→18 yantra.patterns.javadsl.cqrs.events uses yantra.patterns.javadsl.cqrs.results✕
- Connections
- 1 pair of types, where a type in yantra.patterns.javadsl.cqrs.events uses a type in yantra.patterns.javadsl.cqrs.results.
- The types involved
cloud.yantra.patterns.javadsl.cqrs.events.FailureEvent→cloud.yantra.patterns.javadsl.cqrs.results.Failure
- Direction
- yantra.patterns.javadsl.cqrs.events uses yantra.patterns.javadsl.cqrs.results, so a change to yantra.patterns.javadsl.cqrs.results can break yantra.patterns.javadsl.cqrs.events, while a change to yantra.patterns.javadsl.cqrs.events can't break yantra.patterns.javadsl.cqrs.results.
- Position
- Below the diagonal: yantra.patterns.javadsl.cqrs.events uses a module listed above it, which is the healthy direction.
21→32 yantra.patterns.javadsl.cqrs.events uses yantra.patterns.javadsl.cqrs part of a loop✕
- Connections
- 2 pairs of types, where a type in yantra.patterns.javadsl.cqrs.events uses a type in yantra.patterns.javadsl.cqrs.
- The types involved
cloud.yantra.patterns.javadsl.cqrs.events.DomainEvent→cloud.yantra.patterns.javadsl.cqrs.EventIdcloud.yantra.patterns.javadsl.cqrs.events.DomainEvent→cloud.yantra.patterns.javadsl.cqrs.Version
- Direction
- yantra.patterns.javadsl.cqrs.events uses yantra.patterns.javadsl.cqrs, so a change to yantra.patterns.javadsl.cqrs can break yantra.patterns.javadsl.cqrs.events, while a change to yantra.patterns.javadsl.cqrs.events can't break yantra.patterns.javadsl.cqrs.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
22→12 yantra.patterns.actors.commands.CommandHandlerActor.Events uses yantra.patterns.cqrs.stages✕
- Connections
- 6 pairs of types, where a type in yantra.patterns.actors.commands.CommandHandlerActor.Events uses a type in yantra.patterns.cqrs.stages.
- The types involved
cloud.yantra.patterns.actors.commands.CommandHandlerActor.Events.AggregateMutationSuccessful→cloud.yantra.patterns.cqrs.stages.DomainProcessingStagecloud.yantra.patterns.actors.commands.CommandHandlerActor.Events.BusinessValidationSuccessful→cloud.yantra.patterns.cqrs.stages.DomainProcessingStagecloud.yantra.patterns.actors.commands.CommandHandlerActor.Events.CommandProcessingEvent→cloud.yantra.patterns.cqrs.stages.DomainProcessingStagecloud.yantra.patterns.actors.commands.CommandHandlerActor.Events.CommandProcessingFailed→cloud.yantra.patterns.cqrs.stages.DomainProcessingStagecloud.yantra.patterns.actors.commands.CommandHandlerActor.Events.CommandReceived→cloud.yantra.patterns.cqrs.stages.DomainProcessingStagecloud.yantra.patterns.actors.commands.CommandHandlerActor.Events.TechnicalValidationSuccessful→cloud.yantra.patterns.cqrs.stages.DomainProcessingStage
- Direction
- yantra.patterns.actors.commands.CommandHandlerActor.Events uses yantra.patterns.cqrs.stages, so a change to yantra.patterns.cqrs.stages can break yantra.patterns.actors.commands.CommandHandlerActor.Events, while a change to yantra.patterns.actors.commands.CommandHandlerActor.Events can't break yantra.patterns.cqrs.stages.
- Position
- Below the diagonal: yantra.patterns.actors.commands.CommandHandlerActor.Events uses a module listed above it, which is the healthy direction.
22→17 yantra.patterns.actors.commands.CommandHandlerActor.Events uses yantra.patterns.es✕
- Connections
- 6 pairs of types, where a type in yantra.patterns.actors.commands.CommandHandlerActor.Events uses a type in yantra.patterns.es.
- The types involved
cloud.yantra.patterns.actors.commands.CommandHandlerActor.Events.AggregateMutationSuccessful→cloud.yantra.patterns.es.EntityIdcloud.yantra.patterns.actors.commands.CommandHandlerActor.Events.CommandProcessingEvent→cloud.yantra.patterns.es.AggregateIdcloud.yantra.patterns.actors.commands.CommandHandlerActor.Events.CommandProcessingEvent→cloud.yantra.patterns.es.Eventcloud.yantra.patterns.actors.commands.CommandHandlerActor.Events.CommandProcessingEvent→cloud.yantra.patterns.es.EventIdcloud.yantra.patterns.actors.commands.CommandHandlerActor.Events.CommandProcessingFailed→cloud.yantra.patterns.es.AggregateIdcloud.yantra.patterns.actors.commands.CommandHandlerActor.Events.TechnicalValidationSuccessful→cloud.yantra.patterns.es.AggregateId
- Direction
- yantra.patterns.actors.commands.CommandHandlerActor.Events uses yantra.patterns.es, so a change to yantra.patterns.es can break yantra.patterns.actors.commands.CommandHandlerActor.Events, while a change to yantra.patterns.actors.commands.CommandHandlerActor.Events can't break yantra.patterns.es.
- Position
- Below the diagonal: yantra.patterns.actors.commands.CommandHandlerActor.Events uses a module listed above it, which is the healthy direction.
22→20 yantra.patterns.actors.commands.CommandHandlerActor.Events uses yantra.patterns.cqrs✕
- Connections
- 8 pairs of types, where a type in yantra.patterns.actors.commands.CommandHandlerActor.Events uses a type in yantra.patterns.cqrs.
- The types involved
cloud.yantra.patterns.actors.commands.CommandHandlerActor.Events.AggregateMutationSuccessful→cloud.yantra.patterns.cqrs.CommandIdcloud.yantra.patterns.actors.commands.CommandHandlerActor.Events.BusinessValidationSuccessful→cloud.yantra.patterns.cqrs.CommandIdcloud.yantra.patterns.actors.commands.CommandHandlerActor.Events.CommandProcessingEvent→cloud.yantra.patterns.cqrs.CommandIdcloud.yantra.patterns.actors.commands.CommandHandlerActor.Events.CommandProcessingFailed→cloud.yantra.patterns.cqrs.CommandIdcloud.yantra.patterns.actors.commands.CommandHandlerActor.Events.CommandProcessingFailed→cloud.yantra.patterns.cqrs.Failedcloud.yantra.patterns.actors.commands.CommandHandlerActor.Events.CommandReceived→cloud.yantra.patterns.cqrs.Commandcloud.yantra.patterns.actors.commands.CommandHandlerActor.Events.CommandReceived→cloud.yantra.patterns.cqrs.CommandIdcloud.yantra.patterns.actors.commands.CommandHandlerActor.Events.TechnicalValidationSuccessful→cloud.yantra.patterns.cqrs.CommandId
- Direction
- yantra.patterns.actors.commands.CommandHandlerActor.Events uses yantra.patterns.cqrs, so a change to yantra.patterns.cqrs can break yantra.patterns.actors.commands.CommandHandlerActor.Events, while a change to yantra.patterns.actors.commands.CommandHandlerActor.Events can't break yantra.patterns.cqrs.
- Position
- Below the diagonal: yantra.patterns.actors.commands.CommandHandlerActor.Events uses a module listed above it, which is the healthy direction.
23→17 yantra.patterns.actors.entities uses yantra.patterns.es✕
- Connections
- 3 pairs of types, where a type in yantra.patterns.actors.entities uses a type in yantra.patterns.es.
- The types involved
cloud.yantra.patterns.actors.entities.EntityManagerActor→cloud.yantra.patterns.es.EntityIdcloud.yantra.patterns.actors.entities.EntityPersistentActor→cloud.yantra.patterns.es.Eventcloud.yantra.patterns.actors.entities.EntityPersistentActor→cloud.yantra.patterns.es.ZeroEvent
- Direction
- yantra.patterns.actors.entities uses yantra.patterns.es, so a change to yantra.patterns.es can break yantra.patterns.actors.entities, while a change to yantra.patterns.actors.entities can't break yantra.patterns.es.
- Position
- Below the diagonal: yantra.patterns.actors.entities uses a module listed above it, which is the healthy direction.
23→20 yantra.patterns.actors.entities uses yantra.patterns.cqrs✕
- Connections
- 3 pairs of types, where a type in yantra.patterns.actors.entities uses a type in yantra.patterns.cqrs.
- The types involved
cloud.yantra.patterns.actors.entities.EntityPersistentActor→cloud.yantra.patterns.cqrs.CommandHandlercloud.yantra.patterns.actors.entities.EntityPersistentActor→cloud.yantra.patterns.cqrs.CreateCommandcloud.yantra.patterns.actors.entities.EntityPersistentActor→cloud.yantra.patterns.cqrs.UpdateCommand
- Direction
- yantra.patterns.actors.entities uses yantra.patterns.cqrs, so a change to yantra.patterns.cqrs can break yantra.patterns.actors.entities, while a change to yantra.patterns.actors.entities can't break yantra.patterns.cqrs.
- Position
- Below the diagonal: yantra.patterns.actors.entities uses a module listed above it, which is the healthy direction.
24→17 yantra.patterns.actors.entities.EntityPersistentActor.Commands uses yantra.patterns.es✕
- Connections
- 4 pairs of types, where a type in yantra.patterns.actors.entities.EntityPersistentActor.Commands uses a type in yantra.patterns.es.
- The types involved
cloud.yantra.patterns.actors.entities.EntityPersistentActor.Commands.GetEntity→cloud.yantra.patterns.es.EntityIdcloud.yantra.patterns.actors.entities.EntityPersistentActor.Commands.PublishToObserver→cloud.yantra.patterns.es.EntityIdcloud.yantra.patterns.actors.entities.EntityPersistentActor.Commands.PublishToObservers→cloud.yantra.patterns.es.EntityIdcloud.yantra.patterns.actors.entities.EntityPersistentActor.Commands.Stop→cloud.yantra.patterns.es.EntityId
- Direction
- yantra.patterns.actors.entities.EntityPersistentActor.Commands uses yantra.patterns.es, so a change to yantra.patterns.es can break yantra.patterns.actors.entities.EntityPersistentActor.Commands, while a change to yantra.patterns.actors.entities.EntityPersistentActor.Commands can't break yantra.patterns.es.
- Position
- Below the diagonal: yantra.patterns.actors.entities.EntityPersistentActor.Commands uses a module listed above it, which is the healthy direction.
24→20 yantra.patterns.actors.entities.EntityPersistentActor.Commands uses yantra.patterns.cqrs✕
- Connections
- 6 pairs of types, where a type in yantra.patterns.actors.entities.EntityPersistentActor.Commands uses a type in yantra.patterns.cqrs.
- The types involved
cloud.yantra.patterns.actors.entities.EntityPersistentActor.Commands.GetEntity→cloud.yantra.patterns.cqrs.CommandIdcloud.yantra.patterns.actors.entities.EntityPersistentActor.Commands.GetEntity→cloud.yantra.patterns.cqrs.QueryCommandcloud.yantra.patterns.actors.entities.EntityPersistentActor.Commands.PublishToObserver→cloud.yantra.patterns.cqrs.CommandIdcloud.yantra.patterns.actors.entities.EntityPersistentActor.Commands.PublishToObserver→cloud.yantra.patterns.cqrs.QueryCommandcloud.yantra.patterns.actors.entities.EntityPersistentActor.Commands.PublishToObservers→cloud.yantra.patterns.cqrs.CommandIdcloud.yantra.patterns.actors.entities.EntityPersistentActor.Commands.PublishToObservers→cloud.yantra.patterns.cqrs.QueryCommand
- Direction
- yantra.patterns.actors.entities.EntityPersistentActor.Commands uses yantra.patterns.cqrs, so a change to yantra.patterns.cqrs can break yantra.patterns.actors.entities.EntityPersistentActor.Commands, while a change to yantra.patterns.actors.entities.EntityPersistentActor.Commands can't break yantra.patterns.cqrs.
- Position
- Below the diagonal: yantra.patterns.actors.entities.EntityPersistentActor.Commands uses a module listed above it, which is the healthy direction.
25→20 yantra.patterns.actors.filters uses yantra.patterns.cqrs✕
- Connections
- 3 pairs of types, where a type in yantra.patterns.actors.filters uses a type in yantra.patterns.cqrs.
- The types involved
cloud.yantra.patterns.actors.filters.AuthorizationFilter→cloud.yantra.patterns.cqrs.Resultcloud.yantra.patterns.actors.filters.Filter→cloud.yantra.patterns.cqrs.Resultcloud.yantra.patterns.actors.filters.FilterStage→cloud.yantra.patterns.cqrs.Result
- Direction
- yantra.patterns.actors.filters uses yantra.patterns.cqrs, so a change to yantra.patterns.cqrs can break yantra.patterns.actors.filters, while a change to yantra.patterns.actors.filters can't break yantra.patterns.cqrs.
- Position
- Below the diagonal: yantra.patterns.actors.filters uses a module listed above it, which is the healthy direction.
26→10 yantra.patterns.actors.serializer uses yantra.patterns.cqrs.errors✕
- Connections
- 1 pair of types, where a type in yantra.patterns.actors.serializer uses a type in yantra.patterns.cqrs.errors.
- The types involved
cloud.yantra.patterns.actors.serializer.CommandValidationJsonSerializer→cloud.yantra.patterns.cqrs.errors.DomainError
- Direction
- yantra.patterns.actors.serializer uses yantra.patterns.cqrs.errors, so a change to yantra.patterns.cqrs.errors can break yantra.patterns.actors.serializer, while a change to yantra.patterns.actors.serializer can't break yantra.patterns.cqrs.errors.
- Position
- Below the diagonal: yantra.patterns.actors.serializer uses a module listed above it, which is the healthy direction.
26→20 yantra.patterns.actors.serializer uses yantra.patterns.cqrs✕
- Connections
- 2 pairs of types, where a type in yantra.patterns.actors.serializer uses a type in yantra.patterns.cqrs.
- The types involved
cloud.yantra.patterns.actors.serializer.CommandValidationJsonSerializer→cloud.yantra.patterns.cqrs.Commandcloud.yantra.patterns.actors.serializer.CommandValidationJsonSerializer→cloud.yantra.patterns.cqrs.Version
- Direction
- yantra.patterns.actors.serializer uses yantra.patterns.cqrs, so a change to yantra.patterns.cqrs can break yantra.patterns.actors.serializer, while a change to yantra.patterns.actors.serializer can't break yantra.patterns.cqrs.
- Position
- Below the diagonal: yantra.patterns.actors.serializer uses a module listed above it, which is the healthy direction.
27→20 yantra.patterns.actors.serializer.CommandValidationJsonSerializer uses yantra.patterns.cqrs✕
- Connections
- 6 pairs of types, where a type in yantra.patterns.actors.serializer.CommandValidationJsonSerializer uses a type in yantra.patterns.cqrs.
- The types involved
cloud.yantra.patterns.actors.serializer.CommandValidationJsonSerializer.commandIdReads→cloud.yantra.patterns.cqrs.CommandIdcloud.yantra.patterns.actors.serializer.CommandValidationJsonSerializer.commandIdWrites→cloud.yantra.patterns.cqrs.CommandIdcloud.yantra.patterns.actors.serializer.CommandValidationJsonSerializer.resultReads→cloud.yantra.patterns.cqrs.Resultcloud.yantra.patterns.actors.serializer.CommandValidationJsonSerializer.resultWrites→cloud.yantra.patterns.cqrs.Resultcloud.yantra.patterns.actors.serializer.CommandValidationJsonSerializer.ruleIdReads→cloud.yantra.patterns.cqrs.RuleIdcloud.yantra.patterns.actors.serializer.CommandValidationJsonSerializer.ruleIdWrites→cloud.yantra.patterns.cqrs.RuleId
- Direction
- yantra.patterns.actors.serializer.CommandValidationJsonSerializer uses yantra.patterns.cqrs, so a change to yantra.patterns.cqrs can break yantra.patterns.actors.serializer.CommandValidationJsonSerializer, while a change to yantra.patterns.actors.serializer.CommandValidationJsonSerializer can't break yantra.patterns.cqrs.
- Position
- Below the diagonal: yantra.patterns.actors.serializer.CommandValidationJsonSerializer uses a module listed above it, which is the healthy direction.
28→12 yantra.patterns.actors.validations uses yantra.patterns.cqrs.stages✕
- Connections
- 3 pairs of types, where a type in yantra.patterns.actors.validations uses a type in yantra.patterns.cqrs.stages.
- The types involved
cloud.yantra.patterns.actors.validations.BusinessDomainCommandValidation→cloud.yantra.patterns.cqrs.stages.DomainProcessingStagecloud.yantra.patterns.actors.validations.CommandValidation→cloud.yantra.patterns.cqrs.stages.DomainProcessingStagecloud.yantra.patterns.actors.validations.TechnicalDomainCommandValidation→cloud.yantra.patterns.cqrs.stages.DomainProcessingStage
- Direction
- yantra.patterns.actors.validations uses yantra.patterns.cqrs.stages, so a change to yantra.patterns.cqrs.stages can break yantra.patterns.actors.validations, while a change to yantra.patterns.actors.validations can't break yantra.patterns.cqrs.stages.
- Position
- Below the diagonal: yantra.patterns.actors.validations uses a module listed above it, which is the healthy direction.
28→20 yantra.patterns.actors.validations uses yantra.patterns.cqrs✕
- Connections
- 4 pairs of types, where a type in yantra.patterns.actors.validations uses a type in yantra.patterns.cqrs.
- The types involved
cloud.yantra.patterns.actors.validations.CommandValidation→cloud.yantra.patterns.cqrs.Resultcloud.yantra.patterns.actors.validations.CommandValidation→cloud.yantra.patterns.cqrs.Rulecloud.yantra.patterns.actors.validations.CommandValidation→cloud.yantra.patterns.cqrs.RuleIdcloud.yantra.patterns.actors.validations.ValidationRuleWorker→cloud.yantra.patterns.cqrs.Result
- Direction
- yantra.patterns.actors.validations uses yantra.patterns.cqrs, so a change to yantra.patterns.cqrs can break yantra.patterns.actors.validations, while a change to yantra.patterns.actors.validations can't break yantra.patterns.cqrs.
- Position
- Below the diagonal: yantra.patterns.actors.validations uses a module listed above it, which is the healthy direction.
29→12 yantra.patterns.actors.validations.CommandValidation uses yantra.patterns.cqrs.stages✕
- Connections
- 8 pairs of types, where a type in yantra.patterns.actors.validations.CommandValidation uses a type in yantra.patterns.cqrs.stages.
- The types involved
cloud.yantra.patterns.actors.validations.CommandValidation.CommandValidationEvent→cloud.yantra.patterns.cqrs.stages.DomainProcessingStagecloud.yantra.patterns.actors.validations.CommandValidation.CommandValidationInitiated→cloud.yantra.patterns.cqrs.stages.DomainProcessingStagecloud.yantra.patterns.actors.validations.CommandValidation.NoCommandAvailableForValidation→cloud.yantra.patterns.cqrs.stages.DomainProcessingStagecloud.yantra.patterns.actors.validations.CommandValidation.RuleValidationCompleted→cloud.yantra.patterns.cqrs.stages.DomainProcessingStagecloud.yantra.patterns.actors.validations.CommandValidation.RuleValidationInitiated→cloud.yantra.patterns.cqrs.stages.DomainProcessingStagecloud.yantra.patterns.actors.validations.CommandValidation.UnavailableForCommandValidation→cloud.yantra.patterns.cqrs.stages.DomainProcessingStagecloud.yantra.patterns.actors.validations.CommandValidation.ValidationCompleted→cloud.yantra.patterns.cqrs.stages.DomainProcessingStagecloud.yantra.patterns.actors.validations.CommandValidation.ValidationInProgress→cloud.yantra.patterns.cqrs.stages.DomainProcessingStage
- Direction
- yantra.patterns.actors.validations.CommandValidation uses yantra.patterns.cqrs.stages, so a change to yantra.patterns.cqrs.stages can break yantra.patterns.actors.validations.CommandValidation, while a change to yantra.patterns.actors.validations.CommandValidation can't break yantra.patterns.cqrs.stages.
- Position
- Below the diagonal: yantra.patterns.actors.validations.CommandValidation uses a module listed above it, which is the healthy direction.
29→17 yantra.patterns.actors.validations.CommandValidation uses yantra.patterns.es✕
- Connections
- 3 pairs of types, where a type in yantra.patterns.actors.validations.CommandValidation uses a type in yantra.patterns.es.
- The types involved
cloud.yantra.patterns.actors.validations.CommandValidation.CommandValidationEvent→cloud.yantra.patterns.es.AggregateIdcloud.yantra.patterns.actors.validations.CommandValidation.CommandValidationEvent→cloud.yantra.patterns.es.Eventcloud.yantra.patterns.actors.validations.CommandValidation.CommandValidationEvent→cloud.yantra.patterns.es.EventId
- Direction
- yantra.patterns.actors.validations.CommandValidation uses yantra.patterns.es, so a change to yantra.patterns.es can break yantra.patterns.actors.validations.CommandValidation, while a change to yantra.patterns.actors.validations.CommandValidation can't break yantra.patterns.es.
- Position
- Below the diagonal: yantra.patterns.actors.validations.CommandValidation uses a module listed above it, which is the healthy direction.
29→20 yantra.patterns.actors.validations.CommandValidation uses yantra.patterns.cqrs✕
- Connections
- 8 pairs of types, where a type in yantra.patterns.actors.validations.CommandValidation uses a type in yantra.patterns.cqrs.
- The types involved
cloud.yantra.patterns.actors.validations.CommandValidation.CommandValidationInitiated→cloud.yantra.patterns.cqrs.Commandcloud.yantra.patterns.actors.validations.CommandValidation.RuleValidationCompleted→cloud.yantra.patterns.cqrs.Resultcloud.yantra.patterns.actors.validations.CommandValidation.RuleValidationCompleted→cloud.yantra.patterns.cqrs.Rulecloud.yantra.patterns.actors.validations.CommandValidation.RuleValidationInitiated→cloud.yantra.patterns.cqrs.Rulecloud.yantra.patterns.actors.validations.CommandValidation.ValidationCompleted→cloud.yantra.patterns.cqrs.Commandcloud.yantra.patterns.actors.validations.CommandValidation.ValidationCompleted→cloud.yantra.patterns.cqrs.Resultcloud.yantra.patterns.actors.validations.CommandValidation.ValidationInProgress→cloud.yantra.patterns.cqrs.Commandcloud.yantra.patterns.actors.validations.CommandValidation.ValidationInProgress→cloud.yantra.patterns.cqrs.Result
- Direction
- yantra.patterns.actors.validations.CommandValidation uses yantra.patterns.cqrs, so a change to yantra.patterns.cqrs can break yantra.patterns.actors.validations.CommandValidation, while a change to yantra.patterns.actors.validations.CommandValidation can't break yantra.patterns.cqrs.
- Position
- Below the diagonal: yantra.patterns.actors.validations.CommandValidation uses a module listed above it, which is the healthy direction.
30→20 yantra.patterns.actors.validations.ValidationRuleWorker uses yantra.patterns.cqrs✕
- Connections
- 6 pairs of types, where a type in yantra.patterns.actors.validations.ValidationRuleWorker uses a type in yantra.patterns.cqrs.
- The types involved
cloud.yantra.patterns.actors.validations.ValidationRuleWorker.WorkerEvent→cloud.yantra.patterns.cqrs.Resultcloud.yantra.patterns.actors.validations.ValidationRuleWorker.WorkerEvent→cloud.yantra.patterns.cqrs.Rulecloud.yantra.patterns.actors.validations.ValidationRuleWorker.WorkerFinishedValidation→cloud.yantra.patterns.cqrs.Resultcloud.yantra.patterns.actors.validations.ValidationRuleWorker.WorkerFinishedValidation→cloud.yantra.patterns.cqrs.Rulecloud.yantra.patterns.actors.validations.ValidationRuleWorker.WorkerWaitingInitiation→cloud.yantra.patterns.cqrs.Resultcloud.yantra.patterns.actors.validations.ValidationRuleWorker.WorkerWaitingInitiation→cloud.yantra.patterns.cqrs.Rule
- Direction
- yantra.patterns.actors.validations.ValidationRuleWorker uses yantra.patterns.cqrs, so a change to yantra.patterns.cqrs can break yantra.patterns.actors.validations.ValidationRuleWorker, while a change to yantra.patterns.actors.validations.ValidationRuleWorker can't break yantra.patterns.cqrs.
- Position
- Below the diagonal: yantra.patterns.actors.validations.ValidationRuleWorker uses a module listed above it, which is the healthy direction.
31→20 yantra.patterns.cqrs.Version uses yantra.patterns.cqrs✕
- Connections
- 1 pair of types, where a type in yantra.patterns.cqrs.Version uses a type in yantra.patterns.cqrs.
- The types involved
cloud.yantra.patterns.cqrs.Version.DefaultVersion→cloud.yantra.patterns.cqrs.Version
- Direction
- yantra.patterns.cqrs.Version uses yantra.patterns.cqrs, so a change to yantra.patterns.cqrs can break yantra.patterns.cqrs.Version, while a change to yantra.patterns.cqrs.Version can't break yantra.patterns.cqrs.
- Position
- Below the diagonal: yantra.patterns.cqrs.Version uses a module listed above it, which is the healthy direction.
32→18 yantra.patterns.javadsl.cqrs uses yantra.patterns.javadsl.cqrs.results✕
- Connections
- 4 pairs of types, where a type in yantra.patterns.javadsl.cqrs uses a type in yantra.patterns.javadsl.cqrs.results.
- The types involved
cloud.yantra.patterns.javadsl.cqrs.CommandProcessor→cloud.yantra.patterns.javadsl.cqrs.results.Failurecloud.yantra.patterns.javadsl.cqrs.CommandProcessor→cloud.yantra.patterns.javadsl.cqrs.results.Resultcloud.yantra.patterns.javadsl.cqrs.CommandStore→cloud.yantra.patterns.javadsl.cqrs.results.Resultcloud.yantra.patterns.javadsl.cqrs.ValidationRule→cloud.yantra.patterns.javadsl.cqrs.results.Result
- Direction
- yantra.patterns.javadsl.cqrs uses yantra.patterns.javadsl.cqrs.results, so a change to yantra.patterns.javadsl.cqrs.results can break yantra.patterns.javadsl.cqrs, while a change to yantra.patterns.javadsl.cqrs can't break yantra.patterns.javadsl.cqrs.results.
- Position
- Below the diagonal: yantra.patterns.javadsl.cqrs uses a module listed above it, which is the healthy direction.
32→21 yantra.patterns.javadsl.cqrs uses yantra.patterns.javadsl.cqrs.events✕
- Connections
- 2 pairs of types, where a type in yantra.patterns.javadsl.cqrs uses a type in yantra.patterns.javadsl.cqrs.events.
- The types involved
cloud.yantra.patterns.javadsl.cqrs.CommandProcessor→cloud.yantra.patterns.javadsl.cqrs.events.FailureEventcloud.yantra.patterns.javadsl.cqrs.CommandStore→cloud.yantra.patterns.javadsl.cqrs.events.DomainEvent
- Direction
- yantra.patterns.javadsl.cqrs uses yantra.patterns.javadsl.cqrs.events, so a change to yantra.patterns.javadsl.cqrs.events can break yantra.patterns.javadsl.cqrs, while a change to yantra.patterns.javadsl.cqrs can't break yantra.patterns.javadsl.cqrs.events.
- Position
- Below the diagonal: yantra.patterns.javadsl.cqrs uses a module listed above it, which is the healthy direction.
33→20 yantra.patterns.actors.commands uses yantra.patterns.cqrs✕
- Connections
- 5 pairs of types, where a type in yantra.patterns.actors.commands uses a type in yantra.patterns.cqrs.
- The types involved
cloud.yantra.patterns.actors.commands.CommandHandlerActor→cloud.yantra.patterns.cqrs.Resultcloud.yantra.patterns.actors.commands.CommandHandlerActor→cloud.yantra.patterns.cqrs.Rulecloud.yantra.patterns.actors.commands.CommandProcessingStatus→cloud.yantra.patterns.cqrs.Commandcloud.yantra.patterns.actors.commands.CommandProcessingStatus→cloud.yantra.patterns.cqrs.CommandIdcloud.yantra.patterns.actors.commands.CommandProcessingStatus→cloud.yantra.patterns.cqrs.Result
- Direction
- yantra.patterns.actors.commands uses yantra.patterns.cqrs, so a change to yantra.patterns.cqrs can break yantra.patterns.actors.commands, while a change to yantra.patterns.actors.commands can't break yantra.patterns.cqrs.
- Position
- Below the diagonal: yantra.patterns.actors.commands uses a module listed above it, which is the healthy direction.
33→22 yantra.patterns.actors.commands uses yantra.patterns.actors.commands.CommandHandlerActor.Events✕
- Connections
- 2 pairs of types, where a type in yantra.patterns.actors.commands uses a type in yantra.patterns.actors.commands.CommandHandlerActor.Events.
- The types involved
cloud.yantra.patterns.actors.commands.CommandHandlerActor→cloud.yantra.patterns.actors.commands.CommandHandlerActor.Events.CommandProcessingEventcloud.yantra.patterns.actors.commands.CommandProcessingStatus→cloud.yantra.patterns.actors.commands.CommandHandlerActor.Events.CommandProcessingEvent
- Direction
- yantra.patterns.actors.commands uses yantra.patterns.actors.commands.CommandHandlerActor.Events, so a change to yantra.patterns.actors.commands.CommandHandlerActor.Events can break yantra.patterns.actors.commands, while a change to yantra.patterns.actors.commands can't break yantra.patterns.actors.commands.CommandHandlerActor.Events.
- Position
- Below the diagonal: yantra.patterns.actors.commands uses a module listed above it, which is the healthy direction.
33→29 yantra.patterns.actors.commands uses yantra.patterns.actors.validations.CommandValidation✕
- Connections
- 1 pair of types, where a type in yantra.patterns.actors.commands uses a type in yantra.patterns.actors.validations.CommandValidation.
- The types involved
cloud.yantra.patterns.actors.commands.CommandProcessorManagerActor→cloud.yantra.patterns.actors.validations.CommandValidation.ValidationCompleted
- Direction
- yantra.patterns.actors.commands uses yantra.patterns.actors.validations.CommandValidation, so a change to yantra.patterns.actors.validations.CommandValidation can break yantra.patterns.actors.commands, while a change to yantra.patterns.actors.commands can't break yantra.patterns.actors.validations.CommandValidation.
- Position
- Below the diagonal: yantra.patterns.actors.commands uses a module listed above it, which is the healthy direction.
34→10 yantra.patterns.actors.errors uses yantra.patterns.cqrs.errors✕
- Connections
- 3 pairs of types, where a type in yantra.patterns.actors.errors uses a type in yantra.patterns.cqrs.errors.
- The types involved
cloud.yantra.patterns.actors.errors.UnrecognizedMessageError→cloud.yantra.patterns.cqrs.errors.DomainErrorcloud.yantra.patterns.actors.errors.UnsupportedEntityOperation→cloud.yantra.patterns.cqrs.errors.DomainErrorcloud.yantra.patterns.actors.errors.UnsupportedOperation→cloud.yantra.patterns.cqrs.errors.DomainError
- Direction
- yantra.patterns.actors.errors uses yantra.patterns.cqrs.errors, so a change to yantra.patterns.cqrs.errors can break yantra.patterns.actors.errors, while a change to yantra.patterns.actors.errors can't break yantra.patterns.cqrs.errors.
- Position
- Below the diagonal: yantra.patterns.actors.errors uses a module listed above it, which is the healthy direction.
34→17 yantra.patterns.actors.errors uses yantra.patterns.es✕
- Connections
- 1 pair of types, where a type in yantra.patterns.actors.errors uses a type in yantra.patterns.es.
- The types involved
cloud.yantra.patterns.actors.errors.UnsupportedEntityOperation→cloud.yantra.patterns.es.EntityId
- Direction
- yantra.patterns.actors.errors uses yantra.patterns.es, so a change to yantra.patterns.es can break yantra.patterns.actors.errors, while a change to yantra.patterns.actors.errors can't break yantra.patterns.es.
- Position
- Below the diagonal: yantra.patterns.actors.errors uses a module listed above it, which is the healthy direction.
34→25 yantra.patterns.actors.errors uses yantra.patterns.actors.filters✕
- Connections
- 1 pair of types, where a type in yantra.patterns.actors.errors uses a type in yantra.patterns.actors.filters.
- The types involved
cloud.yantra.patterns.actors.errors.UnrecognizedMessageError→cloud.yantra.patterns.actors.filters.Filterable
- Direction
- yantra.patterns.actors.errors uses yantra.patterns.actors.filters, so a change to yantra.patterns.actors.filters can break yantra.patterns.actors.errors, while a change to yantra.patterns.actors.errors can't break yantra.patterns.actors.filters.
- Position
- Below the diagonal: yantra.patterns.actors.errors 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
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A03:2025 — Software Supply Chain Failures | 2 | Medium |
Roadmap
Top priorities: Resolve the 1 No ADRs found finding(s) in ADR Quality; 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; Expand the README with getting-started, architecture overview and a project map.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 1 No ADRs found finding(s) in ADR Quality. | +5.2 pts | Low | ADR Quality |
| 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. | +3.5 pts | Medium | Architecture documentation |
| Expand the README with getting-started, architecture overview and a project map. | +3.0 pts | Medium | Documentation (README) |
| On Scala 3, add `-Yexplicit-nulls` to `scalacOptions` so `String` and `String | Null` mean different things, and type each Java API's result as nullable where it can return null; on Scala 2 (or as a first step), enable WartRemover's `Null` wart (`wartremoverErrors += Wart.Null`) or Scalafix's `DisableSyntax.noNulls = true` so the code holds absence in `Option`. Then pay the assertions down rather than adding to them: each `.nn` is a null the compiler could not rule out — wrap the Java value in `Option(…)` at the boundary, pattern-match on `null` once there, or change the API so the null cannot arrive; an `unsafeNulls` import switches the checking off for everything after it. | +2.7 pts | Medium | Nullable reference types |
| Swallowed exception (caught, then discarded) | +2.1 pts | Medium | Exception handling |
| Nothing pauses a release for a human: publish as a draft release (or gate the release job on a protected tag/manual dispatch) so a bad build can be stopped before users can download it. | +0.9 pts | Medium | Deployment & Rollback |
| Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release. | +0.9 pts | Medium | Release Hygiene |
| Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. | +0.4 pts | Low | Supply-chain Provenance & Signing |
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 61 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.8, the weighted average across measured dimensions.
What we checked — 61 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, 8 of 24 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Canine Code Analyzer duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 | ✓ deterministic |
Run transparency — what happened this run
- D8 Code Coverage — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT READ here — but this repository measures it: a coverage step in CI (`sbt clean coverage test coverageReport`) shows that coverage is collected and tracked in your own CI. The built-in collector has no runner for this ecosystem (.scala), so the analyzer could not read the number — a gap in the analyzer's language coverage, not an unmeasured repo. Not scored. To have the real number read, produce a coverage report in a standard format (`addSbtPlugin("org.scoverage" % "sbt-scoverage" % "<version>")` in `project/plugins.sbt`, then `sbt clean coverage test coverageReport`) 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. You can widen what we reach: optional: produce a coverage report in a standard format (`addSbtPlugin("org.scoverage" % "sbt-scoverage" % "<version>")` in `project/plugins.sbt`, then `sbt clean coverage test coverageReport`) 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 — then the real number is read on the next scan.
- D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test source is present (.scala) and this repository declares an sbt build (repository root, 23 test files), but it was not re-run: the analyzer environment could not run it. Not scored — this is a gap in the analyzer's language coverage, not a finding about this repository.
- 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 43 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 — 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. D22 identifies the intentionally-exposed surface from `IsPackable` and `.Contracts` project names, MSBuild conventions read off the loaded project set. This target exposed no such projects, so the probe never ran; this says nothing about whether the repository has a public API. This repository commits no C#/VB source at all, so there was never an MSBuild project set to read these conventions off. That is OUR side and it is an ADMISSION gap, not an environment fault: no published-package marker D22 reads admitted any project here. D22 DOES collect the public API of every language in this tree, and admits a project only when its manifest makes that ecosystem's publication act in a form the marker recognises — so what is missing is not a collector but an admission rule for the publication act this repository makes, if it makes one. The remedy is a better discriminator for that marker — not a collector, and no change to the scan image can close it. The marker's rules are measured to refuse applications, so one refused repository is the rule working as calibrated; several are the evidence that it is too strict.
- 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.
- D27 Navigability — 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. Navigability is taken over call sites whose callee resolved. For C# that population includes calls into referenced assemblies; for this language only calls declared inside the repository count, so the abstention threshold reads the repository's use of its standard library as a resolution failure. That is a limit of this analyzer, not a build problem in this repository.
- D34 Knowledge Freshness — 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. Too few commits to judge knowledge freshness (43 commit(s) sampled).
- 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.
- 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 — 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. Arm one resolves each comparison operand to the domain member it judges, and that binding exists only in a Roslyn compilation, which this run did not load. Arm two ran over the neutral model because this repository's frontend declares whether each construction is produced or passed. A rule decided in two places would not appear above.
- 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.
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.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
- D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
- D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- 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.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- 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.
- P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
- P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
Dimensions
D1 · Cyclomatic Complexity
0 method(s) exceeded the cyclomatic complexity threshold of 15.
D2 · Cognitive Complexity
0 method(s) exceeded the cognitive complexity threshold of 15.
D3 · God Classes
0 god class(es) detected.
D4 · Code Duplication
0 duplicated block group(s) detected.
D6 · Cohesion (LCOM4)
0 of 3 classes have LCOM4 above 3.
D9 · Test Distribution
76 test methods: 76 unit, 0 integration, 0 BDD, 0 e2e. The Scala suite contributes 76 test case(s) across 15 file(s) in a test source set declaring at least one — every `test("…")`, `it("…")`, `property("…")` and `"…" in {…}` registration and every JUnit `@Test`, which is how munit, ScalaTest, utest, ZIO Test and specs2 declare a case; a case registered under a computed name is not counted, so this is a floor. Its tier split is INFERRED from paths and file names, except sbt's src/it source set, which the build declares.
D12 · Dependency Hygiene
8 outdated direct sbt declarations. An sbt declaration names an EXACT version, so the remedy is an edit to the build file — there is no lockfile refresh that would move it. Test-, Provided- and it-scoped declarations are excluded, because a consumer of this project never receives them. A version held in a Scala val is read only when the val is one string literal: sbt is a program rather than a manifest, and evaluating a computed version would invent the measurement rather than take it. Whether any artifact is DEPRECATED or ABANDONED is not graded and cannot be — Maven Central publishes no such marker, and release age does not stand in for one: the most widely depended-upon libraries are routinely the stalest, being finished rather than abandoned. Known CVEs in this dependency graph are D30's question.
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D14 · License Compliance
0 of 8 declared sbt dependency artifact(s) use a banned license. Licences were resolved from the POMs Maven Central publishes, over the production coordinates this repository's 2 sbt build file(s) (build.sbt and project/*.scala) declare with a literal version, directly or through a string-literal val — `%%` resolved to the Scala binary suffix Central publishes under, test-scoped declarations excluded — the same declaration-site closure this analysis reads for dependency currency. sbt has no lockfile a checkout carries, so this is deliberately NOT the transitive closure.
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window. Repeated repair below the complexity floor: src/main/scala/cloud/yantra/patterns/actors/validations/BusinessDomainCommandValidation.scala (3 of 4 changes were fixes); src/main/scala/cloud/yantra/patterns/actors/validations/TechnicalDomainCommandValidation.scala (3 of 4 changes were fixes)
What to do
- Resolve the 2 Repeated repair finding(s) in Churn × Complexity Hotspots — start with BusinessDomainCommandValidation.scala, TechnicalDomainCommandValidation.scala. — One of this dimension's main actionable groups (2 warning-level).
D17 · Explicit Debt
0 deducted task-comment markers across 3158 LoC (0.0/KLoC) → score 10.0. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
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).
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
semgrep found no security issues.
D30 · Dependency Vulnerabilities
No known-vulnerable dependencies in any ecosystem this repository declares.
D35 · Change Coupling
No strong hidden change-coupling between production files.
D36 · Supply-chain Provenance & Signing
1/3 supply-chain integrity signals present (provenance, signing, SBOM).
What to do
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 1 platform declaration(s) and 0 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
Frontend & cross-cutting dimensions
AX10 · Code composition
AX3 · Project dependency cycles
AX5 · Architecture & structure
AX6 · Interface segregation
DM1 · Aggregate boundaries
DM10 · One transaction, one aggregate
DM12 · Ambient inputs in the domain
DM6 · Domain ↔ infrastructure boundary
- `CommandHandlerActor` (domain) — the domain type's supertype is an infrastructure/framework type from `akka.persistence` — the domain state/event is fused to the framework. Invert the dependency: keep the domain core free of framework/transport types (derive codecs on a boundary DTO; express infra behind a domain-owned port). — src/main/scala/cloud/yantra/patterns/actors/commands/CommandHandlerActor.scala:25
- `EntityPersistentActor` (domain) — the domain type's supertype is an infrastructure/framework type from `akka.persistence` — the domain state/event is fused to the framework. Invert the dependency: keep the domain core free of framework/transport types (derive codecs on a boundary DTO; express infra behind a domain-owned port). — src/main/scala/cloud/yantra/patterns/actors/entities/EntityPersistentActor.scala:20
- `CommandValidation` (domain) — the domain type's supertype is an infrastructure/framework type from `akka.persistence` — the domain state/event is fused to the framework. Invert the dependency: keep the domain core free of framework/transport types (derive codecs on a boundary DTO; express infra behind a domain-owned port). — src/main/scala/cloud/yantra/patterns/actors/validations/CommandValidation.scala:17
What to do
- Invert domain→infrastructure dependencies: declare interfaces in the domain, implement them in infrastructure (Dependency Inversion).
DM9 · Scattered domain decisions
GD1 · Unfinished & placeholder code
IC1 · Incompleteness & stubs
M1 · Documentation (README)
- The root README is 107 words, against a bar of 120. Of the three newcomer-critical sections this check looks for by heading, in the README and in the repository documents it links, it found no a build/run or getting-started section, no a testing section, no an architecture or project-map section. Sections are matched on HEADING text only, so material written under a heading this check does not recognise — or with no heading at all — is not seen and this row may understate what the document covers. — README.md:1
What to do
- Expand the README with getting-started, architecture overview and a project map.
- Add a build/run (quick start) section to the root README — the first thing a newcomer needs.
- Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
- Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
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
P1 · CI/CD gates
- A CI pipeline exists but no build step was matched — changes may merge without the build ever running. A build step may be invoked directly as a command, or declared as a task that a runner named in the pipeline resolves.
What to do
- Add an explicit build step to your CI pipeline — your stack's own build command, or, if the pipeline delegates to a task runner, a build task that runner executes in CI — so every change is built before merge.
P10 · Library API & versioning
- 25/25 types (100%) declared in the published library are public. For a library, every public type is a stability contract — keep implementation types off the surface and expose only the intended API.
What to do
- Keep implementation types off the public surface (Java: package-private (no modifier), or leave its package out of `module-info` exports) so internals can change without breaking consumers.
P3 · Security & performance tooling
What to do
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
What to do
- Nothing pauses a release for a human: publish as a draft release (or gate the release job on a protected tag/manual dispatch) so a bad build can be stopped before users can download it.
P6 · Release Hygiene
- No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
What to do
- Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.
P8 · Schema migrations
X1 · Async correctness
X12 · Unreachable branch
X13 · Undrained process stream
X14 · Bypassable address classification
X15 · Unvalidated length from an untrusted reader
X16 · Unfloored truncation loop
X17 · Uncapped recursion over a caller-supplied document
X18 · Disposal-pattern correctness
X19 · Unrestored process-global state
X20 · Mistyped argument guard
X21 · Side-effecting pattern guard
X22 · Contradicted release guard
X23 · Unguarded diagnostic materialisation
- `debug` at line 57 is called with an argument built by `subscribeToValidatedCommandTopics.mkString("…")` (line 59), whose cost grows with the collection it walks. Scala evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: the logger takes a built `String` (SLF4J, Akka/Pekko `LoggingAdapter`, `context.log`), and there is no `isDebugEnabled`/`isTraceEnabled` test and no debug flag. — src/main/scala/cloud/yantra/patterns/actors/entities/EntityManagerActor.scala:57
What to do
- In Scala, put the construction behind the logger's own check (`if (log.isDebugEnabled)`), or log through a logger that takes the message by name or by macro and so builds it only when the level is on — scala-logging's `LazyLogging`/`StrictLogging` (`logger.debug(s"rows: ${rows.mkString(", ")}")` expands to that check), log4s or log4cats. Interpolating into an `s"…"` is not the fix on SLF4J or Akka's `LoggingAdapter`: their `debug` takes a `String`, so the interpolation and every `mkString` inside it run before the call is entered.
X24 · Document value interpolated into markup unescaped
X25 · Inert configuration knob
X26 · Unsynchronised callback handoff
X27 · Collection changed while being enumerated
X28 · Index access outside its own emptiness guard
X29 · Per-element action decided by a fixed element
X3 · Exception handling
- `case _: Exception` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. — src/main/scala/cloud/yantra/patterns/tools.scala:23
What to do
- Swallowed exception (caught, then discarded)
X30 · Support guard that admits what it rejects
X5 · Nullable reference types
- No build over this repository's 73 Scala product file(s) passes `-Yexplicit-nulls`, enables WartRemover's `Null` wart or runs Scalafix's `DisableSyntax.noNulls`, so every reference type admits null and nothing reports a `null` written into the code or returned from a Java API — the first one to reach a method call is a `NullPointerException`. `Option` by convention is a habit no tool here holds the code to.
What to do
- On Scala 3, add `-Yexplicit-nulls` to `scalacOptions` so `String` and `String | Null` mean different things, and type each Java API's result as nullable where it can return null; on Scala 2 (or as a first step), enable WartRemover's `Null` wart (`wartremoverErrors += Wart.Null`) or Scalafix's `DisableSyntax.noNulls = true` so the code holds absence in `Option`. Then pay the assertions down rather than adding to them: each `.nn` is a null the compiler could not rule out — wrap the Java value in `Option(…)` at the boundary, pattern-match on `null` once there, or change the API so the null cannot arrive; an `unsafeNulls` import switches the checking off for everything after it.
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 61% | Adequate — gated by X3, X5 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 100% | Exemplary | Strongest area. |
| Maturity | 58% | Adequate — gated by M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 60% | Adequate | Acceptable, with room to improve. |
| Security | 83% | Adequate — gated by D36 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Domain Modelling | 90% | Exemplary | Solid. |
Not evidenced — 1 control(s) we could not find positive evidence for
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 68 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 applicable: this repository's Java imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's; this repository's Scala imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's.
- AX2 Stateful singletons — No container singleton was found, so there is no shared instance for concurrent requests to race on. No class in this Java code is a Spring, JSR-330 or CDI singleton bean. No class in this Scala code is a Play controller, a Cask routes object, a Scalatra servlet, a Finatra controller, an Akka/Pekko HTTP routes holder or a JSR-330/Spring singleton, so no instance is shared between request threads.
- AX4 Dependency direction — not applicable to a CQRS architecture (the inward-dependency rule is for layered/clean styles)
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AX8 Test isolation — no test/production split to check
- AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
- AXB1 Runtime evidence locked — no reproducible boot — This repository has nothing the runtime tiers could boot or serve — no markup, no UI framework or web-server dependency, no UI component source, no native UI project and no API definition — nothing here is a surface to boot — so runtime a11y/egress/header evidence has no subject here. Not applicable: this is neither a gap in the scan nor a finding about your code.
- 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.
- C3 Audit Trail — No personal data detected in a persisted data model — no PII-named column (email, first_name, date_of_birth, phone_number, …) or stored credential on a Slick table or in a SQL migration's CREATE TABLE or ALTER TABLE — and no database client (Slick, Doobie, Quill, ScalikeJDBC, Anorm, Skunk, a MongoDB or Cassandra driver, JDBC) imported either, so this repository keeps no sensitive data whose changes an audit trail would record. If it does (through a store configured outside this repository, for instance), the trail belongs to wherever that data is stored.
- C4 Data Retention — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a Slick table or in a SQL migration's CREATE TABLE or ALTER TABLE — and no database or data-store client (Slick, Doobie, Quill, ScalikeJDBC, Anorm, Skunk, JDBC, MongoDB, Cassandra, …) imported either, so this repository keeps no personal data whose lifetime a retention limit would bound.
- C5 Data-Subject Rights — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a Slick table or in a SQL migration's CREATE TABLE or ALTER TABLE — and no database or data-store client (Slick, Doobie, Quill, ScalikeJDBC, Anorm, Skunk, JDBC, MongoDB, Cassandra, …) imported either, so this repository keeps no personal data for a data subject to erase, export or consent over.
- D10 Test Quality — ~2001 lines of test source are present (.scala) 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.
- D11 Test Reliability — Test reliability not included — the .scala suite was found but not re-run
- D16 Bus Factor — single-contributor repository — bus factor is not applicable
- D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, 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; Java, Scala not measured.
- D22 Internal API Consistency — The exposed public-API surface could not be collected — no C#/VB projects loaded.
- D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Aggregate roots were found in only one source directory (main), which is a layered codebase, not two contexts. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D24 Comment Value — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only — this repository's production source is .java, .scala, 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
- D26 Project Cohesion — This repository is one build unit, `(repository root)` (3158 LoC, 172 module-visible types across 24 directories), within the size bounds. Not scored: a single unit of this size gives project cohesion nothing to grade.
- D27 Navigability — D27 counts a call into the standard library or a dependency as unresolved for this repository's language (.scala), so too few call sites counted as resolved to assess navigability. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
- D32 Data Compliance (PII/GDPR) — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
- D34 Knowledge Freshness — too few commits to judge knowledge freshness
- 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 — D39 measures the IL emitted by a .NET build; this repository has no .NET solution or project files, so the dimension does not apply.
- 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.
- D5 Coupling — Not applicable — this sbt build ships 1 production module(s), so there is no coupling BETWEEN modules to measure. (Its test and non-production modules are not part of the shipped graph.)
- D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
- D8 Code Coverage — Coverage not included — suite not readable by the collector
- 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)
- ED1 Event-Driven — not scored — this repository shows only 1 of the 3 signals this lens looks for (1 CQRS handler(s))
- ED5 Idempotency — Not assessed, and this one is on us: 1 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.
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- M4 Documentation accuracy — Not applicable: the 1 current-state document(s) make no claim of a kind M4 checks.
- 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'.
- P2 Observability — This repository's JVM source (1 module(s), 99 file(s) read) declares no entry point and bootstraps no server, and nothing here deploys a service — it is a library, run inside whatever hosts it, so production observability (structured logging, tracing/metrics, health checks) is N/A. If it grows a binary or a service, the dimension reactivates.
- P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the JVM source, so there is no service whose uptime a failing dependency could take down
- P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (`addSbtPlugin("org.scoverage" % "sbt-scoverage" % "<version>")` in `project/plugins.sbt`, then `sbt clean coverage test coverageReport`) 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 `@Benchmark` in a Java, Kotlin or Scala file importing JMH or kotlinx-benchmark, Jetpack Benchmark's `measureRepeated` in a file importing androidx.benchmark, or JMH/kotlinx-benchmark/androidx.benchmark in a pom.xml, Gradle or sbt build, 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.
- PF3 Async & latency hygiene — Not applicable: this repository declares no async functions, so there is no asynchronous code for a blocking call to stall.
- S1 Web-Security Posture — No web surface: 98 Scala file(s) were read for weak hashes and ciphers, key material fixed in the source, disabled TLS certificate validation and obsolete TLS versions, and none was found. This repository serves no HTTP of its own — no HTTP-server artifact (akka-http, pekko-http, http4s, Play, Finagle, zio-http, cask, Scalatra, a tapir server, Jetty, Undertow, …) outside test scope in its build, and no server package imported or server bound in its production source — so HTTPS enforcement, HSTS, cookie flags and input validation are N/A here, as they are for a C# library or worker. If this codebase starts serving HTTP, the dimension reactivates automatically.
- X10 Duplicated predicate — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X2 Cancellation propagation — no C# was loaded; this repository's Scala and Java were read, and no request in it can be cancelled by a caller — a Scala request takes no token: a Future cannot be cancelled, and cats-effect, ZIO and Monix interrupt the fiber that made the request from outside the call, not through a parameter; a Java request off Android takes no token: it is cancelled through the handle it returns (Future.cancel, Call.cancel, a Disposable), ambiently (io.grpc.Context) or by interrupting its thread, not through a parameter
- X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X4 Structured logging — This check asks whether log calls keep a message's values apart from its text, which needs a logger that can carry them as fields. This repository's Java was read, and it logs through none that an assembled message defeats: java.util.logging's level methods, log4j 1, commons-logging, JBoss Logging and Flogger take one finished message (as log4net does in C#), or it makes no call through a named logger at all. Calls made through SLF4J or log4j 2 (`org.slf4j.Logger`, `org.apache.logging.log4j.Logger`, Lombok's `@Slf4j`) would be judged.
- X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X7 Silent fallback defaults — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
Critical — 3 finding(s)
- Domain depends on infrastructure: CommandHandlerActor src/main/scala/cloud/yantra/patterns/actors/commands/CommandHandlerActor.scala:25
- Domain depends on infrastructure: EntityPersistentActor src/main/scala/cloud/yantra/patterns/actors/entities/EntityPersistentActor.scala:20
- Domain depends on infrastructure: CommandValidation src/main/scala/cloud/yantra/patterns/actors/validations/CommandValidation.scala:17
Serious — 3 finding(s)
- Repeated repair: src/main/scala/cloud/yantra/patterns/actors/validations/BusinessDomainCommandValidation.scala src/main/scala/cloud/yantra/patterns/actors/validations/BusinessDomainCommandValidation.scala:22
- Repeated repair: src/main/scala/cloud/yantra/patterns/actors/validations/TechnicalDomainCommandValidation.scala src/main/scala/cloud/yantra/patterns/actors/validations/TechnicalDomainCommandValidation.scala:21
- Swallowed exception (caught, then discarded) src/main/scala/cloud/yantra/patterns/tools.scala:23
Minor — 10 finding(s)
- No ADRs found
- REDACTED
- REDACTED
- Thin README README.md:1
- No ADRs
- CI build step not evidenced
- Large public API surface
- No changelog
- Diagnostic log message is built whether or not it is wanted src/main/scala/cloud/yantra/patterns/actors/entities/EntityManagerActor.scala:57
- Scala's null is not held to the type system everywhere
Minor — 8 finding(s)
- Outdated: com.typesafe.akka:akka-actor_2.12
- Outdated: com.typesafe.akka:akka-cluster-tools_2.12
- Outdated: com.typesafe.akka:akka-http-spray-json_2.12
- Outdated: com.typesafe.akka:akka-persistence_2.12
- Outdated: com.typesafe.akka:akka-remote_2.12
- Outdated: com.typesafe.play:play-json_2.12
- Outdated: org.slf4j:slf4j-api
- Outdated: org.slf4j:slf4j-simple
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-c766f76530a24e21beb66654e4b358d9/history.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-c766f76530a24e21beb66654e4b358d9/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 . | 0 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | 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-71f8ecee40b443d0a2dad6d1a63cabfe | 0 | artifacts/raw/osv-scanner.json |
| D31 · IaC & Container Security | trivy | — | trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan. | 0 | — |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. | 0 | — |
| 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-71f8ecee40b443d0a2dad6d1a63cabfe | 0 | artifacts/raw/osv-scanner.json |