Executive summary
nestjslatam/ddd is rated At risk because critical security findings are open, most of them in the build pipeline. Its score is held back because three passwords or keys sit in the current code and it has uses of packages that aren't listed. It scores 60 out of 100, which the At risk rating leaves unchanged.
Production Readiness, at 55, is the weakest lens and counts most in the score. The best first step is replacing the three exposed passwords or keys and switching the old ones off, worth about 5 points. Tidying the declared packages comes next, worth about 4 points. Raising Production Readiness to 70 would lift the score to about 64.
Twenty-one pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Ten known security holes in the packages the code depends on can be used by attackers, and three passwords or keys in the code and two in the code's history are open to anyone who can read the repository. Pinning each tool to an exact version, updating the vulnerable packages and replacing each exposed password or key would close these risks. Limiting each secret to its own step would fix the two secrets exposed to more of the pipeline than needed, and the two unsafe settings in infrastructure or container files need changing to safe values. The five loops of files that import each other need breaking.
The product code is 10,786 lines, about €36,000 to rebuild. The check for the health of its packages couldn't finish, so that result is missing, not a clean pass.
If Production Readiness rose from 55 to 70, the lowest score rated Strong, the score would rise from 60 to about 64.
New since the last survey: 6 findings
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
Fixed since the last survey: 2 findings
- Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · Medium CVE: [GHSA redacted] REDACTED
Rebuild cost: about €36,000 · Estimate
| Cost to rebuild | €12,000 to €60,000, for 200 to 635 hours of work, about 0.2 person-years for one engineer |
|---|---|
| Difficulty of the problem | High, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.8 at a score of 60. 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: 10,786 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 libs.ddd.src.core.business-rules.impl.broken-rule | 2 libs.ddd.src.core.tracking-state.interfaces.itracking-state-manager | 3 src.orders.application.use-cases.add-item-to-order.add-item-to-order_dto | 4 src.orders.application.use-cases.cancel-order.cancel-order_dto | 5 src.orders.application.use-cases.change-item-quantity.change-item-quantity_dto | 6 src.orders.application.use-cases.create-order.create-order_dto | 7 src.orders.application.use-cases.ship-order.ship-order_dto | 8 src.orders.domain.order-aggregate.order-status_enum | 9 src.products.application.use-cases.change-product-status.change-product-status_dto | 10 src.products.application.use-cases.create-product.create-product-dto | 11 src.products.application.use-cases.update-product.update-product_dto | 12 src.shared.valueobjects.price | 13 libs.ddd.src.core.business-rules.impl.broken-rules-extension | 14 libs.ddd.src.core.business-rules.impl.property-change.notify-property-changed_context | 15 libs.ddd.src.core.tracking-state.interfaces.ichange-detector | 16 libs.ddd.src.core.validator-rules.impl.abstract-rule-validator | 17 libs.ddd.src.validator-rule_manager | 18 src.orders.presentation.orders_controller | 19 src.products.presentation.products_controller | 20 libs.ddd.src.broken-rules_manager | 21 libs.ddd.src.core.business-rules.impl.property-change.notify-property-changed_base | 22 libs.ddd.src.tracking-state-manager | 23 libs.ddd.src.core.aggregate.aggregate-validation-orchestrator | 24 libs.ddd.src.valueobject | 25 libs.ddd.src.valueobjects.id_valueobject | 26 libs.ddd.src.valueobjects.string_valueobject | 27 src.orders.domain.value-objects.money_vo | 28 libs.ddd.src.aggregate-root | 29 libs.ddd.src.core.aggregate.aggregate-identity | 30 libs.ddd.src.core.aggregate.aggregate-serializer | 31 src.orders.domain.entities.order-item_entity | 32 src.orders.domain.events.order_events | 33 src.shared.valueobjects.Name | 34 src.shared.valueobjects.description | 35 src.orders.domain.order-aggregate.order | 36 src.products.domain.product-aggregate.product | 37 src.orders.infrastructure.repositories.order_repository | 38 src.products.infrastructure.repositories.product_repository | 39 src.orders.application.queries.get-order.get-order_query-handler | 40 src.products.application.queries.get-product.get-product_query-handler |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 libs.ddd.src.core.business-rules.impl.broken-rule | ||||||||||||||||||||||||||||||||||||||||
| 2 libs.ddd.src.core.tracking-state.interfaces.itracking-state-manager | ||||||||||||||||||||||||||||||||||||||||
| 3 src.orders.application.use-cases.add-item-to-order.add-item-to-order_dto | ||||||||||||||||||||||||||||||||||||||||
| 4 src.orders.application.use-cases.cancel-order.cancel-order_dto | ||||||||||||||||||||||||||||||||||||||||
| 5 src.orders.application.use-cases.change-item-quantity.change-item-quantity_dto | ||||||||||||||||||||||||||||||||||||||||
| 6 src.orders.application.use-cases.create-order.create-order_dto | ||||||||||||||||||||||||||||||||||||||||
| 7 src.orders.application.use-cases.ship-order.ship-order_dto | ||||||||||||||||||||||||||||||||||||||||
| 8 src.orders.domain.order-aggregate.order-status_enum | ||||||||||||||||||||||||||||||||||||||||
| 9 src.products.application.use-cases.change-product-status.change-product-status_dto | ||||||||||||||||||||||||||||||||||||||||
| 10 src.products.application.use-cases.create-product.create-product-dto | ||||||||||||||||||||||||||||||||||||||||
| 11 src.products.application.use-cases.update-product.update-product_dto | ||||||||||||||||||||||||||||||||||||||||
| 12 src.shared.valueobjects.price | ||||||||||||||||||||||||||||||||||||||||
| 13 libs.ddd.src.core.business-rules.impl.broken-rules-extension | 2 | |||||||||||||||||||||||||||||||||||||||
| 14 libs.ddd.src.core.business-rules.impl.property-change.notify-property-changed_context | 1 | |||||||||||||||||||||||||||||||||||||||
| 15 libs.ddd.src.core.tracking-state.interfaces.ichange-detector | 1 | |||||||||||||||||||||||||||||||||||||||
| 16 libs.ddd.src.core.validator-rules.impl.abstract-rule-validator | 1 | |||||||||||||||||||||||||||||||||||||||
| 17 libs.ddd.src.validator-rule_manager | 1 | |||||||||||||||||||||||||||||||||||||||
| 18 src.orders.presentation.orders_controller | 1 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 19 src.products.presentation.products_controller | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 20 libs.ddd.src.broken-rules_manager | 2 | 1 | ||||||||||||||||||||||||||||||||||||||
| 21 libs.ddd.src.core.business-rules.impl.property-change.notify-property-changed_base | 1 | |||||||||||||||||||||||||||||||||||||||
| 22 libs.ddd.src.tracking-state-manager | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 23 libs.ddd.src.core.aggregate.aggregate-validation-orchestrator | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 24 libs.ddd.src.valueobject | 1 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 25 libs.ddd.src.valueobjects.id_valueobject | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 26 libs.ddd.src.valueobjects.string_valueobject | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 27 src.orders.domain.value-objects.money_vo | 1 | |||||||||||||||||||||||||||||||||||||||
| 28 libs.ddd.src.aggregate-root | 1 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 29 libs.ddd.src.core.aggregate.aggregate-identity | 1 | |||||||||||||||||||||||||||||||||||||||
| 30 libs.ddd.src.core.aggregate.aggregate-serializer | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 31 src.orders.domain.entities.order-item_entity | 1 | 2 | 2 | |||||||||||||||||||||||||||||||||||||
| 32 src.orders.domain.events.order_events | 1 | 9 | ||||||||||||||||||||||||||||||||||||||
| 33 src.shared.valueobjects.Name | 1 | |||||||||||||||||||||||||||||||||||||||
| 34 src.shared.valueobjects.description | 1 | |||||||||||||||||||||||||||||||||||||||
| 35 src.orders.domain.order-aggregate.order | 2 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 36 src.products.domain.product-aggregate.product | 2 | 1 | 1 | 2 | 2 | |||||||||||||||||||||||||||||||||||
| 37 src.orders.infrastructure.repositories.order_repository | 1 | |||||||||||||||||||||||||||||||||||||||
| 38 src.products.infrastructure.repositories.product_repository | 1 | |||||||||||||||||||||||||||||||||||||||
| 39 src.orders.application.queries.get-order.get-order_query-handler | 1 | |||||||||||||||||||||||||||||||||||||||
| 40 src.products.application.queries.get-product.get-product_query-handler | 1 |
13→1 libs.ddd.src.core.business-rules.impl.broken-rules-extension uses libs.ddd.src.core.business-rules.impl.broken-rule✕
- Connections
- 2 pairs of types, where a type in libs.ddd.src.core.business-rules.impl.broken-rules-extension uses a type in libs.ddd.src.core.business-rules.impl.broken-rule.
- The types involved
libs.ddd.src.core.business-rules.impl.broken-rules-extension.BrokenRulesExtension→libs.ddd.src.core.business-rules.impl.broken-rule.BrokenRulelibs.ddd.src.core.business-rules.impl.broken-rules-extension.IBrokenRulesManager→libs.ddd.src.core.business-rules.impl.broken-rule.BrokenRule
- Direction
- libs.ddd.src.core.business-rules.impl.broken-rules-extension uses libs.ddd.src.core.business-rules.impl.broken-rule, so a change to libs.ddd.src.core.business-rules.impl.broken-rule can break libs.ddd.src.core.business-rules.impl.broken-rules-extension, while a change to libs.ddd.src.core.business-rules.impl.broken-rules-extension can't break libs.ddd.src.core.business-rules.impl.broken-rule.
- Position
- Below the diagonal: libs.ddd.src.core.business-rules.impl.broken-rules-extension uses a module listed above it, which is the healthy direction.
14→21 libs.ddd.src.core.business-rules.impl.property-change.notify-property-changed_context uses libs.ddd.src.core.business-rules.impl.property-change.notify-property-changed_base part of a loop✕
- Connections
- 1 pair of types, where a type in libs.ddd.src.core.business-rules.impl.property-change.notify-property-changed_context uses a type in libs.ddd.src.core.business-rules.impl.property-change.notify-property-changed_base.
- The types involved
libs.ddd.src.core.business-rules.impl.property-change.notify-property-changed_context.NotifyPropertyChangedContext→libs.ddd.src.core.business-rules.impl.property-change.notify-property-changed_base.AbstractNotifyPropertyChanged
- Direction
- libs.ddd.src.core.business-rules.impl.property-change.notify-property-changed_context uses libs.ddd.src.core.business-rules.impl.property-change.notify-property-changed_base, so a change to libs.ddd.src.core.business-rules.impl.property-change.notify-property-changed_base can break libs.ddd.src.core.business-rules.impl.property-change.notify-property-changed_context, while a change to libs.ddd.src.core.business-rules.impl.property-change.notify-property-changed_context can't break libs.ddd.src.core.business-rules.impl.property-change.notify-property-changed_base.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
15→2 libs.ddd.src.core.tracking-state.interfaces.ichange-detector uses libs.ddd.src.core.tracking-state.interfaces.itracking-state-manager✕
- Connections
- 1 pair of types, where a type in libs.ddd.src.core.tracking-state.interfaces.ichange-detector uses a type in libs.ddd.src.core.tracking-state.interfaces.itracking-state-manager.
- The types involved
libs.ddd.src.core.tracking-state.interfaces.ichange-detector.IChangeDetector→libs.ddd.src.core.tracking-state.interfaces.itracking-state-manager.ITrackingStateManager
- Direction
- libs.ddd.src.core.tracking-state.interfaces.ichange-detector uses libs.ddd.src.core.tracking-state.interfaces.itracking-state-manager, so a change to libs.ddd.src.core.tracking-state.interfaces.itracking-state-manager can break libs.ddd.src.core.tracking-state.interfaces.ichange-detector, while a change to libs.ddd.src.core.tracking-state.interfaces.ichange-detector can't break libs.ddd.src.core.tracking-state.interfaces.itracking-state-manager.
- Position
- Below the diagonal: libs.ddd.src.core.tracking-state.interfaces.ichange-detector uses a module listed above it, which is the healthy direction.
16→1 libs.ddd.src.core.validator-rules.impl.abstract-rule-validator uses libs.ddd.src.core.business-rules.impl.broken-rule✕
- Connections
- 1 pair of types, where a type in libs.ddd.src.core.validator-rules.impl.abstract-rule-validator uses a type in libs.ddd.src.core.business-rules.impl.broken-rule.
- The types involved
libs.ddd.src.core.validator-rules.impl.abstract-rule-validator.AbstractRuleValidator→libs.ddd.src.core.business-rules.impl.broken-rule.BrokenRule
- Direction
- libs.ddd.src.core.validator-rules.impl.abstract-rule-validator uses libs.ddd.src.core.business-rules.impl.broken-rule, so a change to libs.ddd.src.core.business-rules.impl.broken-rule can break libs.ddd.src.core.validator-rules.impl.abstract-rule-validator, while a change to libs.ddd.src.core.validator-rules.impl.abstract-rule-validator can't break libs.ddd.src.core.business-rules.impl.broken-rule.
- Position
- Below the diagonal: libs.ddd.src.core.validator-rules.impl.abstract-rule-validator uses a module listed above it, which is the healthy direction.
17→1 libs.ddd.src.validator-rule_manager uses libs.ddd.src.core.business-rules.impl.broken-rule✕
- Connections
- 1 pair of types, where a type in libs.ddd.src.validator-rule_manager uses a type in libs.ddd.src.core.business-rules.impl.broken-rule.
- The types involved
libs.ddd.src.validator-rule_manager.ValidatorRuleManager→libs.ddd.src.core.business-rules.impl.broken-rule.BrokenRule
- Direction
- libs.ddd.src.validator-rule_manager uses libs.ddd.src.core.business-rules.impl.broken-rule, so a change to libs.ddd.src.core.business-rules.impl.broken-rule can break libs.ddd.src.validator-rule_manager, while a change to libs.ddd.src.validator-rule_manager can't break libs.ddd.src.core.business-rules.impl.broken-rule.
- Position
- Below the diagonal: libs.ddd.src.validator-rule_manager uses a module listed above it, which is the healthy direction.
18→3 src.orders.presentation.orders_controller uses src.orders.application.use-cases.add-item-to-order.add-item-to-order_dto✕
- Connections
- 1 pair of types, where a type in src.orders.presentation.orders_controller uses a type in src.orders.application.use-cases.add-item-to-order.add-item-to-order_dto.
- The types involved
src.orders.presentation.orders_controller.OrdersController→src.orders.application.use-cases.add-item-to-order.add-item-to-order_dto.AddItemToOrderBodyDto
- Direction
- src.orders.presentation.orders_controller uses src.orders.application.use-cases.add-item-to-order.add-item-to-order_dto, so a change to src.orders.application.use-cases.add-item-to-order.add-item-to-order_dto can break src.orders.presentation.orders_controller, while a change to src.orders.presentation.orders_controller can't break src.orders.application.use-cases.add-item-to-order.add-item-to-order_dto.
- Position
- Below the diagonal: src.orders.presentation.orders_controller uses a module listed above it, which is the healthy direction.
18→4 src.orders.presentation.orders_controller uses src.orders.application.use-cases.cancel-order.cancel-order_dto✕
- Connections
- 1 pair of types, where a type in src.orders.presentation.orders_controller uses a type in src.orders.application.use-cases.cancel-order.cancel-order_dto.
- The types involved
src.orders.presentation.orders_controller.OrdersController→src.orders.application.use-cases.cancel-order.cancel-order_dto.CancelOrderBodyDto
- Direction
- src.orders.presentation.orders_controller uses src.orders.application.use-cases.cancel-order.cancel-order_dto, so a change to src.orders.application.use-cases.cancel-order.cancel-order_dto can break src.orders.presentation.orders_controller, while a change to src.orders.presentation.orders_controller can't break src.orders.application.use-cases.cancel-order.cancel-order_dto.
- Position
- Below the diagonal: src.orders.presentation.orders_controller uses a module listed above it, which is the healthy direction.
18→5 src.orders.presentation.orders_controller uses src.orders.application.use-cases.change-item-quantity.change-item-quantity_dto✕
- Connections
- 1 pair of types, where a type in src.orders.presentation.orders_controller uses a type in src.orders.application.use-cases.change-item-quantity.change-item-quantity_dto.
- The types involved
src.orders.presentation.orders_controller.OrdersController→src.orders.application.use-cases.change-item-quantity.change-item-quantity_dto.ChangeItemQuantityBodyDto
- Direction
- src.orders.presentation.orders_controller uses src.orders.application.use-cases.change-item-quantity.change-item-quantity_dto, so a change to src.orders.application.use-cases.change-item-quantity.change-item-quantity_dto can break src.orders.presentation.orders_controller, while a change to src.orders.presentation.orders_controller can't break src.orders.application.use-cases.change-item-quantity.change-item-quantity_dto.
- Position
- Below the diagonal: src.orders.presentation.orders_controller uses a module listed above it, which is the healthy direction.
18→6 src.orders.presentation.orders_controller uses src.orders.application.use-cases.create-order.create-order_dto✕
- Connections
- 1 pair of types, where a type in src.orders.presentation.orders_controller uses a type in src.orders.application.use-cases.create-order.create-order_dto.
- The types involved
src.orders.presentation.orders_controller.OrdersController→src.orders.application.use-cases.create-order.create-order_dto.CreateOrderDto
- Direction
- src.orders.presentation.orders_controller uses src.orders.application.use-cases.create-order.create-order_dto, so a change to src.orders.application.use-cases.create-order.create-order_dto can break src.orders.presentation.orders_controller, while a change to src.orders.presentation.orders_controller can't break src.orders.application.use-cases.create-order.create-order_dto.
- Position
- Below the diagonal: src.orders.presentation.orders_controller uses a module listed above it, which is the healthy direction.
18→7 src.orders.presentation.orders_controller uses src.orders.application.use-cases.ship-order.ship-order_dto✕
- Connections
- 1 pair of types, where a type in src.orders.presentation.orders_controller uses a type in src.orders.application.use-cases.ship-order.ship-order_dto.
- The types involved
src.orders.presentation.orders_controller.OrdersController→src.orders.application.use-cases.ship-order.ship-order_dto.ShipOrderBodyDto
- Direction
- src.orders.presentation.orders_controller uses src.orders.application.use-cases.ship-order.ship-order_dto, so a change to src.orders.application.use-cases.ship-order.ship-order_dto can break src.orders.presentation.orders_controller, while a change to src.orders.presentation.orders_controller can't break src.orders.application.use-cases.ship-order.ship-order_dto.
- Position
- Below the diagonal: src.orders.presentation.orders_controller uses a module listed above it, which is the healthy direction.
19→9 src.products.presentation.products_controller uses src.products.application.use-cases.change-product-status.change-product-status_dto✕
- Connections
- 1 pair of types, where a type in src.products.presentation.products_controller uses a type in src.products.application.use-cases.change-product-status.change-product-status_dto.
- The types involved
src.products.presentation.products_controller.ProductsController→src.products.application.use-cases.change-product-status.change-product-status_dto.ChangeProductStatusDto
- Direction
- src.products.presentation.products_controller uses src.products.application.use-cases.change-product-status.change-product-status_dto, so a change to src.products.application.use-cases.change-product-status.change-product-status_dto can break src.products.presentation.products_controller, while a change to src.products.presentation.products_controller can't break src.products.application.use-cases.change-product-status.change-product-status_dto.
- Position
- Below the diagonal: src.products.presentation.products_controller uses a module listed above it, which is the healthy direction.
19→10 src.products.presentation.products_controller uses src.products.application.use-cases.create-product.create-product-dto✕
- Connections
- 1 pair of types, where a type in src.products.presentation.products_controller uses a type in src.products.application.use-cases.create-product.create-product-dto.
- The types involved
src.products.presentation.products_controller.ProductsController→src.products.application.use-cases.create-product.create-product-dto.CreateProductDto
- Direction
- src.products.presentation.products_controller uses src.products.application.use-cases.create-product.create-product-dto, so a change to src.products.application.use-cases.create-product.create-product-dto can break src.products.presentation.products_controller, while a change to src.products.presentation.products_controller can't break src.products.application.use-cases.create-product.create-product-dto.
- Position
- Below the diagonal: src.products.presentation.products_controller uses a module listed above it, which is the healthy direction.
19→11 src.products.presentation.products_controller uses src.products.application.use-cases.update-product.update-product_dto✕
- Connections
- 1 pair of types, where a type in src.products.presentation.products_controller uses a type in src.products.application.use-cases.update-product.update-product_dto.
- The types involved
src.products.presentation.products_controller.ProductsController→src.products.application.use-cases.update-product.update-product_dto.UpdateProductDto
- Direction
- src.products.presentation.products_controller uses src.products.application.use-cases.update-product.update-product_dto, so a change to src.products.application.use-cases.update-product.update-product_dto can break src.products.presentation.products_controller, while a change to src.products.presentation.products_controller can't break src.products.application.use-cases.update-product.update-product_dto.
- Position
- Below the diagonal: src.products.presentation.products_controller uses a module listed above it, which is the healthy direction.
20→1 libs.ddd.src.broken-rules_manager uses libs.ddd.src.core.business-rules.impl.broken-rule✕
- Connections
- 2 pairs of types, where a type in libs.ddd.src.broken-rules_manager uses a type in libs.ddd.src.core.business-rules.impl.broken-rule.
- The types involved
libs.ddd.src.broken-rules_manager.BrokenRulesManager→libs.ddd.src.core.business-rules.impl.broken-rule.BrokenRulelibs.ddd.src.broken-rules_manager.IBrokenRulesManager→libs.ddd.src.core.business-rules.impl.broken-rule.BrokenRule
- Direction
- libs.ddd.src.broken-rules_manager uses libs.ddd.src.core.business-rules.impl.broken-rule, so a change to libs.ddd.src.core.business-rules.impl.broken-rule can break libs.ddd.src.broken-rules_manager, while a change to libs.ddd.src.broken-rules_manager can't break libs.ddd.src.core.business-rules.impl.broken-rule.
- Position
- Below the diagonal: libs.ddd.src.broken-rules_manager uses a module listed above it, which is the healthy direction.
20→13 libs.ddd.src.broken-rules_manager uses libs.ddd.src.core.business-rules.impl.broken-rules-extension✕
- Connections
- 1 pair of types, where a type in libs.ddd.src.broken-rules_manager uses a type in libs.ddd.src.core.business-rules.impl.broken-rules-extension.
- The types involved
libs.ddd.src.broken-rules_manager.BrokenRulesManager→libs.ddd.src.core.business-rules.impl.broken-rules-extension.IBrokenRulesManager
- Direction
- libs.ddd.src.broken-rules_manager uses libs.ddd.src.core.business-rules.impl.broken-rules-extension, so a change to libs.ddd.src.core.business-rules.impl.broken-rules-extension can break libs.ddd.src.broken-rules_manager, while a change to libs.ddd.src.broken-rules_manager can't break libs.ddd.src.core.business-rules.impl.broken-rules-extension.
- Position
- Below the diagonal: libs.ddd.src.broken-rules_manager uses a module listed above it, which is the healthy direction.
21→14 libs.ddd.src.core.business-rules.impl.property-change.notify-property-changed_base uses libs.ddd.src.core.business-rules.impl.property-change.notify-property-changed_context✕
- Connections
- 1 pair of types, where a type in libs.ddd.src.core.business-rules.impl.property-change.notify-property-changed_base uses a type in libs.ddd.src.core.business-rules.impl.property-change.notify-property-changed_context.
- The types involved
libs.ddd.src.core.business-rules.impl.property-change.notify-property-changed_base.AbstractNotifyPropertyChanged→libs.ddd.src.core.business-rules.impl.property-change.notify-property-changed_context.NotifyPropertyChangedContext
- Direction
- libs.ddd.src.core.business-rules.impl.property-change.notify-property-changed_base uses libs.ddd.src.core.business-rules.impl.property-change.notify-property-changed_context, so a change to libs.ddd.src.core.business-rules.impl.property-change.notify-property-changed_context can break libs.ddd.src.core.business-rules.impl.property-change.notify-property-changed_base, while a change to libs.ddd.src.core.business-rules.impl.property-change.notify-property-changed_base can't break libs.ddd.src.core.business-rules.impl.property-change.notify-property-changed_context.
- Position
- Below the diagonal: libs.ddd.src.core.business-rules.impl.property-change.notify-property-changed_base uses a module listed above it, which is the healthy direction.
22→2 libs.ddd.src.tracking-state-manager uses libs.ddd.src.core.tracking-state.interfaces.itracking-state-manager✕
- Connections
- 1 pair of types, where a type in libs.ddd.src.tracking-state-manager uses a type in libs.ddd.src.core.tracking-state.interfaces.itracking-state-manager.
- The types involved
libs.ddd.src.tracking-state-manager.TrackingStateManager→libs.ddd.src.core.tracking-state.interfaces.itracking-state-manager.ITrackingStateManager
- Direction
- libs.ddd.src.tracking-state-manager uses libs.ddd.src.core.tracking-state.interfaces.itracking-state-manager, so a change to libs.ddd.src.core.tracking-state.interfaces.itracking-state-manager can break libs.ddd.src.tracking-state-manager, while a change to libs.ddd.src.tracking-state-manager can't break libs.ddd.src.core.tracking-state.interfaces.itracking-state-manager.
- Position
- Below the diagonal: libs.ddd.src.tracking-state-manager uses a module listed above it, which is the healthy direction.
22→15 libs.ddd.src.tracking-state-manager uses libs.ddd.src.core.tracking-state.interfaces.ichange-detector✕
- Connections
- 1 pair of types, where a type in libs.ddd.src.tracking-state-manager uses a type in libs.ddd.src.core.tracking-state.interfaces.ichange-detector.
- The types involved
libs.ddd.src.tracking-state-manager.TrackingStateManager→libs.ddd.src.core.tracking-state.interfaces.ichange-detector.IChangeDetector
- Direction
- libs.ddd.src.tracking-state-manager uses libs.ddd.src.core.tracking-state.interfaces.ichange-detector, so a change to libs.ddd.src.core.tracking-state.interfaces.ichange-detector can break libs.ddd.src.tracking-state-manager, while a change to libs.ddd.src.tracking-state-manager can't break libs.ddd.src.core.tracking-state.interfaces.ichange-detector.
- Position
- Below the diagonal: libs.ddd.src.tracking-state-manager uses a module listed above it, which is the healthy direction.
23→16 libs.ddd.src.core.aggregate.aggregate-validation-orchestrator uses libs.ddd.src.core.validator-rules.impl.abstract-rule-validator✕
- Connections
- 1 pair of types, where a type in libs.ddd.src.core.aggregate.aggregate-validation-orchestrator uses a type in libs.ddd.src.core.validator-rules.impl.abstract-rule-validator.
- The types involved
libs.ddd.src.core.aggregate.aggregate-validation-orchestrator.AggregateValidationOrchestrator→libs.ddd.src.core.validator-rules.impl.abstract-rule-validator.AbstractRuleValidator
- Direction
- libs.ddd.src.core.aggregate.aggregate-validation-orchestrator uses libs.ddd.src.core.validator-rules.impl.abstract-rule-validator, so a change to libs.ddd.src.core.validator-rules.impl.abstract-rule-validator can break libs.ddd.src.core.aggregate.aggregate-validation-orchestrator, while a change to libs.ddd.src.core.aggregate.aggregate-validation-orchestrator can't break libs.ddd.src.core.validator-rules.impl.abstract-rule-validator.
- Position
- Below the diagonal: libs.ddd.src.core.aggregate.aggregate-validation-orchestrator uses a module listed above it, which is the healthy direction.
23→17 libs.ddd.src.core.aggregate.aggregate-validation-orchestrator uses libs.ddd.src.validator-rule_manager✕
- Connections
- 1 pair of types, where a type in libs.ddd.src.core.aggregate.aggregate-validation-orchestrator uses a type in libs.ddd.src.validator-rule_manager.
- The types involved
libs.ddd.src.core.aggregate.aggregate-validation-orchestrator.AggregateValidationOrchestrator→libs.ddd.src.validator-rule_manager.ValidatorRuleManager
- Direction
- libs.ddd.src.core.aggregate.aggregate-validation-orchestrator uses libs.ddd.src.validator-rule_manager, so a change to libs.ddd.src.validator-rule_manager can break libs.ddd.src.core.aggregate.aggregate-validation-orchestrator, while a change to libs.ddd.src.core.aggregate.aggregate-validation-orchestrator can't break libs.ddd.src.validator-rule_manager.
- Position
- Below the diagonal: libs.ddd.src.core.aggregate.aggregate-validation-orchestrator uses a module listed above it, which is the healthy direction.
23→20 libs.ddd.src.core.aggregate.aggregate-validation-orchestrator uses libs.ddd.src.broken-rules_manager✕
- Connections
- 1 pair of types, where a type in libs.ddd.src.core.aggregate.aggregate-validation-orchestrator uses a type in libs.ddd.src.broken-rules_manager.
- The types involved
libs.ddd.src.core.aggregate.aggregate-validation-orchestrator.AggregateValidationOrchestrator→libs.ddd.src.broken-rules_manager.BrokenRulesManager
- Direction
- libs.ddd.src.core.aggregate.aggregate-validation-orchestrator uses libs.ddd.src.broken-rules_manager, so a change to libs.ddd.src.broken-rules_manager can break libs.ddd.src.core.aggregate.aggregate-validation-orchestrator, while a change to libs.ddd.src.core.aggregate.aggregate-validation-orchestrator can't break libs.ddd.src.broken-rules_manager.
- Position
- Below the diagonal: libs.ddd.src.core.aggregate.aggregate-validation-orchestrator uses a module listed above it, which is the healthy direction.
24→16 libs.ddd.src.valueobject uses libs.ddd.src.core.validator-rules.impl.abstract-rule-validator✕
- Connections
- 1 pair of types, where a type in libs.ddd.src.valueobject uses a type in libs.ddd.src.core.validator-rules.impl.abstract-rule-validator.
- The types involved
libs.ddd.src.valueobject.DddValueObject→libs.ddd.src.core.validator-rules.impl.abstract-rule-validator.AbstractRuleValidator
- Direction
- libs.ddd.src.valueobject uses libs.ddd.src.core.validator-rules.impl.abstract-rule-validator, so a change to libs.ddd.src.core.validator-rules.impl.abstract-rule-validator can break libs.ddd.src.valueobject, while a change to libs.ddd.src.valueobject can't break libs.ddd.src.core.validator-rules.impl.abstract-rule-validator.
- Position
- Below the diagonal: libs.ddd.src.valueobject uses a module listed above it, which is the healthy direction.
24→17 libs.ddd.src.valueobject uses libs.ddd.src.validator-rule_manager✕
- Connections
- 1 pair of types, where a type in libs.ddd.src.valueobject uses a type in libs.ddd.src.validator-rule_manager.
- The types involved
libs.ddd.src.valueobject.DddValueObject→libs.ddd.src.validator-rule_manager.ValidatorRuleManager
- Direction
- libs.ddd.src.valueobject uses libs.ddd.src.validator-rule_manager, so a change to libs.ddd.src.validator-rule_manager can break libs.ddd.src.valueobject, while a change to libs.ddd.src.valueobject can't break libs.ddd.src.validator-rule_manager.
- Position
- Below the diagonal: libs.ddd.src.valueobject uses a module listed above it, which is the healthy direction.
24→20 libs.ddd.src.valueobject uses libs.ddd.src.broken-rules_manager✕
- Connections
- 1 pair of types, where a type in libs.ddd.src.valueobject uses a type in libs.ddd.src.broken-rules_manager.
- The types involved
libs.ddd.src.valueobject.DddValueObject→libs.ddd.src.broken-rules_manager.BrokenRulesManager
- Direction
- libs.ddd.src.valueobject uses libs.ddd.src.broken-rules_manager, so a change to libs.ddd.src.broken-rules_manager can break libs.ddd.src.valueobject, while a change to libs.ddd.src.valueobject can't break libs.ddd.src.broken-rules_manager.
- Position
- Below the diagonal: libs.ddd.src.valueobject uses a module listed above it, which is the healthy direction.
24→21 libs.ddd.src.valueobject uses libs.ddd.src.core.business-rules.impl.property-change.notify-property-changed_base✕
- Connections
- 1 pair of types, where a type in libs.ddd.src.valueobject uses a type in libs.ddd.src.core.business-rules.impl.property-change.notify-property-changed_base.
- The types involved
libs.ddd.src.valueobject.DddValueObject→libs.ddd.src.core.business-rules.impl.property-change.notify-property-changed_base.AbstractNotifyPropertyChanged
- Direction
- libs.ddd.src.valueobject uses libs.ddd.src.core.business-rules.impl.property-change.notify-property-changed_base, so a change to libs.ddd.src.core.business-rules.impl.property-change.notify-property-changed_base can break libs.ddd.src.valueobject, while a change to libs.ddd.src.valueobject can't break libs.ddd.src.core.business-rules.impl.property-change.notify-property-changed_base.
- Position
- Below the diagonal: libs.ddd.src.valueobject uses a module listed above it, which is the healthy direction.
24→22 libs.ddd.src.valueobject uses libs.ddd.src.tracking-state-manager✕
- Connections
- 1 pair of types, where a type in libs.ddd.src.valueobject uses a type in libs.ddd.src.tracking-state-manager.
- The types involved
libs.ddd.src.valueobject.DddValueObject→libs.ddd.src.tracking-state-manager.TrackingStateManager
- Direction
- libs.ddd.src.valueobject uses libs.ddd.src.tracking-state-manager, so a change to libs.ddd.src.tracking-state-manager can break libs.ddd.src.valueobject, while a change to libs.ddd.src.valueobject can't break libs.ddd.src.tracking-state-manager.
- Position
- Below the diagonal: libs.ddd.src.valueobject uses a module listed above it, which is the healthy direction.
25→16 libs.ddd.src.valueobjects.id_valueobject uses libs.ddd.src.core.validator-rules.impl.abstract-rule-validator✕
- Connections
- 1 pair of types, where a type in libs.ddd.src.valueobjects.id_valueobject uses a type in libs.ddd.src.core.validator-rules.impl.abstract-rule-validator.
- The types involved
libs.ddd.src.valueobjects.id_valueobject.UuidFormatValidator→libs.ddd.src.core.validator-rules.impl.abstract-rule-validator.AbstractRuleValidator
- Direction
- libs.ddd.src.valueobjects.id_valueobject uses libs.ddd.src.core.validator-rules.impl.abstract-rule-validator, so a change to libs.ddd.src.core.validator-rules.impl.abstract-rule-validator can break libs.ddd.src.valueobjects.id_valueobject, while a change to libs.ddd.src.valueobjects.id_valueobject can't break libs.ddd.src.core.validator-rules.impl.abstract-rule-validator.
- Position
- Below the diagonal: libs.ddd.src.valueobjects.id_valueobject uses a module listed above it, which is the healthy direction.
25→24 libs.ddd.src.valueobjects.id_valueobject uses libs.ddd.src.valueobject✕
- Connections
- 1 pair of types, where a type in libs.ddd.src.valueobjects.id_valueobject uses a type in libs.ddd.src.valueobject.
- The types involved
libs.ddd.src.valueobjects.id_valueobject.IdValueObject→libs.ddd.src.valueobject.DddValueObject
- Direction
- libs.ddd.src.valueobjects.id_valueobject uses libs.ddd.src.valueobject, so a change to libs.ddd.src.valueobject can break libs.ddd.src.valueobjects.id_valueobject, while a change to libs.ddd.src.valueobjects.id_valueobject can't break libs.ddd.src.valueobject.
- Position
- Below the diagonal: libs.ddd.src.valueobjects.id_valueobject uses a module listed above it, which is the healthy direction.
26→16 libs.ddd.src.valueobjects.string_valueobject uses libs.ddd.src.core.validator-rules.impl.abstract-rule-validator✕
- Connections
- 1 pair of types, where a type in libs.ddd.src.valueobjects.string_valueobject uses a type in libs.ddd.src.core.validator-rules.impl.abstract-rule-validator.
- The types involved
libs.ddd.src.valueobjects.string_valueobject.StringMaxLengthValidator→libs.ddd.src.core.validator-rules.impl.abstract-rule-validator.AbstractRuleValidator
- Direction
- libs.ddd.src.valueobjects.string_valueobject uses libs.ddd.src.core.validator-rules.impl.abstract-rule-validator, so a change to libs.ddd.src.core.validator-rules.impl.abstract-rule-validator can break libs.ddd.src.valueobjects.string_valueobject, while a change to libs.ddd.src.valueobjects.string_valueobject can't break libs.ddd.src.core.validator-rules.impl.abstract-rule-validator.
- Position
- Below the diagonal: libs.ddd.src.valueobjects.string_valueobject uses a module listed above it, which is the healthy direction.
26→24 libs.ddd.src.valueobjects.string_valueobject uses libs.ddd.src.valueobject✕
- Connections
- 2 pairs of types, where a type in libs.ddd.src.valueobjects.string_valueobject uses a type in libs.ddd.src.valueobject.
- The types involved
libs.ddd.src.valueobjects.string_valueobject.StringMaxLengthValidator→libs.ddd.src.valueobject.DddValueObjectlibs.ddd.src.valueobjects.string_valueobject.StringValueObject→libs.ddd.src.valueobject.DddValueObject
- Direction
- libs.ddd.src.valueobjects.string_valueobject uses libs.ddd.src.valueobject, so a change to libs.ddd.src.valueobject can break libs.ddd.src.valueobjects.string_valueobject, while a change to libs.ddd.src.valueobjects.string_valueobject can't break libs.ddd.src.valueobject.
- Position
- Below the diagonal: libs.ddd.src.valueobjects.string_valueobject uses a module listed above it, which is the healthy direction.
27→24 src.orders.domain.value-objects.money_vo uses libs.ddd.src.valueobject✕
- Connections
- 1 pair of types, where a type in src.orders.domain.value-objects.money_vo uses a type in libs.ddd.src.valueobject.
- The types involved
src.orders.domain.value-objects.money_vo.Money→libs.ddd.src.valueobject.DddValueObject
- Direction
- src.orders.domain.value-objects.money_vo uses libs.ddd.src.valueobject, so a change to libs.ddd.src.valueobject can break src.orders.domain.value-objects.money_vo, while a change to src.orders.domain.value-objects.money_vo can't break libs.ddd.src.valueobject.
- Position
- Below the diagonal: src.orders.domain.value-objects.money_vo uses a module listed above it, which is the healthy direction.
28→16 libs.ddd.src.aggregate-root uses libs.ddd.src.core.validator-rules.impl.abstract-rule-validator✕
- Connections
- 1 pair of types, where a type in libs.ddd.src.aggregate-root uses a type in libs.ddd.src.core.validator-rules.impl.abstract-rule-validator.
- The types involved
libs.ddd.src.aggregate-root.DddAggregateRoot→libs.ddd.src.core.validator-rules.impl.abstract-rule-validator.AbstractRuleValidator
- Direction
- libs.ddd.src.aggregate-root uses libs.ddd.src.core.validator-rules.impl.abstract-rule-validator, so a change to libs.ddd.src.core.validator-rules.impl.abstract-rule-validator can break libs.ddd.src.aggregate-root, while a change to libs.ddd.src.aggregate-root can't break libs.ddd.src.core.validator-rules.impl.abstract-rule-validator.
- Position
- Below the diagonal: libs.ddd.src.aggregate-root uses a module listed above it, which is the healthy direction.
28→17 libs.ddd.src.aggregate-root uses libs.ddd.src.validator-rule_manager✕
- Connections
- 1 pair of types, where a type in libs.ddd.src.aggregate-root uses a type in libs.ddd.src.validator-rule_manager.
- The types involved
libs.ddd.src.aggregate-root.DddAggregateRoot→libs.ddd.src.validator-rule_manager.ValidatorRuleManager
- Direction
- libs.ddd.src.aggregate-root uses libs.ddd.src.validator-rule_manager, so a change to libs.ddd.src.validator-rule_manager can break libs.ddd.src.aggregate-root, while a change to libs.ddd.src.aggregate-root can't break libs.ddd.src.validator-rule_manager.
- Position
- Below the diagonal: libs.ddd.src.aggregate-root uses a module listed above it, which is the healthy direction.
28→20 libs.ddd.src.aggregate-root uses libs.ddd.src.broken-rules_manager✕
- Connections
- 1 pair of types, where a type in libs.ddd.src.aggregate-root uses a type in libs.ddd.src.broken-rules_manager.
- The types involved
libs.ddd.src.aggregate-root.DddAggregateRoot→libs.ddd.src.broken-rules_manager.BrokenRulesManager
- Direction
- libs.ddd.src.aggregate-root uses libs.ddd.src.broken-rules_manager, so a change to libs.ddd.src.broken-rules_manager can break libs.ddd.src.aggregate-root, while a change to libs.ddd.src.aggregate-root can't break libs.ddd.src.broken-rules_manager.
- Position
- Below the diagonal: libs.ddd.src.aggregate-root uses a module listed above it, which is the healthy direction.
28→22 libs.ddd.src.aggregate-root uses libs.ddd.src.tracking-state-manager✕
- Connections
- 1 pair of types, where a type in libs.ddd.src.aggregate-root uses a type in libs.ddd.src.tracking-state-manager.
- The types involved
libs.ddd.src.aggregate-root.DddAggregateRoot→libs.ddd.src.tracking-state-manager.TrackingStateManager
- Direction
- libs.ddd.src.aggregate-root uses libs.ddd.src.tracking-state-manager, so a change to libs.ddd.src.tracking-state-manager can break libs.ddd.src.aggregate-root, while a change to libs.ddd.src.aggregate-root can't break libs.ddd.src.tracking-state-manager.
- Position
- Below the diagonal: libs.ddd.src.aggregate-root uses a module listed above it, which is the healthy direction.
28→25 libs.ddd.src.aggregate-root uses libs.ddd.src.valueobjects.id_valueobject✕
- Connections
- 1 pair of types, where a type in libs.ddd.src.aggregate-root uses a type in libs.ddd.src.valueobjects.id_valueobject.
- The types involved
libs.ddd.src.aggregate-root.DddAggregateRoot→libs.ddd.src.valueobjects.id_valueobject.IdValueObject
- Direction
- libs.ddd.src.aggregate-root uses libs.ddd.src.valueobjects.id_valueobject, so a change to libs.ddd.src.valueobjects.id_valueobject can break libs.ddd.src.aggregate-root, while a change to libs.ddd.src.aggregate-root can't break libs.ddd.src.valueobjects.id_valueobject.
- Position
- Below the diagonal: libs.ddd.src.aggregate-root uses a module listed above it, which is the healthy direction.
29→25 libs.ddd.src.core.aggregate.aggregate-identity uses libs.ddd.src.valueobjects.id_valueobject✕
- Connections
- 1 pair of types, where a type in libs.ddd.src.core.aggregate.aggregate-identity uses a type in libs.ddd.src.valueobjects.id_valueobject.
- The types involved
libs.ddd.src.core.aggregate.aggregate-identity.AggregateIdentity→libs.ddd.src.valueobjects.id_valueobject.IdValueObject
- Direction
- libs.ddd.src.core.aggregate.aggregate-identity uses libs.ddd.src.valueobjects.id_valueobject, so a change to libs.ddd.src.valueobjects.id_valueobject can break libs.ddd.src.core.aggregate.aggregate-identity, while a change to libs.ddd.src.core.aggregate.aggregate-identity can't break libs.ddd.src.valueobjects.id_valueobject.
- Position
- Below the diagonal: libs.ddd.src.core.aggregate.aggregate-identity uses a module listed above it, which is the healthy direction.
30→22 libs.ddd.src.core.aggregate.aggregate-serializer uses libs.ddd.src.tracking-state-manager✕
- Connections
- 1 pair of types, where a type in libs.ddd.src.core.aggregate.aggregate-serializer uses a type in libs.ddd.src.tracking-state-manager.
- The types involved
libs.ddd.src.core.aggregate.aggregate-serializer.AggregateSerializer→libs.ddd.src.tracking-state-manager.TrackingStateManager
- Direction
- libs.ddd.src.core.aggregate.aggregate-serializer uses libs.ddd.src.tracking-state-manager, so a change to libs.ddd.src.tracking-state-manager can break libs.ddd.src.core.aggregate.aggregate-serializer, while a change to libs.ddd.src.core.aggregate.aggregate-serializer can't break libs.ddd.src.tracking-state-manager.
- Position
- Below the diagonal: libs.ddd.src.core.aggregate.aggregate-serializer uses a module listed above it, which is the healthy direction.
30→25 libs.ddd.src.core.aggregate.aggregate-serializer uses libs.ddd.src.valueobjects.id_valueobject✕
- Connections
- 1 pair of types, where a type in libs.ddd.src.core.aggregate.aggregate-serializer uses a type in libs.ddd.src.valueobjects.id_valueobject.
- The types involved
libs.ddd.src.core.aggregate.aggregate-serializer.AggregateSerializer→libs.ddd.src.valueobjects.id_valueobject.IdValueObject
- Direction
- libs.ddd.src.core.aggregate.aggregate-serializer uses libs.ddd.src.valueobjects.id_valueobject, so a change to libs.ddd.src.valueobjects.id_valueobject can break libs.ddd.src.core.aggregate.aggregate-serializer, while a change to libs.ddd.src.core.aggregate.aggregate-serializer can't break libs.ddd.src.valueobjects.id_valueobject.
- Position
- Below the diagonal: libs.ddd.src.core.aggregate.aggregate-serializer uses a module listed above it, which is the healthy direction.
31→24 src.orders.domain.entities.order-item_entity uses libs.ddd.src.valueobject✕
- Connections
- 1 pair of types, where a type in src.orders.domain.entities.order-item_entity uses a type in libs.ddd.src.valueobject.
- The types involved
src.orders.domain.entities.order-item_entity.OrderItem→libs.ddd.src.valueobject.DddValueObject
- Direction
- src.orders.domain.entities.order-item_entity uses libs.ddd.src.valueobject, so a change to libs.ddd.src.valueobject can break src.orders.domain.entities.order-item_entity, while a change to src.orders.domain.entities.order-item_entity can't break libs.ddd.src.valueobject.
- Position
- Below the diagonal: src.orders.domain.entities.order-item_entity uses a module listed above it, which is the healthy direction.
31→25 src.orders.domain.entities.order-item_entity uses libs.ddd.src.valueobjects.id_valueobject✕
- Connections
- 2 pairs of types, where a type in src.orders.domain.entities.order-item_entity uses a type in libs.ddd.src.valueobjects.id_valueobject.
- The types involved
src.orders.domain.entities.order-item_entity.IOrderItemProps→libs.ddd.src.valueobjects.id_valueobject.IdValueObjectsrc.orders.domain.entities.order-item_entity.OrderItem→libs.ddd.src.valueobjects.id_valueobject.IdValueObject
- Direction
- src.orders.domain.entities.order-item_entity uses libs.ddd.src.valueobjects.id_valueobject, so a change to libs.ddd.src.valueobjects.id_valueobject can break src.orders.domain.entities.order-item_entity, while a change to src.orders.domain.entities.order-item_entity can't break libs.ddd.src.valueobjects.id_valueobject.
- Position
- Below the diagonal: src.orders.domain.entities.order-item_entity uses a module listed above it, which is the healthy direction.
31→27 src.orders.domain.entities.order-item_entity uses src.orders.domain.value-objects.money_vo✕
- Connections
- 2 pairs of types, where a type in src.orders.domain.entities.order-item_entity uses a type in src.orders.domain.value-objects.money_vo.
- The types involved
src.orders.domain.entities.order-item_entity.IOrderItemProps→src.orders.domain.value-objects.money_vo.Moneysrc.orders.domain.entities.order-item_entity.OrderItem→src.orders.domain.value-objects.money_vo.Money
- Direction
- src.orders.domain.entities.order-item_entity uses src.orders.domain.value-objects.money_vo, so a change to src.orders.domain.value-objects.money_vo can break src.orders.domain.entities.order-item_entity, while a change to src.orders.domain.entities.order-item_entity can't break src.orders.domain.value-objects.money_vo.
- Position
- Below the diagonal: src.orders.domain.entities.order-item_entity uses a module listed above it, which is the healthy direction.
32→8 src.orders.domain.events.order_events uses src.orders.domain.order-aggregate.order-status_enum✕
- Connections
- 1 pair of types, where a type in src.orders.domain.events.order_events uses a type in src.orders.domain.order-aggregate.order-status_enum.
- The types involved
src.orders.domain.events.order_events.OrderStatusChangedEvent→src.orders.domain.order-aggregate.order-status_enum.OrderStatus
- Direction
- src.orders.domain.events.order_events uses src.orders.domain.order-aggregate.order-status_enum, so a change to src.orders.domain.order-aggregate.order-status_enum can break src.orders.domain.events.order_events, while a change to src.orders.domain.events.order_events can't break src.orders.domain.order-aggregate.order-status_enum.
- Position
- Below the diagonal: src.orders.domain.events.order_events uses a module listed above it, which is the healthy direction.
32→25 src.orders.domain.events.order_events uses libs.ddd.src.valueobjects.id_valueobject✕
- Connections
- 9 pairs of types, where a type in src.orders.domain.events.order_events uses a type in libs.ddd.src.valueobjects.id_valueobject.
- The types involved
src.orders.domain.events.order_events.OrderCancelledEvent→libs.ddd.src.valueobjects.id_valueobject.IdValueObjectsrc.orders.domain.events.order_events.OrderConfirmedEvent→libs.ddd.src.valueobjects.id_valueobject.IdValueObjectsrc.orders.domain.events.order_events.OrderCreatedEvent→libs.ddd.src.valueobjects.id_valueobject.IdValueObjectsrc.orders.domain.events.order_events.OrderDeliveredEvent→libs.ddd.src.valueobjects.id_valueobject.IdValueObjectsrc.orders.domain.events.order_events.OrderItemAddedEvent→libs.ddd.src.valueobjects.id_valueobject.IdValueObjectsrc.orders.domain.events.order_events.OrderItemQuantityChangedEvent→libs.ddd.src.valueobjects.id_valueobject.IdValueObjectsrc.orders.domain.events.order_events.OrderItemRemovedEvent→libs.ddd.src.valueobjects.id_valueobject.IdValueObjectsrc.orders.domain.events.order_events.OrderShippedEvent→libs.ddd.src.valueobjects.id_valueobject.IdValueObjectsrc.orders.domain.events.order_events.OrderStatusChangedEvent→libs.ddd.src.valueobjects.id_valueobject.IdValueObject
- Direction
- src.orders.domain.events.order_events uses libs.ddd.src.valueobjects.id_valueobject, so a change to libs.ddd.src.valueobjects.id_valueobject can break src.orders.domain.events.order_events, while a change to src.orders.domain.events.order_events can't break libs.ddd.src.valueobjects.id_valueobject.
- Position
- Below the diagonal: src.orders.domain.events.order_events uses a module listed above it, which is the healthy direction.
33→26 src.shared.valueobjects.Name uses libs.ddd.src.valueobjects.string_valueobject✕
- Connections
- 1 pair of types, where a type in src.shared.valueobjects.Name uses a type in libs.ddd.src.valueobjects.string_valueobject.
- The types involved
src.shared.valueobjects.Name.Name→libs.ddd.src.valueobjects.string_valueobject.StringValueObject
- Direction
- src.shared.valueobjects.Name uses libs.ddd.src.valueobjects.string_valueobject, so a change to libs.ddd.src.valueobjects.string_valueobject can break src.shared.valueobjects.Name, while a change to src.shared.valueobjects.Name can't break libs.ddd.src.valueobjects.string_valueobject.
- Position
- Below the diagonal: src.shared.valueobjects.Name uses a module listed above it, which is the healthy direction.
34→26 src.shared.valueobjects.description uses libs.ddd.src.valueobjects.string_valueobject✕
- Connections
- 1 pair of types, where a type in src.shared.valueobjects.description uses a type in libs.ddd.src.valueobjects.string_valueobject.
- The types involved
src.shared.valueobjects.description.Description→libs.ddd.src.valueobjects.string_valueobject.StringValueObject
- Direction
- src.shared.valueobjects.description uses libs.ddd.src.valueobjects.string_valueobject, so a change to libs.ddd.src.valueobjects.string_valueobject can break src.shared.valueobjects.description, while a change to src.shared.valueobjects.description can't break libs.ddd.src.valueobjects.string_valueobject.
- Position
- Below the diagonal: src.shared.valueobjects.description uses a module listed above it, which is the healthy direction.
35→8 src.orders.domain.order-aggregate.order uses src.orders.domain.order-aggregate.order-status_enum✕
- Connections
- 2 pairs of types, where a type in src.orders.domain.order-aggregate.order uses a type in src.orders.domain.order-aggregate.order-status_enum.
- The types involved
src.orders.domain.order-aggregate.order.IOrderProps→src.orders.domain.order-aggregate.order-status_enum.OrderStatussrc.orders.domain.order-aggregate.order.Order→src.orders.domain.order-aggregate.order-status_enum.OrderStatus
- Direction
- src.orders.domain.order-aggregate.order uses src.orders.domain.order-aggregate.order-status_enum, so a change to src.orders.domain.order-aggregate.order-status_enum can break src.orders.domain.order-aggregate.order, while a change to src.orders.domain.order-aggregate.order can't break src.orders.domain.order-aggregate.order-status_enum.
- Position
- Below the diagonal: src.orders.domain.order-aggregate.order uses a module listed above it, which is the healthy direction.
35→25 src.orders.domain.order-aggregate.order uses libs.ddd.src.valueobjects.id_valueobject✕
- Connections
- 1 pair of types, where a type in src.orders.domain.order-aggregate.order uses a type in libs.ddd.src.valueobjects.id_valueobject.
- The types involved
src.orders.domain.order-aggregate.order.Order→libs.ddd.src.valueobjects.id_valueobject.IdValueObject
- Direction
- src.orders.domain.order-aggregate.order uses libs.ddd.src.valueobjects.id_valueobject, so a change to libs.ddd.src.valueobjects.id_valueobject can break src.orders.domain.order-aggregate.order, while a change to src.orders.domain.order-aggregate.order can't break libs.ddd.src.valueobjects.id_valueobject.
- Position
- Below the diagonal: src.orders.domain.order-aggregate.order uses a module listed above it, which is the healthy direction.
35→27 src.orders.domain.order-aggregate.order uses src.orders.domain.value-objects.money_vo✕
- Connections
- 1 pair of types, where a type in src.orders.domain.order-aggregate.order uses a type in src.orders.domain.value-objects.money_vo.
- The types involved
src.orders.domain.order-aggregate.order.Order→src.orders.domain.value-objects.money_vo.Money
- Direction
- src.orders.domain.order-aggregate.order uses src.orders.domain.value-objects.money_vo, so a change to src.orders.domain.value-objects.money_vo can break src.orders.domain.order-aggregate.order, while a change to src.orders.domain.order-aggregate.order can't break src.orders.domain.value-objects.money_vo.
- Position
- Below the diagonal: src.orders.domain.order-aggregate.order uses a module listed above it, which is the healthy direction.
35→28 src.orders.domain.order-aggregate.order uses libs.ddd.src.aggregate-root✕
- Connections
- 1 pair of types, where a type in src.orders.domain.order-aggregate.order uses a type in libs.ddd.src.aggregate-root.
- The types involved
src.orders.domain.order-aggregate.order.Order→libs.ddd.src.aggregate-root.DddAggregateRoot
- Direction
- src.orders.domain.order-aggregate.order uses libs.ddd.src.aggregate-root, so a change to libs.ddd.src.aggregate-root can break src.orders.domain.order-aggregate.order, while a change to src.orders.domain.order-aggregate.order can't break libs.ddd.src.aggregate-root.
- Position
- Below the diagonal: src.orders.domain.order-aggregate.order uses a module listed above it, which is the healthy direction.
35→31 src.orders.domain.order-aggregate.order uses src.orders.domain.entities.order-item_entity✕
- Connections
- 1 pair of types, where a type in src.orders.domain.order-aggregate.order uses a type in src.orders.domain.entities.order-item_entity.
- The types involved
src.orders.domain.order-aggregate.order.Order→src.orders.domain.entities.order-item_entity.OrderItem
- Direction
- src.orders.domain.order-aggregate.order uses src.orders.domain.entities.order-item_entity, so a change to src.orders.domain.entities.order-item_entity can break src.orders.domain.order-aggregate.order, while a change to src.orders.domain.order-aggregate.order can't break src.orders.domain.entities.order-item_entity.
- Position
- Below the diagonal: src.orders.domain.order-aggregate.order uses a module listed above it, which is the healthy direction.
36→12 src.products.domain.product-aggregate.product uses src.shared.valueobjects.price✕
- Connections
- 2 pairs of types, where a type in src.products.domain.product-aggregate.product uses a type in src.shared.valueobjects.price.
- The types involved
src.products.domain.product-aggregate.product.IProductProps→src.shared.valueobjects.price.Pricesrc.products.domain.product-aggregate.product.Product→src.shared.valueobjects.price.Price
- Direction
- src.products.domain.product-aggregate.product uses src.shared.valueobjects.price, so a change to src.shared.valueobjects.price can break src.products.domain.product-aggregate.product, while a change to src.products.domain.product-aggregate.product can't break src.shared.valueobjects.price.
- Position
- Below the diagonal: src.products.domain.product-aggregate.product uses a module listed above it, which is the healthy direction.
36→25 src.products.domain.product-aggregate.product uses libs.ddd.src.valueobjects.id_valueobject✕
- Connections
- 1 pair of types, where a type in src.products.domain.product-aggregate.product uses a type in libs.ddd.src.valueobjects.id_valueobject.
- The types involved
src.products.domain.product-aggregate.product.Product→libs.ddd.src.valueobjects.id_valueobject.IdValueObject
- Direction
- src.products.domain.product-aggregate.product uses libs.ddd.src.valueobjects.id_valueobject, so a change to libs.ddd.src.valueobjects.id_valueobject can break src.products.domain.product-aggregate.product, while a change to src.products.domain.product-aggregate.product can't break libs.ddd.src.valueobjects.id_valueobject.
- Position
- Below the diagonal: src.products.domain.product-aggregate.product uses a module listed above it, which is the healthy direction.
36→28 src.products.domain.product-aggregate.product uses libs.ddd.src.aggregate-root✕
- Connections
- 1 pair of types, where a type in src.products.domain.product-aggregate.product uses a type in libs.ddd.src.aggregate-root.
- The types involved
src.products.domain.product-aggregate.product.Product→libs.ddd.src.aggregate-root.DddAggregateRoot
- Direction
- src.products.domain.product-aggregate.product uses libs.ddd.src.aggregate-root, so a change to libs.ddd.src.aggregate-root can break src.products.domain.product-aggregate.product, while a change to src.products.domain.product-aggregate.product can't break libs.ddd.src.aggregate-root.
- Position
- Below the diagonal: src.products.domain.product-aggregate.product uses a module listed above it, which is the healthy direction.
36→33 src.products.domain.product-aggregate.product uses src.shared.valueobjects.Name✕
- Connections
- 2 pairs of types, where a type in src.products.domain.product-aggregate.product uses a type in src.shared.valueobjects.Name.
- The types involved
src.products.domain.product-aggregate.product.IProductProps→src.shared.valueobjects.Name.Namesrc.products.domain.product-aggregate.product.Product→src.shared.valueobjects.Name.Name
- Direction
- src.products.domain.product-aggregate.product uses src.shared.valueobjects.Name, so a change to src.shared.valueobjects.Name can break src.products.domain.product-aggregate.product, while a change to src.products.domain.product-aggregate.product can't break src.shared.valueobjects.Name.
- Position
- Below the diagonal: src.products.domain.product-aggregate.product uses a module listed above it, which is the healthy direction.
36→34 src.products.domain.product-aggregate.product uses src.shared.valueobjects.description✕
- Connections
- 2 pairs of types, where a type in src.products.domain.product-aggregate.product uses a type in src.shared.valueobjects.description.
- The types involved
src.products.domain.product-aggregate.product.IProductProps→src.shared.valueobjects.description.Descriptionsrc.products.domain.product-aggregate.product.Product→src.shared.valueobjects.description.Description
- Direction
- src.products.domain.product-aggregate.product uses src.shared.valueobjects.description, so a change to src.shared.valueobjects.description can break src.products.domain.product-aggregate.product, while a change to src.products.domain.product-aggregate.product can't break src.shared.valueobjects.description.
- Position
- Below the diagonal: src.products.domain.product-aggregate.product uses a module listed above it, which is the healthy direction.
37→35 src.orders.infrastructure.repositories.order_repository uses src.orders.domain.order-aggregate.order✕
- Connections
- 1 pair of types, where a type in src.orders.infrastructure.repositories.order_repository uses a type in src.orders.domain.order-aggregate.order.
- The types involved
src.orders.infrastructure.repositories.order_repository.OrderRepository→src.orders.domain.order-aggregate.order.Order
- Direction
- src.orders.infrastructure.repositories.order_repository uses src.orders.domain.order-aggregate.order, so a change to src.orders.domain.order-aggregate.order can break src.orders.infrastructure.repositories.order_repository, while a change to src.orders.infrastructure.repositories.order_repository can't break src.orders.domain.order-aggregate.order.
- Position
- Below the diagonal: src.orders.infrastructure.repositories.order_repository uses a module listed above it, which is the healthy direction.
38→36 src.products.infrastructure.repositories.product_repository uses src.products.domain.product-aggregate.product✕
- Connections
- 1 pair of types, where a type in src.products.infrastructure.repositories.product_repository uses a type in src.products.domain.product-aggregate.product.
- The types involved
src.products.infrastructure.repositories.product_repository.ProductRepository→src.products.domain.product-aggregate.product.Product
- Direction
- src.products.infrastructure.repositories.product_repository uses src.products.domain.product-aggregate.product, so a change to src.products.domain.product-aggregate.product can break src.products.infrastructure.repositories.product_repository, while a change to src.products.infrastructure.repositories.product_repository can't break src.products.domain.product-aggregate.product.
- Position
- Below the diagonal: src.products.infrastructure.repositories.product_repository uses a module listed above it, which is the healthy direction.
39→37 src.orders.application.queries.get-order.get-order_query-handler uses src.orders.infrastructure.repositories.order_repository✕
- Connections
- 1 pair of types, where a type in src.orders.application.queries.get-order.get-order_query-handler uses a type in src.orders.infrastructure.repositories.order_repository.
- The types involved
src.orders.application.queries.get-order.get-order_query-handler.GetOrderQueryHandler→src.orders.infrastructure.repositories.order_repository.OrderRepository
- Direction
- src.orders.application.queries.get-order.get-order_query-handler uses src.orders.infrastructure.repositories.order_repository, so a change to src.orders.infrastructure.repositories.order_repository can break src.orders.application.queries.get-order.get-order_query-handler, while a change to src.orders.application.queries.get-order.get-order_query-handler can't break src.orders.infrastructure.repositories.order_repository.
- Position
- Below the diagonal: src.orders.application.queries.get-order.get-order_query-handler uses a module listed above it, which is the healthy direction.
40→38 src.products.application.queries.get-product.get-product_query-handler uses src.products.infrastructure.repositories.product_repository✕
- Connections
- 1 pair of types, where a type in src.products.application.queries.get-product.get-product_query-handler uses a type in src.products.infrastructure.repositories.product_repository.
- The types involved
src.products.application.queries.get-product.get-product_query-handler.GetProductQueryHandler→src.products.infrastructure.repositories.product_repository.ProductRepository
- Direction
- src.products.application.queries.get-product.get-product_query-handler uses src.products.infrastructure.repositories.product_repository, so a change to src.products.infrastructure.repositories.product_repository can break src.products.application.queries.get-product.get-product_query-handler, while a change to src.products.application.queries.get-product.get-product_query-handler can't break src.products.infrastructure.repositories.product_repository.
- Position
- Below the diagonal: src.products.application.queries.get-product.get-product_query-handler uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
At a glance — Domain Modelling
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A05:2025 — Injection | 25 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 25 | High / Critical |
| A07:2025 — Authentication Failures | 6 | High / Critical |
| A02:2025 — Security Misconfiguration | 2 | High / Critical |
Roadmap
Top priorities: Resolve the 3 Leaked secret finding(s) in Secret Scanning — start with REDACTED (3); Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies; Adopt strongly-typed ids across the domain — finish the migration or document the boundary; primitive ids invite transposed-argument bugs.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 3 Leaked secret finding(s) in Secret Scanning — start with REDACTED (3). | +4.7 pts | Low | Secret Scanning |
| Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies. | +3.9 pts | Medium | Dependency Hygiene |
| Adopt strongly-typed ids across the domain — finish the migration or document the boundary; primitive ids invite transposed-argument bugs. | +2.8 pts | Medium | Strongly-typed ids |
| Move business rules onto the aggregates/entities they govern so invariants are enforced at the source, not in anemic services. | +2.8 pts | Medium | Rich vs anemic model |
| Keep the ORM/table mapping on a boundary data-model + mapper; leave the domain entity framework-free (map row↔domain through a repository). | +1.4 pts | Medium | Domain ↔ infrastructure boundary |
| Resolve the 1 No ADRs found finding(s) in ADR Quality. | +0.6 pts | Low | ADR Quality |
| Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion. | +0.5 pts | Low | Project Cohesion |
| Break each cycle by extracting the shared piece into a module both sides can import. | +0.9 pts | Medium | Circular Imports |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 0.0 | Slop | Secret Scanning: Leaked secret: REDACTED |
| REDACTED | 1.6 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.4 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.1 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.8 | Mixed | IaC & Container Security: High IaC: REDACTED |
| src/orders/domain/validators/order-status.validator.ts | 7.0 | Mixed | Cognitive Complexity: OrderStatusValidator.addRules (cognitive 16) |
| REDACTED | 7.2 | Mixed | Secrets (history): High secret: REDACTED |
| REDACTED | 7.2 | Mixed | Static Analysis (SAST): High: REDACTED |
| src/orders/application/use-cases/create-order/create-order.command-handler.ts | 8.0 | Near-clean | Code Coverage: Low coverage: src/orders/application/use-cases/create-order/create-order.command-handler.ts |
| src/orders/application/events/order-cancelled.event-handler.ts | 8.5 | Near-clean | Code Coverage: Low coverage: src/orders/application/events/order-cancelled.event-handler.ts |
| src/orders/application/events/order-confirmed.event-handler.ts | 8.5 | Near-clean | Code Coverage: Low coverage: src/orders/application/events/order-confirmed.event-handler.ts |
| src/orders/application/events/order-created.event-handler.ts | 8.5 | Near-clean | Code Coverage: Low coverage: src/orders/application/events/order-created.event-handler.ts |
| src/orders/application/events/order-item-added.event-handler.ts | 8.5 | Near-clean | Code Coverage: Low coverage: src/orders/application/events/order-item-added.event-handler.ts |
| src/orders/application/events/order-shipped.event-handler.ts | 8.5 | Near-clean | Code Coverage: Low coverage: src/orders/application/events/order-shipped.event-handler.ts |
| src/orders/application/queries/get-order/get-order.query-handler.ts | 8.5 | Near-clean | Code Coverage: Low coverage: src/orders/application/queries/get-order/get-order.query-handler.ts |
| src/orders/application/queries/get-order/get-order.query.ts | 8.5 | Near-clean | Code Coverage: Low coverage: src/orders/application/queries/get-order/get-order.query.ts |
| src/orders/application/queries/get-orders/get-orders.query-handler.ts | 8.5 | Near-clean | Code Coverage: Low coverage: src/orders/application/queries/get-orders/get-orders.query-handler.ts |
| src/orders/application/queries/get-orders/get-orders.query.ts | 8.5 | Near-clean | Code Coverage: Low coverage: src/orders/application/queries/get-orders/get-orders.query.ts |
| src/orders/application/sagas/order.saga.ts | 8.5 | Near-clean | Code Coverage: Low coverage: src/orders/application/sagas/order.saga.ts |
| src/orders/application/use-cases/add-item-to-order/add-item-to-order.command-handler.ts | 8.5 | Near-clean | Code Coverage: Low coverage: src/orders/application/use-cases/add-item-to-order/add-item-to-order.command-handler.ts |
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 86 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 — 86 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, 267 of 280 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Canine Code Analyzer duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy · checkov | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 · 3.2.533 | ✓ deterministic |
Run transparency — what happened this run
- D12 Dependency Hygiene — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This repository's dependency manifests WERE read and their pinning discipline assessed; what went unanswered is the currency half, because registry.npmjs.org — the registry that answers it — was asked and did not reply (registry returned 429). This is OUR side and it is an ENVIRONMENT fault, not a missing collector: the collector exists and ran. An HTTP 403 here is what this scan's egress allowlist returns for a host that is not on it, so the remedy is to add registry.npmjs.org to the allowlist and re-run — not to build anything.
- 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 182 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. This kind did not reach the 95 % precision gate in three adjudicated runs (docs/plans/deterministic-engine/adjudication/D19-sample3-v3.md), so by the pre-registered fallback it publishes no row until a re-measurement shows it does. The candidates are counted here, not reported as findings, and the score does not include them.
- 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: it declares a published package (package.json), but 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 — 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. D24 compares a comment's words with the identifiers, literals and constructs of the code it annotates, using English function-word and rationale lexicons. Comments in another script or language were left unread rather than counted as clean.
- D34 Knowledge Freshness — 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. File-level freshness contradicts repo activity: 44 commits in the last 90 days, yet 20 of 31 significant files carry no living knowledge. Those two readings cannot both be true, so the per-file recency signal is treated as unreliable here and freshness is not scored for this run.
- AXB2 Runtime readiness — 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. The dev server kept running but no port it opened served a page in the time allowed. (rule: no-answer). The renderer reported: the dev server (`npm run start`) kept running but served no page within 2 minutes. Likely cause (not identified): the dev server kept running but no port it opened served a page in the time allowed. Last output: "[Nest] 1656 - 11/08/2026, 6:26:11 AM LOG [RouterExplorer] Mapped {/orders/:id/confirm, POST} route +0ms / [Nest] 1656 - 11/08/2026, 6:26:11 AM LOG [RouterExplorer] Mapped {/orders/:id/ship, POST} route +0ms / [Nest] 1656 - 11/08/2026, 6:26:11 AM LOG [RouterExplorer] Mapped {/orders/:id/deliver, POST} route +0ms / [Nest] 1656 - 11/08/2026, 6:26:11 AM LOG [RouterExplorer] Mapped {/orders/:id/cancel, POST} route +0ms / [Nest] 1656 - 11/08/2026, 6:26:11 AM LOG [NestApplication] Nest application successfully started +3ms / Listening at http://localhost:3000" No runtime evidence was gathered.
- 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 DevServer (start). the dev server (`npm run start`) kept running but served no page within 2 minutes. Likely cause (not identified): the dev server kept running but no port it opened served a page in the time allowed. Last output: "[Nest] 1656 - 11/08/2026, 6:26:11 AM LOG [RouterExplorer] Mapped {/orders/:id/confirm, POST} route +0ms / [Nest] 1656 - 11/08/2026, 6:26:11 AM LOG [RouterExplorer] Mapped {/orders/:id/ship, POST} route +0ms / [Nest] 1656 - 11/08/2026, 6:26:11 AM LOG [RouterExplorer] Mapped {/orders/:id/deliver, POST} route +0ms / [Nest] 1656 - 11/08/2026, 6:26:11 AM LOG [RouterExplorer] Mapped {/orders/:id/cancel, POST} route +0ms / [Nest] 1656 - 11/08/2026, 6:26:11 AM LOG [NestApplication] Nest application successfully started +3ms / Listening at http://localhost:3000" No runtime evidence was gathered.
- DM9 Scattered domain decisions — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Arm two tells a construction that PRODUCES a measurement from one that merely passes it along, and this repository's frontend does not compute that fact. A measurement built independently in two places would not appear above.
- M4 Documentation accuracy — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
- P2 Observability — 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. 19 further occurrence(s) are not listed individually; the score already reflects all 59.
- X2 Cancellation propagation — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Go, PHP, Dart, Kotlin, Ruby, Scala, Java, Python and Rust source only, and no C# was loaded, and no named async function in this repository's JavaScript/TypeScript, nor any Go, PHP or Dart function or Kotlin suspend function, makes a request that can be cancelled (fetch, axios, ky, ofetch, got, undici, node:http; net/http, net.Dial; amphp; Dio; Ktor, OkHttp), so there is nothing to judge, 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.
- X4 Structured logging — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Python, PHP, Dart, Ruby, Scala and Rust source only, and no C# was loaded, and this repository's JavaScript/TypeScript, Python and PHP log through no library that carries a message's values as fields (pino, winston, bunyan, tslog, LogTape, roarr; Python's logging, structlog; PHP's PSR-3 loggers), so its log calls cannot be judged, 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.
- D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- D8 Code Coverage: Coverage is measured by building and running the test suite inside our isolated image — the target repo is never modified, and nothing on your systems runs. So coverage exists only when the suite builds and runs within the inline time budget; one that needs external services, can't build, or exceeds the budget yields no coverage (D8 then degrades to not-measured, not a low score). Line coverage also says nothing about assertion quality.
- D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
- D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
- D11 Test Reliability: Flakiness is inferred from history/markers — we run the suite once (for coverage), not the repeated runs under varied conditions that reveal nondeterminism, so a flaky test never recorded as failing is invisible here.
- D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
- D23 Boundary Type-Coupling: Boundary leakage is detected from type references across detected contexts — leaks that flow through primitives, serialization or shared infrastructure may not surface as a typed reference.
- D24 Comment Value: Comment value is measured as redundancy only: a comment that repeats its code's words is found, but a paraphrase in other words, a vague comment, or one the code contradicts is not, and whether a comment is valuable is not claimed. Comments in other scripts or languages, and outside C#, are not judged.
- D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
- D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- AX9 CQS / query purity: Handlers are found by interface/name convention — a query handler using neither is not seen. Mutation is a resolved write/publish invocation (SaveChanges/repository/bus), so a write hidden behind a hand-rolled wrapper, reflection, or a string-keyed service locator resolves to a non-persistence type and isn't flagged; it detects that a query writes state, not whether the write is a legitimate read-side cache update. Clean means "no resolved write/publish in a query body", not a proof of CQS purity.
- DM4 Rich vs anemic model: Behaviour is detected as state mutation inside a method body — a method that enforces an invariant by validating-and-throwing without mutating reads as a query, and mutation delegated through an interface the scan can't resolve isn't credited; entities with zero public properties still drop out of the population. It detects that state changes, not whether the rule is correct.
- DM6 Domain ↔ infrastructure boundary: Infrastructure reached through a hand-rolled wrapper, a domain-named facade, reflection, or a string-keyed service locator resolves to a non-infra type and isn't seen; the body scan is symbol resolution over syntax, not full dataflow. A clean result means "no resolved infra reference in a domain body", not a proof of purity.
- ED5 Idempotency: Idempotency is read from the handler body and one hop below: a mutation is flagged only on structural double-apply evidence (a fresh-identity insert, an accumulation, a growing list, an unkeyed POST/send/charge), so a duplicate effect through a home-grown gateway two hops down, or an insert keyed on the message with no unique constraint, is not flagged but counted as not classified; a guard enforced by a database constraint or a broker's exactly-once delivery is invisible either way. It flags the at-least-once double-apply SHAPE, not a runtime proof of a duplicate effect.
- M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
- P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
- P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
Dimensions
D1 · Cyclomatic Complexity
0 method(s) exceeded the cyclomatic complexity threshold of 15.
D2 · Cognitive Complexity
1 method(s) exceeded the cognitive complexity threshold of 15; the worst was OrderStatusValidator.addRules at 16.
What to do
- Bring the 1 body over 15 down to 15 or less in Cognitive Complexity — start with OrderStatusValidator.addRules (cognitive 16). — Refactoring it lifts Cognitive Complexity from 9.9 to about 10.0/10.
- Enforce Cognitive Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D3 · God Classes
0 god class(es) detected.
D5 · Coupling
2 production modules (npm), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; 0 module(s) off the main sequence.
D6 · Cohesion (LCOM4)
0 of 19 classes have LCOM4 above 3.
D8 · Code Coverage
Line coverage 64.3% — 64 file(s) below 50%. Measured from the JavaScript/TypeScript suite (jest via `npm ci --ignore-scripts` in the repository root).
What to do
- Resolve the 64 Low coverage finding(s) in Code Coverage — start with order-cancelled.event-handler.ts, order-confirmed.event-handler.ts, order-created.event-handler.ts. — One of this dimension's main actionable groups (64 warning-level).
- Enforce Code Coverage in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D9 · Test Distribution
1027 test methods: 1010 unit, 0 integration, 0 BDD, 17 e2e. The JavaScript/TypeScript suite contributes 1027 `it`/`test` case(s) across 43 test file(s) declaring at least one; its tier split is read from package names and paths only.
D10 · Test Quality
0 skipped, 0 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 1027 tests.
D11 · Test Reliability
0 flaky across 1 measured tier(s). JavaScript/TypeScript (jest via `npm ci --ignore-scripts` in the repository root (1111 tests)): measured (0 flaky).
D13 · Secret Scanning
1 secret(s) detected.
What to do
- Resolve the 3 Leaked secret finding(s) in Secret Scanning — start with REDACTED (3). — One of this dimension's main actionable groups (3 issue-level).
- Enforce Secret Scanning in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window.
D17 · Explicit Debt
0 deducted task-comment markers across 10709 LoC (0.0/KLoC) → score 10.0. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
D19 · Documentation Quality
1 of 1 documentation facets pass in full. 20 document(s) read across 2 unit(s).
D20 · ADR Quality
No architecture decision records were found.
What to do
- Resolve the 1 No ADRs found finding(s) in ADR Quality. — One of this dimension's main actionable groups (1 recommendation-level).
D23 · Boundary Type-Coupling
No domain types leak across context boundaries (2 contexts). Contexts: orders, products.
D24 · Comment Value
6 of 391 judged comments only repeat the code they sit on (1.5 %). 141 comment(s) in another language or script were not judged.
What to do
- Resolve the 6 redundant comment finding(s) in Comment Value — start with aggregate-validation-orchestrator.spec.ts, valueobject.ts, number-notnull.validator.ts. — One of this dimension's main actionable groups (6 recommendation-level).
D26 · Project Cohesion
1 of 2 build units (npm) flagged as possibly oversized/incoherent.
What to do
- Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion. — One of this dimension's main actionable groups (1 recommendation-level).
D27 · Navigability
53 % of calls cross a namespace and 7 % go through an interface, but 85 % of collaborators are co-located — so a call's collaborators sit together and tracing stays easy. Baseline: small — navigation cost is tolerated.
D28 · Secrets (history)
2 finding(s): 0 critical, 2 high, 0 medium, 0 low. Remediation for historically-committed secrets is credential rotation — they remain in history regardless of later deletion.
What to do
- Resolve the 2 High secret finding(s) in Secrets (history) — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
- Resolve the 1 Rotate the exposed credentials finding(s) in Secrets (history). — One of this dimension's main actionable groups (1 recommendation-level).
D29 · Static Analysis (SAST)
25 finding(s): 0 critical, 24 high, 1 medium, 0 low. 21 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. semgrep hit a parse error in 1 file(s) — `graph.json` — so no absence of findings in them is evidence of anything, and nothing in them was analysed. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them. Separately, one or more rules could not re-parse an embedded snippet in 2 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.
What to do
- Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 issue-level).
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- No action in Static Analysis (SAST) — all 21 REDACTED finding(s) are reported here at file:line but scored by D36 (supply-chain provenance), so none is charged to this dimension. — One of this dimension's main actionable groups (21 issue-level, 0 of them charged here).
D30 · Dependency Vulnerabilities
18 finding(s): 2 critical, 8 high, 7 medium, 1 low.
What to do
- Resolve the 8 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (8). — One of this dimension's main actionable groups (8 issue-level).
- Resolve the 6 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (6). — One of this dimension's main actionable groups (6 warning-level).
- Resolve the 2 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
D31 · IaC & Container Security
2 finding(s): 0 critical, 2 high, 0 medium, 0 low.
What to do
- Resolve the 2 High IaC finding(s) in IaC & Container Security — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
D35 · Change Coupling
No strong hidden change-coupling between production files.
D36 · Supply-chain Provenance & Signing
0/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).
What to do
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).
D37 · Vulnerability-disclosure Policy
A vulnerability-disclosure policy (.github/SECURITY.md) is published with a reporting contact.
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 0 platform declaration(s) and 13 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
Frontend & cross-cutting dimensions
AX10 · Code composition
AX3 · Project dependency cycles
AX4 · Dependency direction
AX5 · Architecture & structure
AX6 · Interface segregation
AX9 · CQS / query purity
C2 · Access Controls
- Authorization IS enforced here (by route guards, auth middleware or checks that refuse a caller) — this is NOT a claim that endpoints are unprotected. What's missing is a NAMED rule set: who may do what is encoded inline where it is checked, so the rules can't be listed, reviewed or tested apart from the code that applies them. Recommendation, not a defect. — src/orders/domain/order-aggregate/order.ts:510
What to do
- Name the access rules — roles/permissions declared once (a @Roles/@Permissions decorator with its guard, a CASL ability, a casbin model, or Supabase CREATE POLICY) and consulted where access is checked, so the rule set is reviewable and testable on its own.
DM1 · Aggregate boundaries
DM11 · Constructible invalid state
DM2 · Strongly-typed ids
- `OrderCreatedEvent.customerId` is a raw `string` — give it a strongly-typed id: a dedicated single-field type wrapping the `string`, in whatever form your language spells that. — src/orders/domain/events/order.events.ts:11
What to do
- Adopt strongly-typed ids across the domain — finish the migration or document the boundary; primitive ids invite transposed-argument bugs.
DM4 · Rich vs anemic model
- `OrderItem` is an aggregate/entity with 5 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — src/orders/domain/entities/order-item.entity.ts:45
- `Order` is an aggregate/entity with 13 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — src/orders/domain/order-aggregate/order.ts:92
What to do
- Move business rules onto the aggregates/entities they govern so invariants are enforced at the source, not in anemic services.
DM5 · Encapsulated state
DM6 · Domain ↔ infrastructure boundary
- `src/orders/domain/order-aggregate/order.ts` (domain layer) depends on `@nestjs/common` (import) — a HTTP module; the domain should own a port and let an infrastructure adapter implement it. — src/orders/domain/order-aggregate/order.ts:1
What to do
- Keep the ORM/table mapping on a boundary data-model + mapper; leave the domain entity framework-free (map row↔domain through a repository).
DM9 · Scattered domain decisions
ED5 · Idempotency
GD1 · Unfinished & placeholder code
IC1 · Incompleteness & stubs
- `save` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. (×2) — src/orders/infrastructure/repositories/order.repository.ts:12, src/products/infrastructure/repositories/product.repository.ts:12
- `delete` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. (×2) — src/orders/infrastructure/repositories/order.repository.ts:24, src/products/infrastructure/repositories/product.repository.ts:24
What to do
- Remove the dead code that still moves this score: delete dead if(false) branches and either do the real async work or drop the async keyword from fake-async functions.
M1 · Documentation (README)
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
M3 · Folder & project structure
M4 · Documentation accuracy
P1 · CI/CD gates
- `prettier --write "src/**/*.ts" "test/**/*.ts" "libs/**/*.ts"` (the `format` script this step runs) invokes prettier in the mode that REWRITES the files it reformats and exits 0 whatever it changed. The rewrite happens inside the runner's throwaway checkout and is then discarded, so the step passes on a badly-formatted change exactly as it passes on a clean one — it enforces nothing, and no other step in this file reads the result. `--check` is the flag that turns the same invocation into a gate: it leaves the files alone and exits non-zero when anything would have been reformatted. (×2) — REDACTED:40, REDACTED:56
What to do
- Add `--check` to the prettier step in `REDACTED` so a change that is not formatted fails CI, instead of being silently reformatted into a checkout that is thrown away — or, if reformatting the branch is the intent, commit the result back so the fix reaches the repository.
- Add `--check` to the prettier step in `REDACTED` so a change that is not formatted fails CI, instead of being silently reformatted into a checkout that is thrown away — or, if reformatting the branch is the intent, commit the result back so the fix reaches the repository.
P10 · Library API & versioning
P2 · Observability
- `src/products/domain/product-aggregate/product.ts` reports through `console.*` at line 165 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — src/products/domain/product-aggregate/product.ts:165
- `src/products/domain/product-aggregate/product.ts` reports through `console.*` at line 201 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — src/products/domain/product-aggregate/product.ts:201
- `src/products/domain/product-aggregate/product.ts` reports through `console.*` at line 208 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — src/products/domain/product-aggregate/product.ts:208
- `src/orders/domain/value-objects/money.vo.ts` reports through `console.*` at line 17 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — src/orders/domain/value-objects/money.vo.ts:17
- `src/orders/domain/entities/order-item.entity.ts` reports through `console.*` at line 27 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — src/orders/domain/entities/order-item.entity.ts:27
- `libs/ddd/src/aggregate-root.ts` reports through `console.*` at line 161 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — libs/ddd/src/aggregate-root.ts:161
- `libs/ddd/src/broken-rules.manager.ts` reports through `console.*` at line 36 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — libs/ddd/src/broken-rules.manager.ts:36
- `libs/ddd/src/broken-rules.manager.ts` reports through `console.*` at line 181 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — libs/ddd/src/broken-rules.manager.ts:181
- `libs/ddd/src/enum.ts` reports through `console.*` at line 52 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — libs/ddd/src/enum.ts:52
- `libs/ddd/src/enum.ts` reports through `console.*` at line 53 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — libs/ddd/src/enum.ts:53
- `libs/ddd/src/enum.ts` reports through `console.*` at line 128 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — libs/ddd/src/enum.ts:128
- `libs/ddd/src/enum.ts` reports through `console.*` at line 241 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — libs/ddd/src/enum.ts:241
- `libs/ddd/src/enum.ts` reports through `console.*` at line 268 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — libs/ddd/src/enum.ts:268
- `libs/ddd/src/state-transition.manager.ts` reports through `console.*` at line 305 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — libs/ddd/src/state-transition.manager.ts:305
- `libs/ddd/src/state-transition.manager.ts` reports through `console.*` at line 366 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — libs/ddd/src/state-transition.manager.ts:366
- `libs/ddd/src/state-transition.manager.ts` reports through `console.*` at line 389 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — libs/ddd/src/state-transition.manager.ts:389
- `libs/ddd/src/tracking-state-manager.ts` reports through `console.*` at line 66 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — libs/ddd/src/tracking-state-manager.ts:66
- `libs/ddd/src/tracking-state-manager.ts` reports through `console.*` at line 71 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — libs/ddd/src/tracking-state-manager.ts:71
- `libs/ddd/src/tracking-state-manager.ts` reports through `console.*` at line 97 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — libs/ddd/src/tracking-state-manager.ts:97
- `libs/ddd/src/tracking-state-manager.ts` reports through `console.*` at line 101 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — libs/ddd/src/tracking-state-manager.ts:101
- `libs/ddd/src/tracking-state-manager.ts` reports through `console.*` at line 115 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — libs/ddd/src/tracking-state-manager.ts:115
- `libs/ddd/src/tracking-state-manager.ts` reports through `console.*` at line 119 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — libs/ddd/src/tracking-state-manager.ts:119
- `libs/ddd/src/tracking-state-manager.ts` reports through `console.*` at line 141 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — libs/ddd/src/tracking-state-manager.ts:141
- `libs/ddd/src/tracking-state-manager.ts` reports through `console.*` at line 159 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — libs/ddd/src/tracking-state-manager.ts:159
- `libs/ddd/src/tracking-state-manager.ts` reports through `console.*` at line 204 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — libs/ddd/src/tracking-state-manager.ts:204
- `libs/ddd/src/tracking-state-manager.ts` reports through `console.*` at line 323 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — libs/ddd/src/tracking-state-manager.ts:323
- `libs/ddd/src/validator-rule.manager.ts` reports through `console.*` at line 140 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — libs/ddd/src/validator-rule.manager.ts:140
- `libs/ddd/src/validator-rule.manager.ts` reports through `console.*` at line 156 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — libs/ddd/src/validator-rule.manager.ts:156
- `libs/ddd/src/validator-rule.manager.ts` reports through `console.*` at line 157 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — libs/ddd/src/validator-rule.manager.ts:157
- `libs/ddd/src/validator-rule.manager.ts` reports through `console.*` at line 178 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — libs/ddd/src/validator-rule.manager.ts:178
- `libs/ddd/src/validator-rule.manager.ts` reports through `console.*` at line 180 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — libs/ddd/src/validator-rule.manager.ts:180
- `libs/ddd/src/validator-rule.manager.ts` reports through `console.*` at line 216 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — libs/ddd/src/validator-rule.manager.ts:216
- `libs/ddd/src/validator-rule.manager.ts` reports through `console.*` at line 231 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — libs/ddd/src/validator-rule.manager.ts:231
- `libs/ddd/src/validator-rule.manager.ts` reports through `console.*` at line 247 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — libs/ddd/src/validator-rule.manager.ts:247
- `libs/ddd/src/validator-rule.manager.ts` reports through `console.*` at line 265 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — libs/ddd/src/validator-rule.manager.ts:265
- `libs/ddd/src/valueobject.ts` reports through `console.*` at line 135 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — libs/ddd/src/valueobject.ts:135
- `libs/ddd/src/valueobject.ts` reports through `console.*` at line 266 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — libs/ddd/src/valueobject.ts:266
- `libs/ddd/src/valueobject.ts` reports through `console.*` at line 415 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — libs/ddd/src/valueobject.ts:415
- `libs/ddd/src/valueobject.ts` reports through `console.*` at line 416 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — libs/ddd/src/valueobject.ts:416
- `libs/ddd/src/valueobject.ts` reports through `console.*` at line 452 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — libs/ddd/src/valueobject.ts:452
What to do
- Route service-code `console.*` output through the module's structured logger (with named fields), so delivery outcomes and failures reach the log pipeline with a level.
- Consider OpenTelemetry tracing/metrics (@opentelemetry/sdk-node) and a health-check endpoint (@godaddy/terminus or a /health route) for operability.
P3 · Security & performance tooling
- `REDACTED` schedules updates, but no `package-ecosystem` entry covers `github-actions`, which this tree depends on — so those dependencies get no update pull requests and no advisory pressure, however complete the dep-scan credit looks. Add the missing entry to the `updates:` list. — REDACTED:2
What to do
- Dependabot is configured but does not watch `github-actions` — add that `package-ecosystem` entry to REDACTED so those dependencies get the same automatic update and advisory pressure as the ones it already covers.
- 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.
P6 · Release Hygiene
P9 · Domain vs controller coverage
What to do
- Raise domain coverage toward 100% — cover the remaining aggregates / value objects / domain services where the business invariants and costly bugs live.
PF3 · Async & latency hygiene
R1 · Type Safety
- 255 typed · 1 plain JS — the untyped files are scripts/merge-coverage.js. tsconfig.json switches off noImplicitAny, strictNullChecks, so the typed files are only partly type-checked.
What to do
- Migrate the remaining .js/.jsx files to TypeScript.
R10 · Code Duplication
- 21 duplicated blocks under src/ have copies in at least two of the sibling directories orders, products, shared — 10 of them are reported below, and 11 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 21 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 21 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 21 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. — src/orders/presentation/orders.controller.ts:50
- libs/ddd/src/valueobjects/number.valueobject.ts:80 · libs/ddd/src/valueobjects/string.valueobject.ts:93 — the two spans are one implementation copied and then locally edited — 327 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. — libs/ddd/src/valueobjects/number.valueobject.ts:80
- src/orders/domain/value-objects/customer-info.vo.ts:8 · src/orders/domain/value-objects/shipping-address.vo.ts:8 — the two spans are one implementation copied and then locally edited — 255 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. — src/orders/domain/value-objects/customer-info.vo.ts:8
- src/orders/presentation/orders.controller.ts:50 · src/products/presentation/products.controller.ts:37 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — src/orders/presentation/orders.controller.ts:50
- libs/ddd/src/valueobjects/number-notnull.validator.ts:48 · libs/ddd/src/valueobjects/number-positive.validator.ts:69 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — libs/ddd/src/valueobjects/number-notnull.validator.ts:48
- src/orders/application/use-cases/change-item-quantity/change-item-quantity.command-handler.ts:8 · src/orders/application/use-cases/remove-item-from-order/remove-item-from-order.command-handler.ts:8 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — src/orders/application/use-cases/change-item-quantity/change-item-quantity.command-handler.ts:8
- src/orders/application/use-cases/cancel-order/cancel-order.command-handler.ts:7 · src/orders/application/use-cases/ship-order/ship-order.command-handler.ts:7 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — src/orders/application/use-cases/cancel-order/cancel-order.command-handler.ts:7
- src/orders/application/use-cases/confirm-order/confirm-order.command-handler.ts:7 · src/orders/application/use-cases/deliver-order/deliver-order.command-handler.ts:7 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — src/orders/application/use-cases/confirm-order/confirm-order.command-handler.ts:7
- src/shared/valueobjects/Name.ts:1 · src/shared/valueobjects/description.ts:1 · src/shared/valueobjects/price.ts:5 — the 3 copies are spread across 3 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — src/shared/valueobjects/Name.ts:1
- src/orders/application/queries/get-order/get-order.query-handler.ts:18 · src/orders/application/queries/get-orders/get-orders.query-handler.ts:25 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — src/orders/application/queries/get-order/get-order.query-handler.ts:18
- src/products/domain/product-aggregate/events/ProductNameChangedEvent.ts:3 · src/products/domain/product-aggregate/events/ProductPriceChangedEvent.ts:3 · src/products/domain/product-aggregate/events/ProductStatusChanged.ts:3 — the 3 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. There is one copy in each of 3 separate files rather than several in one place, so check first whether these are sibling modules that each declare their own version of one shape — one per entity, per provider, per language. Where they are, no single extracted module collapses them: each module still has to be written, and what recurs is the TEMPLATE. The moves that do collapse a template are to generate these modules from the set they enumerate, or to replace the repeated construction with one factory each site calls with its own values — and where the set is the point, each module pinning one distinct thing, the repetition IS the enumeration and there is nothing to delete. — src/products/domain/product-aggregate/events/ProductNameChangedEvent.ts:3
- libs/ddd/src/aggregate-root.ts:468 · libs/ddd/src/core/aggregate/aggregate-identity.ts:68 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — libs/ddd/src/aggregate-root.ts:468
- src/orders/application/use-cases/remove-item-from-order/remove-item-from-order.command-handler.ts:8 · src/products/application/use-cases/change-product-status/change-product-status.command-handler.ts:9 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — src/orders/application/use-cases/remove-item-from-order/remove-item-from-order.command-handler.ts:8
- src/orders/presentation/orders.controller.ts:131 · src/orders/presentation/orders.controller.ts:157 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — src/orders/presentation/orders.controller.ts:131
- src/orders/application/sagas/order.saga.ts:42 · src/products/application/sagas/product.saga.ts:20 · src/products/application/sagas/product.saga.ts:39 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — src/orders/application/sagas/order.saga.ts:42
- src/orders/domain/order-aggregate/order.ts:609 · src/products/domain/product-aggregate/product.ts:260 — the two spans are one implementation copied and then locally edited — 83 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. — src/orders/domain/order-aggregate/order.ts:609
- libs/ddd/src/broken-rules.manager.ts:230 · libs/ddd/src/core/business-rules/impl/broken-rules-extension.ts:29 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — libs/ddd/src/broken-rules.manager.ts:230
- src/shared/valueobjects/validators/description-length.validator.ts:5 · src/shared/valueobjects/validators/price-range.validator.ts:5 — the two spans are one implementation copied and then locally edited — 54 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. — src/shared/valueobjects/validators/description-length.validator.ts:5
- libs/ddd/src/aggregate-root.ts:371 · libs/ddd/src/core/aggregate/aggregate-validation-orchestrator.ts:80 — the two spans are one implementation copied and then locally edited — 51 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. — libs/ddd/src/aggregate-root.ts:371
- src/products/domain/product-aggregate/events/ProductCreatedEvent.ts:15 · src/products/domain/product-aggregate/events/ProductNameChangedEvent.ts:15 · src/products/domain/product-aggregate/events/ProductPriceChangedEvent.ts:15 · src/products/domain/product-aggregate/events/ProductStatusChanged.ts:15 — the 4 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. There is one copy in each of 4 separate files rather than several in one place, so check first whether these are sibling modules that each declare their own version of one shape — one per entity, per provider, per language. Where they are, no single extracted module collapses them: each module still has to be written, and what recurs is the TEMPLATE. The moves that do collapse a template are to generate these modules from the set they enumerate, or to replace the repeated construction with one factory each site calls with its own values — and where the set is the point, each module pinning one distinct thing, the repetition IS the enumeration and there is nothing to delete. — src/products/domain/product-aggregate/events/ProductCreatedEvent.ts:15
- src/orders/application/events/order-cancelled.event-handler.ts:1 · src/orders/application/events/order-confirmed.event-handler.ts:1 · src/orders/application/events/order-created.event-handler.ts:1 · src/orders/application/events/order-item-added.event-handler.ts:1 · +4 more site(s) not listed — the 8 copies are spread across 8 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — src/orders/application/events/order-cancelled.event-handler.ts:1
- src/orders/application/use-cases/add-item-to-order/add-item-to-order.command-handler.ts:32 · src/orders/application/use-cases/cancel-order/cancel-order.command-handler.ts:27 · src/orders/application/use-cases/change-item-quantity/change-item-quantity.command-handler.ts:29 · src/orders/application/use-cases/confirm-order/confirm-order.command-handler.ts:27 · +5 more site(s) not listed — the 9 copies are spread across 9 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. There is one copy in each of 9 separate files rather than several in one place, so check first whether these are sibling modules that each declare their own version of one shape — one per entity, per provider, per language. Where they are, no single extracted module collapses them: each module still has to be written, and what recurs is the TEMPLATE. The moves that do collapse a template are to generate these modules from the set they enumerate, or to replace the repeated construction with one factory each site calls with its own values — and where the set is the point, each module pinning one distinct thing, the repetition IS the enumeration and there is nothing to delete. — src/orders/application/use-cases/add-item-to-order/add-item-to-order.command-handler.ts:32
- src/orders/domain/validators/order-item-price.validator.ts:1 · src/orders/domain/validators/order-item-product.validator.ts:1 · src/orders/domain/validators/order-status.validator.ts:2 — the 3 copies are spread across 3 files, and each CITED SPAN is a SPECIALISATION DECLARATION — a type whose `extends` clause names a base and whose body hands that base its own values through `super(…)`. The shared module this dimension usually asks you to extract already exists: it is that base, every one of these sites already reaches it, and the `super(…)` call this row matched on is where each site passes its differences in. So do not read this as an extract-a-helper row — there is no missing helper, and what is left at each site is the declaration of one distinct specialisation, which cannot be deleted without deleting the thing it declares. Read what actually differs between the spans, because two different answers follow. Where the sites differ only in the values they hand the base — a type argument, a service, an alias, a cache — the repetition is a TEMPLATE, and the only moves that collapse it are to generate these declarations from the set they enumerate or to replace the repeated construction with one factory each site calls with its own values; where that set is the point, each site pinning one distinct thing, the repetition IS the enumeration and there is nothing to remove. Where instead a span carries logic OUTSIDE the delegation that is the same at every site, that logic is the part to move, and its home is the base type rather than a new module. Reported because the copies still drift apart the first time only one of them is edited. — src/orders/domain/validators/order-item-price.validator.ts:1
- src/shared/valueobjects/validators/description-length.validator.ts:2 · src/shared/valueobjects/validators/name-length.validator.ts:2 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — src/shared/valueobjects/validators/description-length.validator.ts:2
- src/orders/application/queries/get-order/get-order.query-handler.ts:7 · src/products/application/queries/get-product/get-product.query-handler.ts:7 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — src/orders/application/queries/get-order/get-order.query-handler.ts:7
- src/orders/application/use-cases/add-item-to-order/add-item-to-order.service.ts:1 · src/orders/application/use-cases/cancel-order/cancel-order.service.ts:1 · src/orders/application/use-cases/change-item-quantity/change-item-quantity.service.ts:1 · src/orders/application/use-cases/confirm-order/confirm-order.service.ts:1 · +5 more site(s) not listed — the 9 copies are spread across 9 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — src/orders/application/use-cases/add-item-to-order/add-item-to-order.service.ts:1
- src/orders/application/use-cases/create-order/create-order.service.ts:6 · src/products/application/use-cases/create-product/create-product.service.ts:6 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — src/orders/application/use-cases/create-order/create-order.service.ts:6
- src/products/application/use-cases/change-product-status/change-product-status.service.ts:6 · src/products/application/use-cases/update-product/update-product.service.ts:6 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — src/products/application/use-cases/change-product-status/change-product-status.service.ts:6
- src/orders/application/use-cases/add-item-to-order/add-item-to-order.command-handler.ts:32 · src/orders/application/use-cases/cancel-order/cancel-order.command-handler.ts:27 · src/orders/application/use-cases/change-item-quantity/change-item-quantity.command-handler.ts:29 · src/orders/application/use-cases/confirm-order/confirm-order.command-handler.ts:27 · +7 more site(s) not listed — the 11 copies are spread across 11 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. There is one copy in each of 11 separate files rather than several in one place, so check first whether these are sibling modules that each declare their own version of one shape — one per entity, per provider, per language. Where they are, no single extracted module collapses them: each module still has to be written, and what recurs is the TEMPLATE. The moves that do collapse a template are to generate these modules from the set they enumerate, or to replace the repeated construction with one factory each site calls with its own values — and where the set is the point, each module pinning one distinct thing, the repetition IS the enumeration and there is nothing to delete. — src/orders/application/use-cases/add-item-to-order/add-item-to-order.command-handler.ts:32
- src/products/application/queries/get-product/get-product.query-handler.ts:18 · src/products/application/queries/get-products/get-products.query-handler.ts:28 — the 2 copies are spread across 2 files, and what repeats is a LIST OF ENTRIES rather than behaviour — the same entries written out more than once. Extract them into one shared, exported constant and spread that constant into each site, rather than into a function the sites call: a list like this often lives in declarative metadata (a decorator's options object, a static configuration table) that a build step must be able to read statically, where a function call is not allowed. Adding an entry to one copy and not the other is the failure this prevents. — src/products/application/queries/get-product/get-product.query-handler.ts:18
- src/orders/domain/value-objects/shipping-address.vo.ts:75 · src/orders/domain/value-objects/shipping-address.vo.ts:81 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — src/orders/domain/value-objects/shipping-address.vo.ts:75
- libs/ddd/src/enum.ts:400 · libs/ddd/src/enum.ts:412 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — libs/ddd/src/enum.ts:400
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
- (top-level) has cyclomatic complexity 13 and cognitive complexity 16; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — src/orders/domain/validators/order-status.validator.ts:1
- (top-level) has cyclomatic complexity 11 and cognitive complexity 11; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — src/orders/domain/validators/order-customer.validator.ts:1
R3 · Large Files
- libs/ddd/src/aggregate-root.ts has 540 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — libs/ddd/src/aggregate-root.ts:1
- src/orders/domain/order-aggregate/order.ts has 538 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/orders/domain/order-aggregate/order.ts:1
- libs/ddd/src/valueobject.ts has 528 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — libs/ddd/src/valueobject.ts:1
- libs/ddd/src/tracking-state-manager.ts has 470 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — libs/ddd/src/tracking-state-manager.ts:1
- libs/ddd/src/domain-event.ts has 454 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — libs/ddd/src/domain-event.ts:1
- libs/ddd/src/enum.ts has 444 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — libs/ddd/src/enum.ts:1
- libs/ddd/src/state-transition.manager.ts has 440 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — libs/ddd/src/state-transition.manager.ts:1
What to do
- Split each oversized file along the responsibilities already in it, into smaller focused modules in the same package.
R4 · Test Coverage
- No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one. (×5) — scripts/merge-coverage.js:1, src/main.ts:1, src/products/domain/product-aggregate/events/ProductDescriptionChangedEvent.ts:1, …
What to do
- Add tests that import the unreached modules (directly or through their public entry).
R5 · Dependency Freshness
What to do
- Bump outdated dependencies to current versions to limit upgrade debt.
R6 · Tooling
R7 · Dead Code
- Unreachable from the 4 application, 4 tooling and 44 test entry point(s) detected in this repo. Gate removals on `npm run build` — an undetected custom entry would make these reachable.
- no import path from any entry point (4 application, 4 tooling, 44 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (src/products/domain/product-aggregate/events/index.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it (×2) — src/products/domain/product-aggregate/events/ProductDescriptionChangedEvent.ts, src/products/domain/product-aggregate/events/ProductNameChangedEvent.ts
- no import path from any entry point (4 application, 4 tooling, 44 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (src/orders/application/index.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — src/orders/application/use-cases/index.ts
- no import path from any entry point (4 application, 4 tooling, 44 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (src/products/domain/product-aggregate/index.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — src/products/domain/product-aggregate/events/index.ts
- no import path from any entry point (4 application, 4 tooling, 44 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make (×8) — src/products/application/use-cases/index.ts, src/orders/application/index.ts, src/orders/infrastructure/index.ts, …
- no import path from any entry point (4 application, 4 tooling, 44 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (src/products/domain/index.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — src/products/domain/product-aggregate/index.ts
- no import path from any entry point (4 application, 4 tooling, 44 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (src/orders/infrastructure/index.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — src/orders/infrastructure/repositories/index.ts
- no import path from any entry point (4 application, 4 tooling, 44 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (src/products/infrastructure/index.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — src/products/infrastructure/repositories/index.ts
- Nothing ultimately consumes this binding: its only referrer is the re-export in libs/ddd/src/core/repositories/index.ts, whose re-exported name has no consumer either. Removing it is therefore not a one-file change — drop the re-export line in libs/ddd/src/core/repositories/index.ts in the same commit, or the barrel will import a name that no longer exists. (×2) — libs/ddd/src/core/repositories/repository-read.interface.ts:9, libs/ddd/src/core/repositories/repository-write.interface.ts:4
- Nothing ultimately consumes this binding: its only referrer is the re-export in libs/ddd/src/core/validator-rules/interfaces/index.ts, whose re-exported name has no consumer either. Removing it is therefore not a one-file change — drop the re-export line in libs/ddd/src/core/validator-rules/interfaces/index.ts in the same commit, or the barrel will import a name that no longer exists. — libs/ddd/src/core/validator-rules/interfaces/irule-context.ts:5
- Nothing ultimately consumes this binding: its only referrer is the re-export in src/orders/application/queries/index.ts, whose re-exported name has no consumer either. Removing it is therefore not a one-file change — drop the re-export line in src/orders/application/queries/index.ts in the same commit, or the barrel will import a name that no longer exists. (×2) — src/orders/application/queries/dtos/order-response.dto.ts:1, src/orders/application/queries/dtos/order-response.dto.ts:5
- Nothing imports this binding — it is safe to review for removal. — src/orders/domain/order-aggregate/order-status.enum.ts:59
- Nothing ultimately consumes this binding: its only referrer is the re-export in src/products/application/queries/index.ts, whose re-exported name has no consumer either. Removing it is therefore not a one-file change — drop the re-export line in src/products/application/queries/index.ts in the same commit, or the barrel will import a name that no longer exists. (×2) — src/products/application/queries/dtos/product-response.dto.ts:1, src/products/application/queries/dtos/product-response.dto.ts:5
- Nothing ultimately consumes this binding: its only referrer is the re-export in src/products/application/use-cases/delete-product/index.ts, whose re-exported name has no consumer either. Removing it is therefore not a one-file change — drop the re-export line in src/products/application/use-cases/delete-product/index.ts in the same commit, or the barrel will import a name that no longer exists. — src/products/application/use-cases/delete-product/delete-product.dto.ts:1
- Nothing in its class reads or assigns this private field (for a constructor parameter property: it is stored and never read), and no string key or test reaches it by name. Remove it, or use it where it was meant to take effect. — libs/ddd/src/ddd.service.ts:10
- Nothing in its class calls or references this private method — no member access, no string key, no decorator, and no test reaches it by name. A private member cannot be called from outside its class, so this is the whole search: remove it, or call it where it was meant to be used. — src/orders/domain/order-aggregate/order.ts:494
What to do
- Delete the dead files and unused exports — every line is maintenance cost and rebuild-estimate inflation with zero runtime value.
R8 · Dependency Hygiene
- Imported but not declared in any reachable package.json — installs work only by hoisting accident. (×4) — src/shared/filters/domain-exception.filter.ts:8, scripts/merge-coverage.js:24, scripts/merge-coverage.js:25, …
- Only test files import it (first: libs/ddd/src/helpers/domain-object.helper.spec.ts:1) — move it to devDependencies. — package.json:43
What to do
- Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.
R9 · Circular Imports
- libs/ddd/src/aggregate-root.ts → libs/ddd/src/core/validator-rules/index.ts → libs/ddd/src/core/validator-rules/impl/index.ts → libs/ddd/src/core/validator-rules/impl/entity-validator.ts → libs/ddd/src/aggregate-root.ts (one verified cycle inside a mutually-dependent group of 14 files) — libs/ddd/src/aggregate-root.ts:3
- libs/ddd/src/core/business-rules/impl/property-change/notify-property-changed.base.ts → libs/ddd/src/core/business-rules/impl/property-change/notify-property-changed.context.ts → libs/ddd/src/core/business-rules/impl/property-change/notify-property-changed.base.ts — libs/ddd/src/core/business-rules/impl/property-change/notify-property-changed.base.ts:1
- src/orders/domain/entities/order-item.entity.ts → src/orders/domain/validators/index.ts → src/orders/domain/validators/order-amount.validator.ts → src/orders/domain/order-aggregate/order.ts → src/orders/domain/entities/order-item.entity.ts (one verified cycle inside a mutually-dependent group of 11 files) — src/orders/domain/entities/order-item.entity.ts:3
- src/products/domain/product-aggregate/product.ts → src/products/domain/product-aggregate/validators/index.ts → src/products/domain/product-aggregate/validators/product-business-rules.validator.ts → src/products/domain/product-aggregate/product.ts (one verified cycle inside a mutually-dependent group of 7 files) — src/products/domain/product-aggregate/product.ts:9
- src/shared/valueobjects/validators/index.ts → src/shared/valueobjects/validators/description-length.validator.ts → src/shared/valueobjects/description.ts → src/shared/valueobjects/validators/index.ts (one verified cycle inside a mutually-dependent group of 7 files) — src/shared/valueobjects/validators/index.ts:2
What to do
- Break each cycle by extracting the shared piece into a module both sides can import.
S1 · Web-Security Posture
- `app.listen(…)` serves plain HTTP on a network address, and nothing in its package enforces HTTPS: no TLS served (`https.createServer`, Fastify `https`, Nest `httpsOptions`), no redirect of plain requests to `https://`, no `Strict-Transport-Security` (helmet sends it by default), and no TLS-terminating proxy configuration committed beside it — so a browser may talk to it in clear text. (−2.0 on this card.) — src/main.ts:49
What to do
- Enforce HTTPS on each listed server: serve TLS itself, or redirect plain requests to `https://` and send `Strict-Transport-Security` (`helmet()` does by default) behind the TLS-terminating proxy — and commit that proxy's configuration beside the service. A server only this machine reaches should bind `127.0.0.1`.
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
X21 · Side-effecting pattern guard
X22 · Contradicted release guard
X23 · Unguarded diagnostic materialisation
X24 · Document value interpolated into markup unescaped
X25 · Inert configuration knob
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
X5 · Nullable reference types
- 0/2 of this repository's type-checking configuration(s) turn on strict null checking (`"strict": true`, or `"strictNullChecks": true`). A configuration that states neither is counted as OFF, because off is tsc's own default; a solution-style one whose `"files"` is empty and whose `"references"` point at other projects is in neither number, because it checks no source itself. Where it is off, `string` admits `null` and `undefined`: passing a value that is null compiles silently and throws on the first property access.
What to do
- The findings name the configuration each number was taken from and, for the assertions, the files that hold them. Turn null checking on where it is off — `"strict": true` in the base tsconfig that the others extend switches `strictNullChecks` on with the rest of the family — and then resolve the assertions rather than adding to them. A `!` on a value the checker could show to be null is a promise the author cannot check from where they are standing, and each one is a `TypeError: Cannot read properties of null` waiting for the path that makes it true; where the value genuinely cannot be null, say something the checker can see instead (narrow it with a test, make the property required, drop the `?`).
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 67% | Adequate — gated by X5 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 68% | Adequate — gated by D26, R9 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Maturity | 74% | Adequate — gated by M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 55% | Adequate — gated by R8 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 73% | Adequate — gated by D36 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Domain Modelling | 57% | Adequate — gated by DM4, DM2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Performance | 100% | Exemplary | Strongest area. |
Unscored — 4 check(s) recorded observations but carry no score
- D12 Dependency Hygiene — 2 observation(s) recorded · Dependency currency not established — registry.npmjs.org did not answer
- P12 CI test-gate honesty — 2 observation(s) recorded · Reported, not scored — this card publishes what the CI gate does with the test inventory rather than grading it. The findings above are its output.
- SC1 Supply-chain hygiene — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
- X10 Duplicated predicate — 3 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 1 control(s) we could not find positive evidence for
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 50 check(s) not relevant to this codebase
- AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
- AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
- AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
- AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
- AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
- AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
- AC7 A11y enforcement — No web markup found — accessibility is not applicable to this repository.
- AX1 Captive dependencies — Not applicable: NestJS makes a provider that injects a request-scoped one request-scoped itself (scope bubbles up the injection chain), and gives every consumer its own transient instance by contract.
- AX2 Stateful singletons — Not applicable: TypeScript/JavaScript runs each process's requests on one event loop, so no two requests write a shared object at the same instant (interleaving across an await is a different defect).
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AX8 Test isolation — no test/production split to check
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXR1 Runtime accessibility — the dev server (`npm run start`) kept running but served no page within 2 minutes. Likely cause (not identified): the dev server kept running but no port it opened served a page in the time allowed. Last output: "[Nest] 1656 - 11/08/2026, 6:26:11 AM LOG [RouterExplorer] Mapped {/orders/:id/confirm, POST} route +0ms / [Nest] 1656 - 11/08/2026, 6:26:11 AM LOG [RouterExplorer] Mapped {/orders/:id/ship, POST} route +0ms / [Nest] 1656 - 11/08/2026, 6:26:11 AM LOG [RouterExplorer] Mapped {/orders/:id/deliver, POST} route +0ms / [Nest] 1656 - 11/08/2026, 6:26:11 AM LOG [RouterExplorer] Mapped {/orders/:id/cancel, POST} route +0ms / [Nest] 1656 - 11/08/2026, 6:26:11 AM LOG [NestApplication] Nest application successfully started +3ms / Listening at http://localhost:3000" No runtime evidence was gathered. This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
- C1 Data Protection — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entity, a Mongoose schema, a Sequelize or Drizzle table, a Knex migration or a Prisma model — and no database or data-store client in the source either, so this repository keeps no data at rest for these controls to protect. If it does persist personal data (through a hosted backend configured outside this repository, for instance), the controls belong to wherever that data is stored.
- C3 Audit Trail — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entity, a Mongoose schema, a Sequelize or Drizzle table, a Knex migration or a Prisma model — and no database or data-store client in the source either, so this repository keeps no sensitive data whose changes an audit trail would record. If it does (through a hosted backend configured outside this repository, for instance), the trail belongs to wherever that data is stored.
- C4 Data Retention — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entity, a Mongoose schema, a Sequelize or Drizzle table, a Knex migration or a Prisma model — and no database or data-store client in the source either, so this repository keeps no personal data whose lifetime a retention limit would bound. If it does (through a hosted backend configured outside this repository, for instance), the limit belongs wherever that data is stored.
- C5 Data-Subject Rights — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entity, a Mongoose schema, a Sequelize or Drizzle table, a Knex migration or a Prisma model — and no database or data-store client in the source either, so this repository keeps no personal data for a data subject to erase, export or consent over. If it does (through a hosted backend configured outside this repository, for instance), the rights are served wherever that data is stored.
- D14 License Compliance — Not scored — this repository's 117 shipped npm package(s) were resolved from its committed lockfile, but registry.npmjs.org could not be asked for the licence of 2 of them (registry returned 429), and a licence verdict over part of a dependency graph is not a licence verdict. Nothing is asserted about this repository's licensing in either direction.
- 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.
- D21 Naming Consistency — Naming consistency is measured on C# and TypeScript only; JavaScript not measured.
- D22 Internal API Consistency — The exposed public-API surface could not be collected — no C#/VB projects loaded.
- D25 ADR Conformance — no ADRs to check
- D32 Data Compliance (PII/GDPR) — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
- D34 Knowledge Freshness — knowledge concentrated in recent work — freshness signal contradicted by repo activity
- 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.
- D4 Code Duplication — This repository's production source (.ts) is not read by D4's token comparison, which compares .NET source: duplication in it is measured by R10 Code Duplication, the frontend lens's card running the same clone algorithm over the JS/TS token stream. Not scored here — read the R10 card for this repository's duplication.
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
- DM10 One transaction, one aggregate — no repository writes detected — no operation to judge against the one-aggregate rule
- DM3 Integration-event coupling — no integration events detected — coupling check not applicable
- DM7 Repository granularity — no repository abstraction detected (e.g. uses a document session)
- ED1 Event-Driven — applicable but not scored (2 of 3 signals for this style — below the bar we score at): 8 event handler(s); 16 CQRS handler(s)
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- P7 Outbound HTTP resilience — no outbound HTTP usage detected — no HTTP client call or construction in the JavaScript/TypeScript source (service entry point: src/main.ts:11 (NestFactory.create))
- 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
- PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for tinybench, mitata, benchmark.js, benny or vitest `bench(...)` calls in files that import them (or `*.bench.*` files), or one of those in a package.json, 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.
- R11 Import Boundaries — No recognizable feature-sliced/layered src layout — boundary rules not applicable.
- X2 Cancellation propagation — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X20 Mistyped argument guard — This check asks whether an argument guard reports an EMPTY value as a NULL one, which needs a language that throws a null-specific argument exception — .NET's ArgumentNullException, the JVM's NullPointerException, Dart's ArgumentError.notNull. This repository contains none of those languages: the ones it is written in have a single exception for a bad argument, so there is no pair of exceptions to confuse and nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X26 Unsynchronised callback handoff — Not applicable: this check looks for a collection written by a callback on one thread while the body waiting on it touches it on another, and in this repository's languages no collection is reachable from two threads at once. TypeScript/JavaScript runs every callback on the one thread that owns its objects: a callback runs only when the body waiting on it has yielded, never alongside it, and a worker thread receives a COPY of what it is sent. A SharedArrayBuffer carries raw bytes, never an Array, Map or Set, so no collection is reachable from two threads at once. Not a gap in the analyzer and not a finding about your code.
- X27 Collection changed while being enumerated — Not applicable: this check looks for a loop whose body adds to or removes from the very collection the loop is walking, invalidating the enumerator it holds, and in this repository's languages that cannot happen. JavaScript and TypeScript have no iterator that a change can invalidate: an `Array` is walked by index against its live length, and a `Map` or `Set` by the ECMAScript specification's live entry list, so a body that adds to, removes from or empties what it walks raises nothing — every loop form (`for…of`, `for…in`, `forEach`, `map`, `filter`, `reduce`, `entries()`) on every built-in collection (`Array`, `Map`, `Set`, plain objects, `URLSearchParams`, `Headers`, `FormData`) runs to completion. Such a loop can still skip an element or never end, which is a different defect and not the one this check asks about. Not a gap in the analyzer and not a finding about your code.
- X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X4 Structured logging — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X6 Hand-rolled structured-format parsing — 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 — 51 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
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Import cycle (4 files) libs/ddd/src/aggregate-root.ts:3
- Import cycle (4 files) src/orders/domain/entities/order-item.entity.ts:3
- Import cycle (3 files) src/products/domain/product-aggregate/product.ts:9
- Import cycle (3 files) src/shared/valueobjects/validators/index.ts:2
- REDACTED
- Domain depends on infrastructure: order src/orders/domain/order-aggregate/order.ts:1
- Unlisted import 'express' src/shared/filters/domain-exception.filter.ts:8
- Unlisted import 'istanbul-lib-coverage' scripts/merge-coverage.js:24
- Unlisted import 'istanbul-lib-report' scripts/merge-coverage.js:25
- Unlisted import 'istanbul-reports' scripts/merge-coverage.js:26
- Import cycle (2 files) libs/ddd/src/core/business-rules/impl/property-change/notify-property-changed.base.ts:1
Serious — 148 finding(s)
- Low coverage: src/orders/application/events/order-cancelled.event-handler.ts src/orders/application/events/order-cancelled.event-handler.ts:1
- Low coverage: src/orders/application/events/order-confirmed.event-handler.ts src/orders/application/events/order-confirmed.event-handler.ts:1
- Low coverage: src/orders/application/events/order-created.event-handler.ts src/orders/application/events/order-created.event-handler.ts:1
- Low coverage: src/orders/application/events/order-item-added.event-handler.ts src/orders/application/events/order-item-added.event-handler.ts:1
- Low coverage: src/orders/application/events/order-shipped.event-handler.ts src/orders/application/events/order-shipped.event-handler.ts:1
- Low coverage: src/orders/application/queries/get-order/get-order.query-handler.ts src/orders/application/queries/get-order/get-order.query-handler.ts:1
- Low coverage: src/orders/application/queries/get-order/get-order.query.ts src/orders/application/queries/get-order/get-order.query.ts:1
- Low coverage: src/orders/application/queries/get-orders/get-orders.query-handler.ts src/orders/application/queries/get-orders/get-orders.query-handler.ts:1
- Low coverage: src/orders/application/queries/get-orders/get-orders.query.ts src/orders/application/queries/get-orders/get-orders.query.ts:1
- Low coverage: src/orders/application/sagas/order.saga.ts src/orders/application/sagas/order.saga.ts:1
- Low coverage: src/orders/application/use-cases/add-item-to-order/add-item-to-order.command-handler.ts src/orders/application/use-cases/add-item-to-order/add-item-to-order.command-handler.ts:1
- Low coverage: src/orders/application/use-cases/add-item-to-order/add-item-to-order.command.ts src/orders/application/use-cases/add-item-to-order/add-item-to-order.command.ts:1
- Low coverage: src/orders/application/use-cases/add-item-to-order/add-item-to-order.service.ts src/orders/application/use-cases/add-item-to-order/add-item-to-order.service.ts:1
- Low coverage: src/orders/application/use-cases/cancel-order/cancel-order.command-handler.ts src/orders/application/use-cases/cancel-order/cancel-order.command-handler.ts:1
- Low coverage: src/orders/application/use-cases/cancel-order/cancel-order.command.ts src/orders/application/use-cases/cancel-order/cancel-order.command.ts:1
- Low coverage: src/orders/application/use-cases/cancel-order/cancel-order.service.ts src/orders/application/use-cases/cancel-order/cancel-order.service.ts:1
- Low coverage: src/orders/application/use-cases/change-item-quantity/change-item-quantity.command-handler.ts src/orders/application/use-cases/change-item-quantity/change-item-quantity.command-handler.ts:1
- Low coverage: src/orders/application/use-cases/change-item-quantity/change-item-quantity.command.ts src/orders/application/use-cases/change-item-quantity/change-item-quantity.command.ts:1
- Low coverage: src/orders/application/use-cases/change-item-quantity/change-item-quantity.service.ts src/orders/application/use-cases/change-item-quantity/change-item-quantity.service.ts:1
- Low coverage: src/orders/application/use-cases/confirm-order/confirm-order.command-handler.ts src/orders/application/use-cases/confirm-order/confirm-order.command-handler.ts:1
- Low coverage: src/orders/application/use-cases/confirm-order/confirm-order.command.ts src/orders/application/use-cases/confirm-order/confirm-order.command.ts:1
- Low coverage: src/orders/application/use-cases/confirm-order/confirm-order.service.ts src/orders/application/use-cases/confirm-order/confirm-order.service.ts:1
- Low coverage: src/orders/application/use-cases/create-order/create-order.command-handler.ts src/orders/application/use-cases/create-order/create-order.command-handler.ts:1
- Low coverage: src/orders/application/use-cases/create-order/create-order.command.ts src/orders/application/use-cases/create-order/create-order.command.ts:1
- Low coverage: src/orders/application/use-cases/create-order/create-order.service.ts src/orders/application/use-cases/create-order/create-order.service.ts:1
- Dead file (~1 LoC) src/orders/application/index.ts
- Dead file (~1 LoC) src/orders/infrastructure/index.ts
- Dead file (~1 LoC) src/orders/infrastructure/repositories/index.ts
- Dead file (~1 LoC) src/orders/presentation/index.ts
- Dead file (~1 LoC) src/products/domain/index.ts
- Dead file (~1 LoC) src/products/infrastructure/index.ts
- Dead file (~1 LoC) src/products/infrastructure/repositories/index.ts
- Dead file (~1 LoC) src/products/presentation/index.ts
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- No test reaches this file scripts/merge-coverage.js:1
- No test reaches this file src/main.ts:1
- No test reaches this file src/products/domain/product-aggregate/events/ProductDescriptionChangedEvent.ts:1
- No test reaches this file src/products/domain/product-aggregate/events/ProductNameChangedEvent.ts:1
- No test reaches this file src/products/application/index.ts:1
- Fake-async — async method never awaits src/orders/infrastructure/repositories/order.repository.ts:12
- Fake-async — async method never awaits src/orders/infrastructure/repositories/order.repository.ts:24
- Fake-async — async method never awaits src/products/infrastructure/repositories/product.repository.ts:12
- Fake-async — async method never awaits src/products/infrastructure/repositories/product.repository.ts:24
- Duplicated block (16 lines × 2 locations) libs/ddd/src/aggregate-root.ts:468
- Duplicated block (16 lines × 2 locations) src/orders/application/use-cases/remove-item-from-order/remove-item-from-order.command-handler.ts:8
- Duplicated block (16 lines × 2 locations) src/orders/presentation/orders.controller.ts:131
- Duplicated block (8 lines × 2 locations) src/orders/application/queries/get-order/get-order.query-handler.ts:7
- Duplicated block (8 lines × 2 locations) src/orders/application/use-cases/create-order/create-order.service.ts:6
- Duplicated block (8 lines × 2 locations) src/products/application/use-cases/change-product-status/change-product-status.service.ts:6
- Anemic entity: OrderItem src/orders/domain/entities/order-item.entity.ts:45
- Anemic entity: Order src/orders/domain/order-aggregate/order.ts:92
- CI formatting step cannot fail REDACTED:40
- CI formatting step cannot fail REDACTED:56
- Test failure does not fail the CI gate REDACTED:148
- Test failure does not fail the CI gate REDACTED:217
- Duplicated block (25 lines × 2 locations) src/orders/application/use-cases/cancel-order/cancel-order.command-handler.ts:7
- Duplicated block (25 lines × 2 locations) src/orders/application/use-cases/confirm-order/confirm-order.command-handler.ts:7
- OrderStatusValidator.addRules (cognitive 16) src/orders/domain/validators/order-status.validator.ts:10
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Type Safety
- Duplication concentrated across 3 sibling directories (21 clone groups) src/orders/presentation/orders.controller.ts:50
- Duplicated block with local edits (61 matched lines × 2 locations) libs/ddd/src/valueobjects/number.valueobject.ts:80
- Duplicated block with local edits (41 matched lines × 2 locations) src/orders/domain/value-objects/customer-info.vo.ts:8
- Duplicated block (33 lines × 2 locations) src/orders/presentation/orders.controller.ts:50
- Duplicated block (27 lines × 2 locations) libs/ddd/src/valueobjects/number-notnull.validator.ts:48
- Duplicated block (26 lines × 2 locations) src/orders/application/use-cases/change-item-quantity/change-item-quantity.command-handler.ts:8
- Duplicated block (21 lines × 3 locations) src/shared/valueobjects/Name.ts:1
- Duplicated block (20 lines × 2 locations) src/orders/application/queries/get-order/get-order.query-handler.ts:18
- Duplicated block (20 lines × 3 locations) src/products/domain/product-aggregate/events/ProductNameChangedEvent.ts:3
- Duplicated block (14 lines × 3 locations) src/orders/application/sagas/order.saga.ts:42
- Duplicated block with local edits (13 matched lines × 2 locations) src/orders/domain/order-aggregate/order.ts:609
- Duplicated block (12 lines × 2 locations) libs/ddd/src/broken-rules.manager.ts:230
- Duplicated block with local edits (12 matched lines × 2 locations) src/shared/valueobjects/validators/description-length.validator.ts:5
- Duplicated block with local edits (11 matched lines × 2 locations) libs/ddd/src/aggregate-root.ts:371
- Duplicated block (10 lines × 4 locations) src/products/domain/product-aggregate/events/ProductCreatedEvent.ts:15
- Duplicated block (9 lines × 8 locations) src/orders/application/events/order-cancelled.event-handler.ts:1
- Duplicated block (9 lines × 9 locations) src/orders/application/use-cases/add-item-to-order/add-item-to-order.command-handler.ts:32
- Duplicated block (9 lines × 3 locations) src/orders/domain/validators/order-item-price.validator.ts:1
- Duplicated block (9 lines × 2 locations) src/shared/valueobjects/validators/description-length.validator.ts:2
- Duplicated block (8 lines × 9 locations) src/orders/application/use-cases/add-item-to-order/add-item-to-order.service.ts:1
- Duplicated block (7 lines × 11 locations) src/orders/application/use-cases/add-item-to-order/add-item-to-order.command-handler.ts:32
- Duplicated block (7 lines × 2 locations) src/products/application/queries/get-product/get-product.query-handler.ts:18
- Duplicated block (6 lines × 2 locations) src/orders/domain/value-objects/shipping-address.vo.ts:75
- Duplicated block (5 lines × 2 locations) libs/ddd/src/enum.ts:400
- Complex function (top-level) (cyclomatic 13, cognitive 16) src/orders/domain/validators/order-status.validator.ts:1
- Complex function (top-level) (cyclomatic 11, cognitive 11) src/orders/domain/validators/order-customer.validator.ts:1
- libs/ddd/src/aggregate-root.ts: 540 lines of code libs/ddd/src/aggregate-root.ts:1
- src/orders/domain/order-aggregate/order.ts: 538 lines of code src/orders/domain/order-aggregate/order.ts:1
- libs/ddd/src/valueobject.ts: 528 lines of code libs/ddd/src/valueobject.ts:1
- libs/ddd/src/tracking-state-manager.ts: 470 lines of code libs/ddd/src/tracking-state-manager.ts:1
- libs/ddd/src/domain-event.ts: 454 lines of code libs/ddd/src/domain-event.ts:1
- libs/ddd/src/enum.ts: 444 lines of code libs/ddd/src/enum.ts:1
- libs/ddd/src/state-transition.manager.ts: 440 lines of code libs/ddd/src/state-transition.manager.ts:1
- Dead file (~27 LoC) src/products/domain/product-aggregate/events/ProductDescriptionChangedEvent.ts
- Dead file (~25 LoC) src/products/domain/product-aggregate/events/ProductNameChangedEvent.ts
- Dead file (~8 LoC) src/orders/application/use-cases/index.ts
- Dead file (~5 LoC) src/products/domain/product-aggregate/events/index.ts
- Dead file (~4 LoC) src/products/application/use-cases/index.ts
- Dead file (~3 LoC) src/products/domain/product-aggregate/index.ts
- Dead file (~0 LoC) src/products/application/index.ts
- JavaScript dependencies are not locked libs/ddd/package.json:37
Minor — 79 finding(s)
- Console output used as the logging channel src/products/domain/product-aggregate/product.ts:165
- Console output used as the logging channel src/products/domain/product-aggregate/product.ts:201
- Console output used as the logging channel src/products/domain/product-aggregate/product.ts:208
- Console output used as the logging channel src/orders/domain/value-objects/money.vo.ts:17
- Console output used as the logging channel src/orders/domain/entities/order-item.entity.ts:27
- Console output used as the logging channel libs/ddd/src/aggregate-root.ts:161
- Console output used as the logging channel libs/ddd/src/broken-rules.manager.ts:36
- Console output used as the logging channel libs/ddd/src/broken-rules.manager.ts:181
- Console output used as the logging channel libs/ddd/src/enum.ts:52
- Console output used as the logging channel libs/ddd/src/enum.ts:53
- Console output used as the logging channel libs/ddd/src/enum.ts:128
- Console output used as the logging channel libs/ddd/src/enum.ts:241
- Console output used as the logging channel libs/ddd/src/enum.ts:268
- Console output used as the logging channel libs/ddd/src/state-transition.manager.ts:305
- Console output used as the logging channel libs/ddd/src/state-transition.manager.ts:366
- Console output used as the logging channel libs/ddd/src/state-transition.manager.ts:389
- Console output used as the logging channel libs/ddd/src/tracking-state-manager.ts:66
- Console output used as the logging channel libs/ddd/src/tracking-state-manager.ts:71
- Console output used as the logging channel libs/ddd/src/tracking-state-manager.ts:97
- Console output used as the logging channel libs/ddd/src/tracking-state-manager.ts:101
- Console output used as the logging channel libs/ddd/src/tracking-state-manager.ts:115
- Console output used as the logging channel libs/ddd/src/tracking-state-manager.ts:119
- Console output used as the logging channel libs/ddd/src/tracking-state-manager.ts:141
- Console output used as the logging channel libs/ddd/src/tracking-state-manager.ts:159
- Console output used as the logging channel libs/ddd/src/tracking-state-manager.ts:204
- redundant comment libs/ddd/src/core/aggregate/aggregate-validation-orchestrator.spec.ts:17
- redundant comment libs/ddd/src/valueobject.ts:319
- redundant comment libs/ddd/src/valueobjects/number-notnull.validator.ts:80
- redundant comment libs/ddd/src/valueobjects/string-notnullorempty.validator.ts:101
- redundant comment src/orders/application/use-cases/create-order/create-order.command-handler.ts:57
- redundant comment src/orders/domain/order-aggregate/order.ts:262
- Duplicated predicate libs/ddd/src/broken-rules.manager.ts:229
- Duplicated predicate libs/ddd/src/aggregate-root.ts:472
- Duplicated predicate libs/ddd/src/broken-rules.manager.ts:242
- Mock-dominated test: debe invocar múltiples callbacks registrados libs/ddd/src/core/business-rules/impl/property-change/notify-property-changed.base.spec.ts:270
- Mock-dominated test: debe permitir múltiples callbacks diferentes libs/ddd/src/core/business-rules/impl/property-change/notify-property-changed.context.spec.ts:73
- No named authorization policies src/orders/domain/order-aggregate/order.ts:510
- No ADRs found
- Projects may be oversized for their cohesion
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Primitive id on a domain type: OrderCreatedEvent.customerId src/orders/domain/events/order.events.ts:11
- No ADRs
- Dependabot does not watch github-actions REDACTED:2
- No rollback/health safety
- Unused export 'IDomainReadRepository' libs/ddd/src/core/repositories/repository-read.interface.ts:9
- Unused export 'IDomainWriteRepository' libs/ddd/src/core/repositories/repository-write.interface.ts:4
- Unused export 'IRuleContext' libs/ddd/src/core/validator-rules/interfaces/irule-context.ts:5
- Unused export 'GetOrderDto' src/orders/application/queries/dtos/order-response.dto.ts:1
- Unused export 'GetOrdersDto' src/orders/application/queries/dtos/order-response.dto.ts:5
- Unused export 'getStatusDisplayName' src/orders/domain/order-aggregate/order-status.enum.ts:59
- Unused export 'GetProductDto' src/products/application/queries/dtos/product-response.dto.ts:1
- Unused export 'GetProductsDto' src/products/application/queries/dtos/product-response.dto.ts:5
- Unused export 'DeleteProductDto' src/products/application/use-cases/delete-product/delete-product.dto.ts:1
- Unused private field 'modulesContainer' libs/ddd/src/ddd.service.ts:10
- Unused private method 'findItemByProductId' src/orders/domain/order-aggregate/order.ts:494
- Test-only dependency 'reflect-metadata' in production deps package.json:43
- No app-layer HTTPS enforcement detected src/main.ts:49
- Strict null checking is not enabled everywhere the repository type-checks
Minor — 2 finding(s)
- doc comments repeat the names libs/ddd/src/aggregate-root.ts:584
- doc comments repeat the names src/orders/domain/entities/order-item.entity.ts:86
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-b73842e0600a426a8bdee8db817529e0/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-b73842e0600a426a8bdee8db817529e0/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 . | 25 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . --skip-db-update | 18 | artifacts/raw/trivy-fs.json |
| D31 · IaC & Container Security | trivy | — | trivy config --format json --quiet . | 2 | 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 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . --skip-db-update | 0 | artifacts/raw/trivy-fs.json |