Executive summary
idugalic/micro-company is rated At risk because critical security findings are open, most of them in the packages it uses. Its score is held back because we found no automated security scanning of the code, its secrets or its dependencies. It scores 51 out of 100, which the At risk rating leaves unchanged.
Production Readiness, at 43, is the weakest lens and counts most in the score. The best first step is fixing the password or key in the code, worth about 7 points. Adding automated security scanning would lift Production Readiness itself, worth about 6 points. Raising Production Readiness to 70 would lift the score to about 58.
Forty known security holes in the packages the code depends on can be used by attackers. Thirty-two settings leave the servers or containers unsafe, and eight form fields can't be read by a screen reader. Updating the vulnerable packages, correcting the unsafe settings and labelling the form fields would close these risks. Pinning each tool to an exact version would fix the two pipeline tools referenced by a changeable name. The three pages that don't say their language need their language set.
The product code is 3,990 lines, about €6,100 to rebuild. The check for the health of its packages couldn't finish, so that result is missing, not a clean pass.
If Production Readiness rose from 43 to 70, the lowest score rated Strong, the score would rise from 51 to about 58.
New since the last survey: 48 findings
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
Fixed since the last survey: 2 findings
- Dependency Vulnerabilities · Critical CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · High CVE: [GHSA redacted] adminserver/pom.xml
Rebuild cost: about €6,100 · Estimate
| Cost to rebuild | €2,000 to €10,000, for 34 to 107 hours of work, under 0.1 person-years for one engineer |
|---|---|
| Difficulty of the problem | High, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.7 at a score of 51. 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,990 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 api-gateway.src.main.resources.static.socket | 2 com.idugalic | 3 com.idugalic.apigateway | 4 com.idugalic.apigateway.configuration | 5 com.idugalic.common.blog.model | 6 com.idugalic.common.model | 7 monolithic.src.main.frontend.src.app.blog-posts.shared.blog-post_model | 8 monolithic.src.main.frontend.src.app.projects.shared.project_model | 9 monolithic.src.main.frontend.src.app.shared.alert.alert_service | 10 monolithic.src.main.frontend.src.app.shared.event-manager_service | 11 monolithic.src.main.frontend.src.app.shared.interceptor.http_interceptable | 12 com.idugalic.commandside.blog.web | 13 com.idugalic.commandside.project.web | 14 com.idugalic.common.command | 15 com.idugalic.common.event | 16 monolithic.src.main.frontend.src.app.blog-posts.shared.blog-posts_service | 17 monolithic.src.main.frontend.src.app.projects.shared.projects_service | 18 monolithic.src.main.frontend.src.app.shared.alert.alert-error_component | 19 monolithic.src.main.frontend.src.app.shared.alert.alert_component | 20 monolithic.src.main.frontend.src.app.shared.interceptor.errorhandler_interceptor | 21 monolithic.src.main.frontend.src.app.shared.interceptor.http_interceptor | 22 com.idugalic.commandside.blog.command | 23 com.idugalic.commandside.project.command | 24 com.idugalic.common.blog.event | 25 com.idugalic.common.project.event | 26 monolithic.src.main.frontend.src.app.blog-posts.blog-post-list.blog-post-list_component | 27 monolithic.src.main.frontend.src.app.blog-posts.blog-post-new.blog-post-new_component | 28 monolithic.src.main.frontend.src.app.blog-posts.blog-post.blog-post_component | 29 monolithic.src.main.frontend.src.app.projects.project-list.project-list_component | 30 monolithic.src.main.frontend.src.app.projects.project-new.project-new_component | 31 monolithic.src.main.frontend.src.app.projects.project.project_component | 32 com.idugalic.apigateway.handler | 33 com.idugalic.commandside.blog.aggregate | 34 com.idugalic.commandside.project.aggregate | 35 com.idugalic.queryside.blog.domain | 36 com.idugalic.queryside.project.domain | 37 com.idugalic.queryside.blog.repository | 38 com.idugalic.queryside.project.repository | 39 com.idugalic.queryside.blog.handler | 40 com.idugalic.queryside.project.handler |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 api-gateway.src.main.resources.static.socket | ||||||||||||||||||||||||||||||||||||||||
| 2 com.idugalic | ||||||||||||||||||||||||||||||||||||||||
| 3 com.idugalic.apigateway | ||||||||||||||||||||||||||||||||||||||||
| 4 com.idugalic.apigateway.configuration | ||||||||||||||||||||||||||||||||||||||||
| 5 com.idugalic.common.blog.model | ||||||||||||||||||||||||||||||||||||||||
| 6 com.idugalic.common.model | ||||||||||||||||||||||||||||||||||||||||
| 7 monolithic.src.main.frontend.src.app.blog-posts.shared.blog-post_model | ||||||||||||||||||||||||||||||||||||||||
| 8 monolithic.src.main.frontend.src.app.projects.shared.project_model | ||||||||||||||||||||||||||||||||||||||||
| 9 monolithic.src.main.frontend.src.app.shared.alert.alert_service | ||||||||||||||||||||||||||||||||||||||||
| 10 monolithic.src.main.frontend.src.app.shared.event-manager_service | ||||||||||||||||||||||||||||||||||||||||
| 11 monolithic.src.main.frontend.src.app.shared.interceptor.http_interceptable | ||||||||||||||||||||||||||||||||||||||||
| 12 com.idugalic.commandside.blog.web | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 13 com.idugalic.commandside.project.web | 1 | |||||||||||||||||||||||||||||||||||||||
| 14 com.idugalic.common.command | 1 | |||||||||||||||||||||||||||||||||||||||
| 15 com.idugalic.common.event | 1 | |||||||||||||||||||||||||||||||||||||||
| 16 monolithic.src.main.frontend.src.app.blog-posts.shared.blog-posts_service | 1 | |||||||||||||||||||||||||||||||||||||||
| 17 monolithic.src.main.frontend.src.app.projects.shared.projects_service | 1 | |||||||||||||||||||||||||||||||||||||||
| 18 monolithic.src.main.frontend.src.app.shared.alert.alert-error_component | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 19 monolithic.src.main.frontend.src.app.shared.alert.alert_component | 1 | |||||||||||||||||||||||||||||||||||||||
| 20 monolithic.src.main.frontend.src.app.shared.interceptor.errorhandler_interceptor | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 21 monolithic.src.main.frontend.src.app.shared.interceptor.http_interceptor | 1 | |||||||||||||||||||||||||||||||||||||||
| 22 com.idugalic.commandside.blog.command | 1 | 2 | 2 | |||||||||||||||||||||||||||||||||||||
| 23 com.idugalic.commandside.project.command | 2 | 2 | ||||||||||||||||||||||||||||||||||||||
| 24 com.idugalic.common.blog.event | 1 | 2 | 2 | |||||||||||||||||||||||||||||||||||||
| 25 com.idugalic.common.project.event | 2 | 2 | ||||||||||||||||||||||||||||||||||||||
| 26 monolithic.src.main.frontend.src.app.blog-posts.blog-post-list.blog-post-list_component | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 27 monolithic.src.main.frontend.src.app.blog-posts.blog-post-new.blog-post-new_component | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 28 monolithic.src.main.frontend.src.app.blog-posts.blog-post.blog-post_component | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 29 monolithic.src.main.frontend.src.app.projects.project-list.project-list_component | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 30 monolithic.src.main.frontend.src.app.projects.project-new.project-new_component | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 31 monolithic.src.main.frontend.src.app.projects.project.project_component | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 32 com.idugalic.apigateway.handler | 1 | 2 | 2 | |||||||||||||||||||||||||||||||||||||
| 33 com.idugalic.commandside.blog.aggregate | 1 | 2 | 2 | |||||||||||||||||||||||||||||||||||||
| 34 com.idugalic.commandside.project.aggregate | 2 | 2 | ||||||||||||||||||||||||||||||||||||||
| 35 com.idugalic.queryside.blog.domain | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 36 com.idugalic.queryside.project.domain | 1 | |||||||||||||||||||||||||||||||||||||||
| 37 com.idugalic.queryside.blog.repository | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 38 com.idugalic.queryside.project.repository | 1 | |||||||||||||||||||||||||||||||||||||||
| 39 com.idugalic.queryside.blog.handler | 2 | 1 | ||||||||||||||||||||||||||||||||||||||
| 40 com.idugalic.queryside.project.handler | 1 | 1 |
12→5 com.idugalic.commandside.blog.web uses com.idugalic.common.blog.model✕
- Connections
- 1 pair of types, where a type in com.idugalic.commandside.blog.web uses a type in com.idugalic.common.blog.model.
- The types involved
com.idugalic.commandside.blog.web.CreateBlogPostRequest→com.idugalic.common.blog.model.BlogPostCategory
- Direction
- com.idugalic.commandside.blog.web uses com.idugalic.common.blog.model, so a change to com.idugalic.common.blog.model can break com.idugalic.commandside.blog.web, while a change to com.idugalic.commandside.blog.web can't break com.idugalic.common.blog.model.
- Position
- Below the diagonal: com.idugalic.commandside.blog.web uses a module listed above it, which is the healthy direction.
12→6 com.idugalic.commandside.blog.web uses com.idugalic.common.model✕
- Connections
- 1 pair of types, where a type in com.idugalic.commandside.blog.web uses a type in com.idugalic.common.model.
- The types involved
com.idugalic.commandside.blog.web.BlogController→com.idugalic.common.model.AuditEntry
- Direction
- com.idugalic.commandside.blog.web uses com.idugalic.common.model, so a change to com.idugalic.common.model can break com.idugalic.commandside.blog.web, while a change to com.idugalic.commandside.blog.web can't break com.idugalic.common.model.
- Position
- Below the diagonal: com.idugalic.commandside.blog.web uses a module listed above it, which is the healthy direction.
13→6 com.idugalic.commandside.project.web uses com.idugalic.common.model✕
- Connections
- 1 pair of types, where a type in com.idugalic.commandside.project.web uses a type in com.idugalic.common.model.
- The types involved
com.idugalic.commandside.project.web.ProjectController→com.idugalic.common.model.AuditEntry
- Direction
- com.idugalic.commandside.project.web uses com.idugalic.common.model, so a change to com.idugalic.common.model can break com.idugalic.commandside.project.web, while a change to com.idugalic.commandside.project.web can't break com.idugalic.common.model.
- Position
- Below the diagonal: com.idugalic.commandside.project.web uses a module listed above it, which is the healthy direction.
14→6 com.idugalic.common.command uses com.idugalic.common.model✕
- Connections
- 1 pair of types, where a type in com.idugalic.common.command uses a type in com.idugalic.common.model.
- The types involved
com.idugalic.common.command.AuditableAbstractCommand→com.idugalic.common.model.AuditEntry
- Direction
- com.idugalic.common.command uses com.idugalic.common.model, so a change to com.idugalic.common.model can break com.idugalic.common.command, while a change to com.idugalic.common.command can't break com.idugalic.common.model.
- Position
- Below the diagonal: com.idugalic.common.command uses a module listed above it, which is the healthy direction.
15→6 com.idugalic.common.event uses com.idugalic.common.model✕
- Connections
- 1 pair of types, where a type in com.idugalic.common.event uses a type in com.idugalic.common.model.
- The types involved
com.idugalic.common.event.AuditableAbstractEvent→com.idugalic.common.model.AuditEntry
- Direction
- com.idugalic.common.event uses com.idugalic.common.model, so a change to com.idugalic.common.model can break com.idugalic.common.event, while a change to com.idugalic.common.event can't break com.idugalic.common.model.
- Position
- Below the diagonal: com.idugalic.common.event uses a module listed above it, which is the healthy direction.
16→7 monolithic.src.main.frontend.src.app.blog-posts.shared.blog-posts_service uses monolithic.src.main.frontend.src.app.blog-posts.shared.blog-post_model✕
- Connections
- 1 pair of types, where a type in monolithic.src.main.frontend.src.app.blog-posts.shared.blog-posts_service uses a type in monolithic.src.main.frontend.src.app.blog-posts.shared.blog-post_model.
- The types involved
monolithic.src.main.frontend.src.app.blog-posts.shared.blog-posts_service.BlogPostsService→monolithic.src.main.frontend.src.app.blog-posts.shared.blog-post_model.BlogPostModel
- Direction
- monolithic.src.main.frontend.src.app.blog-posts.shared.blog-posts_service uses monolithic.src.main.frontend.src.app.blog-posts.shared.blog-post_model, so a change to monolithic.src.main.frontend.src.app.blog-posts.shared.blog-post_model can break monolithic.src.main.frontend.src.app.blog-posts.shared.blog-posts_service, while a change to monolithic.src.main.frontend.src.app.blog-posts.shared.blog-posts_service can't break monolithic.src.main.frontend.src.app.blog-posts.shared.blog-post_model.
- Position
- Below the diagonal: monolithic.src.main.frontend.src.app.blog-posts.shared.blog-posts_service uses a module listed above it, which is the healthy direction.
17→8 monolithic.src.main.frontend.src.app.projects.shared.projects_service uses monolithic.src.main.frontend.src.app.projects.shared.project_model✕
- Connections
- 1 pair of types, where a type in monolithic.src.main.frontend.src.app.projects.shared.projects_service uses a type in monolithic.src.main.frontend.src.app.projects.shared.project_model.
- The types involved
monolithic.src.main.frontend.src.app.projects.shared.projects_service.ProjectsService→monolithic.src.main.frontend.src.app.projects.shared.project_model.ProjectModel
- Direction
- monolithic.src.main.frontend.src.app.projects.shared.projects_service uses monolithic.src.main.frontend.src.app.projects.shared.project_model, so a change to monolithic.src.main.frontend.src.app.projects.shared.project_model can break monolithic.src.main.frontend.src.app.projects.shared.projects_service, while a change to monolithic.src.main.frontend.src.app.projects.shared.projects_service can't break monolithic.src.main.frontend.src.app.projects.shared.project_model.
- Position
- Below the diagonal: monolithic.src.main.frontend.src.app.projects.shared.projects_service uses a module listed above it, which is the healthy direction.
18→9 monolithic.src.main.frontend.src.app.shared.alert.alert-error_component uses monolithic.src.main.frontend.src.app.shared.alert.alert_service✕
- Connections
- 1 pair of types, where a type in monolithic.src.main.frontend.src.app.shared.alert.alert-error_component uses a type in monolithic.src.main.frontend.src.app.shared.alert.alert_service.
- The types involved
monolithic.src.main.frontend.src.app.shared.alert.alert-error_component.AlertErrorComponent→monolithic.src.main.frontend.src.app.shared.alert.alert_service.AlertService
- Direction
- monolithic.src.main.frontend.src.app.shared.alert.alert-error_component uses monolithic.src.main.frontend.src.app.shared.alert.alert_service, so a change to monolithic.src.main.frontend.src.app.shared.alert.alert_service can break monolithic.src.main.frontend.src.app.shared.alert.alert-error_component, while a change to monolithic.src.main.frontend.src.app.shared.alert.alert-error_component can't break monolithic.src.main.frontend.src.app.shared.alert.alert_service.
- Position
- Below the diagonal: monolithic.src.main.frontend.src.app.shared.alert.alert-error_component uses a module listed above it, which is the healthy direction.
18→10 monolithic.src.main.frontend.src.app.shared.alert.alert-error_component uses monolithic.src.main.frontend.src.app.shared.event-manager_service✕
- Connections
- 1 pair of types, where a type in monolithic.src.main.frontend.src.app.shared.alert.alert-error_component uses a type in monolithic.src.main.frontend.src.app.shared.event-manager_service.
- The types involved
monolithic.src.main.frontend.src.app.shared.alert.alert-error_component.AlertErrorComponent→monolithic.src.main.frontend.src.app.shared.event-manager_service.EventManager
- Direction
- monolithic.src.main.frontend.src.app.shared.alert.alert-error_component uses monolithic.src.main.frontend.src.app.shared.event-manager_service, so a change to monolithic.src.main.frontend.src.app.shared.event-manager_service can break monolithic.src.main.frontend.src.app.shared.alert.alert-error_component, while a change to monolithic.src.main.frontend.src.app.shared.alert.alert-error_component can't break monolithic.src.main.frontend.src.app.shared.event-manager_service.
- Position
- Below the diagonal: monolithic.src.main.frontend.src.app.shared.alert.alert-error_component uses a module listed above it, which is the healthy direction.
19→9 monolithic.src.main.frontend.src.app.shared.alert.alert_component uses monolithic.src.main.frontend.src.app.shared.alert.alert_service✕
- Connections
- 1 pair of types, where a type in monolithic.src.main.frontend.src.app.shared.alert.alert_component uses a type in monolithic.src.main.frontend.src.app.shared.alert.alert_service.
- The types involved
monolithic.src.main.frontend.src.app.shared.alert.alert_component.AlertComponent→monolithic.src.main.frontend.src.app.shared.alert.alert_service.AlertService
- Direction
- monolithic.src.main.frontend.src.app.shared.alert.alert_component uses monolithic.src.main.frontend.src.app.shared.alert.alert_service, so a change to monolithic.src.main.frontend.src.app.shared.alert.alert_service can break monolithic.src.main.frontend.src.app.shared.alert.alert_component, while a change to monolithic.src.main.frontend.src.app.shared.alert.alert_component can't break monolithic.src.main.frontend.src.app.shared.alert.alert_service.
- Position
- Below the diagonal: monolithic.src.main.frontend.src.app.shared.alert.alert_component uses a module listed above it, which is the healthy direction.
20→10 monolithic.src.main.frontend.src.app.shared.interceptor.errorhandler_interceptor uses monolithic.src.main.frontend.src.app.shared.event-manager_service✕
- Connections
- 1 pair of types, where a type in monolithic.src.main.frontend.src.app.shared.interceptor.errorhandler_interceptor uses a type in monolithic.src.main.frontend.src.app.shared.event-manager_service.
- The types involved
monolithic.src.main.frontend.src.app.shared.interceptor.errorhandler_interceptor.ErrorHandlerInterceptor→monolithic.src.main.frontend.src.app.shared.event-manager_service.EventManager
- Direction
- monolithic.src.main.frontend.src.app.shared.interceptor.errorhandler_interceptor uses monolithic.src.main.frontend.src.app.shared.event-manager_service, so a change to monolithic.src.main.frontend.src.app.shared.event-manager_service can break monolithic.src.main.frontend.src.app.shared.interceptor.errorhandler_interceptor, while a change to monolithic.src.main.frontend.src.app.shared.interceptor.errorhandler_interceptor can't break monolithic.src.main.frontend.src.app.shared.event-manager_service.
- Position
- Below the diagonal: monolithic.src.main.frontend.src.app.shared.interceptor.errorhandler_interceptor uses a module listed above it, which is the healthy direction.
20→11 monolithic.src.main.frontend.src.app.shared.interceptor.errorhandler_interceptor uses monolithic.src.main.frontend.src.app.shared.interceptor.http_interceptable✕
- Connections
- 1 pair of types, where a type in monolithic.src.main.frontend.src.app.shared.interceptor.errorhandler_interceptor uses a type in monolithic.src.main.frontend.src.app.shared.interceptor.http_interceptable.
- The types involved
monolithic.src.main.frontend.src.app.shared.interceptor.errorhandler_interceptor.ErrorHandlerInterceptor→monolithic.src.main.frontend.src.app.shared.interceptor.http_interceptable.HttpInterceptable
- Direction
- monolithic.src.main.frontend.src.app.shared.interceptor.errorhandler_interceptor uses monolithic.src.main.frontend.src.app.shared.interceptor.http_interceptable, so a change to monolithic.src.main.frontend.src.app.shared.interceptor.http_interceptable can break monolithic.src.main.frontend.src.app.shared.interceptor.errorhandler_interceptor, while a change to monolithic.src.main.frontend.src.app.shared.interceptor.errorhandler_interceptor can't break monolithic.src.main.frontend.src.app.shared.interceptor.http_interceptable.
- Position
- Below the diagonal: monolithic.src.main.frontend.src.app.shared.interceptor.errorhandler_interceptor uses a module listed above it, which is the healthy direction.
21→11 monolithic.src.main.frontend.src.app.shared.interceptor.http_interceptor uses monolithic.src.main.frontend.src.app.shared.interceptor.http_interceptable✕
- Connections
- 1 pair of types, where a type in monolithic.src.main.frontend.src.app.shared.interceptor.http_interceptor uses a type in monolithic.src.main.frontend.src.app.shared.interceptor.http_interceptable.
- The types involved
monolithic.src.main.frontend.src.app.shared.interceptor.http_interceptor.HttpInterceptor→monolithic.src.main.frontend.src.app.shared.interceptor.http_interceptable.HttpInterceptable
- Direction
- monolithic.src.main.frontend.src.app.shared.interceptor.http_interceptor uses monolithic.src.main.frontend.src.app.shared.interceptor.http_interceptable, so a change to monolithic.src.main.frontend.src.app.shared.interceptor.http_interceptable can break monolithic.src.main.frontend.src.app.shared.interceptor.http_interceptor, while a change to monolithic.src.main.frontend.src.app.shared.interceptor.http_interceptor can't break monolithic.src.main.frontend.src.app.shared.interceptor.http_interceptable.
- Position
- Below the diagonal: monolithic.src.main.frontend.src.app.shared.interceptor.http_interceptor uses a module listed above it, which is the healthy direction.
22→5 com.idugalic.commandside.blog.command uses com.idugalic.common.blog.model✕
- Connections
- 1 pair of types, where a type in com.idugalic.commandside.blog.command uses a type in com.idugalic.common.blog.model.
- The types involved
com.idugalic.commandside.blog.command.CreateBlogPostCommand→com.idugalic.common.blog.model.BlogPostCategory
- Direction
- com.idugalic.commandside.blog.command uses com.idugalic.common.blog.model, so a change to com.idugalic.common.blog.model can break com.idugalic.commandside.blog.command, while a change to com.idugalic.commandside.blog.command can't break com.idugalic.common.blog.model.
- Position
- Below the diagonal: com.idugalic.commandside.blog.command uses a module listed above it, which is the healthy direction.
22→6 com.idugalic.commandside.blog.command uses com.idugalic.common.model✕
- Connections
- 2 pairs of types, where a type in com.idugalic.commandside.blog.command uses a type in com.idugalic.common.model.
- The types involved
com.idugalic.commandside.blog.command.CreateBlogPostCommand→com.idugalic.common.model.AuditEntrycom.idugalic.commandside.blog.command.PublishBlogPostCommand→com.idugalic.common.model.AuditEntry
- Direction
- com.idugalic.commandside.blog.command uses com.idugalic.common.model, so a change to com.idugalic.common.model can break com.idugalic.commandside.blog.command, while a change to com.idugalic.commandside.blog.command can't break com.idugalic.common.model.
- Position
- Below the diagonal: com.idugalic.commandside.blog.command uses a module listed above it, which is the healthy direction.
22→14 com.idugalic.commandside.blog.command uses com.idugalic.common.command✕
- Connections
- 2 pairs of types, where a type in com.idugalic.commandside.blog.command uses a type in com.idugalic.common.command.
- The types involved
com.idugalic.commandside.blog.command.CreateBlogPostCommand→com.idugalic.common.command.AuditableAbstractCommandcom.idugalic.commandside.blog.command.PublishBlogPostCommand→com.idugalic.common.command.AuditableAbstractCommand
- Direction
- com.idugalic.commandside.blog.command uses com.idugalic.common.command, so a change to com.idugalic.common.command can break com.idugalic.commandside.blog.command, while a change to com.idugalic.commandside.blog.command can't break com.idugalic.common.command.
- Position
- Below the diagonal: com.idugalic.commandside.blog.command uses a module listed above it, which is the healthy direction.
23→6 com.idugalic.commandside.project.command uses com.idugalic.common.model✕
- Connections
- 2 pairs of types, where a type in com.idugalic.commandside.project.command uses a type in com.idugalic.common.model.
- The types involved
com.idugalic.commandside.project.command.CreateProjectCommand→com.idugalic.common.model.AuditEntrycom.idugalic.commandside.project.command.UpdateProjectCommand→com.idugalic.common.model.AuditEntry
- Direction
- com.idugalic.commandside.project.command uses com.idugalic.common.model, so a change to com.idugalic.common.model can break com.idugalic.commandside.project.command, while a change to com.idugalic.commandside.project.command can't break com.idugalic.common.model.
- Position
- Below the diagonal: com.idugalic.commandside.project.command uses a module listed above it, which is the healthy direction.
23→14 com.idugalic.commandside.project.command uses com.idugalic.common.command✕
- Connections
- 2 pairs of types, where a type in com.idugalic.commandside.project.command uses a type in com.idugalic.common.command.
- The types involved
com.idugalic.commandside.project.command.CreateProjectCommand→com.idugalic.common.command.AuditableAbstractCommandcom.idugalic.commandside.project.command.UpdateProjectCommand→com.idugalic.common.command.AuditableAbstractCommand
- Direction
- com.idugalic.commandside.project.command uses com.idugalic.common.command, so a change to com.idugalic.common.command can break com.idugalic.commandside.project.command, while a change to com.idugalic.commandside.project.command can't break com.idugalic.common.command.
- Position
- Below the diagonal: com.idugalic.commandside.project.command uses a module listed above it, which is the healthy direction.
24→5 com.idugalic.common.blog.event uses com.idugalic.common.blog.model✕
- Connections
- 1 pair of types, where a type in com.idugalic.common.blog.event uses a type in com.idugalic.common.blog.model.
- The types involved
com.idugalic.common.blog.event.BlogPostCreatedEvent→com.idugalic.common.blog.model.BlogPostCategory
- Direction
- com.idugalic.common.blog.event uses com.idugalic.common.blog.model, so a change to com.idugalic.common.blog.model can break com.idugalic.common.blog.event, while a change to com.idugalic.common.blog.event can't break com.idugalic.common.blog.model.
- Position
- Below the diagonal: com.idugalic.common.blog.event uses a module listed above it, which is the healthy direction.
24→6 com.idugalic.common.blog.event uses com.idugalic.common.model✕
- Connections
- 2 pairs of types, where a type in com.idugalic.common.blog.event uses a type in com.idugalic.common.model.
- The types involved
com.idugalic.common.blog.event.BlogPostCreatedEvent→com.idugalic.common.model.AuditEntrycom.idugalic.common.blog.event.BlogPostPublishedEvent→com.idugalic.common.model.AuditEntry
- Direction
- com.idugalic.common.blog.event uses com.idugalic.common.model, so a change to com.idugalic.common.model can break com.idugalic.common.blog.event, while a change to com.idugalic.common.blog.event can't break com.idugalic.common.model.
- Position
- Below the diagonal: com.idugalic.common.blog.event uses a module listed above it, which is the healthy direction.
24→15 com.idugalic.common.blog.event uses com.idugalic.common.event✕
- Connections
- 2 pairs of types, where a type in com.idugalic.common.blog.event uses a type in com.idugalic.common.event.
- The types involved
com.idugalic.common.blog.event.BlogPostCreatedEvent→com.idugalic.common.event.AuditableAbstractEventcom.idugalic.common.blog.event.BlogPostPublishedEvent→com.idugalic.common.event.AuditableAbstractEvent
- Direction
- com.idugalic.common.blog.event uses com.idugalic.common.event, so a change to com.idugalic.common.event can break com.idugalic.common.blog.event, while a change to com.idugalic.common.blog.event can't break com.idugalic.common.event.
- Position
- Below the diagonal: com.idugalic.common.blog.event uses a module listed above it, which is the healthy direction.
25→6 com.idugalic.common.project.event uses com.idugalic.common.model✕
- Connections
- 2 pairs of types, where a type in com.idugalic.common.project.event uses a type in com.idugalic.common.model.
- The types involved
com.idugalic.common.project.event.ProjectCreatedEvent→com.idugalic.common.model.AuditEntrycom.idugalic.common.project.event.ProjectUpdatedEvent→com.idugalic.common.model.AuditEntry
- Direction
- com.idugalic.common.project.event uses com.idugalic.common.model, so a change to com.idugalic.common.model can break com.idugalic.common.project.event, while a change to com.idugalic.common.project.event can't break com.idugalic.common.model.
- Position
- Below the diagonal: com.idugalic.common.project.event uses a module listed above it, which is the healthy direction.
25→15 com.idugalic.common.project.event uses com.idugalic.common.event✕
- Connections
- 2 pairs of types, where a type in com.idugalic.common.project.event uses a type in com.idugalic.common.event.
- The types involved
com.idugalic.common.project.event.ProjectCreatedEvent→com.idugalic.common.event.AuditableAbstractEventcom.idugalic.common.project.event.ProjectUpdatedEvent→com.idugalic.common.event.AuditableAbstractEvent
- Direction
- com.idugalic.common.project.event uses com.idugalic.common.event, so a change to com.idugalic.common.event can break com.idugalic.common.project.event, while a change to com.idugalic.common.project.event can't break com.idugalic.common.event.
- Position
- Below the diagonal: com.idugalic.common.project.event uses a module listed above it, which is the healthy direction.
26→10 monolithic.src.main.frontend.src.app.blog-posts.blog-post-list.blog-post-list_component uses monolithic.src.main.frontend.src.app.shared.event-manager_service✕
- Connections
- 1 pair of types, where a type in monolithic.src.main.frontend.src.app.blog-posts.blog-post-list.blog-post-list_component uses a type in monolithic.src.main.frontend.src.app.shared.event-manager_service.
- The types involved
monolithic.src.main.frontend.src.app.blog-posts.blog-post-list.blog-post-list_component.BlogPostListComponent→monolithic.src.main.frontend.src.app.shared.event-manager_service.EventManager
- Direction
- monolithic.src.main.frontend.src.app.blog-posts.blog-post-list.blog-post-list_component uses monolithic.src.main.frontend.src.app.shared.event-manager_service, so a change to monolithic.src.main.frontend.src.app.shared.event-manager_service can break monolithic.src.main.frontend.src.app.blog-posts.blog-post-list.blog-post-list_component, while a change to monolithic.src.main.frontend.src.app.blog-posts.blog-post-list.blog-post-list_component can't break monolithic.src.main.frontend.src.app.shared.event-manager_service.
- Position
- Below the diagonal: monolithic.src.main.frontend.src.app.blog-posts.blog-post-list.blog-post-list_component uses a module listed above it, which is the healthy direction.
26→16 monolithic.src.main.frontend.src.app.blog-posts.blog-post-list.blog-post-list_component uses monolithic.src.main.frontend.src.app.blog-posts.shared.blog-posts_service✕
- Connections
- 1 pair of types, where a type in monolithic.src.main.frontend.src.app.blog-posts.blog-post-list.blog-post-list_component uses a type in monolithic.src.main.frontend.src.app.blog-posts.shared.blog-posts_service.
- The types involved
monolithic.src.main.frontend.src.app.blog-posts.blog-post-list.blog-post-list_component.BlogPostListComponent→monolithic.src.main.frontend.src.app.blog-posts.shared.blog-posts_service.BlogPostsService
- Direction
- monolithic.src.main.frontend.src.app.blog-posts.blog-post-list.blog-post-list_component uses monolithic.src.main.frontend.src.app.blog-posts.shared.blog-posts_service, so a change to monolithic.src.main.frontend.src.app.blog-posts.shared.blog-posts_service can break monolithic.src.main.frontend.src.app.blog-posts.blog-post-list.blog-post-list_component, while a change to monolithic.src.main.frontend.src.app.blog-posts.blog-post-list.blog-post-list_component can't break monolithic.src.main.frontend.src.app.blog-posts.shared.blog-posts_service.
- Position
- Below the diagonal: monolithic.src.main.frontend.src.app.blog-posts.blog-post-list.blog-post-list_component uses a module listed above it, which is the healthy direction.
27→10 monolithic.src.main.frontend.src.app.blog-posts.blog-post-new.blog-post-new_component uses monolithic.src.main.frontend.src.app.shared.event-manager_service✕
- Connections
- 1 pair of types, where a type in monolithic.src.main.frontend.src.app.blog-posts.blog-post-new.blog-post-new_component uses a type in monolithic.src.main.frontend.src.app.shared.event-manager_service.
- The types involved
monolithic.src.main.frontend.src.app.blog-posts.blog-post-new.blog-post-new_component.BlogPostNewComponent→monolithic.src.main.frontend.src.app.shared.event-manager_service.EventManager
- Direction
- monolithic.src.main.frontend.src.app.blog-posts.blog-post-new.blog-post-new_component uses monolithic.src.main.frontend.src.app.shared.event-manager_service, so a change to monolithic.src.main.frontend.src.app.shared.event-manager_service can break monolithic.src.main.frontend.src.app.blog-posts.blog-post-new.blog-post-new_component, while a change to monolithic.src.main.frontend.src.app.blog-posts.blog-post-new.blog-post-new_component can't break monolithic.src.main.frontend.src.app.shared.event-manager_service.
- Position
- Below the diagonal: monolithic.src.main.frontend.src.app.blog-posts.blog-post-new.blog-post-new_component uses a module listed above it, which is the healthy direction.
27→16 monolithic.src.main.frontend.src.app.blog-posts.blog-post-new.blog-post-new_component uses monolithic.src.main.frontend.src.app.blog-posts.shared.blog-posts_service✕
- Connections
- 1 pair of types, where a type in monolithic.src.main.frontend.src.app.blog-posts.blog-post-new.blog-post-new_component uses a type in monolithic.src.main.frontend.src.app.blog-posts.shared.blog-posts_service.
- The types involved
monolithic.src.main.frontend.src.app.blog-posts.blog-post-new.blog-post-new_component.BlogPostNewComponent→monolithic.src.main.frontend.src.app.blog-posts.shared.blog-posts_service.BlogPostsService
- Direction
- monolithic.src.main.frontend.src.app.blog-posts.blog-post-new.blog-post-new_component uses monolithic.src.main.frontend.src.app.blog-posts.shared.blog-posts_service, so a change to monolithic.src.main.frontend.src.app.blog-posts.shared.blog-posts_service can break monolithic.src.main.frontend.src.app.blog-posts.blog-post-new.blog-post-new_component, while a change to monolithic.src.main.frontend.src.app.blog-posts.blog-post-new.blog-post-new_component can't break monolithic.src.main.frontend.src.app.blog-posts.shared.blog-posts_service.
- Position
- Below the diagonal: monolithic.src.main.frontend.src.app.blog-posts.blog-post-new.blog-post-new_component uses a module listed above it, which is the healthy direction.
28→7 monolithic.src.main.frontend.src.app.blog-posts.blog-post.blog-post_component uses monolithic.src.main.frontend.src.app.blog-posts.shared.blog-post_model✕
- Connections
- 1 pair of types, where a type in monolithic.src.main.frontend.src.app.blog-posts.blog-post.blog-post_component uses a type in monolithic.src.main.frontend.src.app.blog-posts.shared.blog-post_model.
- The types involved
monolithic.src.main.frontend.src.app.blog-posts.blog-post.blog-post_component.BlogPostComponent→monolithic.src.main.frontend.src.app.blog-posts.shared.blog-post_model.BlogPostModel
- Direction
- monolithic.src.main.frontend.src.app.blog-posts.blog-post.blog-post_component uses monolithic.src.main.frontend.src.app.blog-posts.shared.blog-post_model, so a change to monolithic.src.main.frontend.src.app.blog-posts.shared.blog-post_model can break monolithic.src.main.frontend.src.app.blog-posts.blog-post.blog-post_component, while a change to monolithic.src.main.frontend.src.app.blog-posts.blog-post.blog-post_component can't break monolithic.src.main.frontend.src.app.blog-posts.shared.blog-post_model.
- Position
- Below the diagonal: monolithic.src.main.frontend.src.app.blog-posts.blog-post.blog-post_component uses a module listed above it, which is the healthy direction.
28→16 monolithic.src.main.frontend.src.app.blog-posts.blog-post.blog-post_component uses monolithic.src.main.frontend.src.app.blog-posts.shared.blog-posts_service✕
- Connections
- 1 pair of types, where a type in monolithic.src.main.frontend.src.app.blog-posts.blog-post.blog-post_component uses a type in monolithic.src.main.frontend.src.app.blog-posts.shared.blog-posts_service.
- The types involved
monolithic.src.main.frontend.src.app.blog-posts.blog-post.blog-post_component.BlogPostComponent→monolithic.src.main.frontend.src.app.blog-posts.shared.blog-posts_service.BlogPostsService
- Direction
- monolithic.src.main.frontend.src.app.blog-posts.blog-post.blog-post_component uses monolithic.src.main.frontend.src.app.blog-posts.shared.blog-posts_service, so a change to monolithic.src.main.frontend.src.app.blog-posts.shared.blog-posts_service can break monolithic.src.main.frontend.src.app.blog-posts.blog-post.blog-post_component, while a change to monolithic.src.main.frontend.src.app.blog-posts.blog-post.blog-post_component can't break monolithic.src.main.frontend.src.app.blog-posts.shared.blog-posts_service.
- Position
- Below the diagonal: monolithic.src.main.frontend.src.app.blog-posts.blog-post.blog-post_component uses a module listed above it, which is the healthy direction.
29→10 monolithic.src.main.frontend.src.app.projects.project-list.project-list_component uses monolithic.src.main.frontend.src.app.shared.event-manager_service✕
- Connections
- 1 pair of types, where a type in monolithic.src.main.frontend.src.app.projects.project-list.project-list_component uses a type in monolithic.src.main.frontend.src.app.shared.event-manager_service.
- The types involved
monolithic.src.main.frontend.src.app.projects.project-list.project-list_component.ProjectListComponent→monolithic.src.main.frontend.src.app.shared.event-manager_service.EventManager
- Direction
- monolithic.src.main.frontend.src.app.projects.project-list.project-list_component uses monolithic.src.main.frontend.src.app.shared.event-manager_service, so a change to monolithic.src.main.frontend.src.app.shared.event-manager_service can break monolithic.src.main.frontend.src.app.projects.project-list.project-list_component, while a change to monolithic.src.main.frontend.src.app.projects.project-list.project-list_component can't break monolithic.src.main.frontend.src.app.shared.event-manager_service.
- Position
- Below the diagonal: monolithic.src.main.frontend.src.app.projects.project-list.project-list_component uses a module listed above it, which is the healthy direction.
29→17 monolithic.src.main.frontend.src.app.projects.project-list.project-list_component uses monolithic.src.main.frontend.src.app.projects.shared.projects_service✕
- Connections
- 1 pair of types, where a type in monolithic.src.main.frontend.src.app.projects.project-list.project-list_component uses a type in monolithic.src.main.frontend.src.app.projects.shared.projects_service.
- The types involved
monolithic.src.main.frontend.src.app.projects.project-list.project-list_component.ProjectListComponent→monolithic.src.main.frontend.src.app.projects.shared.projects_service.ProjectsService
- Direction
- monolithic.src.main.frontend.src.app.projects.project-list.project-list_component uses monolithic.src.main.frontend.src.app.projects.shared.projects_service, so a change to monolithic.src.main.frontend.src.app.projects.shared.projects_service can break monolithic.src.main.frontend.src.app.projects.project-list.project-list_component, while a change to monolithic.src.main.frontend.src.app.projects.project-list.project-list_component can't break monolithic.src.main.frontend.src.app.projects.shared.projects_service.
- Position
- Below the diagonal: monolithic.src.main.frontend.src.app.projects.project-list.project-list_component uses a module listed above it, which is the healthy direction.
30→10 monolithic.src.main.frontend.src.app.projects.project-new.project-new_component uses monolithic.src.main.frontend.src.app.shared.event-manager_service✕
- Connections
- 1 pair of types, where a type in monolithic.src.main.frontend.src.app.projects.project-new.project-new_component uses a type in monolithic.src.main.frontend.src.app.shared.event-manager_service.
- The types involved
monolithic.src.main.frontend.src.app.projects.project-new.project-new_component.ProjectNewComponent→monolithic.src.main.frontend.src.app.shared.event-manager_service.EventManager
- Direction
- monolithic.src.main.frontend.src.app.projects.project-new.project-new_component uses monolithic.src.main.frontend.src.app.shared.event-manager_service, so a change to monolithic.src.main.frontend.src.app.shared.event-manager_service can break monolithic.src.main.frontend.src.app.projects.project-new.project-new_component, while a change to monolithic.src.main.frontend.src.app.projects.project-new.project-new_component can't break monolithic.src.main.frontend.src.app.shared.event-manager_service.
- Position
- Below the diagonal: monolithic.src.main.frontend.src.app.projects.project-new.project-new_component uses a module listed above it, which is the healthy direction.
30→17 monolithic.src.main.frontend.src.app.projects.project-new.project-new_component uses monolithic.src.main.frontend.src.app.projects.shared.projects_service✕
- Connections
- 1 pair of types, where a type in monolithic.src.main.frontend.src.app.projects.project-new.project-new_component uses a type in monolithic.src.main.frontend.src.app.projects.shared.projects_service.
- The types involved
monolithic.src.main.frontend.src.app.projects.project-new.project-new_component.ProjectNewComponent→monolithic.src.main.frontend.src.app.projects.shared.projects_service.ProjectsService
- Direction
- monolithic.src.main.frontend.src.app.projects.project-new.project-new_component uses monolithic.src.main.frontend.src.app.projects.shared.projects_service, so a change to monolithic.src.main.frontend.src.app.projects.shared.projects_service can break monolithic.src.main.frontend.src.app.projects.project-new.project-new_component, while a change to monolithic.src.main.frontend.src.app.projects.project-new.project-new_component can't break monolithic.src.main.frontend.src.app.projects.shared.projects_service.
- Position
- Below the diagonal: monolithic.src.main.frontend.src.app.projects.project-new.project-new_component uses a module listed above it, which is the healthy direction.
31→8 monolithic.src.main.frontend.src.app.projects.project.project_component uses monolithic.src.main.frontend.src.app.projects.shared.project_model✕
- Connections
- 1 pair of types, where a type in monolithic.src.main.frontend.src.app.projects.project.project_component uses a type in monolithic.src.main.frontend.src.app.projects.shared.project_model.
- The types involved
monolithic.src.main.frontend.src.app.projects.project.project_component.ProjectComponent→monolithic.src.main.frontend.src.app.projects.shared.project_model.ProjectModel
- Direction
- monolithic.src.main.frontend.src.app.projects.project.project_component uses monolithic.src.main.frontend.src.app.projects.shared.project_model, so a change to monolithic.src.main.frontend.src.app.projects.shared.project_model can break monolithic.src.main.frontend.src.app.projects.project.project_component, while a change to monolithic.src.main.frontend.src.app.projects.project.project_component can't break monolithic.src.main.frontend.src.app.projects.shared.project_model.
- Position
- Below the diagonal: monolithic.src.main.frontend.src.app.projects.project.project_component uses a module listed above it, which is the healthy direction.
31→17 monolithic.src.main.frontend.src.app.projects.project.project_component uses monolithic.src.main.frontend.src.app.projects.shared.projects_service✕
- Connections
- 1 pair of types, where a type in monolithic.src.main.frontend.src.app.projects.project.project_component uses a type in monolithic.src.main.frontend.src.app.projects.shared.projects_service.
- The types involved
monolithic.src.main.frontend.src.app.projects.project.project_component.ProjectComponent→monolithic.src.main.frontend.src.app.projects.shared.projects_service.ProjectsService
- Direction
- monolithic.src.main.frontend.src.app.projects.project.project_component uses monolithic.src.main.frontend.src.app.projects.shared.projects_service, so a change to monolithic.src.main.frontend.src.app.projects.shared.projects_service can break monolithic.src.main.frontend.src.app.projects.project.project_component, while a change to monolithic.src.main.frontend.src.app.projects.project.project_component can't break monolithic.src.main.frontend.src.app.projects.shared.projects_service.
- Position
- Below the diagonal: monolithic.src.main.frontend.src.app.projects.project.project_component uses a module listed above it, which is the healthy direction.
32→15 com.idugalic.apigateway.handler uses com.idugalic.common.event✕
- Connections
- 1 pair of types, where a type in com.idugalic.apigateway.handler uses a type in com.idugalic.common.event.
- The types involved
com.idugalic.apigateway.handler.EventLoggingHandler→com.idugalic.common.event.AuditableAbstractEvent
- Direction
- com.idugalic.apigateway.handler uses com.idugalic.common.event, so a change to com.idugalic.common.event can break com.idugalic.apigateway.handler, while a change to com.idugalic.apigateway.handler can't break com.idugalic.common.event.
- Position
- Below the diagonal: com.idugalic.apigateway.handler uses a module listed above it, which is the healthy direction.
32→24 com.idugalic.apigateway.handler uses com.idugalic.common.blog.event✕
- Connections
- 2 pairs of types, where a type in com.idugalic.apigateway.handler uses a type in com.idugalic.common.blog.event.
- The types involved
com.idugalic.apigateway.handler.EventLoggingHandler→com.idugalic.common.blog.event.BlogPostCreatedEventcom.idugalic.apigateway.handler.EventLoggingHandler→com.idugalic.common.blog.event.BlogPostPublishedEvent
- Direction
- com.idugalic.apigateway.handler uses com.idugalic.common.blog.event, so a change to com.idugalic.common.blog.event can break com.idugalic.apigateway.handler, while a change to com.idugalic.apigateway.handler can't break com.idugalic.common.blog.event.
- Position
- Below the diagonal: com.idugalic.apigateway.handler uses a module listed above it, which is the healthy direction.
32→25 com.idugalic.apigateway.handler uses com.idugalic.common.project.event✕
- Connections
- 2 pairs of types, where a type in com.idugalic.apigateway.handler uses a type in com.idugalic.common.project.event.
- The types involved
com.idugalic.apigateway.handler.EventLoggingHandler→com.idugalic.common.project.event.ProjectCreatedEventcom.idugalic.apigateway.handler.EventLoggingHandler→com.idugalic.common.project.event.ProjectUpdatedEvent
- Direction
- com.idugalic.apigateway.handler uses com.idugalic.common.project.event, so a change to com.idugalic.common.project.event can break com.idugalic.apigateway.handler, while a change to com.idugalic.apigateway.handler can't break com.idugalic.common.project.event.
- Position
- Below the diagonal: com.idugalic.apigateway.handler uses a module listed above it, which is the healthy direction.
33→5 com.idugalic.commandside.blog.aggregate uses com.idugalic.common.blog.model✕
- Connections
- 1 pair of types, where a type in com.idugalic.commandside.blog.aggregate uses a type in com.idugalic.common.blog.model.
- The types involved
com.idugalic.commandside.blog.aggregate.BlogPostAggregate→com.idugalic.common.blog.model.BlogPostCategory
- Direction
- com.idugalic.commandside.blog.aggregate uses com.idugalic.common.blog.model, so a change to com.idugalic.common.blog.model can break com.idugalic.commandside.blog.aggregate, while a change to com.idugalic.commandside.blog.aggregate can't break com.idugalic.common.blog.model.
- Position
- Below the diagonal: com.idugalic.commandside.blog.aggregate uses a module listed above it, which is the healthy direction.
33→22 com.idugalic.commandside.blog.aggregate uses com.idugalic.commandside.blog.command✕
- Connections
- 2 pairs of types, where a type in com.idugalic.commandside.blog.aggregate uses a type in com.idugalic.commandside.blog.command.
- The types involved
com.idugalic.commandside.blog.aggregate.BlogPostAggregate→com.idugalic.commandside.blog.command.CreateBlogPostCommandcom.idugalic.commandside.blog.aggregate.BlogPostAggregate→com.idugalic.commandside.blog.command.PublishBlogPostCommand
- Direction
- com.idugalic.commandside.blog.aggregate uses com.idugalic.commandside.blog.command, so a change to com.idugalic.commandside.blog.command can break com.idugalic.commandside.blog.aggregate, while a change to com.idugalic.commandside.blog.aggregate can't break com.idugalic.commandside.blog.command.
- Position
- Below the diagonal: com.idugalic.commandside.blog.aggregate uses a module listed above it, which is the healthy direction.
33→24 com.idugalic.commandside.blog.aggregate uses com.idugalic.common.blog.event✕
- Connections
- 2 pairs of types, where a type in com.idugalic.commandside.blog.aggregate uses a type in com.idugalic.common.blog.event.
- The types involved
com.idugalic.commandside.blog.aggregate.BlogPostAggregate→com.idugalic.common.blog.event.BlogPostCreatedEventcom.idugalic.commandside.blog.aggregate.BlogPostAggregate→com.idugalic.common.blog.event.BlogPostPublishedEvent
- Direction
- com.idugalic.commandside.blog.aggregate uses com.idugalic.common.blog.event, so a change to com.idugalic.common.blog.event can break com.idugalic.commandside.blog.aggregate, while a change to com.idugalic.commandside.blog.aggregate can't break com.idugalic.common.blog.event.
- Position
- Below the diagonal: com.idugalic.commandside.blog.aggregate uses a module listed above it, which is the healthy direction.
34→23 com.idugalic.commandside.project.aggregate uses com.idugalic.commandside.project.command✕
- Connections
- 2 pairs of types, where a type in com.idugalic.commandside.project.aggregate uses a type in com.idugalic.commandside.project.command.
- The types involved
com.idugalic.commandside.project.aggregate.ProjectAggregate→com.idugalic.commandside.project.command.CreateProjectCommandcom.idugalic.commandside.project.aggregate.ProjectAggregate→com.idugalic.commandside.project.command.UpdateProjectCommand
- Direction
- com.idugalic.commandside.project.aggregate uses com.idugalic.commandside.project.command, so a change to com.idugalic.commandside.project.command can break com.idugalic.commandside.project.aggregate, while a change to com.idugalic.commandside.project.aggregate can't break com.idugalic.commandside.project.command.
- Position
- Below the diagonal: com.idugalic.commandside.project.aggregate uses a module listed above it, which is the healthy direction.
34→25 com.idugalic.commandside.project.aggregate uses com.idugalic.common.project.event✕
- Connections
- 2 pairs of types, where a type in com.idugalic.commandside.project.aggregate uses a type in com.idugalic.common.project.event.
- The types involved
com.idugalic.commandside.project.aggregate.ProjectAggregate→com.idugalic.common.project.event.ProjectCreatedEventcom.idugalic.commandside.project.aggregate.ProjectAggregate→com.idugalic.common.project.event.ProjectUpdatedEvent
- Direction
- com.idugalic.commandside.project.aggregate uses com.idugalic.common.project.event, so a change to com.idugalic.common.project.event can break com.idugalic.commandside.project.aggregate, while a change to com.idugalic.commandside.project.aggregate can't break com.idugalic.common.project.event.
- Position
- Below the diagonal: com.idugalic.commandside.project.aggregate uses a module listed above it, which is the healthy direction.
35→5 com.idugalic.queryside.blog.domain uses com.idugalic.common.blog.model✕
- Connections
- 1 pair of types, where a type in com.idugalic.queryside.blog.domain uses a type in com.idugalic.common.blog.model.
- The types involved
com.idugalic.queryside.blog.domain.BlogPost→com.idugalic.common.blog.model.BlogPostCategory
- Direction
- com.idugalic.queryside.blog.domain uses com.idugalic.common.blog.model, so a change to com.idugalic.common.blog.model can break com.idugalic.queryside.blog.domain, while a change to com.idugalic.queryside.blog.domain can't break com.idugalic.common.blog.model.
- Position
- Below the diagonal: com.idugalic.queryside.blog.domain uses a module listed above it, which is the healthy direction.
35→24 com.idugalic.queryside.blog.domain uses com.idugalic.common.blog.event✕
- Connections
- 1 pair of types, where a type in com.idugalic.queryside.blog.domain uses a type in com.idugalic.common.blog.event.
- The types involved
com.idugalic.queryside.blog.domain.BlogPost→com.idugalic.common.blog.event.BlogPostCreatedEvent
- Direction
- com.idugalic.queryside.blog.domain uses com.idugalic.common.blog.event, so a change to com.idugalic.common.blog.event can break com.idugalic.queryside.blog.domain, while a change to com.idugalic.queryside.blog.domain can't break com.idugalic.common.blog.event.
- Position
- Below the diagonal: com.idugalic.queryside.blog.domain uses a module listed above it, which is the healthy direction.
36→25 com.idugalic.queryside.project.domain uses com.idugalic.common.project.event✕
- Connections
- 1 pair of types, where a type in com.idugalic.queryside.project.domain uses a type in com.idugalic.common.project.event.
- The types involved
com.idugalic.queryside.project.domain.Project→com.idugalic.common.project.event.ProjectCreatedEvent
- Direction
- com.idugalic.queryside.project.domain uses com.idugalic.common.project.event, so a change to com.idugalic.common.project.event can break com.idugalic.queryside.project.domain, while a change to com.idugalic.queryside.project.domain can't break com.idugalic.common.project.event.
- Position
- Below the diagonal: com.idugalic.queryside.project.domain uses a module listed above it, which is the healthy direction.
37→5 com.idugalic.queryside.blog.repository uses com.idugalic.common.blog.model✕
- Connections
- 1 pair of types, where a type in com.idugalic.queryside.blog.repository uses a type in com.idugalic.common.blog.model.
- The types involved
com.idugalic.queryside.blog.repository.BlogPostRepository→com.idugalic.common.blog.model.BlogPostCategory
- Direction
- com.idugalic.queryside.blog.repository uses com.idugalic.common.blog.model, so a change to com.idugalic.common.blog.model can break com.idugalic.queryside.blog.repository, while a change to com.idugalic.queryside.blog.repository can't break com.idugalic.common.blog.model.
- Position
- Below the diagonal: com.idugalic.queryside.blog.repository uses a module listed above it, which is the healthy direction.
37→35 com.idugalic.queryside.blog.repository uses com.idugalic.queryside.blog.domain✕
- Connections
- 2 pairs of types, where a type in com.idugalic.queryside.blog.repository uses a type in com.idugalic.queryside.blog.domain.
- The types involved
com.idugalic.queryside.blog.repository.BlogPostRepository→com.idugalic.queryside.blog.domain.BlogPostcom.idugalic.queryside.blog.repository.ReadOnlyPagingAndSortingRepository→com.idugalic.queryside.blog.domain.BlogPost
- Direction
- com.idugalic.queryside.blog.repository uses com.idugalic.queryside.blog.domain, so a change to com.idugalic.queryside.blog.domain can break com.idugalic.queryside.blog.repository, while a change to com.idugalic.queryside.blog.repository can't break com.idugalic.queryside.blog.domain.
- Position
- Below the diagonal: com.idugalic.queryside.blog.repository uses a module listed above it, which is the healthy direction.
38→36 com.idugalic.queryside.project.repository uses com.idugalic.queryside.project.domain✕
- Connections
- 1 pair of types, where a type in com.idugalic.queryside.project.repository uses a type in com.idugalic.queryside.project.domain.
- The types involved
com.idugalic.queryside.project.repository.ReadOnlyPagingAndSortingRepository→com.idugalic.queryside.project.domain.Project
- Direction
- com.idugalic.queryside.project.repository uses com.idugalic.queryside.project.domain, so a change to com.idugalic.queryside.project.domain can break com.idugalic.queryside.project.repository, while a change to com.idugalic.queryside.project.repository can't break com.idugalic.queryside.project.domain.
- Position
- Below the diagonal: com.idugalic.queryside.project.repository uses a module listed above it, which is the healthy direction.
39→24 com.idugalic.queryside.blog.handler uses com.idugalic.common.blog.event✕
- Connections
- 2 pairs of types, where a type in com.idugalic.queryside.blog.handler uses a type in com.idugalic.common.blog.event.
- The types involved
com.idugalic.queryside.blog.handler.BlogPostViewEventHandler→com.idugalic.common.blog.event.BlogPostCreatedEventcom.idugalic.queryside.blog.handler.BlogPostViewEventHandler→com.idugalic.common.blog.event.BlogPostPublishedEvent
- Direction
- com.idugalic.queryside.blog.handler uses com.idugalic.common.blog.event, so a change to com.idugalic.common.blog.event can break com.idugalic.queryside.blog.handler, while a change to com.idugalic.queryside.blog.handler can't break com.idugalic.common.blog.event.
- Position
- Below the diagonal: com.idugalic.queryside.blog.handler uses a module listed above it, which is the healthy direction.
39→37 com.idugalic.queryside.blog.handler uses com.idugalic.queryside.blog.repository✕
- Connections
- 1 pair of types, where a type in com.idugalic.queryside.blog.handler uses a type in com.idugalic.queryside.blog.repository.
- The types involved
com.idugalic.queryside.blog.handler.BlogPostViewEventHandler→com.idugalic.queryside.blog.repository.BlogPostRepository
- Direction
- com.idugalic.queryside.blog.handler uses com.idugalic.queryside.blog.repository, so a change to com.idugalic.queryside.blog.repository can break com.idugalic.queryside.blog.handler, while a change to com.idugalic.queryside.blog.handler can't break com.idugalic.queryside.blog.repository.
- Position
- Below the diagonal: com.idugalic.queryside.blog.handler uses a module listed above it, which is the healthy direction.
40→25 com.idugalic.queryside.project.handler uses com.idugalic.common.project.event✕
- Connections
- 1 pair of types, where a type in com.idugalic.queryside.project.handler uses a type in com.idugalic.common.project.event.
- The types involved
com.idugalic.queryside.project.handler.ProjectViewEventHandler→com.idugalic.common.project.event.ProjectCreatedEvent
- Direction
- com.idugalic.queryside.project.handler uses com.idugalic.common.project.event, so a change to com.idugalic.common.project.event can break com.idugalic.queryside.project.handler, while a change to com.idugalic.queryside.project.handler can't break com.idugalic.common.project.event.
- Position
- Below the diagonal: com.idugalic.queryside.project.handler uses a module listed above it, which is the healthy direction.
40→38 com.idugalic.queryside.project.handler uses com.idugalic.queryside.project.repository✕
- Connections
- 1 pair of types, where a type in com.idugalic.queryside.project.handler uses a type in com.idugalic.queryside.project.repository.
- The types involved
com.idugalic.queryside.project.handler.ProjectViewEventHandler→com.idugalic.queryside.project.repository.ProjectRepository
- Direction
- com.idugalic.queryside.project.handler uses com.idugalic.queryside.project.repository, so a change to com.idugalic.queryside.project.repository can break com.idugalic.queryside.project.handler, while a change to com.idugalic.queryside.project.handler can't break com.idugalic.queryside.project.repository.
- Position
- Below the diagonal: com.idugalic.queryside.project.handler uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
At a glance — Domain Modelling
At a glance — Event Sourcing
At a glance — Accessibility
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A02:2025 — Security Misconfiguration | 76 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 55 | High / Critical |
| A05:2025 — Injection | 6 | High / Critical |
| A07:2025 — Authentication Failures | 2 | High / Critical |
Roadmap
Top priorities: Resolve the 1 Leaked secret finding(s) in Secret Scanning — start with REDACTED; 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; Resolve the 1 No ADRs found finding(s) in ADR Quality.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 1 Leaked secret finding(s) in Secret Scanning — start with REDACTED. | +6.5 pts | Low | Secret Scanning |
| 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. | +5.6 pts | Medium | Security & performance tooling |
| Resolve the 1 No ADRs found finding(s) in ADR Quality. | +2.5 pts | Low | ADR Quality |
| Resolve the 19 Orphaned file finding(s) in Knowledge Freshness — start with RestResponseEntityExceptionHandler.java (3), RabbitConfiguration.java (3), ProjectRelease.java. | +2.5 pts | Medium | Knowledge Freshness |
| 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. | +2.1 pts | Medium | Architecture documentation |
| Give every control a programmatic label (a <label for> / wrapping <label> / aria-label) and every button text — a placeholder is not a label. | +1.8 pts | Medium | Forms & labels |
| Add tests that import the unreached modules (directly or through their public entry). | +1.8 pts | Medium | Test Coverage |
| Enforce accessibility in the toolchain: add @angular-eslint/eslint-plugin-template (a11y rules), then assert with your test runner's axe binding (jest-axe, vitest-axe, cypress-axe or @axe-core/playwright) in tests, then gate axe/pa11y/Lighthouse in CI. | +1.6 pts | Medium | A11y enforcement |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 0.0 | Slop | Dependency Vulnerabilities: Critical CVE: REDACTED |
| REDACTED | 0.1 | Slop | Dependency Vulnerabilities: Critical CVE: REDACTED |
| REDACTED | 1.4 | Slop | Dependency Vulnerabilities: Critical CVE: REDACTED |
| REDACTED | 2.1 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.3 | Slop | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 2.3 | Slop | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 3.9 | Slop | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 3.9 | Slop | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 3.9 | Slop | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 3.9 | Slop | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 3.9 | Slop | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 3.9 | Slop | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 3.9 | Slop | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 3.9 | Slop | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 3.9 | Slop | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 4.1 | Mixed | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 4.1 | Mixed | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 4.4 | Mixed | Secret Scanning: Leaked secret: REDACTED |
| REDACTED | 5.1 | Mixed | Dependency Vulnerabilities: High CVE: REDACTED |
| command-side-blog-service/src/main/java/com/idugalic/commandside/blog/RestResponseEntityExceptionHandler.java | 6.0 | Mixed | Explicit Debt: TodoComment |
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 87 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 — 87 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, 243 of 257 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: the JavaScript/TypeScript half could not be measured — the JavaScript/TypeScript suite(s) run through a browser-driven runner the coverage collector does not drive — monolithic/src/main/frontend/ (karma) — a gap in the analyzer, not something this repository is missing. Coverage is excluded from the score rather than counted as a near-zero. This is OUR limitation, not a defect in the repo. In the meantime, commit (or publish into the working tree) the lcov/Cobertura report your CI produces and the real number is read on the next scan. You can widen what we reach: optional: commit the lcov/Cobertura report your CI produces, and the real number is read on the next scan.
- D10 Test 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. The 15 test(s) behind this row are the ones the code-model census could read, and this repository also carries at least 11 test source file(s) (.ts) that it cannot: it reads the test types the .java frontend declared, so a suite in any other language is invisible to it. Skipped tests, zero-assertion tests and the other quality signals on this row are UNMEASURED in that suite — their absence from the counts above is a gap in this analyzer's language coverage, not a finding that those tests are sound.
- 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 reliability NOT SCORED: this repository's production source includes .ts, and the built-in reliability runner cannot re-run the .ts test suite(s) — so reliability was not measured for the repository as a whole. The Java/Kotlin (repository root, Maven): measured (0 flaky) suite(s) did re-run, and came back with 0 flaky across 1 measured tier(s) — but that is a figure for one half of the product, and we do not publish a partial one as if it were complete. This is OUR limitation, not a defect in the repo — test reliability is excluded from the score rather than counted.
- D12 Dependency Hygiene — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This repository's dependency manifests WERE read and their pinning discipline assessed; what went unanswered is the currency half, because repo.spring.io — the registry that answers it — was asked and did not reply (the build stopped because repo.spring.io, a repository this project declares, refused it with HTTP 403 — what this scan's egress allowlist returns for a host that is not on it; 11 dependencies were resolved and graded first, but the graph is partial so the result is reported and not scored). This is OUR side and it is an ENVIRONMENT fault, not a missing collector: the collector exists and ran. An HTTP 403 here is what this scan's egress allowlist returns for a host that is not on it, so the remedy is to add repo.spring.io to the allowlist and re-run — not to build anything.
- D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Single-maintainer repository — bus factor is not applicable (4 contributor(s) across 270 commit(s) sampled, automation and bot accounts excluded). One of them holds 97% of the history; the other 3 hold 1% each on average, below the 5% at which there is somebody to hand the work to. That is a single maintainer with drive-by contributors, not a team whose knowledge has concentrated — so the bus factor is not applicable and there is nothing here for the owner to act on.
- D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
- D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D21's deterministic naming rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. Until then its declarations carry no naming verdict this run — this says nothing about whether its names are consistent.
- D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22 identifies the intentionally-exposed surface from `IsPackable` and `.Contracts` project names, MSBuild conventions read off the loaded project set. This target exposed no such projects, so the probe never ran; this says nothing about whether the repository has a public API. This repository commits no C#/VB source at all, so there was never an MSBuild project set to read these conventions off. That is OUR side and it is an ADMISSION gap, not an environment fault: no published-package marker D22 reads admitted any project here. D22 DOES collect the public API of every language in this tree, and admits a project only when its manifest makes that ecosystem's publication act in a form the marker recognises — so what is missing is not a collector but an admission rule for the publication act this repository makes, if it makes one. The remedy is a better discriminator for that marker — not a collector, and no change to the scan image can close it. The marker's rules are measured to refuse applications, so one refused repository is the rule working as calibrated; several are the evidence that it is too strict. For npm the surface is what a published package.json's entry points (exports, main, module, types) export, followed through the source; an entry that names build output the tree does not commit (dist/, build/) is not followed back to source, because only a tsconfig outDir/rootDir pair states that mapping and a bundler's input lives in executable configuration this engine does not evaluate.
- D24 Comment Value — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Each source language's comment syntax, and the code a comment annotates in it, needs its own proof before D24 judges it. Until then those comments are left unread, not counted as clean.
- D27 Navigability — 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. Tracing effort is measured over resolved call sites, and all 101 sampled here came from .java files. This repository's .ts source is a material share of its production lines and contributed none, so the score above is a verdict about the part that was read. Not a finding that the unread half navigates well — it is unmeasured.
- D30 Dependency Vulnerabilities — 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. Osv-scanner resolved ch.qos.logback:logback-classic 1.1.5 in adminserver/pom.xml, but the org.springframework.boot:spring-boot-dependencies:1.5.22.RELEASE BOM that file imports manages it at 1.1.11 — the scanner resolved this pom without its BOM (it does so silently when the BOM cannot be fetched), so the 250 advisory row(s) it raised against this file's graph describe versions the build does not use and were withheld. 2 of 3 declared ecosystem(s) (npm,osv) WERE scanned and every vulnerability they reported is included in this result; Maven (adminserver/pom.xml) was not, so this dimension's score covers less than the dependency surface this repository declares, and nothing here is evidence that Maven (adminserver/pom.xml) is free of known-vulnerable dependencies.
- 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 REDACTED (REDACTED). the image ran but published no HTTP port — nothing to crawl (EXPOSE the web port to unlock runtime evidence).
- C1 Data Protection — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These personal data controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks personal data controls.
- C2 Access Controls — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These authorization controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks authorization controls.
- C3 Audit Trail — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These audit controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks audit controls.
- C4 Data Retention — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These retention controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks retention controls.
- C5 Data-Subject Rights — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These data-subject rights controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks data-subject rights controls.
- DM8 Value-object opportunities — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check finds primitive parameters that travel together through several signatures of the domain (a missing value object). Its deterministic rule has not yet shown 95 % precision on adjudicated rows, so the clumps it finds are counted here and not published as findings, and the card carries no score. That is a limit of the analyzer, not a finding about your code.
- ED5 Idempotency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check decides whether a handler's mutation is safe to re-run by recognising its persistence writes (a database save, a repository write, an event publish) and its guards. Those markers are .NET member names, so in this repository's language a write such as `repository.save(order)` is not recognised and a same-named call on an unrelated library type could be. The handlers were found; their idempotency was neither confirmed nor ruled out.
- GD1 Unfinished & placeholder code — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, F#, JavaScript/TypeScript, Dart, Ruby and Scala source only, and this repository's Java is most of its product and is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- 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.
- P8 Schema migrations — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. The schema may be created by a runner, a deploy script or a config file outside what this check reads, so an absence here is our blind spot rather than a missing migration strategy. The card abstains instead of scoring. You can widen what we reach: if the schema is created and evolved by a tool this check does not name, naming it lets us teach the detector to read it.
- 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.
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.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
- D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
- D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a REDACTED (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- AC2 Forms & labels: Label association is read from static markup — a label wired up at runtime (JS-set aria-labelledby, framework-injected ids) reads as missing, a present label says nothing about whether its text is correct. A known UI-library field component (e.g. a JSX <TextField>) is now checked conservatively — flagged only when it carries NO label/aria-label/aria-labelledby/id/name — but wrapper/context-labelled libraries (Chakra/Radix FormControl+FormLabel) aren't statically visible (possible false positive) and non-JSX lowercased components are still skipped. A click handler on a plain element is now asked for a name too (it is a control the author declared), but the subtree test that answers it is deliberately generous: any DYNAMIC text expression in the subtree counts as a name, so an icon chosen by a ternary ({cond ? <IconA/> : <IconB/>}) reads as named, and a glyph component from a library the icon-import list does not know still names its parent. A clean result is "no unlabelled control found", not a labelling proof.
- AC3 Page structure: Page structure is read from the static markup tree — landmarks, headings and lang injected at runtime aren't seen, heading ORDER is checked structurally (not against the rendered visual hierarchy), and lang/title/main fire only on full documents, never partials, and the data-table check sees header-cell presence (a <th> exists), not whether each header correctly associates with its cells. Static readiness, not conformance.
- AC5 ARIA correctness: ARIA correctness is checked against the static role/attribute shape — roles/attributes set dynamically aren't seen, a valid role says nothing about whether it matches the element's real behaviour, and required-state checks are suppressed when a JSX spread could supply them. The two-branch toggle check (a control whose state is conveyed only by which of two mutually exclusive branches renders) reads CONDITIONALS THAT ARE ATTRIBUTES — Vue v-if/v-else/v-show and Alpine x-if/x-show — so the same toggle written as a Svelte {#if} block or a JSX ternary is control flow the markup model never projects as a branch and is not seen at all.
- AC6 Visual & motion safety: Contrast and motion safety are PARTIAL by construction — literal colours (hex/rgb/hsl/named) in inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS top-level declarations are read (same-rule/same-element colour+background pairs only); computed/runtime/theme colour, external-CDN stylesheets, CSS-in-JS dynamic (${…}) and nested-selector colours, cross-element pairs and image contrast stay out of reach, so a clean result is bounded by what the static CSS itself shows.
- AC7 A11y enforcement: Enforcement is scored from in-repo config/CI evidence only — an a11y gate enforced in external tooling with no in-repo trace can't be credited, and a configured linter is presence, not proof the rules actually run or block a merge.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- DM4 Rich vs anemic model: Behaviour is detected as state mutation inside a method body — a method that enforces an invariant by validating-and-throwing without mutating reads as a query, and mutation delegated through an interface the scan can't resolve isn't credited; entities with zero public properties still drop out of the population. It detects that state changes, not whether the rule is correct.
- DM6 Domain ↔ infrastructure boundary: Infrastructure reached through a hand-rolled wrapper, a domain-named facade, reflection, or a string-keyed service locator resolves to a non-infra type and isn't seen; the body scan is symbol resolution over syntax, not full dataflow. A clean result means "no resolved infra reference in a domain body", not a proof of purity.
- P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
- P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
Dimensions
D1 · Cyclomatic Complexity
0 method(s) exceeded the cyclomatic complexity threshold of 15.
D2 · Cognitive Complexity
0 method(s) exceeded the cognitive complexity threshold of 15.
D3 · God Classes
0 god class(es) detected.
D4 · Code Duplication
18 duplicated block group(s) detected. 2 of the 18 are in trees this repository does not ship — vendored, example/demo, project-template, fixture and benchmark code — and are ranked below the shipped groups rather than excluded from them: the duplication there is real and is still counted in this dimension's score. The dimensions that publish a production-file census leave those trees out of theirs, so this count is deliberately drawn over the wider population. Measured on part of this repository only: .ts (23% of production source) was not exposed to THIS dimension's token comparison and is not in this count; duplication there is measured by R10 Code Duplication, the frontend lens's card running the same clone algorithm over the JS/TS token stream.
What to do
- Resolve the 4 Duplicated block (5 lines × 3) finding(s) in Code Duplication — start with RestResponseEntityExceptionHandler.java (4). — One of this dimension's main actionable groups (4 warning-level).
- Resolve the 3 Duplicated block (6 lines × 2) finding(s) in Code Duplication — start with BlogPostAggregate.java, BlogController.java, DocumentationApplication.java. — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 1 Duplicated block (12 lines × 3) finding(s) in Code Duplication — start with Application.java. — One of this dimension's main actionable groups (1 warning-level).
- Enforce Code Duplication in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D5 · Coupling
20 production modules (Maven+npm), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; 2 module(s) off the main sequence.
D6 · Cohesion (LCOM4)
0 of 8 classes have LCOM4 above 3.
D9 · Test Distribution
27 test methods: 26 unit, 0 integration, 0 BDD, 1 e2e. The JavaScript/TypeScript suite contributes 12 `it`/`test` case(s) across 10 test file(s) declaring at least one beside 15 .NET test method(s); its tier split is read from package names and paths only.
D10 · Test Quality
0 skipped, 11 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 15 tests (1 harness-style project(s) excluded from the assertion penalty). Measured on the .java suite only — at least 11 test source file(s) (.ts) went unread, so its test quality is unmeasured and is not in these counts.
D13 · Secret Scanning
1 secret(s) detected.
What to do
- Resolve the 1 Leaked secret finding(s) in Secret Scanning — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- Enforce Secret Scanning in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D14 · License Compliance
0 of 8 declared JVM dependency artifact(s) use a banned license. Licences were resolved from the POMs Maven Central publishes, over the coordinates this repository's 20 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. 189 further coordinate(s) are declared with no version at the declaration site — inherited from a parent POM, a BOM or an unresolved Gradle version reference — and are NOT graded: this verdict covers what the checkout pins, not the full transitive graph.
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window.
D17 · Explicit Debt
8 deducted task-comment markers across 3990 LoC (0.1/KLoC) → score 9.7. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
What to do
- Resolve the 8 TodoComment finding(s) in Explicit Debt — start with RestResponseEntityExceptionHandler.java (6), BlogPost.java, EventLoggingHandler.java. — One of this dimension's main actionable groups (8 warning-level).
- Enforce Explicit Debt in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D19 · Documentation Quality
1 of 1 documentation facets pass in full. 5 document(s) read across 2 unit(s).
D20 · ADR Quality
No architecture decision records were found.
What to do
- Resolve the 1 No ADRs found finding(s) in ADR Quality. — One of this dimension's main actionable groups (1 recommendation-level).
D26 · Project Cohesion
0 of 20 build units (Maven, npm) flagged as possibly oversized/incoherent.
D27 · Navigability
56 % of calls cross a namespace and 3 % go through an interface, but 100 % of collaborators are co-located — so a call's collaborators sit together and tracing stays easy. Baseline: small — navigation cost is tolerated. Measured over the .java source only — this repository's .ts was not sampled for call sites, so this score covers part of the tree, not all of it.
D28 · Secrets (history)
1 finding(s): 0 critical, 1 high, 0 medium, 0 low.
What to do
- Resolve the 1 High secret finding(s) in Secrets (history) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
D29 · Static Analysis (SAST)
6 finding(s): 0 critical, 2 high, 4 medium, 0 low. 2 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.
What to do
- Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2). — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2). — One of this dimension's main actionable groups (2 warning-level).
- No action in Static Analysis (SAST) — all 2 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 (2 issue-level, 0 of them charged here).
D30 · Dependency Vulnerabilities
55 finding(s): 18 critical, 22 high, 13 medium, 2 low. Partial dependency scan: 2 of 3 declared ecosystem(s) were scanned (npm,osv), and the findings above are real and complete for them. Maven (adminserver/pom.xml) was not scanned (Maven (adminserver/pom.xml): osv-scanner resolved ch.qos.logback:logback-classic 1.1.5 in adminserver/pom.xml, but the org.springframework.boot:spring-boot-dependencies:1.5.22.RELEASE BOM that file imports manages it at 1.1.11 — the scanner resolved this pom without its BOM (it does so silently when the BOM cannot be fetched), so the 250 advisory row(s) it raised against this file's graph describe versions the build does not use and were withheld), so this is not the whole dependency surface and the result is reported at reduced confidence.
What to do
- Resolve the 22 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (22). — One of this dimension's main actionable groups (22 issue-level).
- Resolve the 18 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (18). — One of this dimension's main actionable groups (18 issue-level).
- Resolve the 13 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (13). — One of this dimension's main actionable groups (13 warning-level).
D31 · IaC & Container Security
76 finding(s): 0 critical, 32 high, 13 medium, 31 low.
What to do
- Resolve the 32 High IaC finding(s) in IaC & Container Security — start with REDACTED (11), REDACTED (10), REDACTED (10). — One of this dimension's main actionable groups (32 issue-level).
- Resolve the 31 Low IaC finding(s) in IaC & Container Security — start with REDACTED (31). — One of this dimension's main actionable groups (31 recommendation-level).
- Resolve the 13 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (11), REDACTED, REDACTED. — One of this dimension's main actionable groups (13 warning-level).
D34 · Knowledge Freshness
19 of 19 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is command-side-project/src/main/java/com/idugalic/commandside/project/aggregate/ProjectRelease.java. Counted over 19 of the 103 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
What to do
- Resolve the 19 Orphaned file finding(s) in Knowledge Freshness — start with RestResponseEntityExceptionHandler.java (3), RabbitConfiguration.java (3), ProjectRelease.java. — One of this dimension's main actionable groups (19 recommendation-level).
- Resolve the 1 Orphaned files with no living knowledge finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
D35 · Change Coupling
No strong hidden change-coupling between production files.
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 1 end-of-life framework(s), read from 1 platform declaration(s) and 35 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.
What to do
- Resolve the 1 End-of-life framework finding(s) in Platform End-of-Life — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
Frontend & cross-cutting dimensions
AC2 · Forms & labels
- This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label for>, a wrapping <label>, or aria-label. (×8) — monolithic/src/main/frontend/src/app/blog-posts/blog-post-new/blog-post-new.component.html:7, monolithic/src/main/frontend/src/app/blog-posts/blog-post-new/blog-post-new.component.html:10, monolithic/src/main/frontend/src/app/blog-posts/blog-post-new/blog-post-new.component.html:13, …
- This <label> has no for and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label for="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id. — monolithic/src/main/frontend/src/app/blog-posts/blog-post-new/blog-post-new.component.html:31
What to do
- Give every control a programmatic label (a <label for> / wrapping <label> / aria-label) and every button text — a placeholder is not a label.
AC3 · Page structure
- The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en"). (×3) — api-gateway/src/main/resources/static/socket/index.html:2, REDACTED:2, REDACTED:2
- No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>. (×3) — api-gateway/src/main/resources/static/socket/index.html:2, REDACTED:2, REDACTED:2
What to do
- Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh.
AC5 · ARIA correctness
AC6 · Visual & motion safety
AC7 · A11y enforcement
- No accessibility enforcement found — no a11y linter (@angular-eslint/eslint-plugin-template (a11y rules)) and no axe/pa11y/Lighthouse in tests or CI. Start with the linter to catch issues at author time. What was searched, so you can tell an absence from a miss: the 14 markup file(s) this pass actually assessed, the linter configuration checked in beside them, and this repository's test and CI files — matched by name against the accessibility checkers this dimension carries. An audit run outside the repository, a hosted scanner, or a check whose name is not one of those, is not seen here. — monolithic/src/main/frontend/package.json:35
What to do
- Enforce accessibility in the toolchain: add @angular-eslint/eslint-plugin-template (a11y rules), then assert with your test runner's axe binding (jest-axe, vitest-axe, cypress-axe or @axe-core/playwright) in tests, then gate axe/pa11y/Lighthouse in CI.
AX1 · Captive dependencies
AX10 · Code composition
AX2 · Stateful singletons
AX3 · Project dependency cycles
AX4 · Dependency direction
AX6 · Interface segregation
DM1 · Aggregate boundaries
DM10 · One transaction, one aggregate
DM11 · Constructible invalid state
- `Project`'s public constructor takes `id`, `name`, `repoUrl`, `siteUrl`, … as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `Project` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. — query-side-project/src/main/java/com/idugalic/queryside/project/domain/Project.java:41
- `BlogPost`'s public constructor takes `id`, `title`, `rawContent`, `renderContent`, … as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `BlogPost` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. — query-side-blog/src/main/java/com/idugalic/queryside/blog/domain/BlogPost.java:41
What to do
- Give each aggregate one way in that can refuse — a guarded constructor, value-object parameters that validate themselves, or a private constructor behind a factory that returns a failure.
DM12 · Ambient inputs in the domain
DM4 · Rich vs anemic model
DM5 · Encapsulated state
DM6 · Domain ↔ infrastructure boundary
DM7 · Repository granularity
- `ProjectRepository` is a repository over `Project`, which is an entity but not an aggregate root. Repositories should be per aggregate ROOT — loading/saving a child entity independently lets callers bypass the root's invariants. Access `Project` through its owning aggregate instead. — query-side-project/src/main/java/com/idugalic/queryside/project/repository/ProjectRepository.java:14
- `BlogPostRepository` is a repository over `BlogPost`, which is an entity but not an aggregate root. Repositories should be per aggregate ROOT — loading/saving a child entity independently lets callers bypass the root's invariants. Access `BlogPost` through its owning aggregate instead. — query-side-blog/src/main/java/com/idugalic/queryside/blog/repository/BlogPostRepository.java:21
What to do
- Define repositories per aggregate root and keep the query handle inside them; reach child entities through their root so invariants can't be bypassed.
DM9 · Scattered domain decisions
ES1 · Fold determinism
IC1 · Incompleteness & stubs
M1 · Documentation (README)
What to do
- Add a README to the 17 of 20 project(s) that lack one — worth up to 1.7 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 9/16 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `adminserver`, `authserver`, `circuit-breaker`, `configserver`, `query-side-blog-service` and 2 more.
What to do
- Extend structured logging to the remaining runnable modules so everything you run is diagnosable in production.
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 541 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. — REDACTED:9
- `monolithic/src/main/frontend/package.json` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`. — monolithic/src/main/frontend/package.json:15
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
- Deployment is orchestrated by compose, but no service declares a `healthcheck:` and nothing pins a previous image to fall back to — the runtime can tell that the container is up, not that it is serving, so a bad release is harder to detect and reverse.
What to do
- Add a `healthcheck:` to the served compose service — probing the endpoint it already answers on where it has one — with `depends_on: condition: service_healthy` on whatever waits for it, and keep the deployed image tag immutable and recorded so rolling back is re-pointing at the previous tag rather than rebuilding.
- Add an approval/environment gate (required reviewers / protection rules) before production promotion.
P6 · Release Hygiene
- No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
What to do
- Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.
R1 · Type Safety
What to do
- Migrate the remaining .js/.jsx files to TypeScript.
R10 · Code Duplication
- 5 duplicated blocks under monolithic/src/main/frontend/src/app/ have copies in at least two of the sibling directories blog-posts, projects — 4 of them are reported below, and 1 is counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 5 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 5 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 5 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — monolithic/src/main/frontend/src/app/blog-posts/blog-posts-routing.module.ts:10
- monolithic/src/main/frontend/src/app/blog-posts/blog-posts-routing.module.ts:10 · monolithic/src/main/frontend/src/app/projects/projects-routing.module.ts:10 — the 2 copies are spread across 2 files, and the CITED SPAN is a run of DECLARATIONS inside a construct — the members of a type, or the entries of an object or array literal — with no statement anywhere in it. Do not read this as an extract-a-helper row: nothing here executes, so there is no call site, and a call expression cannot stand where a member declaration or a literal's entry was. What repeats is a SHAPE, and which shape decides the move. Where the copies declare the same members, the repetition is a missing common ancestor: give it a base type, an interface both extend, a generic instantiated twice, or — where the copies are a literal's entries rather than a type's members — one shared constant each site spreads or refers to, so the set is written once. Where they declare DIFFERENT members and only the form is shared — a decorator and its options, an annotation, a registration table's keys — the form is prescribed by a framework or a schema rather than copied, and the only collapse available is to generate the declarations from that schema; where you do not own the generator, this is the cost of the framework and there is nothing to extract. Check which of the two it is before acting: these copies still drift apart the first time only one of them is edited, which is why the repetition is reported, but the sentence to act on is not the same in both cases. — monolithic/src/main/frontend/src/app/blog-posts/blog-posts-routing.module.ts:10
- monolithic/src/main/frontend/src/app/blog-posts/blog-post/blog-post.component.ts:11 · monolithic/src/main/frontend/src/app/projects/project/project.component.ts:11 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — monolithic/src/main/frontend/src/app/blog-posts/blog-post/blog-post.component.ts:11
- monolithic/src/main/frontend/src/app/blog-posts/shared/blog-posts.service.ts:9 · monolithic/src/main/frontend/src/app/projects/shared/projects.service.ts:9 — the two spans are one implementation copied and then locally edited — 210 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — monolithic/src/main/frontend/src/app/blog-posts/shared/blog-posts.service.ts:9
- monolithic/src/main/frontend/src/app/blog-posts/blog-post-new/blog-post-new.component.ts:43 · monolithic/src/main/frontend/src/app/projects/project-new/project-new.component.ts:39 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — monolithic/src/main/frontend/src/app/blog-posts/blog-post-new/blog-post-new.component.ts:43
What to do
- Act on each finding's own remediation rather than one rule: the move depends on what recurs. Where the copies are executable blocks, give the shared part one home and call it from each site; where they are declarations, a listing, a specialisation already delegating to its base, or one shape repeated per entity, there is no call site and the move is a shared type, a generated set or a factory — sometimes there is nothing to extract.
R11 · Import Boundaries
- monolithic/src/main/frontend/src/polyfills.ts:19 imports zone.js/dist/zone, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — monolithic/src/main/frontend/src/polyfills.ts:19
What to do
- Fix the listed violations: import through public entries (package exports / slice index), never reach into another layer or package's internals.
R2 · Cyclomatic Complexity
R3 · Large Files
R4 · Test Coverage
- No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one. (×16) — monolithic/src/main/frontend/src/app/shared/alert/alert.service.ts:1, monolithic/src/main/frontend/src/app/shared/interceptor/http.interceptor.ts:1, monolithic/src/main/frontend/src/app/shared/alert/alert-error.component.ts:1, …
What to do
- Add tests that import the unreached modules (directly or through their public entry).
R6 · Tooling
- test ✓ · lint ✓ · typecheck ✗ — read from this repository's package.json scripts and corroborated against its CI workflows. A script counts when its name or command matches the step: `test` for the suite, `lint` or `prettier` for linting, `typecheck`/`type-check`/`tsc` for type checking. ✗ therefore means no script or CI step under those names was found, NOT that the step is absent from your pipeline — a task invoked by a runner this check does not read, or named something else entirely, is not seen and is worth confirming before acting on a cross. A ✓ means the wiring is DECLARED — a script or CI step under those names exists. It is not a statement that the step passes, or that it runs at all: nothing here installs a dependency or executes a suite.
What to do
- Add `tsc --noEmit` as package.json scripts and run them in CI.
R7 · Dead Code
R8 · Dependency Hygiene
- Declared in monolithic/src/main/frontend/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it. (×3)
What to do
- Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.
R9 · Circular Imports
X1 · Async correctness
X12 · Unreachable branch
X13 · Undrained process stream
X14 · Bypassable address classification
X15 · Unvalidated length from an untrusted reader
X16 · Unfloored truncation loop
X17 · Uncapped recursion over a caller-supplied document
X18 · Disposal-pattern correctness
X19 · Unrestored process-global state
X20 · Mistyped argument guard
X21 · Side-effecting pattern guard
X22 · Contradicted release guard
X23 · Unguarded diagnostic materialisation
X24 · Document value interpolated into markup unescaped
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/2 of this repository's type-checking configuration(s) turn on strict null checking (`"strict": true`, or `"strictNullChecks": true`). A configuration that states neither is counted as OFF, because off is tsc's own default; a solution-style one whose `"files"` is empty and whose `"references"` point at other projects is in neither number, because it checks no source itself. Where it is off, `string` admits `null` and `undefined`: passing a value that is null compiles silently and throws on the first property access.
What to do
- The findings name the configuration each number was taken from and, for the assertions, the files that hold them. Turn null checking on where it is off — `"strict": true` in the base tsconfig that the others extend switches `strictNullChecks` on with the rest of the family — and then resolve the assertions rather than adding to them. A `!` on a value the checker could show to be null is a promise the author cannot check from where they are standing, and each one is a `TypeError: Cannot read properties of null` waiting for the path that makes it true; where the value genuinely cannot be null, say something the checker can see instead (narrow it with a test, make the property required, drop the `?`).
WCAG coverage — what static analysis assessed
| Dimension | WCAG 2.2 A/AA criteria | Coverage |
|---|---|---|
| AC2 · Forms & labels | 1.3.1, 3.3.2, 4.1.2 | Partial signal |
| AC3 · Page structure | 1.4.4, 2.2.1, 2.4.1, 2.4.2, 3.1.1, 4.1.2 | Partial signal |
| AC5 · ARIA correctness | 4.1.2 | Partial signal |
| AC6 · Visual & motion safety | 1.4.3, 2.4.7 | Partial — literal CSS only |
| AC7 · A11y enforcement | enforcement — no page criterion | Enforcement posture (process) |
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 75% | Adequate — gated by X5 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 87% | Strong | Solid. |
| Maturity | 54% | Adequate — gated by D34, M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 43% | Weak — gated by P3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 64% | Checked 5 of 11 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Domain Modelling | 68% | Adequate — gated by DM7 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Event Sourcing | 100% | Exemplary | Strongest area. |
| Accessibility | 53% | Adequate — gated by AC2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
Unscored — 3 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.
- SC1 Supply-chain hygiene — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
- X10 Duplicated predicate — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
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.
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 50 check(s) not relevant to this codebase
- AC1 Text alternatives — No image/media element found in the parsed markup — AC1 not applicable here.
- AC4 Keyboard semantics — No interactive element found in the parsed markup — AC4 not applicable here.
- AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AX8 Test isolation — no test/production split to check
- AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXR1 Runtime accessibility — the image ran but published no HTTP port — nothing to crawl (EXPOSE the web port to unlock runtime evidence) 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 scored — polyglot repository, one half has no runner
- D12 Dependency Hygiene — Dependency currency not established — repo.spring.io did not answer
- D16 Bus Factor — single-maintainer repository — bus factor is not applicable
- D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
- D21 Naming Consistency — Naming consistency is measured on C# and TypeScript only; Java, JavaScript, html 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. Aggregate roots were found in only one source directory (commandside), which is a layered codebase, not two contexts. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D24 Comment Value — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only; comments in this repository's .java source were not judged.
- D25 ADR Conformance — no ADRs to check
- D32 Data Compliance (PII/GDPR) — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
- 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 measured — JavaScript/TypeScript suite
- DM2 Strongly-typed ids — no id-bearing domain types detected — strongly-typed-id adoption not assessable
- DM3 Integration-event coupling — no integration events detected — coupling check not applicable
- DM8 Value-object opportunities — not scored — the deterministic rule found 0 candidate clump(s); its rows are withheld until it has a measured precision of 95 % (a sample of fewer than 10 rows cannot show one)
- ED1 Event-Driven — not scored — this repository shows only 1 of the 3 signals this lens looks for (3 event handler(s))
- ED5 Idempotency — Not assessed, and this one is on us: 3 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.
- ES2 Immutable events — no persisted event types detected — immutability check not applicable
- ES3 PII in the event store — no persisted event types detected — PII-in-events check not applicable
- 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 5 current-state document(s) make no claim of a kind M4 checks. 12 claim(s) of kinds M4 does not check were not checked (path 1, command argument 3, environment variable 1, cd 7); 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, JavaScript/TypeScript source (service entry point: registry/src/main/java/com/idugalic/registry/Application.java:7 (@SpringBootApplication))
- P8 Schema migrations — Hibernate is declared, but the schema-migration mechanism could not be identified. Our limit, not a verdict on this repository.
- P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (JaCoCo XML — `mvn jacoco:report`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures, or wire coverage collection into CI, to enable this cross-layer check
- PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for tinybench, mitata, benchmark.js, benny or vitest `bench(...)` calls in files that import them (or `*.bench.*` files), or one of those in a package.json, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
- PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
- PF3 Async & latency hygiene — Not applicable: this repository declares no async functions, so there is no asynchronous code for a blocking call to stall.
- R5 Dependency Freshness — no package-lock.json — dependency freshness not measured (would require an npm lockfile); JS/npm CVEs are scored in D30 (Dependency Vulnerabilities), which answers every ecosystem
- S1 Web-Security Posture — Not assessed: these web-security controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks web-security controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- X2 Cancellation propagation — no C# was loaded; this repository's 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 — 88 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- <input> without a programmatic label monolithic/src/main/frontend/src/app/blog-posts/blog-post-new/blog-post-new.component.html:7
- <input> without a programmatic label monolithic/src/main/frontend/src/app/blog-posts/blog-post-new/blog-post-new.component.html:13
- <input> without a programmatic label monolithic/src/main/frontend/src/app/projects/project-new/project-new.component.html:7
- <input> without a programmatic label monolithic/src/main/frontend/src/app/projects/project-new/project-new.component.html:10
- <input> without a programmatic label monolithic/src/main/frontend/src/app/projects/project-new/project-new.component.html:13
- <input> without a programmatic label monolithic/src/main/frontend/src/app/projects/project-new/project-new.component.html:16
- <html> without a lang api-gateway/src/main/resources/static/socket/index.html:2
- <html> without a lang REDACTED:2
- <html> without a lang REDACTED:2
- <textarea> without a programmatic label monolithic/src/main/frontend/src/app/blog-posts/blog-post-new/blog-post-new.component.html:10
- <textarea> without a programmatic label monolithic/src/main/frontend/src/app/projects/project-new/project-new.component.html:19
- REDACTED
- REDACTED
- <label> that labels no control monolithic/src/main/frontend/src/app/blog-posts/blog-post-new/blog-post-new.component.html:31
- REDACTED
- REDACTED
Serious — 93 finding(s)
- No test reaches this file monolithic/src/main/frontend/src/app/shared/alert/alert.service.ts:1
- No test reaches this file monolithic/src/main/frontend/src/app/shared/interceptor/http.interceptor.ts:1
- No test reaches this file monolithic/src/main/frontend/src/app/shared/alert/alert-error.component.ts:1
- No test reaches this file monolithic/src/main/frontend/src/app/blog-posts/blog-posts-routing.module.ts:1
- No test reaches this file monolithic/src/main/frontend/src/app/projects/projects-routing.module.ts:1
- No test reaches this file monolithic/src/main/frontend/src/app/app.module.ts:1
- No test reaches this file monolithic/src/main/frontend/src/test.ts:1
- No test reaches this file monolithic/src/main/frontend/src/app/shared/interceptor/http.interceptable.ts:1
- No test reaches this file monolithic/src/main/frontend/src/app/shared/interceptor/http.provider.ts:1
- No test reaches this file monolithic/src/main/frontend/src/app/blog-posts/blog-posts.module.ts:1
- No test reaches this file monolithic/src/main/frontend/src/app/shared/alert/alert.component.ts:1
- No test reaches this file monolithic/src/main/frontend/src/app/shared/interceptor/errorhandler.interceptor.ts:1
- No test reaches this file monolithic/src/main/frontend/src/app/projects/projects.module.ts:1
- No test reaches this file monolithic/src/main/frontend/src/app/app-routing.module.ts:1
- No test reaches this file monolithic/src/main/frontend/src/app/shared/alert/alert.provider.ts:1
- No test reaches this file monolithic/src/main/frontend/src/main.ts:1
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- TodoComment query-side-blog/src/main/java/com/idugalic/queryside/blog/domain/BlogPost.java:63
- TodoComment monolithic/src/main/java/com/idugalic/RestResponseEntityExceptionHandler.java:56
- TodoComment command-side-project-service/src/main/java/com/idugalic/commandside/project/RestResponseEntityExceptionHandler.java:47
- TodoComment command-side-blog-service/src/main/java/com/idugalic/commandside/blog/RestResponseEntityExceptionHandler.java:49
- TodoComment monolithic/src/main/java/com/idugalic/RestResponseEntityExceptionHandler.java:97
- TodoComment command-side-project-service/src/main/java/com/idugalic/commandside/project/RestResponseEntityExceptionHandler.java:85
- TodoComment command-side-blog-service/src/main/java/com/idugalic/commandside/blog/RestResponseEntityExceptionHandler.java:90
- TodoComment api-gateway/src/main/java/com/idugalic/apigateway/handler/EventLoggingHandler.java:36
- Duplicated block (5 lines × 3) command-side-blog-service/src/main/java/com/idugalic/commandside/blog/RestResponseEntityExceptionHandler.java:52
- Duplicated block (5 lines × 3) command-side-blog-service/src/main/java/com/idugalic/commandside/blog/RestResponseEntityExceptionHandler.java:68
- Duplicated block (5 lines × 3) command-side-blog-service/src/main/java/com/idugalic/commandside/blog/RestResponseEntityExceptionHandler.java:75
- Duplicated block (5 lines × 3) command-side-blog-service/src/main/java/com/idugalic/commandside/blog/RestResponseEntityExceptionHandler.java:82
- Page without a main landmark api-gateway/src/main/resources/static/socket/index.html:2
- Page without a main landmark REDACTED:2
- Page without a main landmark REDACTED:2
- Duplicated block (6 lines × 2) command-side-blog/src/main/java/com/idugalic/commandside/blog/aggregate/BlogPostAggregate.java:99
- Duplicated block (6 lines × 2) command-side-blog/src/main/java/com/idugalic/commandside/blog/web/BlogController.java:37
- Duplicated block (6 lines × 2) documentation/src/main/java/com/idugalic/documentation/DocumentationApplication.java:97
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Constructible in an invalid state: Project query-side-project/src/main/java/com/idugalic/queryside/project/domain/Project.java:41
- Constructible in an invalid state: BlogPost query-side-blog/src/main/java/com/idugalic/queryside/blog/domain/BlogPost.java:41
- Repository for a non-root entity: ProjectRepository → Project query-side-project/src/main/java/com/idugalic/queryside/project/repository/ProjectRepository.java:14
- Repository for a non-root entity: BlogPostRepository → BlogPost query-side-blog/src/main/java/com/idugalic/queryside/blog/repository/BlogPostRepository.java:21
- Accessibility enforcement below the top rung monolithic/src/main/frontend/package.json:35
- REDACTED
- Duplicated block (12 lines × 3) api-gateway/src/main/java/com/idugalic/apigateway/Application.java:29
- Duplicated block (11 lines × 3) command-side-blog-service/src/main/java/com/idugalic/commandside/blog/Application.java:21
- Duplicated block (7 lines × 2) command-side-blog-service/src/main/java/com/idugalic/commandside/blog/RestResponseEntityExceptionHandler.java:59
- Duplicated block (27 lines × 3) command-side-blog-service/src/main/java/com/idugalic/commandside/blog/configuration/AxonConfiguration.java:1
- Duplicated block (45 lines × 2) command-side-blog-service/src/main/java/com/idugalic/commandside/blog/configuration/RabbitConfiguration.java:1
- Duplicated block (15 lines × 2) command-side-blog/src/main/java/com/idugalic/commandside/blog/web/ValidationWsDto.java:19
- Duplicated block (34 lines × 2) command-side-project/src/main/java/com/idugalic/commandside/project/web/CreateProjectRequest.java:17
- Duplicated block (82 lines × 2) query-side-blog-service/src/main/java/com/idugalic/queryside/blog/configuration/RabbitConfiguration.java:1
- Duplicated block (5 lines × 6) command-side-blog-service/src/main/java/com/idugalic/commandside/blog/RestResponseEntityExceptionHandler.java:35
- Duplicated block (6 lines × 3) command-side-blog-service/src/main/java/com/idugalic/commandside/blog/RestResponseEntityExceptionHandler.java:89
- Duplicated block (16 lines × 2) documentation/src/main/java/com/idugalic/documentation/DocumentationApplication.java:126
- End-of-life framework: Spring Boot 1 REDACTED:1
- Duplication concentrated across 2 sibling directories (5 clone groups) monolithic/src/main/frontend/src/app/blog-posts/blog-posts-routing.module.ts:10
- Duplicated block (30 lines × 2 locations) monolithic/src/main/frontend/src/app/blog-posts/blog-posts-routing.module.ts:10
- Duplicated block (29 lines × 2 locations) monolithic/src/main/frontend/src/app/blog-posts/blog-post/blog-post.component.ts:11
- Duplicated block with local edits (28 matched lines × 2 locations) monolithic/src/main/frontend/src/app/blog-posts/shared/blog-posts.service.ts:9
- Duplicated block (8 lines × 2 locations) monolithic/src/main/frontend/src/app/blog-posts/blog-post-new/blog-post-new.component.ts:43
- Boundary violation [package:third-party-deep-import] monolithic/src/main/frontend/src/polyfills.ts:19
- No typecheck script
- Unused dependency '@angular/compiler'
- Unused dependency '@angular/compiler-cli'
- Unused dependency 'bootstrap'
- JavaScript dependencies are not locked monolithic/src/main/frontend/package.json:15
Minor — 74 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Orphaned file command-side-project/src/main/java/com/idugalic/commandside/project/aggregate/ProjectRelease.java:1
- Orphaned file monolithic/src/main/java/com/idugalic/RestResponseEntityExceptionHandler.java:1
- Orphaned file command-side-blog-service/src/main/java/com/idugalic/commandside/blog/RestResponseEntityExceptionHandler.java:1
- Orphaned file authserver/src/main/java/com/idugalic/authserver/AuthserverApplication.java:1
- Orphaned file command-side-project-service/src/main/java/com/idugalic/commandside/project/RestResponseEntityExceptionHandler.java:1
- Orphaned file command-side-blog/src/main/java/com/idugalic/commandside/blog/aggregate/BlogPostAggregate.java:1
- Orphaned file command-side-project/src/main/java/com/idugalic/commandside/project/aggregate/ProjectAggregate.java:1
- Orphaned file query-side-blog/src/main/java/com/idugalic/queryside/blog/domain/BlogPost.java:1
- Orphaned file api-gateway/src/main/java/com/idugalic/apigateway/configuration/RabbitConfiguration.java:1
- Orphaned file command-side-blog/src/main/java/com/idugalic/commandside/blog/web/BlogController.java:1
- Orphaned file command-side-project/src/main/java/com/idugalic/commandside/project/web/ProjectController.java:1
- Orphaned file monolithic/src/main/frontend/src/app/shared/alert/alert.service.ts:1
- Orphaned file monolithic/src/main/java/com/idugalic/configuration/RestConfiguration.java:1
- Orphaned file query-side-project-service/src/main/java/com/idugalic/queryside/project/configuration/RabbitConfiguration.java:1
- Orphaned file query-side-blog-service/src/main/java/com/idugalic/queryside/blog/configuration/RabbitConfiguration.java:1
- Orphaned file query-side-project/src/main/java/com/idugalic/queryside/project/domain/Project.java:1
- Orphaned file query-side-blog/src/main/java/com/idugalic/queryside/blog/repository/BlogPostRepository.java:1
- Orphaned file command-side-blog/src/main/java/com/idugalic/commandside/blog/command/CreateBlogPostCommand.java:1
- Orphaned file monolithic/src/main/frontend/src/app/shared/interceptor/http.interceptor.ts:1
- No direct assertions: createBlogPostTest monolithic/src/test/java/com/idugalic/commandside/blog/aggregate/BlogPostAggregateTest.java:43
- No direct assertions: createBlogPostWithWrongTitleTest monolithic/src/test/java/com/idugalic/commandside/blog/aggregate/BlogPostAggregateTest.java:50
- No direct assertions: publishBlogPostTest monolithic/src/test/java/com/idugalic/commandside/blog/aggregate/BlogPostAggregateTest.java:57
- No direct assertions: publishBlogPostWithWrongIdTest monolithic/src/test/java/com/idugalic/commandside/blog/aggregate/BlogPostAggregateTest.java:64
- No direct assertions: createBlogPostWithSuccessTest monolithic/src/test/java/com/idugalic/commandside/blog/web/BlogControllerTest.java:71
- No direct assertions: createBlogPostWithValidationErrorTest monolithic/src/test/java/com/idugalic/commandside/blog/web/BlogControllerTest.java:60
- No direct assertions: createBlogPostTest monolithic/src/test/java/com/idugalic/commandside/project/aggregate/BlogPostAggregateTest.java:36
- No direct assertions: createBlogPostWithWrongNameTest monolithic/src/test/java/com/idugalic/commandside/project/aggregate/BlogPostAggregateTest.java:42
- No direct assertions: updateBlogPostTest monolithic/src/test/java/com/idugalic/commandside/project/aggregate/BlogPostAggregateTest.java:48
- No direct assertions: createProjectWithSuccessTest monolithic/src/test/java/com/idugalic/commandside/project/web/ProjectControllerTest.java:71
- No direct assertions: createProjectWithValidationErrorTest monolithic/src/test/java/com/idugalic/commandside/project/web/ProjectControllerTest.java:60
- REDACTED
- REDACTED
- No ADRs found
- Orphaned files with no living knowledge
- REDACTED
- No ADRs
- Logging is not universal
- No SAST REDACTED:9
- No dependency-update automation monolithic/src/main/frontend/package.json:15
- No rollback/health safety
- No changelog
- Duplicated predicate api-gateway/src/main/java/com/idugalic/apigateway/Application.java:33
- Strict null checking is not enabled everywhere the repository type-checks
Minor — 2 finding(s)
- Off the main sequence: common-blog
- Off the main sequence: common-project
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-de3a577f5c0343ebaf8b48711fcf0c92/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-de3a577f5c0343ebaf8b48711fcf0c92/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 --exclude api-gateway/src/main/resources/static . | 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 . | 0 | artifacts/raw/osv-scanner.json |
| D30 · Dependency Vulnerabilities | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . --skip-db-update | 55 | artifacts/raw/trivy-fs.json |
| D31 · IaC & Container Security | trivy | — | trivy config --format json --quiet . | 76 | artifacts/raw/trivy-config.json |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. | 0 | — |
| 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 | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . --skip-db-update | 0 | artifacts/raw/trivy-fs.json |