Executive summary
mrh-jishan/bookstore-cqrs-example falls short of our standard for production because we found no working pipeline that builds or tests changes to the code and no automated security scanning of the code, its secrets or its dependencies. It scores 41 out of 100 and is rated Weak, and one of its three critical findings is a security problem in the packages it uses.
Production Readiness, at 33, is the weakest lens and counts most in the score. The best first step is recording design decisions, worth about 6 points. Moving the pipeline to a build service that still runs would lift Production Readiness itself, worth about 4 points. Raising Production Readiness to 70 would lift the score to about 47.
One known security hole in a package the code depends on can be used by attackers. Updating the vulnerable packages would close this risk. The two pages that don't say their language need their language set.
The product code is 2,155 lines, about €3,300 to rebuild.
If Production Readiness rose from 33 to 70, the lowest score rated Strong, the score would rise from 41 to about 47.
New since the last survey: 1 finding
- Dependency Vulnerabilities · REDACTED
Fixed since the last survey: 3 findings
- Boundary Type-Coupling · Cross-context type AggregateRoot (domain → ordercontext) order-context-parent/order-application/src/main/java/se/citerus/cqrs/bookstore/ordercontext/application/infrastructure/InMemoryDomainEventStore.java
- Boundary Type-Coupling · Cross-context type AggregateRoot (domain → ordercontext) order-context-parent/order-application/src/main/java/se/citerus/cqrs/bookstore/ordercontext/application/infrastructure/SimpleFileBasedEventStore.java
- Dependency Vulnerabilities · Medium CVE: [GHSA redacted] REDACTED
Rebuild cost: about €3,300 · Estimate
| Cost to rebuild | €1,100 to €5,500, for 18 to 58 hours of work, under 0.1 person-years for one engineer |
|---|---|
| Difficulty of the problem | High, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.7 at a score of 41. 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: 2,155 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 order-context-parent.order-application.src.main.resources.assets | 2 se.citerus.cqrs.bookstore | 3 se.citerus.cqrs.bookstore.command | 4 se.citerus.cqrs.bookstore.ordercontext.application | 5 se.citerus.cqrs.bookstore.ordercontext.client.productcatalog | 6 se.citerus.cqrs.bookstore.productcatalog.application | 7 se.citerus.cqrs.bookstore.shopping.application | 8 shopping-context.src.main.resources.assets | 9 se.citerus.cqrs.bookstore.event | 10 se.citerus.cqrs.bookstore.ordercontext.api | 11 se.citerus.cqrs.bookstore.ordercontext.order | 12 se.citerus.cqrs.bookstore.ordercontext.publishercontract | 13 se.citerus.cqrs.bookstore.shopping.client.productcatalog | 14 se.citerus.cqrs.bookstore.domain | 15 se.citerus.cqrs.bookstore.ordercontext.application.task | 16 se.citerus.cqrs.bookstore.ordercontext.order.event | 17 se.citerus.cqrs.bookstore.ordercontext.publishercontract.event | 18 se.citerus.cqrs.bookstore.saga | 19 se.citerus.cqrs.bookstore.ordercontext.application.infrastructure | 20 se.citerus.cqrs.bookstore.ordercontext.order.domain | 21 se.citerus.cqrs.bookstore.ordercontext.publishercontract.command | 22 se.citerus.cqrs.bookstore.ordercontext.publishercontract.domain | 23 se.citerus.cqrs.bookstore.ordercontext.query.sales | 24 se.citerus.cqrs.bookstore.productcatalog.domain | 25 se.citerus.cqrs.bookstore.shopping.domain | 26 se.citerus.cqrs.bookstore.ordercontext.order.command | 27 se.citerus.cqrs.bookstore.ordercontext.query | 28 se.citerus.cqrs.bookstore.productcatalog.api | 29 se.citerus.cqrs.bookstore.productcatalog.infrastructure | 30 se.citerus.cqrs.bookstore.shopping.api | 31 se.citerus.cqrs.bookstore.shopping.infrastructure | 32 se.citerus.cqrs.bookstore.ordercontext.query.orderlist | 33 se.citerus.cqrs.bookstore.ordercontext.saga | 34 se.citerus.cqrs.bookstore.productcatalog.resource | 35 se.citerus.cqrs.bookstore.shopping.resource | 36 se.citerus.cqrs.bookstore.ordercontext.infrastructure | 37 se.citerus.cqrs.bookstore.ordercontext.resource |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 order-context-parent.order-application.src.main.resources.assets | |||||||||||||||||||||||||||||||||||||
| 2 se.citerus.cqrs.bookstore | |||||||||||||||||||||||||||||||||||||
| 3 se.citerus.cqrs.bookstore.command | |||||||||||||||||||||||||||||||||||||
| 4 se.citerus.cqrs.bookstore.ordercontext.application | |||||||||||||||||||||||||||||||||||||
| 5 se.citerus.cqrs.bookstore.ordercontext.client.productcatalog | |||||||||||||||||||||||||||||||||||||
| 6 se.citerus.cqrs.bookstore.productcatalog.application | |||||||||||||||||||||||||||||||||||||
| 7 se.citerus.cqrs.bookstore.shopping.application | |||||||||||||||||||||||||||||||||||||
| 8 shopping-context.src.main.resources.assets | |||||||||||||||||||||||||||||||||||||
| 9 se.citerus.cqrs.bookstore.event | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 10 se.citerus.cqrs.bookstore.ordercontext.api | 3 | ||||||||||||||||||||||||||||||||||||
| 11 se.citerus.cqrs.bookstore.ordercontext.order | 5 | ||||||||||||||||||||||||||||||||||||
| 12 se.citerus.cqrs.bookstore.ordercontext.publishercontract | 1 | ||||||||||||||||||||||||||||||||||||
| 13 se.citerus.cqrs.bookstore.shopping.client.productcatalog | 2 | ||||||||||||||||||||||||||||||||||||
| 14 se.citerus.cqrs.bookstore.domain | 1 | ||||||||||||||||||||||||||||||||||||
| 15 se.citerus.cqrs.bookstore.ordercontext.application.task | 2 | ||||||||||||||||||||||||||||||||||||
| 16 se.citerus.cqrs.bookstore.ordercontext.order.event | 2 | 4 | |||||||||||||||||||||||||||||||||||
| 17 se.citerus.cqrs.bookstore.ordercontext.publishercontract.event | 2 | 1 | 2 | ||||||||||||||||||||||||||||||||||
| 18 se.citerus.cqrs.bookstore.saga | 1 | ||||||||||||||||||||||||||||||||||||
| 19 se.citerus.cqrs.bookstore.ordercontext.application.infrastructure | 2 | 2 | 8 | 3 | |||||||||||||||||||||||||||||||||
| 20 se.citerus.cqrs.bookstore.ordercontext.order.domain | 5 | 3 | 2 | ||||||||||||||||||||||||||||||||||
| 21 se.citerus.cqrs.bookstore.ordercontext.publishercontract.command | 3 | 1 | 1 | 3 | 1 | ||||||||||||||||||||||||||||||||
| 22 se.citerus.cqrs.bookstore.ordercontext.publishercontract.domain | 1 | 1 | 3 | 2 | |||||||||||||||||||||||||||||||||
| 23 se.citerus.cqrs.bookstore.ordercontext.query.sales | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 24 se.citerus.cqrs.bookstore.productcatalog.domain | 2 | ||||||||||||||||||||||||||||||||||||
| 25 se.citerus.cqrs.bookstore.shopping.domain | 3 | ||||||||||||||||||||||||||||||||||||
| 26 se.citerus.cqrs.bookstore.ordercontext.order.command | 3 | 3 | 2 | 1 | 4 | ||||||||||||||||||||||||||||||||
| 27 se.citerus.cqrs.bookstore.ordercontext.query | 1 | 2 | 1 | 1 | 2 | ||||||||||||||||||||||||||||||||
| 28 se.citerus.cqrs.bookstore.productcatalog.api | 2 | 2 | |||||||||||||||||||||||||||||||||||
| 29 se.citerus.cqrs.bookstore.productcatalog.infrastructure | 3 | ||||||||||||||||||||||||||||||||||||
| 30 se.citerus.cqrs.bookstore.shopping.api | 4 | 2 | |||||||||||||||||||||||||||||||||||
| 31 se.citerus.cqrs.bookstore.shopping.infrastructure | 2 | ||||||||||||||||||||||||||||||||||||
| 32 se.citerus.cqrs.bookstore.ordercontext.query.orderlist | 1 | 5 | 2 | 1 | |||||||||||||||||||||||||||||||||
| 33 se.citerus.cqrs.bookstore.ordercontext.saga | 1 | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||
| 34 se.citerus.cqrs.bookstore.productcatalog.resource | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 35 se.citerus.cqrs.bookstore.shopping.resource | 2 | 1 | 3 | ||||||||||||||||||||||||||||||||||
| 36 se.citerus.cqrs.bookstore.ordercontext.infrastructure | 1 | 3 | |||||||||||||||||||||||||||||||||||
| 37 se.citerus.cqrs.bookstore.ordercontext.resource | 2 | 1 | 3 | 1 | 1 | 1 | 1 |
9→2 se.citerus.cqrs.bookstore.event uses se.citerus.cqrs.bookstore✕
- Connections
- 1 pair of types, where a type in se.citerus.cqrs.bookstore.event uses a type in se.citerus.cqrs.bookstore.
- The types involved
se.citerus.cqrs.bookstore.event.DomainEventStore→se.citerus.cqrs.bookstore.GenericId
- Direction
- se.citerus.cqrs.bookstore.event uses se.citerus.cqrs.bookstore, so a change to se.citerus.cqrs.bookstore can break se.citerus.cqrs.bookstore.event, while a change to se.citerus.cqrs.bookstore.event can't break se.citerus.cqrs.bookstore.
- Position
- Below the diagonal: se.citerus.cqrs.bookstore.event uses a module listed above it, which is the healthy direction.
9→14 se.citerus.cqrs.bookstore.event uses se.citerus.cqrs.bookstore.domain part of a loop✕
- Connections
- 1 pair of types, where a type in se.citerus.cqrs.bookstore.event uses a type in se.citerus.cqrs.bookstore.domain.
- The types involved
se.citerus.cqrs.bookstore.event.DomainEventStore→se.citerus.cqrs.bookstore.domain.AggregateRoot
- Direction
- se.citerus.cqrs.bookstore.event uses se.citerus.cqrs.bookstore.domain, so a change to se.citerus.cqrs.bookstore.domain can break se.citerus.cqrs.bookstore.event, while a change to se.citerus.cqrs.bookstore.event can't break se.citerus.cqrs.bookstore.domain.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
10→2 se.citerus.cqrs.bookstore.ordercontext.api uses se.citerus.cqrs.bookstore✕
- Connections
- 3 pairs of types, where a type in se.citerus.cqrs.bookstore.ordercontext.api uses a type in se.citerus.cqrs.bookstore.
- The types involved
se.citerus.cqrs.bookstore.ordercontext.api.ActivateOrderRequest→se.citerus.cqrs.bookstore.TransportObjectse.citerus.cqrs.bookstore.ordercontext.api.PlaceOrderRequest→se.citerus.cqrs.bookstore.TransportObjectse.citerus.cqrs.bookstore.ordercontext.api.RegisterPublisherContractRequest→se.citerus.cqrs.bookstore.TransportObject
- Direction
- se.citerus.cqrs.bookstore.ordercontext.api uses se.citerus.cqrs.bookstore, so a change to se.citerus.cqrs.bookstore can break se.citerus.cqrs.bookstore.ordercontext.api, while a change to se.citerus.cqrs.bookstore.ordercontext.api can't break se.citerus.cqrs.bookstore.
- Position
- Below the diagonal: se.citerus.cqrs.bookstore.ordercontext.api uses a module listed above it, which is the healthy direction.
11→2 se.citerus.cqrs.bookstore.ordercontext.order uses se.citerus.cqrs.bookstore✕
- Connections
- 5 pairs of types, where a type in se.citerus.cqrs.bookstore.ordercontext.order uses a type in se.citerus.cqrs.bookstore.
- The types involved
se.citerus.cqrs.bookstore.ordercontext.order.BookId→se.citerus.cqrs.bookstore.GenericIdse.citerus.cqrs.bookstore.ordercontext.order.CustomerInformation→se.citerus.cqrs.bookstore.TransportObjectse.citerus.cqrs.bookstore.ordercontext.order.OrderId→se.citerus.cqrs.bookstore.GenericIdse.citerus.cqrs.bookstore.ordercontext.order.OrderLine→se.citerus.cqrs.bookstore.TransportObjectse.citerus.cqrs.bookstore.ordercontext.order.ProductId→se.citerus.cqrs.bookstore.GenericId
- Direction
- se.citerus.cqrs.bookstore.ordercontext.order uses se.citerus.cqrs.bookstore, so a change to se.citerus.cqrs.bookstore can break se.citerus.cqrs.bookstore.ordercontext.order, while a change to se.citerus.cqrs.bookstore.ordercontext.order can't break se.citerus.cqrs.bookstore.
- Position
- Below the diagonal: se.citerus.cqrs.bookstore.ordercontext.order uses a module listed above it, which is the healthy direction.
12→2 se.citerus.cqrs.bookstore.ordercontext.publishercontract uses se.citerus.cqrs.bookstore✕
- Connections
- 1 pair of types, where a type in se.citerus.cqrs.bookstore.ordercontext.publishercontract uses a type in se.citerus.cqrs.bookstore.
- The types involved
se.citerus.cqrs.bookstore.ordercontext.publishercontract.PublisherContractId→se.citerus.cqrs.bookstore.GenericId
- Direction
- se.citerus.cqrs.bookstore.ordercontext.publishercontract uses se.citerus.cqrs.bookstore, so a change to se.citerus.cqrs.bookstore can break se.citerus.cqrs.bookstore.ordercontext.publishercontract, while a change to se.citerus.cqrs.bookstore.ordercontext.publishercontract can't break se.citerus.cqrs.bookstore.
- Position
- Below the diagonal: se.citerus.cqrs.bookstore.ordercontext.publishercontract uses a module listed above it, which is the healthy direction.
13→2 se.citerus.cqrs.bookstore.shopping.client.productcatalog uses se.citerus.cqrs.bookstore✕
- Connections
- 2 pairs of types, where a type in se.citerus.cqrs.bookstore.shopping.client.productcatalog uses a type in se.citerus.cqrs.bookstore.
- The types involved
se.citerus.cqrs.bookstore.shopping.client.productcatalog.BookDto→se.citerus.cqrs.bookstore.TransportObjectse.citerus.cqrs.bookstore.shopping.client.productcatalog.ProductDto→se.citerus.cqrs.bookstore.TransportObject
- Direction
- se.citerus.cqrs.bookstore.shopping.client.productcatalog uses se.citerus.cqrs.bookstore, so a change to se.citerus.cqrs.bookstore can break se.citerus.cqrs.bookstore.shopping.client.productcatalog, while a change to se.citerus.cqrs.bookstore.shopping.client.productcatalog can't break se.citerus.cqrs.bookstore.
- Position
- Below the diagonal: se.citerus.cqrs.bookstore.shopping.client.productcatalog uses a module listed above it, which is the healthy direction.
14→9 se.citerus.cqrs.bookstore.domain uses se.citerus.cqrs.bookstore.event✕
- Connections
- 1 pair of types, where a type in se.citerus.cqrs.bookstore.domain uses a type in se.citerus.cqrs.bookstore.event.
- The types involved
se.citerus.cqrs.bookstore.domain.AggregateRoot→se.citerus.cqrs.bookstore.event.DomainEvent
- Direction
- se.citerus.cqrs.bookstore.domain uses se.citerus.cqrs.bookstore.event, so a change to se.citerus.cqrs.bookstore.event can break se.citerus.cqrs.bookstore.domain, while a change to se.citerus.cqrs.bookstore.domain can't break se.citerus.cqrs.bookstore.event.
- Position
- Below the diagonal: se.citerus.cqrs.bookstore.domain uses a module listed above it, which is the healthy direction.
15→9 se.citerus.cqrs.bookstore.ordercontext.application.task uses se.citerus.cqrs.bookstore.event✕
- Connections
- 2 pairs of types, where a type in se.citerus.cqrs.bookstore.ordercontext.application.task uses a type in se.citerus.cqrs.bookstore.event.
- The types involved
se.citerus.cqrs.bookstore.ordercontext.application.task.ReplayEventsTask→se.citerus.cqrs.bookstore.event.DomainEventBusse.citerus.cqrs.bookstore.ordercontext.application.task.ReplayEventsTask→se.citerus.cqrs.bookstore.event.DomainEventStore
- Direction
- se.citerus.cqrs.bookstore.ordercontext.application.task uses se.citerus.cqrs.bookstore.event, so a change to se.citerus.cqrs.bookstore.event can break se.citerus.cqrs.bookstore.ordercontext.application.task, while a change to se.citerus.cqrs.bookstore.ordercontext.application.task can't break se.citerus.cqrs.bookstore.event.
- Position
- Below the diagonal: se.citerus.cqrs.bookstore.ordercontext.application.task uses a module listed above it, which is the healthy direction.
16→9 se.citerus.cqrs.bookstore.ordercontext.order.event uses se.citerus.cqrs.bookstore.event✕
- Connections
- 2 pairs of types, where a type in se.citerus.cqrs.bookstore.ordercontext.order.event uses a type in se.citerus.cqrs.bookstore.event.
- The types involved
se.citerus.cqrs.bookstore.ordercontext.order.event.OrderActivatedEvent→se.citerus.cqrs.bookstore.event.DomainEventse.citerus.cqrs.bookstore.ordercontext.order.event.OrderPlacedEvent→se.citerus.cqrs.bookstore.event.DomainEvent
- Direction
- se.citerus.cqrs.bookstore.ordercontext.order.event uses se.citerus.cqrs.bookstore.event, so a change to se.citerus.cqrs.bookstore.event can break se.citerus.cqrs.bookstore.ordercontext.order.event, while a change to se.citerus.cqrs.bookstore.ordercontext.order.event can't break se.citerus.cqrs.bookstore.event.
- Position
- Below the diagonal: se.citerus.cqrs.bookstore.ordercontext.order.event uses a module listed above it, which is the healthy direction.
16→11 se.citerus.cqrs.bookstore.ordercontext.order.event uses se.citerus.cqrs.bookstore.ordercontext.order✕
- Connections
- 4 pairs of types, where a type in se.citerus.cqrs.bookstore.ordercontext.order.event uses a type in se.citerus.cqrs.bookstore.ordercontext.order.
- The types involved
se.citerus.cqrs.bookstore.ordercontext.order.event.OrderActivatedEvent→se.citerus.cqrs.bookstore.ordercontext.order.OrderIdse.citerus.cqrs.bookstore.ordercontext.order.event.OrderPlacedEvent→se.citerus.cqrs.bookstore.ordercontext.order.CustomerInformationse.citerus.cqrs.bookstore.ordercontext.order.event.OrderPlacedEvent→se.citerus.cqrs.bookstore.ordercontext.order.OrderIdse.citerus.cqrs.bookstore.ordercontext.order.event.OrderPlacedEvent→se.citerus.cqrs.bookstore.ordercontext.order.OrderLine
- Direction
- se.citerus.cqrs.bookstore.ordercontext.order.event uses se.citerus.cqrs.bookstore.ordercontext.order, so a change to se.citerus.cqrs.bookstore.ordercontext.order can break se.citerus.cqrs.bookstore.ordercontext.order.event, while a change to se.citerus.cqrs.bookstore.ordercontext.order.event can't break se.citerus.cqrs.bookstore.ordercontext.order.
- Position
- Below the diagonal: se.citerus.cqrs.bookstore.ordercontext.order.event uses a module listed above it, which is the healthy direction.
17→9 se.citerus.cqrs.bookstore.ordercontext.publishercontract.event uses se.citerus.cqrs.bookstore.event✕
- Connections
- 2 pairs of types, where a type in se.citerus.cqrs.bookstore.ordercontext.publishercontract.event uses a type in se.citerus.cqrs.bookstore.event.
- The types involved
se.citerus.cqrs.bookstore.ordercontext.publishercontract.event.PublisherContractRegisteredEvent→se.citerus.cqrs.bookstore.event.DomainEventse.citerus.cqrs.bookstore.ordercontext.publishercontract.event.PurchaseRegisteredEvent→se.citerus.cqrs.bookstore.event.DomainEvent
- Direction
- se.citerus.cqrs.bookstore.ordercontext.publishercontract.event uses se.citerus.cqrs.bookstore.event, so a change to se.citerus.cqrs.bookstore.event can break se.citerus.cqrs.bookstore.ordercontext.publishercontract.event, while a change to se.citerus.cqrs.bookstore.ordercontext.publishercontract.event can't break se.citerus.cqrs.bookstore.event.
- Position
- Below the diagonal: se.citerus.cqrs.bookstore.ordercontext.publishercontract.event uses a module listed above it, which is the healthy direction.
17→11 se.citerus.cqrs.bookstore.ordercontext.publishercontract.event uses se.citerus.cqrs.bookstore.ordercontext.order✕
- Connections
- 1 pair of types, where a type in se.citerus.cqrs.bookstore.ordercontext.publishercontract.event uses a type in se.citerus.cqrs.bookstore.ordercontext.order.
- The types involved
se.citerus.cqrs.bookstore.ordercontext.publishercontract.event.PurchaseRegisteredEvent→se.citerus.cqrs.bookstore.ordercontext.order.ProductId
- Direction
- se.citerus.cqrs.bookstore.ordercontext.publishercontract.event uses se.citerus.cqrs.bookstore.ordercontext.order, so a change to se.citerus.cqrs.bookstore.ordercontext.order can break se.citerus.cqrs.bookstore.ordercontext.publishercontract.event, while a change to se.citerus.cqrs.bookstore.ordercontext.publishercontract.event can't break se.citerus.cqrs.bookstore.ordercontext.order.
- Position
- Below the diagonal: se.citerus.cqrs.bookstore.ordercontext.publishercontract.event uses a module listed above it, which is the healthy direction.
17→12 se.citerus.cqrs.bookstore.ordercontext.publishercontract.event uses se.citerus.cqrs.bookstore.ordercontext.publishercontract✕
- Connections
- 2 pairs of types, where a type in se.citerus.cqrs.bookstore.ordercontext.publishercontract.event uses a type in se.citerus.cqrs.bookstore.ordercontext.publishercontract.
- The types involved
se.citerus.cqrs.bookstore.ordercontext.publishercontract.event.PublisherContractRegisteredEvent→se.citerus.cqrs.bookstore.ordercontext.publishercontract.PublisherContractIdse.citerus.cqrs.bookstore.ordercontext.publishercontract.event.PurchaseRegisteredEvent→se.citerus.cqrs.bookstore.ordercontext.publishercontract.PublisherContractId
- Direction
- se.citerus.cqrs.bookstore.ordercontext.publishercontract.event uses se.citerus.cqrs.bookstore.ordercontext.publishercontract, so a change to se.citerus.cqrs.bookstore.ordercontext.publishercontract can break se.citerus.cqrs.bookstore.ordercontext.publishercontract.event, while a change to se.citerus.cqrs.bookstore.ordercontext.publishercontract.event can't break se.citerus.cqrs.bookstore.ordercontext.publishercontract.
- Position
- Below the diagonal: se.citerus.cqrs.bookstore.ordercontext.publishercontract.event uses a module listed above it, which is the healthy direction.
18→9 se.citerus.cqrs.bookstore.saga uses se.citerus.cqrs.bookstore.event✕
- Connections
- 1 pair of types, where a type in se.citerus.cqrs.bookstore.saga uses a type in se.citerus.cqrs.bookstore.event.
- The types involved
se.citerus.cqrs.bookstore.saga.Saga→se.citerus.cqrs.bookstore.event.DomainEventListener
- Direction
- se.citerus.cqrs.bookstore.saga uses se.citerus.cqrs.bookstore.event, so a change to se.citerus.cqrs.bookstore.event can break se.citerus.cqrs.bookstore.saga, while a change to se.citerus.cqrs.bookstore.saga can't break se.citerus.cqrs.bookstore.event.
- Position
- Below the diagonal: se.citerus.cqrs.bookstore.saga uses a module listed above it, which is the healthy direction.
19→2 se.citerus.cqrs.bookstore.ordercontext.application.infrastructure uses se.citerus.cqrs.bookstore✕
- Connections
- 2 pairs of types, where a type in se.citerus.cqrs.bookstore.ordercontext.application.infrastructure uses a type in se.citerus.cqrs.bookstore.
- The types involved
se.citerus.cqrs.bookstore.ordercontext.application.infrastructure.InMemoryDomainEventStore→se.citerus.cqrs.bookstore.GenericIdse.citerus.cqrs.bookstore.ordercontext.application.infrastructure.SimpleFileBasedEventStore→se.citerus.cqrs.bookstore.GenericId
- Direction
- se.citerus.cqrs.bookstore.ordercontext.application.infrastructure uses se.citerus.cqrs.bookstore, so a change to se.citerus.cqrs.bookstore can break se.citerus.cqrs.bookstore.ordercontext.application.infrastructure, while a change to se.citerus.cqrs.bookstore.ordercontext.application.infrastructure can't break se.citerus.cqrs.bookstore.
- Position
- Below the diagonal: se.citerus.cqrs.bookstore.ordercontext.application.infrastructure uses a module listed above it, which is the healthy direction.
19→3 se.citerus.cqrs.bookstore.ordercontext.application.infrastructure uses se.citerus.cqrs.bookstore.command✕
- Connections
- 2 pairs of types, where a type in se.citerus.cqrs.bookstore.ordercontext.application.infrastructure uses a type in se.citerus.cqrs.bookstore.command.
- The types involved
se.citerus.cqrs.bookstore.ordercontext.application.infrastructure.GuavaCommandBus→se.citerus.cqrs.bookstore.command.Commandse.citerus.cqrs.bookstore.ordercontext.application.infrastructure.GuavaCommandBus→se.citerus.cqrs.bookstore.command.CommandBus
- Direction
- se.citerus.cqrs.bookstore.ordercontext.application.infrastructure uses se.citerus.cqrs.bookstore.command, so a change to se.citerus.cqrs.bookstore.command can break se.citerus.cqrs.bookstore.ordercontext.application.infrastructure, while a change to se.citerus.cqrs.bookstore.ordercontext.application.infrastructure can't break se.citerus.cqrs.bookstore.command.
- Position
- Below the diagonal: se.citerus.cqrs.bookstore.ordercontext.application.infrastructure uses a module listed above it, which is the healthy direction.
19→9 se.citerus.cqrs.bookstore.ordercontext.application.infrastructure uses se.citerus.cqrs.bookstore.event✕
- Connections
- 8 pairs of types, where a type in se.citerus.cqrs.bookstore.ordercontext.application.infrastructure uses a type in se.citerus.cqrs.bookstore.event.
- The types involved
se.citerus.cqrs.bookstore.ordercontext.application.infrastructure.DefaultRepository→se.citerus.cqrs.bookstore.event.DomainEventBusse.citerus.cqrs.bookstore.ordercontext.application.infrastructure.DefaultRepository→se.citerus.cqrs.bookstore.event.DomainEventStorese.citerus.cqrs.bookstore.ordercontext.application.infrastructure.GuavaDomainEventBus→se.citerus.cqrs.bookstore.event.DomainEventse.citerus.cqrs.bookstore.ordercontext.application.infrastructure.GuavaDomainEventBus→se.citerus.cqrs.bookstore.event.DomainEventBusse.citerus.cqrs.bookstore.ordercontext.application.infrastructure.InMemoryDomainEventStore→se.citerus.cqrs.bookstore.event.DomainEventse.citerus.cqrs.bookstore.ordercontext.application.infrastructure.InMemoryDomainEventStore→se.citerus.cqrs.bookstore.event.DomainEventStorese.citerus.cqrs.bookstore.ordercontext.application.infrastructure.SimpleFileBasedEventStore→se.citerus.cqrs.bookstore.event.DomainEventse.citerus.cqrs.bookstore.ordercontext.application.infrastructure.SimpleFileBasedEventStore→se.citerus.cqrs.bookstore.event.DomainEventStore
- Direction
- se.citerus.cqrs.bookstore.ordercontext.application.infrastructure uses se.citerus.cqrs.bookstore.event, so a change to se.citerus.cqrs.bookstore.event can break se.citerus.cqrs.bookstore.ordercontext.application.infrastructure, while a change to se.citerus.cqrs.bookstore.ordercontext.application.infrastructure can't break se.citerus.cqrs.bookstore.event.
- Position
- Below the diagonal: se.citerus.cqrs.bookstore.ordercontext.application.infrastructure uses a module listed above it, which is the healthy direction.
19→14 se.citerus.cqrs.bookstore.ordercontext.application.infrastructure uses se.citerus.cqrs.bookstore.domain✕
- Connections
- 3 pairs of types, where a type in se.citerus.cqrs.bookstore.ordercontext.application.infrastructure uses a type in se.citerus.cqrs.bookstore.domain.
- The types involved
se.citerus.cqrs.bookstore.ordercontext.application.infrastructure.DefaultRepository→se.citerus.cqrs.bookstore.domain.Repositoryse.citerus.cqrs.bookstore.ordercontext.application.infrastructure.InMemoryDomainEventStore→se.citerus.cqrs.bookstore.domain.AggregateRootse.citerus.cqrs.bookstore.ordercontext.application.infrastructure.SimpleFileBasedEventStore→se.citerus.cqrs.bookstore.domain.AggregateRoot
- Direction
- se.citerus.cqrs.bookstore.ordercontext.application.infrastructure uses se.citerus.cqrs.bookstore.domain, so a change to se.citerus.cqrs.bookstore.domain can break se.citerus.cqrs.bookstore.ordercontext.application.infrastructure, while a change to se.citerus.cqrs.bookstore.ordercontext.application.infrastructure can't break se.citerus.cqrs.bookstore.domain.
- Position
- Below the diagonal: se.citerus.cqrs.bookstore.ordercontext.application.infrastructure uses a module listed above it, which is the healthy direction.
20→11 se.citerus.cqrs.bookstore.ordercontext.order.domain uses se.citerus.cqrs.bookstore.ordercontext.order✕
- Connections
- 5 pairs of types, where a type in se.citerus.cqrs.bookstore.ordercontext.order.domain uses a type in se.citerus.cqrs.bookstore.ordercontext.order.
- The types involved
se.citerus.cqrs.bookstore.ordercontext.order.domain.Order→se.citerus.cqrs.bookstore.ordercontext.order.CustomerInformationse.citerus.cqrs.bookstore.ordercontext.order.domain.Order→se.citerus.cqrs.bookstore.ordercontext.order.OrderIdse.citerus.cqrs.bookstore.ordercontext.order.domain.Order→se.citerus.cqrs.bookstore.ordercontext.order.OrderLinese.citerus.cqrs.bookstore.ordercontext.order.domain.Order→se.citerus.cqrs.bookstore.ordercontext.order.OrderStatusse.citerus.cqrs.bookstore.ordercontext.order.domain.OrderLine→se.citerus.cqrs.bookstore.ordercontext.order.ProductId
- Direction
- se.citerus.cqrs.bookstore.ordercontext.order.domain uses se.citerus.cqrs.bookstore.ordercontext.order, so a change to se.citerus.cqrs.bookstore.ordercontext.order can break se.citerus.cqrs.bookstore.ordercontext.order.domain, while a change to se.citerus.cqrs.bookstore.ordercontext.order.domain can't break se.citerus.cqrs.bookstore.ordercontext.order.
- Position
- Below the diagonal: se.citerus.cqrs.bookstore.ordercontext.order.domain uses a module listed above it, which is the healthy direction.
20→14 se.citerus.cqrs.bookstore.ordercontext.order.domain uses se.citerus.cqrs.bookstore.domain✕
- Connections
- 3 pairs of types, where a type in se.citerus.cqrs.bookstore.ordercontext.order.domain uses a type in se.citerus.cqrs.bookstore.domain.
- The types involved
se.citerus.cqrs.bookstore.ordercontext.order.domain.CustomerInformation→se.citerus.cqrs.bookstore.domain.ValueObjectse.citerus.cqrs.bookstore.ordercontext.order.domain.Order→se.citerus.cqrs.bookstore.domain.AggregateRootse.citerus.cqrs.bookstore.ordercontext.order.domain.OrderLine→se.citerus.cqrs.bookstore.domain.ValueObject
- Direction
- se.citerus.cqrs.bookstore.ordercontext.order.domain uses se.citerus.cqrs.bookstore.domain, so a change to se.citerus.cqrs.bookstore.domain can break se.citerus.cqrs.bookstore.ordercontext.order.domain, while a change to se.citerus.cqrs.bookstore.ordercontext.order.domain can't break se.citerus.cqrs.bookstore.domain.
- Position
- Below the diagonal: se.citerus.cqrs.bookstore.ordercontext.order.domain uses a module listed above it, which is the healthy direction.
20→16 se.citerus.cqrs.bookstore.ordercontext.order.domain uses se.citerus.cqrs.bookstore.ordercontext.order.event✕
- Connections
- 2 pairs of types, where a type in se.citerus.cqrs.bookstore.ordercontext.order.domain uses a type in se.citerus.cqrs.bookstore.ordercontext.order.event.
- The types involved
se.citerus.cqrs.bookstore.ordercontext.order.domain.Order→se.citerus.cqrs.bookstore.ordercontext.order.event.OrderActivatedEventse.citerus.cqrs.bookstore.ordercontext.order.domain.Order→se.citerus.cqrs.bookstore.ordercontext.order.event.OrderPlacedEvent
- Direction
- se.citerus.cqrs.bookstore.ordercontext.order.domain uses se.citerus.cqrs.bookstore.ordercontext.order.event, so a change to se.citerus.cqrs.bookstore.ordercontext.order.event can break se.citerus.cqrs.bookstore.ordercontext.order.domain, while a change to se.citerus.cqrs.bookstore.ordercontext.order.domain can't break se.citerus.cqrs.bookstore.ordercontext.order.event.
- Position
- Below the diagonal: se.citerus.cqrs.bookstore.ordercontext.order.domain uses a module listed above it, which is the healthy direction.
21→3 se.citerus.cqrs.bookstore.ordercontext.publishercontract.command uses se.citerus.cqrs.bookstore.command✕
- Connections
- 3 pairs of types, where a type in se.citerus.cqrs.bookstore.ordercontext.publishercontract.command uses a type in se.citerus.cqrs.bookstore.command.
- The types involved
se.citerus.cqrs.bookstore.ordercontext.publishercontract.command.PublisherContractCommandHandler→se.citerus.cqrs.bookstore.command.CommandHandlerse.citerus.cqrs.bookstore.ordercontext.publishercontract.command.RegisterPublisherContractCommand→se.citerus.cqrs.bookstore.command.Commandse.citerus.cqrs.bookstore.ordercontext.publishercontract.command.RegisterPurchaseCommand→se.citerus.cqrs.bookstore.command.Command
- Direction
- se.citerus.cqrs.bookstore.ordercontext.publishercontract.command uses se.citerus.cqrs.bookstore.command, so a change to se.citerus.cqrs.bookstore.command can break se.citerus.cqrs.bookstore.ordercontext.publishercontract.command, while a change to se.citerus.cqrs.bookstore.ordercontext.publishercontract.command can't break se.citerus.cqrs.bookstore.command.
- Position
- Below the diagonal: se.citerus.cqrs.bookstore.ordercontext.publishercontract.command uses a module listed above it, which is the healthy direction.
21→10 se.citerus.cqrs.bookstore.ordercontext.publishercontract.command uses se.citerus.cqrs.bookstore.ordercontext.api✕
- Connections
- 1 pair of types, where a type in se.citerus.cqrs.bookstore.ordercontext.publishercontract.command uses a type in se.citerus.cqrs.bookstore.ordercontext.api.
- The types involved
se.citerus.cqrs.bookstore.ordercontext.publishercontract.command.CommandFactory→se.citerus.cqrs.bookstore.ordercontext.api.RegisterPublisherContractRequest
- Direction
- se.citerus.cqrs.bookstore.ordercontext.publishercontract.command uses se.citerus.cqrs.bookstore.ordercontext.api, so a change to se.citerus.cqrs.bookstore.ordercontext.api can break se.citerus.cqrs.bookstore.ordercontext.publishercontract.command, while a change to se.citerus.cqrs.bookstore.ordercontext.publishercontract.command can't break se.citerus.cqrs.bookstore.ordercontext.api.
- Position
- Below the diagonal: se.citerus.cqrs.bookstore.ordercontext.publishercontract.command uses a module listed above it, which is the healthy direction.
21→11 se.citerus.cqrs.bookstore.ordercontext.publishercontract.command uses se.citerus.cqrs.bookstore.ordercontext.order✕
- Connections
- 1 pair of types, where a type in se.citerus.cqrs.bookstore.ordercontext.publishercontract.command uses a type in se.citerus.cqrs.bookstore.ordercontext.order.
- The types involved
se.citerus.cqrs.bookstore.ordercontext.publishercontract.command.RegisterPurchaseCommand→se.citerus.cqrs.bookstore.ordercontext.order.ProductId
- Direction
- se.citerus.cqrs.bookstore.ordercontext.publishercontract.command uses se.citerus.cqrs.bookstore.ordercontext.order, so a change to se.citerus.cqrs.bookstore.ordercontext.order can break se.citerus.cqrs.bookstore.ordercontext.publishercontract.command, while a change to se.citerus.cqrs.bookstore.ordercontext.publishercontract.command can't break se.citerus.cqrs.bookstore.ordercontext.order.
- Position
- Below the diagonal: se.citerus.cqrs.bookstore.ordercontext.publishercontract.command uses a module listed above it, which is the healthy direction.
21→12 se.citerus.cqrs.bookstore.ordercontext.publishercontract.command uses se.citerus.cqrs.bookstore.ordercontext.publishercontract✕
- Connections
- 3 pairs of types, where a type in se.citerus.cqrs.bookstore.ordercontext.publishercontract.command uses a type in se.citerus.cqrs.bookstore.ordercontext.publishercontract.
- The types involved
se.citerus.cqrs.bookstore.ordercontext.publishercontract.command.CommandFactory→se.citerus.cqrs.bookstore.ordercontext.publishercontract.PublisherContractIdse.citerus.cqrs.bookstore.ordercontext.publishercontract.command.RegisterPublisherContractCommand→se.citerus.cqrs.bookstore.ordercontext.publishercontract.PublisherContractIdse.citerus.cqrs.bookstore.ordercontext.publishercontract.command.RegisterPurchaseCommand→se.citerus.cqrs.bookstore.ordercontext.publishercontract.PublisherContractId
- Direction
- se.citerus.cqrs.bookstore.ordercontext.publishercontract.command uses se.citerus.cqrs.bookstore.ordercontext.publishercontract, so a change to se.citerus.cqrs.bookstore.ordercontext.publishercontract can break se.citerus.cqrs.bookstore.ordercontext.publishercontract.command, while a change to se.citerus.cqrs.bookstore.ordercontext.publishercontract.command can't break se.citerus.cqrs.bookstore.ordercontext.publishercontract.
- Position
- Below the diagonal: se.citerus.cqrs.bookstore.ordercontext.publishercontract.command uses a module listed above it, which is the healthy direction.
21→14 se.citerus.cqrs.bookstore.ordercontext.publishercontract.command uses se.citerus.cqrs.bookstore.domain✕
- Connections
- 1 pair of types, where a type in se.citerus.cqrs.bookstore.ordercontext.publishercontract.command uses a type in se.citerus.cqrs.bookstore.domain.
- The types involved
se.citerus.cqrs.bookstore.ordercontext.publishercontract.command.PublisherContractCommandHandler→se.citerus.cqrs.bookstore.domain.Repository
- Direction
- se.citerus.cqrs.bookstore.ordercontext.publishercontract.command uses se.citerus.cqrs.bookstore.domain, so a change to se.citerus.cqrs.bookstore.domain can break se.citerus.cqrs.bookstore.ordercontext.publishercontract.command, while a change to se.citerus.cqrs.bookstore.ordercontext.publishercontract.command can't break se.citerus.cqrs.bookstore.domain.
- Position
- Below the diagonal: se.citerus.cqrs.bookstore.ordercontext.publishercontract.command uses a module listed above it, which is the healthy direction.
22→11 se.citerus.cqrs.bookstore.ordercontext.publishercontract.domain uses se.citerus.cqrs.bookstore.ordercontext.order✕
- Connections
- 1 pair of types, where a type in se.citerus.cqrs.bookstore.ordercontext.publishercontract.domain uses a type in se.citerus.cqrs.bookstore.ordercontext.order.
- The types involved
se.citerus.cqrs.bookstore.ordercontext.publishercontract.domain.PublisherContract→se.citerus.cqrs.bookstore.ordercontext.order.ProductId
- Direction
- se.citerus.cqrs.bookstore.ordercontext.publishercontract.domain uses se.citerus.cqrs.bookstore.ordercontext.order, so a change to se.citerus.cqrs.bookstore.ordercontext.order can break se.citerus.cqrs.bookstore.ordercontext.publishercontract.domain, while a change to se.citerus.cqrs.bookstore.ordercontext.publishercontract.domain can't break se.citerus.cqrs.bookstore.ordercontext.order.
- Position
- Below the diagonal: se.citerus.cqrs.bookstore.ordercontext.publishercontract.domain uses a module listed above it, which is the healthy direction.
22→12 se.citerus.cqrs.bookstore.ordercontext.publishercontract.domain uses se.citerus.cqrs.bookstore.ordercontext.publishercontract✕
- Connections
- 1 pair of types, where a type in se.citerus.cqrs.bookstore.ordercontext.publishercontract.domain uses a type in se.citerus.cqrs.bookstore.ordercontext.publishercontract.
- The types involved
se.citerus.cqrs.bookstore.ordercontext.publishercontract.domain.PublisherContract→se.citerus.cqrs.bookstore.ordercontext.publishercontract.PublisherContractId
- Direction
- se.citerus.cqrs.bookstore.ordercontext.publishercontract.domain uses se.citerus.cqrs.bookstore.ordercontext.publishercontract, so a change to se.citerus.cqrs.bookstore.ordercontext.publishercontract can break se.citerus.cqrs.bookstore.ordercontext.publishercontract.domain, while a change to se.citerus.cqrs.bookstore.ordercontext.publishercontract.domain can't break se.citerus.cqrs.bookstore.ordercontext.publishercontract.
- Position
- Below the diagonal: se.citerus.cqrs.bookstore.ordercontext.publishercontract.domain uses a module listed above it, which is the healthy direction.
22→14 se.citerus.cqrs.bookstore.ordercontext.publishercontract.domain uses se.citerus.cqrs.bookstore.domain✕
- Connections
- 3 pairs of types, where a type in se.citerus.cqrs.bookstore.ordercontext.publishercontract.domain uses a type in se.citerus.cqrs.bookstore.domain.
- The types involved
se.citerus.cqrs.bookstore.ordercontext.publishercontract.domain.AccumulatedFee→se.citerus.cqrs.bookstore.domain.ValueObjectse.citerus.cqrs.bookstore.ordercontext.publishercontract.domain.Fee→se.citerus.cqrs.bookstore.domain.ValueObjectse.citerus.cqrs.bookstore.ordercontext.publishercontract.domain.PublisherContract→se.citerus.cqrs.bookstore.domain.AggregateRoot
- Direction
- se.citerus.cqrs.bookstore.ordercontext.publishercontract.domain uses se.citerus.cqrs.bookstore.domain, so a change to se.citerus.cqrs.bookstore.domain can break se.citerus.cqrs.bookstore.ordercontext.publishercontract.domain, while a change to se.citerus.cqrs.bookstore.ordercontext.publishercontract.domain can't break se.citerus.cqrs.bookstore.domain.
- Position
- Below the diagonal: se.citerus.cqrs.bookstore.ordercontext.publishercontract.domain uses a module listed above it, which is the healthy direction.
22→17 se.citerus.cqrs.bookstore.ordercontext.publishercontract.domain uses se.citerus.cqrs.bookstore.ordercontext.publishercontract.event✕
- Connections
- 2 pairs of types, where a type in se.citerus.cqrs.bookstore.ordercontext.publishercontract.domain uses a type in se.citerus.cqrs.bookstore.ordercontext.publishercontract.event.
- The types involved
se.citerus.cqrs.bookstore.ordercontext.publishercontract.domain.PublisherContract→se.citerus.cqrs.bookstore.ordercontext.publishercontract.event.PublisherContractRegisteredEventse.citerus.cqrs.bookstore.ordercontext.publishercontract.domain.PublisherContract→se.citerus.cqrs.bookstore.ordercontext.publishercontract.event.PurchaseRegisteredEvent
- Direction
- se.citerus.cqrs.bookstore.ordercontext.publishercontract.domain uses se.citerus.cqrs.bookstore.ordercontext.publishercontract.event, so a change to se.citerus.cqrs.bookstore.ordercontext.publishercontract.event can break se.citerus.cqrs.bookstore.ordercontext.publishercontract.domain, while a change to se.citerus.cqrs.bookstore.ordercontext.publishercontract.domain can't break se.citerus.cqrs.bookstore.ordercontext.publishercontract.event.
- Position
- Below the diagonal: se.citerus.cqrs.bookstore.ordercontext.publishercontract.domain uses a module listed above it, which is the healthy direction.
23→9 se.citerus.cqrs.bookstore.ordercontext.query.sales uses se.citerus.cqrs.bookstore.event✕
- Connections
- 1 pair of types, where a type in se.citerus.cqrs.bookstore.ordercontext.query.sales uses a type in se.citerus.cqrs.bookstore.event.
- The types involved
se.citerus.cqrs.bookstore.ordercontext.query.sales.OrdersPerDayAggregator→se.citerus.cqrs.bookstore.event.DomainEventListener
- Direction
- se.citerus.cqrs.bookstore.ordercontext.query.sales uses se.citerus.cqrs.bookstore.event, so a change to se.citerus.cqrs.bookstore.event can break se.citerus.cqrs.bookstore.ordercontext.query.sales, while a change to se.citerus.cqrs.bookstore.ordercontext.query.sales can't break se.citerus.cqrs.bookstore.event.
- Position
- Below the diagonal: se.citerus.cqrs.bookstore.ordercontext.query.sales uses a module listed above it, which is the healthy direction.
23→16 se.citerus.cqrs.bookstore.ordercontext.query.sales uses se.citerus.cqrs.bookstore.ordercontext.order.event✕
- Connections
- 1 pair of types, where a type in se.citerus.cqrs.bookstore.ordercontext.query.sales uses a type in se.citerus.cqrs.bookstore.ordercontext.order.event.
- The types involved
se.citerus.cqrs.bookstore.ordercontext.query.sales.OrdersPerDayAggregator→se.citerus.cqrs.bookstore.ordercontext.order.event.OrderPlacedEvent
- Direction
- se.citerus.cqrs.bookstore.ordercontext.query.sales uses se.citerus.cqrs.bookstore.ordercontext.order.event, so a change to se.citerus.cqrs.bookstore.ordercontext.order.event can break se.citerus.cqrs.bookstore.ordercontext.query.sales, while a change to se.citerus.cqrs.bookstore.ordercontext.query.sales can't break se.citerus.cqrs.bookstore.ordercontext.order.event.
- Position
- Below the diagonal: se.citerus.cqrs.bookstore.ordercontext.query.sales uses a module listed above it, which is the healthy direction.
24→14 se.citerus.cqrs.bookstore.productcatalog.domain uses se.citerus.cqrs.bookstore.domain✕
- Connections
- 2 pairs of types, where a type in se.citerus.cqrs.bookstore.productcatalog.domain uses a type in se.citerus.cqrs.bookstore.domain.
- The types involved
se.citerus.cqrs.bookstore.productcatalog.domain.Book→se.citerus.cqrs.bookstore.domain.ValueObjectse.citerus.cqrs.bookstore.productcatalog.domain.Product→se.citerus.cqrs.bookstore.domain.ValueObject
- Direction
- se.citerus.cqrs.bookstore.productcatalog.domain uses se.citerus.cqrs.bookstore.domain, so a change to se.citerus.cqrs.bookstore.domain can break se.citerus.cqrs.bookstore.productcatalog.domain, while a change to se.citerus.cqrs.bookstore.productcatalog.domain can't break se.citerus.cqrs.bookstore.domain.
- Position
- Below the diagonal: se.citerus.cqrs.bookstore.productcatalog.domain uses a module listed above it, which is the healthy direction.
25→14 se.citerus.cqrs.bookstore.shopping.domain uses se.citerus.cqrs.bookstore.domain✕
- Connections
- 3 pairs of types, where a type in se.citerus.cqrs.bookstore.shopping.domain uses a type in se.citerus.cqrs.bookstore.domain.
- The types involved
se.citerus.cqrs.bookstore.shopping.domain.Item→se.citerus.cqrs.bookstore.domain.ValueObjectse.citerus.cqrs.bookstore.shopping.domain.LineItem→se.citerus.cqrs.bookstore.domain.ValueObjectse.citerus.cqrs.bookstore.shopping.domain.ProductId→se.citerus.cqrs.bookstore.domain.ValueObject
- Direction
- se.citerus.cqrs.bookstore.shopping.domain uses se.citerus.cqrs.bookstore.domain, so a change to se.citerus.cqrs.bookstore.domain can break se.citerus.cqrs.bookstore.shopping.domain, while a change to se.citerus.cqrs.bookstore.shopping.domain can't break se.citerus.cqrs.bookstore.domain.
- Position
- Below the diagonal: se.citerus.cqrs.bookstore.shopping.domain uses a module listed above it, which is the healthy direction.
26→3 se.citerus.cqrs.bookstore.ordercontext.order.command uses se.citerus.cqrs.bookstore.command✕
- Connections
- 3 pairs of types, where a type in se.citerus.cqrs.bookstore.ordercontext.order.command uses a type in se.citerus.cqrs.bookstore.command.
- The types involved
se.citerus.cqrs.bookstore.ordercontext.order.command.ActivateOrderCommand→se.citerus.cqrs.bookstore.command.Commandse.citerus.cqrs.bookstore.ordercontext.order.command.OrderCommandHandler→se.citerus.cqrs.bookstore.command.CommandHandlerse.citerus.cqrs.bookstore.ordercontext.order.command.PlaceOrderCommand→se.citerus.cqrs.bookstore.command.Command
- Direction
- se.citerus.cqrs.bookstore.ordercontext.order.command uses se.citerus.cqrs.bookstore.command, so a change to se.citerus.cqrs.bookstore.command can break se.citerus.cqrs.bookstore.ordercontext.order.command, while a change to se.citerus.cqrs.bookstore.ordercontext.order.command can't break se.citerus.cqrs.bookstore.command.
- Position
- Below the diagonal: se.citerus.cqrs.bookstore.ordercontext.order.command uses a module listed above it, which is the healthy direction.
26→10 se.citerus.cqrs.bookstore.ordercontext.order.command uses se.citerus.cqrs.bookstore.ordercontext.api✕
- Connections
- 3 pairs of types, where a type in se.citerus.cqrs.bookstore.ordercontext.order.command uses a type in se.citerus.cqrs.bookstore.ordercontext.api.
- The types involved
se.citerus.cqrs.bookstore.ordercontext.order.command.CommandFactory→se.citerus.cqrs.bookstore.ordercontext.api.ActivateOrderRequestse.citerus.cqrs.bookstore.ordercontext.order.command.CommandFactory→se.citerus.cqrs.bookstore.ordercontext.api.CartDtose.citerus.cqrs.bookstore.ordercontext.order.command.CommandFactory→se.citerus.cqrs.bookstore.ordercontext.api.PlaceOrderRequest
- Direction
- se.citerus.cqrs.bookstore.ordercontext.order.command uses se.citerus.cqrs.bookstore.ordercontext.api, so a change to se.citerus.cqrs.bookstore.ordercontext.api can break se.citerus.cqrs.bookstore.ordercontext.order.command, while a change to se.citerus.cqrs.bookstore.ordercontext.order.command can't break se.citerus.cqrs.bookstore.ordercontext.api.
- Position
- Below the diagonal: se.citerus.cqrs.bookstore.ordercontext.order.command uses a module listed above it, which is the healthy direction.
26→11 se.citerus.cqrs.bookstore.ordercontext.order.command uses se.citerus.cqrs.bookstore.ordercontext.order✕
- Connections
- 2 pairs of types, where a type in se.citerus.cqrs.bookstore.ordercontext.order.command uses a type in se.citerus.cqrs.bookstore.ordercontext.order.
- The types involved
se.citerus.cqrs.bookstore.ordercontext.order.command.ActivateOrderCommand→se.citerus.cqrs.bookstore.ordercontext.order.OrderIdse.citerus.cqrs.bookstore.ordercontext.order.command.PlaceOrderCommand→se.citerus.cqrs.bookstore.ordercontext.order.OrderId
- Direction
- se.citerus.cqrs.bookstore.ordercontext.order.command uses se.citerus.cqrs.bookstore.ordercontext.order, so a change to se.citerus.cqrs.bookstore.ordercontext.order can break se.citerus.cqrs.bookstore.ordercontext.order.command, while a change to se.citerus.cqrs.bookstore.ordercontext.order.command can't break se.citerus.cqrs.bookstore.ordercontext.order.
- Position
- Below the diagonal: se.citerus.cqrs.bookstore.ordercontext.order.command uses a module listed above it, which is the healthy direction.
26→14 se.citerus.cqrs.bookstore.ordercontext.order.command uses se.citerus.cqrs.bookstore.domain✕
- Connections
- 1 pair of types, where a type in se.citerus.cqrs.bookstore.ordercontext.order.command uses a type in se.citerus.cqrs.bookstore.domain.
- The types involved
se.citerus.cqrs.bookstore.ordercontext.order.command.OrderCommandHandler→se.citerus.cqrs.bookstore.domain.Repository
- Direction
- se.citerus.cqrs.bookstore.ordercontext.order.command uses se.citerus.cqrs.bookstore.domain, so a change to se.citerus.cqrs.bookstore.domain can break se.citerus.cqrs.bookstore.ordercontext.order.command, while a change to se.citerus.cqrs.bookstore.ordercontext.order.command can't break se.citerus.cqrs.bookstore.domain.
- Position
- Below the diagonal: se.citerus.cqrs.bookstore.ordercontext.order.command uses a module listed above it, which is the healthy direction.
26→20 se.citerus.cqrs.bookstore.ordercontext.order.command uses se.citerus.cqrs.bookstore.ordercontext.order.domain✕
- Connections
- 4 pairs of types, where a type in se.citerus.cqrs.bookstore.ordercontext.order.command uses a type in se.citerus.cqrs.bookstore.ordercontext.order.domain.
- The types involved
se.citerus.cqrs.bookstore.ordercontext.order.command.CommandFactory→se.citerus.cqrs.bookstore.ordercontext.order.domain.CustomerInformationse.citerus.cqrs.bookstore.ordercontext.order.command.CommandFactory→se.citerus.cqrs.bookstore.ordercontext.order.domain.OrderLinese.citerus.cqrs.bookstore.ordercontext.order.command.PlaceOrderCommand→se.citerus.cqrs.bookstore.ordercontext.order.domain.CustomerInformationse.citerus.cqrs.bookstore.ordercontext.order.command.PlaceOrderCommand→se.citerus.cqrs.bookstore.ordercontext.order.domain.OrderLine
- Direction
- se.citerus.cqrs.bookstore.ordercontext.order.command uses se.citerus.cqrs.bookstore.ordercontext.order.domain, so a change to se.citerus.cqrs.bookstore.ordercontext.order.domain can break se.citerus.cqrs.bookstore.ordercontext.order.command, while a change to se.citerus.cqrs.bookstore.ordercontext.order.command can't break se.citerus.cqrs.bookstore.ordercontext.order.domain.
- Position
- Below the diagonal: se.citerus.cqrs.bookstore.ordercontext.order.command uses a module listed above it, which is the healthy direction.
27→5 se.citerus.cqrs.bookstore.ordercontext.query uses se.citerus.cqrs.bookstore.ordercontext.client.productcatalog✕
- Connections
- 1 pair of types, where a type in se.citerus.cqrs.bookstore.ordercontext.query uses a type in se.citerus.cqrs.bookstore.ordercontext.client.productcatalog.
- The types involved
se.citerus.cqrs.bookstore.ordercontext.query.QueryService→se.citerus.cqrs.bookstore.ordercontext.client.productcatalog.ProductCatalogClient
- Direction
- se.citerus.cqrs.bookstore.ordercontext.query uses se.citerus.cqrs.bookstore.ordercontext.client.productcatalog, so a change to se.citerus.cqrs.bookstore.ordercontext.client.productcatalog can break se.citerus.cqrs.bookstore.ordercontext.query, while a change to se.citerus.cqrs.bookstore.ordercontext.query can't break se.citerus.cqrs.bookstore.ordercontext.client.productcatalog.
- Position
- Below the diagonal: se.citerus.cqrs.bookstore.ordercontext.query uses a module listed above it, which is the healthy direction.
27→11 se.citerus.cqrs.bookstore.ordercontext.query uses se.citerus.cqrs.bookstore.ordercontext.order✕
- Connections
- 2 pairs of types, where a type in se.citerus.cqrs.bookstore.ordercontext.query uses a type in se.citerus.cqrs.bookstore.ordercontext.order.
- The types involved
se.citerus.cqrs.bookstore.ordercontext.query.QueryService→se.citerus.cqrs.bookstore.ordercontext.order.OrderIdse.citerus.cqrs.bookstore.ordercontext.query.QueryService→se.citerus.cqrs.bookstore.ordercontext.order.ProductId
- Direction
- se.citerus.cqrs.bookstore.ordercontext.query uses se.citerus.cqrs.bookstore.ordercontext.order, so a change to se.citerus.cqrs.bookstore.ordercontext.order can break se.citerus.cqrs.bookstore.ordercontext.query, while a change to se.citerus.cqrs.bookstore.ordercontext.query can't break se.citerus.cqrs.bookstore.ordercontext.order.
- Position
- Below the diagonal: se.citerus.cqrs.bookstore.ordercontext.query uses a module listed above it, which is the healthy direction.
27→12 se.citerus.cqrs.bookstore.ordercontext.query uses se.citerus.cqrs.bookstore.ordercontext.publishercontract✕
- Connections
- 1 pair of types, where a type in se.citerus.cqrs.bookstore.ordercontext.query uses a type in se.citerus.cqrs.bookstore.ordercontext.publishercontract.
- The types involved
se.citerus.cqrs.bookstore.ordercontext.query.QueryService→se.citerus.cqrs.bookstore.ordercontext.publishercontract.PublisherContractId
- Direction
- se.citerus.cqrs.bookstore.ordercontext.query uses se.citerus.cqrs.bookstore.ordercontext.publishercontract, so a change to se.citerus.cqrs.bookstore.ordercontext.publishercontract can break se.citerus.cqrs.bookstore.ordercontext.query, while a change to se.citerus.cqrs.bookstore.ordercontext.query can't break se.citerus.cqrs.bookstore.ordercontext.publishercontract.
- Position
- Below the diagonal: se.citerus.cqrs.bookstore.ordercontext.query uses a module listed above it, which is the healthy direction.
27→23 se.citerus.cqrs.bookstore.ordercontext.query uses se.citerus.cqrs.bookstore.ordercontext.query.sales✕
- Connections
- 1 pair of types, where a type in se.citerus.cqrs.bookstore.ordercontext.query uses a type in se.citerus.cqrs.bookstore.ordercontext.query.sales.
- The types involved
se.citerus.cqrs.bookstore.ordercontext.query.QueryService→se.citerus.cqrs.bookstore.ordercontext.query.sales.OrdersPerDayAggregator
- Direction
- se.citerus.cqrs.bookstore.ordercontext.query uses se.citerus.cqrs.bookstore.ordercontext.query.sales, so a change to se.citerus.cqrs.bookstore.ordercontext.query.sales can break se.citerus.cqrs.bookstore.ordercontext.query, while a change to se.citerus.cqrs.bookstore.ordercontext.query can't break se.citerus.cqrs.bookstore.ordercontext.query.sales.
- Position
- Below the diagonal: se.citerus.cqrs.bookstore.ordercontext.query uses a module listed above it, which is the healthy direction.
27→32 se.citerus.cqrs.bookstore.ordercontext.query uses se.citerus.cqrs.bookstore.ordercontext.query.orderlist part of a loop✕
- Connections
- 2 pairs of types, where a type in se.citerus.cqrs.bookstore.ordercontext.query uses a type in se.citerus.cqrs.bookstore.ordercontext.query.orderlist.
- The types involved
se.citerus.cqrs.bookstore.ordercontext.query.QueryService→se.citerus.cqrs.bookstore.ordercontext.query.orderlist.OrderListDenormalizerse.citerus.cqrs.bookstore.ordercontext.query.QueryService→se.citerus.cqrs.bookstore.ordercontext.query.orderlist.OrderProjection
- Direction
- se.citerus.cqrs.bookstore.ordercontext.query uses se.citerus.cqrs.bookstore.ordercontext.query.orderlist, so a change to se.citerus.cqrs.bookstore.ordercontext.query.orderlist can break se.citerus.cqrs.bookstore.ordercontext.query, while a change to se.citerus.cqrs.bookstore.ordercontext.query can't break se.citerus.cqrs.bookstore.ordercontext.query.orderlist.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
28→2 se.citerus.cqrs.bookstore.productcatalog.api uses se.citerus.cqrs.bookstore✕
- Connections
- 2 pairs of types, where a type in se.citerus.cqrs.bookstore.productcatalog.api uses a type in se.citerus.cqrs.bookstore.
- The types involved
se.citerus.cqrs.bookstore.productcatalog.api.BookDto→se.citerus.cqrs.bookstore.TransportObjectse.citerus.cqrs.bookstore.productcatalog.api.ProductDto→se.citerus.cqrs.bookstore.TransportObject
- Direction
- se.citerus.cqrs.bookstore.productcatalog.api uses se.citerus.cqrs.bookstore, so a change to se.citerus.cqrs.bookstore can break se.citerus.cqrs.bookstore.productcatalog.api, while a change to se.citerus.cqrs.bookstore.productcatalog.api can't break se.citerus.cqrs.bookstore.
- Position
- Below the diagonal: se.citerus.cqrs.bookstore.productcatalog.api uses a module listed above it, which is the healthy direction.
28→24 se.citerus.cqrs.bookstore.productcatalog.api uses se.citerus.cqrs.bookstore.productcatalog.domain✕
- Connections
- 2 pairs of types, where a type in se.citerus.cqrs.bookstore.productcatalog.api uses a type in se.citerus.cqrs.bookstore.productcatalog.domain.
- The types involved
se.citerus.cqrs.bookstore.productcatalog.api.ProductDtoFactory→se.citerus.cqrs.bookstore.productcatalog.domain.Bookse.citerus.cqrs.bookstore.productcatalog.api.ProductDtoFactory→se.citerus.cqrs.bookstore.productcatalog.domain.Product
- Direction
- se.citerus.cqrs.bookstore.productcatalog.api uses se.citerus.cqrs.bookstore.productcatalog.domain, so a change to se.citerus.cqrs.bookstore.productcatalog.domain can break se.citerus.cqrs.bookstore.productcatalog.api, while a change to se.citerus.cqrs.bookstore.productcatalog.api can't break se.citerus.cqrs.bookstore.productcatalog.domain.
- Position
- Below the diagonal: se.citerus.cqrs.bookstore.productcatalog.api uses a module listed above it, which is the healthy direction.
29→24 se.citerus.cqrs.bookstore.productcatalog.infrastructure uses se.citerus.cqrs.bookstore.productcatalog.domain✕
- Connections
- 3 pairs of types, where a type in se.citerus.cqrs.bookstore.productcatalog.infrastructure uses a type in se.citerus.cqrs.bookstore.productcatalog.domain.
- The types involved
se.citerus.cqrs.bookstore.productcatalog.infrastructure.1→se.citerus.cqrs.bookstore.productcatalog.domain.Productse.citerus.cqrs.bookstore.productcatalog.infrastructure.InMemoryProductRepository→se.citerus.cqrs.bookstore.productcatalog.domain.Productse.citerus.cqrs.bookstore.productcatalog.infrastructure.InMemoryProductRepository→se.citerus.cqrs.bookstore.productcatalog.domain.ProductRepository
- Direction
- se.citerus.cqrs.bookstore.productcatalog.infrastructure uses se.citerus.cqrs.bookstore.productcatalog.domain, so a change to se.citerus.cqrs.bookstore.productcatalog.domain can break se.citerus.cqrs.bookstore.productcatalog.infrastructure, while a change to se.citerus.cqrs.bookstore.productcatalog.infrastructure can't break se.citerus.cqrs.bookstore.productcatalog.domain.
- Position
- Below the diagonal: se.citerus.cqrs.bookstore.productcatalog.infrastructure uses a module listed above it, which is the healthy direction.
30→2 se.citerus.cqrs.bookstore.shopping.api uses se.citerus.cqrs.bookstore✕
- Connections
- 4 pairs of types, where a type in se.citerus.cqrs.bookstore.shopping.api uses a type in se.citerus.cqrs.bookstore.
- The types involved
se.citerus.cqrs.bookstore.shopping.api.AddItemRequest→se.citerus.cqrs.bookstore.TransportObjectse.citerus.cqrs.bookstore.shopping.api.CartDto→se.citerus.cqrs.bookstore.TransportObjectse.citerus.cqrs.bookstore.shopping.api.CreateCartRequest→se.citerus.cqrs.bookstore.TransportObjectse.citerus.cqrs.bookstore.shopping.api.LineItemDto→se.citerus.cqrs.bookstore.TransportObject
- Direction
- se.citerus.cqrs.bookstore.shopping.api uses se.citerus.cqrs.bookstore, so a change to se.citerus.cqrs.bookstore can break se.citerus.cqrs.bookstore.shopping.api, while a change to se.citerus.cqrs.bookstore.shopping.api can't break se.citerus.cqrs.bookstore.
- Position
- Below the diagonal: se.citerus.cqrs.bookstore.shopping.api uses a module listed above it, which is the healthy direction.
30→25 se.citerus.cqrs.bookstore.shopping.api uses se.citerus.cqrs.bookstore.shopping.domain✕
- Connections
- 2 pairs of types, where a type in se.citerus.cqrs.bookstore.shopping.api uses a type in se.citerus.cqrs.bookstore.shopping.domain.
- The types involved
se.citerus.cqrs.bookstore.shopping.api.CartDtoFactory→se.citerus.cqrs.bookstore.shopping.domain.Cartse.citerus.cqrs.bookstore.shopping.api.CartDtoFactory→se.citerus.cqrs.bookstore.shopping.domain.LineItem
- Direction
- se.citerus.cqrs.bookstore.shopping.api uses se.citerus.cqrs.bookstore.shopping.domain, so a change to se.citerus.cqrs.bookstore.shopping.domain can break se.citerus.cqrs.bookstore.shopping.api, while a change to se.citerus.cqrs.bookstore.shopping.api can't break se.citerus.cqrs.bookstore.shopping.domain.
- Position
- Below the diagonal: se.citerus.cqrs.bookstore.shopping.api uses a module listed above it, which is the healthy direction.
31→25 se.citerus.cqrs.bookstore.shopping.infrastructure uses se.citerus.cqrs.bookstore.shopping.domain✕
- Connections
- 2 pairs of types, where a type in se.citerus.cqrs.bookstore.shopping.infrastructure uses a type in se.citerus.cqrs.bookstore.shopping.domain.
- The types involved
se.citerus.cqrs.bookstore.shopping.infrastructure.InMemoryCartRepository→se.citerus.cqrs.bookstore.shopping.domain.Cartse.citerus.cqrs.bookstore.shopping.infrastructure.InMemoryCartRepository→se.citerus.cqrs.bookstore.shopping.domain.CartRepository
- Direction
- se.citerus.cqrs.bookstore.shopping.infrastructure uses se.citerus.cqrs.bookstore.shopping.domain, so a change to se.citerus.cqrs.bookstore.shopping.domain can break se.citerus.cqrs.bookstore.shopping.infrastructure, while a change to se.citerus.cqrs.bookstore.shopping.infrastructure can't break se.citerus.cqrs.bookstore.shopping.domain.
- Position
- Below the diagonal: se.citerus.cqrs.bookstore.shopping.infrastructure uses a module listed above it, which is the healthy direction.
32→9 se.citerus.cqrs.bookstore.ordercontext.query.orderlist uses se.citerus.cqrs.bookstore.event✕
- Connections
- 1 pair of types, where a type in se.citerus.cqrs.bookstore.ordercontext.query.orderlist uses a type in se.citerus.cqrs.bookstore.event.
- The types involved
se.citerus.cqrs.bookstore.ordercontext.query.orderlist.OrderListDenormalizer→se.citerus.cqrs.bookstore.event.DomainEventListener
- Direction
- se.citerus.cqrs.bookstore.ordercontext.query.orderlist uses se.citerus.cqrs.bookstore.event, so a change to se.citerus.cqrs.bookstore.event can break se.citerus.cqrs.bookstore.ordercontext.query.orderlist, while a change to se.citerus.cqrs.bookstore.ordercontext.query.orderlist can't break se.citerus.cqrs.bookstore.event.
- Position
- Below the diagonal: se.citerus.cqrs.bookstore.ordercontext.query.orderlist uses a module listed above it, which is the healthy direction.
32→11 se.citerus.cqrs.bookstore.ordercontext.query.orderlist uses se.citerus.cqrs.bookstore.ordercontext.order✕
- Connections
- 5 pairs of types, where a type in se.citerus.cqrs.bookstore.ordercontext.query.orderlist uses a type in se.citerus.cqrs.bookstore.ordercontext.order.
- The types involved
se.citerus.cqrs.bookstore.ordercontext.query.orderlist.OrderLineProjection→se.citerus.cqrs.bookstore.ordercontext.order.ProductIdse.citerus.cqrs.bookstore.ordercontext.query.orderlist.OrderListDenormalizer→se.citerus.cqrs.bookstore.ordercontext.order.OrderIdse.citerus.cqrs.bookstore.ordercontext.query.orderlist.OrderProjection→se.citerus.cqrs.bookstore.ordercontext.order.OrderIdse.citerus.cqrs.bookstore.ordercontext.query.orderlist.OrderProjection→se.citerus.cqrs.bookstore.ordercontext.order.OrderStatusse.citerus.cqrs.bookstore.ordercontext.query.orderlist.OrderProjectionRepository→se.citerus.cqrs.bookstore.ordercontext.order.OrderId
- Direction
- se.citerus.cqrs.bookstore.ordercontext.query.orderlist uses se.citerus.cqrs.bookstore.ordercontext.order, so a change to se.citerus.cqrs.bookstore.ordercontext.order can break se.citerus.cqrs.bookstore.ordercontext.query.orderlist, while a change to se.citerus.cqrs.bookstore.ordercontext.query.orderlist can't break se.citerus.cqrs.bookstore.ordercontext.order.
- Position
- Below the diagonal: se.citerus.cqrs.bookstore.ordercontext.query.orderlist uses a module listed above it, which is the healthy direction.
32→16 se.citerus.cqrs.bookstore.ordercontext.query.orderlist uses se.citerus.cqrs.bookstore.ordercontext.order.event✕
- Connections
- 2 pairs of types, where a type in se.citerus.cqrs.bookstore.ordercontext.query.orderlist uses a type in se.citerus.cqrs.bookstore.ordercontext.order.event.
- The types involved
se.citerus.cqrs.bookstore.ordercontext.query.orderlist.OrderListDenormalizer→se.citerus.cqrs.bookstore.ordercontext.order.event.OrderActivatedEventse.citerus.cqrs.bookstore.ordercontext.query.orderlist.OrderListDenormalizer→se.citerus.cqrs.bookstore.ordercontext.order.event.OrderPlacedEvent
- Direction
- se.citerus.cqrs.bookstore.ordercontext.query.orderlist uses se.citerus.cqrs.bookstore.ordercontext.order.event, so a change to se.citerus.cqrs.bookstore.ordercontext.order.event can break se.citerus.cqrs.bookstore.ordercontext.query.orderlist, while a change to se.citerus.cqrs.bookstore.ordercontext.query.orderlist can't break se.citerus.cqrs.bookstore.ordercontext.order.event.
- Position
- Below the diagonal: se.citerus.cqrs.bookstore.ordercontext.query.orderlist uses a module listed above it, which is the healthy direction.
32→27 se.citerus.cqrs.bookstore.ordercontext.query.orderlist uses se.citerus.cqrs.bookstore.ordercontext.query✕
- Connections
- 1 pair of types, where a type in se.citerus.cqrs.bookstore.ordercontext.query.orderlist uses a type in se.citerus.cqrs.bookstore.ordercontext.query.
- The types involved
se.citerus.cqrs.bookstore.ordercontext.query.orderlist.OrderProjection→se.citerus.cqrs.bookstore.ordercontext.query.Projection
- Direction
- se.citerus.cqrs.bookstore.ordercontext.query.orderlist uses se.citerus.cqrs.bookstore.ordercontext.query, so a change to se.citerus.cqrs.bookstore.ordercontext.query can break se.citerus.cqrs.bookstore.ordercontext.query.orderlist, while a change to se.citerus.cqrs.bookstore.ordercontext.query.orderlist can't break se.citerus.cqrs.bookstore.ordercontext.query.
- Position
- Below the diagonal: se.citerus.cqrs.bookstore.ordercontext.query.orderlist uses a module listed above it, which is the healthy direction.
33→3 se.citerus.cqrs.bookstore.ordercontext.saga uses se.citerus.cqrs.bookstore.command✕
- Connections
- 1 pair of types, where a type in se.citerus.cqrs.bookstore.ordercontext.saga uses a type in se.citerus.cqrs.bookstore.command.
- The types involved
se.citerus.cqrs.bookstore.ordercontext.saga.PurchaseRegistrationSaga→se.citerus.cqrs.bookstore.command.CommandBus
- Direction
- se.citerus.cqrs.bookstore.ordercontext.saga uses se.citerus.cqrs.bookstore.command, so a change to se.citerus.cqrs.bookstore.command can break se.citerus.cqrs.bookstore.ordercontext.saga, while a change to se.citerus.cqrs.bookstore.ordercontext.saga can't break se.citerus.cqrs.bookstore.command.
- Position
- Below the diagonal: se.citerus.cqrs.bookstore.ordercontext.saga uses a module listed above it, which is the healthy direction.
33→16 se.citerus.cqrs.bookstore.ordercontext.saga uses se.citerus.cqrs.bookstore.ordercontext.order.event✕
- Connections
- 1 pair of types, where a type in se.citerus.cqrs.bookstore.ordercontext.saga uses a type in se.citerus.cqrs.bookstore.ordercontext.order.event.
- The types involved
se.citerus.cqrs.bookstore.ordercontext.saga.PurchaseRegistrationSaga→se.citerus.cqrs.bookstore.ordercontext.order.event.OrderActivatedEvent
- Direction
- se.citerus.cqrs.bookstore.ordercontext.saga uses se.citerus.cqrs.bookstore.ordercontext.order.event, so a change to se.citerus.cqrs.bookstore.ordercontext.order.event can break se.citerus.cqrs.bookstore.ordercontext.saga, while a change to se.citerus.cqrs.bookstore.ordercontext.saga can't break se.citerus.cqrs.bookstore.ordercontext.order.event.
- Position
- Below the diagonal: se.citerus.cqrs.bookstore.ordercontext.saga uses a module listed above it, which is the healthy direction.
33→18 se.citerus.cqrs.bookstore.ordercontext.saga uses se.citerus.cqrs.bookstore.saga✕
- Connections
- 1 pair of types, where a type in se.citerus.cqrs.bookstore.ordercontext.saga uses a type in se.citerus.cqrs.bookstore.saga.
- The types involved
se.citerus.cqrs.bookstore.ordercontext.saga.PurchaseRegistrationSaga→se.citerus.cqrs.bookstore.saga.Saga
- Direction
- se.citerus.cqrs.bookstore.ordercontext.saga uses se.citerus.cqrs.bookstore.saga, so a change to se.citerus.cqrs.bookstore.saga can break se.citerus.cqrs.bookstore.ordercontext.saga, while a change to se.citerus.cqrs.bookstore.ordercontext.saga can't break se.citerus.cqrs.bookstore.saga.
- Position
- Below the diagonal: se.citerus.cqrs.bookstore.ordercontext.saga uses a module listed above it, which is the healthy direction.
33→21 se.citerus.cqrs.bookstore.ordercontext.saga uses se.citerus.cqrs.bookstore.ordercontext.publishercontract.command✕
- Connections
- 1 pair of types, where a type in se.citerus.cqrs.bookstore.ordercontext.saga uses a type in se.citerus.cqrs.bookstore.ordercontext.publishercontract.command.
- The types involved
se.citerus.cqrs.bookstore.ordercontext.saga.PurchaseRegistrationSaga→se.citerus.cqrs.bookstore.ordercontext.publishercontract.command.RegisterPurchaseCommand
- Direction
- se.citerus.cqrs.bookstore.ordercontext.saga uses se.citerus.cqrs.bookstore.ordercontext.publishercontract.command, so a change to se.citerus.cqrs.bookstore.ordercontext.publishercontract.command can break se.citerus.cqrs.bookstore.ordercontext.saga, while a change to se.citerus.cqrs.bookstore.ordercontext.saga can't break se.citerus.cqrs.bookstore.ordercontext.publishercontract.command.
- Position
- Below the diagonal: se.citerus.cqrs.bookstore.ordercontext.saga uses a module listed above it, which is the healthy direction.
33→27 se.citerus.cqrs.bookstore.ordercontext.saga uses se.citerus.cqrs.bookstore.ordercontext.query✕
- Connections
- 1 pair of types, where a type in se.citerus.cqrs.bookstore.ordercontext.saga uses a type in se.citerus.cqrs.bookstore.ordercontext.query.
- The types involved
se.citerus.cqrs.bookstore.ordercontext.saga.PurchaseRegistrationSaga→se.citerus.cqrs.bookstore.ordercontext.query.QueryService
- Direction
- se.citerus.cqrs.bookstore.ordercontext.saga uses se.citerus.cqrs.bookstore.ordercontext.query, so a change to se.citerus.cqrs.bookstore.ordercontext.query can break se.citerus.cqrs.bookstore.ordercontext.saga, while a change to se.citerus.cqrs.bookstore.ordercontext.saga can't break se.citerus.cqrs.bookstore.ordercontext.query.
- Position
- Below the diagonal: se.citerus.cqrs.bookstore.ordercontext.saga uses a module listed above it, which is the healthy direction.
34→24 se.citerus.cqrs.bookstore.productcatalog.resource uses se.citerus.cqrs.bookstore.productcatalog.domain✕
- Connections
- 1 pair of types, where a type in se.citerus.cqrs.bookstore.productcatalog.resource uses a type in se.citerus.cqrs.bookstore.productcatalog.domain.
- The types involved
se.citerus.cqrs.bookstore.productcatalog.resource.ProductResource→se.citerus.cqrs.bookstore.productcatalog.domain.ProductRepository
- Direction
- se.citerus.cqrs.bookstore.productcatalog.resource uses se.citerus.cqrs.bookstore.productcatalog.domain, so a change to se.citerus.cqrs.bookstore.productcatalog.domain can break se.citerus.cqrs.bookstore.productcatalog.resource, while a change to se.citerus.cqrs.bookstore.productcatalog.resource can't break se.citerus.cqrs.bookstore.productcatalog.domain.
- Position
- Below the diagonal: se.citerus.cqrs.bookstore.productcatalog.resource uses a module listed above it, which is the healthy direction.
34→28 se.citerus.cqrs.bookstore.productcatalog.resource uses se.citerus.cqrs.bookstore.productcatalog.api✕
- Connections
- 1 pair of types, where a type in se.citerus.cqrs.bookstore.productcatalog.resource uses a type in se.citerus.cqrs.bookstore.productcatalog.api.
- The types involved
se.citerus.cqrs.bookstore.productcatalog.resource.ProductResource→se.citerus.cqrs.bookstore.productcatalog.api.ProductDto
- Direction
- se.citerus.cqrs.bookstore.productcatalog.resource uses se.citerus.cqrs.bookstore.productcatalog.api, so a change to se.citerus.cqrs.bookstore.productcatalog.api can break se.citerus.cqrs.bookstore.productcatalog.resource, while a change to se.citerus.cqrs.bookstore.productcatalog.resource can't break se.citerus.cqrs.bookstore.productcatalog.api.
- Position
- Below the diagonal: se.citerus.cqrs.bookstore.productcatalog.resource uses a module listed above it, which is the healthy direction.
35→13 se.citerus.cqrs.bookstore.shopping.resource uses se.citerus.cqrs.bookstore.shopping.client.productcatalog✕
- Connections
- 2 pairs of types, where a type in se.citerus.cqrs.bookstore.shopping.resource uses a type in se.citerus.cqrs.bookstore.shopping.client.productcatalog.
- The types involved
se.citerus.cqrs.bookstore.shopping.resource.CartResource→se.citerus.cqrs.bookstore.shopping.client.productcatalog.ProductCatalogClientse.citerus.cqrs.bookstore.shopping.resource.CartResource→se.citerus.cqrs.bookstore.shopping.client.productcatalog.ProductDto
- Direction
- se.citerus.cqrs.bookstore.shopping.resource uses se.citerus.cqrs.bookstore.shopping.client.productcatalog, so a change to se.citerus.cqrs.bookstore.shopping.client.productcatalog can break se.citerus.cqrs.bookstore.shopping.resource, while a change to se.citerus.cqrs.bookstore.shopping.resource can't break se.citerus.cqrs.bookstore.shopping.client.productcatalog.
- Position
- Below the diagonal: se.citerus.cqrs.bookstore.shopping.resource uses a module listed above it, which is the healthy direction.
35→25 se.citerus.cqrs.bookstore.shopping.resource uses se.citerus.cqrs.bookstore.shopping.domain✕
- Connections
- 1 pair of types, where a type in se.citerus.cqrs.bookstore.shopping.resource uses a type in se.citerus.cqrs.bookstore.shopping.domain.
- The types involved
se.citerus.cqrs.bookstore.shopping.resource.CartResource→se.citerus.cqrs.bookstore.shopping.domain.CartRepository
- Direction
- se.citerus.cqrs.bookstore.shopping.resource uses se.citerus.cqrs.bookstore.shopping.domain, so a change to se.citerus.cqrs.bookstore.shopping.domain can break se.citerus.cqrs.bookstore.shopping.resource, while a change to se.citerus.cqrs.bookstore.shopping.resource can't break se.citerus.cqrs.bookstore.shopping.domain.
- Position
- Below the diagonal: se.citerus.cqrs.bookstore.shopping.resource uses a module listed above it, which is the healthy direction.
35→30 se.citerus.cqrs.bookstore.shopping.resource uses se.citerus.cqrs.bookstore.shopping.api✕
- Connections
- 3 pairs of types, where a type in se.citerus.cqrs.bookstore.shopping.resource uses a type in se.citerus.cqrs.bookstore.shopping.api.
- The types involved
se.citerus.cqrs.bookstore.shopping.resource.CartResource→se.citerus.cqrs.bookstore.shopping.api.AddItemRequestse.citerus.cqrs.bookstore.shopping.resource.CartResource→se.citerus.cqrs.bookstore.shopping.api.CartDtose.citerus.cqrs.bookstore.shopping.resource.CartResource→se.citerus.cqrs.bookstore.shopping.api.CreateCartRequest
- Direction
- se.citerus.cqrs.bookstore.shopping.resource uses se.citerus.cqrs.bookstore.shopping.api, so a change to se.citerus.cqrs.bookstore.shopping.api can break se.citerus.cqrs.bookstore.shopping.resource, while a change to se.citerus.cqrs.bookstore.shopping.resource can't break se.citerus.cqrs.bookstore.shopping.api.
- Position
- Below the diagonal: se.citerus.cqrs.bookstore.shopping.resource uses a module listed above it, which is the healthy direction.
36→11 se.citerus.cqrs.bookstore.ordercontext.infrastructure uses se.citerus.cqrs.bookstore.ordercontext.order✕
- Connections
- 1 pair of types, where a type in se.citerus.cqrs.bookstore.ordercontext.infrastructure uses a type in se.citerus.cqrs.bookstore.ordercontext.order.
- The types involved
se.citerus.cqrs.bookstore.ordercontext.infrastructure.InMemOrderProjectionRepository→se.citerus.cqrs.bookstore.ordercontext.order.OrderId
- Direction
- se.citerus.cqrs.bookstore.ordercontext.infrastructure uses se.citerus.cqrs.bookstore.ordercontext.order, so a change to se.citerus.cqrs.bookstore.ordercontext.order can break se.citerus.cqrs.bookstore.ordercontext.infrastructure, while a change to se.citerus.cqrs.bookstore.ordercontext.infrastructure can't break se.citerus.cqrs.bookstore.ordercontext.order.
- Position
- Below the diagonal: se.citerus.cqrs.bookstore.ordercontext.infrastructure uses a module listed above it, which is the healthy direction.
36→32 se.citerus.cqrs.bookstore.ordercontext.infrastructure uses se.citerus.cqrs.bookstore.ordercontext.query.orderlist✕
- Connections
- 3 pairs of types, where a type in se.citerus.cqrs.bookstore.ordercontext.infrastructure uses a type in se.citerus.cqrs.bookstore.ordercontext.query.orderlist.
- The types involved
se.citerus.cqrs.bookstore.ordercontext.infrastructure.InMemOrderProjectionRepository→se.citerus.cqrs.bookstore.ordercontext.query.orderlist.OrderProjectionse.citerus.cqrs.bookstore.ordercontext.infrastructure.InMemOrderProjectionRepository→se.citerus.cqrs.bookstore.ordercontext.query.orderlist.OrderProjectionRepositoryse.citerus.cqrs.bookstore.ordercontext.infrastructure.OrderTimestampComparator→se.citerus.cqrs.bookstore.ordercontext.query.orderlist.OrderProjection
- Direction
- se.citerus.cqrs.bookstore.ordercontext.infrastructure uses se.citerus.cqrs.bookstore.ordercontext.query.orderlist, so a change to se.citerus.cqrs.bookstore.ordercontext.query.orderlist can break se.citerus.cqrs.bookstore.ordercontext.infrastructure, while a change to se.citerus.cqrs.bookstore.ordercontext.infrastructure can't break se.citerus.cqrs.bookstore.ordercontext.query.orderlist.
- Position
- Below the diagonal: se.citerus.cqrs.bookstore.ordercontext.infrastructure uses a module listed above it, which is the healthy direction.
37→3 se.citerus.cqrs.bookstore.ordercontext.resource uses se.citerus.cqrs.bookstore.command✕
- Connections
- 2 pairs of types, where a type in se.citerus.cqrs.bookstore.ordercontext.resource uses a type in se.citerus.cqrs.bookstore.command.
- The types involved
se.citerus.cqrs.bookstore.ordercontext.resource.OrderResource→se.citerus.cqrs.bookstore.command.CommandBusse.citerus.cqrs.bookstore.ordercontext.resource.PublisherContractResource→se.citerus.cqrs.bookstore.command.CommandBus
- Direction
- se.citerus.cqrs.bookstore.ordercontext.resource uses se.citerus.cqrs.bookstore.command, so a change to se.citerus.cqrs.bookstore.command can break se.citerus.cqrs.bookstore.ordercontext.resource, while a change to se.citerus.cqrs.bookstore.ordercontext.resource can't break se.citerus.cqrs.bookstore.command.
- Position
- Below the diagonal: se.citerus.cqrs.bookstore.ordercontext.resource uses a module listed above it, which is the healthy direction.
37→9 se.citerus.cqrs.bookstore.ordercontext.resource uses se.citerus.cqrs.bookstore.event✕
- Connections
- 1 pair of types, where a type in se.citerus.cqrs.bookstore.ordercontext.resource uses a type in se.citerus.cqrs.bookstore.event.
- The types involved
se.citerus.cqrs.bookstore.ordercontext.resource.QueryResource→se.citerus.cqrs.bookstore.event.DomainEventStore
- Direction
- se.citerus.cqrs.bookstore.ordercontext.resource uses se.citerus.cqrs.bookstore.event, so a change to se.citerus.cqrs.bookstore.event can break se.citerus.cqrs.bookstore.ordercontext.resource, while a change to se.citerus.cqrs.bookstore.ordercontext.resource can't break se.citerus.cqrs.bookstore.event.
- Position
- Below the diagonal: se.citerus.cqrs.bookstore.ordercontext.resource uses a module listed above it, which is the healthy direction.
37→10 se.citerus.cqrs.bookstore.ordercontext.resource uses se.citerus.cqrs.bookstore.ordercontext.api✕
- Connections
- 3 pairs of types, where a type in se.citerus.cqrs.bookstore.ordercontext.resource uses a type in se.citerus.cqrs.bookstore.ordercontext.api.
- The types involved
se.citerus.cqrs.bookstore.ordercontext.resource.OrderResource→se.citerus.cqrs.bookstore.ordercontext.api.ActivateOrderRequestse.citerus.cqrs.bookstore.ordercontext.resource.OrderResource→se.citerus.cqrs.bookstore.ordercontext.api.PlaceOrderRequestse.citerus.cqrs.bookstore.ordercontext.resource.PublisherContractResource→se.citerus.cqrs.bookstore.ordercontext.api.RegisterPublisherContractRequest
- Direction
- se.citerus.cqrs.bookstore.ordercontext.resource uses se.citerus.cqrs.bookstore.ordercontext.api, so a change to se.citerus.cqrs.bookstore.ordercontext.api can break se.citerus.cqrs.bookstore.ordercontext.resource, while a change to se.citerus.cqrs.bookstore.ordercontext.resource can't break se.citerus.cqrs.bookstore.ordercontext.api.
- Position
- Below the diagonal: se.citerus.cqrs.bookstore.ordercontext.resource uses a module listed above it, which is the healthy direction.
37→21 se.citerus.cqrs.bookstore.ordercontext.resource uses se.citerus.cqrs.bookstore.ordercontext.publishercontract.command✕
- Connections
- 1 pair of types, where a type in se.citerus.cqrs.bookstore.ordercontext.resource uses a type in se.citerus.cqrs.bookstore.ordercontext.publishercontract.command.
- The types involved
se.citerus.cqrs.bookstore.ordercontext.resource.PublisherContractResource→se.citerus.cqrs.bookstore.ordercontext.publishercontract.command.CommandFactory
- Direction
- se.citerus.cqrs.bookstore.ordercontext.resource uses se.citerus.cqrs.bookstore.ordercontext.publishercontract.command, so a change to se.citerus.cqrs.bookstore.ordercontext.publishercontract.command can break se.citerus.cqrs.bookstore.ordercontext.resource, while a change to se.citerus.cqrs.bookstore.ordercontext.resource can't break se.citerus.cqrs.bookstore.ordercontext.publishercontract.command.
- Position
- Below the diagonal: se.citerus.cqrs.bookstore.ordercontext.resource uses a module listed above it, which is the healthy direction.
37→26 se.citerus.cqrs.bookstore.ordercontext.resource uses se.citerus.cqrs.bookstore.ordercontext.order.command✕
- Connections
- 1 pair of types, where a type in se.citerus.cqrs.bookstore.ordercontext.resource uses a type in se.citerus.cqrs.bookstore.ordercontext.order.command.
- The types involved
se.citerus.cqrs.bookstore.ordercontext.resource.OrderResource→se.citerus.cqrs.bookstore.ordercontext.order.command.CommandFactory
- Direction
- se.citerus.cqrs.bookstore.ordercontext.resource uses se.citerus.cqrs.bookstore.ordercontext.order.command, so a change to se.citerus.cqrs.bookstore.ordercontext.order.command can break se.citerus.cqrs.bookstore.ordercontext.resource, while a change to se.citerus.cqrs.bookstore.ordercontext.resource can't break se.citerus.cqrs.bookstore.ordercontext.order.command.
- Position
- Below the diagonal: se.citerus.cqrs.bookstore.ordercontext.resource uses a module listed above it, which is the healthy direction.
37→27 se.citerus.cqrs.bookstore.ordercontext.resource uses se.citerus.cqrs.bookstore.ordercontext.query✕
- Connections
- 1 pair of types, where a type in se.citerus.cqrs.bookstore.ordercontext.resource uses a type in se.citerus.cqrs.bookstore.ordercontext.query.
- The types involved
se.citerus.cqrs.bookstore.ordercontext.resource.QueryResource→se.citerus.cqrs.bookstore.ordercontext.query.QueryService
- Direction
- se.citerus.cqrs.bookstore.ordercontext.resource uses se.citerus.cqrs.bookstore.ordercontext.query, so a change to se.citerus.cqrs.bookstore.ordercontext.query can break se.citerus.cqrs.bookstore.ordercontext.resource, while a change to se.citerus.cqrs.bookstore.ordercontext.resource can't break se.citerus.cqrs.bookstore.ordercontext.query.
- Position
- Below the diagonal: se.citerus.cqrs.bookstore.ordercontext.resource uses a module listed above it, which is the healthy direction.
37→32 se.citerus.cqrs.bookstore.ordercontext.resource uses se.citerus.cqrs.bookstore.ordercontext.query.orderlist✕
- Connections
- 1 pair of types, where a type in se.citerus.cqrs.bookstore.ordercontext.resource uses a type in se.citerus.cqrs.bookstore.ordercontext.query.orderlist.
- The types involved
se.citerus.cqrs.bookstore.ordercontext.resource.QueryResource→se.citerus.cqrs.bookstore.ordercontext.query.orderlist.OrderProjection
- Direction
- se.citerus.cqrs.bookstore.ordercontext.resource uses se.citerus.cqrs.bookstore.ordercontext.query.orderlist, so a change to se.citerus.cqrs.bookstore.ordercontext.query.orderlist can break se.citerus.cqrs.bookstore.ordercontext.resource, while a change to se.citerus.cqrs.bookstore.ordercontext.resource can't break se.citerus.cqrs.bookstore.ordercontext.query.orderlist.
- Position
- Below the diagonal: se.citerus.cqrs.bookstore.ordercontext.resource uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
At a glance — Domain Modelling
At a glance — Accessibility
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A05:2025 — Injection | 7 | Medium |
| A03:2025 — Software Supply Chain Failures | 3 | High / Critical |
Roadmap
Top priorities: Resolve the 1 No ADRs found finding(s) in ADR Quality; Resolve the 5 Orphaned file finding(s) in Knowledge Freshness — start with OrderApplication.java, CartResource.java, SimpleFileBasedEventStore.java; Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 1 No ADRs found finding(s) in ADR Quality. | +5.9 pts | Low | ADR Quality |
| Resolve the 5 Orphaned file finding(s) in Knowledge Freshness — start with OrderApplication.java, CartResource.java, SimpleFileBasedEventStore.java. | +4.9 pts | Low | Knowledge Freshness |
| Resolve the 6 No assertions finding(s) in Test Quality — start with OrderTest.java (2), OrderResourceTest.java, AccumulatedFeeTest.java. | +2.7 pts | Low | Test Quality |
| Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them. | +3.9 pts | Medium | Architecture documentation |
| Port the existing pipeline to a CI service that is still operating — the build and test steps are already specified — and remove the dead configuration and its badge so the repository stops advertising a gate that no longer exists. | +3.9 pts | Medium | CI/CD gates |
| Add a SAST step to CI running what this repository's stack ships: spotbugs with find-sec-bugs — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing. | +3.9 pts | Medium | Security & performance tooling |
| Resolve the 1 Orphaned files with no living knowledge finding(s) in Knowledge Freshness. | +1.4 pts | Low | Knowledge Freshness |
| Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href. | +2.6 pts | Medium | Keyboard semantics |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 6.1 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| REDACTED | 6.3 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| REDACTED | 6.9 | Mixed | Dependency Vulnerabilities: Medium CVE: REDACTED |
| REDACTED | 7.2 | Mixed | Dependency Vulnerabilities: High CVE: REDACTED |
| order-context-parent/order-command/src/test/java/se/citerus/cqrs/bookstore/ordercontext/order/domain/OrderTest.java | 7.8 | Mixed | Test Quality: No assertions: cannotPlaceAnOrderTwice |
| order-context-parent/publisher-contract-command/src/test/java/se/citerus/cqrs/bookstore/ordercontext/resource/PublisherContractResourceTest.java | 8.2 | Near-clean | Explicit Debt: TodoComment |
| order-context-parent/order-application/src/main/java/se/citerus/cqrs/bookstore/ordercontext/application/OrderApplication.java | 8.5 | Near-clean | Code Duplication: Duplicated block (7 lines × 2) |
| cqrs-lib/src/main/java/se/citerus/cqrs/bookstore/TransportObject.java | 8.5 | Near-clean | Code Duplication: Duplicated block (23 lines × 2) |
| cqrs-lib/src/main/java/se/citerus/cqrs/bookstore/command/Command.java | 8.5 | Near-clean | Code Duplication: Duplicated block (27 lines × 2) |
| order-context-parent/order-query/src/main/java/se/citerus/cqrs/bookstore/ordercontext/client/productcatalog/ProductCatalogClient.java | 8.5 | Near-clean | Code Duplication: Duplicated block (12 lines × 2) |
| order-context-parent/order-command/src/test/java/se/citerus/cqrs/bookstore/ordercontext/resource/OrderResourceTest.java | 8.5 | Near-clean | Test Quality: No assertions: testCreateOrderRequest |
| order-context-parent/publisher-contract-command/src/test/java/se/citerus/cqrs/bookstore/ordercontext/publishercontract/domain/AccumulatedFeeTest.java | 8.5 | Near-clean | Test Quality: No assertions: feeCannotBeNegative |
| order-context-parent/publisher-contract-command/src/test/java/se/citerus/cqrs/bookstore/ordercontext/publishercontract/domain/PublisherContractTest.java | 8.5 | Near-clean | Test Quality: No assertions: testCannotRegisterTwice |
| shopping-context/src/test/java/se/citerus/cqrs/bookstore/shopping/resource/CartResourceTest.java | 8.5 | Near-clean | Test Quality: No assertions: shouldClearCart |
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, 48 of 59 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Canine Code Analyzer duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 | ✓ deterministic |
Run transparency — what happened this run
- D8 Code Coverage — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: test source is present (.java) 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 — `mvn jacoco:report`) 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 — `mvn jacoco:report`) 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.
- 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 — a Maven build resolved 15 artifact(s) (14 behind a shipped release, reported), but the build resolved only part of the graph, so this dimension's own question is only partly answered. 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. Every one of the 5 significant source file(s) was last meaningfully changed so long ago that no living knowledge remains, so there is no concentration to measure — the bus factor is not scored. This is not a clean bill: nobody currently holds working knowledge of this code (see D34 Knowledge Freshness).
- D19 Documentation Quality — 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. 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.
- D23 Boundary Type-Coupling — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This kind measured 0/40 valid on a seeded held-out sample of its rows on 98 C# repositories (docs/plans/deterministic-engine/adjudication/P5c-D23-units.md, "Version 1 ON MAIN"): the noise rows were dependencies on layer folders, shared cores and grouping folders read as contexts. By the pre-registered fallback (PREREGISTRATION v37) it publishes no row until version 4 passes its gate. The candidates are counted here, not reported as findings, and the score does not include them.
- D24 Comment Value — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
- AXB1 Runtime evidence locked — no reproducible boot — 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. Subject: 2 markup document(s) — HTML, Razor, JSX, Vue, Svelte or server templates. The Runtime Evidence tier boots an app only via docker-compose, an Aspire AppHost, a Dockerfile, an npm dev script, a web service's own toolchain entry point (cargo, go, dotnet, Python, Spring Boot), or an Android app's own Gradle wrapper (run on an emulator); an Apple or Flutter app needs a host it lacks. None applied, so no live runtime a11y/egress/header evidence was collected. You can widen what we reach: add a docker-compose.yml (or an Aspire AppHost) that brings the app up with its dependencies. We then boot it in an isolated sandbox and gathers real runtime evidence — you change nothing in your pipeline (no CI step, no SDK).
- C1 Data Protection — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These personal data controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks personal data controls.
- C2 Access Controls — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These authorization controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks authorization controls.
- C3 Audit Trail — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These audit controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks audit controls.
- C4 Data Retention — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These retention controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks retention controls.
- C5 Data-Subject Rights — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These data-subject rights controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks data-subject rights controls.
- DM8 Value-object opportunities — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check finds primitive parameters that travel together through several signatures of the domain (a missing value object). Its deterministic rule has not yet shown 95 % precision on adjudicated rows, so the clumps it finds are counted here and not published as findings, and the card carries no score. That is a limit of the analyzer, not a finding about your code.
- 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 Java 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.
- P5 DR & Backup — 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. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
- X1 Async correctness — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Python, Dart, Ruby, Scala, Rust and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala, Rust or Kotlin 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.
- X12 Unreachable branch — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Python, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala or Kotlin 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.
- X13 Undrained process stream — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Python, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala or Kotlin 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.
- X17 Uncapped recursion over a caller-supplied document — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Python, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala or Kotlin 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.
- D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
- D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
- D11 Test Reliability: Flakiness is inferred from history/markers — we run the suite once (for coverage), not the repeated runs under varied conditions that reveal nondeterminism, so a flaky test never recorded as failing is invisible here.
- D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
- D23 Boundary Type-Coupling: Boundary leakage is detected from type references across detected contexts — leaks that flow through primitives, serialization or shared infrastructure may not surface as a typed reference.
- D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
- D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- 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.
- 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.
- AC2 Forms & labels: Label association is read from static markup — a label wired up at runtime (JS-set aria-labelledby, framework-injected ids) reads as missing, a present label says nothing about whether its text is correct. A known UI-library field component (e.g. a JSX <TextField>) is now checked conservatively — flagged only when it carries NO label/aria-label/aria-labelledby/id/name — but wrapper/context-labelled libraries (Chakra/Radix FormControl+FormLabel) aren't statically visible (possible false positive) and non-JSX lowercased components are still skipped. A click handler on a plain element is now asked for a name too (it is a control the author declared), but the subtree test that answers it is deliberately generous: any DYNAMIC text expression in the subtree counts as a name, so an icon chosen by a ternary ({cond ? <IconA/> : <IconB/>}) reads as named, and a glyph component from a library the icon-import list does not know still names its parent. A clean result is "no unlabelled control found", not a labelling proof.
- AC3 Page structure: Page structure is read from the static markup tree — landmarks, headings and lang injected at runtime aren't seen, heading ORDER is checked structurally (not against the rendered visual hierarchy), and lang/title/main fire only on full documents, never partials, and the data-table check sees header-cell presence (a <th> exists), not whether each header correctly associates with its cells. Static readiness, not conformance.
- AC4 Keyboard semantics: Keyboard semantics are inferred from markup attributes — interactivity wired purely in script, focus managed at runtime, and component-level handlers are invisible. A clean result means "no static keyboard-trap shape", not a keyboard-operability proof.
- AC6 Visual & motion safety: Contrast and motion safety are PARTIAL by construction — literal colours (hex/rgb/hsl/named) in inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS top-level declarations are read (same-rule/same-element colour+background pairs only); computed/runtime/theme colour, external-CDN stylesheets, CSS-in-JS dynamic (${…}) and nested-selector colours, cross-element pairs and image contrast stay out of reach, so a clean result is bounded by what the static CSS itself shows.
- AC7 A11y enforcement: Enforcement is scored from in-repo config/CI evidence only — an a11y gate enforced in external tooling with no in-repo trace can't be credited, and a configured linter is presence, not proof the rules actually run or block a merge.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- DM4 Rich vs anemic model: Behaviour is detected as state mutation inside a method body — a method that enforces an invariant by validating-and-throwing without mutating reads as a query, and mutation delegated through an interface the scan can't resolve isn't credited; entities with zero public properties still drop out of the population. It detects that state changes, not whether the rule is correct.
- DM6 Domain ↔ infrastructure boundary: Infrastructure reached through a hand-rolled wrapper, a domain-named facade, reflection, or a string-keyed service locator resolves to a non-infra type and isn't seen; the body scan is symbol resolution over syntax, not full dataflow. A clean result means "no resolved infra reference in a domain body", not a proof of purity.
- 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
4 duplicated block group(s) detected.
What to do
- Resolve the 1 Duplicated block (7 lines × 2) finding(s) in Code Duplication — start with OrderApplication.java. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Duplicated block (23 lines × 2) finding(s) in Code Duplication — start with TransportObject.java. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Duplicated block (27 lines × 2) finding(s) in Code Duplication — start with Command.java. — One of this dimension's main actionable groups (1 warning-level).
D5 · Coupling
9 production modules (Maven), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; 1 module(s) off the main sequence.
D6 · Cohesion (LCOM4)
0 of 23 classes have LCOM4 above 3.
D9 · Test Distribution
31 test methods: 31 unit, 0 integration, 0 BDD, 0 e2e.
D10 · Test Quality
0 skipped, 6 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 31 tests.
What to do
- Resolve the 6 No assertions finding(s) in Test Quality — start with OrderTest.java (2), OrderResourceTest.java, AccumulatedFeeTest.java. — One of this dimension's main actionable groups (6 warning-level).
D11 · Test Reliability
0 flaky across 1 measured tier(s). Java/Kotlin (repository root, Maven): measured (0 flaky).
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D14 · License Compliance
0 of 1 declared JVM dependency artifact(s) use a banned license. Licences were resolved from the POMs Maven Central publishes, over the coordinates this repository's 11 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. 38 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.
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window.
D17 · Explicit Debt
1 deducted task-comment markers across 2155 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.
What to do
- Resolve the 1 TodoComment finding(s) in Explicit Debt — start with PublisherContractResourceTest.java. — One of this dimension's main actionable groups (1 warning-level).
D20 · ADR Quality
No architecture decision records were found.
What to do
- Resolve the 1 No ADRs found finding(s) in ADR Quality. — One of this dimension's main actionable groups (1 recommendation-level).
D23 · Boundary Type-Coupling
2 domain type(s) cross context boundaries across 2 contexts; they are measured and withheld (not published, not scored). Contexts: domain, ordercontext.
D26 · Project Cohesion
0 of 9 build units (Maven) flagged as possibly oversized/incoherent.
D27 · Navigability
67 % of calls cross a namespace and 25 % go through an interface, but 100 % of collaborators are co-located — so following a call takes several hops. Baseline: small — navigation cost is tolerated.
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
7 finding(s): 0 critical, 0 high, 7 medium, 0 low.
What to do
- Resolve the 7 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (4), REDACTED (3). — One of this dimension's main actionable groups (7 warning-level).
D30 · Dependency Vulnerabilities
3 finding(s): 0 critical, 1 high, 2 medium, 0 low.
What to do
- Resolve the 1 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 2 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (2). — One of this dimension's main actionable groups (2 warning-level).
D34 · Knowledge Freshness
5 of 5 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is order-context-parent/order-application/src/main/java/se/citerus/cqrs/bookstore/ordercontext/application/OrderApplication.java. Counted over 5 of the 93 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
What to do
- Resolve the 5 Orphaned file finding(s) in Knowledge Freshness — start with OrderApplication.java, CartResource.java, SimpleFileBasedEventStore.java. — One of this dimension's main actionable groups (5 recommendation-level).
- Resolve the 1 Orphaned files with no living knowledge finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
D35 · Change Coupling
No strong hidden change-coupling between production files.
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 1 platform declaration(s) and 11 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
AC2 · Forms & labels
- A fieldset groups related controls but has no <legend> to name the group. Add a <legend> as its first child — or, if the group already has a visible caption beside it (or the fieldset is there only to disable its subtree and carries no group box), point aria-labelledby at that caption's id instead, which names the group without rendering a second one. — REDACTED:58
What to do
- Give every control a programmatic label (a <label for> / wrapping <label> / aria-label) and every button text — a placeholder is not a label.
AC3 · Page structure
- The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en"). (×2) — REDACTED:2, REDACTED:2
- No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>. (×2) — REDACTED:2, REDACTED:2
- Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one. — REDACTED:33
What to do
- Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh.
AC4 · Keyboard semantics
- An <a> with no href, role or tabindex isn't focusable or keyboard-activatable. Give it a real href, or use a <button> for an action. — REDACTED:14
What to do
- Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href.
AC6 · Visual & motion safety
AC7 · A11y enforcement
- No accessibility enforcement found — no accessibility linting at author time and no automated accessibility check in tests or CI. Add your UI toolkit's own accessibility assertion to the test suite (Flutter `meetsGuideline`, Espresso `AccessibilityChecks`, XCTest `performAccessibilityAudit`), then gate that test in the pipeline. What was searched, so you can tell an absence from a miss: the 2 markup file(s) this pass actually assessed, the linter configuration checked in beside them, and this repository's test and CI files — matched by name against the accessibility checkers this dimension carries. An audit run outside the repository, a hosted scanner, or a check whose name is not one of those, is not seen here.
What to do
- Enforce accessibility in the toolchain your project already uses: assert accessibility in your UI test suite with your toolkit's own matcher (Flutter `meetsGuideline`, Espresso `AccessibilityChecks`, XCTest `performAccessibilityAudit`), then gate that test in CI so a regression blocks the merge.
AX10 · Code composition
AX3 · Project dependency cycles
AX4 · Dependency direction
AX5 · Architecture & structure
AX6 · Interface segregation
DM1 · Aggregate boundaries
DM10 · One transaction, one aggregate
DM11 · Constructible invalid state
DM12 · Ambient inputs in the domain
DM4 · Rich vs anemic model
DM5 · Encapsulated state
DM6 · Domain ↔ infrastructure boundary
DM9 · Scattered domain decisions
IC1 · Incompleteness & stubs
- A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something. (×4) — order-context-parent/order-application/src/test/java/se/citerus/cqrs/bookstore/ordercontext/application/TestContractDataImporter.java:14, order-context-parent/order-application/src/test/java/se/citerus/cqrs/bookstore/ordercontext/application/TestHttpClient.java:17, product-catalog-context/src/test/java/se/citerus/cqrs/bookstore/productcatalog/application/TestHttpClient.java:17, …
What to do
- Clear the softer debt: re-enable or delete @Disabled/@Ignore tests, decide whether each empty method or UnsupportedOperationException is deliberate (and say so in a comment), and replace @SuppressWarnings("all") with targeted, justified suppressions.
M1 · Documentation (README)
- The root README is 28 words, against a bar of 120. Of the three newcomer-critical sections this check looks for by heading, in the README and in the repository documents it links, it found no a build/run or getting-started section, no a testing section, no an architecture or project-map section. Sections are matched on HEADING text only, so material written under a heading this check does not recognise — or with no heading at all — is not seen and this row may understate what the document covers. — README.md:1
What to do
- Expand the README with getting-started, architecture overview and a project map.
- Add a build/run (quick start) section to the root README — the first thing a newcomer needs.
- Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
- Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
- Describe the projects a newcomer cannot place from the root README: 10 of 10 have no README of their own, in their folder or in their family's project (`cqrs-lib`, `order-context-parent`, `product-catalog-context`, `shopping-context`, `order-context-parent/eventbus-contract` and 5 more).
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
- No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
- Add a C4 context/container diagram (Structurizr, PlantUML or Mermaid) or an architecture.md overview.
M3 · Folder & project structure
P1 · CI/CD gates
- The pipeline is well-formed, but the only CI definition is `.travis.yml`, and its `README.md` build badge still points at `travis-ci.org` — a service shut down in June 2021. No other CI is configured in this repository, so nothing has been building or testing changes here since that shutdown — the steps below describe a gate that is not running. Porting it is mostly mechanical: the build and test commands already written here are what a replacement pipeline would run.
What to do
- Port the existing pipeline to a CI service that is still operating — the build and test steps are already specified — and remove the dead configuration and its badge so the repository stops advertising a gate that no longer exists.
P2 · Observability
P3 · Security & performance tooling
- No static application security testing detected. For this repository's stack, add spotbugs with find-sec-bugs (or `semgrep --config=auto`, which runs on any language) as a CI step. What was searched, so you can tell an absence from a miss: the 1 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.
What to do
- Add a SAST step to CI running what this repository's stack ships: spotbugs with find-sec-bugs — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing.
- Enable Dependabot/Renovate or a dependency-review gate.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P6 · Release Hygiene
- No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
What to do
- Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.
S1 · Web-Security Posture
- `http://code.jquery.com/jquery-1.9.1.min.js` is executed by this page with no Subresource Integrity. Whoever can answer that request — the CDN, anyone who compromises it, anyone on the network path — runs arbitrary script in this page's origin, with its session. The URL also names no version, so it resolves to whatever that origin serves at fetch time — the executed bytes can change with nobody touching this repository. 5 such include(s) across the repository's markup. — REDACTED:73
What to do
- Pin third-party scripts and verify them: name an exact version in the URL and add an `integrity="sha384-…"` hash alongside `crossorigin="anonymous"` (both are required — an integrity hash on a cross-origin script without `crossorigin` is not evaluated, it blocks the script). Where the vendor ships a continuously-updated loader and publishes no stable hash (tag managers, analytics, chat widgets), Subresource Integrity is not available: constrain it instead with a `Content-Security-Policy` that names the exact origins allowed to execute, and drop the script from the pages that do not need it. Where the page is shipped inside a package that others host, prefer vendoring the asset and serving it from the app’s own origin, so no consumer inherits a third-party dependency they did not choose.
X14 · Bypassable address classification
X15 · Unvalidated length from an untrusted reader
X16 · Unfloored truncation loop
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
X24 · Document value interpolated into markup unescaped
X25 · Inert configuration knob
X26 · Unsynchronised callback handoff
X27 · Collection changed while being enumerated
X28 · Index access outside its own emptiness guard
X29 · Per-element action decided by a fixed element
X3 · Exception handling
X30 · Support guard that admits what it rejects
X4 · Structured logging
- `debug` at line 49 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — shopping-context/src/main/java/se/citerus/cqrs/bookstore/shopping/resource/CartResource.java:49
- `info` at line 53 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — shopping-context/src/main/java/se/citerus/cqrs/bookstore/shopping/resource/CartResource.java:53
- `info` at line 32 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — order-context-parent/sagas/src/main/java/se/citerus/cqrs/bookstore/ordercontext/saga/PurchaseRegistrationSaga.java:32
- `info` at line 35 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. (×2) — order-context-parent/publisher-contract-command/src/main/java/se/citerus/cqrs/bookstore/ordercontext/resource/PublisherContractResource.java:35, order-context-parent/order-command/src/main/java/se/citerus/cqrs/bookstore/ordercontext/resource/OrderResource.java:35
- `info` at line 33 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — order-context-parent/order-query/src/main/java/se/citerus/cqrs/bookstore/ordercontext/query/orderlist/OrderListDenormalizer.java:33
- `info` at line 50 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — order-context-parent/order-query/src/main/java/se/citerus/cqrs/bookstore/ordercontext/query/orderlist/OrderListDenormalizer.java:50
- `info` at line 43 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — order-context-parent/order-command/src/main/java/se/citerus/cqrs/bookstore/ordercontext/resource/OrderResource.java:43
- `info` at line 64 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — order-context-parent/order-application/src/main/java/se/citerus/cqrs/bookstore/ordercontext/application/OrderApplication.java:64
What to do
- Interpolated log message defeats structured logging
X5 · Nullable reference types
- 0/38 of this repository's Java package directories are under a non-null default: a `package-info.java` declaring `@NullMarked` (JSpecify) or `@NonNullApi`, `@ParametersAreNonnullByDefault`, `@NonNullByDefault`, `@DefaultQualifier(NonNull.class)`; a `module-info.java` declaring `@NullMarked`; every type in it `@NullMarked`; or a build that runs NullAway with the package in `AnnotatedPackages`, or the Checker Framework's `NullnessChecker`. Elsewhere every reference admits null and no checker warns on the dereference that throws a `NullPointerException`.
What to do
- Declare the default where Java declares it: `@NullMarked` (org.jspecify.annotations) in each package's `package-info.java`, or once in `module-info.java`, and run NullAway (Error Prone) or the Checker Framework so the declaration is enforced. Then annotate the real exceptions `@Nullable` and resolve the suppressions rather than adding to them: a `@SuppressWarnings("NullAway")` or `castToNonNull(x)` on a value the checker could show to be null is a `NullPointerException` waiting for the path that makes it true — where the value genuinely cannot be null, say something the checker can see instead (a null check, `Objects.requireNonNull`, a non-null field initialised in the constructor).
WCAG coverage — what static analysis assessed
| Dimension | WCAG 2.2 A/AA criteria | Coverage |
|---|---|---|
| AC2 · Forms & labels | 1.3.1, 3.3.2, 4.1.2 | Partial signal |
| AC3 · Page structure | 1.4.4, 2.2.1, 2.4.1, 2.4.2, 3.1.1, 4.1.2 | Partial signal |
| AC4 · Keyboard semantics | 2.1.1, 2.4.3 | Partial signal |
| AC6 · Visual & motion safety | 1.4.3, 2.4.7 | Partial — literal CSS only |
| AC7 · A11y enforcement | enforcement — no page criterion | Enforcement posture (process) |
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 61% | Adequate — gated by X4, X5 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 92% | Exemplary | Solid. |
| Maturity | 37% | Weak — gated by D34, M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 33% | Weak — gated by P1, P3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 84% | Strong | Solid. |
| Domain Modelling | 100% | Exemplary | Strongest area. |
| Accessibility | 39% | Weak — gated by AC4 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
Not evidenced — 5 control(s) we could not find positive evidence for
- C3 Audit Trail — Not assessed: these audit controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks audit controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- C4 Data Retention — Not assessed: these retention controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks retention controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- C5 Data-Subject Rights — Not assessed: these data-subject rights controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks data-subject rights controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- P4 Deployment & Rollback — not evidenced — no deploy/rollback/approval signal in the repo; absence of evidence is not evidence of a manual release
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 54 check(s) not relevant to this codebase
- AC1 Text alternatives — No image/media element found in the parsed markup — AC1 not applicable here.
- AC5 ARIA correctness — No ARIA usage found in the parsed markup — AC5 not applicable here.
- AX1 Captive dependencies — Not applicable: this repository's Java imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's.
- AX2 Stateful singletons — No container singleton was found, so there is no shared instance for concurrent requests to race on. No class in this Java code is a Spring, JSR-330 or CDI singleton bean.
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AX8 Test isolation — no test/production split to check
- AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
- AXB1 Runtime evidence locked — no reproducible boot — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- C1 Data Protection — Not assessed: these personal data controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks personal data controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- C2 Access Controls — Not assessed: these authorization controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks authorization controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- D12 Dependency Hygiene — Not scored — a Maven build resolved 15 artifact(s) (14 behind a shipped release, reported), but the build resolved only part of the graph, so this dimension's own question is only partly answered. NOT a finding that these dependencies are current or healthy.
- D16 Bus Factor — dormant codebase — no living knowledge left to concentrate
- D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
- D19 Documentation Quality — D19 reads .NET projects and npm packages as units; 11 folder(s) declared by REDACTED were not judged for an overview, an example or the map.
- D21 Naming Consistency — Naming consistency is measured on C# and TypeScript only; Java, html not measured.
- D22 Internal API Consistency — The exposed public-API surface could not be collected — no C#/VB projects loaded.
- D24 Comment Value — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only — this repository's production source is .java, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D25 ADR Conformance — no ADRs to check
- D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
- D32 Data Compliance (PII/GDPR) — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
- D36 Supply-chain Provenance & Signing — The CI pipeline publishes no artifact — no package publish, container push or release with files to download. Supply-chain provenance, signing and an SBOM describe a PUBLISHED artifact for the people who obtain it, so there is nothing to attest here; a deployment of the service itself publishes nothing for anyone else to verify. Add them to the release pipeline when this repo starts publishing artifacts (a package, a container image, or a release with downloadable files). Build integrity and workflow-token hygiene are reported below: they describe what the CI runs and the token it runs with, neither of which is affected by whether the pipeline ships an artifact.
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- D39 IL Efficiency — D39 measures the IL emitted by a .NET build; this repository has no .NET solution or project files, so the dimension does not apply.
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
- D8 Code Coverage — Coverage not included — suite not readable by the collector
- DM2 Strongly-typed ids — no id-bearing domain types detected — strongly-typed-id adoption not assessable
- DM3 Integration-event coupling — no integration events detected — coupling check not applicable
- DM7 Repository granularity — no repository abstraction detected (e.g. uses a document session)
- DM8 Value-object opportunities — not scored — the deterministic rule found 0 candidate clump(s); its rows are withheld until it has a measured precision of 95 % (a sample of fewer than 10 rows cannot show one)
- ED1 Event-Driven — not scored — this repository shows 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.
- M4 Documentation accuracy — Not applicable: the 1 current-state document(s) make no claim of a kind M4 checks.
- P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
- P7 Outbound HTTP resilience — no outbound HTTP usage detected — no HTTP client call or construction in the JVM source (service entry point: shopping-context/src/main/java/se/citerus/cqrs/bookstore/shopping/resource/CartResource.java:26 (@Path())
- P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
- P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (JaCoCo XML — `mvn jacoco:report`) 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 REDACTED, 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.
- X1 Async correctness — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X10 Duplicated predicate — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X12 Unreachable branch — 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
- X13 Undrained process stream — 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
- X17 Uncapped recursion over a caller-supplied document — 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
- X2 Cancellation propagation — no C# was loaded; this repository's Java was read, and no request in it can be cancelled by a caller — a Java request off Android takes no token: it is cancelled through the handle it returns (Future.cancel, Call.cancel, a Disposable), ambiently (io.grpc.Context) or by interrupting its thread, not through a parameter
- X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X7 Silent fallback defaults — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
Critical — 3 finding(s)
- <html> without a lang REDACTED:2
- <html> without a lang REDACTED:2
- REDACTED
Serious — 28 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- No assertions: cannotPlaceAnOrderTwice order-context-parent/order-command/src/test/java/se/citerus/cqrs/bookstore/ordercontext/order/domain/OrderTest.java:59
- No assertions: requireOrderLinesWhenPlacingAnOrder order-context-parent/order-command/src/test/java/se/citerus/cqrs/bookstore/ordercontext/order/domain/OrderTest.java:53
- No assertions: testCreateOrderRequest order-context-parent/order-command/src/test/java/se/citerus/cqrs/bookstore/ordercontext/resource/OrderResourceTest.java:39
- No assertions: feeCannotBeNegative order-context-parent/publisher-contract-command/src/test/java/se/citerus/cqrs/bookstore/ordercontext/publishercontract/domain/AccumulatedFeeTest.java:51
- No assertions: testCannotRegisterTwice order-context-parent/publisher-contract-command/src/test/java/se/citerus/cqrs/bookstore/ordercontext/publishercontract/domain/PublisherContractTest.java:36
- No assertions: shouldClearCart shopping-context/src/test/java/se/citerus/cqrs/bookstore/shopping/resource/CartResourceTest.java:115
- Page without a main landmark REDACTED:2
- Page without a main landmark REDACTED:2
- REDACTED
- REDACTED
- <fieldset> without a <legend> REDACTED:58
- Heading level jumps from h2 to h5 REDACTED:33
- Anchor without href REDACTED:14
- Accessibility enforcement below the top rung
- TodoComment order-context-parent/publisher-contract-command/src/test/java/se/citerus/cqrs/bookstore/ordercontext/resource/PublisherContractResourceTest.java:5
- Duplicated block (7 lines × 2) order-context-parent/order-application/src/main/java/se/citerus/cqrs/bookstore/ordercontext/application/OrderApplication.java:87
- Duplicated block (23 lines × 2) cqrs-lib/src/main/java/se/citerus/cqrs/bookstore/TransportObject.java:1
- Duplicated block (27 lines × 2) cqrs-lib/src/main/java/se/citerus/cqrs/bookstore/command/Command.java:1
- Duplicated block (12 lines × 2) order-context-parent/order-query/src/main/java/se/citerus/cqrs/bookstore/ordercontext/client/productcatalog/ProductCatalogClient.java:11
- CI pipeline targets a decommissioned service
- Third-party script without Subresource Integrity REDACTED:73
Minor — 27 finding(s)
- Interpolated log message defeats structured logging shopping-context/src/main/java/se/citerus/cqrs/bookstore/shopping/resource/CartResource.java:49
- Interpolated log message defeats structured logging shopping-context/src/main/java/se/citerus/cqrs/bookstore/shopping/resource/CartResource.java:53
- Interpolated log message defeats structured logging order-context-parent/sagas/src/main/java/se/citerus/cqrs/bookstore/ordercontext/saga/PurchaseRegistrationSaga.java:32
- Interpolated log message defeats structured logging order-context-parent/publisher-contract-command/src/main/java/se/citerus/cqrs/bookstore/ordercontext/resource/PublisherContractResource.java:35
- Interpolated log message defeats structured logging order-context-parent/order-query/src/main/java/se/citerus/cqrs/bookstore/ordercontext/query/orderlist/OrderListDenormalizer.java:33
- Interpolated log message defeats structured logging order-context-parent/order-query/src/main/java/se/citerus/cqrs/bookstore/ordercontext/query/orderlist/OrderListDenormalizer.java:50
- Interpolated log message defeats structured logging order-context-parent/order-command/src/main/java/se/citerus/cqrs/bookstore/ordercontext/resource/OrderResource.java:35
- Interpolated log message defeats structured logging order-context-parent/order-command/src/main/java/se/citerus/cqrs/bookstore/ordercontext/resource/OrderResource.java:43
- Interpolated log message defeats structured logging order-context-parent/order-application/src/main/java/se/citerus/cqrs/bookstore/ordercontext/application/OrderApplication.java:64
- Orphaned file order-context-parent/order-application/src/main/java/se/citerus/cqrs/bookstore/ordercontext/application/OrderApplication.java:1
- Orphaned file shopping-context/src/main/java/se/citerus/cqrs/bookstore/shopping/resource/CartResource.java:1
- Orphaned file order-context-parent/order-application/src/main/java/se/citerus/cqrs/bookstore/ordercontext/application/infrastructure/SimpleFileBasedEventStore.java:1
- Orphaned file order-context-parent/order-command/src/main/java/se/citerus/cqrs/bookstore/ordercontext/order/domain/Order.java:1
- Orphaned file order-context-parent/order-query/src/main/java/se/citerus/cqrs/bookstore/ordercontext/query/orderlist/OrderListDenormalizer.java:1
- Disabled test order-context-parent/order-application/src/test/java/se/citerus/cqrs/bookstore/ordercontext/application/TestContractDataImporter.java:14
- Disabled test order-context-parent/order-application/src/test/java/se/citerus/cqrs/bookstore/ordercontext/application/TestHttpClient.java:17
- Disabled test product-catalog-context/src/test/java/se/citerus/cqrs/bookstore/productcatalog/application/TestHttpClient.java:17
- Disabled test product-catalog-context/src/test/java/se/citerus/cqrs/bookstore/productcatalog/application/TestProductDataImporter.java:14
- No ADRs found
- Orphaned files with no living knowledge
- REDACTED
- Thin README README.md:1
- No ADRs
- No architecture diagram/doc
- No SAST
- No changelog
- Java packages are not null-marked everywhere
Minor — 1 finding(s)
- Off the main sequence: eventbus-contract
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-41f30ee555514bd785757ca4226d6dc3/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-41f30ee555514bd785757ca4226d6dc3/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 . | 7 | 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 . | 3 | artifacts/raw/osv-scanner.json |
| D31 · IaC & Container Security | trivy | — | trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan. | 0 | — |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. | 0 | — |
| D37 · Vulnerability-disclosure Policy | disclosure | — | disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . | 0 | artifacts/raw/osv-scanner.json |