Executive summary
denis.sajnar/cqrs-microservices meets our standard for production. It scores 73 out of 100 and is rated Strong, and all six of its critical findings are security problems in the packages it uses.
Domain Modelling, at 65, is the weakest lens and counts most in the score. The best first steps are validating new business objects and introducing dedicated id types, each worth about 6 points. Raising Domain Modelling to 70 would lift the score to about 75.
Six known security holes in the packages the code depends on can be used by attackers. Updating the vulnerable packages would close this risk.
The product code is 5,689 lines, about €20,000 to rebuild.
If Domain Modelling rose from 65 to 70, the lowest score rated Strong, the score would rise from 73 to about 75.
Fixed since the last survey: 8 findings
- Cyclomatic Complexity · check-deprecations.main (cyclomatic 21) scripts/check-deprecations.py
- Cognitive Complexity · check-deprecations.main (cognitive 41) scripts/check-deprecations.py
- Cognitive Complexity · check-deprecations.load_deprecations (cognitive 38) scripts/check-deprecations.py
- Secret Scanning · Leaked secret: hardcoded-credential REDACTED
- Secret Scanning · Leaked secret: hardcoded-credential REDACTED
- Secret Scanning · Leaked secret: hardcoded-credential REDACTED
- Secret Scanning · Leaked secret: hardcoded-credential REDACTED
- Secret Scanning · Leaked secret: hardcoded-credential REDACTED
Rebuild cost: about €20,000 · Estimate
| Cost to rebuild | €6,500 to €33,000, for 109 to 344 hours of work, about 0.1 person-years for one engineer |
|---|---|
| Difficulty of the problem | Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×1.1 at a score of 73. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it. |
| Size | Small: 5,689 lines of product code |
| What it is not | Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one. |
Top priorities
Diagnosis: what the measurements show together
Architecture — module dependency graph
Architecture: which parts of the code depend on which
| uses → | 1 command.adapter.output.rabbitmq.config | 2 observability.logging.LoggingProperties | 3 query.core.impl.ProjectionsImpl | 4 shared.events | 5 shared.model | 6 web | 7 command.core.domain | 8 observability.logging | 9 query.core.domain | 10 shared.events.OrderEvent | 11 command.adapter.input.rest.dto | 12 command.adapter.input.rest.exception | 13 command.adapter.output.mongodb.document | 14 command.core.domain.OrderAggregate | 15 command.core.domain.OrderEventType | 16 command.core.domain.OrderId | 17 command.core.domain.OutboxState | 18 command.core.input.usecase | 19 command.core.output.port | 20 query.adapter.input.rest.dto | 21 query.adapter.input.rest.exception | 22 query.adapter.output.postgresql.entity | 23 query.core.input.usecase | 24 query.core.output.port | 25 command.adapter.input.rest.controller | 26 command.adapter.input.rest.mapper | 27 command.adapter.output.mongodb.mapper | 28 command.adapter.output.mongodb.repository | 29 command.adapter.output.rabbitmq.adapter | 30 command.core.impl | 31 command.core.output.port.AppendResult | 32 command.scheduling | 33 query.adapter.input.rabbitmq.listener | 34 query.adapter.input.rest.controller | 35 query.adapter.input.rest.mapper | 36 query.adapter.output.postgresql.mapper | 37 query.adapter.output.postgresql.repository | 38 query.core.impl | 39 command.adapter.output.mongodb.adapter | 40 query.adapter.output.postgresql.adapter |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 command.adapter.output.rabbitmq.config | ||||||||||||||||||||||||||||||||||||||||
| 2 observability.logging.LoggingProperties | ||||||||||||||||||||||||||||||||||||||||
| 3 query.core.impl.ProjectionsImpl | ||||||||||||||||||||||||||||||||||||||||
| 4 shared.events | ||||||||||||||||||||||||||||||||||||||||
| 5 shared.model | ||||||||||||||||||||||||||||||||||||||||
| 6 web | ||||||||||||||||||||||||||||||||||||||||
| 7 command.core.domain | 2 | 3 | ||||||||||||||||||||||||||||||||||||||
| 8 observability.logging | 2 | |||||||||||||||||||||||||||||||||||||||
| 9 query.core.domain | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 10 shared.events.OrderEvent | 3 | 2 | ||||||||||||||||||||||||||||||||||||||
| 11 command.adapter.input.rest.dto | 3 | 2 | ||||||||||||||||||||||||||||||||||||||
| 12 command.adapter.input.rest.exception | 1 | 3 | ||||||||||||||||||||||||||||||||||||||
| 13 command.adapter.output.mongodb.document | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 14 command.core.domain.OrderAggregate | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 15 command.core.domain.OrderEventType | 1 | 4 | ||||||||||||||||||||||||||||||||||||||
| 16 command.core.domain.OrderId | 1 | |||||||||||||||||||||||||||||||||||||||
| 17 command.core.domain.OutboxState | 4 | |||||||||||||||||||||||||||||||||||||||
| 18 command.core.input.usecase | 1 | 13 | ||||||||||||||||||||||||||||||||||||||
| 19 command.core.output.port | 3 | 8 | ||||||||||||||||||||||||||||||||||||||
| 20 query.adapter.input.rest.dto | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 21 query.adapter.input.rest.exception | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 22 query.adapter.output.postgresql.entity | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 23 query.core.input.usecase | 1 | 11 | ||||||||||||||||||||||||||||||||||||||
| 24 query.core.output.port | 1 | 11 | ||||||||||||||||||||||||||||||||||||||
| 25 command.adapter.input.rest.controller | 1 | 12 | 3 | |||||||||||||||||||||||||||||||||||||
| 26 command.adapter.input.rest.mapper | 3 | 6 | ||||||||||||||||||||||||||||||||||||||
| 27 command.adapter.output.mongodb.mapper | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 28 command.adapter.output.mongodb.repository | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 29 command.adapter.output.rabbitmq.adapter | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 30 command.core.impl | 2 | 15 | 4 | 6 | ||||||||||||||||||||||||||||||||||||
| 31 command.core.output.port.AppendResult | 2 | |||||||||||||||||||||||||||||||||||||||
| 32 command.scheduling | 1 | |||||||||||||||||||||||||||||||||||||||
| 33 query.adapter.input.rabbitmq.listener | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 34 query.adapter.input.rest.controller | 1 | 8 | 2 | |||||||||||||||||||||||||||||||||||||
| 35 query.adapter.input.rest.mapper | 1 | 5 | ||||||||||||||||||||||||||||||||||||||
| 36 query.adapter.output.postgresql.mapper | 5 | 1 | ||||||||||||||||||||||||||||||||||||||
| 37 query.adapter.output.postgresql.repository | 1 | 1 | 2 | |||||||||||||||||||||||||||||||||||||
| 38 query.core.impl | 1 | 1 | 14 | 4 | 8 | |||||||||||||||||||||||||||||||||||
| 39 command.adapter.output.mongodb.adapter | 2 | 9 | 5 | 2 | ||||||||||||||||||||||||||||||||||||
| 40 query.adapter.output.postgresql.adapter | 1 | 11 | 5 | 2 |
7→4 command.core.domain uses shared.events✕
- Connections
- 2 pairs of types, where a type in command.core.domain uses a type in shared.events.
- The types involved
dev.denissajnar.cqrs.command.core.domain.OrderAggregate→dev.denissajnar.cqrs.shared.events.OrderEventdev.denissajnar.cqrs.command.core.domain.OutboxRecord→dev.denissajnar.cqrs.shared.events.OrderEvent
- Direction
- command.core.domain uses shared.events, so a change to shared.events can break command.core.domain, while a change to command.core.domain can't break shared.events.
- Position
- Below the diagonal: command.core.domain uses a module listed above it, which is the healthy direction.
7→5 command.core.domain uses shared.model✕
- Connections
- 3 pairs of types, where a type in command.core.domain uses a type in shared.model.
- The types involved
dev.denissajnar.cqrs.command.core.domain.OrderAggregate→dev.denissajnar.cqrs.shared.model.Statusdev.denissajnar.cqrs.command.core.domain.OrderEventTypeKt→dev.denissajnar.cqrs.shared.model.Statusdev.denissajnar.cqrs.command.core.domain.UpdateOrderCommand→dev.denissajnar.cqrs.shared.model.Status
- Direction
- command.core.domain uses shared.model, so a change to shared.model can break command.core.domain, while a change to command.core.domain can't break shared.model.
- Position
- Below the diagonal: command.core.domain uses a module listed above it, which is the healthy direction.
8→2 observability.logging uses observability.logging.LoggingProperties✕
- Connections
- 2 pairs of types, where a type in observability.logging uses a type in observability.logging.LoggingProperties.
- The types involved
dev.denissajnar.cqrs.observability.logging.HttpExchangeLoggingFilter→dev.denissajnar.cqrs.observability.logging.LoggingProperties.Httpdev.denissajnar.cqrs.observability.logging.LoggingProperties→dev.denissajnar.cqrs.observability.logging.LoggingProperties.Http
- Direction
- observability.logging uses observability.logging.LoggingProperties, so a change to observability.logging.LoggingProperties can break observability.logging, while a change to observability.logging can't break observability.logging.LoggingProperties.
- Position
- Below the diagonal: observability.logging uses a module listed above it, which is the healthy direction.
9→4 query.core.domain uses shared.events✕
- Connections
- 1 pair of types, where a type in query.core.domain uses a type in shared.events.
- The types involved
dev.denissajnar.cqrs.query.core.domain.OrderProjectionKt→dev.denissajnar.cqrs.shared.events.OrderEvent
- Direction
- query.core.domain uses shared.events, so a change to shared.events can break query.core.domain, while a change to query.core.domain can't break shared.events.
- Position
- Below the diagonal: query.core.domain uses a module listed above it, which is the healthy direction.
9→5 query.core.domain uses shared.model✕
- Connections
- 2 pairs of types, where a type in query.core.domain uses a type in shared.model.
- The types involved
dev.denissajnar.cqrs.query.core.domain.Order→dev.denissajnar.cqrs.shared.model.Statusdev.denissajnar.cqrs.query.core.domain.OrderFilter→dev.denissajnar.cqrs.shared.model.Status
- Direction
- query.core.domain uses shared.model, so a change to shared.model can break query.core.domain, while a change to query.core.domain can't break shared.model.
- Position
- Below the diagonal: query.core.domain uses a module listed above it, which is the healthy direction.
10→4 shared.events.OrderEvent uses shared.events✕
- Connections
- 3 pairs of types, where a type in shared.events.OrderEvent uses a type in shared.events.
- The types involved
dev.denissajnar.cqrs.shared.events.OrderEvent.Created→dev.denissajnar.cqrs.shared.events.OrderEventdev.denissajnar.cqrs.shared.events.OrderEvent.Deleted→dev.denissajnar.cqrs.shared.events.OrderEventdev.denissajnar.cqrs.shared.events.OrderEvent.Updated→dev.denissajnar.cqrs.shared.events.OrderEvent
- Direction
- shared.events.OrderEvent uses shared.events, so a change to shared.events can break shared.events.OrderEvent, while a change to shared.events.OrderEvent can't break shared.events.
- Position
- Below the diagonal: shared.events.OrderEvent uses a module listed above it, which is the healthy direction.
10→5 shared.events.OrderEvent uses shared.model✕
- Connections
- 2 pairs of types, where a type in shared.events.OrderEvent uses a type in shared.model.
- The types involved
dev.denissajnar.cqrs.shared.events.OrderEvent.Created→dev.denissajnar.cqrs.shared.model.Statusdev.denissajnar.cqrs.shared.events.OrderEvent.Updated→dev.denissajnar.cqrs.shared.model.Status
- Direction
- shared.events.OrderEvent uses shared.model, so a change to shared.model can break shared.events.OrderEvent, while a change to shared.events.OrderEvent can't break shared.model.
- Position
- Below the diagonal: shared.events.OrderEvent uses a module listed above it, which is the healthy direction.
11→5 command.adapter.input.rest.dto uses shared.model✕
- Connections
- 3 pairs of types, where a type in command.adapter.input.rest.dto uses a type in shared.model.
- The types involved
dev.denissajnar.cqrs.command.adapter.input.rest.dto.OrderEventResponse→dev.denissajnar.cqrs.shared.model.Statusdev.denissajnar.cqrs.command.adapter.input.rest.dto.OrderResponse→dev.denissajnar.cqrs.shared.model.Statusdev.denissajnar.cqrs.command.adapter.input.rest.dto.UpdateOrderRequest→dev.denissajnar.cqrs.shared.model.Status
- Direction
- command.adapter.input.rest.dto uses shared.model, so a change to shared.model can break command.adapter.input.rest.dto, while a change to command.adapter.input.rest.dto can't break shared.model.
- Position
- Below the diagonal: command.adapter.input.rest.dto uses a module listed above it, which is the healthy direction.
11→7 command.adapter.input.rest.dto uses command.core.domain✕
- Connections
- 2 pairs of types, where a type in command.adapter.input.rest.dto uses a type in command.core.domain.
- The types involved
dev.denissajnar.cqrs.command.adapter.input.rest.dto.OrderEventResponse→dev.denissajnar.cqrs.command.core.domain.OrderEventTypedev.denissajnar.cqrs.command.adapter.input.rest.dto.OutboxRecordResponse→dev.denissajnar.cqrs.command.core.domain.OutboxState
- Direction
- command.adapter.input.rest.dto uses command.core.domain, so a change to command.core.domain can break command.adapter.input.rest.dto, while a change to command.adapter.input.rest.dto can't break command.core.domain.
- Position
- Below the diagonal: command.adapter.input.rest.dto uses a module listed above it, which is the healthy direction.
12→6 command.adapter.input.rest.exception uses web✕
- Connections
- 1 pair of types, where a type in command.adapter.input.rest.exception uses a type in web.
- The types involved
dev.denissajnar.cqrs.command.adapter.input.rest.exception.RestExceptionHandler→dev.denissajnar.cqrs.web.ProblemDetailHandler
- Direction
- command.adapter.input.rest.exception uses web, so a change to web can break command.adapter.input.rest.exception, while a change to command.adapter.input.rest.exception can't break web.
- Position
- Below the diagonal: command.adapter.input.rest.exception uses a module listed above it, which is the healthy direction.
12→7 command.adapter.input.rest.exception uses command.core.domain✕
- Connections
- 3 pairs of types, where a type in command.adapter.input.rest.exception uses a type in command.core.domain.
- The types involved
dev.denissajnar.cqrs.command.adapter.input.rest.exception.RestExceptionHandler→dev.denissajnar.cqrs.command.core.domain.ConcurrentModificationdev.denissajnar.cqrs.command.adapter.input.rest.exception.RestExceptionHandler→dev.denissajnar.cqrs.command.core.domain.OrderInvariantViolateddev.denissajnar.cqrs.command.adapter.input.rest.exception.RestExceptionHandler→dev.denissajnar.cqrs.command.core.domain.OrderNotFound
- Direction
- command.adapter.input.rest.exception uses command.core.domain, so a change to command.core.domain can break command.adapter.input.rest.exception, while a change to command.adapter.input.rest.exception can't break command.core.domain.
- Position
- Below the diagonal: command.adapter.input.rest.exception uses a module listed above it, which is the healthy direction.
13→5 command.adapter.output.mongodb.document uses shared.model✕
- Connections
- 1 pair of types, where a type in command.adapter.output.mongodb.document uses a type in shared.model.
- The types involved
dev.denissajnar.cqrs.command.adapter.output.mongodb.document.OrderEventDocument→dev.denissajnar.cqrs.shared.model.Status
- Direction
- command.adapter.output.mongodb.document uses shared.model, so a change to shared.model can break command.adapter.output.mongodb.document, while a change to command.adapter.output.mongodb.document can't break shared.model.
- Position
- Below the diagonal: command.adapter.output.mongodb.document uses a module listed above it, which is the healthy direction.
13→7 command.adapter.output.mongodb.document uses command.core.domain✕
- Connections
- 2 pairs of types, where a type in command.adapter.output.mongodb.document uses a type in command.core.domain.
- The types involved
dev.denissajnar.cqrs.command.adapter.output.mongodb.document.OrderEventDocument→dev.denissajnar.cqrs.command.core.domain.OrderEventTypedev.denissajnar.cqrs.command.adapter.output.mongodb.document.OutboxEventDocument→dev.denissajnar.cqrs.command.core.domain.OutboxState
- Direction
- command.adapter.output.mongodb.document uses command.core.domain, so a change to command.core.domain can break command.adapter.output.mongodb.document, while a change to command.adapter.output.mongodb.document can't break command.core.domain.
- Position
- Below the diagonal: command.adapter.output.mongodb.document uses a module listed above it, which is the healthy direction.
14→4 command.core.domain.OrderAggregate uses shared.events✕
- Connections
- 1 pair of types, where a type in command.core.domain.OrderAggregate uses a type in shared.events.
- The types involved
dev.denissajnar.cqrs.command.core.domain.OrderAggregate.Companion→dev.denissajnar.cqrs.shared.events.OrderEvent
- Direction
- command.core.domain.OrderAggregate uses shared.events, so a change to shared.events can break command.core.domain.OrderAggregate, while a change to command.core.domain.OrderAggregate can't break shared.events.
- Position
- Below the diagonal: command.core.domain.OrderAggregate uses a module listed above it, which is the healthy direction.
14→5 command.core.domain.OrderAggregate uses shared.model✕
- Connections
- 1 pair of types, where a type in command.core.domain.OrderAggregate uses a type in shared.model.
- The types involved
dev.denissajnar.cqrs.command.core.domain.OrderAggregate.Companion→dev.denissajnar.cqrs.shared.model.Status
- Direction
- command.core.domain.OrderAggregate uses shared.model, so a change to shared.model can break command.core.domain.OrderAggregate, while a change to command.core.domain.OrderAggregate can't break shared.model.
- Position
- Below the diagonal: command.core.domain.OrderAggregate uses a module listed above it, which is the healthy direction.
14→7 command.core.domain.OrderAggregate uses command.core.domain✕
- Connections
- 1 pair of types, where a type in command.core.domain.OrderAggregate uses a type in command.core.domain.
- The types involved
dev.denissajnar.cqrs.command.core.domain.OrderAggregate.Companion→dev.denissajnar.cqrs.command.core.domain.OrderAggregate
- Direction
- command.core.domain.OrderAggregate uses command.core.domain, so a change to command.core.domain can break command.core.domain.OrderAggregate, while a change to command.core.domain.OrderAggregate can't break command.core.domain.
- Position
- Below the diagonal: command.core.domain.OrderAggregate uses a module listed above it, which is the healthy direction.
14→10 command.core.domain.OrderAggregate uses shared.events.OrderEvent✕
- Connections
- 1 pair of types, where a type in command.core.domain.OrderAggregate uses a type in shared.events.OrderEvent.
- The types involved
dev.denissajnar.cqrs.command.core.domain.OrderAggregate.Companion→dev.denissajnar.cqrs.shared.events.OrderEvent.Created
- Direction
- command.core.domain.OrderAggregate uses shared.events.OrderEvent, so a change to shared.events.OrderEvent can break command.core.domain.OrderAggregate, while a change to command.core.domain.OrderAggregate can't break shared.events.OrderEvent.
- Position
- Below the diagonal: command.core.domain.OrderAggregate uses a module listed above it, which is the healthy direction.
15→4 command.core.domain.OrderEventType uses shared.events✕
- Connections
- 1 pair of types, where a type in command.core.domain.OrderEventType uses a type in shared.events.
- The types involved
dev.denissajnar.cqrs.command.core.domain.OrderEventType.Companion→dev.denissajnar.cqrs.shared.events.OrderEvent
- Direction
- command.core.domain.OrderEventType uses shared.events, so a change to shared.events can break command.core.domain.OrderEventType, while a change to command.core.domain.OrderEventType can't break shared.events.
- Position
- Below the diagonal: command.core.domain.OrderEventType uses a module listed above it, which is the healthy direction.
15→7 command.core.domain.OrderEventType uses command.core.domain✕
- Connections
- 4 pairs of types, where a type in command.core.domain.OrderEventType uses a type in command.core.domain.
- The types involved
dev.denissajnar.cqrs.command.core.domain.OrderEventType.CREATED→dev.denissajnar.cqrs.command.core.domain.OrderEventTypedev.denissajnar.cqrs.command.core.domain.OrderEventType.Companion→dev.denissajnar.cqrs.command.core.domain.OrderEventTypedev.denissajnar.cqrs.command.core.domain.OrderEventType.DELETED→dev.denissajnar.cqrs.command.core.domain.OrderEventTypedev.denissajnar.cqrs.command.core.domain.OrderEventType.UPDATED→dev.denissajnar.cqrs.command.core.domain.OrderEventType
- Direction
- command.core.domain.OrderEventType uses command.core.domain, so a change to command.core.domain can break command.core.domain.OrderEventType, while a change to command.core.domain.OrderEventType can't break command.core.domain.
- Position
- Below the diagonal: command.core.domain.OrderEventType uses a module listed above it, which is the healthy direction.
16→7 command.core.domain.OrderId uses command.core.domain✕
- Connections
- 1 pair of types, where a type in command.core.domain.OrderId uses a type in command.core.domain.
- The types involved
dev.denissajnar.cqrs.command.core.domain.OrderId.Companion→dev.denissajnar.cqrs.command.core.domain.OrderId
- Direction
- command.core.domain.OrderId uses command.core.domain, so a change to command.core.domain can break command.core.domain.OrderId, while a change to command.core.domain.OrderId can't break command.core.domain.
- Position
- Below the diagonal: command.core.domain.OrderId uses a module listed above it, which is the healthy direction.
17→7 command.core.domain.OutboxState uses command.core.domain✕
- Connections
- 4 pairs of types, where a type in command.core.domain.OutboxState uses a type in command.core.domain.
- The types involved
dev.denissajnar.cqrs.command.core.domain.OutboxState.CLAIMED→dev.denissajnar.cqrs.command.core.domain.OutboxStatedev.denissajnar.cqrs.command.core.domain.OutboxState.FAILED→dev.denissajnar.cqrs.command.core.domain.OutboxStatedev.denissajnar.cqrs.command.core.domain.OutboxState.PENDING→dev.denissajnar.cqrs.command.core.domain.OutboxStatedev.denissajnar.cqrs.command.core.domain.OutboxState.PUBLISHED→dev.denissajnar.cqrs.command.core.domain.OutboxState
- Direction
- command.core.domain.OutboxState uses command.core.domain, so a change to command.core.domain can break command.core.domain.OutboxState, while a change to command.core.domain.OutboxState can't break command.core.domain.
- Position
- Below the diagonal: command.core.domain.OutboxState uses a module listed above it, which is the healthy direction.
18→4 command.core.input.usecase uses shared.events✕
- Connections
- 1 pair of types, where a type in command.core.input.usecase uses a type in shared.events.
- The types involved
dev.denissajnar.cqrs.command.core.input.usecase.OrderHistory→dev.denissajnar.cqrs.shared.events.OrderEvent
- Direction
- command.core.input.usecase uses shared.events, so a change to shared.events can break command.core.input.usecase, while a change to command.core.input.usecase can't break shared.events.
- Position
- Below the diagonal: command.core.input.usecase uses a module listed above it, which is the healthy direction.
18→7 command.core.input.usecase uses command.core.domain✕
- Connections
- 13 pairs of types, where a type in command.core.input.usecase uses a type in command.core.domain.
- The types involved
dev.denissajnar.cqrs.command.core.input.usecase.OrderHistory→dev.denissajnar.cqrs.command.core.domain.AggregateStatsdev.denissajnar.cqrs.command.core.input.usecase.OrderHistory→dev.denissajnar.cqrs.command.core.domain.OrderAggregatedev.denissajnar.cqrs.command.core.input.usecase.OrderHistory→dev.denissajnar.cqrs.command.core.domain.OrderIddev.denissajnar.cqrs.command.core.input.usecase.OrderHistory→dev.denissajnar.cqrs.command.core.domain.Pagedev.denissajnar.cqrs.command.core.input.usecase.OrderHistory→dev.denissajnar.cqrs.command.core.domain.Paginationdev.denissajnar.cqrs.command.core.input.usecase.Orders→dev.denissajnar.cqrs.command.core.domain.CreateOrderCommanddev.denissajnar.cqrs.command.core.input.usecase.Orders→dev.denissajnar.cqrs.command.core.domain.DeleteOrderCommanddev.denissajnar.cqrs.command.core.input.usecase.Orders→dev.denissajnar.cqrs.command.core.domain.OrderAggregatedev.denissajnar.cqrs.command.core.input.usecase.Orders→dev.denissajnar.cqrs.command.core.domain.UpdateOrderCommanddev.denissajnar.cqrs.command.core.input.usecase.Outbox→dev.denissajnar.cqrs.command.core.domain.OutboxRecorddev.denissajnar.cqrs.command.core.input.usecase.Outbox→dev.denissajnar.cqrs.command.core.domain.OutboxStatsdev.denissajnar.cqrs.command.core.input.usecase.Outbox→dev.denissajnar.cqrs.command.core.domain.Pagedev.denissajnar.cqrs.command.core.input.usecase.Outbox→dev.denissajnar.cqrs.command.core.domain.Pagination
- Direction
- command.core.input.usecase uses command.core.domain, so a change to command.core.domain can break command.core.input.usecase, while a change to command.core.input.usecase can't break command.core.domain.
- Position
- Below the diagonal: command.core.input.usecase uses a module listed above it, which is the healthy direction.
19→4 command.core.output.port uses shared.events✕
- Connections
- 3 pairs of types, where a type in command.core.output.port uses a type in shared.events.
- The types involved
dev.denissajnar.cqrs.command.core.output.port.EventBrokerPort→dev.denissajnar.cqrs.shared.events.OrderEventdev.denissajnar.cqrs.command.core.output.port.OrderEventRepositoryPort→dev.denissajnar.cqrs.shared.events.OrderEventdev.denissajnar.cqrs.command.core.output.port.OutboxWriter→dev.denissajnar.cqrs.shared.events.OrderEvent
- Direction
- command.core.output.port uses shared.events, so a change to shared.events can break command.core.output.port, while a change to command.core.output.port can't break shared.events.
- Position
- Below the diagonal: command.core.output.port uses a module listed above it, which is the healthy direction.
19→7 command.core.output.port uses command.core.domain✕
- Connections
- 8 pairs of types, where a type in command.core.output.port uses a type in command.core.domain.
- The types involved
dev.denissajnar.cqrs.command.core.output.port.OrderEventRepositoryPort→dev.denissajnar.cqrs.command.core.domain.OrderIddev.denissajnar.cqrs.command.core.output.port.OrderEventRepositoryPort→dev.denissajnar.cqrs.command.core.domain.Pagedev.denissajnar.cqrs.command.core.output.port.OrderEventRepositoryPort→dev.denissajnar.cqrs.command.core.domain.Paginationdev.denissajnar.cqrs.command.core.output.port.OutboxDispatchQueue→dev.denissajnar.cqrs.command.core.domain.OutboxRecorddev.denissajnar.cqrs.command.core.output.port.OutboxQueries→dev.denissajnar.cqrs.command.core.domain.OutboxRecorddev.denissajnar.cqrs.command.core.output.port.OutboxQueries→dev.denissajnar.cqrs.command.core.domain.OutboxStatsdev.denissajnar.cqrs.command.core.output.port.OutboxQueries→dev.denissajnar.cqrs.command.core.domain.Pagedev.denissajnar.cqrs.command.core.output.port.OutboxQueries→dev.denissajnar.cqrs.command.core.domain.Pagination
- Direction
- command.core.output.port uses command.core.domain, so a change to command.core.domain can break command.core.output.port, while a change to command.core.output.port can't break command.core.domain.
- Position
- Below the diagonal: command.core.output.port uses a module listed above it, which is the healthy direction.
20→5 query.adapter.input.rest.dto uses shared.model✕
- Connections
- 1 pair of types, where a type in query.adapter.input.rest.dto uses a type in shared.model.
- The types involved
dev.denissajnar.cqrs.query.adapter.input.rest.dto.OrderResponse→dev.denissajnar.cqrs.shared.model.Status
- Direction
- query.adapter.input.rest.dto uses shared.model, so a change to shared.model can break query.adapter.input.rest.dto, while a change to query.adapter.input.rest.dto can't break shared.model.
- Position
- Below the diagonal: query.adapter.input.rest.dto uses a module listed above it, which is the healthy direction.
20→9 query.adapter.input.rest.dto uses query.core.domain✕
- Connections
- 1 pair of types, where a type in query.adapter.input.rest.dto uses a type in query.core.domain.
- The types involved
dev.denissajnar.cqrs.query.adapter.input.rest.dto.PageParams→dev.denissajnar.cqrs.query.core.domain.Pagination
- Direction
- query.adapter.input.rest.dto uses query.core.domain, so a change to query.core.domain can break query.adapter.input.rest.dto, while a change to query.adapter.input.rest.dto can't break query.core.domain.
- Position
- Below the diagonal: query.adapter.input.rest.dto uses a module listed above it, which is the healthy direction.
21→6 query.adapter.input.rest.exception uses web✕
- Connections
- 1 pair of types, where a type in query.adapter.input.rest.exception uses a type in web.
- The types involved
dev.denissajnar.cqrs.query.adapter.input.rest.exception.RestExceptionHandler→dev.denissajnar.cqrs.web.ProblemDetailHandler
- Direction
- query.adapter.input.rest.exception uses web, so a change to web can break query.adapter.input.rest.exception, while a change to query.adapter.input.rest.exception can't break web.
- Position
- Below the diagonal: query.adapter.input.rest.exception uses a module listed above it, which is the healthy direction.
21→9 query.adapter.input.rest.exception uses query.core.domain✕
- Connections
- 1 pair of types, where a type in query.adapter.input.rest.exception uses a type in query.core.domain.
- The types involved
dev.denissajnar.cqrs.query.adapter.input.rest.exception.RestExceptionHandler→dev.denissajnar.cqrs.query.core.domain.OrderNotFound
- Direction
- query.adapter.input.rest.exception uses query.core.domain, so a change to query.core.domain can break query.adapter.input.rest.exception, while a change to query.adapter.input.rest.exception can't break query.core.domain.
- Position
- Below the diagonal: query.adapter.input.rest.exception uses a module listed above it, which is the healthy direction.
22→5 query.adapter.output.postgresql.entity uses shared.model✕
- Connections
- 1 pair of types, where a type in query.adapter.output.postgresql.entity uses a type in shared.model.
- The types involved
dev.denissajnar.cqrs.query.adapter.output.postgresql.entity.OrderEntity→dev.denissajnar.cqrs.shared.model.Status
- Direction
- query.adapter.output.postgresql.entity uses shared.model, so a change to shared.model can break query.adapter.output.postgresql.entity, while a change to query.adapter.output.postgresql.entity can't break shared.model.
- Position
- Below the diagonal: query.adapter.output.postgresql.entity uses a module listed above it, which is the healthy direction.
22→9 query.adapter.output.postgresql.entity uses query.core.domain✕
- Connections
- 1 pair of types, where a type in query.adapter.output.postgresql.entity uses a type in query.core.domain.
- The types involved
dev.denissajnar.cqrs.query.adapter.output.postgresql.entity.InboxEventEntity→dev.denissajnar.cqrs.query.core.domain.InboxStatus
- Direction
- query.adapter.output.postgresql.entity uses query.core.domain, so a change to query.core.domain can break query.adapter.output.postgresql.entity, while a change to query.adapter.output.postgresql.entity can't break query.core.domain.
- Position
- Below the diagonal: query.adapter.output.postgresql.entity uses a module listed above it, which is the healthy direction.
23→4 query.core.input.usecase uses shared.events✕
- Connections
- 1 pair of types, where a type in query.core.input.usecase uses a type in shared.events.
- The types involved
dev.denissajnar.cqrs.query.core.input.usecase.IncomingEvents→dev.denissajnar.cqrs.shared.events.OrderEvent
- Direction
- query.core.input.usecase uses shared.events, so a change to shared.events can break query.core.input.usecase, while a change to query.core.input.usecase can't break shared.events.
- Position
- Below the diagonal: query.core.input.usecase uses a module listed above it, which is the healthy direction.
23→9 query.core.input.usecase uses query.core.domain✕
- Connections
- 11 pairs of types, where a type in query.core.input.usecase uses a type in query.core.domain.
- The types involved
dev.denissajnar.cqrs.query.core.input.usecase.InboxEvents→dev.denissajnar.cqrs.query.core.domain.InboxEventdev.denissajnar.cqrs.query.core.input.usecase.InboxEvents→dev.denissajnar.cqrs.query.core.domain.InboxStatisticsdev.denissajnar.cqrs.query.core.input.usecase.InboxEvents→dev.denissajnar.cqrs.query.core.domain.InboxStatusdev.denissajnar.cqrs.query.core.input.usecase.InboxEvents→dev.denissajnar.cqrs.query.core.domain.Pagedev.denissajnar.cqrs.query.core.input.usecase.InboxEvents→dev.denissajnar.cqrs.query.core.domain.Paginationdev.denissajnar.cqrs.query.core.input.usecase.Orders→dev.denissajnar.cqrs.query.core.domain.Orderdev.denissajnar.cqrs.query.core.input.usecase.Orders→dev.denissajnar.cqrs.query.core.domain.OrderFilterdev.denissajnar.cqrs.query.core.input.usecase.Orders→dev.denissajnar.cqrs.query.core.domain.OrderIddev.denissajnar.cqrs.query.core.input.usecase.Orders→dev.denissajnar.cqrs.query.core.domain.Pagedev.denissajnar.cqrs.query.core.input.usecase.Orders→dev.denissajnar.cqrs.query.core.domain.Paginationdev.denissajnar.cqrs.query.core.input.usecase.Projections→dev.denissajnar.cqrs.query.core.domain.ProjectionRun
- Direction
- query.core.input.usecase uses query.core.domain, so a change to query.core.domain can break query.core.input.usecase, while a change to query.core.input.usecase can't break query.core.domain.
- Position
- Below the diagonal: query.core.input.usecase uses a module listed above it, which is the healthy direction.
24→4 query.core.output.port uses shared.events✕
- Connections
- 1 pair of types, where a type in query.core.output.port uses a type in shared.events.
- The types involved
dev.denissajnar.cqrs.query.core.output.port.EventPayloadCodecPort→dev.denissajnar.cqrs.shared.events.OrderEvent
- Direction
- query.core.output.port uses shared.events, so a change to shared.events can break query.core.output.port, while a change to query.core.output.port can't break shared.events.
- Position
- Below the diagonal: query.core.output.port uses a module listed above it, which is the healthy direction.
24→9 query.core.output.port uses query.core.domain✕
- Connections
- 11 pairs of types, where a type in query.core.output.port uses a type in query.core.domain.
- The types involved
dev.denissajnar.cqrs.query.core.output.port.InboxClaims→dev.denissajnar.cqrs.query.core.domain.PendingEventdev.denissajnar.cqrs.query.core.output.port.InboxQueries→dev.denissajnar.cqrs.query.core.domain.InboxEventdev.denissajnar.cqrs.query.core.output.port.InboxQueries→dev.denissajnar.cqrs.query.core.domain.InboxStatisticsdev.denissajnar.cqrs.query.core.output.port.InboxQueries→dev.denissajnar.cqrs.query.core.domain.InboxStatusdev.denissajnar.cqrs.query.core.output.port.InboxQueries→dev.denissajnar.cqrs.query.core.domain.Pagedev.denissajnar.cqrs.query.core.output.port.InboxQueries→dev.denissajnar.cqrs.query.core.domain.Paginationdev.denissajnar.cqrs.query.core.output.port.OrderRepositoryPort→dev.denissajnar.cqrs.query.core.domain.Orderdev.denissajnar.cqrs.query.core.output.port.OrderRepositoryPort→dev.denissajnar.cqrs.query.core.domain.OrderFilterdev.denissajnar.cqrs.query.core.output.port.OrderRepositoryPort→dev.denissajnar.cqrs.query.core.domain.OrderIddev.denissajnar.cqrs.query.core.output.port.OrderRepositoryPort→dev.denissajnar.cqrs.query.core.domain.Pagedev.denissajnar.cqrs.query.core.output.port.OrderRepositoryPort→dev.denissajnar.cqrs.query.core.domain.Pagination
- Direction
- query.core.output.port uses query.core.domain, so a change to query.core.domain can break query.core.output.port, while a change to query.core.output.port can't break query.core.domain.
- Position
- Below the diagonal: query.core.output.port uses a module listed above it, which is the healthy direction.
25→7 command.adapter.input.rest.controller uses command.core.domain✕
- Connections
- 1 pair of types, where a type in command.adapter.input.rest.controller uses a type in command.core.domain.
- The types involved
dev.denissajnar.cqrs.command.adapter.input.rest.controller.OrderCommandControllerKt→dev.denissajnar.cqrs.command.core.domain.OrderId
- Direction
- command.adapter.input.rest.controller uses command.core.domain, so a change to command.core.domain can break command.adapter.input.rest.controller, while a change to command.adapter.input.rest.controller can't break command.core.domain.
- Position
- Below the diagonal: command.adapter.input.rest.controller uses a module listed above it, which is the healthy direction.
25→11 command.adapter.input.rest.controller uses command.adapter.input.rest.dto✕
- Connections
- 12 pairs of types, where a type in command.adapter.input.rest.controller uses a type in command.adapter.input.rest.dto.
- The types involved
dev.denissajnar.cqrs.command.adapter.input.rest.controller.EventSourcingController→dev.denissajnar.cqrs.command.adapter.input.rest.dto.AggregateExistsResponsedev.denissajnar.cqrs.command.adapter.input.rest.controller.EventSourcingController→dev.denissajnar.cqrs.command.adapter.input.rest.dto.AggregateStatsResponsedev.denissajnar.cqrs.command.adapter.input.rest.controller.EventSourcingController→dev.denissajnar.cqrs.command.adapter.input.rest.dto.AggregateVersionResponsedev.denissajnar.cqrs.command.adapter.input.rest.controller.EventSourcingController→dev.denissajnar.cqrs.command.adapter.input.rest.dto.OrderEventResponsedev.denissajnar.cqrs.command.adapter.input.rest.controller.EventSourcingController→dev.denissajnar.cqrs.command.adapter.input.rest.dto.OrderResponsedev.denissajnar.cqrs.command.adapter.input.rest.controller.EventSourcingController→dev.denissajnar.cqrs.command.adapter.input.rest.dto.PageResponsedev.denissajnar.cqrs.command.adapter.input.rest.controller.OrderCommandController→dev.denissajnar.cqrs.command.adapter.input.rest.dto.CreateOrderRequestdev.denissajnar.cqrs.command.adapter.input.rest.controller.OrderCommandController→dev.denissajnar.cqrs.command.adapter.input.rest.dto.OrderResponsedev.denissajnar.cqrs.command.adapter.input.rest.controller.OrderCommandController→dev.denissajnar.cqrs.command.adapter.input.rest.dto.UpdateOrderRequestdev.denissajnar.cqrs.command.adapter.input.rest.controller.OutboxController→dev.denissajnar.cqrs.command.adapter.input.rest.dto.OutboxRecordResponsedev.denissajnar.cqrs.command.adapter.input.rest.controller.OutboxController→dev.denissajnar.cqrs.command.adapter.input.rest.dto.OutboxStatsResponsedev.denissajnar.cqrs.command.adapter.input.rest.controller.OutboxController→dev.denissajnar.cqrs.command.adapter.input.rest.dto.PageResponse
- Direction
- command.adapter.input.rest.controller uses command.adapter.input.rest.dto, so a change to command.adapter.input.rest.dto can break command.adapter.input.rest.controller, while a change to command.adapter.input.rest.controller can't break command.adapter.input.rest.dto.
- Position
- Below the diagonal: command.adapter.input.rest.controller uses a module listed above it, which is the healthy direction.
25→18 command.adapter.input.rest.controller uses command.core.input.usecase✕
- Connections
- 3 pairs of types, where a type in command.adapter.input.rest.controller uses a type in command.core.input.usecase.
- The types involved
dev.denissajnar.cqrs.command.adapter.input.rest.controller.EventSourcingController→dev.denissajnar.cqrs.command.core.input.usecase.OrderHistorydev.denissajnar.cqrs.command.adapter.input.rest.controller.OrderCommandController→dev.denissajnar.cqrs.command.core.input.usecase.Ordersdev.denissajnar.cqrs.command.adapter.input.rest.controller.OutboxController→dev.denissajnar.cqrs.command.core.input.usecase.Outbox
- Direction
- command.adapter.input.rest.controller uses command.core.input.usecase, so a change to command.core.input.usecase can break command.adapter.input.rest.controller, while a change to command.adapter.input.rest.controller can't break command.core.input.usecase.
- Position
- Below the diagonal: command.adapter.input.rest.controller uses a module listed above it, which is the healthy direction.
26→7 command.adapter.input.rest.mapper uses command.core.domain✕
- Connections
- 3 pairs of types, where a type in command.adapter.input.rest.mapper uses a type in command.core.domain.
- The types involved
dev.denissajnar.cqrs.command.adapter.input.rest.mapper.OrderMapperKt→dev.denissajnar.cqrs.command.core.domain.CreateOrderCommanddev.denissajnar.cqrs.command.adapter.input.rest.mapper.OrderMapperKt→dev.denissajnar.cqrs.command.core.domain.OrderIddev.denissajnar.cqrs.command.adapter.input.rest.mapper.OrderMapperKt→dev.denissajnar.cqrs.command.core.domain.UpdateOrderCommand
- Direction
- command.adapter.input.rest.mapper uses command.core.domain, so a change to command.core.domain can break command.adapter.input.rest.mapper, while a change to command.adapter.input.rest.mapper can't break command.core.domain.
- Position
- Below the diagonal: command.adapter.input.rest.mapper uses a module listed above it, which is the healthy direction.
26→11 command.adapter.input.rest.mapper uses command.adapter.input.rest.dto✕
- Connections
- 6 pairs of types, where a type in command.adapter.input.rest.mapper uses a type in command.adapter.input.rest.dto.
- The types involved
dev.denissajnar.cqrs.command.adapter.input.rest.mapper.OrderMapperKt→dev.denissajnar.cqrs.command.adapter.input.rest.dto.AggregateStatsResponsedev.denissajnar.cqrs.command.adapter.input.rest.mapper.OrderMapperKt→dev.denissajnar.cqrs.command.adapter.input.rest.dto.OrderEventResponsedev.denissajnar.cqrs.command.adapter.input.rest.mapper.OrderMapperKt→dev.denissajnar.cqrs.command.adapter.input.rest.dto.OrderResponsedev.denissajnar.cqrs.command.adapter.input.rest.mapper.OrderMapperKt→dev.denissajnar.cqrs.command.adapter.input.rest.dto.OutboxRecordResponsedev.denissajnar.cqrs.command.adapter.input.rest.mapper.OrderMapperKt→dev.denissajnar.cqrs.command.adapter.input.rest.dto.OutboxStatsResponsedev.denissajnar.cqrs.command.adapter.input.rest.mapper.OrderMapperKt→dev.denissajnar.cqrs.command.adapter.input.rest.dto.PageResponse
- Direction
- command.adapter.input.rest.mapper uses command.adapter.input.rest.dto, so a change to command.adapter.input.rest.dto can break command.adapter.input.rest.mapper, while a change to command.adapter.input.rest.mapper can't break command.adapter.input.rest.dto.
- Position
- Below the diagonal: command.adapter.input.rest.mapper uses a module listed above it, which is the healthy direction.
27→4 command.adapter.output.mongodb.mapper uses shared.events✕
- Connections
- 1 pair of types, where a type in command.adapter.output.mongodb.mapper uses a type in shared.events.
- The types involved
dev.denissajnar.cqrs.command.adapter.output.mongodb.mapper.OrderEventMapperKt→dev.denissajnar.cqrs.shared.events.OrderEvent
- Direction
- command.adapter.output.mongodb.mapper uses shared.events, so a change to shared.events can break command.adapter.output.mongodb.mapper, while a change to command.adapter.output.mongodb.mapper can't break shared.events.
- Position
- Below the diagonal: command.adapter.output.mongodb.mapper uses a module listed above it, which is the healthy direction.
27→7 command.adapter.output.mongodb.mapper uses command.core.domain✕
- Connections
- 1 pair of types, where a type in command.adapter.output.mongodb.mapper uses a type in command.core.domain.
- The types involved
dev.denissajnar.cqrs.command.adapter.output.mongodb.mapper.OrderEventMapperKt→dev.denissajnar.cqrs.command.core.domain.OutboxRecord
- Direction
- command.adapter.output.mongodb.mapper uses command.core.domain, so a change to command.core.domain can break command.adapter.output.mongodb.mapper, while a change to command.adapter.output.mongodb.mapper can't break command.core.domain.
- Position
- Below the diagonal: command.adapter.output.mongodb.mapper uses a module listed above it, which is the healthy direction.
27→13 command.adapter.output.mongodb.mapper uses command.adapter.output.mongodb.document✕
- Connections
- 1 pair of types, where a type in command.adapter.output.mongodb.mapper uses a type in command.adapter.output.mongodb.document.
- The types involved
dev.denissajnar.cqrs.command.adapter.output.mongodb.mapper.OrderEventMapperKt→dev.denissajnar.cqrs.command.adapter.output.mongodb.document.OrderEventDocument
- Direction
- command.adapter.output.mongodb.mapper uses command.adapter.output.mongodb.document, so a change to command.adapter.output.mongodb.document can break command.adapter.output.mongodb.mapper, while a change to command.adapter.output.mongodb.mapper can't break command.adapter.output.mongodb.document.
- Position
- Below the diagonal: command.adapter.output.mongodb.mapper uses a module listed above it, which is the healthy direction.
28→7 command.adapter.output.mongodb.repository uses command.core.domain✕
- Connections
- 1 pair of types, where a type in command.adapter.output.mongodb.repository uses a type in command.core.domain.
- The types involved
dev.denissajnar.cqrs.command.adapter.output.mongodb.repository.OutboxEventRepository→dev.denissajnar.cqrs.command.core.domain.OutboxState
- Direction
- command.adapter.output.mongodb.repository uses command.core.domain, so a change to command.core.domain can break command.adapter.output.mongodb.repository, while a change to command.adapter.output.mongodb.repository can't break command.core.domain.
- Position
- Below the diagonal: command.adapter.output.mongodb.repository uses a module listed above it, which is the healthy direction.
28→13 command.adapter.output.mongodb.repository uses command.adapter.output.mongodb.document✕
- Connections
- 2 pairs of types, where a type in command.adapter.output.mongodb.repository uses a type in command.adapter.output.mongodb.document.
- The types involved
dev.denissajnar.cqrs.command.adapter.output.mongodb.repository.OrderEventRepository→dev.denissajnar.cqrs.command.adapter.output.mongodb.document.OrderEventDocumentdev.denissajnar.cqrs.command.adapter.output.mongodb.repository.OutboxEventRepository→dev.denissajnar.cqrs.command.adapter.output.mongodb.document.OutboxEventDocument
- Direction
- command.adapter.output.mongodb.repository uses command.adapter.output.mongodb.document, so a change to command.adapter.output.mongodb.document can break command.adapter.output.mongodb.repository, while a change to command.adapter.output.mongodb.repository can't break command.adapter.output.mongodb.document.
- Position
- Below the diagonal: command.adapter.output.mongodb.repository uses a module listed above it, which is the healthy direction.
29→1 command.adapter.output.rabbitmq.adapter uses command.adapter.output.rabbitmq.config✕
- Connections
- 1 pair of types, where a type in command.adapter.output.rabbitmq.adapter uses a type in command.adapter.output.rabbitmq.config.
- The types involved
dev.denissajnar.cqrs.command.adapter.output.rabbitmq.adapter.RabbitEventBrokerAdapter→dev.denissajnar.cqrs.command.adapter.output.rabbitmq.config.MessagingProperties
- Direction
- command.adapter.output.rabbitmq.adapter uses command.adapter.output.rabbitmq.config, so a change to command.adapter.output.rabbitmq.config can break command.adapter.output.rabbitmq.adapter, while a change to command.adapter.output.rabbitmq.adapter can't break command.adapter.output.rabbitmq.config.
- Position
- Below the diagonal: command.adapter.output.rabbitmq.adapter uses a module listed above it, which is the healthy direction.
29→4 command.adapter.output.rabbitmq.adapter uses shared.events✕
- Connections
- 1 pair of types, where a type in command.adapter.output.rabbitmq.adapter uses a type in shared.events.
- The types involved
dev.denissajnar.cqrs.command.adapter.output.rabbitmq.adapter.RabbitEventBrokerAdapter→dev.denissajnar.cqrs.shared.events.OrderEvent
- Direction
- command.adapter.output.rabbitmq.adapter uses shared.events, so a change to shared.events can break command.adapter.output.rabbitmq.adapter, while a change to command.adapter.output.rabbitmq.adapter can't break shared.events.
- Position
- Below the diagonal: command.adapter.output.rabbitmq.adapter uses a module listed above it, which is the healthy direction.
29→19 command.adapter.output.rabbitmq.adapter uses command.core.output.port✕
- Connections
- 1 pair of types, where a type in command.adapter.output.rabbitmq.adapter uses a type in command.core.output.port.
- The types involved
dev.denissajnar.cqrs.command.adapter.output.rabbitmq.adapter.RabbitEventBrokerAdapter→dev.denissajnar.cqrs.command.core.output.port.EventBrokerPort
- Direction
- command.adapter.output.rabbitmq.adapter uses command.core.output.port, so a change to command.core.output.port can break command.adapter.output.rabbitmq.adapter, while a change to command.adapter.output.rabbitmq.adapter can't break command.core.output.port.
- Position
- Below the diagonal: command.adapter.output.rabbitmq.adapter uses a module listed above it, which is the healthy direction.
30→4 command.core.impl uses shared.events✕
- Connections
- 2 pairs of types, where a type in command.core.impl uses a type in shared.events.
- The types involved
dev.denissajnar.cqrs.command.core.impl.OrderHistoryImpl→dev.denissajnar.cqrs.shared.events.OrderEventdev.denissajnar.cqrs.command.core.impl.OrdersImpl→dev.denissajnar.cqrs.shared.events.OrderEvent
- Direction
- command.core.impl uses shared.events, so a change to shared.events can break command.core.impl, while a change to command.core.impl can't break shared.events.
- Position
- Below the diagonal: command.core.impl uses a module listed above it, which is the healthy direction.
30→7 command.core.impl uses command.core.domain✕
- Connections
- 15 pairs of types, where a type in command.core.impl uses a type in command.core.domain.
- The types involved
dev.denissajnar.cqrs.command.core.impl.OrderHistoryImpl→dev.denissajnar.cqrs.command.core.domain.AggregateStatsdev.denissajnar.cqrs.command.core.impl.OrderHistoryImpl→dev.denissajnar.cqrs.command.core.domain.OrderAggregatedev.denissajnar.cqrs.command.core.impl.OrderHistoryImpl→dev.denissajnar.cqrs.command.core.domain.OrderIddev.denissajnar.cqrs.command.core.impl.OrderHistoryImpl→dev.denissajnar.cqrs.command.core.domain.Pagedev.denissajnar.cqrs.command.core.impl.OrderHistoryImpl→dev.denissajnar.cqrs.command.core.domain.Paginationdev.denissajnar.cqrs.command.core.impl.OrdersImpl→dev.denissajnar.cqrs.command.core.domain.CreateOrderCommanddev.denissajnar.cqrs.command.core.impl.OrdersImpl→dev.denissajnar.cqrs.command.core.domain.DeleteOrderCommanddev.denissajnar.cqrs.command.core.impl.OrdersImpl→dev.denissajnar.cqrs.command.core.domain.OrderAggregatedev.denissajnar.cqrs.command.core.impl.OrdersImpl→dev.denissajnar.cqrs.command.core.domain.OrderIddev.denissajnar.cqrs.command.core.impl.OrdersImpl→dev.denissajnar.cqrs.command.core.domain.UpdateOrderCommanddev.denissajnar.cqrs.command.core.impl.OutboxDispatchImpl→dev.denissajnar.cqrs.command.core.domain.OutboxRecorddev.denissajnar.cqrs.command.core.impl.OutboxImpl→dev.denissajnar.cqrs.command.core.domain.OutboxRecorddev.denissajnar.cqrs.command.core.impl.OutboxImpl→dev.denissajnar.cqrs.command.core.domain.OutboxStatsdev.denissajnar.cqrs.command.core.impl.OutboxImpl→dev.denissajnar.cqrs.command.core.domain.Pagedev.denissajnar.cqrs.command.core.impl.OutboxImpl→dev.denissajnar.cqrs.command.core.domain.Pagination
- Direction
- command.core.impl uses command.core.domain, so a change to command.core.domain can break command.core.impl, while a change to command.core.impl can't break command.core.domain.
- Position
- Below the diagonal: command.core.impl uses a module listed above it, which is the healthy direction.
30→18 command.core.impl uses command.core.input.usecase✕
- Connections
- 4 pairs of types, where a type in command.core.impl uses a type in command.core.input.usecase.
- The types involved
dev.denissajnar.cqrs.command.core.impl.OrderHistoryImpl→dev.denissajnar.cqrs.command.core.input.usecase.OrderHistorydev.denissajnar.cqrs.command.core.impl.OrdersImpl→dev.denissajnar.cqrs.command.core.input.usecase.Ordersdev.denissajnar.cqrs.command.core.impl.OutboxDispatchImpl→dev.denissajnar.cqrs.command.core.input.usecase.OutboxDispatchdev.denissajnar.cqrs.command.core.impl.OutboxImpl→dev.denissajnar.cqrs.command.core.input.usecase.Outbox
- Direction
- command.core.impl uses command.core.input.usecase, so a change to command.core.input.usecase can break command.core.impl, while a change to command.core.impl can't break command.core.input.usecase.
- Position
- Below the diagonal: command.core.impl uses a module listed above it, which is the healthy direction.
30→19 command.core.impl uses command.core.output.port✕
- Connections
- 6 pairs of types, where a type in command.core.impl uses a type in command.core.output.port.
- The types involved
dev.denissajnar.cqrs.command.core.impl.OrderHistoryImpl→dev.denissajnar.cqrs.command.core.output.port.OrderEventRepositoryPortdev.denissajnar.cqrs.command.core.impl.OrdersImpl→dev.denissajnar.cqrs.command.core.output.port.OrderEventRepositoryPortdev.denissajnar.cqrs.command.core.impl.OrdersImpl→dev.denissajnar.cqrs.command.core.output.port.OutboxWriterdev.denissajnar.cqrs.command.core.impl.OutboxDispatchImpl→dev.denissajnar.cqrs.command.core.output.port.EventBrokerPortdev.denissajnar.cqrs.command.core.impl.OutboxDispatchImpl→dev.denissajnar.cqrs.command.core.output.port.OutboxDispatchQueuedev.denissajnar.cqrs.command.core.impl.OutboxImpl→dev.denissajnar.cqrs.command.core.output.port.OutboxQueries
- Direction
- command.core.impl uses command.core.output.port, so a change to command.core.output.port can break command.core.impl, while a change to command.core.impl can't break command.core.output.port.
- Position
- Below the diagonal: command.core.impl uses a module listed above it, which is the healthy direction.
31→19 command.core.output.port.AppendResult uses command.core.output.port✕
- Connections
- 2 pairs of types, where a type in command.core.output.port.AppendResult uses a type in command.core.output.port.
- The types involved
dev.denissajnar.cqrs.command.core.output.port.AppendResult.Appended→dev.denissajnar.cqrs.command.core.output.port.AppendResultdev.denissajnar.cqrs.command.core.output.port.AppendResult.VersionTaken→dev.denissajnar.cqrs.command.core.output.port.AppendResult
- Direction
- command.core.output.port.AppendResult uses command.core.output.port, so a change to command.core.output.port can break command.core.output.port.AppendResult, while a change to command.core.output.port.AppendResult can't break command.core.output.port.
- Position
- Below the diagonal: command.core.output.port.AppendResult uses a module listed above it, which is the healthy direction.
32→18 command.scheduling uses command.core.input.usecase✕
- Connections
- 1 pair of types, where a type in command.scheduling uses a type in command.core.input.usecase.
- The types involved
dev.denissajnar.cqrs.command.scheduling.OutboxDispatchScheduler→dev.denissajnar.cqrs.command.core.input.usecase.OutboxDispatch
- Direction
- command.scheduling uses command.core.input.usecase, so a change to command.core.input.usecase can break command.scheduling, while a change to command.scheduling can't break command.core.input.usecase.
- Position
- Below the diagonal: command.scheduling uses a module listed above it, which is the healthy direction.
33→4 query.adapter.input.rabbitmq.listener uses shared.events✕
- Connections
- 1 pair of types, where a type in query.adapter.input.rabbitmq.listener uses a type in shared.events.
- The types involved
dev.denissajnar.cqrs.query.adapter.input.rabbitmq.listener.OrderEventListener→dev.denissajnar.cqrs.shared.events.OrderEvent
- Direction
- query.adapter.input.rabbitmq.listener uses shared.events, so a change to shared.events can break query.adapter.input.rabbitmq.listener, while a change to query.adapter.input.rabbitmq.listener can't break shared.events.
- Position
- Below the diagonal: query.adapter.input.rabbitmq.listener uses a module listed above it, which is the healthy direction.
33→23 query.adapter.input.rabbitmq.listener uses query.core.input.usecase✕
- Connections
- 1 pair of types, where a type in query.adapter.input.rabbitmq.listener uses a type in query.core.input.usecase.
- The types involved
dev.denissajnar.cqrs.query.adapter.input.rabbitmq.listener.OrderEventListener→dev.denissajnar.cqrs.query.core.input.usecase.IncomingEvents
- Direction
- query.adapter.input.rabbitmq.listener uses query.core.input.usecase, so a change to query.core.input.usecase can break query.adapter.input.rabbitmq.listener, while a change to query.adapter.input.rabbitmq.listener can't break query.core.input.usecase.
- Position
- Below the diagonal: query.adapter.input.rabbitmq.listener uses a module listed above it, which is the healthy direction.
34→5 query.adapter.input.rest.controller uses shared.model✕
- Connections
- 1 pair of types, where a type in query.adapter.input.rest.controller uses a type in shared.model.
- The types involved
dev.denissajnar.cqrs.query.adapter.input.rest.controller.OrderController→dev.denissajnar.cqrs.shared.model.Status
- Direction
- query.adapter.input.rest.controller uses shared.model, so a change to shared.model can break query.adapter.input.rest.controller, while a change to query.adapter.input.rest.controller can't break shared.model.
- Position
- Below the diagonal: query.adapter.input.rest.controller uses a module listed above it, which is the healthy direction.
34→20 query.adapter.input.rest.controller uses query.adapter.input.rest.dto✕
- Connections
- 8 pairs of types, where a type in query.adapter.input.rest.controller uses a type in query.adapter.input.rest.dto.
- The types involved
dev.denissajnar.cqrs.query.adapter.input.rest.controller.InboxController→dev.denissajnar.cqrs.query.adapter.input.rest.dto.InboxEventResponsedev.denissajnar.cqrs.query.adapter.input.rest.controller.InboxController→dev.denissajnar.cqrs.query.adapter.input.rest.dto.InboxEventStatusDtodev.denissajnar.cqrs.query.adapter.input.rest.controller.InboxController→dev.denissajnar.cqrs.query.adapter.input.rest.dto.InboxStatsResponsedev.denissajnar.cqrs.query.adapter.input.rest.controller.InboxController→dev.denissajnar.cqrs.query.adapter.input.rest.dto.PageParamsdev.denissajnar.cqrs.query.adapter.input.rest.controller.InboxController→dev.denissajnar.cqrs.query.adapter.input.rest.dto.PageResponsedev.denissajnar.cqrs.query.adapter.input.rest.controller.OrderController→dev.denissajnar.cqrs.query.adapter.input.rest.dto.OrderResponsedev.denissajnar.cqrs.query.adapter.input.rest.controller.OrderController→dev.denissajnar.cqrs.query.adapter.input.rest.dto.PageParamsdev.denissajnar.cqrs.query.adapter.input.rest.controller.OrderController→dev.denissajnar.cqrs.query.adapter.input.rest.dto.PageResponse
- Direction
- query.adapter.input.rest.controller uses query.adapter.input.rest.dto, so a change to query.adapter.input.rest.dto can break query.adapter.input.rest.controller, while a change to query.adapter.input.rest.controller can't break query.adapter.input.rest.dto.
- Position
- Below the diagonal: query.adapter.input.rest.controller uses a module listed above it, which is the healthy direction.
34→23 query.adapter.input.rest.controller uses query.core.input.usecase✕
- Connections
- 2 pairs of types, where a type in query.adapter.input.rest.controller uses a type in query.core.input.usecase.
- The types involved
dev.denissajnar.cqrs.query.adapter.input.rest.controller.InboxController→dev.denissajnar.cqrs.query.core.input.usecase.InboxEventsdev.denissajnar.cqrs.query.adapter.input.rest.controller.OrderController→dev.denissajnar.cqrs.query.core.input.usecase.Orders
- Direction
- query.adapter.input.rest.controller uses query.core.input.usecase, so a change to query.core.input.usecase can break query.adapter.input.rest.controller, while a change to query.adapter.input.rest.controller can't break query.core.input.usecase.
- Position
- Below the diagonal: query.adapter.input.rest.controller uses a module listed above it, which is the healthy direction.
35→9 query.adapter.input.rest.mapper uses query.core.domain✕
- Connections
- 1 pair of types, where a type in query.adapter.input.rest.mapper uses a type in query.core.domain.
- The types involved
dev.denissajnar.cqrs.query.adapter.input.rest.mapper.ResponseMappersKt→dev.denissajnar.cqrs.query.core.domain.InboxStatus
- Direction
- query.adapter.input.rest.mapper uses query.core.domain, so a change to query.core.domain can break query.adapter.input.rest.mapper, while a change to query.adapter.input.rest.mapper can't break query.core.domain.
- Position
- Below the diagonal: query.adapter.input.rest.mapper uses a module listed above it, which is the healthy direction.
35→20 query.adapter.input.rest.mapper uses query.adapter.input.rest.dto✕
- Connections
- 5 pairs of types, where a type in query.adapter.input.rest.mapper uses a type in query.adapter.input.rest.dto.
- The types involved
dev.denissajnar.cqrs.query.adapter.input.rest.mapper.ResponseMappersKt→dev.denissajnar.cqrs.query.adapter.input.rest.dto.InboxEventResponsedev.denissajnar.cqrs.query.adapter.input.rest.mapper.ResponseMappersKt→dev.denissajnar.cqrs.query.adapter.input.rest.dto.InboxEventStatusDtodev.denissajnar.cqrs.query.adapter.input.rest.mapper.ResponseMappersKt→dev.denissajnar.cqrs.query.adapter.input.rest.dto.InboxStatsResponsedev.denissajnar.cqrs.query.adapter.input.rest.mapper.ResponseMappersKt→dev.denissajnar.cqrs.query.adapter.input.rest.dto.OrderResponsedev.denissajnar.cqrs.query.adapter.input.rest.mapper.ResponseMappersKt→dev.denissajnar.cqrs.query.adapter.input.rest.dto.PageResponse
- Direction
- query.adapter.input.rest.mapper uses query.adapter.input.rest.dto, so a change to query.adapter.input.rest.dto can break query.adapter.input.rest.mapper, while a change to query.adapter.input.rest.mapper can't break query.adapter.input.rest.dto.
- Position
- Below the diagonal: query.adapter.input.rest.mapper uses a module listed above it, which is the healthy direction.
36→9 query.adapter.output.postgresql.mapper uses query.core.domain✕
- Connections
- 5 pairs of types, where a type in query.adapter.output.postgresql.mapper uses a type in query.core.domain.
- The types involved
dev.denissajnar.cqrs.query.adapter.output.postgresql.mapper.EntityMappersKt→dev.denissajnar.cqrs.query.core.domain.InboxEventdev.denissajnar.cqrs.query.adapter.output.postgresql.mapper.EntityMappersKt→dev.denissajnar.cqrs.query.core.domain.Orderdev.denissajnar.cqrs.query.adapter.output.postgresql.mapper.EntityMappersKt→dev.denissajnar.cqrs.query.core.domain.Pagedev.denissajnar.cqrs.query.adapter.output.postgresql.mapper.EntityMappersKt→dev.denissajnar.cqrs.query.core.domain.Paginationdev.denissajnar.cqrs.query.adapter.output.postgresql.mapper.EntityMappersKt→dev.denissajnar.cqrs.query.core.domain.PendingEvent
- Direction
- query.adapter.output.postgresql.mapper uses query.core.domain, so a change to query.core.domain can break query.adapter.output.postgresql.mapper, while a change to query.adapter.output.postgresql.mapper can't break query.core.domain.
- Position
- Below the diagonal: query.adapter.output.postgresql.mapper uses a module listed above it, which is the healthy direction.
36→22 query.adapter.output.postgresql.mapper uses query.adapter.output.postgresql.entity✕
- Connections
- 1 pair of types, where a type in query.adapter.output.postgresql.mapper uses a type in query.adapter.output.postgresql.entity.
- The types involved
dev.denissajnar.cqrs.query.adapter.output.postgresql.mapper.EntityMappersKt→dev.denissajnar.cqrs.query.adapter.output.postgresql.entity.OrderEntity
- Direction
- query.adapter.output.postgresql.mapper uses query.adapter.output.postgresql.entity, so a change to query.adapter.output.postgresql.entity can break query.adapter.output.postgresql.mapper, while a change to query.adapter.output.postgresql.mapper can't break query.adapter.output.postgresql.entity.
- Position
- Below the diagonal: query.adapter.output.postgresql.mapper uses a module listed above it, which is the healthy direction.
37→5 query.adapter.output.postgresql.repository uses shared.model✕
- Connections
- 1 pair of types, where a type in query.adapter.output.postgresql.repository uses a type in shared.model.
- The types involved
dev.denissajnar.cqrs.query.adapter.output.postgresql.repository.OrderRepository→dev.denissajnar.cqrs.shared.model.Status
- Direction
- query.adapter.output.postgresql.repository uses shared.model, so a change to shared.model can break query.adapter.output.postgresql.repository, while a change to query.adapter.output.postgresql.repository can't break shared.model.
- Position
- Below the diagonal: query.adapter.output.postgresql.repository uses a module listed above it, which is the healthy direction.
37→9 query.adapter.output.postgresql.repository uses query.core.domain✕
- Connections
- 1 pair of types, where a type in query.adapter.output.postgresql.repository uses a type in query.core.domain.
- The types involved
dev.denissajnar.cqrs.query.adapter.output.postgresql.repository.InboxEventRepository→dev.denissajnar.cqrs.query.core.domain.InboxStatus
- Direction
- query.adapter.output.postgresql.repository uses query.core.domain, so a change to query.core.domain can break query.adapter.output.postgresql.repository, while a change to query.adapter.output.postgresql.repository can't break query.core.domain.
- Position
- Below the diagonal: query.adapter.output.postgresql.repository uses a module listed above it, which is the healthy direction.
37→22 query.adapter.output.postgresql.repository uses query.adapter.output.postgresql.entity✕
- Connections
- 2 pairs of types, where a type in query.adapter.output.postgresql.repository uses a type in query.adapter.output.postgresql.entity.
- The types involved
dev.denissajnar.cqrs.query.adapter.output.postgresql.repository.InboxEventRepository→dev.denissajnar.cqrs.query.adapter.output.postgresql.entity.InboxEventEntitydev.denissajnar.cqrs.query.adapter.output.postgresql.repository.OrderRepository→dev.denissajnar.cqrs.query.adapter.output.postgresql.entity.OrderEntity
- Direction
- query.adapter.output.postgresql.repository uses query.adapter.output.postgresql.entity, so a change to query.adapter.output.postgresql.entity can break query.adapter.output.postgresql.repository, while a change to query.adapter.output.postgresql.repository can't break query.adapter.output.postgresql.entity.
- Position
- Below the diagonal: query.adapter.output.postgresql.repository uses a module listed above it, which is the healthy direction.
38→3 query.core.impl uses query.core.impl.ProjectionsImpl✕
- Connections
- 1 pair of types, where a type in query.core.impl uses a type in query.core.impl.ProjectionsImpl.
- The types involved
dev.denissajnar.cqrs.query.core.impl.ProjectionsImpl→dev.denissajnar.cqrs.query.core.impl.ProjectionsImpl.Outcome
- Direction
- query.core.impl uses query.core.impl.ProjectionsImpl, so a change to query.core.impl.ProjectionsImpl can break query.core.impl, while a change to query.core.impl can't break query.core.impl.ProjectionsImpl.
- Position
- Below the diagonal: query.core.impl uses a module listed above it, which is the healthy direction.
38→4 query.core.impl uses shared.events✕
- Connections
- 1 pair of types, where a type in query.core.impl uses a type in shared.events.
- The types involved
dev.denissajnar.cqrs.query.core.impl.IncomingEventsImpl→dev.denissajnar.cqrs.shared.events.OrderEvent
- Direction
- query.core.impl uses shared.events, so a change to shared.events can break query.core.impl, while a change to query.core.impl can't break shared.events.
- Position
- Below the diagonal: query.core.impl uses a module listed above it, which is the healthy direction.
38→9 query.core.impl uses query.core.domain✕
- Connections
- 14 pairs of types, where a type in query.core.impl uses a type in query.core.domain.
- The types involved
dev.denissajnar.cqrs.query.core.impl.EventProjector→dev.denissajnar.cqrs.query.core.domain.PendingEventdev.denissajnar.cqrs.query.core.impl.InboxEventsImpl→dev.denissajnar.cqrs.query.core.domain.InboxEventdev.denissajnar.cqrs.query.core.impl.InboxEventsImpl→dev.denissajnar.cqrs.query.core.domain.InboxStatisticsdev.denissajnar.cqrs.query.core.impl.InboxEventsImpl→dev.denissajnar.cqrs.query.core.domain.InboxStatusdev.denissajnar.cqrs.query.core.impl.InboxEventsImpl→dev.denissajnar.cqrs.query.core.domain.Pagedev.denissajnar.cqrs.query.core.impl.InboxEventsImpl→dev.denissajnar.cqrs.query.core.domain.Paginationdev.denissajnar.cqrs.query.core.impl.OrdersImpl→dev.denissajnar.cqrs.query.core.domain.Orderdev.denissajnar.cqrs.query.core.impl.OrdersImpl→dev.denissajnar.cqrs.query.core.domain.OrderFilterdev.denissajnar.cqrs.query.core.impl.OrdersImpl→dev.denissajnar.cqrs.query.core.domain.OrderIddev.denissajnar.cqrs.query.core.impl.OrdersImpl→dev.denissajnar.cqrs.query.core.domain.Pagedev.denissajnar.cqrs.query.core.impl.OrdersImpl→dev.denissajnar.cqrs.query.core.domain.Paginationdev.denissajnar.cqrs.query.core.impl.ProjectionsImpl→dev.denissajnar.cqrs.query.core.domain.PendingEventdev.denissajnar.cqrs.query.core.impl.ProjectionsImpl→dev.denissajnar.cqrs.query.core.domain.ProjectionRundev.denissajnar.cqrs.query.core.impl.ProjectionsImplKt→dev.denissajnar.cqrs.query.core.domain.ProjectionRun
- Direction
- query.core.impl uses query.core.domain, so a change to query.core.domain can break query.core.impl, while a change to query.core.impl can't break query.core.domain.
- Position
- Below the diagonal: query.core.impl uses a module listed above it, which is the healthy direction.
38→23 query.core.impl uses query.core.input.usecase✕
- Connections
- 4 pairs of types, where a type in query.core.impl uses a type in query.core.input.usecase.
- The types involved
dev.denissajnar.cqrs.query.core.impl.InboxEventsImpl→dev.denissajnar.cqrs.query.core.input.usecase.InboxEventsdev.denissajnar.cqrs.query.core.impl.IncomingEventsImpl→dev.denissajnar.cqrs.query.core.input.usecase.IncomingEventsdev.denissajnar.cqrs.query.core.impl.OrdersImpl→dev.denissajnar.cqrs.query.core.input.usecase.Ordersdev.denissajnar.cqrs.query.core.impl.ProjectionsImpl→dev.denissajnar.cqrs.query.core.input.usecase.Projections
- Direction
- query.core.impl uses query.core.input.usecase, so a change to query.core.input.usecase can break query.core.impl, while a change to query.core.impl can't break query.core.input.usecase.
- Position
- Below the diagonal: query.core.impl uses a module listed above it, which is the healthy direction.
38→24 query.core.impl uses query.core.output.port✕
- Connections
- 8 pairs of types, where a type in query.core.impl uses a type in query.core.output.port.
- The types involved
dev.denissajnar.cqrs.query.core.impl.EventProjector→dev.denissajnar.cqrs.query.core.output.port.EventPayloadCodecPortdev.denissajnar.cqrs.query.core.impl.EventProjector→dev.denissajnar.cqrs.query.core.output.port.InboxClaimsdev.denissajnar.cqrs.query.core.impl.EventProjector→dev.denissajnar.cqrs.query.core.output.port.OrderRepositoryPortdev.denissajnar.cqrs.query.core.impl.InboxEventsImpl→dev.denissajnar.cqrs.query.core.output.port.InboxQueriesdev.denissajnar.cqrs.query.core.impl.IncomingEventsImpl→dev.denissajnar.cqrs.query.core.output.port.EventPayloadCodecPortdev.denissajnar.cqrs.query.core.impl.IncomingEventsImpl→dev.denissajnar.cqrs.query.core.output.port.InboxWriterdev.denissajnar.cqrs.query.core.impl.OrdersImpl→dev.denissajnar.cqrs.query.core.output.port.OrderRepositoryPortdev.denissajnar.cqrs.query.core.impl.ProjectionsImpl→dev.denissajnar.cqrs.query.core.output.port.InboxClaims
- Direction
- query.core.impl uses query.core.output.port, so a change to query.core.output.port can break query.core.impl, while a change to query.core.impl can't break query.core.output.port.
- Position
- Below the diagonal: query.core.impl uses a module listed above it, which is the healthy direction.
39→4 command.adapter.output.mongodb.adapter uses shared.events✕
- Connections
- 2 pairs of types, where a type in command.adapter.output.mongodb.adapter uses a type in shared.events.
- The types involved
dev.denissajnar.cqrs.command.adapter.output.mongodb.adapter.OrderEventPersistenceAdapter→dev.denissajnar.cqrs.shared.events.OrderEventdev.denissajnar.cqrs.command.adapter.output.mongodb.adapter.OutboxPersistenceAdapter→dev.denissajnar.cqrs.shared.events.OrderEvent
- Direction
- command.adapter.output.mongodb.adapter uses shared.events, so a change to shared.events can break command.adapter.output.mongodb.adapter, while a change to command.adapter.output.mongodb.adapter can't break shared.events.
- Position
- Below the diagonal: command.adapter.output.mongodb.adapter uses a module listed above it, which is the healthy direction.
39→7 command.adapter.output.mongodb.adapter uses command.core.domain✕
- Connections
- 9 pairs of types, where a type in command.adapter.output.mongodb.adapter uses a type in command.core.domain.
- The types involved
dev.denissajnar.cqrs.command.adapter.output.mongodb.adapter.OrderEventPersistenceAdapter→dev.denissajnar.cqrs.command.core.domain.OrderIddev.denissajnar.cqrs.command.adapter.output.mongodb.adapter.OrderEventPersistenceAdapter→dev.denissajnar.cqrs.command.core.domain.Pagedev.denissajnar.cqrs.command.adapter.output.mongodb.adapter.OrderEventPersistenceAdapter→dev.denissajnar.cqrs.command.core.domain.Paginationdev.denissajnar.cqrs.command.adapter.output.mongodb.adapter.OutboxPersistenceAdapter→dev.denissajnar.cqrs.command.core.domain.OutboxRecorddev.denissajnar.cqrs.command.adapter.output.mongodb.adapter.OutboxPersistenceAdapter→dev.denissajnar.cqrs.command.core.domain.OutboxStatsdev.denissajnar.cqrs.command.adapter.output.mongodb.adapter.OutboxPersistenceAdapter→dev.denissajnar.cqrs.command.core.domain.Pagedev.denissajnar.cqrs.command.adapter.output.mongodb.adapter.OutboxPersistenceAdapter→dev.denissajnar.cqrs.command.core.domain.Paginationdev.denissajnar.cqrs.command.adapter.output.mongodb.adapter.OutboxPersistenceAdapterKt→dev.denissajnar.cqrs.command.core.domain.OutboxStatedev.denissajnar.cqrs.command.adapter.output.mongodb.adapter.OutboxPersistenceAdapterKt→dev.denissajnar.cqrs.command.core.domain.Pagination
- Direction
- command.adapter.output.mongodb.adapter uses command.core.domain, so a change to command.core.domain can break command.adapter.output.mongodb.adapter, while a change to command.adapter.output.mongodb.adapter can't break command.core.domain.
- Position
- Below the diagonal: command.adapter.output.mongodb.adapter uses a module listed above it, which is the healthy direction.
39→19 command.adapter.output.mongodb.adapter uses command.core.output.port✕
- Connections
- 5 pairs of types, where a type in command.adapter.output.mongodb.adapter uses a type in command.core.output.port.
- The types involved
dev.denissajnar.cqrs.command.adapter.output.mongodb.adapter.OrderEventPersistenceAdapter→dev.denissajnar.cqrs.command.core.output.port.AppendResultdev.denissajnar.cqrs.command.adapter.output.mongodb.adapter.OrderEventPersistenceAdapter→dev.denissajnar.cqrs.command.core.output.port.OrderEventRepositoryPortdev.denissajnar.cqrs.command.adapter.output.mongodb.adapter.OutboxPersistenceAdapter→dev.denissajnar.cqrs.command.core.output.port.OutboxDispatchQueuedev.denissajnar.cqrs.command.adapter.output.mongodb.adapter.OutboxPersistenceAdapter→dev.denissajnar.cqrs.command.core.output.port.OutboxQueriesdev.denissajnar.cqrs.command.adapter.output.mongodb.adapter.OutboxPersistenceAdapter→dev.denissajnar.cqrs.command.core.output.port.OutboxWriter
- Direction
- command.adapter.output.mongodb.adapter uses command.core.output.port, so a change to command.core.output.port can break command.adapter.output.mongodb.adapter, while a change to command.adapter.output.mongodb.adapter can't break command.core.output.port.
- Position
- Below the diagonal: command.adapter.output.mongodb.adapter uses a module listed above it, which is the healthy direction.
39→28 command.adapter.output.mongodb.adapter uses command.adapter.output.mongodb.repository✕
- Connections
- 2 pairs of types, where a type in command.adapter.output.mongodb.adapter uses a type in command.adapter.output.mongodb.repository.
- The types involved
dev.denissajnar.cqrs.command.adapter.output.mongodb.adapter.OrderEventPersistenceAdapter→dev.denissajnar.cqrs.command.adapter.output.mongodb.repository.OrderEventRepositorydev.denissajnar.cqrs.command.adapter.output.mongodb.adapter.OutboxPersistenceAdapter→dev.denissajnar.cqrs.command.adapter.output.mongodb.repository.OutboxEventRepository
- Direction
- command.adapter.output.mongodb.adapter uses command.adapter.output.mongodb.repository, so a change to command.adapter.output.mongodb.repository can break command.adapter.output.mongodb.adapter, while a change to command.adapter.output.mongodb.adapter can't break command.adapter.output.mongodb.repository.
- Position
- Below the diagonal: command.adapter.output.mongodb.adapter uses a module listed above it, which is the healthy direction.
40→4 query.adapter.output.postgresql.adapter uses shared.events✕
- Connections
- 1 pair of types, where a type in query.adapter.output.postgresql.adapter uses a type in shared.events.
- The types involved
dev.denissajnar.cqrs.query.adapter.output.postgresql.adapter.InboxPayloadCodec→dev.denissajnar.cqrs.shared.events.OrderEvent
- Direction
- query.adapter.output.postgresql.adapter uses shared.events, so a change to shared.events can break query.adapter.output.postgresql.adapter, while a change to query.adapter.output.postgresql.adapter can't break shared.events.
- Position
- Below the diagonal: query.adapter.output.postgresql.adapter uses a module listed above it, which is the healthy direction.
40→9 query.adapter.output.postgresql.adapter uses query.core.domain✕
- Connections
- 11 pairs of types, where a type in query.adapter.output.postgresql.adapter uses a type in query.core.domain.
- The types involved
dev.denissajnar.cqrs.query.adapter.output.postgresql.adapter.InboxPersistenceAdapter→dev.denissajnar.cqrs.query.core.domain.InboxEventdev.denissajnar.cqrs.query.adapter.output.postgresql.adapter.InboxPersistenceAdapter→dev.denissajnar.cqrs.query.core.domain.InboxStatisticsdev.denissajnar.cqrs.query.adapter.output.postgresql.adapter.InboxPersistenceAdapter→dev.denissajnar.cqrs.query.core.domain.InboxStatusdev.denissajnar.cqrs.query.adapter.output.postgresql.adapter.InboxPersistenceAdapter→dev.denissajnar.cqrs.query.core.domain.Pagedev.denissajnar.cqrs.query.adapter.output.postgresql.adapter.InboxPersistenceAdapter→dev.denissajnar.cqrs.query.core.domain.Paginationdev.denissajnar.cqrs.query.adapter.output.postgresql.adapter.InboxPersistenceAdapter→dev.denissajnar.cqrs.query.core.domain.PendingEventdev.denissajnar.cqrs.query.adapter.output.postgresql.adapter.OrderPersistenceAdapter→dev.denissajnar.cqrs.query.core.domain.Orderdev.denissajnar.cqrs.query.adapter.output.postgresql.adapter.OrderPersistenceAdapter→dev.denissajnar.cqrs.query.core.domain.OrderFilterdev.denissajnar.cqrs.query.adapter.output.postgresql.adapter.OrderPersistenceAdapter→dev.denissajnar.cqrs.query.core.domain.OrderIddev.denissajnar.cqrs.query.adapter.output.postgresql.adapter.OrderPersistenceAdapter→dev.denissajnar.cqrs.query.core.domain.Pagedev.denissajnar.cqrs.query.adapter.output.postgresql.adapter.OrderPersistenceAdapter→dev.denissajnar.cqrs.query.core.domain.Pagination
- Direction
- query.adapter.output.postgresql.adapter uses query.core.domain, so a change to query.core.domain can break query.adapter.output.postgresql.adapter, while a change to query.adapter.output.postgresql.adapter can't break query.core.domain.
- Position
- Below the diagonal: query.adapter.output.postgresql.adapter uses a module listed above it, which is the healthy direction.
40→24 query.adapter.output.postgresql.adapter uses query.core.output.port✕
- Connections
- 5 pairs of types, where a type in query.adapter.output.postgresql.adapter uses a type in query.core.output.port.
- The types involved
dev.denissajnar.cqrs.query.adapter.output.postgresql.adapter.InboxPayloadCodec→dev.denissajnar.cqrs.query.core.output.port.EventPayloadCodecPortdev.denissajnar.cqrs.query.adapter.output.postgresql.adapter.InboxPersistenceAdapter→dev.denissajnar.cqrs.query.core.output.port.InboxClaimsdev.denissajnar.cqrs.query.adapter.output.postgresql.adapter.InboxPersistenceAdapter→dev.denissajnar.cqrs.query.core.output.port.InboxQueriesdev.denissajnar.cqrs.query.adapter.output.postgresql.adapter.InboxPersistenceAdapter→dev.denissajnar.cqrs.query.core.output.port.InboxWriterdev.denissajnar.cqrs.query.adapter.output.postgresql.adapter.OrderPersistenceAdapter→dev.denissajnar.cqrs.query.core.output.port.OrderRepositoryPort
- Direction
- query.adapter.output.postgresql.adapter uses query.core.output.port, so a change to query.core.output.port can break query.adapter.output.postgresql.adapter, while a change to query.adapter.output.postgresql.adapter can't break query.core.output.port.
- Position
- Below the diagonal: query.adapter.output.postgresql.adapter uses a module listed above it, which is the healthy direction.
40→37 query.adapter.output.postgresql.adapter uses query.adapter.output.postgresql.repository✕
- Connections
- 2 pairs of types, where a type in query.adapter.output.postgresql.adapter uses a type in query.adapter.output.postgresql.repository.
- The types involved
dev.denissajnar.cqrs.query.adapter.output.postgresql.adapter.InboxPersistenceAdapter→dev.denissajnar.cqrs.query.adapter.output.postgresql.repository.InboxEventRepositorydev.denissajnar.cqrs.query.adapter.output.postgresql.adapter.OrderPersistenceAdapter→dev.denissajnar.cqrs.query.adapter.output.postgresql.repository.OrderRepository
- Direction
- query.adapter.output.postgresql.adapter uses query.adapter.output.postgresql.repository, so a change to query.adapter.output.postgresql.repository can break query.adapter.output.postgresql.adapter, while a change to query.adapter.output.postgresql.adapter can't break query.adapter.output.postgresql.repository.
- Position
- Below the diagonal: query.adapter.output.postgresql.adapter 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 | 11 | High / Critical |
| A02:2025 — Security Misconfiguration | 4 | Medium |
Roadmap
Top priorities: Give each aggregate one way in that can refuse — a guarded constructor, value-object parameters that validate themselves, or a private constructor behind a factory that returns a failure; Adopt strongly-typed ids across the domain — finish the migration or document the boundary; primitive ids invite transposed-argument bugs; Resolve the 1 REDACTED finding(s) in Vulnerability-disclosure Policy — start with REDACTED.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Give each aggregate one way in that can refuse — a guarded constructor, value-object parameters that validate themselves, or a private constructor behind a factory that returns a failure. | +5.6 pts | Medium | Constructible invalid state |
| Adopt strongly-typed ids across the domain — finish the migration or document the boundary; primitive ids invite transposed-argument bugs. | +5.6 pts | Medium | Strongly-typed ids |
| Resolve the 1 REDACTED finding(s) in Vulnerability-disclosure Policy — start with REDACTED. | +1.9 pts | Low | Vulnerability-disclosure Policy |
| Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. | +1.1 pts | Low | Supply-chain Provenance & Signing |
| Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. | +1.1 pts | Low | Supply-chain Provenance & Signing |
| Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. | +1.1 pts | Low | Supply-chain Provenance & Signing |
| Resolve the 6 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (6). | +1.0 pts | Low | Dependency Vulnerabilities |
| Resolve the 2 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (2). | +0.3 pts | Low | Dependency Vulnerabilities |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 3.7 | Slop | Dependency Vulnerabilities: High CVE: REDACTED |
| REDACTED | 3.7 | Slop | Dependency Vulnerabilities: High CVE: REDACTED |
| REDACTED | 5.8 | Mixed | Dependency Vulnerabilities: High CVE: REDACTED |
| REDACTED | 6.3 | Mixed | IaC & Container Security: Medium IaC: REDACTED |
| REDACTED | 9.3 | Near-clean | Vulnerability-disclosure Policy: REDACTED |
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 70 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 — 70 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, 18 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 · checkov | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 · 3.2.533 | ✓ deterministic |
Run transparency — what happened this run
- D8 Code Coverage — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: test source is present (.kt) but the built-in coverage collector has no runner for this repository's ecosystem — so this suite was never executed by it. Not scored — this is a gap in the analyzer's language coverage, not a defect in the repo. To have real coverage read, produce a coverage report in a standard format (JaCoCo XML — the Gradle `jacocoTestReport` task) 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 (JaCoCo XML — the Gradle `jacocoTestReport` task) 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 (.kt) and this repository declares a JVM test suite (repository root, Gradle), 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.
- D12 Dependency Hygiene — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Not scored — 25 Maven/Gradle manifest(s) were read, stating a version for 16 dependency(ies) and leaving 1 to a parent or an imported BOM, but no build resolved the dependency graph, so the outdated signal was not established. NOT a finding that these dependencies are current or healthy.
- D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Single-maintainer repository — bus factor is not applicable (2 contributor(s) across 61 commit(s) sampled, automation and bot accounts excluded). One of them holds 98% of the history; the other 1 hold 2% each on average, below the 5% at which there is somebody to hand the work to. That is a single maintainer with drive-by contributors, not a team whose knowledge has concentrated — so the bus factor is not applicable and there is nothing here for the owner to act on.
- D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
- 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.
- D32 Data Compliance (PII/GDPR) — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `order-command-service/core/src/main/kotlin/dev/denissajnar/cqrs/command/core/domain/OrderId.kt`, `order-query-service/adapter/input/rabbitmq/src/main/kotlin/dev/denissajnar/cqrs/query/adapter/input/rabbitmq/listener/OrderEventListener.kt`, `order-query-service/app/src/main/kotlin/dev/denissajnar/cqrs/query/scheduling/InboxProjectionScheduler.kt`, `order-query-service/core/src/main/kotlin/dev/denissajnar/cqrs/query/core/domain/OrderId.kt` produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
- AX6 Interface segregation — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is computed over the public interfaces this run's compilations declare, and none was loaded, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- AXR1 Runtime accessibility — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via ToolchainServer (observability). the service did not build — `gradle --no-daemon -q classes` exited 1: olvers had internal failures: foojay (Connect timed out). * Try: > Learn more about toolchain auto-detection and auto-provisioning at https://docs.gradle.org/9.5.1/userguide/toolchains.html#sec:auto_…; runtime evidence skipped (launch chosen because observability/build.gradle.kts applies the Spring Boot plugin and declares spring-boot-starter-web).
- 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 two tells a construction that PRODUCES a measurement from one that merely passes it along, and this repository's frontend does not compute that fact. A measurement built independently in two places would not appear above.
- 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. Some of this repository's production types come from a frontend that does not bind comparison operands to the members they read, which arm one needs, and those types were not walked for this dimension. The counts above speak for the languages that declare it.
- GD1 Unfinished & placeholder code — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, F#, JavaScript/TypeScript, Dart, Ruby and Scala source only, and no C#, F#, JavaScript/TypeScript, Dart, Ruby or Scala was found, and this repository's Kotlin is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- IC1 Incompleteness & stubs — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, JavaScript/TypeScript, Java, Dart, Ruby and Scala source only, and no C#, JavaScript/TypeScript, Java, Dart, Ruby or Scala was found, and this repository's Kotlin is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- M4 Documentation accuracy — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
- S1 Web-Security Posture — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These web-security controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks web-security controls.
- X24 Document value interpolated into markup unescaped — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Scala, Ruby and Python source only, and no C# was loaded and no JavaScript/TypeScript, Java, Scala, Ruby or Python was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
- D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- D7 Architectural Integrity: Layering is checked against detected/declared rules — an architecture whose boundaries live in convention or in code review, not in a rule a scanner can read, is not enforced here.
- D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
- D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
- D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a 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.
- M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
- P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
- P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
Dimensions
D1 · Cyclomatic Complexity
0 method(s) exceeded the cyclomatic complexity threshold of 15.
D2 · Cognitive Complexity
0 method(s) exceeded the cognitive complexity threshold of 15.
D3 · God Classes
0 god class(es) detected.
D4 · Code Duplication
0 duplicated block group(s) detected.
D5 · Coupling
23 production modules (Gradle), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; edges a convention plugin adds from buildSrc or build-logic are not visible there; 2 module(s) off the main sequence, with abstractness counted on 14 of the 23 (the rest declare no modelled class or interface, export only macros, declare types in source no model reads, or have no source directory of their own).
What to do
- Resolve the 1 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (1 warning-level).
D6 · Cohesion (LCOM4)
0 of 11 classes have LCOM4 above 3.
D7 · Architectural Integrity
No mechanizable ADR was identified, so enforcement is not measured. Dependency cycles not checked (no project-reference graph; where this repository's language has an import-cycle lens, cycles are reported there).
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D14 · License Compliance
0 of 15 declared JVM dependency artifact(s) use a banned license. Licences were resolved from the POMs Maven Central publishes, over the coordinates this repository's 25 Maven/Gradle manifest(s) declare with a version resolvable from the manifest itself — the same declaration-site closure this analysis reads for dependency currency. The JVM has no lockfile a checkout is guaranteed to carry, so this is deliberately NOT the transitive closure. 1 further coordinate(s) are declared with no version at the declaration site — inherited from a parent POM, a BOM or an unresolved Gradle version reference — and are NOT graded: this verdict covers what the checkout pins, not the full transitive graph. A further 1 coordinate(s) are not published to Maven Central — another repository (Google's Maven hosts androidx), a SNAPSHOT, or a private artifact — so their licences are not readable from here and they are outside this verdict.
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window.
D17 · Explicit Debt
0 deducted task-comment markers across 5689 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.
D19 · Documentation Quality
1 of 1 documentation facets pass in full. 5 document(s) read across 1 unit(s).
D20 · ADR Quality
0 of 20 evaluated ADRs have a defect readable from the log itself (a missing or empty section, no title, a single option, consequences with no cost, no status, a missing enforcement field, a status the log contradicts, a dangling link, an unlinked second decision on one question, a date that is no calendar day). How well each record argues its case is not measured.
D26 · Project Cohesion
0 of 15 build units (Gradle) flagged as possibly oversized/incoherent.
D27 · Navigability
69 % of calls cross a namespace and 56 % go through an interface, but 100 % of collaborators are co-located — so following a call takes several hops. Baseline: small — navigation cost is tolerated.
What to do
- Resolve the 1 High interface indirection finding(s) in Navigability. — 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. semgrep hit a parse error in 1 file(s) — `gradlew` (line 74, line 178) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them.
D30 · Dependency Vulnerabilities
8 finding(s): 0 critical, 6 high, 2 medium, 0 low.
What to do
- Resolve the 6 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (6). — One of this dimension's main actionable groups (6 issue-level).
- Resolve the 2 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (2). — One of this dimension's main actionable groups (2 warning-level).
D31 · IaC & Container Security
3 finding(s): 0 critical, 0 high, 3 medium, 0 low.
What to do
- Resolve the 3 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (3). — One of this dimension's main actionable groups (3 warning-level).
D34 · Knowledge Freshness
Every significant source file has living knowledge — recently and meaningfully worked. Counted over 45 of the 134 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
D35 · Change Coupling
No strong hidden change-coupling between production files.
D36 · Supply-chain Provenance & Signing
0/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).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).
D37 · Vulnerability-disclosure Policy
A vulnerability-disclosure policy (REDACTED) is present but lists no reporting contact.
What to do
- Resolve the 1 REDACTED finding(s) in Vulnerability-disclosure Policy — start with REDACTED. — 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 2 platform declaration(s) and 16 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
Frontend & cross-cutting dimensions
AX1 · Captive dependencies
AX10 · Code composition
AX2 · Stateful singletons
AX3 · Project dependency cycles
AX4 · Dependency direction
DM1 · Aggregate boundaries
DM10 · One transaction, one aggregate
DM11 · Constructible invalid state
- `InboxEventEntity`'s public constructor takes `eventId`, `eventType`, `eventPayload` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `InboxEventEntity` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. — order-query-service/adapter/output/postgresql/src/main/kotlin/dev/denissajnar/cqrs/query/adapter/output/postgresql/entity/InboxEventEntity.kt:28
- `OrderEntity`'s public constructor takes `orderId` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `OrderEntity` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. — order-query-service/adapter/output/postgresql/src/main/kotlin/dev/denissajnar/cqrs/query/adapter/output/postgresql/entity/OrderEntity.kt:23
What to do
- Give each aggregate one way in that can refuse — a guarded constructor, value-object parameters that validate themselves, or a private constructor behind a factory that returns a failure.
DM12 · Ambient inputs in the domain
DM2 · Strongly-typed ids
- `OrderEvent.orderId` is a raw `String` — give it a strongly-typed id: a dedicated single-field type wrapping the `String`, in whatever form your language spells that. — shared/src/main/kotlin/dev/denissajnar/cqrs/shared/events/OrderEvent.kt:27
What to do
- Adopt strongly-typed ids across the domain — finish the migration or document the boundary; primitive ids invite transposed-argument bugs.
DM6 · Domain ↔ infrastructure boundary
DM7 · Repository granularity
DM9 · Scattered domain decisions
M1 · Documentation (README)
What to do
- Describe the projects a newcomer cannot place from the root README: 23 of 23 have no README of their own, in their folder or in their family's project (`architecture`, `build-logic`, `observability`, `order-command-service`, `order-query-service` and 18 more).
M2 · Architecture documentation
M3 · Folder & project structure
M4 · Documentation accuracy
P1 · CI/CD gates
P2 · Observability
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
- Add an approval/environment gate (required reviewers / protection rules) before production promotion.
P6 · Release Hygiene
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
X25 · Inert configuration knob
X26 · Unsynchronised callback handoff
X27 · Collection changed while being enumerated
X28 · Index access outside its own emptiness guard
X29 · Per-element action decided by a fixed element
X3 · Exception handling
X30 · Support guard that admits what it rejects
X4 · Structured logging
X5 · Nullable reference types
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 100% | Exemplary | Strongest area. |
| Architecture | 83% | Strong | Solid. |
| Maturity | 89% | Strong | Solid. |
| Readiness | 87% | Strong | Solid. |
| Security | 73% | Adequate — gated by D36 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Domain Modelling | 65% | Adequate — gated by DM2, DM11 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
Unscored — 1 check(s) recorded observations but carry no score
- X10 Duplicated predicate — 3 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 1 control(s) we could not find positive evidence for
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 58 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.
- AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX6 Interface segregation — not assessed — interface segregation is computed over a type surface that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- 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
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXR1 Runtime accessibility — the service did not build — `gradle --no-daemon -q classes` exited 1: olvers had internal failures: foojay (Connect timed out). * Try: > Learn more about toolchain auto-detection and auto-provisioning at https://docs.gradle.org/9.5.1/userguide/toolchains.html#sec:auto_…; runtime evidence skipped (launch chosen because observability/build.gradle.kts applies the Spring Boot plugin and declares spring-boot-starter-web) This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
- C1 Data Protection — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a Room, JPA or MongoDB entity, an Exposed or Ktorm table, or in a SQL CREATE TABLE or ALTER TABLE — and no database or data-store client (Room, Exposed, SQLDelight, Realm, JPA, JDBC, MongoDB, Firebase, …) imported either, so this repository keeps no data at rest for these controls to protect.
- 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 Room, JPA or MongoDB entity, an Exposed or Ktorm table, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store client (Room, Exposed, SQLDelight, Realm, JPA, JDBC, MongoDB, Firebase, …) 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 Room, JPA or MongoDB entity, an Exposed or Ktorm table, or in a SQL CREATE TABLE or ALTER TABLE — and no database or data-store client (Room, Exposed, SQLDelight, Realm, JPA, JDBC, MongoDB, Firebase, …) 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 Room, JPA or MongoDB entity, an Exposed or Ktorm table, or in a SQL CREATE TABLE or ALTER TABLE — and no database or data-store client (Room, Exposed, SQLDelight, Realm, JPA, JDBC, MongoDB, Firebase, …) imported either, so this repository keeps no personal data for a data subject to erase, export or consent over.
- D10 Test Quality — ~6398 lines of test source are present (.kt) 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 .kt suite was found but not re-run
- D12 Dependency Hygiene — Not scored — 25 Maven/Gradle manifest(s) were read, stating a version for 16 dependency(ies) and leaving 1 to a parent or an imported BOM, but no build resolved the dependency graph, so the outdated signal was not established. NOT a finding that these dependencies are current or healthy.
- D16 Bus Factor — single-maintainer 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.
- D21 Naming Consistency — Naming consistency is measured on C# and TypeScript only; Kotlin, Python 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. 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 .kt, .py, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D25 ADR Conformance — None of 19 binding record(s) states a rule in checkable form (a backticked element with a prohibition, or an `adr-rules` block), so conformance cannot be read from the code. Write the rule as an `adr-rules` block (`forbid:` a symbol, a package or a dependency) to make it checkable.
- D32 Data Compliance (PII/GDPR) — 4 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
- 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.
- D8 Code Coverage — Coverage not included — suite not readable by the collector
- D9 Test Distribution — Test source is present (.kt) but no test cases reached the test census for this repository — no test root we could resolve declared them, or the files we read declare no cases in a test framework we recognise — so its unit/integration/BDD/E2E split couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
- 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
- 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 none of the 3 signals this lens looks for
- ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- GD1 Unfinished & placeholder code — no source files were read — this check reads C#, F#, JavaScript/TypeScript, Dart, Ruby and Scala, and none was read for this repository's product. That is a limit of the analyzer, not a finding about your code.
- IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- P12 CI test-gate honesty — Reported, not scored — this card publishes what the CI gate does with the test inventory rather than grading it. The findings above are its output.
- P7 Outbound HTTP resilience — no outbound HTTP usage detected — no HTTP client call or construction in the JVM source (service entry point: order-query-service/app/src/main/kotlin/dev/denissajnar/cqrs/query/OrderQueryServiceApplication.kt:13 (@SpringBootApplication))
- P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (JaCoCo XML — the Gradle `jacocoTestReport` task) 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 — Not assessed: these web-security controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks web-security controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- X2 Cancellation propagation — no C# was loaded; this repository's Kotlin was read, and no request in it can be cancelled by a caller (Ktor, OkHttp's newCall or a URL stream, from a suspend function) — a Kotlin request outside a suspend function has no caller's cancellation to honour
- X24 Document value interpolated into markup unescaped — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- 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.
- 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 — 6 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
Serious — 8 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Constructible in an invalid state: InboxEventEntity order-query-service/adapter/output/postgresql/src/main/kotlin/dev/denissajnar/cqrs/query/adapter/output/postgresql/entity/InboxEventEntity.kt:28
- Constructible in an invalid state: OrderEntity order-query-service/adapter/output/postgresql/src/main/kotlin/dev/denissajnar/cqrs/query/adapter/output/postgresql/entity/OrderEntity.kt:23
- Off the main sequence: :observability
Minor — 9 finding(s)
- Duplicated predicate order-command-service/core/src/main/kotlin/dev/denissajnar/cqrs/command/core/domain/OrderCommands.kt:37
- Duplicated predicate build-logic/build.gradle.kts:53
- Duplicated predicate build-logic/src/main/kotlin/cqrs.kotlin-conventions.gradle.kts:93
- High interface indirection
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Primitive id on a domain type: OrderEvent.orderId shared/src/main/kotlin/dev/denissajnar/cqrs/shared/events/OrderEvent.kt:27
Minor — 1 finding(s)
- Off the main sequence: :shared
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-06245a3e91c34e34ae56187d7406c6db/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-06245a3e91c34e34ae56187d7406c6db/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 . | 8 | artifacts/raw/osv-scanner.json |
| D31 · IaC & Container Security | trivy | — | trivy config --format json --quiet . | 3 | artifacts/raw/trivy-config.json |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. semgrep could not parse 4 file(s) — `order-command-service/core/src/main/kotlin/dev/denissajnar/cqrs/command/core/domain/OrderId.kt`, `order-query-service/adapter/input/rabbitmq/src/main/kotlin/dev/denissajnar/cqrs/query/adapter/input/rabbitmq/listener/OrderEventListener.kt`, `order-query-service/app/src/main/kotlin/dev/denissajnar/cqrs/query/scheduling/InboxProjectionScheduler.kt`, `order-query-service/core/src/main/kotlin/dev/denissajnar/cqrs/query/core/domain/OrderId.kt` — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real. | 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 . | 0 | artifacts/raw/osv-scanner.json |