Executive summary
rafaelfgx/Microservices falls short of our standard for production because we found no automated security scanning of the code, its secrets or its dependencies. It scores 64 out of 100 and is rated Adequate, and all 17 of its critical findings are security problems.
Production Readiness, at 50, is the weakest lens and counts most in the score. The best first step is recording design decisions, worth about 4 points. Adding structured logging would lift Production Readiness itself, also worth about 4. Raising Production Readiness to 70 would lift the score to about 73.
Nine settings leave the servers or containers unsafe. Six pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Correcting the unsafe settings and pinning each tool to an exact version would close both risks. Updating the vulnerable packages would fix the two packages with a known security hole.
The product code is 3,054 lines, about €8,700 to rebuild.
If Production Readiness rose from 50 to 70, the lowest score rated Strong, the score would rise from 64 to about 73.
New since the last survey: 1 finding
- Dependency Vulnerabilities · REDACTED
Fixed since the last survey: 32 findings
- Test Quality · No assertions: shouldThrowConflictWhenNoUserMatchesBothUsernameAndEmail authservice/src/test/java/com/company/authservice/keycloak/KeycloakServiceTest.java
- Test Quality · No assertions: shouldThrowInvalidCredentialsWhenTokenIsRejected authservice/src/test/java/com/company/authservice/keycloak/KeycloakServiceTest.java
- Test Quality · No assertions: shouldHandleAsBadGatewayWhenHttpServerErrorExceptionOccurs starter/src/test/java/com/company/starter/exception/GlobalExceptionHandlerTest.java
- Test Quality · No assertions: shouldHandleAsBadGatewayWhenResourceAccessExceptionOccurs starter/src/test/java/com/company/starter/exception/GlobalExceptionHandlerTest.java
- Test Quality · No assertions: shouldHandleAsBadRequestWhenConstraintViolationExceptionOccurs starter/src/test/java/com/company/starter/exception/GlobalExceptionHandlerTest.java
- Test Quality · No assertions: shouldHandleAsBadRequestWhenHandlerMethodValidationExceptionOccurs starter/src/test/java/com/company/starter/exception/GlobalExceptionHandlerTest.java
- Test Quality · No assertions: shouldHandleAsBadRequestWhenHttpMessageNotReadableExceptionOccurs starter/src/test/java/com/company/starter/exception/GlobalExceptionHandlerTest.java
- Test Quality · No assertions: shouldHandleAsBadRequestWhenMethodArgumentNotValidExceptionOccurs starter/src/test/java/com/company/starter/exception/GlobalExceptionHandlerTest.java
- Test Quality · No assertions: shouldHandleAsBadRequestWhenMethodArgumentTypeMismatchExceptionOccurs starter/src/test/java/com/company/starter/exception/GlobalExceptionHandlerTest.java
- Test Quality · No assertions: shouldHandleAsBadRequestWhenMissingServletRequestParameterExceptionOccurs starter/src/test/java/com/company/starter/exception/GlobalExceptionHandlerTest.java
- Test Quality · No assertions: shouldHandleAsBadRequestWhenTypeMismatchExceptionOccurs starter/src/test/java/com/company/starter/exception/GlobalExceptionHandlerTest.java
- Test Quality · No assertions: shouldHandleAsForbiddenWhenAccessDeniedExceptionOccurs starter/src/test/java/com/company/starter/exception/GlobalExceptionHandlerTest.java
- Test Quality · No assertions: shouldHandleAsInternalServerErrorWhenUnexpectedExceptionOccurs starter/src/test/java/com/company/starter/exception/GlobalExceptionHandlerTest.java
- Test Quality · No assertions: shouldHandleAsMethodNotAllowedWhenHttpRequestMethodNotSupportedExceptionOccurs starter/src/test/java/com/company/starter/exception/GlobalExceptionHandlerTest.java
- Test Quality · No assertions: shouldHandleAsNotFoundWhenApplicationExceptionOccurs starter/src/test/java/com/company/starter/exception/GlobalExceptionHandlerTest.java
- Test Quality · No assertions: shouldHandleAsNotFoundWhenNoResourceFoundExceptionOccurs starter/src/test/java/com/company/starter/exception/GlobalExceptionHandlerTest.java
- Test Quality · No assertions: shouldHandleAsServiceUnavailableWhenAsyncRequestTimeoutExceptionOccurs starter/src/test/java/com/company/starter/exception/GlobalExceptionHandlerTest.java
- Test Quality · No assertions: shouldHandleAsUnsupportedMediaTypeWhenHttpMediaTypeNotSupportedExceptionOccurs starter/src/test/java/com/company/starter/exception/GlobalExceptionHandlerTest.java
- Test Quality · No assertions: shouldHandleWithProblemDetailWhenErrorResponseExceptionOccurs starter/src/test/java/com/company/starter/exception/GlobalExceptionHandlerTest.java
- Test Quality · No assertions: shouldHandleWithProblemDetailWhenResponseStatusExceptionOccurs starter/src/test/java/com/company/starter/exception/GlobalExceptionHandlerTest.java
- Test Quality · No assertions: shouldResolveFieldErrorsWhenMessageSourceIsConfigured starter/src/test/java/com/company/starter/exception/GlobalExceptionHandlerTest.java
- Test Quality · No assertions: shouldFallbackToAnonymousWhenJwtHasNoRelevantClaims starter/src/test/java/com/company/starter/filters/SubjectFilterTest.java
- Test Quality · No assertions: shouldPreferUserNameWhenJwtHasUserAndClientClaims starter/src/test/java/com/company/starter/filters/SubjectFilterTest.java
- Test Quality · No assertions: shouldPutAnonymousWhenNoAuthenticationExists starter/src/test/java/com/company/starter/filters/SubjectFilterTest.java
- Test Quality · No assertions: shouldPutAnonymousWhenPrincipalIsNotJwt starter/src/test/java/com/company/starter/filters/SubjectFilterTest.java
- Test Quality · No assertions: shouldPutAuthenticatedUserInMdc starter/src/test/java/com/company/starter/filters/SubjectFilterTest.java
- Test Quality · No assertions: shouldPutClientInMdcWhenJwtHasClientOnlyClaims starter/src/test/java/com/company/starter/filters/SubjectFilterTest.java
- Dependency Vulnerabilities · Critical CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
Rebuild cost: about €8,700 · Estimate
| Cost to rebuild | €2,900 to €15,000, for 48 to 153 hours of work, under 0.1 person-years for one engineer |
|---|---|
| Difficulty of the problem | Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.9 at a score of 64. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it. |
| Size | Small: 3,054 lines of product code |
| What it is not | Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one. |
Top priorities
Diagnosis: what the measurements show together
Architecture — module dependency graph
Architecture: which parts of the code depend on which
| uses → | 1 authservice | 2 configurationservice | 3 configurationservice.configuration.requests | 4 customerservice | 5 customerservice.customer.domains | 6 customerservice.customer.requests | 7 customerservice.customer.responses | 8 orderservice | 9 orderservice.order.domains | 10 orderservice.order.events | 11 orderservice.order.requests | 12 paymentservice.payment.domains | 13 paymentservice.payment.events | 14 paymentservice.payment.requests | 15 productservice.product.domains | 16 productservice.product.requests | 17 productservice.product.responses | 18 starter.clients.auth.dtos | 19 starter.configuration | 20 starter.exception | 21 starter.mediator | 22 starter.outbox | 23 authservice.user | 24 configurationservice.configuration | 25 customerservice.customer | 26 orderservice.order.responses | 27 paymentservice.payment.responses | 28 productservice.product | 29 starter.clients.auth | 30 authservice.keycloak | 31 configurationservice.configuration.handlers | 32 customerservice.customer.handlers | 33 orderservice.order | 34 paymentservice.payment | 35 productservice.product.handlers | 36 authservice.auth | 37 orderservice.order.handlers | 38 paymentservice.payment.handlers | 39 orderservice.order.listeners | 40 paymentservice.payment.listeners |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 authservice | ||||||||||||||||||||||||||||||||||||||||
| 2 configurationservice | ||||||||||||||||||||||||||||||||||||||||
| 3 configurationservice.configuration.requests | ||||||||||||||||||||||||||||||||||||||||
| 4 customerservice | ||||||||||||||||||||||||||||||||||||||||
| 5 customerservice.customer.domains | ||||||||||||||||||||||||||||||||||||||||
| 6 customerservice.customer.requests | ||||||||||||||||||||||||||||||||||||||||
| 7 customerservice.customer.responses | ||||||||||||||||||||||||||||||||||||||||
| 8 orderservice | ||||||||||||||||||||||||||||||||||||||||
| 9 orderservice.order.domains | ||||||||||||||||||||||||||||||||||||||||
| 10 orderservice.order.events | ||||||||||||||||||||||||||||||||||||||||
| 11 orderservice.order.requests | ||||||||||||||||||||||||||||||||||||||||
| 12 paymentservice.payment.domains | ||||||||||||||||||||||||||||||||||||||||
| 13 paymentservice.payment.events | ||||||||||||||||||||||||||||||||||||||||
| 14 paymentservice.payment.requests | ||||||||||||||||||||||||||||||||||||||||
| 15 productservice.product.domains | ||||||||||||||||||||||||||||||||||||||||
| 16 productservice.product.requests | ||||||||||||||||||||||||||||||||||||||||
| 17 productservice.product.responses | ||||||||||||||||||||||||||||||||||||||||
| 18 starter.clients.auth.dtos | ||||||||||||||||||||||||||||||||||||||||
| 19 starter.configuration | ||||||||||||||||||||||||||||||||||||||||
| 20 starter.exception | ||||||||||||||||||||||||||||||||||||||||
| 21 starter.mediator | ||||||||||||||||||||||||||||||||||||||||
| 22 starter.outbox | ||||||||||||||||||||||||||||||||||||||||
| 23 authservice.user | 1 | |||||||||||||||||||||||||||||||||||||||
| 24 configurationservice.configuration | 4 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 25 customerservice.customer | 1 | 7 | 2 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||
| 26 orderservice.order.responses | 1 | |||||||||||||||||||||||||||||||||||||||
| 27 paymentservice.payment.responses | 1 | |||||||||||||||||||||||||||||||||||||||
| 28 productservice.product | 1 | 7 | 2 | 1 | ||||||||||||||||||||||||||||||||||||
| 29 starter.clients.auth | 2 | |||||||||||||||||||||||||||||||||||||||
| 30 authservice.keycloak | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 31 configurationservice.configuration.handlers | 5 | 3 | 7 | 10 | ||||||||||||||||||||||||||||||||||||
| 32 customerservice.customer.handlers | 1 | 6 | 2 | 6 | 8 | 2 | ||||||||||||||||||||||||||||||||||
| 33 orderservice.order | 1 | 1 | 5 | 1 | 2 | |||||||||||||||||||||||||||||||||||
| 34 paymentservice.payment | 2 | 3 | 3 | 1 | 2 | |||||||||||||||||||||||||||||||||||
| 35 productservice.product.handlers | 5 | 2 | 5 | 7 | ||||||||||||||||||||||||||||||||||||
| 36 authservice.auth | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 37 orderservice.order.handlers | 2 | 2 | 3 | 5 | 1 | 2 | 6 | |||||||||||||||||||||||||||||||||
| 38 paymentservice.payment.handlers | 2 | 1 | 5 | 6 | 2 | 3 | 9 | |||||||||||||||||||||||||||||||||
| 39 orderservice.order.listeners | 2 | 2 | ||||||||||||||||||||||||||||||||||||||
| 40 paymentservice.payment.listeners | 1 | 1 |
23→30 authservice.user uses authservice.keycloak part of a loop✕
- Connections
- 1 pair of types, where a type in authservice.user uses a type in authservice.keycloak.
- The types involved
com.company.authservice.user.UserController→com.company.authservice.keycloak.KeycloakService
- Direction
- authservice.user uses authservice.keycloak, so a change to authservice.keycloak can break authservice.user, while a change to authservice.user can't break authservice.keycloak.
- 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.
24→3 configurationservice.configuration uses configurationservice.configuration.requests✕
- Connections
- 4 pairs of types, where a type in configurationservice.configuration uses a type in configurationservice.configuration.requests.
- The types involved
com.company.configurationservice.configuration.ConfigurationController→com.company.configurationservice.configuration.requests.CreateConfigurationRequestcom.company.configurationservice.configuration.ConfigurationController→com.company.configurationservice.configuration.requests.UpdateConfigurationRequestcom.company.configurationservice.configuration.ConfigurationMapper→com.company.configurationservice.configuration.requests.CreateConfigurationRequestcom.company.configurationservice.configuration.ConfigurationMapper→com.company.configurationservice.configuration.requests.UpdateConfigurationRequest
- Direction
- configurationservice.configuration uses configurationservice.configuration.requests, so a change to configurationservice.configuration.requests can break configurationservice.configuration, while a change to configurationservice.configuration can't break configurationservice.configuration.requests.
- Position
- Below the diagonal: configurationservice.configuration uses a module listed above it, which is the healthy direction.
24→19 configurationservice.configuration uses starter.configuration✕
- Connections
- 1 pair of types, where a type in configurationservice.configuration uses a type in starter.configuration.
- The types involved
com.company.configurationservice.configuration.ConfigurationController→com.company.starter.configuration.Configuration
- Direction
- configurationservice.configuration uses starter.configuration, so a change to starter.configuration can break configurationservice.configuration, while a change to configurationservice.configuration can't break starter.configuration.
- Position
- Below the diagonal: configurationservice.configuration uses a module listed above it, which is the healthy direction.
24→21 configurationservice.configuration uses starter.mediator✕
- Connections
- 1 pair of types, where a type in configurationservice.configuration uses a type in starter.mediator.
- The types involved
com.company.configurationservice.configuration.ConfigurationController→com.company.starter.mediator.Mediator
- Direction
- configurationservice.configuration uses starter.mediator, so a change to starter.mediator can break configurationservice.configuration, while a change to configurationservice.configuration can't break starter.mediator.
- Position
- Below the diagonal: configurationservice.configuration uses a module listed above it, which is the healthy direction.
25→5 customerservice.customer uses customerservice.customer.domains✕
- Connections
- 1 pair of types, where a type in customerservice.customer uses a type in customerservice.customer.domains.
- The types involved
com.company.customerservice.customer.CustomerMapper→com.company.customerservice.customer.domains.Customer
- Direction
- customerservice.customer uses customerservice.customer.domains, so a change to customerservice.customer.domains can break customerservice.customer, while a change to customerservice.customer can't break customerservice.customer.domains.
- Position
- Below the diagonal: customerservice.customer uses a module listed above it, which is the healthy direction.
25→6 customerservice.customer uses customerservice.customer.requests✕
- Connections
- 7 pairs of types, where a type in customerservice.customer uses a type in customerservice.customer.requests.
- The types involved
com.company.customerservice.customer.CustomerController→com.company.customerservice.customer.requests.CreateCustomerRequestcom.company.customerservice.customer.CustomerController→com.company.customerservice.customer.requests.ListCustomerRequestcom.company.customerservice.customer.CustomerController→com.company.customerservice.customer.requests.UpdateCustomerRequestcom.company.customerservice.customer.CustomerMapper→com.company.customerservice.customer.requests.CreateCustomerRequestcom.company.customerservice.customer.CustomerMapper→com.company.customerservice.customer.requests.ListCustomerRequestcom.company.customerservice.customer.CustomerMapper→com.company.customerservice.customer.requests.UpdateCustomerRequestcom.company.customerservice.customer.CustomerRepository→com.company.customerservice.customer.requests.ListCustomerRequest
- Direction
- customerservice.customer uses customerservice.customer.requests, so a change to customerservice.customer.requests can break customerservice.customer, while a change to customerservice.customer can't break customerservice.customer.requests.
- Position
- Below the diagonal: customerservice.customer uses a module listed above it, which is the healthy direction.
25→7 customerservice.customer uses customerservice.customer.responses✕
- Connections
- 2 pairs of types, where a type in customerservice.customer uses a type in customerservice.customer.responses.
- The types involved
com.company.customerservice.customer.CustomerController→com.company.customerservice.customer.responses.CustomerResponsecom.company.customerservice.customer.CustomerRepository→com.company.customerservice.customer.responses.CustomerResponse
- Direction
- customerservice.customer uses customerservice.customer.responses, so a change to customerservice.customer.responses can break customerservice.customer, while a change to customerservice.customer can't break customerservice.customer.responses.
- Position
- Below the diagonal: customerservice.customer uses a module listed above it, which is the healthy direction.
25→18 customerservice.customer uses starter.clients.auth.dtos✕
- Connections
- 1 pair of types, where a type in customerservice.customer uses a type in starter.clients.auth.dtos.
- The types involved
com.company.customerservice.customer.CustomerMapper→com.company.starter.clients.auth.dtos.SaveUserRequest
- Direction
- customerservice.customer uses starter.clients.auth.dtos, so a change to starter.clients.auth.dtos can break customerservice.customer, while a change to customerservice.customer can't break starter.clients.auth.dtos.
- Position
- Below the diagonal: customerservice.customer uses a module listed above it, which is the healthy direction.
25→20 customerservice.customer uses starter.exception✕
- Connections
- 1 pair of types, where a type in customerservice.customer uses a type in starter.exception.
- The types involved
com.company.customerservice.customer.CustomerError→com.company.starter.exception.ApplicationError
- Direction
- customerservice.customer uses starter.exception, so a change to starter.exception can break customerservice.customer, while a change to customerservice.customer can't break starter.exception.
- Position
- Below the diagonal: customerservice.customer uses a module listed above it, which is the healthy direction.
25→21 customerservice.customer uses starter.mediator✕
- Connections
- 1 pair of types, where a type in customerservice.customer uses a type in starter.mediator.
- The types involved
com.company.customerservice.customer.CustomerController→com.company.starter.mediator.Mediator
- Direction
- customerservice.customer uses starter.mediator, so a change to starter.mediator can break customerservice.customer, while a change to customerservice.customer can't break starter.mediator.
- Position
- Below the diagonal: customerservice.customer uses a module listed above it, which is the healthy direction.
26→9 orderservice.order.responses uses orderservice.order.domains✕
- Connections
- 1 pair of types, where a type in orderservice.order.responses uses a type in orderservice.order.domains.
- The types involved
com.company.orderservice.order.responses.OrderResponse→com.company.orderservice.order.domains.OrderStatus
- Direction
- orderservice.order.responses uses orderservice.order.domains, so a change to orderservice.order.domains can break orderservice.order.responses, while a change to orderservice.order.responses can't break orderservice.order.domains.
- Position
- Below the diagonal: orderservice.order.responses uses a module listed above it, which is the healthy direction.
27→12 paymentservice.payment.responses uses paymentservice.payment.domains✕
- Connections
- 1 pair of types, where a type in paymentservice.payment.responses uses a type in paymentservice.payment.domains.
- The types involved
com.company.paymentservice.payment.responses.PaymentResponse→com.company.paymentservice.payment.domains.PaymentStatus
- Direction
- paymentservice.payment.responses uses paymentservice.payment.domains, so a change to paymentservice.payment.domains can break paymentservice.payment.responses, while a change to paymentservice.payment.responses can't break paymentservice.payment.domains.
- Position
- Below the diagonal: paymentservice.payment.responses uses a module listed above it, which is the healthy direction.
28→15 productservice.product uses productservice.product.domains✕
- Connections
- 1 pair of types, where a type in productservice.product uses a type in productservice.product.domains.
- The types involved
com.company.productservice.product.ProductMapper→com.company.productservice.product.domains.Product
- Direction
- productservice.product uses productservice.product.domains, so a change to productservice.product.domains can break productservice.product, while a change to productservice.product can't break productservice.product.domains.
- Position
- Below the diagonal: productservice.product uses a module listed above it, which is the healthy direction.
28→16 productservice.product uses productservice.product.requests✕
- Connections
- 7 pairs of types, where a type in productservice.product uses a type in productservice.product.requests.
- The types involved
com.company.productservice.product.ProductController→com.company.productservice.product.requests.CreateProductRequestcom.company.productservice.product.ProductController→com.company.productservice.product.requests.ListProductRequestcom.company.productservice.product.ProductController→com.company.productservice.product.requests.UpdateProductRequestcom.company.productservice.product.ProductMapper→com.company.productservice.product.requests.CreateProductRequestcom.company.productservice.product.ProductMapper→com.company.productservice.product.requests.ListProductRequestcom.company.productservice.product.ProductMapper→com.company.productservice.product.requests.UpdateProductRequestcom.company.productservice.product.ProductRepository→com.company.productservice.product.requests.ListProductRequest
- Direction
- productservice.product uses productservice.product.requests, so a change to productservice.product.requests can break productservice.product, while a change to productservice.product can't break productservice.product.requests.
- Position
- Below the diagonal: productservice.product uses a module listed above it, which is the healthy direction.
28→17 productservice.product uses productservice.product.responses✕
- Connections
- 2 pairs of types, where a type in productservice.product uses a type in productservice.product.responses.
- The types involved
com.company.productservice.product.ProductController→com.company.productservice.product.responses.ProductResponsecom.company.productservice.product.ProductRepository→com.company.productservice.product.responses.ProductResponse
- Direction
- productservice.product uses productservice.product.responses, so a change to productservice.product.responses can break productservice.product, while a change to productservice.product can't break productservice.product.responses.
- Position
- Below the diagonal: productservice.product uses a module listed above it, which is the healthy direction.
28→21 productservice.product uses starter.mediator✕
- Connections
- 1 pair of types, where a type in productservice.product uses a type in starter.mediator.
- The types involved
com.company.productservice.product.ProductController→com.company.starter.mediator.Mediator
- Direction
- productservice.product uses starter.mediator, so a change to starter.mediator can break productservice.product, while a change to productservice.product can't break starter.mediator.
- Position
- Below the diagonal: productservice.product uses a module listed above it, which is the healthy direction.
29→18 starter.clients.auth uses starter.clients.auth.dtos✕
- Connections
- 2 pairs of types, where a type in starter.clients.auth uses a type in starter.clients.auth.dtos.
- The types involved
com.company.starter.clients.auth.AuthAmbassador→com.company.starter.clients.auth.dtos.SaveUserRequestcom.company.starter.clients.auth.AuthClient→com.company.starter.clients.auth.dtos.SaveUserRequest
- Direction
- starter.clients.auth uses starter.clients.auth.dtos, so a change to starter.clients.auth.dtos can break starter.clients.auth, while a change to starter.clients.auth can't break starter.clients.auth.dtos.
- Position
- Below the diagonal: starter.clients.auth uses a module listed above it, which is the healthy direction.
30→23 authservice.keycloak uses authservice.user✕
- Connections
- 1 pair of types, where a type in authservice.keycloak uses a type in authservice.user.
- The types involved
com.company.authservice.keycloak.KeycloakService→com.company.authservice.user.SaveUserRequest
- Direction
- authservice.keycloak uses authservice.user, so a change to authservice.user can break authservice.keycloak, while a change to authservice.keycloak can't break authservice.user.
- Position
- Below the diagonal: authservice.keycloak uses a module listed above it, which is the healthy direction.
30→36 authservice.keycloak uses authservice.auth part of a loop✕
- Connections
- 2 pairs of types, where a type in authservice.keycloak uses a type in authservice.auth.
- The types involved
com.company.authservice.keycloak.KeycloakService→com.company.authservice.auth.AuthRequestcom.company.authservice.keycloak.KeycloakService→com.company.authservice.auth.AuthResponse
- Direction
- authservice.keycloak uses authservice.auth, so a change to authservice.auth can break authservice.keycloak, while a change to authservice.keycloak can't break authservice.auth.
- 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.
31→3 configurationservice.configuration.handlers uses configurationservice.configuration.requests✕
- Connections
- 5 pairs of types, where a type in configurationservice.configuration.handlers uses a type in configurationservice.configuration.requests.
- The types involved
com.company.configurationservice.configuration.handlers.CreateConfigurationHandler→com.company.configurationservice.configuration.requests.CreateConfigurationRequestcom.company.configurationservice.configuration.handlers.DeleteConfigurationHandler→com.company.configurationservice.configuration.requests.DeleteConfigurationRequestcom.company.configurationservice.configuration.handlers.GetConfigurationHandler→com.company.configurationservice.configuration.requests.GetConfigurationRequestcom.company.configurationservice.configuration.handlers.UpdateConfigurationHandler→com.company.configurationservice.configuration.requests.UpdateConfigurationRequestcom.company.configurationservice.configuration.handlers.UpdateConfigurationValueHandler→com.company.configurationservice.configuration.requests.UpdateConfigurationValueRequest
- Direction
- configurationservice.configuration.handlers uses configurationservice.configuration.requests, so a change to configurationservice.configuration.requests can break configurationservice.configuration.handlers, while a change to configurationservice.configuration.handlers can't break configurationservice.configuration.requests.
- Position
- Below the diagonal: configurationservice.configuration.handlers uses a module listed above it, which is the healthy direction.
31→19 configurationservice.configuration.handlers uses starter.configuration✕
- Connections
- 3 pairs of types, where a type in configurationservice.configuration.handlers uses a type in starter.configuration.
- The types involved
com.company.configurationservice.configuration.handlers.GetConfigurationHandler→com.company.starter.configuration.Configurationcom.company.configurationservice.configuration.handlers.ListConfigurationHandler→com.company.starter.configuration.Configurationcom.company.configurationservice.configuration.handlers.PublishConfigurationHandler→com.company.starter.configuration.ConfigurationPublisher
- Direction
- configurationservice.configuration.handlers uses starter.configuration, so a change to starter.configuration can break configurationservice.configuration.handlers, while a change to configurationservice.configuration.handlers can't break starter.configuration.
- Position
- Below the diagonal: configurationservice.configuration.handlers uses a module listed above it, which is the healthy direction.
31→21 configurationservice.configuration.handlers uses starter.mediator✕
- Connections
- 7 pairs of types, where a type in configurationservice.configuration.handlers uses a type in starter.mediator.
- The types involved
com.company.configurationservice.configuration.handlers.CreateConfigurationHandler→com.company.starter.mediator.RequestResponseHandlercom.company.configurationservice.configuration.handlers.DeleteConfigurationHandler→com.company.starter.mediator.RequestResponseHandlercom.company.configurationservice.configuration.handlers.GetConfigurationHandler→com.company.starter.mediator.RequestResponseHandlercom.company.configurationservice.configuration.handlers.ListConfigurationHandler→com.company.starter.mediator.ResponseHandlercom.company.configurationservice.configuration.handlers.PublishConfigurationHandler→com.company.starter.mediator.Handlercom.company.configurationservice.configuration.handlers.UpdateConfigurationHandler→com.company.starter.mediator.RequestResponseHandlercom.company.configurationservice.configuration.handlers.UpdateConfigurationValueHandler→com.company.starter.mediator.RequestResponseHandler
- Direction
- configurationservice.configuration.handlers uses starter.mediator, so a change to starter.mediator can break configurationservice.configuration.handlers, while a change to configurationservice.configuration.handlers can't break starter.mediator.
- Position
- Below the diagonal: configurationservice.configuration.handlers uses a module listed above it, which is the healthy direction.
31→24 configurationservice.configuration.handlers uses configurationservice.configuration✕
- Connections
- 10 pairs of types, where a type in configurationservice.configuration.handlers uses a type in configurationservice.configuration.
- The types involved
com.company.configurationservice.configuration.handlers.CreateConfigurationHandler→com.company.configurationservice.configuration.ConfigurationMappercom.company.configurationservice.configuration.handlers.CreateConfigurationHandler→com.company.configurationservice.configuration.ConfigurationRepositorycom.company.configurationservice.configuration.handlers.DeleteConfigurationHandler→com.company.configurationservice.configuration.ConfigurationRepositorycom.company.configurationservice.configuration.handlers.GetConfigurationHandler→com.company.configurationservice.configuration.ConfigurationRepositorycom.company.configurationservice.configuration.handlers.ListConfigurationHandler→com.company.configurationservice.configuration.ConfigurationRepositorycom.company.configurationservice.configuration.handlers.PublishConfigurationHandler→com.company.configurationservice.configuration.ConfigurationRepositorycom.company.configurationservice.configuration.handlers.UpdateConfigurationHandler→com.company.configurationservice.configuration.ConfigurationMappercom.company.configurationservice.configuration.handlers.UpdateConfigurationHandler→com.company.configurationservice.configuration.ConfigurationRepositorycom.company.configurationservice.configuration.handlers.UpdateConfigurationValueHandler→com.company.configurationservice.configuration.Configurationcom.company.configurationservice.configuration.handlers.UpdateConfigurationValueHandler→com.company.configurationservice.configuration.ConfigurationRepository
- Direction
- configurationservice.configuration.handlers uses configurationservice.configuration, so a change to configurationservice.configuration can break configurationservice.configuration.handlers, while a change to configurationservice.configuration.handlers can't break configurationservice.configuration.
- Position
- Below the diagonal: configurationservice.configuration.handlers uses a module listed above it, which is the healthy direction.
32→5 customerservice.customer.handlers uses customerservice.customer.domains✕
- Connections
- 1 pair of types, where a type in customerservice.customer.handlers uses a type in customerservice.customer.domains.
- The types involved
com.company.customerservice.customer.handlers.DeleteCustomerHandler→com.company.customerservice.customer.domains.Customer
- Direction
- customerservice.customer.handlers uses customerservice.customer.domains, so a change to customerservice.customer.domains can break customerservice.customer.handlers, while a change to customerservice.customer.handlers can't break customerservice.customer.domains.
- Position
- Below the diagonal: customerservice.customer.handlers uses a module listed above it, which is the healthy direction.
32→6 customerservice.customer.handlers uses customerservice.customer.requests✕
- Connections
- 6 pairs of types, where a type in customerservice.customer.handlers uses a type in customerservice.customer.requests.
- The types involved
com.company.customerservice.customer.handlers.CreateCustomerHandler→com.company.customerservice.customer.requests.CreateCustomerRequestcom.company.customerservice.customer.handlers.CreateCustomerValidatorHandler→com.company.customerservice.customer.requests.CreateCustomerRequestcom.company.customerservice.customer.handlers.DeleteCustomerHandler→com.company.customerservice.customer.requests.DeleteCustomerRequestcom.company.customerservice.customer.handlers.GetCustomerHandler→com.company.customerservice.customer.requests.GetCustomerRequestcom.company.customerservice.customer.handlers.ListCustomerHandler→com.company.customerservice.customer.requests.ListCustomerRequestcom.company.customerservice.customer.handlers.UpdateCustomerHandler→com.company.customerservice.customer.requests.UpdateCustomerRequest
- Direction
- customerservice.customer.handlers uses customerservice.customer.requests, so a change to customerservice.customer.requests can break customerservice.customer.handlers, while a change to customerservice.customer.handlers can't break customerservice.customer.requests.
- Position
- Below the diagonal: customerservice.customer.handlers uses a module listed above it, which is the healthy direction.
32→7 customerservice.customer.handlers uses customerservice.customer.responses✕
- Connections
- 2 pairs of types, where a type in customerservice.customer.handlers uses a type in customerservice.customer.responses.
- The types involved
com.company.customerservice.customer.handlers.GetCustomerHandler→com.company.customerservice.customer.responses.CustomerResponsecom.company.customerservice.customer.handlers.ListCustomerHandler→com.company.customerservice.customer.responses.CustomerResponse
- Direction
- customerservice.customer.handlers uses customerservice.customer.responses, so a change to customerservice.customer.responses can break customerservice.customer.handlers, while a change to customerservice.customer.handlers can't break customerservice.customer.responses.
- Position
- Below the diagonal: customerservice.customer.handlers uses a module listed above it, which is the healthy direction.
32→21 customerservice.customer.handlers uses starter.mediator✕
- Connections
- 6 pairs of types, where a type in customerservice.customer.handlers uses a type in starter.mediator.
- The types involved
com.company.customerservice.customer.handlers.CreateCustomerHandler→com.company.starter.mediator.RequestResponseHandlercom.company.customerservice.customer.handlers.CreateCustomerValidatorHandler→com.company.starter.mediator.RequestHandlercom.company.customerservice.customer.handlers.DeleteCustomerHandler→com.company.starter.mediator.RequestResponseHandlercom.company.customerservice.customer.handlers.GetCustomerHandler→com.company.starter.mediator.RequestResponseHandlercom.company.customerservice.customer.handlers.ListCustomerHandler→com.company.starter.mediator.RequestResponseHandlercom.company.customerservice.customer.handlers.UpdateCustomerHandler→com.company.starter.mediator.RequestResponseHandler
- Direction
- customerservice.customer.handlers uses starter.mediator, so a change to starter.mediator can break customerservice.customer.handlers, while a change to customerservice.customer.handlers can't break starter.mediator.
- Position
- Below the diagonal: customerservice.customer.handlers uses a module listed above it, which is the healthy direction.
32→25 customerservice.customer.handlers uses customerservice.customer✕
- Connections
- 8 pairs of types, where a type in customerservice.customer.handlers uses a type in customerservice.customer.
- The types involved
com.company.customerservice.customer.handlers.CreateCustomerHandler→com.company.customerservice.customer.CustomerMappercom.company.customerservice.customer.handlers.CreateCustomerHandler→com.company.customerservice.customer.CustomerRepositorycom.company.customerservice.customer.handlers.CreateCustomerValidatorHandler→com.company.customerservice.customer.CustomerRepositorycom.company.customerservice.customer.handlers.DeleteCustomerHandler→com.company.customerservice.customer.CustomerRepositorycom.company.customerservice.customer.handlers.GetCustomerHandler→com.company.customerservice.customer.CustomerRepositorycom.company.customerservice.customer.handlers.ListCustomerHandler→com.company.customerservice.customer.CustomerRepositorycom.company.customerservice.customer.handlers.UpdateCustomerHandler→com.company.customerservice.customer.CustomerMappercom.company.customerservice.customer.handlers.UpdateCustomerHandler→com.company.customerservice.customer.CustomerRepository
- Direction
- customerservice.customer.handlers uses customerservice.customer, so a change to customerservice.customer can break customerservice.customer.handlers, while a change to customerservice.customer.handlers can't break customerservice.customer.
- Position
- Below the diagonal: customerservice.customer.handlers uses a module listed above it, which is the healthy direction.
32→29 customerservice.customer.handlers uses starter.clients.auth✕
- Connections
- 2 pairs of types, where a type in customerservice.customer.handlers uses a type in starter.clients.auth.
- The types involved
com.company.customerservice.customer.handlers.CreateCustomerHandler→com.company.starter.clients.auth.AuthAmbassadorcom.company.customerservice.customer.handlers.DeleteCustomerHandler→com.company.starter.clients.auth.AuthAmbassador
- Direction
- customerservice.customer.handlers uses starter.clients.auth, so a change to starter.clients.auth can break customerservice.customer.handlers, while a change to customerservice.customer.handlers can't break starter.clients.auth.
- Position
- Below the diagonal: customerservice.customer.handlers uses a module listed above it, which is the healthy direction.
33→9 orderservice.order uses orderservice.order.domains✕
- Connections
- 1 pair of types, where a type in orderservice.order uses a type in orderservice.order.domains.
- The types involved
com.company.orderservice.order.OrderMapper→com.company.orderservice.order.domains.Order
- Direction
- orderservice.order uses orderservice.order.domains, so a change to orderservice.order.domains can break orderservice.order, while a change to orderservice.order can't break orderservice.order.domains.
- Position
- Below the diagonal: orderservice.order uses a module listed above it, which is the healthy direction.
33→10 orderservice.order uses orderservice.order.events✕
- Connections
- 1 pair of types, where a type in orderservice.order uses a type in orderservice.order.events.
- The types involved
com.company.orderservice.order.OrderMapper→com.company.orderservice.order.events.OrderCreatedEvent
- Direction
- orderservice.order uses orderservice.order.events, so a change to orderservice.order.events can break orderservice.order, while a change to orderservice.order can't break orderservice.order.events.
- Position
- Below the diagonal: orderservice.order uses a module listed above it, which is the healthy direction.
33→11 orderservice.order uses orderservice.order.requests✕
- Connections
- 5 pairs of types, where a type in orderservice.order uses a type in orderservice.order.requests.
- The types involved
com.company.orderservice.order.OrderController→com.company.orderservice.order.requests.CreateOrderRequestcom.company.orderservice.order.OrderController→com.company.orderservice.order.requests.ListOrderRequestcom.company.orderservice.order.OrderMapper→com.company.orderservice.order.requests.CreateOrderRequestcom.company.orderservice.order.OrderMapper→com.company.orderservice.order.requests.ListOrderRequestcom.company.orderservice.order.OrderRepository→com.company.orderservice.order.requests.ListOrderRequest
- Direction
- orderservice.order uses orderservice.order.requests, so a change to orderservice.order.requests can break orderservice.order, while a change to orderservice.order can't break orderservice.order.requests.
- Position
- Below the diagonal: orderservice.order uses a module listed above it, which is the healthy direction.
33→21 orderservice.order uses starter.mediator✕
- Connections
- 1 pair of types, where a type in orderservice.order uses a type in starter.mediator.
- The types involved
com.company.orderservice.order.OrderController→com.company.starter.mediator.Mediator
- Direction
- orderservice.order uses starter.mediator, so a change to starter.mediator can break orderservice.order, while a change to orderservice.order can't break starter.mediator.
- Position
- Below the diagonal: orderservice.order uses a module listed above it, which is the healthy direction.
33→26 orderservice.order uses orderservice.order.responses✕
- Connections
- 2 pairs of types, where a type in orderservice.order uses a type in orderservice.order.responses.
- The types involved
com.company.orderservice.order.OrderController→com.company.orderservice.order.responses.OrderResponsecom.company.orderservice.order.OrderRepository→com.company.orderservice.order.responses.OrderResponse
- Direction
- orderservice.order uses orderservice.order.responses, so a change to orderservice.order.responses can break orderservice.order, while a change to orderservice.order can't break orderservice.order.responses.
- Position
- Below the diagonal: orderservice.order uses a module listed above it, which is the healthy direction.
34→12 paymentservice.payment uses paymentservice.payment.domains✕
- Connections
- 2 pairs of types, where a type in paymentservice.payment uses a type in paymentservice.payment.domains.
- The types involved
com.company.paymentservice.payment.PaymentMapper→com.company.paymentservice.payment.domains.Ordercom.company.paymentservice.payment.PaymentMapper→com.company.paymentservice.payment.domains.Payment
- Direction
- paymentservice.payment uses paymentservice.payment.domains, so a change to paymentservice.payment.domains can break paymentservice.payment, while a change to paymentservice.payment can't break paymentservice.payment.domains.
- Position
- Below the diagonal: paymentservice.payment uses a module listed above it, which is the healthy direction.
34→13 paymentservice.payment uses paymentservice.payment.events✕
- Connections
- 3 pairs of types, where a type in paymentservice.payment uses a type in paymentservice.payment.events.
- The types involved
com.company.paymentservice.payment.PaymentMapper→com.company.paymentservice.payment.events.OrderCreatedEventcom.company.paymentservice.payment.PaymentMapper→com.company.paymentservice.payment.events.PaymentApprovedEventcom.company.paymentservice.payment.PaymentMapper→com.company.paymentservice.payment.events.PaymentCanceledEvent
- Direction
- paymentservice.payment uses paymentservice.payment.events, so a change to paymentservice.payment.events can break paymentservice.payment, while a change to paymentservice.payment can't break paymentservice.payment.events.
- Position
- Below the diagonal: paymentservice.payment uses a module listed above it, which is the healthy direction.
34→14 paymentservice.payment uses paymentservice.payment.requests✕
- Connections
- 3 pairs of types, where a type in paymentservice.payment uses a type in paymentservice.payment.requests.
- The types involved
com.company.paymentservice.payment.PaymentController→com.company.paymentservice.payment.requests.ListPaymentRequestcom.company.paymentservice.payment.PaymentMapper→com.company.paymentservice.payment.requests.ListPaymentRequestcom.company.paymentservice.payment.PaymentRepository→com.company.paymentservice.payment.requests.ListPaymentRequest
- Direction
- paymentservice.payment uses paymentservice.payment.requests, so a change to paymentservice.payment.requests can break paymentservice.payment, while a change to paymentservice.payment can't break paymentservice.payment.requests.
- Position
- Below the diagonal: paymentservice.payment uses a module listed above it, which is the healthy direction.
34→21 paymentservice.payment uses starter.mediator✕
- Connections
- 1 pair of types, where a type in paymentservice.payment uses a type in starter.mediator.
- The types involved
com.company.paymentservice.payment.PaymentController→com.company.starter.mediator.Mediator
- Direction
- paymentservice.payment uses starter.mediator, so a change to starter.mediator can break paymentservice.payment, while a change to paymentservice.payment can't break starter.mediator.
- Position
- Below the diagonal: paymentservice.payment uses a module listed above it, which is the healthy direction.
34→27 paymentservice.payment uses paymentservice.payment.responses✕
- Connections
- 2 pairs of types, where a type in paymentservice.payment uses a type in paymentservice.payment.responses.
- The types involved
com.company.paymentservice.payment.PaymentController→com.company.paymentservice.payment.responses.PaymentResponsecom.company.paymentservice.payment.PaymentRepository→com.company.paymentservice.payment.responses.PaymentResponse
- Direction
- paymentservice.payment uses paymentservice.payment.responses, so a change to paymentservice.payment.responses can break paymentservice.payment, while a change to paymentservice.payment can't break paymentservice.payment.responses.
- Position
- Below the diagonal: paymentservice.payment uses a module listed above it, which is the healthy direction.
35→16 productservice.product.handlers uses productservice.product.requests✕
- Connections
- 5 pairs of types, where a type in productservice.product.handlers uses a type in productservice.product.requests.
- The types involved
com.company.productservice.product.handlers.CreateProductHandler→com.company.productservice.product.requests.CreateProductRequestcom.company.productservice.product.handlers.DeleteProductHandler→com.company.productservice.product.requests.DeleteProductRequestcom.company.productservice.product.handlers.GetProductHandler→com.company.productservice.product.requests.GetProductRequestcom.company.productservice.product.handlers.ListProductHandler→com.company.productservice.product.requests.ListProductRequestcom.company.productservice.product.handlers.UpdateProductHandler→com.company.productservice.product.requests.UpdateProductRequest
- Direction
- productservice.product.handlers uses productservice.product.requests, so a change to productservice.product.requests can break productservice.product.handlers, while a change to productservice.product.handlers can't break productservice.product.requests.
- Position
- Below the diagonal: productservice.product.handlers uses a module listed above it, which is the healthy direction.
35→17 productservice.product.handlers uses productservice.product.responses✕
- Connections
- 2 pairs of types, where a type in productservice.product.handlers uses a type in productservice.product.responses.
- The types involved
com.company.productservice.product.handlers.GetProductHandler→com.company.productservice.product.responses.ProductResponsecom.company.productservice.product.handlers.ListProductHandler→com.company.productservice.product.responses.ProductResponse
- Direction
- productservice.product.handlers uses productservice.product.responses, so a change to productservice.product.responses can break productservice.product.handlers, while a change to productservice.product.handlers can't break productservice.product.responses.
- Position
- Below the diagonal: productservice.product.handlers uses a module listed above it, which is the healthy direction.
35→21 productservice.product.handlers uses starter.mediator✕
- Connections
- 5 pairs of types, where a type in productservice.product.handlers uses a type in starter.mediator.
- The types involved
com.company.productservice.product.handlers.CreateProductHandler→com.company.starter.mediator.RequestResponseHandlercom.company.productservice.product.handlers.DeleteProductHandler→com.company.starter.mediator.RequestResponseHandlercom.company.productservice.product.handlers.GetProductHandler→com.company.starter.mediator.RequestResponseHandlercom.company.productservice.product.handlers.ListProductHandler→com.company.starter.mediator.RequestResponseHandlercom.company.productservice.product.handlers.UpdateProductHandler→com.company.starter.mediator.RequestResponseHandler
- Direction
- productservice.product.handlers uses starter.mediator, so a change to starter.mediator can break productservice.product.handlers, while a change to productservice.product.handlers can't break starter.mediator.
- Position
- Below the diagonal: productservice.product.handlers uses a module listed above it, which is the healthy direction.
35→28 productservice.product.handlers uses productservice.product✕
- Connections
- 7 pairs of types, where a type in productservice.product.handlers uses a type in productservice.product.
- The types involved
com.company.productservice.product.handlers.CreateProductHandler→com.company.productservice.product.ProductMappercom.company.productservice.product.handlers.CreateProductHandler→com.company.productservice.product.ProductRepositorycom.company.productservice.product.handlers.DeleteProductHandler→com.company.productservice.product.ProductRepositorycom.company.productservice.product.handlers.GetProductHandler→com.company.productservice.product.ProductRepositorycom.company.productservice.product.handlers.ListProductHandler→com.company.productservice.product.ProductRepositorycom.company.productservice.product.handlers.UpdateProductHandler→com.company.productservice.product.ProductMappercom.company.productservice.product.handlers.UpdateProductHandler→com.company.productservice.product.ProductRepository
- Direction
- productservice.product.handlers uses productservice.product, so a change to productservice.product can break productservice.product.handlers, while a change to productservice.product.handlers can't break productservice.product.
- Position
- Below the diagonal: productservice.product.handlers uses a module listed above it, which is the healthy direction.
36→20 authservice.auth uses starter.exception✕
- Connections
- 1 pair of types, where a type in authservice.auth uses a type in starter.exception.
- The types involved
com.company.authservice.auth.AuthError→com.company.starter.exception.ApplicationError
- Direction
- authservice.auth uses starter.exception, so a change to starter.exception can break authservice.auth, while a change to authservice.auth can't break starter.exception.
- Position
- Below the diagonal: authservice.auth uses a module listed above it, which is the healthy direction.
36→30 authservice.auth uses authservice.keycloak✕
- Connections
- 1 pair of types, where a type in authservice.auth uses a type in authservice.keycloak.
- The types involved
com.company.authservice.auth.AuthController→com.company.authservice.keycloak.KeycloakService
- Direction
- authservice.auth uses authservice.keycloak, so a change to authservice.keycloak can break authservice.auth, while a change to authservice.auth can't break authservice.keycloak.
- Position
- Below the diagonal: authservice.auth uses a module listed above it, which is the healthy direction.
37→9 orderservice.order.handlers uses orderservice.order.domains✕
- Connections
- 2 pairs of types, where a type in orderservice.order.handlers uses a type in orderservice.order.domains.
- The types involved
com.company.orderservice.order.handlers.PaymentApprovedEventHandler→com.company.orderservice.order.domains.Ordercom.company.orderservice.order.handlers.PaymentCanceledEventHandler→com.company.orderservice.order.domains.Order
- Direction
- orderservice.order.handlers uses orderservice.order.domains, so a change to orderservice.order.domains can break orderservice.order.handlers, while a change to orderservice.order.handlers can't break orderservice.order.domains.
- Position
- Below the diagonal: orderservice.order.handlers uses a module listed above it, which is the healthy direction.
37→10 orderservice.order.handlers uses orderservice.order.events✕
- Connections
- 2 pairs of types, where a type in orderservice.order.handlers uses a type in orderservice.order.events.
- The types involved
com.company.orderservice.order.handlers.PaymentApprovedEventHandler→com.company.orderservice.order.events.PaymentApprovedEventcom.company.orderservice.order.handlers.PaymentCanceledEventHandler→com.company.orderservice.order.events.PaymentCanceledEvent
- Direction
- orderservice.order.handlers uses orderservice.order.events, so a change to orderservice.order.events can break orderservice.order.handlers, while a change to orderservice.order.handlers can't break orderservice.order.events.
- Position
- Below the diagonal: orderservice.order.handlers uses a module listed above it, which is the healthy direction.
37→11 orderservice.order.handlers uses orderservice.order.requests✕
- Connections
- 3 pairs of types, where a type in orderservice.order.handlers uses a type in orderservice.order.requests.
- The types involved
com.company.orderservice.order.handlers.CreateOrderHandler→com.company.orderservice.order.requests.CreateOrderRequestcom.company.orderservice.order.handlers.GetOrderHandler→com.company.orderservice.order.requests.GetOrderRequestcom.company.orderservice.order.handlers.ListOrderHandler→com.company.orderservice.order.requests.ListOrderRequest
- Direction
- orderservice.order.handlers uses orderservice.order.requests, so a change to orderservice.order.requests can break orderservice.order.handlers, while a change to orderservice.order.handlers can't break orderservice.order.requests.
- Position
- Below the diagonal: orderservice.order.handlers uses a module listed above it, which is the healthy direction.
37→21 orderservice.order.handlers uses starter.mediator✕
- Connections
- 5 pairs of types, where a type in orderservice.order.handlers uses a type in starter.mediator.
- The types involved
com.company.orderservice.order.handlers.CreateOrderHandler→com.company.starter.mediator.RequestResponseHandlercom.company.orderservice.order.handlers.GetOrderHandler→com.company.starter.mediator.RequestResponseHandlercom.company.orderservice.order.handlers.ListOrderHandler→com.company.starter.mediator.RequestResponseHandlercom.company.orderservice.order.handlers.PaymentApprovedEventHandler→com.company.starter.mediator.RequestHandlercom.company.orderservice.order.handlers.PaymentCanceledEventHandler→com.company.starter.mediator.RequestHandler
- Direction
- orderservice.order.handlers uses starter.mediator, so a change to starter.mediator can break orderservice.order.handlers, while a change to orderservice.order.handlers can't break starter.mediator.
- Position
- Below the diagonal: orderservice.order.handlers uses a module listed above it, which is the healthy direction.
37→22 orderservice.order.handlers uses starter.outbox✕
- Connections
- 1 pair of types, where a type in orderservice.order.handlers uses a type in starter.outbox.
- The types involved
com.company.orderservice.order.handlers.CreateOrderHandler→com.company.starter.outbox.OutboxService
- Direction
- orderservice.order.handlers uses starter.outbox, so a change to starter.outbox can break orderservice.order.handlers, while a change to orderservice.order.handlers can't break starter.outbox.
- Position
- Below the diagonal: orderservice.order.handlers uses a module listed above it, which is the healthy direction.
37→26 orderservice.order.handlers uses orderservice.order.responses✕
- Connections
- 2 pairs of types, where a type in orderservice.order.handlers uses a type in orderservice.order.responses.
- The types involved
com.company.orderservice.order.handlers.GetOrderHandler→com.company.orderservice.order.responses.OrderResponsecom.company.orderservice.order.handlers.ListOrderHandler→com.company.orderservice.order.responses.OrderResponse
- Direction
- orderservice.order.handlers uses orderservice.order.responses, so a change to orderservice.order.responses can break orderservice.order.handlers, while a change to orderservice.order.handlers can't break orderservice.order.responses.
- Position
- Below the diagonal: orderservice.order.handlers uses a module listed above it, which is the healthy direction.
37→33 orderservice.order.handlers uses orderservice.order✕
- Connections
- 6 pairs of types, where a type in orderservice.order.handlers uses a type in orderservice.order.
- The types involved
com.company.orderservice.order.handlers.CreateOrderHandler→com.company.orderservice.order.OrderMappercom.company.orderservice.order.handlers.CreateOrderHandler→com.company.orderservice.order.OrderRepositorycom.company.orderservice.order.handlers.GetOrderHandler→com.company.orderservice.order.OrderRepositorycom.company.orderservice.order.handlers.ListOrderHandler→com.company.orderservice.order.OrderRepositorycom.company.orderservice.order.handlers.PaymentApprovedEventHandler→com.company.orderservice.order.OrderRepositorycom.company.orderservice.order.handlers.PaymentCanceledEventHandler→com.company.orderservice.order.OrderRepository
- Direction
- orderservice.order.handlers uses orderservice.order, so a change to orderservice.order can break orderservice.order.handlers, while a change to orderservice.order.handlers can't break orderservice.order.
- Position
- Below the diagonal: orderservice.order.handlers uses a module listed above it, which is the healthy direction.
38→12 paymentservice.payment.handlers uses paymentservice.payment.domains✕
- Connections
- 2 pairs of types, where a type in paymentservice.payment.handlers uses a type in paymentservice.payment.domains.
- The types involved
com.company.paymentservice.payment.handlers.ApprovePaymentHandler→com.company.paymentservice.payment.domains.Paymentcom.company.paymentservice.payment.handlers.CancelPaymentHandler→com.company.paymentservice.payment.domains.Payment
- Direction
- paymentservice.payment.handlers uses paymentservice.payment.domains, so a change to paymentservice.payment.domains can break paymentservice.payment.handlers, while a change to paymentservice.payment.handlers can't break paymentservice.payment.domains.
- Position
- Below the diagonal: paymentservice.payment.handlers uses a module listed above it, which is the healthy direction.
38→13 paymentservice.payment.handlers uses paymentservice.payment.events✕
- Connections
- 1 pair of types, where a type in paymentservice.payment.handlers uses a type in paymentservice.payment.events.
- The types involved
com.company.paymentservice.payment.handlers.OrderCreatedEventHandler→com.company.paymentservice.payment.events.OrderCreatedEvent
- Direction
- paymentservice.payment.handlers uses paymentservice.payment.events, so a change to paymentservice.payment.events can break paymentservice.payment.handlers, while a change to paymentservice.payment.handlers can't break paymentservice.payment.events.
- Position
- Below the diagonal: paymentservice.payment.handlers uses a module listed above it, which is the healthy direction.
38→14 paymentservice.payment.handlers uses paymentservice.payment.requests✕
- Connections
- 5 pairs of types, where a type in paymentservice.payment.handlers uses a type in paymentservice.payment.requests.
- The types involved
com.company.paymentservice.payment.handlers.ApprovePaymentHandler→com.company.paymentservice.payment.requests.ApprovePaymentRequestcom.company.paymentservice.payment.handlers.CancelPaymentHandler→com.company.paymentservice.payment.requests.CancelPaymentRequestcom.company.paymentservice.payment.handlers.GetPaymentByOrderIdHandler→com.company.paymentservice.payment.requests.GetPaymentByOrderIdRequestcom.company.paymentservice.payment.handlers.GetPaymentHandler→com.company.paymentservice.payment.requests.GetPaymentRequestcom.company.paymentservice.payment.handlers.ListPaymentHandler→com.company.paymentservice.payment.requests.ListPaymentRequest
- Direction
- paymentservice.payment.handlers uses paymentservice.payment.requests, so a change to paymentservice.payment.requests can break paymentservice.payment.handlers, while a change to paymentservice.payment.handlers can't break paymentservice.payment.requests.
- Position
- Below the diagonal: paymentservice.payment.handlers uses a module listed above it, which is the healthy direction.
38→21 paymentservice.payment.handlers uses starter.mediator✕
- Connections
- 6 pairs of types, where a type in paymentservice.payment.handlers uses a type in starter.mediator.
- The types involved
com.company.paymentservice.payment.handlers.ApprovePaymentHandler→com.company.starter.mediator.RequestResponseHandlercom.company.paymentservice.payment.handlers.CancelPaymentHandler→com.company.starter.mediator.RequestResponseHandlercom.company.paymentservice.payment.handlers.GetPaymentByOrderIdHandler→com.company.starter.mediator.RequestResponseHandlercom.company.paymentservice.payment.handlers.GetPaymentHandler→com.company.starter.mediator.RequestResponseHandlercom.company.paymentservice.payment.handlers.ListPaymentHandler→com.company.starter.mediator.RequestResponseHandlercom.company.paymentservice.payment.handlers.OrderCreatedEventHandler→com.company.starter.mediator.RequestHandler
- Direction
- paymentservice.payment.handlers uses starter.mediator, so a change to starter.mediator can break paymentservice.payment.handlers, while a change to paymentservice.payment.handlers can't break starter.mediator.
- Position
- Below the diagonal: paymentservice.payment.handlers uses a module listed above it, which is the healthy direction.
38→22 paymentservice.payment.handlers uses starter.outbox✕
- Connections
- 2 pairs of types, where a type in paymentservice.payment.handlers uses a type in starter.outbox.
- The types involved
com.company.paymentservice.payment.handlers.ApprovePaymentHandler→com.company.starter.outbox.OutboxServicecom.company.paymentservice.payment.handlers.CancelPaymentHandler→com.company.starter.outbox.OutboxService
- Direction
- paymentservice.payment.handlers uses starter.outbox, so a change to starter.outbox can break paymentservice.payment.handlers, while a change to paymentservice.payment.handlers can't break starter.outbox.
- Position
- Below the diagonal: paymentservice.payment.handlers uses a module listed above it, which is the healthy direction.
38→27 paymentservice.payment.handlers uses paymentservice.payment.responses✕
- Connections
- 3 pairs of types, where a type in paymentservice.payment.handlers uses a type in paymentservice.payment.responses.
- The types involved
com.company.paymentservice.payment.handlers.GetPaymentByOrderIdHandler→com.company.paymentservice.payment.responses.PaymentResponsecom.company.paymentservice.payment.handlers.GetPaymentHandler→com.company.paymentservice.payment.responses.PaymentResponsecom.company.paymentservice.payment.handlers.ListPaymentHandler→com.company.paymentservice.payment.responses.PaymentResponse
- Direction
- paymentservice.payment.handlers uses paymentservice.payment.responses, so a change to paymentservice.payment.responses can break paymentservice.payment.handlers, while a change to paymentservice.payment.handlers can't break paymentservice.payment.responses.
- Position
- Below the diagonal: paymentservice.payment.handlers uses a module listed above it, which is the healthy direction.
38→34 paymentservice.payment.handlers uses paymentservice.payment✕
- Connections
- 9 pairs of types, where a type in paymentservice.payment.handlers uses a type in paymentservice.payment.
- The types involved
com.company.paymentservice.payment.handlers.ApprovePaymentHandler→com.company.paymentservice.payment.PaymentMappercom.company.paymentservice.payment.handlers.ApprovePaymentHandler→com.company.paymentservice.payment.PaymentRepositorycom.company.paymentservice.payment.handlers.CancelPaymentHandler→com.company.paymentservice.payment.PaymentMappercom.company.paymentservice.payment.handlers.CancelPaymentHandler→com.company.paymentservice.payment.PaymentRepositorycom.company.paymentservice.payment.handlers.GetPaymentByOrderIdHandler→com.company.paymentservice.payment.PaymentRepositorycom.company.paymentservice.payment.handlers.GetPaymentHandler→com.company.paymentservice.payment.PaymentRepositorycom.company.paymentservice.payment.handlers.ListPaymentHandler→com.company.paymentservice.payment.PaymentRepositorycom.company.paymentservice.payment.handlers.OrderCreatedEventHandler→com.company.paymentservice.payment.PaymentMappercom.company.paymentservice.payment.handlers.OrderCreatedEventHandler→com.company.paymentservice.payment.PaymentRepository
- Direction
- paymentservice.payment.handlers uses paymentservice.payment, so a change to paymentservice.payment can break paymentservice.payment.handlers, while a change to paymentservice.payment.handlers can't break paymentservice.payment.
- Position
- Below the diagonal: paymentservice.payment.handlers uses a module listed above it, which is the healthy direction.
39→10 orderservice.order.listeners uses orderservice.order.events✕
- Connections
- 2 pairs of types, where a type in orderservice.order.listeners uses a type in orderservice.order.events.
- The types involved
com.company.orderservice.order.listeners.PaymentApprovedEventListener→com.company.orderservice.order.events.PaymentApprovedEventcom.company.orderservice.order.listeners.PaymentCanceledEventListener→com.company.orderservice.order.events.PaymentCanceledEvent
- Direction
- orderservice.order.listeners uses orderservice.order.events, so a change to orderservice.order.events can break orderservice.order.listeners, while a change to orderservice.order.listeners can't break orderservice.order.events.
- Position
- Below the diagonal: orderservice.order.listeners uses a module listed above it, which is the healthy direction.
39→37 orderservice.order.listeners uses orderservice.order.handlers✕
- Connections
- 2 pairs of types, where a type in orderservice.order.listeners uses a type in orderservice.order.handlers.
- The types involved
com.company.orderservice.order.listeners.PaymentApprovedEventListener→com.company.orderservice.order.handlers.PaymentApprovedEventHandlercom.company.orderservice.order.listeners.PaymentCanceledEventListener→com.company.orderservice.order.handlers.PaymentCanceledEventHandler
- Direction
- orderservice.order.listeners uses orderservice.order.handlers, so a change to orderservice.order.handlers can break orderservice.order.listeners, while a change to orderservice.order.listeners can't break orderservice.order.handlers.
- Position
- Below the diagonal: orderservice.order.listeners uses a module listed above it, which is the healthy direction.
40→13 paymentservice.payment.listeners uses paymentservice.payment.events✕
- Connections
- 1 pair of types, where a type in paymentservice.payment.listeners uses a type in paymentservice.payment.events.
- The types involved
com.company.paymentservice.payment.listeners.OrderCreatedEventListener→com.company.paymentservice.payment.events.OrderCreatedEvent
- Direction
- paymentservice.payment.listeners uses paymentservice.payment.events, so a change to paymentservice.payment.events can break paymentservice.payment.listeners, while a change to paymentservice.payment.listeners can't break paymentservice.payment.events.
- Position
- Below the diagonal: paymentservice.payment.listeners uses a module listed above it, which is the healthy direction.
40→38 paymentservice.payment.listeners uses paymentservice.payment.handlers✕
- Connections
- 1 pair of types, where a type in paymentservice.payment.listeners uses a type in paymentservice.payment.handlers.
- The types involved
com.company.paymentservice.payment.listeners.OrderCreatedEventListener→com.company.paymentservice.payment.handlers.OrderCreatedEventHandler
- Direction
- paymentservice.payment.listeners uses paymentservice.payment.handlers, so a change to paymentservice.payment.handlers can break paymentservice.payment.listeners, while a change to paymentservice.payment.listeners can't break paymentservice.payment.handlers.
- Position
- Below the diagonal: paymentservice.payment.listeners uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A02:2025 — Security Misconfiguration | 15 | High / Critical |
| A05:2025 — Injection | 6 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 2 | High / Critical |
Roadmap
Top priorities: Extend structured logging to the remaining runnable modules so everything you run is diagnosable in production; Resolve the 1 No ADRs found finding(s) in ADR Quality; Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 1 No ADRs found finding(s) in ADR Quality. | +4.3 pts | Low | ADR Quality |
| Extend structured logging to the remaining runnable modules so everything you run is diagnosable in production. | +4.4 pts | Medium | Observability |
| Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them. | +3.4 pts | Medium | Architecture documentation |
| Declare the default where Java declares it: `@NullMarked` (org.jspecify.annotations) in each package's `package-info.java`, or once in `module-info.java`, and run NullAway (Error Prone) or the Checker Framework so the declaration is enforced. Then annotate the real exceptions `@Nullable` and resolve the suppressions rather than adding to them: a `@SuppressWarnings("NullAway")` or `castToNonNull(x)` on a value the checker could show to be null is a `NullPointerException` waiting for the path that makes it true — where the value genuinely cannot be null, say something the checker can see instead (a null check, `Objects.requireNonNull`, a non-null field initialised in the constructor). | +2.7 pts | Medium | Nullable reference types |
| Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite. | +2.0 pts | Medium | Documentation (README) |
| Document RTO/RPO and a tested restore procedure (a backup config alone isn't disaster recovery). | +1.7 pts | Medium | DR & Backup |
| Resolve the 5 No assertions finding(s) in Test Quality — start with OrderIntegrationTest.java (2), MediatorTest.java (2), PaymentIntegrationTest.java. | +0.8 pts | Low | Test Quality |
| Add an approval/environment gate (required reviewers / protection rules) before production promotion. | +0.9 pts | Medium | Deployment & Rollback |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 0.5 | Slop | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 2.4 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.8 | Mixed | Dependency Vulnerabilities: High CVE: REDACTED |
| REDACTED | 6.9 | Mixed | IaC & Container Security: Medium IaC: REDACTED |
| orderservice/src/test/java/com/company/orderservice/order/OrderIntegrationTest.java | 7.8 | Mixed | Test Quality: No assertions: shouldCancelOrderWhenPaymentEventIsCanceled |
| starter/src/test/java/com/company/starter/mediator/MediatorTest.java | 7.8 | Mixed | Test Quality: No assertions: shouldExecuteHandlerWhenHandlerIsDispatched |
| paymentservice/src/test/java/com/company/paymentservice/payment/PaymentIntegrationTest.java | 8.5 | Near-clean | Test Quality: No assertions: shouldCreatePaymentWhenOrderCreatedEventIsSent |
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 57 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.8, the weighted average across measured dimensions.
What we checked — 57 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, 29 of 36 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Canine Code Analyzer duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy · checkov | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 · 3.2.533 | ✓ deterministic |
Run transparency — what happened this run
- D8 Code Coverage — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: test source is present (.java) but the built-in coverage collector has no runner for this repository's ecosystem — so this suite was never executed by it. Not scored — this is a gap in the analyzer's language coverage, not a defect in the repo. To have real coverage read, produce a coverage report in a standard format (JaCoCo XML — `mvn jacoco:report` or the Gradle `jacocoTestReport` task) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures. You can widen what we reach: optional: produce a coverage report in a standard format (JaCoCo XML — `mvn jacoco:report` or the Gradle `jacocoTestReport` task) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures — then the real number is read on the next scan.
- D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test source is present (.java) and this repository declares a JVM test suite (7 builds), but it was not re-run: no test result was produced. Not scored — this is a gap in the analyzer's language coverage, not a finding about this repository.
- D12 Dependency Hygiene — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Not scored — 8 Maven/Gradle manifest(s) were read, stating a version for 8 dependency(ies) and leaving 20 to a parent or an imported BOM, but no build resolved the dependency graph, so the outdated signal was not established. NOT a finding that these dependencies are current or healthy.
- D15 Churn × Complexity Hotspots — 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-commit history — no usable git history window to measure hotspots: a single-commit clone exposes no history window, so the churn × complexity hotspot signal is unavailable — not scored for this run.
- 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 1 commit(s) sampled, automation and bot accounts excluded). Concentration needs a team to concentrate: with one contributor there is nobody to spread the knowledge to, so there is nothing here for the owner to act on.
- D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
- 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: no published-package marker D22 reads admitted any project here. D22 DOES collect the public API of every language in this tree, and admits a project only when its manifest makes that ecosystem's publication act in a form the marker recognises — so what is missing is not a collector but an admission rule for the publication act this repository makes, if it makes one. The remedy is a better discriminator for that marker — not a collector, and no change to the scan image can close it. The marker's rules are measured to refuse applications, so one refused repository is the rule working as calibrated; several are the evidence that it is too strict.
- D24 Comment Value — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
- D32 Data Compliance (PII/GDPR) — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `starter/src/main/java/com/company/starter/exception/GlobalExceptionHandler.java` produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
- D34 Knowledge Freshness — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Too few commits to judge knowledge freshness (1 commit(s) sampled).
- D35 Change Coupling — measured, with a gap in what it reached — 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. Git history depth insufficient — this repository has 1 commit(s), too few for a reliable change-coupling signal. The clone is complete, so there is no deeper history to fetch: the signal returns as the project accumulates history.
- AXR1 Runtime accessibility — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via DockerCompose (REDACTED). compose up failed (exit 1 — a container did not start, exited, or never became healthy) — container redis-admin is unhealthy; runtime evidence skipped.
- C1 Data Protection — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These personal data controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks personal data controls.
- C2 Access Controls — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These authorization controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks authorization controls.
- C3 Audit Trail — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These audit controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks audit controls.
- C4 Data Retention — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These retention controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks retention controls.
- C5 Data-Subject Rights — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These data-subject rights controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks data-subject rights controls.
- ED5 Idempotency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check decides whether a handler's mutation is safe to re-run by recognising its persistence writes (a database save, a repository write, an event publish) and its guards. Those markers are .NET member names, so in this repository's language a write such as `repository.save(order)` is not recognised and a same-named call on an unrelated library type could be. The handlers were found; their idempotency was neither confirmed nor ruled out.
- GD1 Unfinished & placeholder code — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, F#, JavaScript/TypeScript, Dart, Ruby and Scala source only, and no C#, F#, JavaScript/TypeScript, Dart, Ruby or Scala was found, and this repository's Java is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- P1 CI/CD gates — 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. A CI pipeline exists and the word "test" appears, but no explicit test-runner invocation (your stack's test command, or a test job) was matched — so either the gate runs tests through a step this pass could not recognise, or "test" is incidental here (a path, "latest", a reporter). Which of the two it is cannot be settled from this dimension's evidence; the coverage dimensions report whether a suite exists at all. You can widen what we reach: name the test runner explicitly in the pipeline step (your stack's test command, or a job named for the suite) so the gate is unambiguous to a reader and to this pass.
- S1 Web-Security Posture — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These web-security controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks web-security controls.
- X1 Async correctness — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Python, Dart, Ruby, Scala, Rust and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala, Rust or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X12 Unreachable branch — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Python, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X13 Undrained process stream — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Python, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X17 Uncapped recursion over a caller-supplied document — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Python, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
- D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
- D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
- D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
- D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
- D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
- 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.
- 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".
- P5 DR & Backup: Backup/restore and disaster-recovery readiness is judged from in-repo evidence — a config that exists is not a tested restore, so the absence of positive evidence is reported as "not evidenced", never scored as present.
Dimensions
D1 · Cyclomatic Complexity
0 method(s) exceeded the cyclomatic complexity threshold of 15.
D2 · Cognitive Complexity
0 method(s) exceeded the cognitive complexity threshold of 15.
D3 · God Classes
0 god class(es) detected.
D4 · Code Duplication
0 duplicated block group(s) detected.
D5 · Coupling
7 production modules (Maven), 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 11 classes have LCOM4 above 3.
D9 · Test Distribution
218 test methods: 218 unit, 0 integration, 0 BDD, 0 e2e.
D10 · Test Quality
0 skipped, 5 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 218 tests.
What to do
- Resolve the 5 No assertions finding(s) in Test Quality — start with OrderIntegrationTest.java (2), MediatorTest.java (2), PaymentIntegrationTest.java. — One of this dimension's main actionable groups (5 warning-level).
- Enforce Test Quality in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D14 · License Compliance
0 of 2 declared JVM dependency artifact(s) use a banned license. Licences were resolved from the POMs Maven Central publishes, over the coordinates this repository's 8 Maven/Gradle manifest(s) declare with a version resolvable from the manifest itself — the same declaration-site closure this analysis reads for dependency currency. The JVM has no lockfile a checkout is guaranteed to carry, so this is deliberately NOT the transitive closure. 20 further coordinate(s) are declared with no version at the declaration site — inherited from a parent POM, a BOM or an unresolved Gradle version reference — and are NOT graded: this verdict covers what the checkout pins, not the full transitive graph. A further 1 coordinate(s) are not published to Maven Central — another repository (Google's Maven hosts androidx), a SNAPSHOT, or a private artifact — so their licences are not readable from here and they are outside this verdict.
D17 · Explicit Debt
0 deducted task-comment markers across 3054 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. 1 document(s) read across 1 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).
D26 · Project Cohesion
0 of 7 build units (Maven) flagged as possibly oversized/incoherent.
D27 · Navigability
63 % of calls cross a namespace and 30 % go through an interface, but 100 % of collaborators are co-located — so following a call takes several hops. Baseline: small — navigation cost is tolerated.
What to do
- Resolve the 1 High interface indirection finding(s) in Navigability. — One of this dimension's main actionable groups (1 recommendation-level).
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
6 finding(s): 0 critical, 6 high, 0 medium, 0 low. 6 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) — `starter/src/main/java/com/company/starter/exception/GlobalExceptionHandler.java` (line 38, line 39, line 40) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them.
What to do
- No action in Static Analysis (SAST) — all 6 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 (6 issue-level, 0 of them charged here).
D30 · Dependency Vulnerabilities
2 finding(s): 0 critical, 2 high, 0 medium, 0 low.
What to do
- Resolve the 2 High 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
15 finding(s): 0 critical, 9 high, 6 medium, 0 low.
What to do
- Resolve the 9 High IaC finding(s) in IaC & Container Security — start with REDACTED (9). — One of this dimension's main actionable groups (9 issue-level).
- Resolve the 6 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (4), REDACTED (2). — One of this dimension's main actionable groups (6 warning-level).
D35 · Change Coupling
No strong hidden change-coupling between production files.
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 1 platform declaration(s) and 16 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
Frontend & cross-cutting dimensions
AX1 · Captive dependencies
AX10 · Code composition
What to do
- The domain core is a small share of production code, but most of the rest matched no layer vocabulary at all — so this is not yet an anemic-domain finding. The namespace/path convention could not place that code, which makes the composition above a statement about the naming, not about the design. Name the layers (or check that the repository's conventions differ from the ones this check knows) before reading a thin domain into it.
AX2 · Stateful singletons
AX3 · Project dependency cycles
AX5 · Architecture & structure
AX6 · Interface segregation
AX9 · CQS / query purity
IC1 · Incompleteness & stubs
M1 · Documentation (README)
What to do
- Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
- Add a README to the 8 of 8 project(s) that lack one — worth up to 2 pts.
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
M3 · Folder & project structure
P1 · CI/CD gates
What to do
- Run the test suite in CI via an explicit runner step (`mvn test` for the toolchain this pipeline already uses) and gate merges on it.
P2 · Observability
- Only 1/7 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `authservice`, `configurationservice`, `customerservice`, `orderservice`, `paymentservice` and 1 more.
What to do
- Extend structured logging to the remaining runnable modules so everything you run is diagnosable in production.
- Consider OpenTelemetry tracing/metrics (opentelemetry-java or Micrometer) and a health-check endpoint (Spring Boot Actuator's /actuator/health, or a /health route) for operability.
P3 · Security & performance tooling
- No static application security testing detected. For this repository's stack, add spotbugs with find-sec-bugs (or `semgrep --config=auto`, which runs on any language) as a CI step. What was searched, so you can tell an absence from a miss: the 2117 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.
What to do
- Add a SAST step to CI running what this repository's stack ships: spotbugs with find-sec-bugs — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing.
- Enable Dependabot/Renovate or a dependency-review gate.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
What to do
- Add an approval/environment gate (required reviewers / protection rules) before production promotion.
P5 · DR & Backup
What to do
- Document RTO/RPO and a tested restore procedure (a backup config alone isn't disaster recovery).
X14 · Bypassable address classification
X15 · Unvalidated length from an untrusted reader
X16 · Unfloored truncation loop
X18 · Disposal-pattern correctness
X19 · Unrestored process-global state
X20 · Mistyped argument guard
X21 · Side-effecting pattern guard
X22 · Contradicted release guard
X23 · Unguarded diagnostic materialisation
X24 · Document value interpolated into markup unescaped
X25 · Inert configuration knob
X26 · Unsynchronised callback handoff
X27 · Collection changed while being enumerated
X28 · Index access outside its own emptiness guard
X29 · Per-element action decided by a fixed element
X3 · Exception handling
X30 · Support guard that admits what it rejects
X4 · Structured logging
X5 · Nullable reference types
- 0/51 of this repository's Java package directories are under a non-null default: a `package-info.java` declaring `@NullMarked` (JSpecify) or `@NonNullApi`, `@ParametersAreNonnullByDefault`, `@NonNullByDefault`, `@DefaultQualifier(NonNull.class)`; a `module-info.java` declaring `@NullMarked`; every type in it `@NullMarked`; or a build that runs NullAway with the package in `AnnotatedPackages`, or the Checker Framework's `NullnessChecker`. Elsewhere every reference admits null and no checker warns on the dereference that throws a `NullPointerException`.
What to do
- Declare the default where Java declares it: `@NullMarked` (org.jspecify.annotations) in each package's `package-info.java`, or once in `module-info.java`, and run NullAway (Error Prone) or the Checker Framework so the declaration is enforced. Then annotate the real exceptions `@Nullable` and resolve the suppressions rather than adding to them: a `@SuppressWarnings("NullAway")` or `castToNonNull(x)` on a value the checker could show to be null is a `NullPointerException` waiting for the path that makes it true — where the value genuinely cannot be null, say something the checker can see instead (a null check, `Objects.requireNonNull`, a non-null field initialised in the constructor).
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 76% | Adequate — gated by X5 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 95% | Exemplary | Strongest area. |
| Maturity | 70% | Adequate | Acceptable, with room to improve. |
| Readiness | 50% | Adequate — gated by P3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 91% | Checked 5 of 11 | Solid. |
Unscored — 1 check(s) recorded observations but carry no score
- D36 Supply-chain Provenance & Signing — 1 observation(s) recorded · The CI pipeline builds and tests but publishes no released artifact — no package publish, container push, GitHub release or deployment step. Supply-chain provenance, signing and SBOM attest RELEASED artifacts, so there is nothing to attest here. Add them to the release pipeline when this repo starts shipping artifacts (a published package, a container image, a deployed service or a tagged release). Build integrity and workflow-token hygiene are reported below: they describe what the CI runs and the token it runs with, neither of which is affected by whether the pipeline ships an artifact.
Not evidenced — 4 control(s) we could not find positive evidence for
- C3 Audit Trail — Not assessed: these audit controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks audit controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- C4 Data Retention — Not assessed: these retention controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks retention controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- C5 Data-Subject Rights — Not assessed: these data-subject rights controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks data-subject rights controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- P6 Release Hygiene — not evidenced — no changelog, version stamp or semver release tag in the repo
Not included — 57 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.
- AX4 Dependency direction — not applicable to a CQRS architecture (the inward-dependency rule is for layered/clean styles)
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AX8 Test isolation — no test/production split to check
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXR1 Runtime accessibility — compose up failed (exit 1 — a container did not start, exited, or never became healthy) — container redis-admin is unhealthy; runtime evidence skipped This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
- C1 Data Protection — Not assessed: these personal data controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks personal data controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- C2 Access Controls — Not assessed: these authorization controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks authorization controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- D11 Test Reliability — Test reliability not included — the .java suite was found but not re-run
- D12 Dependency Hygiene — Not scored — 8 Maven/Gradle manifest(s) were read, stating a version for 8 dependency(ies) and leaving 20 to a parent or an imported BOM, but no build resolved the dependency graph, so the outdated signal was not established. NOT a finding that these dependencies are current or healthy.
- D15 Churn × Complexity Hotspots — single-commit history — no usable git history window to measure hotspots
- 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; Java not measured.
- D22 Internal API Consistency — The exposed public-API surface could not be collected — no C#/VB projects loaded.
- D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D24 Comment Value — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only — this repository's production source is .java, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D25 ADR Conformance — no ADRs to check
- D32 Data Compliance (PII/GDPR) — 1 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
- D34 Knowledge Freshness — too few commits to judge knowledge freshness
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- D39 IL Efficiency — D39 measures the IL emitted by a .NET build; this repository has no .NET solution or project files, so the dimension does not apply.
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
- D8 Code Coverage — Coverage not included — suite not readable by the collector
- DM1 Domain Modelling — applicable but not scored (2 of 3 signals for this style — below the bar we score at): 13 value object(s); a Domain/Aggregates/ValueObjects layer
- ED1 Event-Driven — not scored — this repository shows only 1 of the 3 signals this lens looks for (28 CQRS handler(s))
- ED5 Idempotency — Not assessed, and this one is on us: 17 command handler(s) or message consumer(s) were found here, but this check does not yet recognise persistence writes in this repository's language. Idempotency was neither confirmed nor ruled out — this is a limit of the analyzer, not a finding about your code.
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- GD1 Unfinished & placeholder code — no source files were read — this check reads C#, F#, JavaScript/TypeScript, Dart, Ruby and Scala, and none was read for this repository's product. That is a limit of the analyzer, not a finding about your code.
- M4 Documentation accuracy — Not applicable: the 1 current-state document(s) make no claim of a kind M4 checks. 3 claim(s) of kinds M4 does not check were not checked (path 1, command argument 2); M4 checks only links and versions and artefact counts.
- P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
- P7 Outbound HTTP resilience — no outbound HTTP usage detected — no HTTP client call or construction in the JVM source (service entry point: productservice/src/main/java/com/company/productservice/Application.java:6 (@SpringBootApplication))
- P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
- P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (JaCoCo XML — `mvn jacoco:report` or the Gradle `jacocoTestReport` task) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures, or wire coverage collection into CI, to enable this cross-layer check
- PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for `@Benchmark` in a Java, Kotlin or Scala file importing JMH or kotlinx-benchmark, Jetpack Benchmark's `measureRepeated` in a file importing androidx.benchmark, or JMH/kotlinx-benchmark/androidx.benchmark in a REDACTED, Gradle or sbt build, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
- PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
- PF3 Async & latency hygiene — Not applicable: this repository declares no async functions, so there is no asynchronous code for a blocking call to stall.
- S1 Web-Security Posture — Not assessed: these web-security controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks web-security controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- X1 Async correctness — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X10 Duplicated predicate — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X12 Unreachable branch — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X13 Undrained process stream — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X17 Uncapped recursion over a caller-supplied document — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X2 Cancellation propagation — no C# was loaded; this repository's Java was read, and no request in it can be cancelled by a caller — a Java request off Android takes no token: it is cancelled through the handle it returns (Future.cancel, Call.cancel, a Disposable), ambiently (io.grpc.Context) or by interrupting its thread, not through a parameter
- X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X7 Silent fallback defaults — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
Critical — 17 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
Serious — 12 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- No assertions: shouldCancelOrderWhenPaymentEventIsCanceled orderservice/src/test/java/com/company/orderservice/order/OrderIntegrationTest.java:94
- No assertions: shouldCompleteOrderWhenPaymentEventIsApproved orderservice/src/test/java/com/company/orderservice/order/OrderIntegrationTest.java:86
- No assertions: shouldCreatePaymentWhenOrderCreatedEventIsSent paymentservice/src/test/java/com/company/paymentservice/payment/PaymentIntegrationTest.java:106
- No assertions: shouldExecuteHandlerWhenHandlerIsDispatched starter/src/test/java/com/company/starter/mediator/MediatorTest.java:37
- No assertions: shouldExecuteHandlerWhenRequestIsDispatched starter/src/test/java/com/company/starter/mediator/MediatorTest.java:42
- REDACTED
Minor — 7 finding(s)
- No ADRs found
- High interface indirection
- REDACTED
- No ADRs
- Logging is not universal
- No SAST
- Java packages are not null-marked everywhere
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-d3b90abfcadb4cd09209c98bd49f5dd1/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-d3b90abfcadb4cd09209c98bd49f5dd1/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 . | 6 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . | 2 | artifacts/raw/osv-scanner.json |
| D31 · IaC & Container Security | trivy | — | trivy config --format json --quiet . | 15 | artifacts/raw/trivy-config.json |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. semgrep could not parse 1 file(s) — `starter/src/main/java/com/company/starter/exception/GlobalExceptionHandler.java` — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real. | 0 | — |
| D37 · Vulnerability-disclosure Policy | disclosure | — | disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . | 0 | artifacts/raw/osv-scanner.json |