Executive summary
ttulka/ddd-example-ecommerce-microservices falls short of our standard for a template or a sample, held back most by its Accessibility lens, the interface's usability with a keyboard or assistive technology. It scores 37 out of 100 and is rated Weak, and 21 of its 26 critical findings are security problems in its servers and containers.
Accessibility, at 23, is the weakest lens and counts most in the score. The best first steps are making the controls keyboard-usable and fixing focus, motion and contrast, each worth about 6 points. Raising Accessibility to 58 would lift the score to about 47.
Twenty-one settings leave the servers or containers unsafe. One control can't be used without a mouse, and two form fields can't be read by a screen reader. Making the controls work with a keyboard, correcting the unsafe settings and labelling the form fields would close these risks. The page that doesn't say its language needs its language set.
The product code is 3,639 lines, about €6,300 to rebuild.
If Accessibility rose from 23 to 58, the lowest score rated Strong, the score would rise from 37 to about 47.
New since the last survey: 1 finding
- Test Quality · No assertions (empty test): application_starts shipping/dispatching/application/src/test/java/com/ttulka/ecommerce/shipping/dispatching/DispatchingApplicationTest.java
Fixed since the last survey: 1 finding
- Test Quality · No assertions: application_starts shipping/dispatching/application/src/test/java/com/ttulka/ecommerce/shipping/dispatching/DispatchingApplicationTest.java
Rebuild cost: about €6,300 · Estimate
| Cost to rebuild | €2,100 to €11,000, for 35 to 111 hours of work, under 0.1 person-years for one engineer |
|---|---|
| Difficulty of the problem | Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.7 at a score of 37. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it. |
| Size | Small: 3,639 lines of product code |
| What it is not | Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one. |
Top priorities
Diagnosis: what the measurements show together
Architecture: which parts of the code depend on which
| uses → | 1 com.ttulka.ecommerce | 2 com.ttulka.ecommerce.common.events | 3 com.ttulka.ecommerce.common.primitives | 4 com.ttulka.ecommerce.portal | 5 com.ttulka.ecommerce.portal.web | 6 com.ttulka.ecommerce.sales.catalog.category | 7 portal.web.src.main.resources.static.js | 8 portal.web.src.main.resources.static.js.portal | 9 com.ttulka.ecommerce.billing.payment | 10 com.ttulka.ecommerce.common.integration.messaging | 11 com.ttulka.ecommerce.sales.cart.item | 12 com.ttulka.ecommerce.sales.catalog.product | 13 com.ttulka.ecommerce.sales.order.item | 14 com.ttulka.ecommerce.shipping.delivery | 15 com.ttulka.ecommerce.shipping.dispatching | 16 com.ttulka.ecommerce.warehouse | 17 com.ttulka.ecommerce.billing.payment.jdbc | 18 com.ttulka.ecommerce.billing.payment.rest | 19 com.ttulka.ecommerce.sales.cart | 20 com.ttulka.ecommerce.sales.catalog | 21 com.ttulka.ecommerce.sales.order | 22 com.ttulka.ecommerce.shipping.delivery.jdbc | 23 com.ttulka.ecommerce.shipping.delivery.listeners | 24 com.ttulka.ecommerce.shipping.delivery.rest | 25 com.ttulka.ecommerce.shipping.dispatching.jdbc | 26 com.ttulka.ecommerce.warehouse.jdbc | 27 com.ttulka.ecommerce.warehouse.rest | 28 com.ttulka.ecommerce.billing.payment.listeners | 29 com.ttulka.ecommerce.sales.cart.jdbc | 30 com.ttulka.ecommerce.sales.cart.rest | 31 com.ttulka.ecommerce.sales.catalog.jdbc | 32 com.ttulka.ecommerce.sales.catalog.rest | 33 com.ttulka.ecommerce.sales.order.jdbc | 34 com.ttulka.ecommerce.sales.order.rest | 35 com.ttulka.ecommerce.shipping.dispatching.listeners | 36 com.ttulka.ecommerce.warehouse.listeners |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 com.ttulka.ecommerce | ||||||||||||||||||||||||||||||||||||
| 2 com.ttulka.ecommerce.common.events | ||||||||||||||||||||||||||||||||||||
| 3 com.ttulka.ecommerce.common.primitives | ||||||||||||||||||||||||||||||||||||
| 4 com.ttulka.ecommerce.portal | ||||||||||||||||||||||||||||||||||||
| 5 com.ttulka.ecommerce.portal.web | ||||||||||||||||||||||||||||||||||||
| 6 com.ttulka.ecommerce.sales.catalog.category | ||||||||||||||||||||||||||||||||||||
| 7 portal.web.src.main.resources.static.js | ||||||||||||||||||||||||||||||||||||
| 8 portal.web.src.main.resources.static.js.portal | ||||||||||||||||||||||||||||||||||||
| 9 com.ttulka.ecommerce.billing.payment | 1 | 2 | ||||||||||||||||||||||||||||||||||
| 10 com.ttulka.ecommerce.common.integration.messaging | 5 | |||||||||||||||||||||||||||||||||||
| 11 com.ttulka.ecommerce.sales.cart.item | 2 | |||||||||||||||||||||||||||||||||||
| 12 com.ttulka.ecommerce.sales.catalog.product | 1 | 1 | ||||||||||||||||||||||||||||||||||
| 13 com.ttulka.ecommerce.sales.order.item | 1 | |||||||||||||||||||||||||||||||||||
| 14 com.ttulka.ecommerce.shipping.delivery | 1 | |||||||||||||||||||||||||||||||||||
| 15 com.ttulka.ecommerce.shipping.dispatching | 1 | |||||||||||||||||||||||||||||||||||
| 16 com.ttulka.ecommerce.warehouse | 2 | |||||||||||||||||||||||||||||||||||
| 17 com.ttulka.ecommerce.billing.payment.jdbc | 5 | 2 | 9 | |||||||||||||||||||||||||||||||||
| 18 com.ttulka.ecommerce.billing.payment.rest | 1 | |||||||||||||||||||||||||||||||||||
| 19 com.ttulka.ecommerce.sales.cart | 4 | |||||||||||||||||||||||||||||||||||
| 20 com.ttulka.ecommerce.sales.catalog | 4 | 4 | ||||||||||||||||||||||||||||||||||
| 21 com.ttulka.ecommerce.sales.order | 1 | 2 | 2 | |||||||||||||||||||||||||||||||||
| 22 com.ttulka.ecommerce.shipping.delivery.jdbc | 4 | 21 | ||||||||||||||||||||||||||||||||||
| 23 com.ttulka.ecommerce.shipping.delivery.listeners | 1 | 1 | ||||||||||||||||||||||||||||||||||
| 24 com.ttulka.ecommerce.shipping.delivery.rest | 2 | |||||||||||||||||||||||||||||||||||
| 25 com.ttulka.ecommerce.shipping.dispatching.jdbc | 2 | 6 | ||||||||||||||||||||||||||||||||||
| 26 com.ttulka.ecommerce.warehouse.jdbc | 2 | 10 | ||||||||||||||||||||||||||||||||||
| 27 com.ttulka.ecommerce.warehouse.rest | 1 | |||||||||||||||||||||||||||||||||||
| 28 com.ttulka.ecommerce.billing.payment.listeners | 1 | 1 | ||||||||||||||||||||||||||||||||||
| 29 com.ttulka.ecommerce.sales.cart.jdbc | 2 | 5 | ||||||||||||||||||||||||||||||||||
| 30 com.ttulka.ecommerce.sales.cart.rest | 2 | |||||||||||||||||||||||||||||||||||
| 31 com.ttulka.ecommerce.sales.catalog.jdbc | 2 | 16 | 14 | 3 | ||||||||||||||||||||||||||||||||
| 32 com.ttulka.ecommerce.sales.catalog.rest | 1 | 3 | ||||||||||||||||||||||||||||||||||
| 33 com.ttulka.ecommerce.sales.order.jdbc | 4 | 3 | 4 | 10 | ||||||||||||||||||||||||||||||||
| 34 com.ttulka.ecommerce.sales.order.rest | 1 | 1 | ||||||||||||||||||||||||||||||||||
| 35 com.ttulka.ecommerce.shipping.dispatching.listeners | 1 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||
| 36 com.ttulka.ecommerce.warehouse.listeners | 1 | 2 | 1 |
9→2 com.ttulka.ecommerce.billing.payment uses com.ttulka.ecommerce.common.events✕
- Connections
- 1 pair of types, where a type in com.ttulka.ecommerce.billing.payment uses a type in com.ttulka.ecommerce.common.events.
- The types involved
com.ttulka.ecommerce.billing.payment.PaymentCollected→com.ttulka.ecommerce.common.events.DomainEvent
- Direction
- com.ttulka.ecommerce.billing.payment uses com.ttulka.ecommerce.common.events, so a change to com.ttulka.ecommerce.common.events can break com.ttulka.ecommerce.billing.payment, while a change to com.ttulka.ecommerce.billing.payment can't break com.ttulka.ecommerce.common.events.
- Position
- Below the diagonal: com.ttulka.ecommerce.billing.payment uses a module listed above it, which is the healthy direction.
9→3 com.ttulka.ecommerce.billing.payment uses com.ttulka.ecommerce.common.primitives✕
- Connections
- 2 pairs of types, where a type in com.ttulka.ecommerce.billing.payment uses a type in com.ttulka.ecommerce.common.primitives.
- The types involved
com.ttulka.ecommerce.billing.payment.CollectPayment→com.ttulka.ecommerce.common.primitives.Moneycom.ttulka.ecommerce.billing.payment.Payment→com.ttulka.ecommerce.common.primitives.Money
- Direction
- com.ttulka.ecommerce.billing.payment uses com.ttulka.ecommerce.common.primitives, so a change to com.ttulka.ecommerce.common.primitives can break com.ttulka.ecommerce.billing.payment, while a change to com.ttulka.ecommerce.billing.payment can't break com.ttulka.ecommerce.common.primitives.
- Position
- Below the diagonal: com.ttulka.ecommerce.billing.payment uses a module listed above it, which is the healthy direction.
10→2 com.ttulka.ecommerce.common.integration.messaging uses com.ttulka.ecommerce.common.events✕
- Connections
- 5 pairs of types, where a type in com.ttulka.ecommerce.common.integration.messaging uses a type in com.ttulka.ecommerce.common.events.
- The types involved
com.ttulka.ecommerce.common.integration.messaging.DomainEventWrapper→com.ttulka.ecommerce.common.events.DomainEventcom.ttulka.ecommerce.common.integration.messaging.RabbitMqConfig→com.ttulka.ecommerce.common.events.EventPublishercom.ttulka.ecommerce.common.integration.messaging.RedisBrokerConfig→com.ttulka.ecommerce.common.events.DomainEventcom.ttulka.ecommerce.common.integration.messaging.RedisBrokerConfig→com.ttulka.ecommerce.common.events.EventPublishercom.ttulka.ecommerce.common.integration.messaging.SpringMessagingConfig→com.ttulka.ecommerce.common.events.EventPublisher
- Direction
- com.ttulka.ecommerce.common.integration.messaging uses com.ttulka.ecommerce.common.events, so a change to com.ttulka.ecommerce.common.events can break com.ttulka.ecommerce.common.integration.messaging, while a change to com.ttulka.ecommerce.common.integration.messaging can't break com.ttulka.ecommerce.common.events.
- Position
- Below the diagonal: com.ttulka.ecommerce.common.integration.messaging uses a module listed above it, which is the healthy direction.
11→3 com.ttulka.ecommerce.sales.cart.item uses com.ttulka.ecommerce.common.primitives✕
- Connections
- 2 pairs of types, where a type in com.ttulka.ecommerce.sales.cart.item uses a type in com.ttulka.ecommerce.common.primitives.
- The types involved
com.ttulka.ecommerce.sales.cart.item.CartItem→com.ttulka.ecommerce.common.primitives.Moneycom.ttulka.ecommerce.sales.cart.item.CartItem→com.ttulka.ecommerce.common.primitives.Quantity
- Direction
- com.ttulka.ecommerce.sales.cart.item uses com.ttulka.ecommerce.common.primitives, so a change to com.ttulka.ecommerce.common.primitives can break com.ttulka.ecommerce.sales.cart.item, while a change to com.ttulka.ecommerce.sales.cart.item can't break com.ttulka.ecommerce.common.primitives.
- Position
- Below the diagonal: com.ttulka.ecommerce.sales.cart.item uses a module listed above it, which is the healthy direction.
12→3 com.ttulka.ecommerce.sales.catalog.product uses com.ttulka.ecommerce.common.primitives✕
- Connections
- 1 pair of types, where a type in com.ttulka.ecommerce.sales.catalog.product uses a type in com.ttulka.ecommerce.common.primitives.
- The types involved
com.ttulka.ecommerce.sales.catalog.product.Product→com.ttulka.ecommerce.common.primitives.Money
- Direction
- com.ttulka.ecommerce.sales.catalog.product uses com.ttulka.ecommerce.common.primitives, so a change to com.ttulka.ecommerce.common.primitives can break com.ttulka.ecommerce.sales.catalog.product, while a change to com.ttulka.ecommerce.sales.catalog.product can't break com.ttulka.ecommerce.common.primitives.
- Position
- Below the diagonal: com.ttulka.ecommerce.sales.catalog.product uses a module listed above it, which is the healthy direction.
12→6 com.ttulka.ecommerce.sales.catalog.product uses com.ttulka.ecommerce.sales.catalog.category✕
- Connections
- 1 pair of types, where a type in com.ttulka.ecommerce.sales.catalog.product uses a type in com.ttulka.ecommerce.sales.catalog.category.
- The types involved
com.ttulka.ecommerce.sales.catalog.product.Product→com.ttulka.ecommerce.sales.catalog.category.CategoryId
- Direction
- com.ttulka.ecommerce.sales.catalog.product uses com.ttulka.ecommerce.sales.catalog.category, so a change to com.ttulka.ecommerce.sales.catalog.category can break com.ttulka.ecommerce.sales.catalog.product, while a change to com.ttulka.ecommerce.sales.catalog.product can't break com.ttulka.ecommerce.sales.catalog.category.
- Position
- Below the diagonal: com.ttulka.ecommerce.sales.catalog.product uses a module listed above it, which is the healthy direction.
13→3 com.ttulka.ecommerce.sales.order.item uses com.ttulka.ecommerce.common.primitives✕
- Connections
- 1 pair of types, where a type in com.ttulka.ecommerce.sales.order.item uses a type in com.ttulka.ecommerce.common.primitives.
- The types involved
com.ttulka.ecommerce.sales.order.item.OrderItem→com.ttulka.ecommerce.common.primitives.Quantity
- Direction
- com.ttulka.ecommerce.sales.order.item uses com.ttulka.ecommerce.common.primitives, so a change to com.ttulka.ecommerce.common.primitives can break com.ttulka.ecommerce.sales.order.item, while a change to com.ttulka.ecommerce.sales.order.item can't break com.ttulka.ecommerce.common.primitives.
- Position
- Below the diagonal: com.ttulka.ecommerce.sales.order.item uses a module listed above it, which is the healthy direction.
14→2 com.ttulka.ecommerce.shipping.delivery uses com.ttulka.ecommerce.common.events✕
- Connections
- 1 pair of types, where a type in com.ttulka.ecommerce.shipping.delivery uses a type in com.ttulka.ecommerce.common.events.
- The types involved
com.ttulka.ecommerce.shipping.delivery.DeliveryPrepared→com.ttulka.ecommerce.common.events.DomainEvent
- Direction
- com.ttulka.ecommerce.shipping.delivery uses com.ttulka.ecommerce.common.events, so a change to com.ttulka.ecommerce.common.events can break com.ttulka.ecommerce.shipping.delivery, while a change to com.ttulka.ecommerce.shipping.delivery can't break com.ttulka.ecommerce.common.events.
- Position
- Below the diagonal: com.ttulka.ecommerce.shipping.delivery uses a module listed above it, which is the healthy direction.
15→2 com.ttulka.ecommerce.shipping.dispatching uses com.ttulka.ecommerce.common.events✕
- Connections
- 1 pair of types, where a type in com.ttulka.ecommerce.shipping.dispatching uses a type in com.ttulka.ecommerce.common.events.
- The types involved
com.ttulka.ecommerce.shipping.dispatching.DeliveryDispatched→com.ttulka.ecommerce.common.events.DomainEvent
- Direction
- com.ttulka.ecommerce.shipping.dispatching uses com.ttulka.ecommerce.common.events, so a change to com.ttulka.ecommerce.common.events can break com.ttulka.ecommerce.shipping.dispatching, while a change to com.ttulka.ecommerce.shipping.dispatching can't break com.ttulka.ecommerce.common.events.
- Position
- Below the diagonal: com.ttulka.ecommerce.shipping.dispatching uses a module listed above it, which is the healthy direction.
16→2 com.ttulka.ecommerce.warehouse uses com.ttulka.ecommerce.common.events✕
- Connections
- 2 pairs of types, where a type in com.ttulka.ecommerce.warehouse uses a type in com.ttulka.ecommerce.common.events.
- The types involved
com.ttulka.ecommerce.warehouse.GoodsFetched→com.ttulka.ecommerce.common.events.DomainEventcom.ttulka.ecommerce.warehouse.GoodsMissed→com.ttulka.ecommerce.common.events.DomainEvent
- Direction
- com.ttulka.ecommerce.warehouse uses com.ttulka.ecommerce.common.events, so a change to com.ttulka.ecommerce.common.events can break com.ttulka.ecommerce.warehouse, while a change to com.ttulka.ecommerce.warehouse can't break com.ttulka.ecommerce.common.events.
- Position
- Below the diagonal: com.ttulka.ecommerce.warehouse uses a module listed above it, which is the healthy direction.
17→2 com.ttulka.ecommerce.billing.payment.jdbc uses com.ttulka.ecommerce.common.events✕
- Connections
- 5 pairs of types, where a type in com.ttulka.ecommerce.billing.payment.jdbc uses a type in com.ttulka.ecommerce.common.events.
- The types involved
com.ttulka.ecommerce.billing.payment.jdbc.CollectPaymentJdbc→com.ttulka.ecommerce.common.events.EventPublishercom.ttulka.ecommerce.billing.payment.jdbc.FindPaymentsJdbc→com.ttulka.ecommerce.common.events.EventPublishercom.ttulka.ecommerce.billing.payment.jdbc.PaymentJdbc→com.ttulka.ecommerce.common.events.EventPublishercom.ttulka.ecommerce.billing.payment.jdbc.PaymentJdbcConfig→com.ttulka.ecommerce.common.events.EventPublishercom.ttulka.ecommerce.billing.payment.jdbc.PaymentsJdbc→com.ttulka.ecommerce.common.events.EventPublisher
- Direction
- com.ttulka.ecommerce.billing.payment.jdbc uses com.ttulka.ecommerce.common.events, so a change to com.ttulka.ecommerce.common.events can break com.ttulka.ecommerce.billing.payment.jdbc, while a change to com.ttulka.ecommerce.billing.payment.jdbc can't break com.ttulka.ecommerce.common.events.
- Position
- Below the diagonal: com.ttulka.ecommerce.billing.payment.jdbc uses a module listed above it, which is the healthy direction.
17→3 com.ttulka.ecommerce.billing.payment.jdbc uses com.ttulka.ecommerce.common.primitives✕
- Connections
- 2 pairs of types, where a type in com.ttulka.ecommerce.billing.payment.jdbc uses a type in com.ttulka.ecommerce.common.primitives.
- The types involved
com.ttulka.ecommerce.billing.payment.jdbc.CollectPaymentJdbc→com.ttulka.ecommerce.common.primitives.Moneycom.ttulka.ecommerce.billing.payment.jdbc.PaymentJdbc→com.ttulka.ecommerce.common.primitives.Money
- Direction
- com.ttulka.ecommerce.billing.payment.jdbc uses com.ttulka.ecommerce.common.primitives, so a change to com.ttulka.ecommerce.common.primitives can break com.ttulka.ecommerce.billing.payment.jdbc, while a change to com.ttulka.ecommerce.billing.payment.jdbc can't break com.ttulka.ecommerce.common.primitives.
- Position
- Below the diagonal: com.ttulka.ecommerce.billing.payment.jdbc uses a module listed above it, which is the healthy direction.
17→9 com.ttulka.ecommerce.billing.payment.jdbc uses com.ttulka.ecommerce.billing.payment✕
- Connections
- 9 pairs of types, where a type in com.ttulka.ecommerce.billing.payment.jdbc uses a type in com.ttulka.ecommerce.billing.payment.
- The types involved
com.ttulka.ecommerce.billing.payment.jdbc.CollectPaymentJdbc→com.ttulka.ecommerce.billing.payment.CollectPaymentcom.ttulka.ecommerce.billing.payment.jdbc.CollectPaymentJdbc→com.ttulka.ecommerce.billing.payment.ReferenceIdcom.ttulka.ecommerce.billing.payment.jdbc.FindPaymentsJdbc→com.ttulka.ecommerce.billing.payment.FindPaymentscom.ttulka.ecommerce.billing.payment.jdbc.FindPaymentsJdbc→com.ttulka.ecommerce.billing.payment.Paymentscom.ttulka.ecommerce.billing.payment.jdbc.PaymentJdbc→com.ttulka.ecommerce.billing.payment.Paymentcom.ttulka.ecommerce.billing.payment.jdbc.PaymentJdbc→com.ttulka.ecommerce.billing.payment.PaymentIdcom.ttulka.ecommerce.billing.payment.jdbc.PaymentJdbc→com.ttulka.ecommerce.billing.payment.ReferenceIdcom.ttulka.ecommerce.billing.payment.jdbc.PaymentsJdbc→com.ttulka.ecommerce.billing.payment.Paymentcom.ttulka.ecommerce.billing.payment.jdbc.PaymentsJdbc→com.ttulka.ecommerce.billing.payment.Payments
- Direction
- com.ttulka.ecommerce.billing.payment.jdbc uses com.ttulka.ecommerce.billing.payment, so a change to com.ttulka.ecommerce.billing.payment can break com.ttulka.ecommerce.billing.payment.jdbc, while a change to com.ttulka.ecommerce.billing.payment.jdbc can't break com.ttulka.ecommerce.billing.payment.
- Position
- Below the diagonal: com.ttulka.ecommerce.billing.payment.jdbc uses a module listed above it, which is the healthy direction.
18→9 com.ttulka.ecommerce.billing.payment.rest uses com.ttulka.ecommerce.billing.payment✕
- Connections
- 1 pair of types, where a type in com.ttulka.ecommerce.billing.payment.rest uses a type in com.ttulka.ecommerce.billing.payment.
- The types involved
com.ttulka.ecommerce.billing.payment.rest.PaymentController→com.ttulka.ecommerce.billing.payment.FindPayments
- Direction
- com.ttulka.ecommerce.billing.payment.rest uses com.ttulka.ecommerce.billing.payment, so a change to com.ttulka.ecommerce.billing.payment can break com.ttulka.ecommerce.billing.payment.rest, while a change to com.ttulka.ecommerce.billing.payment.rest can't break com.ttulka.ecommerce.billing.payment.
- Position
- Below the diagonal: com.ttulka.ecommerce.billing.payment.rest uses a module listed above it, which is the healthy direction.
19→11 com.ttulka.ecommerce.sales.cart uses com.ttulka.ecommerce.sales.cart.item✕
- Connections
- 4 pairs of types, where a type in com.ttulka.ecommerce.sales.cart uses a type in com.ttulka.ecommerce.sales.cart.item.
- The types involved
com.ttulka.ecommerce.sales.cart.Cart→com.ttulka.ecommerce.sales.cart.item.CartItemcom.ttulka.ecommerce.sales.cart.Cart→com.ttulka.ecommerce.sales.cart.item.ProductIdcom.ttulka.ecommerce.sales.cart.ListCartItems→com.ttulka.ecommerce.sales.cart.item.CartItemcom.ttulka.ecommerce.sales.cart.RemoveCartItem→com.ttulka.ecommerce.sales.cart.item.ProductId
- Direction
- com.ttulka.ecommerce.sales.cart uses com.ttulka.ecommerce.sales.cart.item, so a change to com.ttulka.ecommerce.sales.cart.item can break com.ttulka.ecommerce.sales.cart, while a change to com.ttulka.ecommerce.sales.cart can't break com.ttulka.ecommerce.sales.cart.item.
- Position
- Below the diagonal: com.ttulka.ecommerce.sales.cart uses a module listed above it, which is the healthy direction.
20→6 com.ttulka.ecommerce.sales.catalog uses com.ttulka.ecommerce.sales.catalog.category✕
- Connections
- 4 pairs of types, where a type in com.ttulka.ecommerce.sales.catalog uses a type in com.ttulka.ecommerce.sales.catalog.category.
- The types involved
com.ttulka.ecommerce.sales.catalog.FindCategories→com.ttulka.ecommerce.sales.catalog.category.Categoriescom.ttulka.ecommerce.sales.catalog.FindCategories→com.ttulka.ecommerce.sales.catalog.category.Categorycom.ttulka.ecommerce.sales.catalog.FindCategories→com.ttulka.ecommerce.sales.catalog.category.CategoryIdcom.ttulka.ecommerce.sales.catalog.FindProductsFromCategory→com.ttulka.ecommerce.sales.catalog.category.Uri
- Direction
- com.ttulka.ecommerce.sales.catalog uses com.ttulka.ecommerce.sales.catalog.category, so a change to com.ttulka.ecommerce.sales.catalog.category can break com.ttulka.ecommerce.sales.catalog, while a change to com.ttulka.ecommerce.sales.catalog can't break com.ttulka.ecommerce.sales.catalog.category.
- Position
- Below the diagonal: com.ttulka.ecommerce.sales.catalog uses a module listed above it, which is the healthy direction.
20→12 com.ttulka.ecommerce.sales.catalog uses com.ttulka.ecommerce.sales.catalog.product✕
- Connections
- 4 pairs of types, where a type in com.ttulka.ecommerce.sales.catalog uses a type in com.ttulka.ecommerce.sales.catalog.product.
- The types involved
com.ttulka.ecommerce.sales.catalog.FindProducts→com.ttulka.ecommerce.sales.catalog.product.Productcom.ttulka.ecommerce.sales.catalog.FindProducts→com.ttulka.ecommerce.sales.catalog.product.ProductIdcom.ttulka.ecommerce.sales.catalog.FindProducts→com.ttulka.ecommerce.sales.catalog.product.Productscom.ttulka.ecommerce.sales.catalog.FindProductsFromCategory→com.ttulka.ecommerce.sales.catalog.product.Products
- Direction
- com.ttulka.ecommerce.sales.catalog uses com.ttulka.ecommerce.sales.catalog.product, so a change to com.ttulka.ecommerce.sales.catalog.product can break com.ttulka.ecommerce.sales.catalog, while a change to com.ttulka.ecommerce.sales.catalog can't break com.ttulka.ecommerce.sales.catalog.product.
- Position
- Below the diagonal: com.ttulka.ecommerce.sales.catalog uses a module listed above it, which is the healthy direction.
21→2 com.ttulka.ecommerce.sales.order uses com.ttulka.ecommerce.common.events✕
- Connections
- 1 pair of types, where a type in com.ttulka.ecommerce.sales.order uses a type in com.ttulka.ecommerce.common.events.
- The types involved
com.ttulka.ecommerce.sales.order.OrderPlaced→com.ttulka.ecommerce.common.events.DomainEvent
- Direction
- com.ttulka.ecommerce.sales.order uses com.ttulka.ecommerce.common.events, so a change to com.ttulka.ecommerce.common.events can break com.ttulka.ecommerce.sales.order, while a change to com.ttulka.ecommerce.sales.order can't break com.ttulka.ecommerce.common.events.
- Position
- Below the diagonal: com.ttulka.ecommerce.sales.order uses a module listed above it, which is the healthy direction.
21→3 com.ttulka.ecommerce.sales.order uses com.ttulka.ecommerce.common.primitives✕
- Connections
- 2 pairs of types, where a type in com.ttulka.ecommerce.sales.order uses a type in com.ttulka.ecommerce.common.primitives.
- The types involved
com.ttulka.ecommerce.sales.order.Order→com.ttulka.ecommerce.common.primitives.Moneycom.ttulka.ecommerce.sales.order.PlaceOrder→com.ttulka.ecommerce.common.primitives.Money
- Direction
- com.ttulka.ecommerce.sales.order uses com.ttulka.ecommerce.common.primitives, so a change to com.ttulka.ecommerce.common.primitives can break com.ttulka.ecommerce.sales.order, while a change to com.ttulka.ecommerce.sales.order can't break com.ttulka.ecommerce.common.primitives.
- Position
- Below the diagonal: com.ttulka.ecommerce.sales.order uses a module listed above it, which is the healthy direction.
21→13 com.ttulka.ecommerce.sales.order uses com.ttulka.ecommerce.sales.order.item✕
- Connections
- 2 pairs of types, where a type in com.ttulka.ecommerce.sales.order uses a type in com.ttulka.ecommerce.sales.order.item.
- The types involved
com.ttulka.ecommerce.sales.order.Order→com.ttulka.ecommerce.sales.order.item.OrderItemcom.ttulka.ecommerce.sales.order.PlaceOrder→com.ttulka.ecommerce.sales.order.item.OrderItem
- Direction
- com.ttulka.ecommerce.sales.order uses com.ttulka.ecommerce.sales.order.item, so a change to com.ttulka.ecommerce.sales.order.item can break com.ttulka.ecommerce.sales.order, while a change to com.ttulka.ecommerce.sales.order can't break com.ttulka.ecommerce.sales.order.item.
- Position
- Below the diagonal: com.ttulka.ecommerce.sales.order uses a module listed above it, which is the healthy direction.
22→2 com.ttulka.ecommerce.shipping.delivery.jdbc uses com.ttulka.ecommerce.common.events✕
- Connections
- 4 pairs of types, where a type in com.ttulka.ecommerce.shipping.delivery.jdbc uses a type in com.ttulka.ecommerce.common.events.
- The types involved
com.ttulka.ecommerce.shipping.delivery.jdbc.DeliveryJdbc→com.ttulka.ecommerce.common.events.EventPublishercom.ttulka.ecommerce.shipping.delivery.jdbc.DeliveryJdbcConfig→com.ttulka.ecommerce.common.events.EventPublishercom.ttulka.ecommerce.shipping.delivery.jdbc.FindDeliveriesJdbc→com.ttulka.ecommerce.common.events.EventPublishercom.ttulka.ecommerce.shipping.delivery.jdbc.PrepareDeliveryJdbc→com.ttulka.ecommerce.common.events.EventPublisher
- Direction
- com.ttulka.ecommerce.shipping.delivery.jdbc uses com.ttulka.ecommerce.common.events, so a change to com.ttulka.ecommerce.common.events can break com.ttulka.ecommerce.shipping.delivery.jdbc, while a change to com.ttulka.ecommerce.shipping.delivery.jdbc can't break com.ttulka.ecommerce.common.events.
- Position
- Below the diagonal: com.ttulka.ecommerce.shipping.delivery.jdbc uses a module listed above it, which is the healthy direction.
22→14 com.ttulka.ecommerce.shipping.delivery.jdbc uses com.ttulka.ecommerce.shipping.delivery✕
- Connections
- 21 pairs of types, where a type in com.ttulka.ecommerce.shipping.delivery.jdbc uses a type in com.ttulka.ecommerce.shipping.delivery.
- The types involved
com.ttulka.ecommerce.shipping.delivery.jdbc.DeliveryInfosJdbc→com.ttulka.ecommerce.shipping.delivery.DeliveryInfocom.ttulka.ecommerce.shipping.delivery.jdbc.DeliveryInfosJdbc→com.ttulka.ecommerce.shipping.delivery.DeliveryInfoscom.ttulka.ecommerce.shipping.delivery.jdbc.DeliveryJdbc→com.ttulka.ecommerce.shipping.delivery.Addresscom.ttulka.ecommerce.shipping.delivery.jdbc.DeliveryJdbc→com.ttulka.ecommerce.shipping.delivery.Deliverycom.ttulka.ecommerce.shipping.delivery.jdbc.DeliveryJdbc→com.ttulka.ecommerce.shipping.delivery.DeliveryIdcom.ttulka.ecommerce.shipping.delivery.jdbc.DeliveryJdbc→com.ttulka.ecommerce.shipping.delivery.OrderIdcom.ttulka.ecommerce.shipping.delivery.jdbc.DeliveryJdbcConfig→com.ttulka.ecommerce.shipping.delivery.FindDeliveriescom.ttulka.ecommerce.shipping.delivery.jdbc.DispatchDeliveryJdbc→com.ttulka.ecommerce.shipping.delivery.DispatchDeliverycom.ttulka.ecommerce.shipping.delivery.jdbc.DispatchDeliveryJdbc→com.ttulka.ecommerce.shipping.delivery.FindDeliveriescom.ttulka.ecommerce.shipping.delivery.jdbc.DispatchDeliveryJdbc→com.ttulka.ecommerce.shipping.delivery.OrderIdcom.ttulka.ecommerce.shipping.delivery.jdbc.FindDeliveriesJdbc→com.ttulka.ecommerce.shipping.delivery.Deliverycom.ttulka.ecommerce.shipping.delivery.jdbc.FindDeliveriesJdbc→com.ttulka.ecommerce.shipping.delivery.DeliveryInfoscom.ttulka.ecommerce.shipping.delivery.jdbc.FindDeliveriesJdbc→com.ttulka.ecommerce.shipping.delivery.FindDeliveriescom.ttulka.ecommerce.shipping.delivery.jdbc.FindDeliveriesJdbc→com.ttulka.ecommerce.shipping.delivery.OrderIdcom.ttulka.ecommerce.shipping.delivery.jdbc.PrepareDeliveryJdbc→com.ttulka.ecommerce.shipping.delivery.Addresscom.ttulka.ecommerce.shipping.delivery.jdbc.PrepareDeliveryJdbc→com.ttulka.ecommerce.shipping.delivery.OrderIdcom.ttulka.ecommerce.shipping.delivery.jdbc.PrepareDeliveryJdbc→com.ttulka.ecommerce.shipping.delivery.PrepareDeliverycom.ttulka.ecommerce.shipping.delivery.jdbc.UnknownDelivery→com.ttulka.ecommerce.shipping.delivery.Addresscom.ttulka.ecommerce.shipping.delivery.jdbc.UnknownDelivery→com.ttulka.ecommerce.shipping.delivery.Deliverycom.ttulka.ecommerce.shipping.delivery.jdbc.UnknownDelivery→com.ttulka.ecommerce.shipping.delivery.DeliveryIdcom.ttulka.ecommerce.shipping.delivery.jdbc.UnknownDelivery→com.ttulka.ecommerce.shipping.delivery.OrderId
- Direction
- com.ttulka.ecommerce.shipping.delivery.jdbc uses com.ttulka.ecommerce.shipping.delivery, so a change to com.ttulka.ecommerce.shipping.delivery can break com.ttulka.ecommerce.shipping.delivery.jdbc, while a change to com.ttulka.ecommerce.shipping.delivery.jdbc can't break com.ttulka.ecommerce.shipping.delivery.
- Position
- Below the diagonal: com.ttulka.ecommerce.shipping.delivery.jdbc uses a module listed above it, which is the healthy direction.
23→14 com.ttulka.ecommerce.shipping.delivery.listeners uses com.ttulka.ecommerce.shipping.delivery✕
- Connections
- 1 pair of types, where a type in com.ttulka.ecommerce.shipping.delivery.listeners uses a type in com.ttulka.ecommerce.shipping.delivery.
- The types involved
com.ttulka.ecommerce.shipping.delivery.listeners.DeliveryDispatchedListener→com.ttulka.ecommerce.shipping.delivery.DispatchDelivery
- Direction
- com.ttulka.ecommerce.shipping.delivery.listeners uses com.ttulka.ecommerce.shipping.delivery, so a change to com.ttulka.ecommerce.shipping.delivery can break com.ttulka.ecommerce.shipping.delivery.listeners, while a change to com.ttulka.ecommerce.shipping.delivery.listeners can't break com.ttulka.ecommerce.shipping.delivery.
- Position
- Below the diagonal: com.ttulka.ecommerce.shipping.delivery.listeners uses a module listed above it, which is the healthy direction.
23→15 com.ttulka.ecommerce.shipping.delivery.listeners uses com.ttulka.ecommerce.shipping.dispatching✕
- Connections
- 1 pair of types, where a type in com.ttulka.ecommerce.shipping.delivery.listeners uses a type in com.ttulka.ecommerce.shipping.dispatching.
- The types involved
com.ttulka.ecommerce.shipping.delivery.listeners.DeliveryDispatchedListener→com.ttulka.ecommerce.shipping.dispatching.DeliveryDispatched
- Direction
- com.ttulka.ecommerce.shipping.delivery.listeners uses com.ttulka.ecommerce.shipping.dispatching, so a change to com.ttulka.ecommerce.shipping.dispatching can break com.ttulka.ecommerce.shipping.delivery.listeners, while a change to com.ttulka.ecommerce.shipping.delivery.listeners can't break com.ttulka.ecommerce.shipping.dispatching.
- Position
- Below the diagonal: com.ttulka.ecommerce.shipping.delivery.listeners uses a module listed above it, which is the healthy direction.
24→14 com.ttulka.ecommerce.shipping.delivery.rest uses com.ttulka.ecommerce.shipping.delivery✕
- Connections
- 2 pairs of types, where a type in com.ttulka.ecommerce.shipping.delivery.rest uses a type in com.ttulka.ecommerce.shipping.delivery.
- The types involved
com.ttulka.ecommerce.shipping.delivery.rest.DeliveryController→com.ttulka.ecommerce.shipping.delivery.FindDeliveriescom.ttulka.ecommerce.shipping.delivery.rest.DeliveryController→com.ttulka.ecommerce.shipping.delivery.PrepareDelivery
- Direction
- com.ttulka.ecommerce.shipping.delivery.rest uses com.ttulka.ecommerce.shipping.delivery, so a change to com.ttulka.ecommerce.shipping.delivery can break com.ttulka.ecommerce.shipping.delivery.rest, while a change to com.ttulka.ecommerce.shipping.delivery.rest can't break com.ttulka.ecommerce.shipping.delivery.
- Position
- Below the diagonal: com.ttulka.ecommerce.shipping.delivery.rest uses a module listed above it, which is the healthy direction.
25→2 com.ttulka.ecommerce.shipping.dispatching.jdbc uses com.ttulka.ecommerce.common.events✕
- Connections
- 2 pairs of types, where a type in com.ttulka.ecommerce.shipping.dispatching.jdbc uses a type in com.ttulka.ecommerce.common.events.
- The types involved
com.ttulka.ecommerce.shipping.dispatching.jdbc.DispatchingJdbc→com.ttulka.ecommerce.common.events.EventPublishercom.ttulka.ecommerce.shipping.dispatching.jdbc.DispatchingJdbcConfig→com.ttulka.ecommerce.common.events.EventPublisher
- Direction
- com.ttulka.ecommerce.shipping.dispatching.jdbc uses com.ttulka.ecommerce.common.events, so a change to com.ttulka.ecommerce.common.events can break com.ttulka.ecommerce.shipping.dispatching.jdbc, while a change to com.ttulka.ecommerce.shipping.dispatching.jdbc can't break com.ttulka.ecommerce.common.events.
- Position
- Below the diagonal: com.ttulka.ecommerce.shipping.dispatching.jdbc uses a module listed above it, which is the healthy direction.
25→15 com.ttulka.ecommerce.shipping.dispatching.jdbc uses com.ttulka.ecommerce.shipping.dispatching✕
- Connections
- 6 pairs of types, where a type in com.ttulka.ecommerce.shipping.dispatching.jdbc uses a type in com.ttulka.ecommerce.shipping.dispatching.
- The types involved
com.ttulka.ecommerce.shipping.dispatching.jdbc.DispatchingJdbc→com.ttulka.ecommerce.shipping.dispatching.Dispatchingcom.ttulka.ecommerce.shipping.dispatching.jdbc.DispatchingJdbc→com.ttulka.ecommerce.shipping.dispatching.OrderIdcom.ttulka.ecommerce.shipping.dispatching.jdbc.DispatchingJdbcConfig→com.ttulka.ecommerce.shipping.dispatching.Dispatchingcom.ttulka.ecommerce.shipping.dispatching.jdbc.DispatchingSagaJdbc→com.ttulka.ecommerce.shipping.dispatching.Dispatchingcom.ttulka.ecommerce.shipping.dispatching.jdbc.DispatchingSagaJdbc→com.ttulka.ecommerce.shipping.dispatching.DispatchingSagacom.ttulka.ecommerce.shipping.dispatching.jdbc.DispatchingSagaJdbc→com.ttulka.ecommerce.shipping.dispatching.OrderId
- Direction
- com.ttulka.ecommerce.shipping.dispatching.jdbc uses com.ttulka.ecommerce.shipping.dispatching, so a change to com.ttulka.ecommerce.shipping.dispatching can break com.ttulka.ecommerce.shipping.dispatching.jdbc, while a change to com.ttulka.ecommerce.shipping.dispatching.jdbc can't break com.ttulka.ecommerce.shipping.dispatching.
- Position
- Below the diagonal: com.ttulka.ecommerce.shipping.dispatching.jdbc uses a module listed above it, which is the healthy direction.
26→2 com.ttulka.ecommerce.warehouse.jdbc uses com.ttulka.ecommerce.common.events✕
- Connections
- 2 pairs of types, where a type in com.ttulka.ecommerce.warehouse.jdbc uses a type in com.ttulka.ecommerce.common.events.
- The types involved
com.ttulka.ecommerce.warehouse.jdbc.GoodsFetchingJdbc→com.ttulka.ecommerce.common.events.EventPublishercom.ttulka.ecommerce.warehouse.jdbc.WarehouseJdbcConfig→com.ttulka.ecommerce.common.events.EventPublisher
- Direction
- com.ttulka.ecommerce.warehouse.jdbc uses com.ttulka.ecommerce.common.events, so a change to com.ttulka.ecommerce.common.events can break com.ttulka.ecommerce.warehouse.jdbc, while a change to com.ttulka.ecommerce.warehouse.jdbc can't break com.ttulka.ecommerce.common.events.
- Position
- Below the diagonal: com.ttulka.ecommerce.warehouse.jdbc uses a module listed above it, which is the healthy direction.
26→16 com.ttulka.ecommerce.warehouse.jdbc uses com.ttulka.ecommerce.warehouse✕
- Connections
- 10 pairs of types, where a type in com.ttulka.ecommerce.warehouse.jdbc uses a type in com.ttulka.ecommerce.warehouse.
- The types involved
com.ttulka.ecommerce.warehouse.jdbc.GoodsFetchingJdbc→com.ttulka.ecommerce.warehouse.FetchGoodscom.ttulka.ecommerce.warehouse.jdbc.GoodsFetchingJdbc→com.ttulka.ecommerce.warehouse.OrderIdcom.ttulka.ecommerce.warehouse.jdbc.GoodsFetchingJdbc→com.ttulka.ecommerce.warehouse.RemoveFetchedGoodscom.ttulka.ecommerce.warehouse.jdbc.GoodsFetchingJdbc→com.ttulka.ecommerce.warehouse.ToFetchcom.ttulka.ecommerce.warehouse.jdbc.GoodsFetchingJdbc→com.ttulka.ecommerce.warehouse.Warehousecom.ttulka.ecommerce.warehouse.jdbc.WarehouseJdbc→com.ttulka.ecommerce.warehouse.Amountcom.ttulka.ecommerce.warehouse.jdbc.WarehouseJdbc→com.ttulka.ecommerce.warehouse.InStockcom.ttulka.ecommerce.warehouse.jdbc.WarehouseJdbc→com.ttulka.ecommerce.warehouse.ProductIdcom.ttulka.ecommerce.warehouse.jdbc.WarehouseJdbc→com.ttulka.ecommerce.warehouse.Warehousecom.ttulka.ecommerce.warehouse.jdbc.WarehouseJdbcConfig→com.ttulka.ecommerce.warehouse.Warehouse
- Direction
- com.ttulka.ecommerce.warehouse.jdbc uses com.ttulka.ecommerce.warehouse, so a change to com.ttulka.ecommerce.warehouse can break com.ttulka.ecommerce.warehouse.jdbc, while a change to com.ttulka.ecommerce.warehouse.jdbc can't break com.ttulka.ecommerce.warehouse.
- Position
- Below the diagonal: com.ttulka.ecommerce.warehouse.jdbc uses a module listed above it, which is the healthy direction.
27→16 com.ttulka.ecommerce.warehouse.rest uses com.ttulka.ecommerce.warehouse✕
- Connections
- 1 pair of types, where a type in com.ttulka.ecommerce.warehouse.rest uses a type in com.ttulka.ecommerce.warehouse.
- The types involved
com.ttulka.ecommerce.warehouse.rest.WarehouseController→com.ttulka.ecommerce.warehouse.Warehouse
- Direction
- com.ttulka.ecommerce.warehouse.rest uses com.ttulka.ecommerce.warehouse, so a change to com.ttulka.ecommerce.warehouse can break com.ttulka.ecommerce.warehouse.rest, while a change to com.ttulka.ecommerce.warehouse.rest can't break com.ttulka.ecommerce.warehouse.
- Position
- Below the diagonal: com.ttulka.ecommerce.warehouse.rest uses a module listed above it, which is the healthy direction.
28→9 com.ttulka.ecommerce.billing.payment.listeners uses com.ttulka.ecommerce.billing.payment✕
- Connections
- 1 pair of types, where a type in com.ttulka.ecommerce.billing.payment.listeners uses a type in com.ttulka.ecommerce.billing.payment.
- The types involved
com.ttulka.ecommerce.billing.payment.listeners.OrderPlacedListener→com.ttulka.ecommerce.billing.payment.CollectPayment
- Direction
- com.ttulka.ecommerce.billing.payment.listeners uses com.ttulka.ecommerce.billing.payment, so a change to com.ttulka.ecommerce.billing.payment can break com.ttulka.ecommerce.billing.payment.listeners, while a change to com.ttulka.ecommerce.billing.payment.listeners can't break com.ttulka.ecommerce.billing.payment.
- Position
- Below the diagonal: com.ttulka.ecommerce.billing.payment.listeners uses a module listed above it, which is the healthy direction.
28→21 com.ttulka.ecommerce.billing.payment.listeners uses com.ttulka.ecommerce.sales.order✕
- Connections
- 1 pair of types, where a type in com.ttulka.ecommerce.billing.payment.listeners uses a type in com.ttulka.ecommerce.sales.order.
- The types involved
com.ttulka.ecommerce.billing.payment.listeners.OrderPlacedListener→com.ttulka.ecommerce.sales.order.OrderPlaced
- Direction
- com.ttulka.ecommerce.billing.payment.listeners uses com.ttulka.ecommerce.sales.order, so a change to com.ttulka.ecommerce.sales.order can break com.ttulka.ecommerce.billing.payment.listeners, while a change to com.ttulka.ecommerce.billing.payment.listeners can't break com.ttulka.ecommerce.sales.order.
- Position
- Below the diagonal: com.ttulka.ecommerce.billing.payment.listeners uses a module listed above it, which is the healthy direction.
29→11 com.ttulka.ecommerce.sales.cart.jdbc uses com.ttulka.ecommerce.sales.cart.item✕
- Connections
- 2 pairs of types, where a type in com.ttulka.ecommerce.sales.cart.jdbc uses a type in com.ttulka.ecommerce.sales.cart.item.
- The types involved
com.ttulka.ecommerce.sales.cart.jdbc.CartJdbc→com.ttulka.ecommerce.sales.cart.item.CartItemcom.ttulka.ecommerce.sales.cart.jdbc.CartJdbc→com.ttulka.ecommerce.sales.cart.item.ProductId
- Direction
- com.ttulka.ecommerce.sales.cart.jdbc uses com.ttulka.ecommerce.sales.cart.item, so a change to com.ttulka.ecommerce.sales.cart.item can break com.ttulka.ecommerce.sales.cart.jdbc, while a change to com.ttulka.ecommerce.sales.cart.jdbc can't break com.ttulka.ecommerce.sales.cart.item.
- Position
- Below the diagonal: com.ttulka.ecommerce.sales.cart.jdbc uses a module listed above it, which is the healthy direction.
29→19 com.ttulka.ecommerce.sales.cart.jdbc uses com.ttulka.ecommerce.sales.cart✕
- Connections
- 5 pairs of types, where a type in com.ttulka.ecommerce.sales.cart.jdbc uses a type in com.ttulka.ecommerce.sales.cart.
- The types involved
com.ttulka.ecommerce.sales.cart.jdbc.CartJdbc→com.ttulka.ecommerce.sales.cart.Cartcom.ttulka.ecommerce.sales.cart.jdbc.CartJdbc→com.ttulka.ecommerce.sales.cart.CartIdcom.ttulka.ecommerce.sales.cart.jdbc.RetrieveCartJdbc→com.ttulka.ecommerce.sales.cart.Cartcom.ttulka.ecommerce.sales.cart.jdbc.RetrieveCartJdbc→com.ttulka.ecommerce.sales.cart.CartIdcom.ttulka.ecommerce.sales.cart.jdbc.RetrieveCartJdbc→com.ttulka.ecommerce.sales.cart.RetrieveCart
- Direction
- com.ttulka.ecommerce.sales.cart.jdbc uses com.ttulka.ecommerce.sales.cart, so a change to com.ttulka.ecommerce.sales.cart can break com.ttulka.ecommerce.sales.cart.jdbc, while a change to com.ttulka.ecommerce.sales.cart.jdbc can't break com.ttulka.ecommerce.sales.cart.
- Position
- Below the diagonal: com.ttulka.ecommerce.sales.cart.jdbc uses a module listed above it, which is the healthy direction.
30→19 com.ttulka.ecommerce.sales.cart.rest uses com.ttulka.ecommerce.sales.cart✕
- Connections
- 2 pairs of types, where a type in com.ttulka.ecommerce.sales.cart.rest uses a type in com.ttulka.ecommerce.sales.cart.
- The types involved
com.ttulka.ecommerce.sales.cart.rest.CartController→com.ttulka.ecommerce.sales.cart.RetrieveCartcom.ttulka.ecommerce.sales.cart.rest.CartIdFromCookies→com.ttulka.ecommerce.sales.cart.CartId
- Direction
- com.ttulka.ecommerce.sales.cart.rest uses com.ttulka.ecommerce.sales.cart, so a change to com.ttulka.ecommerce.sales.cart can break com.ttulka.ecommerce.sales.cart.rest, while a change to com.ttulka.ecommerce.sales.cart.rest can't break com.ttulka.ecommerce.sales.cart.
- Position
- Below the diagonal: com.ttulka.ecommerce.sales.cart.rest uses a module listed above it, which is the healthy direction.
31→3 com.ttulka.ecommerce.sales.catalog.jdbc uses com.ttulka.ecommerce.common.primitives✕
- Connections
- 2 pairs of types, where a type in com.ttulka.ecommerce.sales.catalog.jdbc uses a type in com.ttulka.ecommerce.common.primitives.
- The types involved
com.ttulka.ecommerce.sales.catalog.jdbc.ProductJdbc→com.ttulka.ecommerce.common.primitives.Moneycom.ttulka.ecommerce.sales.catalog.jdbc.UnknownProduct→com.ttulka.ecommerce.common.primitives.Money
- Direction
- com.ttulka.ecommerce.sales.catalog.jdbc uses com.ttulka.ecommerce.common.primitives, so a change to com.ttulka.ecommerce.common.primitives can break com.ttulka.ecommerce.sales.catalog.jdbc, while a change to com.ttulka.ecommerce.sales.catalog.jdbc can't break com.ttulka.ecommerce.common.primitives.
- Position
- Below the diagonal: com.ttulka.ecommerce.sales.catalog.jdbc uses a module listed above it, which is the healthy direction.
31→6 com.ttulka.ecommerce.sales.catalog.jdbc uses com.ttulka.ecommerce.sales.catalog.category✕
- Connections
- 16 pairs of types, where a type in com.ttulka.ecommerce.sales.catalog.jdbc uses a type in com.ttulka.ecommerce.sales.catalog.category.
- The types involved
com.ttulka.ecommerce.sales.catalog.jdbc.CategoriesJdbc→com.ttulka.ecommerce.sales.catalog.category.Categoriescom.ttulka.ecommerce.sales.catalog.jdbc.CategoriesJdbc→com.ttulka.ecommerce.sales.catalog.category.Categorycom.ttulka.ecommerce.sales.catalog.jdbc.CategoryJdbc→com.ttulka.ecommerce.sales.catalog.category.Categorycom.ttulka.ecommerce.sales.catalog.jdbc.CategoryJdbc→com.ttulka.ecommerce.sales.catalog.category.CategoryIdcom.ttulka.ecommerce.sales.catalog.jdbc.CategoryJdbc→com.ttulka.ecommerce.sales.catalog.category.Titlecom.ttulka.ecommerce.sales.catalog.jdbc.CategoryJdbc→com.ttulka.ecommerce.sales.catalog.category.Uricom.ttulka.ecommerce.sales.catalog.jdbc.FindCategoriesJdbc→com.ttulka.ecommerce.sales.catalog.category.Categoriescom.ttulka.ecommerce.sales.catalog.jdbc.FindCategoriesJdbc→com.ttulka.ecommerce.sales.catalog.category.Categorycom.ttulka.ecommerce.sales.catalog.jdbc.FindCategoriesJdbc→com.ttulka.ecommerce.sales.catalog.category.CategoryIdcom.ttulka.ecommerce.sales.catalog.jdbc.FindProductsFromCategoryJdbc→com.ttulka.ecommerce.sales.catalog.category.Uricom.ttulka.ecommerce.sales.catalog.jdbc.ProductJdbc→com.ttulka.ecommerce.sales.catalog.category.CategoryIdcom.ttulka.ecommerce.sales.catalog.jdbc.UnknownCategory→com.ttulka.ecommerce.sales.catalog.category.Categorycom.ttulka.ecommerce.sales.catalog.jdbc.UnknownCategory→com.ttulka.ecommerce.sales.catalog.category.CategoryIdcom.ttulka.ecommerce.sales.catalog.jdbc.UnknownCategory→com.ttulka.ecommerce.sales.catalog.category.Titlecom.ttulka.ecommerce.sales.catalog.jdbc.UnknownCategory→com.ttulka.ecommerce.sales.catalog.category.Uricom.ttulka.ecommerce.sales.catalog.jdbc.UnknownProduct→com.ttulka.ecommerce.sales.catalog.category.CategoryId
- Direction
- com.ttulka.ecommerce.sales.catalog.jdbc uses com.ttulka.ecommerce.sales.catalog.category, so a change to com.ttulka.ecommerce.sales.catalog.category can break com.ttulka.ecommerce.sales.catalog.jdbc, while a change to com.ttulka.ecommerce.sales.catalog.jdbc can't break com.ttulka.ecommerce.sales.catalog.category.
- Position
- Below the diagonal: com.ttulka.ecommerce.sales.catalog.jdbc uses a module listed above it, which is the healthy direction.
31→12 com.ttulka.ecommerce.sales.catalog.jdbc uses com.ttulka.ecommerce.sales.catalog.product✕
- Connections
- 14 pairs of types, where a type in com.ttulka.ecommerce.sales.catalog.jdbc uses a type in com.ttulka.ecommerce.sales.catalog.product.
- The types involved
com.ttulka.ecommerce.sales.catalog.jdbc.FindProductsFromCategoryJdbc→com.ttulka.ecommerce.sales.catalog.product.Productscom.ttulka.ecommerce.sales.catalog.jdbc.FindProductsJdbc→com.ttulka.ecommerce.sales.catalog.product.Productcom.ttulka.ecommerce.sales.catalog.jdbc.FindProductsJdbc→com.ttulka.ecommerce.sales.catalog.product.ProductIdcom.ttulka.ecommerce.sales.catalog.jdbc.FindProductsJdbc→com.ttulka.ecommerce.sales.catalog.product.Productscom.ttulka.ecommerce.sales.catalog.jdbc.ProductJdbc→com.ttulka.ecommerce.sales.catalog.product.Descriptioncom.ttulka.ecommerce.sales.catalog.jdbc.ProductJdbc→com.ttulka.ecommerce.sales.catalog.product.Productcom.ttulka.ecommerce.sales.catalog.jdbc.ProductJdbc→com.ttulka.ecommerce.sales.catalog.product.ProductIdcom.ttulka.ecommerce.sales.catalog.jdbc.ProductJdbc→com.ttulka.ecommerce.sales.catalog.product.Titlecom.ttulka.ecommerce.sales.catalog.jdbc.ProductsJdbc→com.ttulka.ecommerce.sales.catalog.product.Productcom.ttulka.ecommerce.sales.catalog.jdbc.ProductsJdbc→com.ttulka.ecommerce.sales.catalog.product.Productscom.ttulka.ecommerce.sales.catalog.jdbc.UnknownProduct→com.ttulka.ecommerce.sales.catalog.product.Descriptioncom.ttulka.ecommerce.sales.catalog.jdbc.UnknownProduct→com.ttulka.ecommerce.sales.catalog.product.Productcom.ttulka.ecommerce.sales.catalog.jdbc.UnknownProduct→com.ttulka.ecommerce.sales.catalog.product.ProductIdcom.ttulka.ecommerce.sales.catalog.jdbc.UnknownProduct→com.ttulka.ecommerce.sales.catalog.product.Title
- Direction
- com.ttulka.ecommerce.sales.catalog.jdbc uses com.ttulka.ecommerce.sales.catalog.product, so a change to com.ttulka.ecommerce.sales.catalog.product can break com.ttulka.ecommerce.sales.catalog.jdbc, while a change to com.ttulka.ecommerce.sales.catalog.jdbc can't break com.ttulka.ecommerce.sales.catalog.product.
- Position
- Below the diagonal: com.ttulka.ecommerce.sales.catalog.jdbc uses a module listed above it, which is the healthy direction.
31→20 com.ttulka.ecommerce.sales.catalog.jdbc uses com.ttulka.ecommerce.sales.catalog✕
- Connections
- 3 pairs of types, where a type in com.ttulka.ecommerce.sales.catalog.jdbc uses a type in com.ttulka.ecommerce.sales.catalog.
- The types involved
com.ttulka.ecommerce.sales.catalog.jdbc.FindCategoriesJdbc→com.ttulka.ecommerce.sales.catalog.FindCategoriescom.ttulka.ecommerce.sales.catalog.jdbc.FindProductsFromCategoryJdbc→com.ttulka.ecommerce.sales.catalog.FindProductsFromCategorycom.ttulka.ecommerce.sales.catalog.jdbc.FindProductsJdbc→com.ttulka.ecommerce.sales.catalog.FindProducts
- Direction
- com.ttulka.ecommerce.sales.catalog.jdbc uses com.ttulka.ecommerce.sales.catalog, so a change to com.ttulka.ecommerce.sales.catalog can break com.ttulka.ecommerce.sales.catalog.jdbc, while a change to com.ttulka.ecommerce.sales.catalog.jdbc can't break com.ttulka.ecommerce.sales.catalog.
- Position
- Below the diagonal: com.ttulka.ecommerce.sales.catalog.jdbc uses a module listed above it, which is the healthy direction.
32→12 com.ttulka.ecommerce.sales.catalog.rest uses com.ttulka.ecommerce.sales.catalog.product✕
- Connections
- 1 pair of types, where a type in com.ttulka.ecommerce.sales.catalog.rest uses a type in com.ttulka.ecommerce.sales.catalog.product.
- The types involved
com.ttulka.ecommerce.sales.catalog.rest.CatalogController→com.ttulka.ecommerce.sales.catalog.product.Product
- Direction
- com.ttulka.ecommerce.sales.catalog.rest uses com.ttulka.ecommerce.sales.catalog.product, so a change to com.ttulka.ecommerce.sales.catalog.product can break com.ttulka.ecommerce.sales.catalog.rest, while a change to com.ttulka.ecommerce.sales.catalog.rest can't break com.ttulka.ecommerce.sales.catalog.product.
- Position
- Below the diagonal: com.ttulka.ecommerce.sales.catalog.rest uses a module listed above it, which is the healthy direction.
32→20 com.ttulka.ecommerce.sales.catalog.rest uses com.ttulka.ecommerce.sales.catalog✕
- Connections
- 3 pairs of types, where a type in com.ttulka.ecommerce.sales.catalog.rest uses a type in com.ttulka.ecommerce.sales.catalog.
- The types involved
com.ttulka.ecommerce.sales.catalog.rest.CatalogController→com.ttulka.ecommerce.sales.catalog.FindCategoriescom.ttulka.ecommerce.sales.catalog.rest.CatalogController→com.ttulka.ecommerce.sales.catalog.FindProductscom.ttulka.ecommerce.sales.catalog.rest.CatalogController→com.ttulka.ecommerce.sales.catalog.FindProductsFromCategory
- Direction
- com.ttulka.ecommerce.sales.catalog.rest uses com.ttulka.ecommerce.sales.catalog, so a change to com.ttulka.ecommerce.sales.catalog can break com.ttulka.ecommerce.sales.catalog.rest, while a change to com.ttulka.ecommerce.sales.catalog.rest can't break com.ttulka.ecommerce.sales.catalog.
- Position
- Below the diagonal: com.ttulka.ecommerce.sales.catalog.rest uses a module listed above it, which is the healthy direction.
33→2 com.ttulka.ecommerce.sales.order.jdbc uses com.ttulka.ecommerce.common.events✕
- Connections
- 4 pairs of types, where a type in com.ttulka.ecommerce.sales.order.jdbc uses a type in com.ttulka.ecommerce.common.events.
- The types involved
com.ttulka.ecommerce.sales.order.jdbc.FindOrdersJdbc→com.ttulka.ecommerce.common.events.EventPublishercom.ttulka.ecommerce.sales.order.jdbc.OrderJdbc→com.ttulka.ecommerce.common.events.EventPublishercom.ttulka.ecommerce.sales.order.jdbc.OrderJdbcConfig→com.ttulka.ecommerce.common.events.EventPublishercom.ttulka.ecommerce.sales.order.jdbc.PlaceOrderJdbc→com.ttulka.ecommerce.common.events.EventPublisher
- Direction
- com.ttulka.ecommerce.sales.order.jdbc uses com.ttulka.ecommerce.common.events, so a change to com.ttulka.ecommerce.common.events can break com.ttulka.ecommerce.sales.order.jdbc, while a change to com.ttulka.ecommerce.sales.order.jdbc can't break com.ttulka.ecommerce.common.events.
- Position
- Below the diagonal: com.ttulka.ecommerce.sales.order.jdbc uses a module listed above it, which is the healthy direction.
33→3 com.ttulka.ecommerce.sales.order.jdbc uses com.ttulka.ecommerce.common.primitives✕
- Connections
- 3 pairs of types, where a type in com.ttulka.ecommerce.sales.order.jdbc uses a type in com.ttulka.ecommerce.common.primitives.
- The types involved
com.ttulka.ecommerce.sales.order.jdbc.OrderJdbc→com.ttulka.ecommerce.common.primitives.Moneycom.ttulka.ecommerce.sales.order.jdbc.PlaceOrderJdbc→com.ttulka.ecommerce.common.primitives.Moneycom.ttulka.ecommerce.sales.order.jdbc.UnknownOrder→com.ttulka.ecommerce.common.primitives.Money
- Direction
- com.ttulka.ecommerce.sales.order.jdbc uses com.ttulka.ecommerce.common.primitives, so a change to com.ttulka.ecommerce.common.primitives can break com.ttulka.ecommerce.sales.order.jdbc, while a change to com.ttulka.ecommerce.sales.order.jdbc can't break com.ttulka.ecommerce.common.primitives.
- Position
- Below the diagonal: com.ttulka.ecommerce.sales.order.jdbc uses a module listed above it, which is the healthy direction.
33→13 com.ttulka.ecommerce.sales.order.jdbc uses com.ttulka.ecommerce.sales.order.item✕
- Connections
- 4 pairs of types, where a type in com.ttulka.ecommerce.sales.order.jdbc uses a type in com.ttulka.ecommerce.sales.order.item.
- The types involved
com.ttulka.ecommerce.sales.order.jdbc.FindOrdersJdbc→com.ttulka.ecommerce.sales.order.item.OrderItemcom.ttulka.ecommerce.sales.order.jdbc.OrderJdbc→com.ttulka.ecommerce.sales.order.item.OrderItemcom.ttulka.ecommerce.sales.order.jdbc.PlaceOrderJdbc→com.ttulka.ecommerce.sales.order.item.OrderItemcom.ttulka.ecommerce.sales.order.jdbc.UnknownOrder→com.ttulka.ecommerce.sales.order.item.OrderItem
- Direction
- com.ttulka.ecommerce.sales.order.jdbc uses com.ttulka.ecommerce.sales.order.item, so a change to com.ttulka.ecommerce.sales.order.item can break com.ttulka.ecommerce.sales.order.jdbc, while a change to com.ttulka.ecommerce.sales.order.jdbc can't break com.ttulka.ecommerce.sales.order.item.
- Position
- Below the diagonal: com.ttulka.ecommerce.sales.order.jdbc uses a module listed above it, which is the healthy direction.
33→21 com.ttulka.ecommerce.sales.order.jdbc uses com.ttulka.ecommerce.sales.order✕
- Connections
- 10 pairs of types, where a type in com.ttulka.ecommerce.sales.order.jdbc uses a type in com.ttulka.ecommerce.sales.order.
- The types involved
com.ttulka.ecommerce.sales.order.jdbc.FindOrdersJdbc→com.ttulka.ecommerce.sales.order.FindOrderscom.ttulka.ecommerce.sales.order.jdbc.FindOrdersJdbc→com.ttulka.ecommerce.sales.order.Ordercom.ttulka.ecommerce.sales.order.jdbc.FindOrdersJdbc→com.ttulka.ecommerce.sales.order.OrderIdcom.ttulka.ecommerce.sales.order.jdbc.OrderJdbc→com.ttulka.ecommerce.sales.order.OrderIdcom.ttulka.ecommerce.sales.order.jdbc.OrderJdbc→com.ttulka.ecommerce.sales.order.OrderPlacedcom.ttulka.ecommerce.sales.order.jdbc.OrderJdbc→com.ttulka.ecommerce.sales.order.PlaceableOrdercom.ttulka.ecommerce.sales.order.jdbc.PlaceOrderJdbc→com.ttulka.ecommerce.sales.order.OrderIdcom.ttulka.ecommerce.sales.order.jdbc.PlaceOrderJdbc→com.ttulka.ecommerce.sales.order.PlaceOrdercom.ttulka.ecommerce.sales.order.jdbc.UnknownOrder→com.ttulka.ecommerce.sales.order.Ordercom.ttulka.ecommerce.sales.order.jdbc.UnknownOrder→com.ttulka.ecommerce.sales.order.OrderId
- Direction
- com.ttulka.ecommerce.sales.order.jdbc uses com.ttulka.ecommerce.sales.order, so a change to com.ttulka.ecommerce.sales.order can break com.ttulka.ecommerce.sales.order.jdbc, while a change to com.ttulka.ecommerce.sales.order.jdbc can't break com.ttulka.ecommerce.sales.order.
- Position
- Below the diagonal: com.ttulka.ecommerce.sales.order.jdbc uses a module listed above it, which is the healthy direction.
34→13 com.ttulka.ecommerce.sales.order.rest uses com.ttulka.ecommerce.sales.order.item✕
- Connections
- 1 pair of types, where a type in com.ttulka.ecommerce.sales.order.rest uses a type in com.ttulka.ecommerce.sales.order.item.
- The types involved
com.ttulka.ecommerce.sales.order.rest.OrderController→com.ttulka.ecommerce.sales.order.item.OrderItem
- Direction
- com.ttulka.ecommerce.sales.order.rest uses com.ttulka.ecommerce.sales.order.item, so a change to com.ttulka.ecommerce.sales.order.item can break com.ttulka.ecommerce.sales.order.rest, while a change to com.ttulka.ecommerce.sales.order.rest can't break com.ttulka.ecommerce.sales.order.item.
- Position
- Below the diagonal: com.ttulka.ecommerce.sales.order.rest uses a module listed above it, which is the healthy direction.
34→21 com.ttulka.ecommerce.sales.order.rest uses com.ttulka.ecommerce.sales.order✕
- Connections
- 1 pair of types, where a type in com.ttulka.ecommerce.sales.order.rest uses a type in com.ttulka.ecommerce.sales.order.
- The types involved
com.ttulka.ecommerce.sales.order.rest.OrderController→com.ttulka.ecommerce.sales.order.PlaceOrder
- Direction
- com.ttulka.ecommerce.sales.order.rest uses com.ttulka.ecommerce.sales.order, so a change to com.ttulka.ecommerce.sales.order can break com.ttulka.ecommerce.sales.order.rest, while a change to com.ttulka.ecommerce.sales.order.rest can't break com.ttulka.ecommerce.sales.order.
- Position
- Below the diagonal: com.ttulka.ecommerce.sales.order.rest uses a module listed above it, which is the healthy direction.
35→9 com.ttulka.ecommerce.shipping.dispatching.listeners uses com.ttulka.ecommerce.billing.payment✕
- Connections
- 1 pair of types, where a type in com.ttulka.ecommerce.shipping.dispatching.listeners uses a type in com.ttulka.ecommerce.billing.payment.
- The types involved
com.ttulka.ecommerce.shipping.dispatching.listeners.DispatchingListeners→com.ttulka.ecommerce.billing.payment.PaymentCollected
- Direction
- com.ttulka.ecommerce.shipping.dispatching.listeners uses com.ttulka.ecommerce.billing.payment, so a change to com.ttulka.ecommerce.billing.payment can break com.ttulka.ecommerce.shipping.dispatching.listeners, while a change to com.ttulka.ecommerce.shipping.dispatching.listeners can't break com.ttulka.ecommerce.billing.payment.
- Position
- Below the diagonal: com.ttulka.ecommerce.shipping.dispatching.listeners uses a module listed above it, which is the healthy direction.
35→14 com.ttulka.ecommerce.shipping.dispatching.listeners uses com.ttulka.ecommerce.shipping.delivery✕
- Connections
- 1 pair of types, where a type in com.ttulka.ecommerce.shipping.dispatching.listeners uses a type in com.ttulka.ecommerce.shipping.delivery.
- The types involved
com.ttulka.ecommerce.shipping.dispatching.listeners.DispatchingListeners→com.ttulka.ecommerce.shipping.delivery.DeliveryPrepared
- Direction
- com.ttulka.ecommerce.shipping.dispatching.listeners uses com.ttulka.ecommerce.shipping.delivery, so a change to com.ttulka.ecommerce.shipping.delivery can break com.ttulka.ecommerce.shipping.dispatching.listeners, while a change to com.ttulka.ecommerce.shipping.dispatching.listeners can't break com.ttulka.ecommerce.shipping.delivery.
- Position
- Below the diagonal: com.ttulka.ecommerce.shipping.dispatching.listeners uses a module listed above it, which is the healthy direction.
35→15 com.ttulka.ecommerce.shipping.dispatching.listeners uses com.ttulka.ecommerce.shipping.dispatching✕
- Connections
- 1 pair of types, where a type in com.ttulka.ecommerce.shipping.dispatching.listeners uses a type in com.ttulka.ecommerce.shipping.dispatching.
- The types involved
com.ttulka.ecommerce.shipping.dispatching.listeners.DispatchingListeners→com.ttulka.ecommerce.shipping.dispatching.DispatchingSaga
- Direction
- com.ttulka.ecommerce.shipping.dispatching.listeners uses com.ttulka.ecommerce.shipping.dispatching, so a change to com.ttulka.ecommerce.shipping.dispatching can break com.ttulka.ecommerce.shipping.dispatching.listeners, while a change to com.ttulka.ecommerce.shipping.dispatching.listeners can't break com.ttulka.ecommerce.shipping.dispatching.
- Position
- Below the diagonal: com.ttulka.ecommerce.shipping.dispatching.listeners uses a module listed above it, which is the healthy direction.
35→16 com.ttulka.ecommerce.shipping.dispatching.listeners uses com.ttulka.ecommerce.warehouse✕
- Connections
- 1 pair of types, where a type in com.ttulka.ecommerce.shipping.dispatching.listeners uses a type in com.ttulka.ecommerce.warehouse.
- The types involved
com.ttulka.ecommerce.shipping.dispatching.listeners.DispatchingListeners→com.ttulka.ecommerce.warehouse.GoodsFetched
- Direction
- com.ttulka.ecommerce.shipping.dispatching.listeners uses com.ttulka.ecommerce.warehouse, so a change to com.ttulka.ecommerce.warehouse can break com.ttulka.ecommerce.shipping.dispatching.listeners, while a change to com.ttulka.ecommerce.shipping.dispatching.listeners can't break com.ttulka.ecommerce.warehouse.
- Position
- Below the diagonal: com.ttulka.ecommerce.shipping.dispatching.listeners uses a module listed above it, which is the healthy direction.
35→21 com.ttulka.ecommerce.shipping.dispatching.listeners uses com.ttulka.ecommerce.sales.order✕
- Connections
- 1 pair of types, where a type in com.ttulka.ecommerce.shipping.dispatching.listeners uses a type in com.ttulka.ecommerce.sales.order.
- The types involved
com.ttulka.ecommerce.shipping.dispatching.listeners.DispatchingListeners→com.ttulka.ecommerce.sales.order.OrderPlaced
- Direction
- com.ttulka.ecommerce.shipping.dispatching.listeners uses com.ttulka.ecommerce.sales.order, so a change to com.ttulka.ecommerce.sales.order can break com.ttulka.ecommerce.shipping.dispatching.listeners, while a change to com.ttulka.ecommerce.shipping.dispatching.listeners can't break com.ttulka.ecommerce.sales.order.
- Position
- Below the diagonal: com.ttulka.ecommerce.shipping.dispatching.listeners uses a module listed above it, which is the healthy direction.
36→15 com.ttulka.ecommerce.warehouse.listeners uses com.ttulka.ecommerce.shipping.dispatching✕
- Connections
- 1 pair of types, where a type in com.ttulka.ecommerce.warehouse.listeners uses a type in com.ttulka.ecommerce.shipping.dispatching.
- The types involved
com.ttulka.ecommerce.warehouse.listeners.DeliveryDispatchedListener→com.ttulka.ecommerce.shipping.dispatching.DeliveryDispatched
- Direction
- com.ttulka.ecommerce.warehouse.listeners uses com.ttulka.ecommerce.shipping.dispatching, so a change to com.ttulka.ecommerce.shipping.dispatching can break com.ttulka.ecommerce.warehouse.listeners, while a change to com.ttulka.ecommerce.warehouse.listeners can't break com.ttulka.ecommerce.shipping.dispatching.
- Position
- Below the diagonal: com.ttulka.ecommerce.warehouse.listeners uses a module listed above it, which is the healthy direction.
36→16 com.ttulka.ecommerce.warehouse.listeners uses com.ttulka.ecommerce.warehouse✕
- Connections
- 2 pairs of types, where a type in com.ttulka.ecommerce.warehouse.listeners uses a type in com.ttulka.ecommerce.warehouse.
- The types involved
com.ttulka.ecommerce.warehouse.listeners.DeliveryDispatchedListener→com.ttulka.ecommerce.warehouse.RemoveFetchedGoodscom.ttulka.ecommerce.warehouse.listeners.OrderPlacedListener→com.ttulka.ecommerce.warehouse.FetchGoods
- Direction
- com.ttulka.ecommerce.warehouse.listeners uses com.ttulka.ecommerce.warehouse, so a change to com.ttulka.ecommerce.warehouse can break com.ttulka.ecommerce.warehouse.listeners, while a change to com.ttulka.ecommerce.warehouse.listeners can't break com.ttulka.ecommerce.warehouse.
- Position
- Below the diagonal: com.ttulka.ecommerce.warehouse.listeners uses a module listed above it, which is the healthy direction.
36→21 com.ttulka.ecommerce.warehouse.listeners uses com.ttulka.ecommerce.sales.order✕
- Connections
- 1 pair of types, where a type in com.ttulka.ecommerce.warehouse.listeners uses a type in com.ttulka.ecommerce.sales.order.
- The types involved
com.ttulka.ecommerce.warehouse.listeners.OrderPlacedListener→com.ttulka.ecommerce.sales.order.OrderPlaced
- Direction
- com.ttulka.ecommerce.warehouse.listeners uses com.ttulka.ecommerce.sales.order, so a change to com.ttulka.ecommerce.sales.order can break com.ttulka.ecommerce.warehouse.listeners, while a change to com.ttulka.ecommerce.warehouse.listeners can't break com.ttulka.ecommerce.sales.order.
- Position
- Below the diagonal: com.ttulka.ecommerce.warehouse.listeners 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 — Accessibility
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A02:2025 — Security Misconfiguration | 344 | High / Critical |
| A05:2025 — Injection | 14 | Medium |
Roadmap
Top priorities: Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href; Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1; Add a CI workflow that builds and runs the test suite on every push/PR.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href. | +5.5 pts | Medium | Keyboard semantics |
| Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1. | +5.5 pts | Medium | Visual & motion safety |
| Add a CI workflow that builds and runs the test suite on every push/PR. | +4.1 pts | Medium | CI/CD gates |
| Run what this repository's stack ships: spotbugs with find-sec-bugs — or `semgrep --config=auto`, which runs on any language — locally for now, since there is no CI pipeline here yet, and as a step of the first workflow you add so a security regression fails the build instead of landing. | +4.1 pts | Medium | Security & performance tooling |
| Resolve the 1 No assertions (empty test) finding(s) in Test Quality — start with DispatchingApplicationTest.java. | +1.7 pts | Low | Test Quality |
| Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh. | +3.1 pts | Medium | Page structure |
| 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. | +3.0 pts | Medium | A11y enforcement |
| Give every control a programmatic label (a <label for> / wrapping <label> / aria-label) and every button text — a placeholder is not a label. | +2.5 pts | Medium | Forms & labels |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 0.0 | Slop | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 0.2 | Slop | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 1.6 | Slop | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 1.6 | Slop | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 4.4 | Mixed | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 4.4 | Mixed | IaC & Container Security: High IaC: REDACTED |
| shipping/dispatching/application/src/test/java/com/ttulka/ecommerce/shipping/dispatching/DispatchingApplicationTest.java | 4.7 | Mixed | Test Quality: No assertions (empty test): application_starts |
| REDACTED | 6.3 | Near-clean | Static Analysis (SAST): Medium: REDACTED |
| sales/cart/application/src/test/java/com/ttulka/ecommerce/sales/cart/CartApplicationTest.java | 7.2 | Near-clean | Test Quality: No assertions: cart_is_emptied |
| sales/catalog/rest/src/test/java/com/ttulka/ecommerce/sales/catalog/rest/CatalogControllerTest.java | 7.2 | Near-clean | Test Quality: No assertions: categories_are_listed |
| shipping/delivery/rest/src/test/java/com/ttulka/ecommerce/shipping/delivery/rest/DeliveryControllerTest.java | 7.2 | Near-clean | Test Quality: No assertions: all_deliveries_are_listed |
| portal/application/src/test/java/com/ttulka/ecommerce/portal/PortalApplicationTest.java | 7.4 | Near-clean | Test Quality: No assertions: JS_resource_works |
| warehouse/rest/src/test/java/com/ttulka/ecommerce/warehouse/rest/WarehouseControllerTest.java | 7.4 | Near-clean | Test Quality: No assertions: left_in_stock |
| billing/payment/jdbc/src/main/java/com/ttulka/ecommerce/billing/payment/jdbc/PaymentsJdbc.java | 7.8 | Near-clean | Code Duplication: Duplicated block (9 lines × 2) |
| billing/payment/rest/src/test/java/com/ttulka/ecommerce/billing/payment/rest/PaymentControllerTest.java | 7.8 | Near-clean | Test Quality: No assertions: all_payments |
| portal/web/src/test/java/com/ttulka/ecommerce/portal/web/PortalControllerTest.java | 7.8 | Near-clean | Test Quality: No assertions: index_works |
| sales/catalog/jdbc/src/test/java/com/ttulka/ecommerce/sales/catalog/jdbc/UnknownProductTest.java | 7.8 | Near-clean | Test Quality: No assertions: categorize_noop |
| sales/order/application/src/test/java/com/ttulka/ecommerce/sales/order/OrderApplicationTest.java | 7.8 | Near-clean | Test Quality: No assertions: order_is_placed |
| REDACTED | 7.9 | Near-clean | IaC & Container Security: Medium IaC: REDACTED |
| REDACTED | 7.9 | Near-clean | IaC & Container Security: Medium IaC: REDACTED |
How the grades work
A definite problem that already costs you something and drags the score down: a missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here tends to cause failures elsewhere.
Likely wrong, but not failing yet. It degrades the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to carry for two years either.
Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.
Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.
Methodology & how to trust this report
This survey is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. All 73 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.9, the weighted average across measured dimensions.
What we checked — 73 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, 477 of 597 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Canine Code Analyzer duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy · checkov | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 · 3.2.533 | ✓ deterministic |
Run transparency — what happened this run
- D8 Code Coverage — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: test source is present (.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 — the Gradle `jacocoTestReport` task) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures. You can widen what we reach: optional: produce a coverage report in a standard format (JaCoCo XML — the Gradle `jacocoTestReport` task) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures — then the real number is read on the next scan.
- D12 Dependency Hygiene — 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. Currency was graded against Maven Central, but whether an artifact is DEPRECATED is not: Maven Central publishes no deprecation marker, exactly as rubygems.org does not. Whether one is UNMAINTAINED is not graded either — no registry publishes a maintenance status, and release age does not stand in for one. Two of this dimension's four signals are therefore unread on a Gradle tree, and its score reflects currency alone.
- D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Single-contributor repository — bus factor is not applicable (1 contributor(s) across 55 commit(s) sampled, automation and bot accounts excluded). Concentration needs a team to concentrate: with one contributor there is nobody to spread the knowledge to, so there is nothing here for the owner to act on.
- D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 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. For npm the surface is what a published package.json's entry points (exports, main, module, types) export, followed through the source; an entry that names build output the tree does not commit (dist/, build/) is not followed back to source, because only a tsconfig outDir/rootDir pair states that mapping and a bundler's input lives in executable configuration this engine does not evaluate.
- 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. Each source language's comment syntax, and the code a comment annotates in it, needs its own proof before D24 judges it. Until then those comments are left unread, not counted as clean.
- AXR1 Runtime accessibility — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via DockerCompose (REDACTED). compose up failed (exit 18 — an image could not be pulled) — warehouse Error context canceled redis Error context canceled portal Error context canceled dispatching Error context canceled reverseproxy Error context canceled postgres Error context canceled Error response from daemon: pull access denied for ttulka/ecommerce-delivery-service, repository does not exist or may require 'docker login': denied: requested access to the resource is denied; the earlier `compose pull` step reported: payment Error context canceled redis Error context canceled delivery Error context canceled order Error context canceled reverseproxy Error context canceled dispatching Error context canceled Error response from daemon: pull access denied for ttulka/ecommerce-warehouse-service, repository does not exist or may require 'docker login': denied: requested access to the resource is denied; the runtime sandbox reaches registries only through the in-fence pull-through mirror, so an image the mirror does not carry cannot be fetched — this is a limit of our sandbox, not of your stack; runtime evidence skipped.
- C1 Data Protection — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These personal data controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks personal data controls.
- C2 Access Controls — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These authorization controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks authorization controls.
- C3 Audit Trail — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These audit controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks audit controls.
- C4 Data Retention — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These retention controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks retention controls.
- C5 Data-Subject Rights — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These data-subject rights controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks data-subject rights controls.
- ED5 Idempotency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check decides whether a handler's mutation is safe to re-run by recognising its persistence writes (a database save, a repository write, an event publish) and its guards. Those markers are .NET member names, so in this repository's language a write such as `repository.save(order)` is not recognised and a same-named call on an unrelated library type could be. The handlers were found; their idempotency was neither confirmed nor ruled out.
- 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 this repository's Java is most of its product and 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.
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.
- D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
- D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
- D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D40 Network Egress Confinement: Egress confinement is read from committed Kubernetes manifests — a policy applied out-of-band (cluster-default deny, a service mesh, or a cloud firewall/security group off-repo) is invisible, and a present NetworkPolicy is declared config, not proof the cluster admission-controller actually enforces it at runtime.
- D41 Kernel & Syscall Confinement: Syscall/MAC confinement is read from committed manifests — a profile applied by a cluster-wide PodSecurity default or a mutating webhook off-repo isn't seen, and a declared seccomp/AppArmor profile is config presence, not proof the node's kernel actually loaded and enforced it.
- 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 REDACTED (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.
- P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
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
6 duplicated block group(s) detected.
What to do
- Resolve the 1 Duplicated block (11 lines × 12) finding(s) in Code Duplication — start with PaymentId.java. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Duplicated block (11 lines × 3) finding(s) in Code Duplication — start with Title.java. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Duplicated block (9 lines × 2) finding(s) in Code Duplication — start with PaymentsJdbc.java. — One of this dimension's main actionable groups (1 warning-level).
- Stand up a CI pipeline, then gate Code Duplication in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D5 · Coupling
63 production modules (Gradle), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; edges a convention plugin adds from buildSrc or build-logic are not visible there; 0 module(s) off the main sequence, with abstractness counted on 49 of the 63 (the rest declare no modelled class or interface, export only macros, declare types in source no model reads, or have no source directory of their own).
D6 · Cohesion (LCOM4)
0 of 10 classes have LCOM4 above 3.
D9 · Test Distribution
241 test methods: 241 unit, 0 integration, 0 BDD, 0 e2e.
D10 · Test Quality
0 skipped, 48 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 241 tests (3 harness-style project(s) excluded from the assertion penalty).
What to do
- Resolve the 1 No assertions (empty test) finding(s) in Test Quality — start with DispatchingApplicationTest.java. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 18 No assertions finding(s) in Test Quality — start with CartApplicationTest.java (3), CatalogControllerTest.java (3), DeliveryControllerTest.java (3). — One of this dimension's main actionable groups (18 warning-level).
- Resolve the 9 Test project verifies nothing finding(s) in Test Quality — start with PaymentControllerTest.java, PortalApplicationTest.java, CartApplicationTest.java. — One of this dimension's main actionable groups (9 warning-level).
- Stand up a CI pipeline, then gate Test Quality in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D11 · Test Reliability
0 flaky across 1 measured tier(s). Java/Kotlin (repository root, Gradle): measured (0 flaky).
D12 · Dependency Hygiene
This repository's Gradle dependency graph was RESOLVED BY A BUILD, across every subproject rather than the root alone: 117 artifact(s) resolved, 117 of them gradable against Maven Central, and 111 behind a shipped release. Where a version was requested and a different one won conflict resolution, the RESOLVED version is what is graded — grading the request would recommend an upgrade already applied. Known CVEs in the same graph are a separate question again, reported under D30.
What to do
- Stand up a CI pipeline, then gate Dependency Hygiene in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
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 63 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.
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window.
D17 · Explicit Debt
2 deducted task-comment markers across 3639 LoC (0.0/KLoC) → score 9.9. 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 2 TodoComment finding(s) in Explicit Debt — start with RemoveFetchedGoodsTest.java, DispatchingApplicationTest.java. — One of this dimension's main actionable groups (2 warning-level).
- Stand up a CI pipeline, then gate Explicit Debt in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D19 · Documentation Quality
1 of 1 documentation facets pass in full. 1 document(s) read across 1 unit(s).
D26 · Project Cohesion
0 of 53 build units (Gradle) flagged as possibly oversized/incoherent.
D27 · Navigability
85 % of calls cross a namespace and 26 % go through an interface, but 100 % of collaborators are co-located — so following a call takes several hops. Baseline: small — navigation cost is tolerated.
What to do
- Improve Navigability — currently 8.7/10. — 85 % of calls cross a namespace and 26 % 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)
14 finding(s): 0 critical, 0 high, 12 medium, 2 low. semgrep hit a parse error in 1 file(s) — `gradlew` (line 72, line 178) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them.
What to do
- Resolve the 11 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (7), REDACTED (2), REDACTED. — One of this dimension's main actionable groups (11 warning-level).
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 recommendation-level).
D31 · IaC & Container Security
344 finding(s): 0 critical, 21 high, 263 medium, 60 low.
What to do
- Resolve the 263 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (165), REDACTED (30), REDACTED (29). — One of this dimension's main actionable groups (263 warning-level).
- Resolve the 21 High IaC finding(s) in IaC & Container Security — start with REDACTED (9), REDACTED (7), REDACTED (2). — One of this dimension's main actionable groups (21 issue-level).
- Resolve the 60 Low IaC finding(s) in IaC & Container Security — start with REDACTED (36), REDACTED (11), REDACTED (6). — One of this dimension's main actionable groups (60 recommendation-level).
D34 · Knowledge Freshness
15 of 15 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is common/application-integration-spring-boot-starter/src/main/java/com/ttulka/ecommerce/common/integration/messaging/RedisBrokerConfig.java. Counted over 15 of the 202 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 15 Orphaned file finding(s) in Knowledge Freshness — start with RedisBrokerConfig.java, settings.gradle, RabbitMqConfig.java. — One of this dimension's main actionable groups (15 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.
D40 · Network Egress Confinement
0/2 network-egress controls present (network policy, egress restriction).
What to do
- Resolve the 1 No network policy finding(s) in Network Egress Confinement. — One of this dimension's main actionable groups (1 recommendation-level).
D41 · Kernel & Syscall Confinement
0/11 workload(s) run every container under a seccomp profile; 0/11 declare an AppArmor/SELinux profile.
What to do
- Resolve the 11 No seccomp profile finding(s) in Kernel & Syscall Confinement — start with REDACTED (7), REDACTED (2), REDACTED. — One of this dimension's main actionable groups (11 recommendation-level).
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 10 platform declaration(s) and 1 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
- This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it. (×2) — shipping/delivery/webcomp/src/main/resources/static/js/delivery/DeliveryForm.js:7, shipping/delivery/webcomp/src/main/resources/static/js/delivery/DeliveryForm.js:11
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"). — portal/web/src/main/resources/templates/index.html:2
- No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>. — portal/web/src/main/resources/templates/index.html:2
- A <table> with data cells but no <th> gives assistive technology no way to associate cells with their headers. Mark the header row/column cells as <th> (with a scope). — shipping/delivery/webcomp/src/main/resources/static/js/delivery/DeliveryForm.js:4
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
- The repo's own CSS styles .remove with `cursor: pointer`, so this <span> is a control — but it has no role, no tabindex="0" and no key handler, so it can only be reached with a mouse. Use a <button>, or add role + tabindex="0" + a key handler. — sales/cart/webcomp/src/main/resources/static/js/cart/ItemList.js:43
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
- `#header` sets color: white on background-color: #66a3ff — 2.5:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — portal/web/src/main/resources/static/css/layout.css:17
What to do
- Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1.
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 11 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.
AX1 · Captive dependencies
AX10 · Code composition
AX2 · Stateful singletons
AX3 · Project dependency cycles
AX4 · Dependency direction
AX6 · Interface segregation
IC1 · Incompleteness & stubs
M1 · Documentation (README)
What to do
- Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
- Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
- Add a README to the 63 of 63 project(s) that lack one — worth up to 2 pts.
M3 · Folder & project structure
P1 · CI/CD gates
- No CI workflow found (.github/workflows, azure-pipelines.yml, .gitlab-ci.yml, …) — changes aren't gated by an automated build/test.
What to do
- Add a CI workflow that builds and runs the test suite on every push/PR.
P2 · Observability
- Only 6/21 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `application`, `billing/payment/application`, `billing/payment/rest`, `portal/application`, `sales/cart/application` and 10 more.
What to do
- Extend structured logging to the remaining runnable modules so everything you run is diagnosable in production.
- Consider OpenTelemetry tracing/metrics (opentelemetry-java or Micrometer) and a health-check endpoint (Spring Boot Actuator's /actuator/health, or a /health route) for operability.
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) — this repository has no CI pipeline yet, so run it locally to clear the existing findings, then make it a step of the first workflow you add so a regression fails the build. What was searched, so you can tell an absence from a miss: the 0 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.
What to do
- Run what this repository's stack ships: spotbugs with find-sec-bugs — or `semgrep --config=auto`, which runs on any language — locally for now, since there is no CI pipeline here yet, and as a step of the first workflow you add so a security regression fails the build instead of landing.
- Enable Dependabot/Renovate or a dependency-review gate.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
- Deployment is orchestrated by compose, but no service declares a `healthcheck:` and nothing pins a previous image to fall back to — the runtime can tell that the container is up, not that it is serving, so a bad release is harder to detect and reverse.
What to do
- Add a `healthcheck:` to the served compose service — probing the endpoint it already answers on where it has one — with `depends_on: condition: service_healthy` on whatever waits for it, and keep the deployed image tag immutable and recorded so rolling back is re-pointing at the previous tag rather than rebuilding.
- Add an approval/environment gate (required reviewers / protection rules) before production promotion.
R1 · Type Safety
- 0 typed · 18 plain JS — the untyped files are portal/web/src/main/resources/static/js/Application.js, portal/web/src/main/resources/static/js/portal/CartPage.js, portal/web/src/main/resources/static/js/portal/CatalogPage.js, portal/web/src/main/resources/static/js/portal/Layout.js, portal/web/src/main/resources/static/js/portal/OrderPage.js, portal/web/src/main/resources/static/js/portal/page.js (+12 more).
What to do
- Adopt TypeScript for the frontend: add a typecheck step to the build, then either type-check the existing JavaScript in place (`checkJs`/JSDoc types) or convert the highest-traffic modules first — no file is typed today, so this is an adoption, not a clean-up.
R10 · Code Duplication
- 8 duplicated blocks under the repository root have copies in at least two of the sibling directories portal, sales, shipping — 0 of them are reported below, and 8 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 8 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 8 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 8 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — sales/order/webcomp/src/main/resources/static/js/order/OrderForm.js:1
- sales/cart/webcomp/src/main/resources/static/js/cart/ItemList.js:8 · sales/catalog/webcomp/src/main/resources/static/js/catalog/ProductList.js:9 — the two spans are one implementation copied and then locally edited — 187 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — sales/cart/webcomp/src/main/resources/static/js/cart/ItemList.js:8
What to do
- Act on each finding's own remediation rather than one rule: the move depends on what recurs. Where the copies are executable blocks, give the shared part one home and call it from each site; where they are declarations, a listing, a specialisation already delegating to its base, or one shape repeated per entity, there is no call site and the move is a shared type, a generated set or a factory — sometimes there is nothing to extract.
R2 · Cyclomatic Complexity
R3 · Large Files
R7 · Dead Code
R9 · Circular Imports
S1 · Web-Security Posture
- None of the 11 security response headers the OWASP Secure Headers Project recommends (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options, …) is configured — defense in depth, even when a reverse proxy could set them. This is reported because `default.conf` is committed to this repository and declares the server that serves it, so the configuration that would carry these headers is in this repository and was read in full. (−2.0 on this card.) — reverseproxy/default.conf:1
What to do
- Set security response headers on the surface this repository serves: an `add_header` directive per header in the nginx/Caddy/Apache config, a `_headers` / `vercel.json` / `netlify.toml` entry for a static host, or `helmet()` in the HTTP server. `Content-Security-Policy` is the one that pays for itself first — it is what contains an injected script once one reaches the page — followed by `X-Content-Type-Options: nosniff` and a frame policy (`X-Frame-Options: DENY`, or CSP `frame-ancestors`). Where the app is served from a build container, the header configuration belongs in the image beside the built assets, so it ships with them rather than depending on where it lands.
X1 · Async correctness
X12 · Unreachable branch
X13 · Undrained process stream
X14 · Bypassable address classification
X15 · Unvalidated length from an untrusted reader
X16 · Unfloored truncation loop
X17 · Uncapped recursion over a caller-supplied document
X18 · Disposal-pattern correctness
X19 · Unrestored process-global state
X20 · Mistyped argument guard
X21 · Side-effecting pattern guard
X22 · Contradicted release guard
X23 · Unguarded diagnostic materialisation
X24 · Document value interpolated into markup unescaped
- `title` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. (×2) — sales/cart/webcomp/src/main/resources/static/js/cart/ItemList.js:39, sales/catalog/webcomp/src/main/resources/static/js/catalog/ProductList.js:44
- `formatPrice(price)` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. (×2) — sales/cart/webcomp/src/main/resources/static/js/cart/ItemList.js:40, sales/catalog/webcomp/src/main/resources/static/js/catalog/ProductList.js:47
- `quantity` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. (×2) — sales/cart/webcomp/src/main/resources/static/js/cart/ItemList.js:41, sales/order/webcomp/src/main/resources/static/js/order/OrderForm.js:44
- `amount?amount:''` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — sales/cart/webcomp/src/main/resources/static/js/cart/MenuLink.js:30
- `uri` is text this program did not author, and it is written into a URL attribute through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — sales/catalog/webcomp/src/main/resources/static/js/catalog/CategoriesMenu.js:24
- `id` is text this program did not author, and it is written into a quoted attribute value through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. (×2) — sales/catalog/webcomp/src/main/resources/static/js/catalog/ProductList.js:43, sales/catalog/webcomp/src/main/resources/static/js/catalog/ProductList.js:49
- `description` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — sales/catalog/webcomp/src/main/resources/static/js/catalog/ProductList.js:45
- `this._inStockValue(id)` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. (×2) — sales/catalog/webcomp/src/main/resources/static/js/catalog/ProductList.js:46, sales/catalog/webcomp/src/main/resources/static/js/catalog/ProductList.js:62
- `title` is text this program did not author, and it is written into a quoted attribute value through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — sales/catalog/webcomp/src/main/resources/static/js/catalog/ProductList.js:50
- `price` is text this program did not author, and it is written into a quoted attribute value through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — sales/catalog/webcomp/src/main/resources/static/js/catalog/ProductList.js:51
What to do
- Each finding names the expression, the attribute it lands in and the line. Confirm the value's origin from the read this analyzer traced, then escape it at the sink or validate it against the shape the attribute accepts before interpolating.
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
- `trace` at line 76 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.trace("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. — shipping/dispatching/jdbc/src/main/java/com/ttulka/ecommerce/shipping/dispatching/jdbc/DispatchingSagaJdbc.java:76
What to do
- Interpolated log message defeats structured logging
X5 · Nullable reference types
- 0/53 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 | 51% | Adequate — gated by R1, X5 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 95% | Exemplary | Strongest area. |
| Maturity | 68% | Adequate — gated by D34 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 33% | Adequate — gated by P1, P3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 70% | Adequate — gated by D31 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Accessibility | 23% | Weak — gated by AC3, AC4, AC6 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
Unscored — 1 check(s) recorded observations but carry no score
- X10 Duplicated predicate — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
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.
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
- P6 Release Hygiene — not evidenced — no changelog, version stamp or semver release tag in the repo
Not included — 51 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.
- AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AX8 Test isolation — no test/production split to check
- AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXR1 Runtime accessibility — compose up failed (exit 18 — an image could not be pulled) — warehouse Error context canceled redis Error context canceled portal Error context canceled dispatching Error context canceled reverseproxy Error context canceled postgres Error context canceled Error response from daemon: pull access denied for ttulka/ecommerce-delivery-service, repository does not exist or may require 'docker login': denied: requested access to the resource is denied; the earlier `compose pull` step reported: payment Error context canceled redis Error context canceled delivery Error context canceled order Error context canceled reverseproxy Error context canceled dispatching Error context canceled Error response from daemon: pull access denied for ttulka/ecommerce-warehouse-service, repository does not exist or may require 'docker login': denied: requested access to the resource is denied; the runtime sandbox reaches registries only through the in-fence pull-through mirror, so an image the mirror does not carry cannot be fetched — this is a limit of our sandbox, not of your stack; runtime evidence skipped This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
- C1 Data Protection — Not assessed: these personal data controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks personal data controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- C2 Access Controls — Not assessed: these authorization controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks authorization controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- D16 Bus Factor — single-contributor repository — bus factor is not applicable
- D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
- D20 ADR Quality — N/A — this repo declares itself a template / kata / sample / demo; a formal ADR log is deferred to a real application built from it.
- D21 Naming Consistency — Naming consistency is measured on C# and TypeScript only; Java, JavaScript not measured.
- D22 Internal API Consistency — The exposed public-API surface could not be collected — no C#/VB projects loaded.
- D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D24 Comment Value — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only; comments in this repository's .java source were not judged.
- D25 ADR Conformance — no ADRs to check
- D30 Dependency Vulnerabilities — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Gradle build (build.gradle/build.gradle.kts) — not scanned yet).
- 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 — No CI/build pipeline found (.github/.forgejo/.gitea workflows, .circleci, .buildkite, .woodpecker, .teamcity, .gitlab-ci.yml, .travis.yml, bitbucket-pipelines.yml, .drone.yml, .cirrus.yml, .woodpecker.yml, appveyor.yml, azure-pipelines*.yml, .pipelines/, .vsts-ci/, .azuredevops/, Jenkinsfile); there is no build to attest provenance for.
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- D39 IL Efficiency — D39 measures the IL emitted by a .NET build; this repository has no .NET solution or project files, so the dimension does not apply.
- D42 Runtime Threat Enforcement — The repository ships application workloads but no cluster-governance resources (CRDs, admission webhooks, or a committed policy engine). Runtime threat-detection (Falco/Tetragon) and admission control (Kyverno/OPA-Gatekeeper/PodSecurity) are cluster-OPERATOR controls owned by the platform, not shipped by an application repo/chart — nothing for this repo to assess.
- D43 Malicious Dependencies — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Gradle build (build.gradle/build.gradle.kts) — not scanned yet).
- 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
- DM1 Domain Modelling — applicable but not scored (2 of 3 signals for this style — below the bar we score at): 40 value object(s); 7 domain event(s); its domain events are published by services or handlers — no domain entity raises one
- ED1 Event-Driven — not scored — this repository shows only 1 of the 3 signals this lens looks for (7 event handler(s))
- ED5 Idempotency — Not assessed, and this one is on us: 7 command handler(s) or message consumer(s) were found here, but this check does not yet recognise persistence writes in this repository's language. Idempotency was neither confirmed nor ruled out — this is a limit of the analyzer, not a finding about your code.
- ES1 Event Sourcing — not scored — this repository shows only 1 of the 3 signals this lens looks for (an Axon event-sourcing framework (@Aggregate/@CommandHandler/@EventSourcingHandler annotations))
- 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.
- M2 Architecture documentation — This repo declares itself a template / kata / sample / demo — formal architecture documentation (ADRs, C4 diagrams) is deferred to a real application built from it, so its absence is not a defect here.
- M4 Documentation accuracy — Not applicable: the 1 current-state document(s) make no claim of a kind M4 checks.
- P12 CI test-gate honesty — no CI workflow found
- P7 Outbound HTTP resilience — no outbound HTTP usage detected — no HTTP client call or construction in the JVM, JavaScript/TypeScript source (service entry point: warehouse/rest/src/main/java/com/ttulka/ecommerce/warehouse/rest/WarehouseController.java:22 (@RestController))
- 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 — the Gradle `jacocoTestReport` task) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures, or wire coverage collection into CI, to enable this cross-layer check
- PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for `@Benchmark` in a Java, Kotlin or Scala file importing JMH or kotlinx-benchmark, Jetpack Benchmark's `measureRepeated` in a file importing androidx.benchmark, or JMH/kotlinx-benchmark/androidx.benchmark in a pom.xml, Gradle or sbt build, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
- PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
- PF3 Async & latency hygiene — Not applicable: this repository declares no async functions, so there is no asynchronous code for a blocking call to stall.
- R11 Import Boundaries — No recognizable feature-sliced/layered src layout — boundary rules not applicable.
- R4 Test Coverage — the JS/TS workspace (18 production file(s)) has no JavaScript/TypeScript test, but it is 14.86% of this repository's production source and the other 85.14% carries 3,761 line(s) of test code this pass cannot read — an incidental frontend's reachability is not the repository's test posture, so it is not scored as one
- R5 Dependency Freshness — no package-lock.json — dependency freshness not measured (would require an npm lockfile); JS/npm CVEs are scored in D30 (Dependency Vulnerabilities), which answers every ecosystem
- R6 Tooling — no package.json in the repository — test/lint/typecheck wiring is read from package.json scripts (corroborated against CI), so this project's own toolchain isn't measured here
- R8 Dependency Hygiene — Not measured — no package.json declares any dependency, so there is nothing to check imports against (imports may resolve through a host runtime rather than node).
- 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 — 26 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- <input> without a programmatic label shipping/delivery/webcomp/src/main/resources/static/js/delivery/DeliveryForm.js:7
- <input> without a programmatic label shipping/delivery/webcomp/src/main/resources/static/js/delivery/DeliveryForm.js:11
- <html> without a lang portal/web/src/main/resources/templates/index.html:2
- Clickable element isn't keyboard-operable sales/cart/webcomp/src/main/resources/static/js/cart/ItemList.js:43
- No assertions (empty test): application_starts shipping/dispatching/application/src/test/java/com/ttulka/ecommerce/shipping/dispatching/DispatchingApplicationTest.java:10
Serious — 333 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- No assertions: all_payments billing/payment/rest/src/test/java/com/ttulka/ecommerce/billing/payment/rest/PaymentControllerTest.java:37
- No assertions: index_works portal/web/src/test/java/com/ttulka/ecommerce/portal/web/PortalControllerTest.java:20
- No assertions: JS_resource_works portal/application/src/test/java/com/ttulka/ecommerce/portal/PortalApplicationTest.java:25
- No assertions: index_works portal/application/src/test/java/com/ttulka/ecommerce/portal/PortalApplicationTest.java:16
- No assertions: cart_is_emptied sales/cart/application/src/test/java/com/ttulka/ecommerce/sales/cart/CartApplicationTest.java:87
- No assertions: item_is_added sales/cart/application/src/test/java/com/ttulka/ecommerce/sales/cart/CartApplicationTest.java:20
- No assertions: item_is_removed sales/cart/application/src/test/java/com/ttulka/ecommerce/sales/cart/CartApplicationTest.java:49
- No assertions: categorize_noop sales/catalog/jdbc/src/test/java/com/ttulka/ecommerce/sales/catalog/jdbc/UnknownProductTest.java:68
- No assertions: put_for_sale_noop sales/catalog/jdbc/src/test/java/com/ttulka/ecommerce/sales/catalog/jdbc/UnknownProductTest.java:62
- No assertions: categories_are_listed sales/catalog/rest/src/test/java/com/ttulka/ecommerce/sales/catalog/rest/CatalogControllerTest.java:50
- No assertions: products_are_listed sales/catalog/rest/src/test/java/com/ttulka/ecommerce/sales/catalog/rest/CatalogControllerTest.java:62
- No assertions: products_from_category_are_listed sales/catalog/rest/src/test/java/com/ttulka/ecommerce/sales/catalog/rest/CatalogControllerTest.java:76
- No assertions: order_is_placed sales/order/application/src/test/java/com/ttulka/ecommerce/sales/order/OrderApplicationTest.java:18
- No assertions: all_deliveries_are_listed shipping/delivery/rest/src/test/java/com/ttulka/ecommerce/shipping/delivery/rest/DeliveryControllerTest.java:47
- No assertions: delivery_by_order_is_listed shipping/delivery/rest/src/test/java/com/ttulka/ecommerce/shipping/delivery/rest/DeliveryControllerTest.java:59
- No assertions: delivery_is_prepared shipping/delivery/rest/src/test/java/com/ttulka/ecommerce/shipping/delivery/rest/DeliveryControllerTest.java:72
- No assertions: left_in_stock warehouse/rest/src/test/java/com/ttulka/ecommerce/warehouse/rest/WarehouseControllerTest.java:37
- No assertions: stock_is_listed_for_product_ids warehouse/rest/src/test/java/com/ttulka/ecommerce/warehouse/rest/WarehouseControllerTest.java:46
- Untrusted text written into markup unescaped sales/cart/webcomp/src/main/resources/static/js/cart/ItemList.js:39
- Untrusted text written into markup unescaped sales/cart/webcomp/src/main/resources/static/js/cart/ItemList.js:40
- Untrusted text written into markup unescaped sales/cart/webcomp/src/main/resources/static/js/cart/ItemList.js:41
- Untrusted text written into markup unescaped sales/cart/webcomp/src/main/resources/static/js/cart/MenuLink.js:30
- Untrusted text written into markup unescaped sales/catalog/webcomp/src/main/resources/static/js/catalog/CategoriesMenu.js:24
- Untrusted text written into markup unescaped sales/catalog/webcomp/src/main/resources/static/js/catalog/ProductList.js:43
- Untrusted text written into markup unescaped sales/catalog/webcomp/src/main/resources/static/js/catalog/ProductList.js:44
- Untrusted text written into markup unescaped sales/catalog/webcomp/src/main/resources/static/js/catalog/ProductList.js:45
- Untrusted text written into markup unescaped sales/catalog/webcomp/src/main/resources/static/js/catalog/ProductList.js:46
- Untrusted text written into markup unescaped sales/catalog/webcomp/src/main/resources/static/js/catalog/ProductList.js:47
- Untrusted text written into markup unescaped sales/catalog/webcomp/src/main/resources/static/js/catalog/ProductList.js:49
- Untrusted text written into markup unescaped sales/catalog/webcomp/src/main/resources/static/js/catalog/ProductList.js:50
- Untrusted text written into markup unescaped sales/catalog/webcomp/src/main/resources/static/js/catalog/ProductList.js:51
- Untrusted text written into markup unescaped sales/catalog/webcomp/src/main/resources/static/js/catalog/ProductList.js:62
- Untrusted text written into markup unescaped sales/order/webcomp/src/main/resources/static/js/order/OrderForm.js:44
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Test project verifies nothing: billing/payment/rest billing/payment/rest/src/test/java/com/ttulka/ecommerce/billing/payment/rest/PaymentControllerTest.java:37
- Test project verifies nothing: portal/application portal/application/src/test/java/com/ttulka/ecommerce/portal/PortalApplicationTest.java:25
- Test project verifies nothing: sales/cart/application sales/cart/application/src/test/java/com/ttulka/ecommerce/sales/cart/CartApplicationTest.java:87
- Test project verifies nothing: sales/catalog/rest sales/catalog/rest/src/test/java/com/ttulka/ecommerce/sales/catalog/rest/CatalogControllerTest.java:50
- Test project verifies nothing: sales/order/application sales/order/application/src/test/java/com/ttulka/ecommerce/sales/order/OrderApplicationTest.java:18
- Test project verifies nothing: shipping/delivery/rest shipping/delivery/rest/src/test/java/com/ttulka/ecommerce/shipping/delivery/rest/DeliveryControllerTest.java:47
- Test project verifies nothing: shipping/dispatching/application shipping/dispatching/application/src/test/java/com/ttulka/ecommerce/shipping/dispatching/DispatchingApplicationTest.java:10
- Test project verifies nothing: warehouse/rest warehouse/rest/src/test/java/com/ttulka/ecommerce/warehouse/rest/WarehouseControllerTest.java:37
- Test project verifies nothing: web portal/web/src/test/java/com/ttulka/ecommerce/portal/web/PortalControllerTest.java:20
- TodoComment warehouse/jdbc/src/test/java/com/ttulka/ecommerce/warehouse/jdbc/RemoveFetchedGoodsTest.java:25
- TodoComment shipping/dispatching/application/src/test/java/com/ttulka/ecommerce/shipping/dispatching/DispatchingApplicationTest.java:11
- Page without a main landmark portal/web/src/main/resources/templates/index.html:2
- Data table has no header cells shipping/delivery/webcomp/src/main/resources/static/js/delivery/DeliveryForm.js:4
- Low contrast colour pair in CSS (2.5:1) portal/web/src/main/resources/static/css/layout.css:17
- Accessibility enforcement below the top rung
- REDACTED
- Duplicated block (11 lines × 12) billing/payment/domain/src/main/java/com/ttulka/ecommerce/billing/payment/PaymentId.java:16
- Duplicated block (11 lines × 3) sales/cart/domain/src/main/java/com/ttulka/ecommerce/sales/cart/item/Title.java:16
- Duplicated block (9 lines × 2) billing/payment/jdbc/src/main/java/com/ttulka/ecommerce/billing/payment/jdbc/PaymentsJdbc.java:44
- Duplicated block (5 lines × 2) sales/order/jdbc/src/main/java/com/ttulka/ecommerce/sales/order/jdbc/FindOrdersJdbc.java:60
- Duplicated block (8 lines × 2) billing/payment/jdbc/src/main/java/com/ttulka/ecommerce/billing/payment/jdbc/PaymentsJdbc.java:60
- Duplicated block (7 lines × 2) sales/catalog/jdbc/src/main/java/com/ttulka/ecommerce/sales/catalog/jdbc/FindCategoriesJdbc.java:30
- No CI pipeline
- Type Safety
- Duplication concentrated across 3 sibling directories (8 clone groups) sales/order/webcomp/src/main/resources/static/js/order/OrderForm.js:1
- Duplicated block with local edits (31 matched lines × 2 locations) sales/cart/webcomp/src/main/resources/static/js/cart/ItemList.js:8
Minor — 127 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- No direct assertions: cart_is_emptied sales/cart/rest/src/test/java/com/ttulka/ecommerce/sales/cart/rest/CartControllerTest.java:87
- No direct assertions: item_is_added_into_the_cart sales/cart/rest/src/test/java/com/ttulka/ecommerce/sales/cart/rest/CartControllerTest.java:59
- No direct assertions: item_is_removed_from_the_cart sales/cart/rest/src/test/java/com/ttulka/ecommerce/sales/cart/rest/CartControllerTest.java:76
- No direct assertions: items_are_listed sales/cart/rest/src/test/java/com/ttulka/ecommerce/sales/cart/rest/CartControllerTest.java:43
- No direct assertions: not_accepted_delivery_is_not_dispatched shipping/dispatching/jdbc/src/test/java/com/ttulka/ecommerce/shipping/dispatching/jdbc/DispatchingSagaTest.java:64
- No direct assertions: not_fetched_delivery_is_not_dispatched shipping/dispatching/jdbc/src/test/java/com/ttulka/ecommerce/shipping/dispatching/jdbc/DispatchingSagaTest.java:54
- No direct assertions: not_paid_delivery_is_not_dispatched shipping/dispatching/jdbc/src/test/java/com/ttulka/ecommerce/shipping/dispatching/jdbc/DispatchingSagaTest.java:44
- No direct assertions: not_prepared_delivery_is_not_dispatched shipping/dispatching/jdbc/src/test/java/com/ttulka/ecommerce/shipping/dispatching/jdbc/DispatchingSagaTest.java:74
- No direct assertions: no_classes_ending_with_aggregate application/src/test/java/com/ttulka/ecommerce/CleanCodeArchTest.java:61
- No direct assertions: no_classes_ending_with_dto application/src/test/java/com/ttulka/ecommerce/CleanCodeArchTest.java:32
- No direct assertions: no_classes_ending_with_entity application/src/test/java/com/ttulka/ecommerce/CleanCodeArchTest.java:52
- No direct assertions: no_classes_ending_with_impl application/src/test/java/com/ttulka/ecommerce/CleanCodeArchTest.java:14
- No direct assertions: no_classes_ending_with_repository application/src/test/java/com/ttulka/ecommerce/CleanCodeArchTest.java:42
- No direct assertions: no_classes_ending_with_service application/src/test/java/com/ttulka/ecommerce/CleanCodeArchTest.java:23
- No direct assertions: billing_payment_domain_has_no_dependency_to_its_implementation application/src/test/java/com/ttulka/ecommerce/CleanModulesArchTest.java:93
- No direct assertions: billing_payment_service_has_no_dependencies_on_others_except_events application/src/test/java/com/ttulka/ecommerce/CleanModulesArchTest.java:80
- No direct assertions: catalog_service_has_no_dependencies_on_billing application/src/test/java/com/ttulka/ecommerce/CleanModulesArchTest.java:181
- No direct assertions: portal_web_uses_only_its_own_use_cases_and_no_direct_dependencies_on_other_services application/src/test/java/com/ttulka/ecommerce/CleanModulesArchTest.java:190
- No direct assertions: sales_cart_service_has_no_dependency_on_others application/src/test/java/com/ttulka/ecommerce/CleanModulesArchTest.java:68
- No direct assertions: sales_catalog_domain_has_no_dependency_to_its_implementation application/src/test/java/com/ttulka/ecommerce/CleanModulesArchTest.java:31
- No direct assertions: sales_catalog_service_has_no_dependency_on_others application/src/test/java/com/ttulka/ecommerce/CleanModulesArchTest.java:19
- No direct assertions: sales_order_domain_has_no_dependency_to_its_implementation application/src/test/java/com/ttulka/ecommerce/CleanModulesArchTest.java:56
- No direct assertions: sales_order_service_has_no_dependencies_on_others_except_events application/src/test/java/com/ttulka/ecommerce/CleanModulesArchTest.java:43
- No direct assertions: shipping_delivery_domain_has_no_dependency_to_its_implementation application/src/test/java/com/ttulka/ecommerce/CleanModulesArchTest.java:118
- No direct assertions: shipping_delivery_service_has_no_dependencies_on_others_except_events application/src/test/java/com/ttulka/ecommerce/CleanModulesArchTest.java:105
- Orphaned file common/application-integration-spring-boot-starter/src/main/java/com/ttulka/ecommerce/common/integration/messaging/RedisBrokerConfig.java:1
- Orphaned file settings.gradle:1
- Orphaned file common/application-integration-spring-boot-starter/src/main/java/com/ttulka/ecommerce/common/integration/messaging/RabbitMqConfig.java:1
- Orphaned file sales/cart/jdbc/src/main/java/com/ttulka/ecommerce/sales/cart/jdbc/CartJdbc.java:1
- Orphaned file billing/payment/jdbc/src/main/java/com/ttulka/ecommerce/billing/payment/jdbc/PaymentJdbc.java:1
- Orphaned file sales/cart/rest/src/main/java/com/ttulka/ecommerce/sales/cart/rest/CartController.java:1
- Orphaned file shipping/delivery/jdbc/src/main/java/com/ttulka/ecommerce/shipping/delivery/jdbc/DeliveryJdbc.java:1
- Orphaned file sales/order/jdbc/src/main/java/com/ttulka/ecommerce/sales/order/jdbc/OrderJdbc.java:1
- Orphaned file shipping/delivery/rest/src/main/java/com/ttulka/ecommerce/shipping/delivery/rest/DeliveryController.java:1
- Orphaned file shipping/dispatching/jdbc/src/main/java/com/ttulka/ecommerce/shipping/dispatching/jdbc/DispatchingSagaJdbc.java:1
- Orphaned file warehouse/jdbc/src/main/java/com/ttulka/ecommerce/warehouse/jdbc/GoodsFetchingJdbc.java:1
- Orphaned file sales/catalog/jdbc/src/main/java/com/ttulka/ecommerce/sales/catalog/jdbc/ProductsJdbc.java:1
- Orphaned file billing/payment/jdbc/src/main/java/com/ttulka/ecommerce/billing/payment/jdbc/PaymentsJdbc.java:1
- Orphaned file shipping/delivery/jdbc/src/main/java/com/ttulka/ecommerce/shipping/delivery/jdbc/FindDeliveriesJdbc.java:1
- Orphaned file sales/catalog/jdbc/src/main/java/com/ttulka/ecommerce/sales/catalog/jdbc/ProductJdbc.java:1
- No seccomp profile REDACTED:2
- No seccomp profile REDACTED:44
- No seccomp profile REDACTED:2
- No seccomp profile REDACTED:54
- No seccomp profile REDACTED:106
- No seccomp profile REDACTED:158
- No seccomp profile REDACTED:210
- No seccomp profile REDACTED:262
- No seccomp profile REDACTED:314
- No seccomp profile REDACTED:2
- No seccomp profile REDACTED:2
- Test project verifies nothing: sales/cart/rest sales/cart/rest/src/test/java/com/ttulka/ecommerce/sales/cart/rest/CartControllerTest.java:87
- REDACTED
- REDACTED
- Orphaned files with no living knowledge
- No network policy
- Logging is not universal
- No SAST
- No rollback/health safety
- No security response headers detected reverseproxy/default.conf:1
- Duplicated predicate billing/payment/jdbc/src/main/java/com/ttulka/ecommerce/billing/payment/jdbc/PaymentsJdbc.java:45
- Interpolated log message defeats structured logging shipping/dispatching/jdbc/src/main/java/com/ttulka/ecommerce/shipping/dispatching/jdbc/DispatchingSagaJdbc.java:76
- Java packages are not null-marked everywhere
Minor — 111 finding(s)
- Outdated (compile): org.projectlombok:lombok
- Outdated (compile): org.springframework.boot:spring-boot-starter-jdbc
- Outdated (compile): org.springframework.boot:spring-boot-starter
- Outdated (compile): org.springframework.boot:spring-boot
- Outdated (compile): org.springframework:spring-core
- Outdated (compile): org.springframework:spring-jcl
- Outdated (compile): org.springframework:spring-context
- Outdated (compile): org.springframework:spring-aop
- Outdated (compile): org.springframework:spring-beans
- Outdated (compile): org.springframework:spring-expression
- Outdated (compile): io.micrometer:micrometer-observation
- Outdated (compile): io.micrometer:micrometer-commons
- Outdated (compile): org.springframework.boot:spring-boot-autoconfigure
- Outdated (compile): org.springframework.boot:spring-boot-starter-logging
- Outdated (compile): ch.qos.logback:logback-classic
- Outdated (compile): ch.qos.logback:logback-core
- Outdated (compile): org.slf4j:slf4j-api
- Outdated (compile): org.apache.logging.log4j:log4j-to-slf4j
- Outdated (compile): org.apache.logging.log4j:log4j-api
- Outdated (compile): org.slf4j:jul-to-slf4j
- Outdated (compile): jakarta.annotation:jakarta.annotation-api
- Outdated (compile): org.yaml:snakeyaml
- Outdated (compile): com.zaxxer:HikariCP
- Outdated (compile): org.springframework:spring-jdbc
- Outdated (compile): org.springframework:spring-tx
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-419e86912c8c418cb52b6dd4c27d8814/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-419e86912c8c418cb52b6dd4c27d8814/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 . | 14 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | none (dependency manifest found, not scanned for vulnerabilities here) | — | none (dependency manifest found, not scanned for vulnerabilities here): not applicable — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Gradle build (build.gradle/build.gradle.kts) — not scanned yet). | 0 | — |
| D31 · IaC & Container Security | trivy | — | trivy config --format json --quiet . | 344 | artifacts/raw/trivy-config.json |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. | 0 | — |
| D36 · Supply-chain Provenance & Signing | provenance | — | provenance: not applicable — No CI/build pipeline found (.github/.forgejo/.gitea workflows, .circleci, .buildkite, .woodpecker, .teamcity, .gitlab-ci.yml, .travis.yml, bitbucket-pipelines.yml, .drone.yml, .cirrus.yml, .woodpecker.yml, appveyor.yml, azure-pipelines*.yml, .pipelines/, .vsts-ci/, .azuredevops/, Jenkinsfile); there is no build to attest provenance for. | 0 | — |
| D37 · Vulnerability-disclosure Policy | disclosure | — | disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — The repository ships application workloads but no cluster-governance resources (CRDs, admission webhooks, or a committed policy engine). Runtime threat-detection (Falco/Tetragon) and admission control (Kyverno/OPA-Gatekeeper/PodSecurity) are cluster-OPERATOR controls owned by the platform, not shipped by an application repo/chart — nothing for this repo to assess. | 0 | — |
| D43 · Malicious Dependencies | none (dependency manifest found, not scanned for vulnerabilities here) | — | none (dependency manifest found, not scanned for vulnerabilities here): not applicable — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Gradle build (build.gradle/build.gradle.kts) — not scanned yet). | 0 | — |