Executive summary
codecentric/spring-boot-admin is rated At risk because critical security findings are open. Its score is held back in part because it has controls that only work with a mouse. It scores 53.6 out of 100, which the At risk rating leaves unchanged.
Accessibility, at 36.3, is the weakest lens and counts most in the score. The best first step is making the controls keyboard-usable, worth about 6.6 points. Adding text alternatives comes next, worth about 3.4 points. Raising Accessibility to 70 would lift the score to about 67.4.
Thirty-three pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Thirty known security holes in the packages the code depends on can be used by attackers, and nine settings leave the servers or containers unsafe. Pinning each tool to an exact version, updating the vulnerable packages and correcting the unsafe settings would close these risks. Passing outside input through environment variables would fix the four pipeline steps that put outside input straight into a shell command, and setting a waiting period for automatic updates would deal with the automatic dependency update that takes a new release at once. The six tests that check nothing need to check the result they produce.
The product code is 58,798 lines, about €86,000 to rebuild. The check for the health of its packages couldn't finish, so that result is missing, not a clean pass.
If Accessibility rose from 36.3 to 70, the lowest score rated Strong, the score would rise from 53.6 to about 67.4.
Rebuild cost: about €86,000 · Estimate
| Cost to rebuild | €29,000 to €140,000, for 475 to 1,507 hours of work, about 0.6 person-years for 1 to 2 engineers |
|---|---|
| Difficulty of the problem | Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.7 at a score of 54. 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 | Medium: 58,798 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 de.codecentric.boot.admin.server.domain.values | 2 de.codecentric.boot.admin.server.ui.extensions | 3 org.springframework.http | 4 spring-boot-admin-docs.src.site.src.components.HexMesh | 5 spring-boot-admin-server-ui.src.main.frontend.services.application | 6 spring-boot-admin-server-ui.src.main.frontend.services.instance | 7 de.codecentric.boot.admin.client.registration.metadata | 8 de.codecentric.boot.admin.server.domain.events | 9 de.codecentric.boot.admin.server.ui.web | 10 de.codecentric.boot.admin.server.utils | 11 de.codecentric.boot.admin.server.utils.jackson | 12 spring-boot-admin-docs.src.site.src.components | 13 spring-boot-admin-server-ui.src.main.frontend | 14 spring-boot-admin-server-ui.src.main.frontend.services.quartz-actuator | 15 spring-boot-admin-server-ui.src.main.frontend.store | 16 spring-boot-admin-server-ui.src.main.frontend.views.applications.ActionHandler | 17 de.codecentric.boot.admin.client.registration | 18 de.codecentric.boot.admin.server.eventstore | 19 de.codecentric.boot.admin.server.ui.web.reactive | 20 de.codecentric.boot.admin.server.ui.web.servlet | 21 de.codecentric.boot.admin.server.web.client.cookies | 22 de.codecentric.boot.admin.client.config | 23 de.codecentric.boot.admin.server.domain.entities | 24 de.codecentric.boot.admin.server.notify.filter | 25 de.codecentric.boot.admin.server.web.client.reactive | 26 de.codecentric.boot.admin.server.notify.filter.web | 27 de.codecentric.boot.admin.server.web.client | 28 de.codecentric.boot.admin.server.mcp.tools | 29 de.codecentric.boot.admin.server.services.endpoints | 30 de.codecentric.boot.admin.server.mcp.config | 31 de.codecentric.boot.admin.server.services | 32 de.codecentric.boot.admin.server.cloud.discovery | 33 de.codecentric.boot.admin.server.notify | 34 de.codecentric.boot.admin.server.web | 35 de.codecentric.boot.admin.server.cloud.config | 36 de.codecentric.boot.admin.server.web.reactive | 37 de.codecentric.boot.admin.server.web.servlet | 38 de.codecentric.boot.admin.server.config | 39 de.codecentric.boot.admin | 40 de.codecentric.boot.admin.server.ui.config |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 de.codecentric.boot.admin.server.domain.values | ||||||||||||||||||||||||||||||||||||||||
| 2 de.codecentric.boot.admin.server.ui.extensions | ||||||||||||||||||||||||||||||||||||||||
| 3 org.springframework.http | ||||||||||||||||||||||||||||||||||||||||
| 4 spring-boot-admin-docs.src.site.src.components.HexMesh | ||||||||||||||||||||||||||||||||||||||||
| 5 spring-boot-admin-server-ui.src.main.frontend.services.application | ||||||||||||||||||||||||||||||||||||||||
| 6 spring-boot-admin-server-ui.src.main.frontend.services.instance | ||||||||||||||||||||||||||||||||||||||||
| 7 de.codecentric.boot.admin.client.registration.metadata | 1 | |||||||||||||||||||||||||||||||||||||||
| 8 de.codecentric.boot.admin.server.domain.events | 12 | |||||||||||||||||||||||||||||||||||||||
| 9 de.codecentric.boot.admin.server.ui.web | 2 | 3 | ||||||||||||||||||||||||||||||||||||||
| 10 de.codecentric.boot.admin.server.utils | 1 | |||||||||||||||||||||||||||||||||||||||
| 11 de.codecentric.boot.admin.server.utils.jackson | 20 | |||||||||||||||||||||||||||||||||||||||
| 12 spring-boot-admin-docs.src.site.src.components | 2 | |||||||||||||||||||||||||||||||||||||||
| 13 spring-boot-admin-server-ui.src.main.frontend | 1 | |||||||||||||||||||||||||||||||||||||||
| 14 spring-boot-admin-server-ui.src.main.frontend.services.quartz-actuator | 1 | |||||||||||||||||||||||||||||||||||||||
| 15 spring-boot-admin-server-ui.src.main.frontend.store | 1 | |||||||||||||||||||||||||||||||||||||||
| 16 spring-boot-admin-server-ui.src.main.frontend.views.applications.ActionHandler | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 17 de.codecentric.boot.admin.client.registration | 6 | 7 | ||||||||||||||||||||||||||||||||||||||
| 18 de.codecentric.boot.admin.server.eventstore | 4 | 6 | ||||||||||||||||||||||||||||||||||||||
| 19 de.codecentric.boot.admin.server.ui.web.reactive | 2 | |||||||||||||||||||||||||||||||||||||||
| 20 de.codecentric.boot.admin.server.ui.web.servlet | 2 | |||||||||||||||||||||||||||||||||||||||
| 21 de.codecentric.boot.admin.server.web.client.cookies | 2 | 2 | 1 | |||||||||||||||||||||||||||||||||||||
| 22 de.codecentric.boot.admin.client.config | 6 | 9 | ||||||||||||||||||||||||||||||||||||||
| 23 de.codecentric.boot.admin.server.domain.entities | 11 | 3 | 2 | |||||||||||||||||||||||||||||||||||||
| 24 de.codecentric.boot.admin.server.notify.filter | 1 | 6 | 8 | 3 | ||||||||||||||||||||||||||||||||||||
| 25 de.codecentric.boot.admin.server.web.client.reactive | 2 | |||||||||||||||||||||||||||||||||||||||
| 26 de.codecentric.boot.admin.server.notify.filter.web | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 27 de.codecentric.boot.admin.server.web.client | 1 | 1 | 6 | 1 | ||||||||||||||||||||||||||||||||||||
| 28 de.codecentric.boot.admin.server.mcp.tools | 3 | 1 | ||||||||||||||||||||||||||||||||||||||
| 29 de.codecentric.boot.admin.server.services.endpoints | 7 | 4 | 2 | 1 | ||||||||||||||||||||||||||||||||||||
| 30 de.codecentric.boot.admin.server.mcp.config | 1 | 1 | 13 | |||||||||||||||||||||||||||||||||||||
| 31 de.codecentric.boot.admin.server.services | 20 | 5 | 1 | 1 | 11 | 2 | 1 | |||||||||||||||||||||||||||||||||
| 32 de.codecentric.boot.admin.server.cloud.discovery | 3 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 33 de.codecentric.boot.admin.server.notify | 3 | 23 | 36 | 10 | 1 | |||||||||||||||||||||||||||||||||||
| 34 de.codecentric.boot.admin.server.web | 3 | 2 | 1 | 1 | 1 | 3 | 1 | 3 | ||||||||||||||||||||||||||||||||
| 35 de.codecentric.boot.admin.server.cloud.config | 1 | 1 | 5 | |||||||||||||||||||||||||||||||||||||
| 36 de.codecentric.boot.admin.server.web.reactive | 1 | 1 | 1 | 4 | ||||||||||||||||||||||||||||||||||||
| 37 de.codecentric.boot.admin.server.web.servlet | 1 | 1 | 1 | 4 | ||||||||||||||||||||||||||||||||||||
| 38 de.codecentric.boot.admin.server.config | 6 | 3 | 3 | 5 | 3 | 16 | 2 | 1 | 1 | 14 | 18 | 32 | 2 | 1 | 1 | |||||||||||||||||||||||||
| 39 de.codecentric.boot.admin | 1 | |||||||||||||||||||||||||||||||||||||||
| 40 de.codecentric.boot.admin.server.ui.config | 1 | 5 | 1 | 2 | 3 |
7→22 de.codecentric.boot.admin.client.registration.metadata uses de.codecentric.boot.admin.client.config part of a loop✕
- Connections
- 1 pair of types, where a type in de.codecentric.boot.admin.client.registration.metadata uses a type in de.codecentric.boot.admin.client.config.
- The types involved
de.codecentric.boot.admin.client.registration.metadata.CloudFoundryMetadataContributor→de.codecentric.boot.admin.client.config.CloudFoundryApplicationProperties
- Direction
- de.codecentric.boot.admin.client.registration.metadata uses de.codecentric.boot.admin.client.config, so a change to de.codecentric.boot.admin.client.config can break de.codecentric.boot.admin.client.registration.metadata, while a change to de.codecentric.boot.admin.client.registration.metadata can't break de.codecentric.boot.admin.client.config.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
8→1 de.codecentric.boot.admin.server.domain.events uses de.codecentric.boot.admin.server.domain.values✕
- Connections
- 12 pairs of types, where a type in de.codecentric.boot.admin.server.domain.events uses a type in de.codecentric.boot.admin.server.domain.values.
- The types involved
de.codecentric.boot.admin.server.domain.events.InstanceDeregisteredEvent→de.codecentric.boot.admin.server.domain.values.InstanceIdde.codecentric.boot.admin.server.domain.events.InstanceEndpointsDetectedEvent→de.codecentric.boot.admin.server.domain.values.Endpointsde.codecentric.boot.admin.server.domain.events.InstanceEndpointsDetectedEvent→de.codecentric.boot.admin.server.domain.values.InstanceIdde.codecentric.boot.admin.server.domain.events.InstanceEvent→de.codecentric.boot.admin.server.domain.values.InstanceIdde.codecentric.boot.admin.server.domain.events.InstanceInfoChangedEvent→de.codecentric.boot.admin.server.domain.values.Infode.codecentric.boot.admin.server.domain.events.InstanceInfoChangedEvent→de.codecentric.boot.admin.server.domain.values.InstanceIdde.codecentric.boot.admin.server.domain.events.InstanceRegisteredEvent→de.codecentric.boot.admin.server.domain.values.InstanceIdde.codecentric.boot.admin.server.domain.events.InstanceRegisteredEvent→de.codecentric.boot.admin.server.domain.values.Registrationde.codecentric.boot.admin.server.domain.events.InstanceRegistrationUpdatedEvent→de.codecentric.boot.admin.server.domain.values.InstanceIdde.codecentric.boot.admin.server.domain.events.InstanceRegistrationUpdatedEvent→de.codecentric.boot.admin.server.domain.values.Registrationde.codecentric.boot.admin.server.domain.events.InstanceStatusChangedEvent→de.codecentric.boot.admin.server.domain.values.InstanceIdde.codecentric.boot.admin.server.domain.events.InstanceStatusChangedEvent→de.codecentric.boot.admin.server.domain.values.StatusInfo
- Direction
- de.codecentric.boot.admin.server.domain.events uses de.codecentric.boot.admin.server.domain.values, so a change to de.codecentric.boot.admin.server.domain.values can break de.codecentric.boot.admin.server.domain.events, while a change to de.codecentric.boot.admin.server.domain.events can't break de.codecentric.boot.admin.server.domain.values.
- Position
- Below the diagonal: de.codecentric.boot.admin.server.domain.events uses a module listed above it, which is the healthy direction.
9→2 de.codecentric.boot.admin.server.ui.web uses de.codecentric.boot.admin.server.ui.extensions✕
- Connections
- 2 pairs of types, where a type in de.codecentric.boot.admin.server.ui.web uses a type in de.codecentric.boot.admin.server.ui.extensions.
- The types involved
de.codecentric.boot.admin.server.ui.web.UiController→de.codecentric.boot.admin.server.ui.extensions.UiExtensionde.codecentric.boot.admin.server.ui.web.UiController→de.codecentric.boot.admin.server.ui.extensions.UiExtensions
- Direction
- de.codecentric.boot.admin.server.ui.web uses de.codecentric.boot.admin.server.ui.extensions, so a change to de.codecentric.boot.admin.server.ui.extensions can break de.codecentric.boot.admin.server.ui.web, while a change to de.codecentric.boot.admin.server.ui.web can't break de.codecentric.boot.admin.server.ui.extensions.
- Position
- Below the diagonal: de.codecentric.boot.admin.server.ui.web uses a module listed above it, which is the healthy direction.
9→40 de.codecentric.boot.admin.server.ui.web uses de.codecentric.boot.admin.server.ui.config part of a loop✕
- Connections
- 3 pairs of types, where a type in de.codecentric.boot.admin.server.ui.web uses a type in de.codecentric.boot.admin.server.ui.config.
- The types involved
de.codecentric.boot.admin.server.ui.web.Settings→de.codecentric.boot.admin.server.ui.config.PollTimerde.codecentric.boot.admin.server.ui.web.Settings→de.codecentric.boot.admin.server.ui.config.UiThemede.codecentric.boot.admin.server.ui.web.UiController→de.codecentric.boot.admin.server.ui.config.Palette
- Direction
- de.codecentric.boot.admin.server.ui.web uses de.codecentric.boot.admin.server.ui.config, so a change to de.codecentric.boot.admin.server.ui.config can break de.codecentric.boot.admin.server.ui.web, while a change to de.codecentric.boot.admin.server.ui.web can't break de.codecentric.boot.admin.server.ui.config.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
10→38 de.codecentric.boot.admin.server.utils uses de.codecentric.boot.admin.server.config part of a loop✕
- Connections
- 1 pair of types, where a type in de.codecentric.boot.admin.server.utils uses a type in de.codecentric.boot.admin.server.config.
- The types involved
de.codecentric.boot.admin.server.utils.SsrfUrlValidator→de.codecentric.boot.admin.server.config.SsrfProtectionProperties
- Direction
- de.codecentric.boot.admin.server.utils uses de.codecentric.boot.admin.server.config, so a change to de.codecentric.boot.admin.server.config can break de.codecentric.boot.admin.server.utils, while a change to de.codecentric.boot.admin.server.utils can't break de.codecentric.boot.admin.server.config.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
11→1 de.codecentric.boot.admin.server.utils.jackson uses de.codecentric.boot.admin.server.domain.values✕
- Connections
- 20 pairs of types, where a type in de.codecentric.boot.admin.server.utils.jackson uses a type in de.codecentric.boot.admin.server.domain.values.
- The types involved
de.codecentric.boot.admin.server.utils.jackson.BuildVersionMixin→de.codecentric.boot.admin.server.domain.values.BuildVersionde.codecentric.boot.admin.server.utils.jackson.Builder→de.codecentric.boot.admin.server.domain.values.Infode.codecentric.boot.admin.server.utils.jackson.EndpointMixin→de.codecentric.boot.admin.server.domain.values.Endpointde.codecentric.boot.admin.server.utils.jackson.EndpointsMixin→de.codecentric.boot.admin.server.domain.values.Endpointde.codecentric.boot.admin.server.utils.jackson.EndpointsMixin→de.codecentric.boot.admin.server.domain.values.Endpointsde.codecentric.boot.admin.server.utils.jackson.InstanceDeregisteredEventMixin→de.codecentric.boot.admin.server.domain.values.InstanceIdde.codecentric.boot.admin.server.utils.jackson.InstanceEndpointsDetectedEventMixin→de.codecentric.boot.admin.server.domain.values.Endpointsde.codecentric.boot.admin.server.utils.jackson.InstanceEndpointsDetectedEventMixin→de.codecentric.boot.admin.server.domain.values.InstanceIdde.codecentric.boot.admin.server.utils.jackson.InstanceIdMixin→de.codecentric.boot.admin.server.domain.values.InstanceIdde.codecentric.boot.admin.server.utils.jackson.InstanceInfoChangedEventMixin→de.codecentric.boot.admin.server.domain.values.Infode.codecentric.boot.admin.server.utils.jackson.InstanceInfoChangedEventMixin→de.codecentric.boot.admin.server.domain.values.InstanceIdde.codecentric.boot.admin.server.utils.jackson.InstanceRegisteredEventMixin→de.codecentric.boot.admin.server.domain.values.InstanceIdde.codecentric.boot.admin.server.utils.jackson.InstanceRegisteredEventMixin→de.codecentric.boot.admin.server.domain.values.Registrationde.codecentric.boot.admin.server.utils.jackson.InstanceRegistrationUpdatedEventMixin→de.codecentric.boot.admin.server.domain.values.InstanceIdde.codecentric.boot.admin.server.utils.jackson.InstanceRegistrationUpdatedEventMixin→de.codecentric.boot.admin.server.domain.values.Registrationde.codecentric.boot.admin.server.utils.jackson.InstanceStatusChangedEventMixin→de.codecentric.boot.admin.server.domain.values.InstanceIdde.codecentric.boot.admin.server.utils.jackson.InstanceStatusChangedEventMixin→de.codecentric.boot.admin.server.domain.values.StatusInfode.codecentric.boot.admin.server.utils.jackson.RegistrationDeserializer→de.codecentric.boot.admin.server.domain.values.Registrationde.codecentric.boot.admin.server.utils.jackson.StatusInfoMixin→de.codecentric.boot.admin.server.domain.values.StatusInfode.codecentric.boot.admin.server.utils.jackson.TagsMixin→de.codecentric.boot.admin.server.domain.values.Tags
- Direction
- de.codecentric.boot.admin.server.utils.jackson uses de.codecentric.boot.admin.server.domain.values, so a change to de.codecentric.boot.admin.server.domain.values can break de.codecentric.boot.admin.server.utils.jackson, while a change to de.codecentric.boot.admin.server.utils.jackson can't break de.codecentric.boot.admin.server.domain.values.
- Position
- Below the diagonal: de.codecentric.boot.admin.server.utils.jackson uses a module listed above it, which is the healthy direction.
12→4 spring-boot-admin-docs.src.site.src.components uses spring-boot-admin-docs.src.site.src.components.HexMesh✕
- Connections
- 2 pairs of types, where a type in spring-boot-admin-docs.src.site.src.components uses a type in spring-boot-admin-docs.src.site.src.components.HexMesh.
- The types involved
spring-boot-admin-docs.src.site.src.components.HexMesh→spring-boot-admin-docs.src.site.src.components.HexMesh.HexMeshPropsspring-boot-admin-docs.src.site.src.components.HexMesh→spring-boot-admin-docs.src.site.src.components.HexMesh.Layout
- Direction
- spring-boot-admin-docs.src.site.src.components uses spring-boot-admin-docs.src.site.src.components.HexMesh, so a change to spring-boot-admin-docs.src.site.src.components.HexMesh can break spring-boot-admin-docs.src.site.src.components, while a change to spring-boot-admin-docs.src.site.src.components can't break spring-boot-admin-docs.src.site.src.components.HexMesh.
- Position
- Below the diagonal: spring-boot-admin-docs.src.site.src.components uses a module listed above it, which is the healthy direction.
13→5 spring-boot-admin-server-ui.src.main.frontend uses spring-boot-admin-server-ui.src.main.frontend.services.application✕
- Connections
- 1 pair of types, where a type in spring-boot-admin-server-ui.src.main.frontend uses a type in spring-boot-admin-server-ui.src.main.frontend.services.application.
- The types involved
spring-boot-admin-server-ui.src.main.frontend.notifications→spring-boot-admin-server-ui.src.main.frontend.services.application.Application
- Direction
- spring-boot-admin-server-ui.src.main.frontend uses spring-boot-admin-server-ui.src.main.frontend.services.application, so a change to spring-boot-admin-server-ui.src.main.frontend.services.application can break spring-boot-admin-server-ui.src.main.frontend, while a change to spring-boot-admin-server-ui.src.main.frontend can't break spring-boot-admin-server-ui.src.main.frontend.services.application.
- Position
- Below the diagonal: spring-boot-admin-server-ui.src.main.frontend uses a module listed above it, which is the healthy direction.
14→6 spring-boot-admin-server-ui.src.main.frontend.services.quartz-actuator uses spring-boot-admin-server-ui.src.main.frontend.services.instance✕
- Connections
- 1 pair of types, where a type in spring-boot-admin-server-ui.src.main.frontend.services.quartz-actuator uses a type in spring-boot-admin-server-ui.src.main.frontend.services.instance.
- The types involved
spring-boot-admin-server-ui.src.main.frontend.services.quartz-actuator.QuartzActuatorService→spring-boot-admin-server-ui.src.main.frontend.services.instance.Instance
- Direction
- spring-boot-admin-server-ui.src.main.frontend.services.quartz-actuator uses spring-boot-admin-server-ui.src.main.frontend.services.instance, so a change to spring-boot-admin-server-ui.src.main.frontend.services.instance can break spring-boot-admin-server-ui.src.main.frontend.services.quartz-actuator, while a change to spring-boot-admin-server-ui.src.main.frontend.services.quartz-actuator can't break spring-boot-admin-server-ui.src.main.frontend.services.instance.
- Position
- Below the diagonal: spring-boot-admin-server-ui.src.main.frontend.services.quartz-actuator uses a module listed above it, which is the healthy direction.
15→5 spring-boot-admin-server-ui.src.main.frontend.store uses spring-boot-admin-server-ui.src.main.frontend.services.application✕
- Connections
- 1 pair of types, where a type in spring-boot-admin-server-ui.src.main.frontend.store uses a type in spring-boot-admin-server-ui.src.main.frontend.services.application.
- The types involved
spring-boot-admin-server-ui.src.main.frontend.store.ApplicationStore→spring-boot-admin-server-ui.src.main.frontend.services.application.Application
- Direction
- spring-boot-admin-server-ui.src.main.frontend.store uses spring-boot-admin-server-ui.src.main.frontend.services.application, so a change to spring-boot-admin-server-ui.src.main.frontend.services.application can break spring-boot-admin-server-ui.src.main.frontend.store, while a change to spring-boot-admin-server-ui.src.main.frontend.store can't break spring-boot-admin-server-ui.src.main.frontend.services.application.
- Position
- Below the diagonal: spring-boot-admin-server-ui.src.main.frontend.store uses a module listed above it, which is the healthy direction.
16→5 spring-boot-admin-server-ui.src.main.frontend.views.applications.ActionHandler uses spring-boot-admin-server-ui.src.main.frontend.services.application✕
- Connections
- 1 pair of types, where a type in spring-boot-admin-server-ui.src.main.frontend.views.applications.ActionHandler uses a type in spring-boot-admin-server-ui.src.main.frontend.services.application.
- The types involved
spring-boot-admin-server-ui.src.main.frontend.views.applications.ActionHandler.ApplicationActionHandler→spring-boot-admin-server-ui.src.main.frontend.services.application.Application
- Direction
- spring-boot-admin-server-ui.src.main.frontend.views.applications.ActionHandler uses spring-boot-admin-server-ui.src.main.frontend.services.application, so a change to spring-boot-admin-server-ui.src.main.frontend.services.application can break spring-boot-admin-server-ui.src.main.frontend.views.applications.ActionHandler, while a change to spring-boot-admin-server-ui.src.main.frontend.views.applications.ActionHandler can't break spring-boot-admin-server-ui.src.main.frontend.services.application.
- Position
- Below the diagonal: spring-boot-admin-server-ui.src.main.frontend.views.applications.ActionHandler uses a module listed above it, which is the healthy direction.
16→6 spring-boot-admin-server-ui.src.main.frontend.views.applications.ActionHandler uses spring-boot-admin-server-ui.src.main.frontend.services.instance✕
- Connections
- 1 pair of types, where a type in spring-boot-admin-server-ui.src.main.frontend.views.applications.ActionHandler uses a type in spring-boot-admin-server-ui.src.main.frontend.services.instance.
- The types involved
spring-boot-admin-server-ui.src.main.frontend.views.applications.ActionHandler.InstanceActionHandler→spring-boot-admin-server-ui.src.main.frontend.services.instance.Instance
- Direction
- spring-boot-admin-server-ui.src.main.frontend.views.applications.ActionHandler uses spring-boot-admin-server-ui.src.main.frontend.services.instance, so a change to spring-boot-admin-server-ui.src.main.frontend.services.instance can break spring-boot-admin-server-ui.src.main.frontend.views.applications.ActionHandler, while a change to spring-boot-admin-server-ui.src.main.frontend.views.applications.ActionHandler can't break spring-boot-admin-server-ui.src.main.frontend.services.instance.
- Position
- Below the diagonal: spring-boot-admin-server-ui.src.main.frontend.views.applications.ActionHandler uses a module listed above it, which is the healthy direction.
17→7 de.codecentric.boot.admin.client.registration uses de.codecentric.boot.admin.client.registration.metadata✕
- Connections
- 6 pairs of types, where a type in de.codecentric.boot.admin.client.registration uses a type in de.codecentric.boot.admin.client.registration.metadata.
- The types involved
de.codecentric.boot.admin.client.registration.AbstractApplicationFactory→de.codecentric.boot.admin.client.registration.metadata.MetadataContributorde.codecentric.boot.admin.client.registration.CloudFoundryApplicationFactory→de.codecentric.boot.admin.client.registration.metadata.MetadataContributorde.codecentric.boot.admin.client.registration.DefaultApplicationFactory→de.codecentric.boot.admin.client.registration.metadata.MetadataContributorde.codecentric.boot.admin.client.registration.ReactiveApplicationFactory→de.codecentric.boot.admin.client.registration.metadata.MetadataContributorde.codecentric.boot.admin.client.registration.ServletApplicationFactory→de.codecentric.boot.admin.client.registration.metadata.MetadataContributorde.codecentric.boot.admin.client.registration.ServletContainerApplicationFactory→de.codecentric.boot.admin.client.registration.metadata.MetadataContributor
- Direction
- de.codecentric.boot.admin.client.registration uses de.codecentric.boot.admin.client.registration.metadata, so a change to de.codecentric.boot.admin.client.registration.metadata can break de.codecentric.boot.admin.client.registration, while a change to de.codecentric.boot.admin.client.registration can't break de.codecentric.boot.admin.client.registration.metadata.
- Position
- Below the diagonal: de.codecentric.boot.admin.client.registration uses a module listed above it, which is the healthy direction.
17→22 de.codecentric.boot.admin.client.registration uses de.codecentric.boot.admin.client.config part of a loop✕
- Connections
- 7 pairs of types, where a type in de.codecentric.boot.admin.client.registration uses a type in de.codecentric.boot.admin.client.config.
- The types involved
de.codecentric.boot.admin.client.registration.AbstractApplicationFactory→de.codecentric.boot.admin.client.config.InstancePropertiesde.codecentric.boot.admin.client.registration.CloudFoundryApplicationFactory→de.codecentric.boot.admin.client.config.CloudFoundryApplicationPropertiesde.codecentric.boot.admin.client.registration.CloudFoundryApplicationFactory→de.codecentric.boot.admin.client.config.InstancePropertiesde.codecentric.boot.admin.client.registration.DefaultApplicationFactory→de.codecentric.boot.admin.client.config.InstancePropertiesde.codecentric.boot.admin.client.registration.ReactiveApplicationFactory→de.codecentric.boot.admin.client.config.InstancePropertiesde.codecentric.boot.admin.client.registration.ServletApplicationFactory→de.codecentric.boot.admin.client.config.InstancePropertiesde.codecentric.boot.admin.client.registration.ServletContainerApplicationFactory→de.codecentric.boot.admin.client.config.InstanceProperties
- Direction
- de.codecentric.boot.admin.client.registration uses de.codecentric.boot.admin.client.config, so a change to de.codecentric.boot.admin.client.config can break de.codecentric.boot.admin.client.registration, while a change to de.codecentric.boot.admin.client.registration can't break de.codecentric.boot.admin.client.config.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
18→1 de.codecentric.boot.admin.server.eventstore uses de.codecentric.boot.admin.server.domain.values✕
- Connections
- 4 pairs of types, where a type in de.codecentric.boot.admin.server.eventstore uses a type in de.codecentric.boot.admin.server.domain.values.
- The types involved
de.codecentric.boot.admin.server.eventstore.1→de.codecentric.boot.admin.server.domain.values.InstanceIdde.codecentric.boot.admin.server.eventstore.ConcurrentMapEventStore→de.codecentric.boot.admin.server.domain.values.InstanceIdde.codecentric.boot.admin.server.eventstore.HazelcastEventStore→de.codecentric.boot.admin.server.domain.values.InstanceIdde.codecentric.boot.admin.server.eventstore.InstanceEventStore→de.codecentric.boot.admin.server.domain.values.InstanceId
- Direction
- de.codecentric.boot.admin.server.eventstore uses de.codecentric.boot.admin.server.domain.values, so a change to de.codecentric.boot.admin.server.domain.values can break de.codecentric.boot.admin.server.eventstore, while a change to de.codecentric.boot.admin.server.eventstore can't break de.codecentric.boot.admin.server.domain.values.
- Position
- Below the diagonal: de.codecentric.boot.admin.server.eventstore uses a module listed above it, which is the healthy direction.
18→8 de.codecentric.boot.admin.server.eventstore uses de.codecentric.boot.admin.server.domain.events✕
- Connections
- 6 pairs of types, where a type in de.codecentric.boot.admin.server.eventstore uses a type in de.codecentric.boot.admin.server.domain.events.
- The types involved
de.codecentric.boot.admin.server.eventstore.1→de.codecentric.boot.admin.server.domain.events.InstanceEventde.codecentric.boot.admin.server.eventstore.ConcurrentMapEventStore→de.codecentric.boot.admin.server.domain.events.InstanceEventde.codecentric.boot.admin.server.eventstore.HazelcastEventStore→de.codecentric.boot.admin.server.domain.events.InstanceEventde.codecentric.boot.admin.server.eventstore.InMemoryEventStore→de.codecentric.boot.admin.server.domain.events.InstanceEventde.codecentric.boot.admin.server.eventstore.InstanceEventPublisher→de.codecentric.boot.admin.server.domain.events.InstanceEventde.codecentric.boot.admin.server.eventstore.InstanceEventStore→de.codecentric.boot.admin.server.domain.events.InstanceEvent
- Direction
- de.codecentric.boot.admin.server.eventstore uses de.codecentric.boot.admin.server.domain.events, so a change to de.codecentric.boot.admin.server.domain.events can break de.codecentric.boot.admin.server.eventstore, while a change to de.codecentric.boot.admin.server.eventstore can't break de.codecentric.boot.admin.server.domain.events.
- Position
- Below the diagonal: de.codecentric.boot.admin.server.eventstore uses a module listed above it, which is the healthy direction.
19→9 de.codecentric.boot.admin.server.ui.web.reactive uses de.codecentric.boot.admin.server.ui.web✕
- Connections
- 2 pairs of types, where a type in de.codecentric.boot.admin.server.ui.web.reactive uses a type in de.codecentric.boot.admin.server.ui.web.
- The types involved
de.codecentric.boot.admin.server.ui.web.reactive.HomepageForwardingFilter→de.codecentric.boot.admin.server.ui.web.HomepageForwardingFilterConfigde.codecentric.boot.admin.server.ui.web.reactive.HomepageForwardingFilter→de.codecentric.boot.admin.server.ui.web.HomepageForwardingMatcher
- Direction
- de.codecentric.boot.admin.server.ui.web.reactive uses de.codecentric.boot.admin.server.ui.web, so a change to de.codecentric.boot.admin.server.ui.web can break de.codecentric.boot.admin.server.ui.web.reactive, while a change to de.codecentric.boot.admin.server.ui.web.reactive can't break de.codecentric.boot.admin.server.ui.web.
- Position
- Below the diagonal: de.codecentric.boot.admin.server.ui.web.reactive uses a module listed above it, which is the healthy direction.
20→9 de.codecentric.boot.admin.server.ui.web.servlet uses de.codecentric.boot.admin.server.ui.web✕
- Connections
- 2 pairs of types, where a type in de.codecentric.boot.admin.server.ui.web.servlet uses a type in de.codecentric.boot.admin.server.ui.web.
- The types involved
de.codecentric.boot.admin.server.ui.web.servlet.HomepageForwardingFilter→de.codecentric.boot.admin.server.ui.web.HomepageForwardingFilterConfigde.codecentric.boot.admin.server.ui.web.servlet.HomepageForwardingFilter→de.codecentric.boot.admin.server.ui.web.HomepageForwardingMatcher
- Direction
- de.codecentric.boot.admin.server.ui.web.servlet uses de.codecentric.boot.admin.server.ui.web, so a change to de.codecentric.boot.admin.server.ui.web can break de.codecentric.boot.admin.server.ui.web.servlet, while a change to de.codecentric.boot.admin.server.ui.web.servlet can't break de.codecentric.boot.admin.server.ui.web.
- Position
- Below the diagonal: de.codecentric.boot.admin.server.ui.web.servlet uses a module listed above it, which is the healthy direction.
21→1 de.codecentric.boot.admin.server.web.client.cookies uses de.codecentric.boot.admin.server.domain.values✕
- Connections
- 2 pairs of types, where a type in de.codecentric.boot.admin.server.web.client.cookies uses a type in de.codecentric.boot.admin.server.domain.values.
- The types involved
de.codecentric.boot.admin.server.web.client.cookies.JdkPerInstanceCookieStore→de.codecentric.boot.admin.server.domain.values.InstanceIdde.codecentric.boot.admin.server.web.client.cookies.PerInstanceCookieStore→de.codecentric.boot.admin.server.domain.values.InstanceId
- Direction
- de.codecentric.boot.admin.server.web.client.cookies uses de.codecentric.boot.admin.server.domain.values, so a change to de.codecentric.boot.admin.server.domain.values can break de.codecentric.boot.admin.server.web.client.cookies, while a change to de.codecentric.boot.admin.server.web.client.cookies can't break de.codecentric.boot.admin.server.domain.values.
- Position
- Below the diagonal: de.codecentric.boot.admin.server.web.client.cookies uses a module listed above it, which is the healthy direction.
21→8 de.codecentric.boot.admin.server.web.client.cookies uses de.codecentric.boot.admin.server.domain.events✕
- Connections
- 2 pairs of types, where a type in de.codecentric.boot.admin.server.web.client.cookies uses a type in de.codecentric.boot.admin.server.domain.events.
- The types involved
de.codecentric.boot.admin.server.web.client.cookies.CookieStoreCleanupTrigger→de.codecentric.boot.admin.server.domain.events.InstanceDeregisteredEventde.codecentric.boot.admin.server.web.client.cookies.CookieStoreCleanupTrigger→de.codecentric.boot.admin.server.domain.events.InstanceEvent
- Direction
- de.codecentric.boot.admin.server.web.client.cookies uses de.codecentric.boot.admin.server.domain.events, so a change to de.codecentric.boot.admin.server.domain.events can break de.codecentric.boot.admin.server.web.client.cookies, while a change to de.codecentric.boot.admin.server.web.client.cookies can't break de.codecentric.boot.admin.server.domain.events.
- Position
- Below the diagonal: de.codecentric.boot.admin.server.web.client.cookies uses a module listed above it, which is the healthy direction.
21→31 de.codecentric.boot.admin.server.web.client.cookies uses de.codecentric.boot.admin.server.services part of a loop✕
- Connections
- 1 pair of types, where a type in de.codecentric.boot.admin.server.web.client.cookies uses a type in de.codecentric.boot.admin.server.services.
- The types involved
de.codecentric.boot.admin.server.web.client.cookies.CookieStoreCleanupTrigger→de.codecentric.boot.admin.server.services.AbstractEventHandler
- Direction
- de.codecentric.boot.admin.server.web.client.cookies uses de.codecentric.boot.admin.server.services, so a change to de.codecentric.boot.admin.server.services can break de.codecentric.boot.admin.server.web.client.cookies, while a change to de.codecentric.boot.admin.server.web.client.cookies can't break de.codecentric.boot.admin.server.services.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
22→7 de.codecentric.boot.admin.client.config uses de.codecentric.boot.admin.client.registration.metadata✕
- Connections
- 6 pairs of types, where a type in de.codecentric.boot.admin.client.config uses a type in de.codecentric.boot.admin.client.registration.metadata.
- The types involved
de.codecentric.boot.admin.client.config.ReactiveConfiguration→de.codecentric.boot.admin.client.registration.metadata.MetadataContributorde.codecentric.boot.admin.client.config.ServletConfiguration→de.codecentric.boot.admin.client.registration.metadata.MetadataContributorde.codecentric.boot.admin.client.config.ServletContainerConfiguration→de.codecentric.boot.admin.client.registration.metadata.MetadataContributorde.codecentric.boot.admin.client.config.SpringBootAdminClientAutoConfiguration→de.codecentric.boot.admin.client.registration.metadata.StartupDateMetadataContributorde.codecentric.boot.admin.client.config.SpringBootAdminClientCloudFoundryAutoConfiguration→de.codecentric.boot.admin.client.registration.metadata.CloudFoundryMetadataContributorde.codecentric.boot.admin.client.config.SpringBootAdminClientCloudFoundryAutoConfiguration→de.codecentric.boot.admin.client.registration.metadata.MetadataContributor
- Direction
- de.codecentric.boot.admin.client.config uses de.codecentric.boot.admin.client.registration.metadata, so a change to de.codecentric.boot.admin.client.registration.metadata can break de.codecentric.boot.admin.client.config, while a change to de.codecentric.boot.admin.client.config can't break de.codecentric.boot.admin.client.registration.metadata.
- Position
- Below the diagonal: de.codecentric.boot.admin.client.config uses a module listed above it, which is the healthy direction.
22→17 de.codecentric.boot.admin.client.config uses de.codecentric.boot.admin.client.registration✕
- Connections
- 9 pairs of types, where a type in de.codecentric.boot.admin.client.config uses a type in de.codecentric.boot.admin.client.registration.
- The types involved
de.codecentric.boot.admin.client.config.ReactiveConfiguration→de.codecentric.boot.admin.client.registration.ApplicationFactoryde.codecentric.boot.admin.client.config.RestClientRegistrationClientConfig→de.codecentric.boot.admin.client.registration.RegistrationClientde.codecentric.boot.admin.client.config.ServletConfiguration→de.codecentric.boot.admin.client.registration.ApplicationFactoryde.codecentric.boot.admin.client.config.ServletContainerConfiguration→de.codecentric.boot.admin.client.registration.ApplicationFactoryde.codecentric.boot.admin.client.config.SpringBootAdminClientAutoConfiguration→de.codecentric.boot.admin.client.registration.ApplicationFactoryde.codecentric.boot.admin.client.config.SpringBootAdminClientAutoConfiguration→de.codecentric.boot.admin.client.registration.ApplicationRegistratorde.codecentric.boot.admin.client.config.SpringBootAdminClientAutoConfiguration→de.codecentric.boot.admin.client.registration.RegistrationApplicationListenerde.codecentric.boot.admin.client.config.SpringBootAdminClientAutoConfiguration→de.codecentric.boot.admin.client.registration.RegistrationClientde.codecentric.boot.admin.client.config.SpringBootAdminClientCloudFoundryAutoConfiguration→de.codecentric.boot.admin.client.registration.CloudFoundryApplicationFactory
- Direction
- de.codecentric.boot.admin.client.config uses de.codecentric.boot.admin.client.registration, so a change to de.codecentric.boot.admin.client.registration can break de.codecentric.boot.admin.client.config, while a change to de.codecentric.boot.admin.client.config can't break de.codecentric.boot.admin.client.registration.
- Position
- Below the diagonal: de.codecentric.boot.admin.client.config uses a module listed above it, which is the healthy direction.
23→1 de.codecentric.boot.admin.server.domain.entities uses de.codecentric.boot.admin.server.domain.values✕
- Connections
- 11 pairs of types, where a type in de.codecentric.boot.admin.server.domain.entities uses a type in de.codecentric.boot.admin.server.domain.values.
- The types involved
de.codecentric.boot.admin.server.domain.entities.Application→de.codecentric.boot.admin.server.domain.values.BuildVersionde.codecentric.boot.admin.server.domain.entities.EventsourcingInstanceRepository→de.codecentric.boot.admin.server.domain.values.InstanceIdde.codecentric.boot.admin.server.domain.entities.Instance→de.codecentric.boot.admin.server.domain.values.BuildVersionde.codecentric.boot.admin.server.domain.entities.Instance→de.codecentric.boot.admin.server.domain.values.Endpointsde.codecentric.boot.admin.server.domain.entities.Instance→de.codecentric.boot.admin.server.domain.values.Infode.codecentric.boot.admin.server.domain.entities.Instance→de.codecentric.boot.admin.server.domain.values.InstanceIdde.codecentric.boot.admin.server.domain.entities.Instance→de.codecentric.boot.admin.server.domain.values.Registrationde.codecentric.boot.admin.server.domain.entities.Instance→de.codecentric.boot.admin.server.domain.values.StatusInfode.codecentric.boot.admin.server.domain.entities.Instance→de.codecentric.boot.admin.server.domain.values.Tagsde.codecentric.boot.admin.server.domain.entities.InstanceRepository→de.codecentric.boot.admin.server.domain.values.InstanceIdde.codecentric.boot.admin.server.domain.entities.SnapshottingInstanceRepository→de.codecentric.boot.admin.server.domain.values.InstanceId
- Direction
- de.codecentric.boot.admin.server.domain.entities uses de.codecentric.boot.admin.server.domain.values, so a change to de.codecentric.boot.admin.server.domain.values can break de.codecentric.boot.admin.server.domain.entities, while a change to de.codecentric.boot.admin.server.domain.entities can't break de.codecentric.boot.admin.server.domain.values.
- Position
- Below the diagonal: de.codecentric.boot.admin.server.domain.entities uses a module listed above it, which is the healthy direction.
23→8 de.codecentric.boot.admin.server.domain.entities uses de.codecentric.boot.admin.server.domain.events✕
- Connections
- 3 pairs of types, where a type in de.codecentric.boot.admin.server.domain.entities uses a type in de.codecentric.boot.admin.server.domain.events.
- The types involved
de.codecentric.boot.admin.server.domain.entities.EventsourcingInstanceRepository→de.codecentric.boot.admin.server.domain.events.InstanceEventde.codecentric.boot.admin.server.domain.entities.Instance→de.codecentric.boot.admin.server.domain.events.InstanceEventde.codecentric.boot.admin.server.domain.entities.SnapshottingInstanceRepository→de.codecentric.boot.admin.server.domain.events.InstanceEvent
- Direction
- de.codecentric.boot.admin.server.domain.entities uses de.codecentric.boot.admin.server.domain.events, so a change to de.codecentric.boot.admin.server.domain.events can break de.codecentric.boot.admin.server.domain.entities, while a change to de.codecentric.boot.admin.server.domain.entities can't break de.codecentric.boot.admin.server.domain.events.
- Position
- Below the diagonal: de.codecentric.boot.admin.server.domain.entities uses a module listed above it, which is the healthy direction.
23→18 de.codecentric.boot.admin.server.domain.entities uses de.codecentric.boot.admin.server.eventstore✕
- Connections
- 2 pairs of types, where a type in de.codecentric.boot.admin.server.domain.entities uses a type in de.codecentric.boot.admin.server.eventstore.
- The types involved
de.codecentric.boot.admin.server.domain.entities.EventsourcingInstanceRepository→de.codecentric.boot.admin.server.eventstore.InstanceEventStorede.codecentric.boot.admin.server.domain.entities.SnapshottingInstanceRepository→de.codecentric.boot.admin.server.eventstore.InstanceEventStore
- Direction
- de.codecentric.boot.admin.server.domain.entities uses de.codecentric.boot.admin.server.eventstore, so a change to de.codecentric.boot.admin.server.eventstore can break de.codecentric.boot.admin.server.domain.entities, while a change to de.codecentric.boot.admin.server.domain.entities can't break de.codecentric.boot.admin.server.eventstore.
- Position
- Below the diagonal: de.codecentric.boot.admin.server.domain.entities uses a module listed above it, which is the healthy direction.
24→1 de.codecentric.boot.admin.server.notify.filter uses de.codecentric.boot.admin.server.domain.values✕
- Connections
- 1 pair of types, where a type in de.codecentric.boot.admin.server.notify.filter uses a type in de.codecentric.boot.admin.server.domain.values.
- The types involved
de.codecentric.boot.admin.server.notify.filter.InstanceIdNotificationFilter→de.codecentric.boot.admin.server.domain.values.InstanceId
- Direction
- de.codecentric.boot.admin.server.notify.filter uses de.codecentric.boot.admin.server.domain.values, so a change to de.codecentric.boot.admin.server.domain.values can break de.codecentric.boot.admin.server.notify.filter, while a change to de.codecentric.boot.admin.server.notify.filter can't break de.codecentric.boot.admin.server.domain.values.
- Position
- Below the diagonal: de.codecentric.boot.admin.server.notify.filter uses a module listed above it, which is the healthy direction.
24→8 de.codecentric.boot.admin.server.notify.filter uses de.codecentric.boot.admin.server.domain.events✕
- Connections
- 6 pairs of types, where a type in de.codecentric.boot.admin.server.notify.filter uses a type in de.codecentric.boot.admin.server.domain.events.
- The types involved
de.codecentric.boot.admin.server.notify.filter.AbstractContentNotifier→de.codecentric.boot.admin.server.domain.events.InstanceEventde.codecentric.boot.admin.server.notify.filter.ApplicationNameNotificationFilter→de.codecentric.boot.admin.server.domain.events.InstanceEventde.codecentric.boot.admin.server.notify.filter.ExpiringNotificationFilter→de.codecentric.boot.admin.server.domain.events.InstanceEventde.codecentric.boot.admin.server.notify.filter.FilteringNotifier→de.codecentric.boot.admin.server.domain.events.InstanceEventde.codecentric.boot.admin.server.notify.filter.InstanceIdNotificationFilter→de.codecentric.boot.admin.server.domain.events.InstanceEventde.codecentric.boot.admin.server.notify.filter.NotificationFilter→de.codecentric.boot.admin.server.domain.events.InstanceEvent
- Direction
- de.codecentric.boot.admin.server.notify.filter uses de.codecentric.boot.admin.server.domain.events, so a change to de.codecentric.boot.admin.server.domain.events can break de.codecentric.boot.admin.server.notify.filter, while a change to de.codecentric.boot.admin.server.notify.filter can't break de.codecentric.boot.admin.server.domain.events.
- Position
- Below the diagonal: de.codecentric.boot.admin.server.notify.filter uses a module listed above it, which is the healthy direction.
24→23 de.codecentric.boot.admin.server.notify.filter uses de.codecentric.boot.admin.server.domain.entities✕
- Connections
- 8 pairs of types, where a type in de.codecentric.boot.admin.server.notify.filter uses a type in de.codecentric.boot.admin.server.domain.entities.
- The types involved
de.codecentric.boot.admin.server.notify.filter.AbstractContentNotifier→de.codecentric.boot.admin.server.domain.entities.Instancede.codecentric.boot.admin.server.notify.filter.AbstractContentNotifier→de.codecentric.boot.admin.server.domain.entities.InstanceRepositoryde.codecentric.boot.admin.server.notify.filter.ApplicationNameNotificationFilter→de.codecentric.boot.admin.server.domain.entities.Instancede.codecentric.boot.admin.server.notify.filter.ExpiringNotificationFilter→de.codecentric.boot.admin.server.domain.entities.Instancede.codecentric.boot.admin.server.notify.filter.FilteringNotifier→de.codecentric.boot.admin.server.domain.entities.Instancede.codecentric.boot.admin.server.notify.filter.FilteringNotifier→de.codecentric.boot.admin.server.domain.entities.InstanceRepositoryde.codecentric.boot.admin.server.notify.filter.InstanceIdNotificationFilter→de.codecentric.boot.admin.server.domain.entities.Instancede.codecentric.boot.admin.server.notify.filter.NotificationFilter→de.codecentric.boot.admin.server.domain.entities.Instance
- Direction
- de.codecentric.boot.admin.server.notify.filter uses de.codecentric.boot.admin.server.domain.entities, so a change to de.codecentric.boot.admin.server.domain.entities can break de.codecentric.boot.admin.server.notify.filter, while a change to de.codecentric.boot.admin.server.notify.filter can't break de.codecentric.boot.admin.server.domain.entities.
- Position
- Below the diagonal: de.codecentric.boot.admin.server.notify.filter uses a module listed above it, which is the healthy direction.
24→33 de.codecentric.boot.admin.server.notify.filter uses de.codecentric.boot.admin.server.notify part of a loop✕
- Connections
- 3 pairs of types, where a type in de.codecentric.boot.admin.server.notify.filter uses a type in de.codecentric.boot.admin.server.notify.
- The types involved
de.codecentric.boot.admin.server.notify.filter.AbstractContentNotifier→de.codecentric.boot.admin.server.notify.AbstractStatusChangeNotifierde.codecentric.boot.admin.server.notify.filter.FilteringNotifier→de.codecentric.boot.admin.server.notify.AbstractEventNotifierde.codecentric.boot.admin.server.notify.filter.FilteringNotifier→de.codecentric.boot.admin.server.notify.Notifier
- Direction
- de.codecentric.boot.admin.server.notify.filter uses de.codecentric.boot.admin.server.notify, so a change to de.codecentric.boot.admin.server.notify can break de.codecentric.boot.admin.server.notify.filter, while a change to de.codecentric.boot.admin.server.notify.filter can't break de.codecentric.boot.admin.server.notify.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
25→23 de.codecentric.boot.admin.server.web.client.reactive uses de.codecentric.boot.admin.server.domain.entities✕
- Connections
- 2 pairs of types, where a type in de.codecentric.boot.admin.server.web.client.reactive uses a type in de.codecentric.boot.admin.server.domain.entities.
- The types involved
de.codecentric.boot.admin.server.web.client.reactive.CompositeReactiveHttpHeadersProvider→de.codecentric.boot.admin.server.domain.entities.Instancede.codecentric.boot.admin.server.web.client.reactive.ReactiveHttpHeadersProvider→de.codecentric.boot.admin.server.domain.entities.Instance
- Direction
- de.codecentric.boot.admin.server.web.client.reactive uses de.codecentric.boot.admin.server.domain.entities, so a change to de.codecentric.boot.admin.server.domain.entities can break de.codecentric.boot.admin.server.web.client.reactive, while a change to de.codecentric.boot.admin.server.web.client.reactive can't break de.codecentric.boot.admin.server.domain.entities.
- Position
- Below the diagonal: de.codecentric.boot.admin.server.web.client.reactive uses a module listed above it, which is the healthy direction.
26→1 de.codecentric.boot.admin.server.notify.filter.web uses de.codecentric.boot.admin.server.domain.values✕
- Connections
- 1 pair of types, where a type in de.codecentric.boot.admin.server.notify.filter.web uses a type in de.codecentric.boot.admin.server.domain.values.
- The types involved
de.codecentric.boot.admin.server.notify.filter.web.NotificationFilterController→de.codecentric.boot.admin.server.domain.values.InstanceId
- Direction
- de.codecentric.boot.admin.server.notify.filter.web uses de.codecentric.boot.admin.server.domain.values, so a change to de.codecentric.boot.admin.server.domain.values can break de.codecentric.boot.admin.server.notify.filter.web, while a change to de.codecentric.boot.admin.server.notify.filter.web can't break de.codecentric.boot.admin.server.domain.values.
- Position
- Below the diagonal: de.codecentric.boot.admin.server.notify.filter.web uses a module listed above it, which is the healthy direction.
26→24 de.codecentric.boot.admin.server.notify.filter.web uses de.codecentric.boot.admin.server.notify.filter✕
- Connections
- 2 pairs of types, where a type in de.codecentric.boot.admin.server.notify.filter.web uses a type in de.codecentric.boot.admin.server.notify.filter.
- The types involved
de.codecentric.boot.admin.server.notify.filter.web.NotificationFilterController→de.codecentric.boot.admin.server.notify.filter.FilteringNotifierde.codecentric.boot.admin.server.notify.filter.web.NotificationFilterController→de.codecentric.boot.admin.server.notify.filter.NotificationFilter
- Direction
- de.codecentric.boot.admin.server.notify.filter.web uses de.codecentric.boot.admin.server.notify.filter, so a change to de.codecentric.boot.admin.server.notify.filter can break de.codecentric.boot.admin.server.notify.filter.web, while a change to de.codecentric.boot.admin.server.notify.filter.web can't break de.codecentric.boot.admin.server.notify.filter.
- Position
- Below the diagonal: de.codecentric.boot.admin.server.notify.filter.web uses a module listed above it, which is the healthy direction.
27→1 de.codecentric.boot.admin.server.web.client uses de.codecentric.boot.admin.server.domain.values✕
- Connections
- 1 pair of types, where a type in de.codecentric.boot.admin.server.web.client uses a type in de.codecentric.boot.admin.server.domain.values.
- The types involved
de.codecentric.boot.admin.server.web.client.InstanceExchangeFilterFunctions→de.codecentric.boot.admin.server.domain.values.InstanceId
- Direction
- de.codecentric.boot.admin.server.web.client uses de.codecentric.boot.admin.server.domain.values, so a change to de.codecentric.boot.admin.server.domain.values can break de.codecentric.boot.admin.server.web.client, while a change to de.codecentric.boot.admin.server.web.client can't break de.codecentric.boot.admin.server.domain.values.
- Position
- Below the diagonal: de.codecentric.boot.admin.server.web.client uses a module listed above it, which is the healthy direction.
27→21 de.codecentric.boot.admin.server.web.client uses de.codecentric.boot.admin.server.web.client.cookies✕
- Connections
- 1 pair of types, where a type in de.codecentric.boot.admin.server.web.client uses a type in de.codecentric.boot.admin.server.web.client.cookies.
- The types involved
de.codecentric.boot.admin.server.web.client.InstanceExchangeFilterFunctions→de.codecentric.boot.admin.server.web.client.cookies.PerInstanceCookieStore
- Direction
- de.codecentric.boot.admin.server.web.client uses de.codecentric.boot.admin.server.web.client.cookies, so a change to de.codecentric.boot.admin.server.web.client.cookies can break de.codecentric.boot.admin.server.web.client, while a change to de.codecentric.boot.admin.server.web.client can't break de.codecentric.boot.admin.server.web.client.cookies.
- Position
- Below the diagonal: de.codecentric.boot.admin.server.web.client uses a module listed above it, which is the healthy direction.
27→23 de.codecentric.boot.admin.server.web.client uses de.codecentric.boot.admin.server.domain.entities✕
- Connections
- 6 pairs of types, where a type in de.codecentric.boot.admin.server.web.client uses a type in de.codecentric.boot.admin.server.domain.entities.
- The types involved
de.codecentric.boot.admin.server.web.client.BasicAuthHttpHeaderProvider→de.codecentric.boot.admin.server.domain.entities.Instancede.codecentric.boot.admin.server.web.client.CloudFoundryHttpHeaderProvider→de.codecentric.boot.admin.server.domain.entities.Instancede.codecentric.boot.admin.server.web.client.CompositeHttpHeadersProvider→de.codecentric.boot.admin.server.domain.entities.Instancede.codecentric.boot.admin.server.web.client.HttpHeadersProvider→de.codecentric.boot.admin.server.domain.entities.Instancede.codecentric.boot.admin.server.web.client.InstanceExchangeFilterFunction→de.codecentric.boot.admin.server.domain.entities.Instancede.codecentric.boot.admin.server.web.client.InstanceWebClient→de.codecentric.boot.admin.server.domain.entities.Instance
- Direction
- de.codecentric.boot.admin.server.web.client uses de.codecentric.boot.admin.server.domain.entities, so a change to de.codecentric.boot.admin.server.domain.entities can break de.codecentric.boot.admin.server.web.client, while a change to de.codecentric.boot.admin.server.web.client can't break de.codecentric.boot.admin.server.domain.entities.
- Position
- Below the diagonal: de.codecentric.boot.admin.server.web.client uses a module listed above it, which is the healthy direction.
27→25 de.codecentric.boot.admin.server.web.client uses de.codecentric.boot.admin.server.web.client.reactive✕
- Connections
- 1 pair of types, where a type in de.codecentric.boot.admin.server.web.client uses a type in de.codecentric.boot.admin.server.web.client.reactive.
- The types involved
de.codecentric.boot.admin.server.web.client.InstanceExchangeFilterFunctions→de.codecentric.boot.admin.server.web.client.reactive.ReactiveHttpHeadersProvider
- Direction
- de.codecentric.boot.admin.server.web.client uses de.codecentric.boot.admin.server.web.client.reactive, so a change to de.codecentric.boot.admin.server.web.client.reactive can break de.codecentric.boot.admin.server.web.client, while a change to de.codecentric.boot.admin.server.web.client can't break de.codecentric.boot.admin.server.web.client.reactive.
- Position
- Below the diagonal: de.codecentric.boot.admin.server.web.client uses a module listed above it, which is the healthy direction.
28→23 de.codecentric.boot.admin.server.mcp.tools uses de.codecentric.boot.admin.server.domain.entities✕
- Connections
- 3 pairs of types, where a type in de.codecentric.boot.admin.server.mcp.tools uses a type in de.codecentric.boot.admin.server.domain.entities.
- The types involved
de.codecentric.boot.admin.server.mcp.tools.ActuatorClient→de.codecentric.boot.admin.server.domain.entities.Instancede.codecentric.boot.admin.server.mcp.tools.ActuatorClient→de.codecentric.boot.admin.server.domain.entities.InstanceRepositoryde.codecentric.boot.admin.server.mcp.tools.ApplicationTools→de.codecentric.boot.admin.server.domain.entities.InstanceRepository
- Direction
- de.codecentric.boot.admin.server.mcp.tools uses de.codecentric.boot.admin.server.domain.entities, so a change to de.codecentric.boot.admin.server.domain.entities can break de.codecentric.boot.admin.server.mcp.tools, while a change to de.codecentric.boot.admin.server.mcp.tools can't break de.codecentric.boot.admin.server.domain.entities.
- Position
- Below the diagonal: de.codecentric.boot.admin.server.mcp.tools uses a module listed above it, which is the healthy direction.
28→27 de.codecentric.boot.admin.server.mcp.tools uses de.codecentric.boot.admin.server.web.client✕
- Connections
- 1 pair of types, where a type in de.codecentric.boot.admin.server.mcp.tools uses a type in de.codecentric.boot.admin.server.web.client.
- The types involved
de.codecentric.boot.admin.server.mcp.tools.ActuatorClient→de.codecentric.boot.admin.server.web.client.InstanceWebClient
- Direction
- de.codecentric.boot.admin.server.mcp.tools uses de.codecentric.boot.admin.server.web.client, so a change to de.codecentric.boot.admin.server.web.client can break de.codecentric.boot.admin.server.mcp.tools, while a change to de.codecentric.boot.admin.server.mcp.tools can't break de.codecentric.boot.admin.server.web.client.
- Position
- Below the diagonal: de.codecentric.boot.admin.server.mcp.tools uses a module listed above it, which is the healthy direction.
29→1 de.codecentric.boot.admin.server.services.endpoints uses de.codecentric.boot.admin.server.domain.values✕
- Connections
- 7 pairs of types, where a type in de.codecentric.boot.admin.server.services.endpoints uses a type in de.codecentric.boot.admin.server.domain.values.
- The types involved
de.codecentric.boot.admin.server.services.endpoints.ChainingStrategy→de.codecentric.boot.admin.server.domain.values.Endpointsde.codecentric.boot.admin.server.services.endpoints.DetectedEndpoint→de.codecentric.boot.admin.server.domain.values.Endpointde.codecentric.boot.admin.server.services.endpoints.EndpointDetectionStrategy→de.codecentric.boot.admin.server.domain.values.Endpointsde.codecentric.boot.admin.server.services.endpoints.ProbeEndpointsStrategy→de.codecentric.boot.admin.server.domain.values.Endpointsde.codecentric.boot.admin.server.services.endpoints.ProbeEndpointsStrategy→de.codecentric.boot.admin.server.domain.values.InstanceIdde.codecentric.boot.admin.server.services.endpoints.QueryIndexEndpointStrategy→de.codecentric.boot.admin.server.domain.values.Endpointsde.codecentric.boot.admin.server.services.endpoints.QueryIndexEndpointStrategy→de.codecentric.boot.admin.server.domain.values.InstanceId
- Direction
- de.codecentric.boot.admin.server.services.endpoints uses de.codecentric.boot.admin.server.domain.values, so a change to de.codecentric.boot.admin.server.domain.values can break de.codecentric.boot.admin.server.services.endpoints, while a change to de.codecentric.boot.admin.server.services.endpoints can't break de.codecentric.boot.admin.server.domain.values.
- Position
- Below the diagonal: de.codecentric.boot.admin.server.services.endpoints uses a module listed above it, which is the healthy direction.
29→23 de.codecentric.boot.admin.server.services.endpoints uses de.codecentric.boot.admin.server.domain.entities✕
- Connections
- 4 pairs of types, where a type in de.codecentric.boot.admin.server.services.endpoints uses a type in de.codecentric.boot.admin.server.domain.entities.
- The types involved
de.codecentric.boot.admin.server.services.endpoints.ChainingStrategy→de.codecentric.boot.admin.server.domain.entities.Instancede.codecentric.boot.admin.server.services.endpoints.EndpointDetectionStrategy→de.codecentric.boot.admin.server.domain.entities.Instancede.codecentric.boot.admin.server.services.endpoints.ProbeEndpointsStrategy→de.codecentric.boot.admin.server.domain.entities.Instancede.codecentric.boot.admin.server.services.endpoints.QueryIndexEndpointStrategy→de.codecentric.boot.admin.server.domain.entities.Instance
- Direction
- de.codecentric.boot.admin.server.services.endpoints uses de.codecentric.boot.admin.server.domain.entities, so a change to de.codecentric.boot.admin.server.domain.entities can break de.codecentric.boot.admin.server.services.endpoints, while a change to de.codecentric.boot.admin.server.services.endpoints can't break de.codecentric.boot.admin.server.domain.entities.
- Position
- Below the diagonal: de.codecentric.boot.admin.server.services.endpoints uses a module listed above it, which is the healthy direction.
29→27 de.codecentric.boot.admin.server.services.endpoints uses de.codecentric.boot.admin.server.web.client✕
- Connections
- 2 pairs of types, where a type in de.codecentric.boot.admin.server.services.endpoints uses a type in de.codecentric.boot.admin.server.web.client.
- The types involved
de.codecentric.boot.admin.server.services.endpoints.ProbeEndpointsStrategy→de.codecentric.boot.admin.server.web.client.InstanceWebClientde.codecentric.boot.admin.server.services.endpoints.QueryIndexEndpointStrategy→de.codecentric.boot.admin.server.web.client.InstanceWebClient
- Direction
- de.codecentric.boot.admin.server.services.endpoints uses de.codecentric.boot.admin.server.web.client, so a change to de.codecentric.boot.admin.server.web.client can break de.codecentric.boot.admin.server.services.endpoints, while a change to de.codecentric.boot.admin.server.services.endpoints can't break de.codecentric.boot.admin.server.web.client.
- Position
- Below the diagonal: de.codecentric.boot.admin.server.services.endpoints uses a module listed above it, which is the healthy direction.
29→31 de.codecentric.boot.admin.server.services.endpoints uses de.codecentric.boot.admin.server.services part of a loop✕
- Connections
- 1 pair of types, where a type in de.codecentric.boot.admin.server.services.endpoints uses a type in de.codecentric.boot.admin.server.services.
- The types involved
de.codecentric.boot.admin.server.services.endpoints.QueryIndexEndpointStrategy→de.codecentric.boot.admin.server.services.ApiMediaTypeHandler
- Direction
- de.codecentric.boot.admin.server.services.endpoints uses de.codecentric.boot.admin.server.services, so a change to de.codecentric.boot.admin.server.services can break de.codecentric.boot.admin.server.services.endpoints, while a change to de.codecentric.boot.admin.server.services.endpoints can't break de.codecentric.boot.admin.server.services.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
30→23 de.codecentric.boot.admin.server.mcp.config uses de.codecentric.boot.admin.server.domain.entities✕
- Connections
- 1 pair of types, where a type in de.codecentric.boot.admin.server.mcp.config uses a type in de.codecentric.boot.admin.server.domain.entities.
- The types involved
de.codecentric.boot.admin.server.mcp.config.McpAutoConfiguration→de.codecentric.boot.admin.server.domain.entities.InstanceRepository
- Direction
- de.codecentric.boot.admin.server.mcp.config uses de.codecentric.boot.admin.server.domain.entities, so a change to de.codecentric.boot.admin.server.domain.entities can break de.codecentric.boot.admin.server.mcp.config, while a change to de.codecentric.boot.admin.server.mcp.config can't break de.codecentric.boot.admin.server.domain.entities.
- Position
- Below the diagonal: de.codecentric.boot.admin.server.mcp.config uses a module listed above it, which is the healthy direction.
30→27 de.codecentric.boot.admin.server.mcp.config uses de.codecentric.boot.admin.server.web.client✕
- Connections
- 1 pair of types, where a type in de.codecentric.boot.admin.server.mcp.config uses a type in de.codecentric.boot.admin.server.web.client.
- The types involved
de.codecentric.boot.admin.server.mcp.config.McpAutoConfiguration→de.codecentric.boot.admin.server.web.client.Builder
- Direction
- de.codecentric.boot.admin.server.mcp.config uses de.codecentric.boot.admin.server.web.client, so a change to de.codecentric.boot.admin.server.web.client can break de.codecentric.boot.admin.server.mcp.config, while a change to de.codecentric.boot.admin.server.mcp.config can't break de.codecentric.boot.admin.server.web.client.
- Position
- Below the diagonal: de.codecentric.boot.admin.server.mcp.config uses a module listed above it, which is the healthy direction.
30→28 de.codecentric.boot.admin.server.mcp.config uses de.codecentric.boot.admin.server.mcp.tools✕
- Connections
- 13 pairs of types, where a type in de.codecentric.boot.admin.server.mcp.config uses a type in de.codecentric.boot.admin.server.mcp.tools.
- The types involved
de.codecentric.boot.admin.server.mcp.config.McpAutoConfiguration→de.codecentric.boot.admin.server.mcp.tools.ActuatorClientde.codecentric.boot.admin.server.mcp.config.McpAutoConfiguration→de.codecentric.boot.admin.server.mcp.tools.ApplicationToolsde.codecentric.boot.admin.server.mcp.config.McpAutoConfiguration→de.codecentric.boot.admin.server.mcp.tools.BeansToolsde.codecentric.boot.admin.server.mcp.config.McpAutoConfiguration→de.codecentric.boot.admin.server.mcp.tools.CachesToolsde.codecentric.boot.admin.server.mcp.config.McpAutoConfiguration→de.codecentric.boot.admin.server.mcp.tools.EnvToolsde.codecentric.boot.admin.server.mcp.config.McpAutoConfiguration→de.codecentric.boot.admin.server.mcp.tools.HealthToolsde.codecentric.boot.admin.server.mcp.config.McpAutoConfiguration→de.codecentric.boot.admin.server.mcp.tools.HttpExchangesToolsde.codecentric.boot.admin.server.mcp.config.McpAutoConfiguration→de.codecentric.boot.admin.server.mcp.tools.LoggersToolsde.codecentric.boot.admin.server.mcp.config.McpAutoConfiguration→de.codecentric.boot.admin.server.mcp.tools.LogsToolsde.codecentric.boot.admin.server.mcp.config.McpAutoConfiguration→de.codecentric.boot.admin.server.mcp.tools.MetricsToolsde.codecentric.boot.admin.server.mcp.config.McpAutoConfiguration→de.codecentric.boot.admin.server.mcp.tools.OperationsToolsde.codecentric.boot.admin.server.mcp.config.McpAutoConfiguration→de.codecentric.boot.admin.server.mcp.tools.ScheduledTasksToolsde.codecentric.boot.admin.server.mcp.config.McpAutoConfiguration→de.codecentric.boot.admin.server.mcp.tools.ThreadDumpTools
- Direction
- de.codecentric.boot.admin.server.mcp.config uses de.codecentric.boot.admin.server.mcp.tools, so a change to de.codecentric.boot.admin.server.mcp.tools can break de.codecentric.boot.admin.server.mcp.config, while a change to de.codecentric.boot.admin.server.mcp.config can't break de.codecentric.boot.admin.server.mcp.tools.
- Position
- Below the diagonal: de.codecentric.boot.admin.server.mcp.config uses a module listed above it, which is the healthy direction.
31→1 de.codecentric.boot.admin.server.services uses de.codecentric.boot.admin.server.domain.values✕
- Connections
- 20 pairs of types, where a type in de.codecentric.boot.admin.server.services uses a type in de.codecentric.boot.admin.server.domain.values.
- The types involved
de.codecentric.boot.admin.server.services.ApplicationRegistry→de.codecentric.boot.admin.server.domain.values.BuildVersionde.codecentric.boot.admin.server.services.ApplicationRegistry→de.codecentric.boot.admin.server.domain.values.InstanceIdde.codecentric.boot.admin.server.services.CloudFoundryInstanceIdGenerator→de.codecentric.boot.admin.server.domain.values.InstanceIdde.codecentric.boot.admin.server.services.CloudFoundryInstanceIdGenerator→de.codecentric.boot.admin.server.domain.values.Registrationde.codecentric.boot.admin.server.services.EndpointDetector→de.codecentric.boot.admin.server.domain.values.InstanceIdde.codecentric.boot.admin.server.services.HashingInstanceUrlIdGenerator→de.codecentric.boot.admin.server.domain.values.InstanceIdde.codecentric.boot.admin.server.services.HashingInstanceUrlIdGenerator→de.codecentric.boot.admin.server.domain.values.Registrationde.codecentric.boot.admin.server.services.HealthGroupsCache→de.codecentric.boot.admin.server.domain.values.InstanceIdde.codecentric.boot.admin.server.services.InMemoryHealthGroupsCache→de.codecentric.boot.admin.server.domain.values.InstanceIdde.codecentric.boot.admin.server.services.InfoUpdateTrigger→de.codecentric.boot.admin.server.domain.values.InstanceIdde.codecentric.boot.admin.server.services.InfoUpdater→de.codecentric.boot.admin.server.domain.values.Infode.codecentric.boot.admin.server.services.InfoUpdater→de.codecentric.boot.admin.server.domain.values.InstanceIdde.codecentric.boot.admin.server.services.InstanceIdGenerator→de.codecentric.boot.admin.server.domain.values.InstanceIdde.codecentric.boot.admin.server.services.InstanceIdGenerator→de.codecentric.boot.admin.server.domain.values.Registrationde.codecentric.boot.admin.server.services.InstanceRegistry→de.codecentric.boot.admin.server.domain.values.InstanceIdde.codecentric.boot.admin.server.services.InstanceRegistry→de.codecentric.boot.admin.server.domain.values.Registrationde.codecentric.boot.admin.server.services.IntervalCheck→de.codecentric.boot.admin.server.domain.values.InstanceIdde.codecentric.boot.admin.server.services.StatusUpdateTrigger→de.codecentric.boot.admin.server.domain.values.InstanceIdde.codecentric.boot.admin.server.services.StatusUpdater→de.codecentric.boot.admin.server.domain.values.InstanceIdde.codecentric.boot.admin.server.services.StatusUpdater→de.codecentric.boot.admin.server.domain.values.StatusInfo
- Direction
- de.codecentric.boot.admin.server.services uses de.codecentric.boot.admin.server.domain.values, so a change to de.codecentric.boot.admin.server.domain.values can break de.codecentric.boot.admin.server.services, while a change to de.codecentric.boot.admin.server.services can't break de.codecentric.boot.admin.server.domain.values.
- Position
- Below the diagonal: de.codecentric.boot.admin.server.services uses a module listed above it, which is the healthy direction.
31→8 de.codecentric.boot.admin.server.services uses de.codecentric.boot.admin.server.domain.events✕
- Connections
- 5 pairs of types, where a type in de.codecentric.boot.admin.server.services uses a type in de.codecentric.boot.admin.server.domain.events.
- The types involved
de.codecentric.boot.admin.server.services.AbstractEventHandler→de.codecentric.boot.admin.server.domain.events.InstanceEventde.codecentric.boot.admin.server.services.EndpointDetectionTrigger→de.codecentric.boot.admin.server.domain.events.InstanceEventde.codecentric.boot.admin.server.services.HealthGroupsCacheCleanupListener→de.codecentric.boot.admin.server.domain.events.InstanceEventde.codecentric.boot.admin.server.services.InfoUpdateTrigger→de.codecentric.boot.admin.server.domain.events.InstanceEventde.codecentric.boot.admin.server.services.StatusUpdateTrigger→de.codecentric.boot.admin.server.domain.events.InstanceEvent
- Direction
- de.codecentric.boot.admin.server.services uses de.codecentric.boot.admin.server.domain.events, so a change to de.codecentric.boot.admin.server.domain.events can break de.codecentric.boot.admin.server.services, while a change to de.codecentric.boot.admin.server.services can't break de.codecentric.boot.admin.server.domain.events.
- Position
- Below the diagonal: de.codecentric.boot.admin.server.services uses a module listed above it, which is the healthy direction.
31→10 de.codecentric.boot.admin.server.services uses de.codecentric.boot.admin.server.utils✕
- Connections
- 1 pair of types, where a type in de.codecentric.boot.admin.server.services uses a type in de.codecentric.boot.admin.server.utils.
- The types involved
de.codecentric.boot.admin.server.services.InstanceRegistry→de.codecentric.boot.admin.server.utils.SsrfUrlValidator
- Direction
- de.codecentric.boot.admin.server.services uses de.codecentric.boot.admin.server.utils, so a change to de.codecentric.boot.admin.server.utils can break de.codecentric.boot.admin.server.services, while a change to de.codecentric.boot.admin.server.services can't break de.codecentric.boot.admin.server.utils.
- Position
- Below the diagonal: de.codecentric.boot.admin.server.services uses a module listed above it, which is the healthy direction.
31→18 de.codecentric.boot.admin.server.services uses de.codecentric.boot.admin.server.eventstore✕
- Connections
- 1 pair of types, where a type in de.codecentric.boot.admin.server.services uses a type in de.codecentric.boot.admin.server.eventstore.
- The types involved
de.codecentric.boot.admin.server.services.ApplicationRegistry→de.codecentric.boot.admin.server.eventstore.InstanceEventPublisher
- Direction
- de.codecentric.boot.admin.server.services uses de.codecentric.boot.admin.server.eventstore, so a change to de.codecentric.boot.admin.server.eventstore can break de.codecentric.boot.admin.server.services, while a change to de.codecentric.boot.admin.server.services can't break de.codecentric.boot.admin.server.eventstore.
- Position
- Below the diagonal: de.codecentric.boot.admin.server.services uses a module listed above it, which is the healthy direction.
31→23 de.codecentric.boot.admin.server.services uses de.codecentric.boot.admin.server.domain.entities✕
- Connections
- 11 pairs of types, where a type in de.codecentric.boot.admin.server.services uses a type in de.codecentric.boot.admin.server.domain.entities.
- The types involved
de.codecentric.boot.admin.server.services.ApplicationRegistry→de.codecentric.boot.admin.server.domain.entities.Applicationde.codecentric.boot.admin.server.services.ApplicationRegistry→de.codecentric.boot.admin.server.domain.entities.Instancede.codecentric.boot.admin.server.services.EndpointDetector→de.codecentric.boot.admin.server.domain.entities.Instancede.codecentric.boot.admin.server.services.EndpointDetector→de.codecentric.boot.admin.server.domain.entities.InstanceRepositoryde.codecentric.boot.admin.server.services.InfoUpdater→de.codecentric.boot.admin.server.domain.entities.Instancede.codecentric.boot.admin.server.services.InfoUpdater→de.codecentric.boot.admin.server.domain.entities.InstanceRepositoryde.codecentric.boot.admin.server.services.InstanceFilter→de.codecentric.boot.admin.server.domain.entities.Instancede.codecentric.boot.admin.server.services.InstanceRegistry→de.codecentric.boot.admin.server.domain.entities.Instancede.codecentric.boot.admin.server.services.InstanceRegistry→de.codecentric.boot.admin.server.domain.entities.InstanceRepositoryde.codecentric.boot.admin.server.services.StatusUpdater→de.codecentric.boot.admin.server.domain.entities.Instancede.codecentric.boot.admin.server.services.StatusUpdater→de.codecentric.boot.admin.server.domain.entities.InstanceRepository
- Direction
- de.codecentric.boot.admin.server.services uses de.codecentric.boot.admin.server.domain.entities, so a change to de.codecentric.boot.admin.server.domain.entities can break de.codecentric.boot.admin.server.services, while a change to de.codecentric.boot.admin.server.services can't break de.codecentric.boot.admin.server.domain.entities.
- Position
- Below the diagonal: de.codecentric.boot.admin.server.services uses a module listed above it, which is the healthy direction.
31→27 de.codecentric.boot.admin.server.services uses de.codecentric.boot.admin.server.web.client✕
- Connections
- 2 pairs of types, where a type in de.codecentric.boot.admin.server.services uses a type in de.codecentric.boot.admin.server.web.client.
- The types involved
de.codecentric.boot.admin.server.services.InfoUpdater→de.codecentric.boot.admin.server.web.client.InstanceWebClientde.codecentric.boot.admin.server.services.StatusUpdater→de.codecentric.boot.admin.server.web.client.InstanceWebClient
- Direction
- de.codecentric.boot.admin.server.services uses de.codecentric.boot.admin.server.web.client, so a change to de.codecentric.boot.admin.server.web.client can break de.codecentric.boot.admin.server.services, while a change to de.codecentric.boot.admin.server.services can't break de.codecentric.boot.admin.server.web.client.
- Position
- Below the diagonal: de.codecentric.boot.admin.server.services uses a module listed above it, which is the healthy direction.
31→29 de.codecentric.boot.admin.server.services uses de.codecentric.boot.admin.server.services.endpoints✕
- Connections
- 1 pair of types, where a type in de.codecentric.boot.admin.server.services uses a type in de.codecentric.boot.admin.server.services.endpoints.
- The types involved
de.codecentric.boot.admin.server.services.EndpointDetector→de.codecentric.boot.admin.server.services.endpoints.EndpointDetectionStrategy
- Direction
- de.codecentric.boot.admin.server.services uses de.codecentric.boot.admin.server.services.endpoints, so a change to de.codecentric.boot.admin.server.services.endpoints can break de.codecentric.boot.admin.server.services, while a change to de.codecentric.boot.admin.server.services can't break de.codecentric.boot.admin.server.services.endpoints.
- Position
- Below the diagonal: de.codecentric.boot.admin.server.services uses a module listed above it, which is the healthy direction.
32→1 de.codecentric.boot.admin.server.cloud.discovery uses de.codecentric.boot.admin.server.domain.values✕
- Connections
- 3 pairs of types, where a type in de.codecentric.boot.admin.server.cloud.discovery uses a type in de.codecentric.boot.admin.server.domain.values.
- The types involved
de.codecentric.boot.admin.server.cloud.discovery.DefaultServiceInstanceConverter→de.codecentric.boot.admin.server.domain.values.Registrationde.codecentric.boot.admin.server.cloud.discovery.InstanceDiscoveryListener→de.codecentric.boot.admin.server.domain.values.InstanceIdde.codecentric.boot.admin.server.cloud.discovery.ServiceInstanceConverter→de.codecentric.boot.admin.server.domain.values.Registration
- Direction
- de.codecentric.boot.admin.server.cloud.discovery uses de.codecentric.boot.admin.server.domain.values, so a change to de.codecentric.boot.admin.server.domain.values can break de.codecentric.boot.admin.server.cloud.discovery, while a change to de.codecentric.boot.admin.server.cloud.discovery can't break de.codecentric.boot.admin.server.domain.values.
- Position
- Below the diagonal: de.codecentric.boot.admin.server.cloud.discovery uses a module listed above it, which is the healthy direction.
32→23 de.codecentric.boot.admin.server.cloud.discovery uses de.codecentric.boot.admin.server.domain.entities✕
- Connections
- 1 pair of types, where a type in de.codecentric.boot.admin.server.cloud.discovery uses a type in de.codecentric.boot.admin.server.domain.entities.
- The types involved
de.codecentric.boot.admin.server.cloud.discovery.InstanceDiscoveryListener→de.codecentric.boot.admin.server.domain.entities.InstanceRepository
- Direction
- de.codecentric.boot.admin.server.cloud.discovery uses de.codecentric.boot.admin.server.domain.entities, so a change to de.codecentric.boot.admin.server.domain.entities can break de.codecentric.boot.admin.server.cloud.discovery, while a change to de.codecentric.boot.admin.server.cloud.discovery can't break de.codecentric.boot.admin.server.domain.entities.
- Position
- Below the diagonal: de.codecentric.boot.admin.server.cloud.discovery uses a module listed above it, which is the healthy direction.
32→27 de.codecentric.boot.admin.server.cloud.discovery uses de.codecentric.boot.admin.server.web.client✕
- Connections
- 1 pair of types, where a type in de.codecentric.boot.admin.server.cloud.discovery uses a type in de.codecentric.boot.admin.server.web.client.
- The types involved
de.codecentric.boot.admin.server.cloud.discovery.InstanceDiscoveryListener→de.codecentric.boot.admin.server.web.client.RefreshInstancesEvent
- Direction
- de.codecentric.boot.admin.server.cloud.discovery uses de.codecentric.boot.admin.server.web.client, so a change to de.codecentric.boot.admin.server.web.client can break de.codecentric.boot.admin.server.cloud.discovery, while a change to de.codecentric.boot.admin.server.cloud.discovery can't break de.codecentric.boot.admin.server.web.client.
- Position
- Below the diagonal: de.codecentric.boot.admin.server.cloud.discovery uses a module listed above it, which is the healthy direction.
32→31 de.codecentric.boot.admin.server.cloud.discovery uses de.codecentric.boot.admin.server.services✕
- Connections
- 1 pair of types, where a type in de.codecentric.boot.admin.server.cloud.discovery uses a type in de.codecentric.boot.admin.server.services.
- The types involved
de.codecentric.boot.admin.server.cloud.discovery.InstanceDiscoveryListener→de.codecentric.boot.admin.server.services.InstanceRegistry
- Direction
- de.codecentric.boot.admin.server.cloud.discovery uses de.codecentric.boot.admin.server.services, so a change to de.codecentric.boot.admin.server.services can break de.codecentric.boot.admin.server.cloud.discovery, while a change to de.codecentric.boot.admin.server.cloud.discovery can't break de.codecentric.boot.admin.server.services.
- Position
- Below the diagonal: de.codecentric.boot.admin.server.cloud.discovery uses a module listed above it, which is the healthy direction.
33→1 de.codecentric.boot.admin.server.notify uses de.codecentric.boot.admin.server.domain.values✕
- Connections
- 3 pairs of types, where a type in de.codecentric.boot.admin.server.notify uses a type in de.codecentric.boot.admin.server.domain.values.
- The types involved
de.codecentric.boot.admin.server.notify.AbstractStatusChangeNotifier→de.codecentric.boot.admin.server.domain.values.InstanceIdde.codecentric.boot.admin.server.notify.HazelcastNotificationTrigger→de.codecentric.boot.admin.server.domain.values.InstanceIdde.codecentric.boot.admin.server.notify.RemindingNotifier→de.codecentric.boot.admin.server.domain.values.InstanceId
- Direction
- de.codecentric.boot.admin.server.notify uses de.codecentric.boot.admin.server.domain.values, so a change to de.codecentric.boot.admin.server.domain.values can break de.codecentric.boot.admin.server.notify, while a change to de.codecentric.boot.admin.server.notify can't break de.codecentric.boot.admin.server.domain.values.
- Position
- Below the diagonal: de.codecentric.boot.admin.server.notify uses a module listed above it, which is the healthy direction.
33→8 de.codecentric.boot.admin.server.notify uses de.codecentric.boot.admin.server.domain.events✕
- Connections
- 23 pairs of types, where a type in de.codecentric.boot.admin.server.notify uses a type in de.codecentric.boot.admin.server.domain.events.
- The types involved
de.codecentric.boot.admin.server.notify.AbstractEventNotifier→de.codecentric.boot.admin.server.domain.events.InstanceEventde.codecentric.boot.admin.server.notify.AbstractStatusChangeNotifier→de.codecentric.boot.admin.server.domain.events.InstanceEventde.codecentric.boot.admin.server.notify.CompositeNotifier→de.codecentric.boot.admin.server.domain.events.InstanceEventde.codecentric.boot.admin.server.notify.DingTalkNotifier→de.codecentric.boot.admin.server.domain.events.InstanceEventde.codecentric.boot.admin.server.notify.DiscordNotifier→de.codecentric.boot.admin.server.domain.events.InstanceEventde.codecentric.boot.admin.server.notify.FeiShuNotifier→de.codecentric.boot.admin.server.domain.events.InstanceEventde.codecentric.boot.admin.server.notify.HazelcastNotificationTrigger→de.codecentric.boot.admin.server.domain.events.InstanceEventde.codecentric.boot.admin.server.notify.HipchatNotifier→de.codecentric.boot.admin.server.domain.events.InstanceEventde.codecentric.boot.admin.server.notify.LetsChatNotifier→de.codecentric.boot.admin.server.domain.events.InstanceEventde.codecentric.boot.admin.server.notify.LoggingNotifier→de.codecentric.boot.admin.server.domain.events.InstanceEventde.codecentric.boot.admin.server.notify.MailNotifier→de.codecentric.boot.admin.server.domain.events.InstanceEventde.codecentric.boot.admin.server.notify.MattermostNotifier→de.codecentric.boot.admin.server.domain.events.InstanceEventde.codecentric.boot.admin.server.notify.MicrosoftTeamsNotifier→de.codecentric.boot.admin.server.domain.events.InstanceEventde.codecentric.boot.admin.server.notify.NotificationTrigger→de.codecentric.boot.admin.server.domain.events.InstanceEventde.codecentric.boot.admin.server.notify.Notifier→de.codecentric.boot.admin.server.domain.events.InstanceEventde.codecentric.boot.admin.server.notify.OpsGenieNotifier→de.codecentric.boot.admin.server.domain.events.InstanceEventde.codecentric.boot.admin.server.notify.PagerdutyNotifier→de.codecentric.boot.admin.server.domain.events.InstanceEventde.codecentric.boot.admin.server.notify.Reminder→de.codecentric.boot.admin.server.domain.events.InstanceEventde.codecentric.boot.admin.server.notify.RemindingNotifier→de.codecentric.boot.admin.server.domain.events.InstanceEventde.codecentric.boot.admin.server.notify.RocketChatNotifier→de.codecentric.boot.admin.server.domain.events.InstanceEventde.codecentric.boot.admin.server.notify.SlackNotifier→de.codecentric.boot.admin.server.domain.events.InstanceEventde.codecentric.boot.admin.server.notify.TelegramNotifier→de.codecentric.boot.admin.server.domain.events.InstanceEventde.codecentric.boot.admin.server.notify.WebexNotifier→de.codecentric.boot.admin.server.domain.events.InstanceEvent
- Direction
- de.codecentric.boot.admin.server.notify uses de.codecentric.boot.admin.server.domain.events, so a change to de.codecentric.boot.admin.server.domain.events can break de.codecentric.boot.admin.server.notify, while a change to de.codecentric.boot.admin.server.notify can't break de.codecentric.boot.admin.server.domain.events.
- Position
- Below the diagonal: de.codecentric.boot.admin.server.notify uses a module listed above it, which is the healthy direction.
33→23 de.codecentric.boot.admin.server.notify uses de.codecentric.boot.admin.server.domain.entities✕
- Connections
- 36 pairs of types, where a type in de.codecentric.boot.admin.server.notify uses a type in de.codecentric.boot.admin.server.domain.entities. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
de.codecentric.boot.admin.server.notify.AbstractEventNotifier→de.codecentric.boot.admin.server.domain.entities.Instancede.codecentric.boot.admin.server.notify.AbstractEventNotifier→de.codecentric.boot.admin.server.domain.entities.InstanceRepositoryde.codecentric.boot.admin.server.notify.AbstractStatusChangeNotifier→de.codecentric.boot.admin.server.domain.entities.Instancede.codecentric.boot.admin.server.notify.AbstractStatusChangeNotifier→de.codecentric.boot.admin.server.domain.entities.InstanceRepositoryde.codecentric.boot.admin.server.notify.DingTalkNotifier→de.codecentric.boot.admin.server.domain.entities.Instancede.codecentric.boot.admin.server.notify.DingTalkNotifier→de.codecentric.boot.admin.server.domain.entities.InstanceRepositoryde.codecentric.boot.admin.server.notify.DiscordNotifier→de.codecentric.boot.admin.server.domain.entities.Instancede.codecentric.boot.admin.server.notify.DiscordNotifier→de.codecentric.boot.admin.server.domain.entities.InstanceRepositoryde.codecentric.boot.admin.server.notify.FeiShuNotifier→de.codecentric.boot.admin.server.domain.entities.Instancede.codecentric.boot.admin.server.notify.FeiShuNotifier→de.codecentric.boot.admin.server.domain.entities.InstanceRepositoryde.codecentric.boot.admin.server.notify.HipchatNotifier→de.codecentric.boot.admin.server.domain.entities.Instancede.codecentric.boot.admin.server.notify.HipchatNotifier→de.codecentric.boot.admin.server.domain.entities.InstanceRepositoryde.codecentric.boot.admin.server.notify.LetsChatNotifier→de.codecentric.boot.admin.server.domain.entities.Instancede.codecentric.boot.admin.server.notify.LetsChatNotifier→de.codecentric.boot.admin.server.domain.entities.InstanceRepositoryde.codecentric.boot.admin.server.notify.LoggingNotifier→de.codecentric.boot.admin.server.domain.entities.Instancede.codecentric.boot.admin.server.notify.LoggingNotifier→de.codecentric.boot.admin.server.domain.entities.InstanceRepositoryde.codecentric.boot.admin.server.notify.MailNotifier→de.codecentric.boot.admin.server.domain.entities.Instancede.codecentric.boot.admin.server.notify.MailNotifier→de.codecentric.boot.admin.server.domain.entities.InstanceRepositoryde.codecentric.boot.admin.server.notify.MattermostNotifier→de.codecentric.boot.admin.server.domain.entities.Instancede.codecentric.boot.admin.server.notify.MattermostNotifier→de.codecentric.boot.admin.server.domain.entities.InstanceRepositoryde.codecentric.boot.admin.server.notify.MicrosoftTeamsNotifier→de.codecentric.boot.admin.server.domain.entities.Instancede.codecentric.boot.admin.server.notify.MicrosoftTeamsNotifier→de.codecentric.boot.admin.server.domain.entities.InstanceRepositoryde.codecentric.boot.admin.server.notify.OpsGenieNotifier→de.codecentric.boot.admin.server.domain.entities.Instancede.codecentric.boot.admin.server.notify.OpsGenieNotifier→de.codecentric.boot.admin.server.domain.entities.InstanceRepositoryde.codecentric.boot.admin.server.notify.PagerdutyNotifier→de.codecentric.boot.admin.server.domain.entities.Instance
- Direction
- de.codecentric.boot.admin.server.notify uses de.codecentric.boot.admin.server.domain.entities, so a change to de.codecentric.boot.admin.server.domain.entities can break de.codecentric.boot.admin.server.notify, while a change to de.codecentric.boot.admin.server.notify can't break de.codecentric.boot.admin.server.domain.entities.
- Position
- Below the diagonal: de.codecentric.boot.admin.server.notify uses a module listed above it, which is the healthy direction.
33→24 de.codecentric.boot.admin.server.notify uses de.codecentric.boot.admin.server.notify.filter✕
- Connections
- 10 pairs of types, where a type in de.codecentric.boot.admin.server.notify uses a type in de.codecentric.boot.admin.server.notify.filter.
- The types involved
de.codecentric.boot.admin.server.notify.DingTalkNotifier→de.codecentric.boot.admin.server.notify.filter.AbstractContentNotifierde.codecentric.boot.admin.server.notify.DiscordNotifier→de.codecentric.boot.admin.server.notify.filter.AbstractContentNotifierde.codecentric.boot.admin.server.notify.FeiShuNotifier→de.codecentric.boot.admin.server.notify.filter.AbstractContentNotifierde.codecentric.boot.admin.server.notify.HipchatNotifier→de.codecentric.boot.admin.server.notify.filter.AbstractContentNotifierde.codecentric.boot.admin.server.notify.LetsChatNotifier→de.codecentric.boot.admin.server.notify.filter.AbstractContentNotifierde.codecentric.boot.admin.server.notify.MattermostNotifier→de.codecentric.boot.admin.server.notify.filter.AbstractContentNotifierde.codecentric.boot.admin.server.notify.RocketChatNotifier→de.codecentric.boot.admin.server.notify.filter.AbstractContentNotifierde.codecentric.boot.admin.server.notify.SlackNotifier→de.codecentric.boot.admin.server.notify.filter.AbstractContentNotifierde.codecentric.boot.admin.server.notify.TelegramNotifier→de.codecentric.boot.admin.server.notify.filter.AbstractContentNotifierde.codecentric.boot.admin.server.notify.WebexNotifier→de.codecentric.boot.admin.server.notify.filter.AbstractContentNotifier
- Direction
- de.codecentric.boot.admin.server.notify uses de.codecentric.boot.admin.server.notify.filter, so a change to de.codecentric.boot.admin.server.notify.filter can break de.codecentric.boot.admin.server.notify, while a change to de.codecentric.boot.admin.server.notify can't break de.codecentric.boot.admin.server.notify.filter.
- Position
- Below the diagonal: de.codecentric.boot.admin.server.notify uses a module listed above it, which is the healthy direction.
33→31 de.codecentric.boot.admin.server.notify uses de.codecentric.boot.admin.server.services✕
- Connections
- 1 pair of types, where a type in de.codecentric.boot.admin.server.notify uses a type in de.codecentric.boot.admin.server.services.
- The types involved
de.codecentric.boot.admin.server.notify.NotificationTrigger→de.codecentric.boot.admin.server.services.AbstractEventHandler
- Direction
- de.codecentric.boot.admin.server.notify uses de.codecentric.boot.admin.server.services, so a change to de.codecentric.boot.admin.server.services can break de.codecentric.boot.admin.server.notify, while a change to de.codecentric.boot.admin.server.notify can't break de.codecentric.boot.admin.server.services.
- Position
- Below the diagonal: de.codecentric.boot.admin.server.notify uses a module listed above it, which is the healthy direction.
34→1 de.codecentric.boot.admin.server.web uses de.codecentric.boot.admin.server.domain.values✕
- Connections
- 3 pairs of types, where a type in de.codecentric.boot.admin.server.web uses a type in de.codecentric.boot.admin.server.domain.values.
- The types involved
de.codecentric.boot.admin.server.web.InstanceResponse→de.codecentric.boot.admin.server.domain.values.InstanceIdde.codecentric.boot.admin.server.web.InstancesController→de.codecentric.boot.admin.server.domain.values.InstanceIdde.codecentric.boot.admin.server.web.InstancesController→de.codecentric.boot.admin.server.domain.values.Registration
- Direction
- de.codecentric.boot.admin.server.web uses de.codecentric.boot.admin.server.domain.values, so a change to de.codecentric.boot.admin.server.domain.values can break de.codecentric.boot.admin.server.web, while a change to de.codecentric.boot.admin.server.web can't break de.codecentric.boot.admin.server.domain.values.
- Position
- Below the diagonal: de.codecentric.boot.admin.server.web uses a module listed above it, which is the healthy direction.
34→3 de.codecentric.boot.admin.server.web uses org.springframework.http✕
- Connections
- 2 pairs of types, where a type in de.codecentric.boot.admin.server.web uses a type in org.springframework.http.
- The types involved
de.codecentric.boot.admin.server.web.ForwardRequest→org.springframework.http.HttpMethodde.codecentric.boot.admin.server.web.InstanceWebProxy→org.springframework.http.HttpMethod
- Direction
- de.codecentric.boot.admin.server.web uses org.springframework.http, so a change to org.springframework.http can break de.codecentric.boot.admin.server.web, while a change to de.codecentric.boot.admin.server.web can't break org.springframework.http.
- Position
- Below the diagonal: de.codecentric.boot.admin.server.web uses a module listed above it, which is the healthy direction.
34→8 de.codecentric.boot.admin.server.web uses de.codecentric.boot.admin.server.domain.events✕
- Connections
- 1 pair of types, where a type in de.codecentric.boot.admin.server.web uses a type in de.codecentric.boot.admin.server.domain.events.
- The types involved
de.codecentric.boot.admin.server.web.InstancesController→de.codecentric.boot.admin.server.domain.events.InstanceEvent
- Direction
- de.codecentric.boot.admin.server.web uses de.codecentric.boot.admin.server.domain.events, so a change to de.codecentric.boot.admin.server.domain.events can break de.codecentric.boot.admin.server.web, while a change to de.codecentric.boot.admin.server.web can't break de.codecentric.boot.admin.server.domain.events.
- Position
- Below the diagonal: de.codecentric.boot.admin.server.web uses a module listed above it, which is the healthy direction.
34→10 de.codecentric.boot.admin.server.web uses de.codecentric.boot.admin.server.utils✕
- Connections
- 1 pair of types, where a type in de.codecentric.boot.admin.server.web uses a type in de.codecentric.boot.admin.server.utils.
- The types involved
de.codecentric.boot.admin.server.web.InstanceWebProxy→de.codecentric.boot.admin.server.utils.SsrfUrlValidator
- Direction
- de.codecentric.boot.admin.server.web uses de.codecentric.boot.admin.server.utils, so a change to de.codecentric.boot.admin.server.utils can break de.codecentric.boot.admin.server.web, while a change to de.codecentric.boot.admin.server.web can't break de.codecentric.boot.admin.server.utils.
- Position
- Below the diagonal: de.codecentric.boot.admin.server.web uses a module listed above it, which is the healthy direction.
34→18 de.codecentric.boot.admin.server.web uses de.codecentric.boot.admin.server.eventstore✕
- Connections
- 1 pair of types, where a type in de.codecentric.boot.admin.server.web uses a type in de.codecentric.boot.admin.server.eventstore.
- The types involved
de.codecentric.boot.admin.server.web.InstancesController→de.codecentric.boot.admin.server.eventstore.InstanceEventStore
- Direction
- de.codecentric.boot.admin.server.web uses de.codecentric.boot.admin.server.eventstore, so a change to de.codecentric.boot.admin.server.eventstore can break de.codecentric.boot.admin.server.web, while a change to de.codecentric.boot.admin.server.web can't break de.codecentric.boot.admin.server.eventstore.
- Position
- Below the diagonal: de.codecentric.boot.admin.server.web uses a module listed above it, which is the healthy direction.
34→23 de.codecentric.boot.admin.server.web uses de.codecentric.boot.admin.server.domain.entities✕
- Connections
- 3 pairs of types, where a type in de.codecentric.boot.admin.server.web uses a type in de.codecentric.boot.admin.server.domain.entities.
- The types involved
de.codecentric.boot.admin.server.web.ApplicationsController→de.codecentric.boot.admin.server.domain.entities.Applicationde.codecentric.boot.admin.server.web.InstanceWebProxy→de.codecentric.boot.admin.server.domain.entities.Instancede.codecentric.boot.admin.server.web.InstancesController→de.codecentric.boot.admin.server.domain.entities.Instance
- Direction
- de.codecentric.boot.admin.server.web uses de.codecentric.boot.admin.server.domain.entities, so a change to de.codecentric.boot.admin.server.domain.entities can break de.codecentric.boot.admin.server.web, while a change to de.codecentric.boot.admin.server.web can't break de.codecentric.boot.admin.server.domain.entities.
- Position
- Below the diagonal: de.codecentric.boot.admin.server.web uses a module listed above it, which is the healthy direction.
34→27 de.codecentric.boot.admin.server.web uses de.codecentric.boot.admin.server.web.client✕
- Connections
- 1 pair of types, where a type in de.codecentric.boot.admin.server.web uses a type in de.codecentric.boot.admin.server.web.client.
- The types involved
de.codecentric.boot.admin.server.web.InstanceWebProxy→de.codecentric.boot.admin.server.web.client.InstanceWebClient
- Direction
- de.codecentric.boot.admin.server.web uses de.codecentric.boot.admin.server.web.client, so a change to de.codecentric.boot.admin.server.web.client can break de.codecentric.boot.admin.server.web, while a change to de.codecentric.boot.admin.server.web can't break de.codecentric.boot.admin.server.web.client.
- Position
- Below the diagonal: de.codecentric.boot.admin.server.web uses a module listed above it, which is the healthy direction.
34→31 de.codecentric.boot.admin.server.web uses de.codecentric.boot.admin.server.services✕
- Connections
- 3 pairs of types, where a type in de.codecentric.boot.admin.server.web uses a type in de.codecentric.boot.admin.server.services.
- The types involved
de.codecentric.boot.admin.server.web.ApplicationsController→de.codecentric.boot.admin.server.services.ApplicationRegistryde.codecentric.boot.admin.server.web.InstancesController→de.codecentric.boot.admin.server.services.HealthGroupsCachede.codecentric.boot.admin.server.web.InstancesController→de.codecentric.boot.admin.server.services.InstanceRegistry
- Direction
- de.codecentric.boot.admin.server.web uses de.codecentric.boot.admin.server.services, so a change to de.codecentric.boot.admin.server.services can break de.codecentric.boot.admin.server.web, while a change to de.codecentric.boot.admin.server.web can't break de.codecentric.boot.admin.server.services.
- Position
- Below the diagonal: de.codecentric.boot.admin.server.web uses a module listed above it, which is the healthy direction.
35→23 de.codecentric.boot.admin.server.cloud.config uses de.codecentric.boot.admin.server.domain.entities✕
- Connections
- 1 pair of types, where a type in de.codecentric.boot.admin.server.cloud.config uses a type in de.codecentric.boot.admin.server.domain.entities.
- The types involved
de.codecentric.boot.admin.server.cloud.config.AdminServerDiscoveryAutoConfiguration→de.codecentric.boot.admin.server.domain.entities.InstanceRepository
- Direction
- de.codecentric.boot.admin.server.cloud.config uses de.codecentric.boot.admin.server.domain.entities, so a change to de.codecentric.boot.admin.server.domain.entities can break de.codecentric.boot.admin.server.cloud.config, while a change to de.codecentric.boot.admin.server.cloud.config can't break de.codecentric.boot.admin.server.domain.entities.
- Position
- Below the diagonal: de.codecentric.boot.admin.server.cloud.config uses a module listed above it, which is the healthy direction.
35→31 de.codecentric.boot.admin.server.cloud.config uses de.codecentric.boot.admin.server.services✕
- Connections
- 1 pair of types, where a type in de.codecentric.boot.admin.server.cloud.config uses a type in de.codecentric.boot.admin.server.services.
- The types involved
de.codecentric.boot.admin.server.cloud.config.AdminServerDiscoveryAutoConfiguration→de.codecentric.boot.admin.server.services.InstanceRegistry
- Direction
- de.codecentric.boot.admin.server.cloud.config uses de.codecentric.boot.admin.server.services, so a change to de.codecentric.boot.admin.server.services can break de.codecentric.boot.admin.server.cloud.config, while a change to de.codecentric.boot.admin.server.cloud.config can't break de.codecentric.boot.admin.server.services.
- Position
- Below the diagonal: de.codecentric.boot.admin.server.cloud.config uses a module listed above it, which is the healthy direction.
35→32 de.codecentric.boot.admin.server.cloud.config uses de.codecentric.boot.admin.server.cloud.discovery✕
- Connections
- 5 pairs of types, where a type in de.codecentric.boot.admin.server.cloud.config uses a type in de.codecentric.boot.admin.server.cloud.discovery.
- The types involved
de.codecentric.boot.admin.server.cloud.config.AdminServerDiscoveryAutoConfiguration→de.codecentric.boot.admin.server.cloud.discovery.DefaultServiceInstanceConverterde.codecentric.boot.admin.server.cloud.config.AdminServerDiscoveryAutoConfiguration→de.codecentric.boot.admin.server.cloud.discovery.InstanceDiscoveryListenerde.codecentric.boot.admin.server.cloud.config.AdminServerDiscoveryAutoConfiguration→de.codecentric.boot.admin.server.cloud.discovery.ServiceInstanceConverterde.codecentric.boot.admin.server.cloud.config.EurekaConverterConfiguration→de.codecentric.boot.admin.server.cloud.discovery.EurekaServiceInstanceConverterde.codecentric.boot.admin.server.cloud.config.KubernetesConverterConfiguration→de.codecentric.boot.admin.server.cloud.discovery.KubernetesServiceInstanceConverter
- Direction
- de.codecentric.boot.admin.server.cloud.config uses de.codecentric.boot.admin.server.cloud.discovery, so a change to de.codecentric.boot.admin.server.cloud.discovery can break de.codecentric.boot.admin.server.cloud.config, while a change to de.codecentric.boot.admin.server.cloud.config can't break de.codecentric.boot.admin.server.cloud.discovery.
- Position
- Below the diagonal: de.codecentric.boot.admin.server.cloud.config uses a module listed above it, which is the healthy direction.
36→10 de.codecentric.boot.admin.server.web.reactive uses de.codecentric.boot.admin.server.utils✕
- Connections
- 1 pair of types, where a type in de.codecentric.boot.admin.server.web.reactive uses a type in de.codecentric.boot.admin.server.utils.
- The types involved
de.codecentric.boot.admin.server.web.reactive.InstancesProxyController→de.codecentric.boot.admin.server.utils.SsrfUrlValidator
- Direction
- de.codecentric.boot.admin.server.web.reactive uses de.codecentric.boot.admin.server.utils, so a change to de.codecentric.boot.admin.server.utils can break de.codecentric.boot.admin.server.web.reactive, while a change to de.codecentric.boot.admin.server.web.reactive can't break de.codecentric.boot.admin.server.utils.
- Position
- Below the diagonal: de.codecentric.boot.admin.server.web.reactive uses a module listed above it, which is the healthy direction.
36→27 de.codecentric.boot.admin.server.web.reactive uses de.codecentric.boot.admin.server.web.client✕
- Connections
- 1 pair of types, where a type in de.codecentric.boot.admin.server.web.reactive uses a type in de.codecentric.boot.admin.server.web.client.
- The types involved
de.codecentric.boot.admin.server.web.reactive.InstancesProxyController→de.codecentric.boot.admin.server.web.client.InstanceWebClient
- Direction
- de.codecentric.boot.admin.server.web.reactive uses de.codecentric.boot.admin.server.web.client, so a change to de.codecentric.boot.admin.server.web.client can break de.codecentric.boot.admin.server.web.reactive, while a change to de.codecentric.boot.admin.server.web.reactive can't break de.codecentric.boot.admin.server.web.client.
- Position
- Below the diagonal: de.codecentric.boot.admin.server.web.reactive uses a module listed above it, which is the healthy direction.
36→31 de.codecentric.boot.admin.server.web.reactive uses de.codecentric.boot.admin.server.services✕
- Connections
- 1 pair of types, where a type in de.codecentric.boot.admin.server.web.reactive uses a type in de.codecentric.boot.admin.server.services.
- The types involved
de.codecentric.boot.admin.server.web.reactive.InstancesProxyController→de.codecentric.boot.admin.server.services.InstanceRegistry
- Direction
- de.codecentric.boot.admin.server.web.reactive uses de.codecentric.boot.admin.server.services, so a change to de.codecentric.boot.admin.server.services can break de.codecentric.boot.admin.server.web.reactive, while a change to de.codecentric.boot.admin.server.web.reactive can't break de.codecentric.boot.admin.server.services.
- Position
- Below the diagonal: de.codecentric.boot.admin.server.web.reactive uses a module listed above it, which is the healthy direction.
36→34 de.codecentric.boot.admin.server.web.reactive uses de.codecentric.boot.admin.server.web✕
- Connections
- 4 pairs of types, where a type in de.codecentric.boot.admin.server.web.reactive uses a type in de.codecentric.boot.admin.server.web.
- The types involved
de.codecentric.boot.admin.server.web.reactive.InstancesProxyController→de.codecentric.boot.admin.server.web.ForwardRequestde.codecentric.boot.admin.server.web.reactive.InstancesProxyController→de.codecentric.boot.admin.server.web.HttpHeaderFilterde.codecentric.boot.admin.server.web.reactive.InstancesProxyController→de.codecentric.boot.admin.server.web.InstanceResponsede.codecentric.boot.admin.server.web.reactive.InstancesProxyController→de.codecentric.boot.admin.server.web.InstanceWebProxy
- Direction
- de.codecentric.boot.admin.server.web.reactive uses de.codecentric.boot.admin.server.web, so a change to de.codecentric.boot.admin.server.web can break de.codecentric.boot.admin.server.web.reactive, while a change to de.codecentric.boot.admin.server.web.reactive can't break de.codecentric.boot.admin.server.web.
- Position
- Below the diagonal: de.codecentric.boot.admin.server.web.reactive uses a module listed above it, which is the healthy direction.
37→10 de.codecentric.boot.admin.server.web.servlet uses de.codecentric.boot.admin.server.utils✕
- Connections
- 1 pair of types, where a type in de.codecentric.boot.admin.server.web.servlet uses a type in de.codecentric.boot.admin.server.utils.
- The types involved
de.codecentric.boot.admin.server.web.servlet.InstancesProxyController→de.codecentric.boot.admin.server.utils.SsrfUrlValidator
- Direction
- de.codecentric.boot.admin.server.web.servlet uses de.codecentric.boot.admin.server.utils, so a change to de.codecentric.boot.admin.server.utils can break de.codecentric.boot.admin.server.web.servlet, while a change to de.codecentric.boot.admin.server.web.servlet can't break de.codecentric.boot.admin.server.utils.
- Position
- Below the diagonal: de.codecentric.boot.admin.server.web.servlet uses a module listed above it, which is the healthy direction.
37→27 de.codecentric.boot.admin.server.web.servlet uses de.codecentric.boot.admin.server.web.client✕
- Connections
- 1 pair of types, where a type in de.codecentric.boot.admin.server.web.servlet uses a type in de.codecentric.boot.admin.server.web.client.
- The types involved
de.codecentric.boot.admin.server.web.servlet.InstancesProxyController→de.codecentric.boot.admin.server.web.client.InstanceWebClient
- Direction
- de.codecentric.boot.admin.server.web.servlet uses de.codecentric.boot.admin.server.web.client, so a change to de.codecentric.boot.admin.server.web.client can break de.codecentric.boot.admin.server.web.servlet, while a change to de.codecentric.boot.admin.server.web.servlet can't break de.codecentric.boot.admin.server.web.client.
- Position
- Below the diagonal: de.codecentric.boot.admin.server.web.servlet uses a module listed above it, which is the healthy direction.
37→31 de.codecentric.boot.admin.server.web.servlet uses de.codecentric.boot.admin.server.services✕
- Connections
- 1 pair of types, where a type in de.codecentric.boot.admin.server.web.servlet uses a type in de.codecentric.boot.admin.server.services.
- The types involved
de.codecentric.boot.admin.server.web.servlet.InstancesProxyController→de.codecentric.boot.admin.server.services.InstanceRegistry
- Direction
- de.codecentric.boot.admin.server.web.servlet uses de.codecentric.boot.admin.server.services, so a change to de.codecentric.boot.admin.server.services can break de.codecentric.boot.admin.server.web.servlet, while a change to de.codecentric.boot.admin.server.web.servlet can't break de.codecentric.boot.admin.server.services.
- Position
- Below the diagonal: de.codecentric.boot.admin.server.web.servlet uses a module listed above it, which is the healthy direction.
37→34 de.codecentric.boot.admin.server.web.servlet uses de.codecentric.boot.admin.server.web✕
- Connections
- 4 pairs of types, where a type in de.codecentric.boot.admin.server.web.servlet uses a type in de.codecentric.boot.admin.server.web.
- The types involved
de.codecentric.boot.admin.server.web.servlet.InstancesProxyController→de.codecentric.boot.admin.server.web.ForwardRequestde.codecentric.boot.admin.server.web.servlet.InstancesProxyController→de.codecentric.boot.admin.server.web.HttpHeaderFilterde.codecentric.boot.admin.server.web.servlet.InstancesProxyController→de.codecentric.boot.admin.server.web.InstanceResponsede.codecentric.boot.admin.server.web.servlet.InstancesProxyController→de.codecentric.boot.admin.server.web.InstanceWebProxy
- Direction
- de.codecentric.boot.admin.server.web.servlet uses de.codecentric.boot.admin.server.web, so a change to de.codecentric.boot.admin.server.web can break de.codecentric.boot.admin.server.web.servlet, while a change to de.codecentric.boot.admin.server.web.servlet can't break de.codecentric.boot.admin.server.web.
- Position
- Below the diagonal: de.codecentric.boot.admin.server.web.servlet uses a module listed above it, which is the healthy direction.
38→1 de.codecentric.boot.admin.server.config uses de.codecentric.boot.admin.server.domain.values✕
- Connections
- 6 pairs of types, where a type in de.codecentric.boot.admin.server.config uses a type in de.codecentric.boot.admin.server.domain.values.
- The types involved
de.codecentric.boot.admin.server.config.1→de.codecentric.boot.admin.server.domain.values.StatusInfode.codecentric.boot.admin.server.config.2→de.codecentric.boot.admin.server.domain.values.StatusInfode.codecentric.boot.admin.server.config.AdminServerAutoConfiguration→de.codecentric.boot.admin.server.domain.values.InstanceIdde.codecentric.boot.admin.server.config.AdminServerHazelcastAutoConfiguration→de.codecentric.boot.admin.server.domain.values.InstanceIdde.codecentric.boot.admin.server.config.NotifierTriggerConfiguration→de.codecentric.boot.admin.server.domain.values.InstanceIdde.codecentric.boot.admin.server.config.StatusChangeDetectionStrategy→de.codecentric.boot.admin.server.domain.values.StatusInfo
- Direction
- de.codecentric.boot.admin.server.config uses de.codecentric.boot.admin.server.domain.values, so a change to de.codecentric.boot.admin.server.domain.values can break de.codecentric.boot.admin.server.config, while a change to de.codecentric.boot.admin.server.config can't break de.codecentric.boot.admin.server.domain.values.
- Position
- Below the diagonal: de.codecentric.boot.admin.server.config uses a module listed above it, which is the healthy direction.
38→8 de.codecentric.boot.admin.server.config uses de.codecentric.boot.admin.server.domain.events✕
- Connections
- 3 pairs of types, where a type in de.codecentric.boot.admin.server.config uses a type in de.codecentric.boot.admin.server.domain.events.
- The types involved
de.codecentric.boot.admin.server.config.AdminServerAutoConfiguration→de.codecentric.boot.admin.server.domain.events.InstanceEventde.codecentric.boot.admin.server.config.CookieStoreConfiguration→de.codecentric.boot.admin.server.domain.events.InstanceEventde.codecentric.boot.admin.server.config.NotifierTriggerConfiguration→de.codecentric.boot.admin.server.domain.events.InstanceEvent
- Direction
- de.codecentric.boot.admin.server.config uses de.codecentric.boot.admin.server.domain.events, so a change to de.codecentric.boot.admin.server.domain.events can break de.codecentric.boot.admin.server.config, while a change to de.codecentric.boot.admin.server.config can't break de.codecentric.boot.admin.server.domain.events.
- Position
- Below the diagonal: de.codecentric.boot.admin.server.config uses a module listed above it, which is the healthy direction.
38→10 de.codecentric.boot.admin.server.config uses de.codecentric.boot.admin.server.utils✕
- Connections
- 3 pairs of types, where a type in de.codecentric.boot.admin.server.config uses a type in de.codecentric.boot.admin.server.utils.
- The types involved
de.codecentric.boot.admin.server.config.AdminServerAutoConfiguration→de.codecentric.boot.admin.server.utils.SsrfUrlValidatorde.codecentric.boot.admin.server.config.ReactiveRestApiConfiguration→de.codecentric.boot.admin.server.utils.SsrfUrlValidatorde.codecentric.boot.admin.server.config.ServletRestApiConfiguration→de.codecentric.boot.admin.server.utils.SsrfUrlValidator
- Direction
- de.codecentric.boot.admin.server.config uses de.codecentric.boot.admin.server.utils, so a change to de.codecentric.boot.admin.server.utils can break de.codecentric.boot.admin.server.config, while a change to de.codecentric.boot.admin.server.config can't break de.codecentric.boot.admin.server.utils.
- Position
- Below the diagonal: de.codecentric.boot.admin.server.config uses a module listed above it, which is the healthy direction.
38→18 de.codecentric.boot.admin.server.config uses de.codecentric.boot.admin.server.eventstore✕
- Connections
- 5 pairs of types, where a type in de.codecentric.boot.admin.server.config uses a type in de.codecentric.boot.admin.server.eventstore.
- The types involved
de.codecentric.boot.admin.server.config.AdminServerAutoConfiguration→de.codecentric.boot.admin.server.eventstore.InMemoryEventStorede.codecentric.boot.admin.server.config.AdminServerAutoConfiguration→de.codecentric.boot.admin.server.eventstore.InstanceEventPublisherde.codecentric.boot.admin.server.config.AdminServerAutoConfiguration→de.codecentric.boot.admin.server.eventstore.InstanceEventStorede.codecentric.boot.admin.server.config.AdminServerHazelcastAutoConfiguration→de.codecentric.boot.admin.server.eventstore.InstanceEventStorede.codecentric.boot.admin.server.config.AdminServerWebConfiguration→de.codecentric.boot.admin.server.eventstore.InstanceEventStore
- Direction
- de.codecentric.boot.admin.server.config uses de.codecentric.boot.admin.server.eventstore, so a change to de.codecentric.boot.admin.server.eventstore can break de.codecentric.boot.admin.server.config, while a change to de.codecentric.boot.admin.server.config can't break de.codecentric.boot.admin.server.eventstore.
- Position
- Below the diagonal: de.codecentric.boot.admin.server.config uses a module listed above it, which is the healthy direction.
38→21 de.codecentric.boot.admin.server.config uses de.codecentric.boot.admin.server.web.client.cookies✕
- Connections
- 3 pairs of types, where a type in de.codecentric.boot.admin.server.config uses a type in de.codecentric.boot.admin.server.web.client.cookies.
- The types involved
de.codecentric.boot.admin.server.config.CookieStoreConfiguration→de.codecentric.boot.admin.server.web.client.cookies.CookieStoreCleanupTriggerde.codecentric.boot.admin.server.config.CookieStoreConfiguration→de.codecentric.boot.admin.server.web.client.cookies.PerInstanceCookieStorede.codecentric.boot.admin.server.config.DefaultInstanceExchangeFiltersConfiguration→de.codecentric.boot.admin.server.web.client.cookies.PerInstanceCookieStore
- Direction
- de.codecentric.boot.admin.server.config uses de.codecentric.boot.admin.server.web.client.cookies, so a change to de.codecentric.boot.admin.server.web.client.cookies can break de.codecentric.boot.admin.server.config, while a change to de.codecentric.boot.admin.server.config can't break de.codecentric.boot.admin.server.web.client.cookies.
- Position
- Below the diagonal: de.codecentric.boot.admin.server.config uses a module listed above it, which is the healthy direction.
38→23 de.codecentric.boot.admin.server.config uses de.codecentric.boot.admin.server.domain.entities✕
- Connections
- 16 pairs of types, where a type in de.codecentric.boot.admin.server.config uses a type in de.codecentric.boot.admin.server.domain.entities.
- The types involved
de.codecentric.boot.admin.server.config.AdminServerAutoConfiguration→de.codecentric.boot.admin.server.domain.entities.InstanceRepositoryde.codecentric.boot.admin.server.config.AdminServerAutoConfiguration→de.codecentric.boot.admin.server.domain.entities.SnapshottingInstanceRepositoryde.codecentric.boot.admin.server.config.DingTalkNotifierConfiguration→de.codecentric.boot.admin.server.domain.entities.InstanceRepositoryde.codecentric.boot.admin.server.config.DiscordNotifierConfiguration→de.codecentric.boot.admin.server.domain.entities.InstanceRepositoryde.codecentric.boot.admin.server.config.FeiShuNotifierConfiguration→de.codecentric.boot.admin.server.domain.entities.InstanceRepositoryde.codecentric.boot.admin.server.config.HipchatNotifierConfiguration→de.codecentric.boot.admin.server.domain.entities.InstanceRepositoryde.codecentric.boot.admin.server.config.LetsChatNotifierConfiguration→de.codecentric.boot.admin.server.domain.entities.InstanceRepositoryde.codecentric.boot.admin.server.config.MailNotifierConfiguration→de.codecentric.boot.admin.server.domain.entities.InstanceRepositoryde.codecentric.boot.admin.server.config.MattermostNotifierConfiguration→de.codecentric.boot.admin.server.domain.entities.InstanceRepositoryde.codecentric.boot.admin.server.config.MicrosoftTeamsNotifierConfiguration→de.codecentric.boot.admin.server.domain.entities.InstanceRepositoryde.codecentric.boot.admin.server.config.OpsGenieNotifierConfiguration→de.codecentric.boot.admin.server.domain.entities.InstanceRepositoryde.codecentric.boot.admin.server.config.PagerdutyNotifierConfiguration→de.codecentric.boot.admin.server.domain.entities.InstanceRepositoryde.codecentric.boot.admin.server.config.RocketChatNotifierConfiguration→de.codecentric.boot.admin.server.domain.entities.InstanceRepositoryde.codecentric.boot.admin.server.config.SlackNotifierConfiguration→de.codecentric.boot.admin.server.domain.entities.InstanceRepositoryde.codecentric.boot.admin.server.config.TelegramNotifierConfiguration→de.codecentric.boot.admin.server.domain.entities.InstanceRepositoryde.codecentric.boot.admin.server.config.WebexNotifierConfiguration→de.codecentric.boot.admin.server.domain.entities.InstanceRepository
- Direction
- de.codecentric.boot.admin.server.config uses de.codecentric.boot.admin.server.domain.entities, so a change to de.codecentric.boot.admin.server.domain.entities can break de.codecentric.boot.admin.server.config, while a change to de.codecentric.boot.admin.server.config can't break de.codecentric.boot.admin.server.domain.entities.
- Position
- Below the diagonal: de.codecentric.boot.admin.server.config uses a module listed above it, which is the healthy direction.
38→24 de.codecentric.boot.admin.server.config uses de.codecentric.boot.admin.server.notify.filter✕
- Connections
- 2 pairs of types, where a type in de.codecentric.boot.admin.server.config uses a type in de.codecentric.boot.admin.server.notify.filter.
- The types involved
de.codecentric.boot.admin.server.config.AdminServerHazelcastAutoConfiguration→de.codecentric.boot.admin.server.notify.filter.NotificationFilterde.codecentric.boot.admin.server.config.FilteringNotifierWebConfiguration→de.codecentric.boot.admin.server.notify.filter.FilteringNotifier
- Direction
- de.codecentric.boot.admin.server.config uses de.codecentric.boot.admin.server.notify.filter, so a change to de.codecentric.boot.admin.server.notify.filter can break de.codecentric.boot.admin.server.config, while a change to de.codecentric.boot.admin.server.config can't break de.codecentric.boot.admin.server.notify.filter.
- Position
- Below the diagonal: de.codecentric.boot.admin.server.config uses a module listed above it, which is the healthy direction.
38→25 de.codecentric.boot.admin.server.config uses de.codecentric.boot.admin.server.web.client.reactive✕
- Connections
- 1 pair of types, where a type in de.codecentric.boot.admin.server.config uses a type in de.codecentric.boot.admin.server.web.client.reactive.
- The types involved
de.codecentric.boot.admin.server.config.DefaultInstanceExchangeFiltersConfiguration→de.codecentric.boot.admin.server.web.client.reactive.ReactiveHttpHeadersProvider
- Direction
- de.codecentric.boot.admin.server.config uses de.codecentric.boot.admin.server.web.client.reactive, so a change to de.codecentric.boot.admin.server.web.client.reactive can break de.codecentric.boot.admin.server.config, while a change to de.codecentric.boot.admin.server.config can't break de.codecentric.boot.admin.server.web.client.reactive.
- Position
- Below the diagonal: de.codecentric.boot.admin.server.config uses a module listed above it, which is the healthy direction.
38→26 de.codecentric.boot.admin.server.config uses de.codecentric.boot.admin.server.notify.filter.web✕
- Connections
- 1 pair of types, where a type in de.codecentric.boot.admin.server.config uses a type in de.codecentric.boot.admin.server.notify.filter.web.
- The types involved
de.codecentric.boot.admin.server.config.FilteringNotifierWebConfiguration→de.codecentric.boot.admin.server.notify.filter.web.NotificationFilterController
- Direction
- de.codecentric.boot.admin.server.config uses de.codecentric.boot.admin.server.notify.filter.web, so a change to de.codecentric.boot.admin.server.notify.filter.web can break de.codecentric.boot.admin.server.config, while a change to de.codecentric.boot.admin.server.config can't break de.codecentric.boot.admin.server.notify.filter.web.
- Position
- Below the diagonal: de.codecentric.boot.admin.server.config uses a module listed above it, which is the healthy direction.
38→27 de.codecentric.boot.admin.server.config uses de.codecentric.boot.admin.server.web.client✕
- Connections
- 14 pairs of types, where a type in de.codecentric.boot.admin.server.config uses a type in de.codecentric.boot.admin.server.web.client.
- The types involved
de.codecentric.boot.admin.server.config.AdminServerAutoConfiguration→de.codecentric.boot.admin.server.web.client.Builderde.codecentric.boot.admin.server.config.AdminServerCloudFoundryAutoConfiguration→de.codecentric.boot.admin.server.web.client.CloudFoundryHttpHeaderProviderde.codecentric.boot.admin.server.config.AdminServerInstanceWebClientConfiguration→de.codecentric.boot.admin.server.web.client.Builderde.codecentric.boot.admin.server.config.AdminServerInstanceWebClientConfiguration→de.codecentric.boot.admin.server.web.client.InstanceWebClientCustomizerde.codecentric.boot.admin.server.config.DefaultInstanceExchangeFiltersConfiguration→de.codecentric.boot.admin.server.web.client.HttpHeadersProviderde.codecentric.boot.admin.server.config.DefaultInstanceExchangeFiltersConfiguration→de.codecentric.boot.admin.server.web.client.InstanceExchangeFilterFunctionde.codecentric.boot.admin.server.config.DefaultInstanceExchangeFiltersConfiguration→de.codecentric.boot.admin.server.web.client.LegacyEndpointConverterde.codecentric.boot.admin.server.config.HttpHeadersProviderConfiguration→de.codecentric.boot.admin.server.web.client.BasicAuthHttpHeaderProviderde.codecentric.boot.admin.server.config.InstanceAuthProperties→de.codecentric.boot.admin.server.web.client.InstanceCredentialsde.codecentric.boot.admin.server.config.InstanceExchangeFiltersConfiguration→de.codecentric.boot.admin.server.web.client.InstanceExchangeFilterFunctionde.codecentric.boot.admin.server.config.InstanceExchangeFiltersConfiguration→de.codecentric.boot.admin.server.web.client.InstanceWebClientCustomizerde.codecentric.boot.admin.server.config.LegacyEndpointConvertersConfiguration→de.codecentric.boot.admin.server.web.client.LegacyEndpointConverterde.codecentric.boot.admin.server.config.ReactiveRestApiConfiguration→de.codecentric.boot.admin.server.web.client.Builderde.codecentric.boot.admin.server.config.ServletRestApiConfiguration→de.codecentric.boot.admin.server.web.client.Builder
- Direction
- de.codecentric.boot.admin.server.config uses de.codecentric.boot.admin.server.web.client, so a change to de.codecentric.boot.admin.server.web.client can break de.codecentric.boot.admin.server.config, while a change to de.codecentric.boot.admin.server.config can't break de.codecentric.boot.admin.server.web.client.
- Position
- Below the diagonal: de.codecentric.boot.admin.server.config uses a module listed above it, which is the healthy direction.
38→31 de.codecentric.boot.admin.server.config uses de.codecentric.boot.admin.server.services✕
- Connections
- 18 pairs of types, where a type in de.codecentric.boot.admin.server.config uses a type in de.codecentric.boot.admin.server.services.
- The types involved
de.codecentric.boot.admin.server.config.AdminServerAutoConfiguration→de.codecentric.boot.admin.server.services.ApplicationRegistryde.codecentric.boot.admin.server.config.AdminServerAutoConfiguration→de.codecentric.boot.admin.server.services.EndpointDetectionTriggerde.codecentric.boot.admin.server.config.AdminServerAutoConfiguration→de.codecentric.boot.admin.server.services.EndpointDetectorde.codecentric.boot.admin.server.config.AdminServerAutoConfiguration→de.codecentric.boot.admin.server.services.HealthGroupsCachede.codecentric.boot.admin.server.config.AdminServerAutoConfiguration→de.codecentric.boot.admin.server.services.HealthGroupsCacheCleanupListenerde.codecentric.boot.admin.server.config.AdminServerAutoConfiguration→de.codecentric.boot.admin.server.services.InfoUpdateTriggerde.codecentric.boot.admin.server.config.AdminServerAutoConfiguration→de.codecentric.boot.admin.server.services.InfoUpdaterde.codecentric.boot.admin.server.config.AdminServerAutoConfiguration→de.codecentric.boot.admin.server.services.InstanceFilterde.codecentric.boot.admin.server.config.AdminServerAutoConfiguration→de.codecentric.boot.admin.server.services.InstanceIdGeneratorde.codecentric.boot.admin.server.config.AdminServerAutoConfiguration→de.codecentric.boot.admin.server.services.InstanceRegistryde.codecentric.boot.admin.server.config.AdminServerAutoConfiguration→de.codecentric.boot.admin.server.services.StatusUpdateTriggerde.codecentric.boot.admin.server.config.AdminServerAutoConfiguration→de.codecentric.boot.admin.server.services.StatusUpdaterde.codecentric.boot.admin.server.config.AdminServerCloudFoundryAutoConfiguration→de.codecentric.boot.admin.server.services.InstanceIdGeneratorde.codecentric.boot.admin.server.config.AdminServerWebConfiguration→de.codecentric.boot.admin.server.services.ApplicationRegistryde.codecentric.boot.admin.server.config.AdminServerWebConfiguration→de.codecentric.boot.admin.server.services.HealthGroupsCachede.codecentric.boot.admin.server.config.AdminServerWebConfiguration→de.codecentric.boot.admin.server.services.InstanceRegistryde.codecentric.boot.admin.server.config.ReactiveRestApiConfiguration→de.codecentric.boot.admin.server.services.InstanceRegistryde.codecentric.boot.admin.server.config.ServletRestApiConfiguration→de.codecentric.boot.admin.server.services.InstanceRegistry
- Direction
- de.codecentric.boot.admin.server.config uses de.codecentric.boot.admin.server.services, so a change to de.codecentric.boot.admin.server.services can break de.codecentric.boot.admin.server.config, while a change to de.codecentric.boot.admin.server.config can't break de.codecentric.boot.admin.server.services.
- Position
- Below the diagonal: de.codecentric.boot.admin.server.config uses a module listed above it, which is the healthy direction.
38→33 de.codecentric.boot.admin.server.config uses de.codecentric.boot.admin.server.notify✕
- Connections
- 32 pairs of types, where a type in de.codecentric.boot.admin.server.config uses a type in de.codecentric.boot.admin.server.notify. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
de.codecentric.boot.admin.server.config.AdminServerNotifierAutoConfiguration→de.codecentric.boot.admin.server.notify.NotifierProxyPropertiesde.codecentric.boot.admin.server.config.CompositeNotifierConfiguration→de.codecentric.boot.admin.server.notify.CompositeNotifierde.codecentric.boot.admin.server.config.CompositeNotifierConfiguration→de.codecentric.boot.admin.server.notify.Notifierde.codecentric.boot.admin.server.config.DingTalkNotifierConfiguration→de.codecentric.boot.admin.server.notify.DingTalkNotifierde.codecentric.boot.admin.server.config.DingTalkNotifierConfiguration→de.codecentric.boot.admin.server.notify.NotifierProxyPropertiesde.codecentric.boot.admin.server.config.DiscordNotifierConfiguration→de.codecentric.boot.admin.server.notify.DiscordNotifierde.codecentric.boot.admin.server.config.DiscordNotifierConfiguration→de.codecentric.boot.admin.server.notify.NotifierProxyPropertiesde.codecentric.boot.admin.server.config.FeiShuNotifierConfiguration→de.codecentric.boot.admin.server.notify.FeiShuNotifierde.codecentric.boot.admin.server.config.FeiShuNotifierConfiguration→de.codecentric.boot.admin.server.notify.NotifierProxyPropertiesde.codecentric.boot.admin.server.config.HipchatNotifierConfiguration→de.codecentric.boot.admin.server.notify.HipchatNotifierde.codecentric.boot.admin.server.config.HipchatNotifierConfiguration→de.codecentric.boot.admin.server.notify.NotifierProxyPropertiesde.codecentric.boot.admin.server.config.LetsChatNotifierConfiguration→de.codecentric.boot.admin.server.notify.LetsChatNotifierde.codecentric.boot.admin.server.config.LetsChatNotifierConfiguration→de.codecentric.boot.admin.server.notify.NotifierProxyPropertiesde.codecentric.boot.admin.server.config.MailNotifierConfiguration→de.codecentric.boot.admin.server.notify.MailNotifierde.codecentric.boot.admin.server.config.MattermostNotifierConfiguration→de.codecentric.boot.admin.server.notify.MattermostNotifierde.codecentric.boot.admin.server.config.MattermostNotifierConfiguration→de.codecentric.boot.admin.server.notify.NotifierProxyPropertiesde.codecentric.boot.admin.server.config.MicrosoftTeamsNotifierConfiguration→de.codecentric.boot.admin.server.notify.MicrosoftTeamsNotifierde.codecentric.boot.admin.server.config.MicrosoftTeamsNotifierConfiguration→de.codecentric.boot.admin.server.notify.NotifierProxyPropertiesde.codecentric.boot.admin.server.config.NotifierTriggerConfiguration→de.codecentric.boot.admin.server.notify.NotificationTriggerde.codecentric.boot.admin.server.config.NotifierTriggerConfiguration→de.codecentric.boot.admin.server.notify.Notifierde.codecentric.boot.admin.server.config.OpsGenieNotifierConfiguration→de.codecentric.boot.admin.server.notify.NotifierProxyPropertiesde.codecentric.boot.admin.server.config.OpsGenieNotifierConfiguration→de.codecentric.boot.admin.server.notify.OpsGenieNotifierde.codecentric.boot.admin.server.config.PagerdutyNotifierConfiguration→de.codecentric.boot.admin.server.notify.NotifierProxyPropertiesde.codecentric.boot.admin.server.config.PagerdutyNotifierConfiguration→de.codecentric.boot.admin.server.notify.PagerdutyNotifierde.codecentric.boot.admin.server.config.RocketChatNotifierConfiguration→de.codecentric.boot.admin.server.notify.NotifierProxyProperties
- Direction
- de.codecentric.boot.admin.server.config uses de.codecentric.boot.admin.server.notify, so a change to de.codecentric.boot.admin.server.notify can break de.codecentric.boot.admin.server.config, while a change to de.codecentric.boot.admin.server.config can't break de.codecentric.boot.admin.server.notify.
- Position
- Below the diagonal: de.codecentric.boot.admin.server.config uses a module listed above it, which is the healthy direction.
38→34 de.codecentric.boot.admin.server.config uses de.codecentric.boot.admin.server.web✕
- Connections
- 2 pairs of types, where a type in de.codecentric.boot.admin.server.config uses a type in de.codecentric.boot.admin.server.web.
- The types involved
de.codecentric.boot.admin.server.config.AdminServerWebConfiguration→de.codecentric.boot.admin.server.web.ApplicationsControllerde.codecentric.boot.admin.server.config.AdminServerWebConfiguration→de.codecentric.boot.admin.server.web.InstancesController
- Direction
- de.codecentric.boot.admin.server.config uses de.codecentric.boot.admin.server.web, so a change to de.codecentric.boot.admin.server.web can break de.codecentric.boot.admin.server.config, while a change to de.codecentric.boot.admin.server.config can't break de.codecentric.boot.admin.server.web.
- Position
- Below the diagonal: de.codecentric.boot.admin.server.config uses a module listed above it, which is the healthy direction.
38→36 de.codecentric.boot.admin.server.config uses de.codecentric.boot.admin.server.web.reactive✕
- Connections
- 1 pair of types, where a type in de.codecentric.boot.admin.server.config uses a type in de.codecentric.boot.admin.server.web.reactive.
- The types involved
de.codecentric.boot.admin.server.config.ReactiveRestApiConfiguration→de.codecentric.boot.admin.server.web.reactive.InstancesProxyController
- Direction
- de.codecentric.boot.admin.server.config uses de.codecentric.boot.admin.server.web.reactive, so a change to de.codecentric.boot.admin.server.web.reactive can break de.codecentric.boot.admin.server.config, while a change to de.codecentric.boot.admin.server.config can't break de.codecentric.boot.admin.server.web.reactive.
- Position
- Below the diagonal: de.codecentric.boot.admin.server.config uses a module listed above it, which is the healthy direction.
38→37 de.codecentric.boot.admin.server.config uses de.codecentric.boot.admin.server.web.servlet✕
- Connections
- 1 pair of types, where a type in de.codecentric.boot.admin.server.config uses a type in de.codecentric.boot.admin.server.web.servlet.
- The types involved
de.codecentric.boot.admin.server.config.ServletRestApiConfiguration→de.codecentric.boot.admin.server.web.servlet.InstancesProxyController
- Direction
- de.codecentric.boot.admin.server.config uses de.codecentric.boot.admin.server.web.servlet, so a change to de.codecentric.boot.admin.server.web.servlet can break de.codecentric.boot.admin.server.config, while a change to de.codecentric.boot.admin.server.config can't break de.codecentric.boot.admin.server.web.servlet.
- Position
- Below the diagonal: de.codecentric.boot.admin.server.config uses a module listed above it, which is the healthy direction.
39→38 de.codecentric.boot.admin uses de.codecentric.boot.admin.server.config✕
- Connections
- 1 pair of types, where a type in de.codecentric.boot.admin uses a type in de.codecentric.boot.admin.server.config.
- The types involved
de.codecentric.boot.admin.SpringBootAdminEurekaApplication→de.codecentric.boot.admin.server.config.AdminServerProperties
- Direction
- de.codecentric.boot.admin uses de.codecentric.boot.admin.server.config, so a change to de.codecentric.boot.admin.server.config can break de.codecentric.boot.admin, while a change to de.codecentric.boot.admin can't break de.codecentric.boot.admin.server.config.
- Position
- Below the diagonal: de.codecentric.boot.admin uses a module listed above it, which is the healthy direction.
40→2 de.codecentric.boot.admin.server.ui.config uses de.codecentric.boot.admin.server.ui.extensions✕
- Connections
- 1 pair of types, where a type in de.codecentric.boot.admin.server.ui.config uses a type in de.codecentric.boot.admin.server.ui.extensions.
- The types involved
de.codecentric.boot.admin.server.ui.config.AdminServerUiAutoConfiguration→de.codecentric.boot.admin.server.ui.extensions.UiExtensions
- Direction
- de.codecentric.boot.admin.server.ui.config uses de.codecentric.boot.admin.server.ui.extensions, so a change to de.codecentric.boot.admin.server.ui.extensions can break de.codecentric.boot.admin.server.ui.config, while a change to de.codecentric.boot.admin.server.ui.config can't break de.codecentric.boot.admin.server.ui.extensions.
- Position
- Below the diagonal: de.codecentric.boot.admin.server.ui.config uses a module listed above it, which is the healthy direction.
40→9 de.codecentric.boot.admin.server.ui.config uses de.codecentric.boot.admin.server.ui.web✕
- Connections
- 5 pairs of types, where a type in de.codecentric.boot.admin.server.ui.config uses a type in de.codecentric.boot.admin.server.ui.web.
- The types involved
de.codecentric.boot.admin.server.ui.config.AdminServerUiAutoConfiguration→de.codecentric.boot.admin.server.ui.web.UiControllerde.codecentric.boot.admin.server.ui.config.AdminServerUiProperties→de.codecentric.boot.admin.server.ui.web.ExternalViewde.codecentric.boot.admin.server.ui.config.AdminServerUiProperties→de.codecentric.boot.admin.server.ui.web.ViewSettingsde.codecentric.boot.admin.server.ui.config.AdminUiWebMvcConfig→de.codecentric.boot.admin.server.ui.web.HomepageForwardingFilterConfigde.codecentric.boot.admin.server.ui.config.AdminUiWebfluxConfig→de.codecentric.boot.admin.server.ui.web.HomepageForwardingFilterConfig
- Direction
- de.codecentric.boot.admin.server.ui.config uses de.codecentric.boot.admin.server.ui.web, so a change to de.codecentric.boot.admin.server.ui.web can break de.codecentric.boot.admin.server.ui.config, while a change to de.codecentric.boot.admin.server.ui.config can't break de.codecentric.boot.admin.server.ui.web.
- Position
- Below the diagonal: de.codecentric.boot.admin.server.ui.config uses a module listed above it, which is the healthy direction.
40→19 de.codecentric.boot.admin.server.ui.config uses de.codecentric.boot.admin.server.ui.web.reactive✕
- Connections
- 1 pair of types, where a type in de.codecentric.boot.admin.server.ui.config uses a type in de.codecentric.boot.admin.server.ui.web.reactive.
- The types involved
de.codecentric.boot.admin.server.ui.config.AdminUiWebfluxConfig→de.codecentric.boot.admin.server.ui.web.reactive.HomepageForwardingFilter
- Direction
- de.codecentric.boot.admin.server.ui.config uses de.codecentric.boot.admin.server.ui.web.reactive, so a change to de.codecentric.boot.admin.server.ui.web.reactive can break de.codecentric.boot.admin.server.ui.config, while a change to de.codecentric.boot.admin.server.ui.config can't break de.codecentric.boot.admin.server.ui.web.reactive.
- Position
- Below the diagonal: de.codecentric.boot.admin.server.ui.config uses a module listed above it, which is the healthy direction.
40→20 de.codecentric.boot.admin.server.ui.config uses de.codecentric.boot.admin.server.ui.web.servlet✕
- Connections
- 2 pairs of types, where a type in de.codecentric.boot.admin.server.ui.config uses a type in de.codecentric.boot.admin.server.ui.web.servlet.
- The types involved
de.codecentric.boot.admin.server.ui.config.AdminUiWebMvcConfig→de.codecentric.boot.admin.server.ui.web.servlet.HomepageForwardingFilterde.codecentric.boot.admin.server.ui.config.AdminUiWebMvcConfig→de.codecentric.boot.admin.server.ui.web.servlet.SbaSettingsAcceptHeaderFilter
- Direction
- de.codecentric.boot.admin.server.ui.config uses de.codecentric.boot.admin.server.ui.web.servlet, so a change to de.codecentric.boot.admin.server.ui.web.servlet can break de.codecentric.boot.admin.server.ui.config, while a change to de.codecentric.boot.admin.server.ui.config can't break de.codecentric.boot.admin.server.ui.web.servlet.
- Position
- Below the diagonal: de.codecentric.boot.admin.server.ui.config uses a module listed above it, which is the healthy direction.
40→38 de.codecentric.boot.admin.server.ui.config uses de.codecentric.boot.admin.server.config✕
- Connections
- 3 pairs of types, where a type in de.codecentric.boot.admin.server.ui.config uses a type in de.codecentric.boot.admin.server.config.
- The types involved
de.codecentric.boot.admin.server.ui.config.AdminServerUiAutoConfiguration→de.codecentric.boot.admin.server.config.AdminServerPropertiesde.codecentric.boot.admin.server.ui.config.AdminUiWebMvcConfig→de.codecentric.boot.admin.server.config.AdminServerPropertiesde.codecentric.boot.admin.server.ui.config.AdminUiWebfluxConfig→de.codecentric.boot.admin.server.config.AdminServerProperties
- Direction
- de.codecentric.boot.admin.server.ui.config uses de.codecentric.boot.admin.server.config, so a change to de.codecentric.boot.admin.server.config can break de.codecentric.boot.admin.server.ui.config, while a change to de.codecentric.boot.admin.server.ui.config can't break de.codecentric.boot.admin.server.config.
- Position
- Below the diagonal: de.codecentric.boot.admin.server.ui.config uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
At a glance — Accessibility
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A03:2025 — Software Supply Chain Failures | 58 | High / Critical |
| A05:2025 — Injection | 54 | High / Critical |
| A02:2025 — Security Misconfiguration | 13 | High / Critical |
Roadmap
Top priorities: Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href; Add a text alternative — alt on images (alt="" for purely decorative ones), a title or aria-label on meaningful svg, an aria-label or inner fallback content on canvas, and a captions <track> on video; Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href. | +6.6 pts | Medium | Keyboard semantics |
| Add a text alternative — alt on images (alt="" for purely decorative ones), a title or aria-label on meaningful svg, an aria-label or inner fallback content on canvas, and a captions <track> on video. | +3.4 pts | Medium | Text alternatives |
| Resolve the 6 No assertions (empty test) finding(s) in Test Quality — start with SpringBootAdminConsulApplicationTest.java, SpringBootAdminHazelcastApplicationTest.java, SpringBootAdminReactiveApplicationTest.java. | +1.4 pts | Low | Test Quality |
| Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1. | +2.3 pts | Medium | Visual & motion safety |
| Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh. | +1.8 pts | Medium | Page structure |
| Give every control a programmatic label (a <label for> / wrapping <label> / aria-label) and every button text — a placeholder is not a label. | +1.5 pts | Medium | Forms & labels |
| Resolve the 62 No assertions finding(s) in Test Quality — start with QueryIndexEndpointStrategyTest.java (10), UiControllerTest.java (6), InstanceDiscoveryListenerTest.java (5). | +1.3 pts | Medium | Test Quality |
| Set connect and read timeouts on every client (`RestTemplateBuilder.connectTimeout/readTimeout`, WebClient `responseTimeout`, `HttpRequest.Builder.timeout`, `HttpURLConnection.setReadTimeout`, Feign `connectTimeout`/`readTimeout` in configuration), and wrap calls to dependencies in resilience4j `@Retry`/`@CircuitBreaker`/`@TimeLimiter` (or Spring Retry). | +1.3 pts | Medium | Outbound HTTP resilience |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 0.0 | Slop | Dependency Vulnerabilities: Critical CVE: REDACTED |
| REDACTED | 0.4 | Slop | Dependency Vulnerabilities: High CVE: REDACTED |
| REDACTED | 2.3 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.3 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.3 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.4 | Slop | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 2.7 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.7 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 3.7 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.1 | Mixed | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 5.8 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.8 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| spring-boot-admin-samples/spring-boot-admin-sample-consul/src/test/java/de/codecentric/boot/admin/sample/SpringBootAdminConsulApplicationTest.java | 6.5 | Mixed | Test Quality: No assertions (empty test): contextLoads |
| spring-boot-admin-samples/spring-boot-admin-sample-hazelcast/src/test/java/de/codecentric/boot/admin/sample/SpringBootAdminHazelcastApplicationTest.java | 6.5 | Mixed | Test Quality: No assertions (empty test): contextLoads |
| spring-boot-admin-samples/spring-boot-admin-sample-reactive/src/test/java/de/codecentric/boot/admin/sample/SpringBootAdminReactiveApplicationTest.java | 6.5 | Mixed | Test Quality: No assertions (empty test): contextLoads |
| spring-boot-admin-samples/spring-boot-admin-sample-servlet/src/test/java/de/codecentric/boot/admin/sample/SpringBootAdminServletApplicationTest.java | 6.5 | Mixed | Test Quality: No assertions (empty test): contextLoads |
| spring-boot-admin-samples/spring-boot-admin-sample-zookeeper/src/test/java/de/codecentric/boot/admin/sample/SpringBootAdminZookeeperApplicationTest.java | 6.5 | Mixed | Test Quality: No assertions (empty test): contextLoads |
| spring-boot-admin-samples/spring-boot-admin-sample-eureka/src/test/java/de/codecentric/boot/admin/SpringBootAdminEurekaApplicationTest.java | 6.5 | Mixed | Test Quality: No assertions (empty test): contextLoads |
| spring-boot-admin-server/src/test/java/de/codecentric/boot/admin/server/services/endpoints/QueryIndexEndpointStrategyTest.java | 7.0 | Mixed | Test Quality: No assertions: should_retry |
| spring-boot-admin-samples/spring-boot-admin-sample-hazelcast/src/main/java/de/codecentric/boot/admin/sample/SpringBootAdminHazelcastApplication.java | 7.0 | Mixed | Code Duplication: Near-duplicate member family (4 members, 13 shared lines) |
How the grades work
A definite problem that already costs you something and drags the score down: a missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here tends to cause failures elsewhere.
Likely wrong, but not failing yet. It degrades the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to carry for two years either.
Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.
Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.
Methodology & how to trust this report
This survey is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. All 73 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.9, the weighted average across measured dimensions.
What we checked — 73 dimensions across the health lenses
- Can you open the finding? Real findings cite a repo-relative file and line you can open at the cited line — never an absolute scratch path. Here, 465 of 478 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
- 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 720 test(s) behind this row are the ones the code-model census could read, and this repository also carries at least 97 test source file(s) (.ts, .js, .tsx) 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 MEASURED: the JavaScript/TypeScript suite could not be re-run in the analyzer sandbox — the dependency install for spring-boot-admin-server-ui/ could not reach codeload.github.com, which the analyzer sandbox's egress allowlist does not carry (npm error 403 403 Forbidden - GET https://codeload.github.com/SteKoe/vue-toast-notificationcenter/tar.gz/refs/tags/1.0.0-RC5), so the suite never ran. This is OUR limitation, not a defect in the repo — it is excluded from the score.
- 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 for the vitest suite in spring-boot-admin-server-ui/ was NOT MEASURED: the dependency install for spring-boot-admin-server-ui/ could not reach codeload.github.com, which the analyzer sandbox's egress allowlist does not carry (npm error 403 403 Forbidden - GET https://codeload.github.com/SteKoe/vue-toast-notificationcenter/tar.gz/refs/tags/1.0.0-RC5), so the suite never ran. This is OUR limitation, not a defect in the repository, and the suite is excluded from the measurement rather than counted against it.
- 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; 168 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.
- D14 License Compliance — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This repository declares package.json, but the licence verdict published here was taken over its JVM dependencies. Nothing was read about its npm dependencies' licensing in either direction, and a clean score on this card must not be read as covering them.
- 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 naming rules read C# through Roslyn and every other language through its sidecar model; these languages are left out (PHP's reading is its own change, a Roslyn-loaded VB or F# project has no population builder yet). Their declarations carry no naming verdict this run — this says nothing about whether their names are consistent.
- 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. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these 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 a COLLECTOR gap, not an environment fault: it declares a published package (spring-boot-admin-dependencies/pom.xml), but no published-package marker D22 reads admitted any project here, so this ecosystem's public API has no collector, and the remedy is to write one — no change to the scan image can close it.
- D24 Comment Value — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 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 308 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.
- D32 Data Compliance (PII/GDPR) — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `spring-boot-admin-docs/src/site/docusaurus.config.ts` produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
- D34 Knowledge Freshness — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. File-level freshness contradicts repo activity: 280 commits in the last 90 days, yet 110 of 142 significant files carry no living knowledge. Those two readings cannot both be true, so the per-file recency signal is treated as unreliable here and freshness is not scored for this run.
- AXR1 Runtime accessibility — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via DockerCompose (REDACTED). compose up failed (exit 18 — an image could not be pulled) — [DEPRECATION NOTICE] Docker Image Format v1 and Docker Image manifest version 2, schema 1 support is disabled by default and will be removed in an upcoming release. Suggest the author of docker.io/tutum/mongodb:latest to upgrade the image to the OCI Format or Docker Image manifest v2, schema 2. More information at https://docs.docker.com/go/deprecated-image-specs/; the earlier `compose pull` step reported: [DEPRECATION NOTICE] Docker Image Format v1 and Docker Image manifest version 2, schema 1 support is disabled by default and will be removed in an upcoming release. Suggest the author of docker.io/springcloud/stores:latest to upgrade the image to the OCI Format or Docker Image manifest v2, schema 2. More information at https://docs.docker.com/go/deprecated-image-specs/; the runtime sandbox reaches registries only through the in-fence pull-through mirror, so an image the mirror does not carry cannot be fetched — this is a limit of our sandbox, not of your stack; runtime evidence skipped.
- C1 Data Protection — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These personal data controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks personal data controls.
- C2 Access Controls — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These authorization controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks authorization controls.
- C3 Audit Trail — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These audit controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks audit controls.
- C4 Data Retention — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These retention controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks retention controls.
- C5 Data-Subject Rights — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These data-subject rights controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks data-subject rights controls.
- ED5 Idempotency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check decides whether a handler's mutation is safe to re-run by recognising its persistence writes (a database save, a repository write, an event publish) and its guards. Those markers are .NET member names, so in this repository's language a write such as `repository.save(order)` is not recognised and a same-named call on an unrelated library type could be. The handlers were found; their idempotency was neither confirmed nor ruled out.
- GD1 Unfinished & placeholder code — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, F#, JavaScript/TypeScript, Dart, Ruby, Scala, Rust and Java source only, and this repository's Vue components 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.
- IC1 Incompleteness & stubs — 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, JavaScript/TypeScript, Java, Dart, Ruby, Scala and Rust source only, and this repository's Vue components 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.
- M4 Documentation accuracy — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
- R10 Code Duplication — 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. 1 further occurrence(s) are not listed individually; the score already reflects all 41.
- R4 Test Coverage — 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. 13 further occurrence(s) are not listed individually; the score already reflects all 53.
- S1 Web-Security Posture — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These web-security controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks web-security controls.
- X1 Async correctness — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This check's reader does not cover every language in this repository. The score describes the part it read, which is most of the product; the rest is a gap in this analyzer's language reach.
- X12 Unreachable branch — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This check's reader does not cover every language in this repository. The score describes the part it read, which is most of the product; the rest is a gap in this analyzer's language reach.
- X17 Uncapped recursion over a caller-supplied document — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This check's reader does not cover every language in this repository. The score describes the part it read, which is most of the product; the rest is a gap in this analyzer's language reach.
- X27 Collection changed while being enumerated — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
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.
- 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.
- D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
- 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.
- D24 Comment Value: Comment value is measured as redundancy only: a comment that repeats its code's words is found, but a paraphrase in other words, a vague comment, or one the code contradicts is not, and whether a comment is valuable is not claimed. Comments in other scripts or languages, and outside C#, are not judged.
- D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
- D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a 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.
- AC1 Text alternatives: Alt-text is detected structurally — the scan sees that an alternative EXISTS, not whether it meaningfully describes the image, and decorative-vs-missing is judged by attribute shape; runtime-injected images and a non-role=img decorative svg are out of scope. This is accessibility readiness, never a WCAG conformance claim.
- AC2 Forms & labels: Label association is read from static markup — a label wired up at runtime (JS-set aria-labelledby, framework-injected ids) reads as missing, a present label says nothing about whether its text is correct. A known UI-library field component (e.g. a JSX <TextField>) is now checked conservatively — flagged only when it carries NO label/aria-label/aria-labelledby/id/name — but wrapper/context-labelled libraries (Chakra/Radix FormControl+FormLabel) aren't statically visible (possible false positive) and non-JSX lowercased components are still skipped. A click handler on a plain element is now asked for a name too (it is a control the author declared), but the subtree test that answers it is deliberately generous: any DYNAMIC text expression in the subtree counts as a name, so an icon chosen by a ternary ({cond ? <IconA/> : <IconB/>}) reads as named, and a glyph component from a library the icon-import list does not know still names its parent. A clean result is "no unlabelled control found", not a labelling proof.
- AC3 Page structure: Page structure is read from the static markup tree — landmarks, headings and lang injected at runtime aren't seen, heading ORDER is checked structurally (not against the rendered visual hierarchy), and lang/title/main fire only on full documents, never partials, and the data-table check sees header-cell presence (a <th> exists), not whether each header correctly associates with its cells. Static readiness, not conformance.
- AC4 Keyboard semantics: Keyboard semantics are inferred from markup attributes — interactivity wired purely in script, focus managed at runtime, and component-level handlers are invisible. A clean result means "no static keyboard-trap shape", not a keyboard-operability proof.
- 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.
- 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.
- M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
- P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
- P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
Dimensions
D1 · Cyclomatic Complexity
7 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was BeansTools.formatBeans at 23.
What to do
- Bring the 7 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with BeansTools.formatBeans (cyclomatic 23), EnvTools.formatEnv (cyclomatic 19), transformToJSON.transformToJSON (cyclomatic 18). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 7 together lifts Cyclomatic Complexity from 9.0 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
D2 · Cognitive Complexity
11 method(s) exceeded the cognitive complexity threshold of 15; the worst was transformToJSON.transformToJSON at 47.
What to do
- Bring the 11 bodies over 15 down to 15 or less in Cognitive Complexity — start with transformToJSON.transformToJSON (cognitive 47), ThreadDumpTools.formatThreadDump (cognitive 41), BeansTools.formatBeans (cognitive 38). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 11 together lifts Cognitive Complexity from 7.9 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
D3 · God Classes
3 god class(es) detected.
What to do
- Resolve the 2 FunctionTooLong finding(s) in God Classes — start with HexMesh.tsx, dependencyTree.ts. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 TooManyMethods finding(s) in God Classes — start with instance.ts. — One of this dimension's main actionable groups (1 warning-level).
D4 · Code Duplication
25 duplicated block group(s) detected. 1.2 % of the production lines (697 of 58,798) are in a reported copy. A further 19 rows report members as variants of one another; the share counts each copied line once, however many rows cite it. Measured on part of this repository only: .ts (41% 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 Edited copy of a member (6 corresponding lines) finding(s) in Code Duplication — start with LegacyEndpointConverters.java, StatusUpdateTrigger.java, LetsChatNotifier.java. — One of this dimension's main actionable groups (4 warning-level).
- Resolve the 3 Edited copy of a member (7 corresponding lines) finding(s) in Code Duplication — start with InfoUpdateTrigger.java, AdminServerWebConfiguration.java, MicrosoftTeamsNotifier.java. — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 3 Duplicated block (10 lines × 2) finding(s) in Code Duplication — start with ScheduledTasksTools.java, OpsGenieNotifier.java, AbstractEventHandler.java. — One of this dimension's main actionable groups (3 warning-level).
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, with abstractness counted on 14 of the 20 (the rest declare no modelled class or interface, export only macros, declare types in source no model reads, or have no source directory of their own).
What to do
- Resolve the 2 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (2 warning-level).
D6 · Cohesion (LCOM4)
2 of 73 classes have LCOM4 above 3.
What to do
- Resolve the 2 Low cohesion finding(s) in Cohesion (LCOM4) — start with StatusUpdater.java, SnapshottingInstanceRepository.java. — One of this dimension's main actionable groups (2 warning-level).
D10 · Test Quality
0 skipped, 68 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 720 tests. Measured on the .java suite only — at least 97 test source file(s) (.ts, .js, .tsx) went unread, so its test quality is unmeasured and is not in these counts.
What to do
- Resolve the 6 No assertions (empty test) finding(s) in Test Quality — start with SpringBootAdminConsulApplicationTest.java, SpringBootAdminHazelcastApplicationTest.java, SpringBootAdminReactiveApplicationTest.java. — One of this dimension's main actionable groups (6 issue-level).
- Resolve the 62 No assertions finding(s) in Test Quality — start with QueryIndexEndpointStrategyTest.java (10), UiControllerTest.java (6), InstanceDiscoveryListenerTest.java (5). — One of this dimension's main actionable groups (62 warning-level).
- Resolve the 6 Test project verifies nothing finding(s) in Test Quality — start with SpringBootAdminConsulApplicationTest.java, SpringBootAdminEurekaApplicationTest.java, SpringBootAdminHazelcastApplicationTest.java. — One of this dimension's main actionable groups (6 warning-level).
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D14 · License Compliance
0 of 1 declared JVM dependency artifact(s) use a banned license. Licences were resolved from the POMs Maven Central publishes, over the coordinates this repository's 23 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. 124 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. ★ COVERAGE OF THIS VERDICT: it grades this repository's JVM dependencies and nothing else. The repository also declares package.json, and the licences of those dependencies were NOT read by this pass — a gap in this engine's coverage, not a statement about them. So this result says the graded closure carries no banned licence; it does NOT say this repository's licensing is clear.
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window. Repeated repair below the complexity floor: spring-boot-admin-server/src/main/java/de/codecentric/boot/admin/server/config/AdminServerHazelcastAutoConfiguration.java (4 of 6 changes were fixes)
What to do
- Resolve the 1 Repeated repair finding(s) in Churn × Complexity Hotspots — start with AdminServerHazelcastAutoConfiguration.java. — One of this dimension's main actionable groups (1 warning-level).
D16 · Bus Factor
10 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is spring-boot-admin-server/src/main/java/de/codecentric/boot/admin/server/notify/MicrosoftTeamsNotifier.java. Counted over 142 of the 352 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
D17 · Explicit Debt
1 deducted task-comment markers across 36393 LoC (0.0/KLoC) → score 10.0. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
What to do
- Resolve the 1 TodoComment finding(s) in Explicit Debt — start with ApplicationRegistry.java. — One of this dimension's main actionable groups (1 warning-level).
D19 · Documentation Quality
2 of 2 documentation facets pass in full. 71 document(s) read across 5 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 — start with REDACTED. — One of this dimension's main actionable groups (1 recommendation-level).
D24 · Comment Value
3 of 245 judged comments only repeat the code they sit on (1.2 %). 6 comment(s) in another language or script were not judged.
What to do
- Resolve the 3 redundant comment finding(s) in Comment Value — start with ViewRegistry.ts, axios.spec.ts, index.spec.ts. — One of this dimension's main actionable groups (3 recommendation-level).
D26 · Project Cohesion
2 of 17 build units (Maven, npm) flagged as possibly oversized/incoherent.
What to do
- Resolve the 2 Projects may be oversized for their cohesion finding(s) in Project Cohesion — start with REDACTED (2). — One of this dimension's main actionable groups (2 recommendation-level).
D27 · Navigability
30 % of calls cross a namespace and 5 % 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)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
54 finding(s): 0 critical, 39 high, 15 medium, 0 low. 32 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. semgrep hit a parse error in 2 file(s) — `mvnw` (line 86, line 124, line 134, …), `spring-boot-admin-docs/src/site/docusaurus.config.ts` (line 44, line 172) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them. Separately, one or more rules could not re-parse an embedded snippet in 3 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.
What to do
- Resolve the 4 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2), REDACTED, REDACTED. — One of this dimension's main actionable groups (4 issue-level).
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- No action in Static Analysis (SAST) — all 32 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 (32 issue-level, 0 of them charged here).
D30 · Dependency Vulnerabilities
50 finding(s): 4 critical, 26 high, 18 medium, 2 low.
What to do
- Resolve the 25 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (25). — One of this dimension's main actionable groups (25 issue-level).
- Resolve the 4 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (4). — One of this dimension's main actionable groups (4 issue-level).
- Resolve the 1 High vulnerability finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
D31 · IaC & Container Security
13 finding(s): 0 critical, 9 high, 2 medium, 2 low.
What to do
- Resolve the 9 High IaC finding(s) in IaC & Container Security — start with REDACTED (8), REDACTED. — One of this dimension's main actionable groups (9 issue-level).
- Resolve the 2 Medium IaC finding(s) in IaC & Container Security — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 2 Low IaC finding(s) in IaC & Container Security — start with REDACTED (2). — One of this dimension's main actionable groups (2 recommendation-level).
D35 · Change Coupling
Strongest change-coupling: sba-config.ts↔AdminServerUiProperties.java 77%
What to do
- Resolve the 1 Change coupling finding(s) in Change Coupling — start with sba-config.ts. — One of this dimension's main actionable groups (1 warning-level).
D36 · Supply-chain Provenance & Signing
2/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).
What to do
- Resolve the 3 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 2 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
D37 · Vulnerability-disclosure Policy
A vulnerability-disclosure policy (SECURITY.md) is published with a reporting contact.
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 2 platform declaration(s) and 1 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
Frontend & cross-cutting dimensions
AC1 · Text alternatives
- An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative. — spring-boot-admin-server-ui/src/main/frontend/login/login.vue:11
- A <canvas> with no aria-label/title and no inner fallback content can't be described by assistive tech. Add a name or fallback content. — spring-boot-admin-server-ui/src/main/frontend/views/instances/details/LineChart.vue:19
What to do
- Add a text alternative — alt on images (alt="" for purely decorative ones), a title or aria-label on meaningful svg, an aria-label or inner fallback content on canvas, and a captions <track> on video.
AC2 · Forms & labels
- This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it. (×2) — spring-boot-admin-server-ui/src/main/frontend/views/instances/gateway/global-filters.vue:24, spring-boot-admin-server-ui/src/main/frontend/views/instances/gateway/routes.vue:33
- A button with no text and no aria-label has no accessible name. Add visible text or an aria-label (an icon-only button still needs one). (×2) — spring-boot-admin-server-ui/src/main/frontend/views/instances/quartz/job-row.vue:10, spring-boot-admin-server-ui/src/main/frontend/views/instances/quartz/trigger-row.vue:9
- This <a> has no href, so it exposes no link role — but it carries a click handler, which makes it a control. It has no text, aria-label or labelled child (the icon-only case), so assistive tech has no name to announce for it. Note that switching it to <button type="button"> — the right fix for its keyboard operability — does not give it a name either: an icon-only button still needs one. Add visible text or an aria-label. — spring-boot-admin-server-ui/src/main/frontend/views/instances/startup/tree-item.vue:25
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) — spring-boot-admin-server-ui/src/main/frontend/index.html:18, spring-boot-admin-server-ui/src/main/frontend/login.html:18, spring-boot-admin-server/src/main/resources/META-INF/spring-boot-admin-server/mail/status-changed.html:18
- A <table> with data cells but no <th> gives assistive technology no way to associate cells with their headers. Mark the header row/column cells as <th> (with a scope). (×5) — spring-boot-admin-server-ui/src/main/frontend/views/instances/configprops/index.vue:42, spring-boot-admin-server-ui/src/main/frontend/views/instances/logfile/index.vue:141, spring-boot-admin-server-ui/src/main/frontend/views/instances/loggers/loggers-list.vue:18, …
- A page with no <title> gives no name in the tab, history or screen-reader page list. Add a descriptive <title> in <head>. — spring-boot-admin-server/src/main/resources/META-INF/spring-boot-admin-server/mail/status-changed.html:18
- No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>. — spring-boot-admin-server/src/main/resources/META-INF/spring-boot-admin-server/mail/status-changed.html:18
What to do
- Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh.
AC4 · Keyboard semantics
- A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler. (×4) — spring-boot-admin-server-ui/src/main/frontend/components/sba-dropdown/sba-dropdown-item.vue:33, spring-boot-admin-server-ui/src/main/frontend/views/instances/details/health-details.vue:25, spring-boot-admin-server-ui/src/main/frontend/views/instances/httptrace/traces-list.vue:61, …
- An <a> with no href, role or tabindex isn't focusable or keyboard-activatable. Give it a real href, or use a <button> for an action. (×7) — spring-boot-admin-server-ui/src/main/frontend/views/instances/details/instance-switcher.vue:48, spring-boot-admin-server-ui/src/main/frontend/views/instances/details/instance-switcher.vue:0, spring-boot-admin-server-ui/src/main/frontend/views/instances/jolokia/index.vue:77, …
What to do
- Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href.
AC5 · ARIA correctness
- A plain <div> has the implicit role "generic", which supports no ARIA states, so this aria-expanded is dropped and assistive tech is never told the state at all. Put aria-expanded on the element that owns the behaviour (the button or control the user operates), or give this <div> a role that supports aria-expanded. (×2) — spring-boot-admin-server-ui/src/main/frontend/components/sba-panel.vue:18, spring-boot-admin-server-ui/src/main/frontend/views/instances/details/health-details.vue:25
What to do
- Use valid, non-abstract roles, supply the ARIA state each role requires, and never put aria-hidden on a focusable element.
AC6 · Visual & motion safety
- <svg> moves — its `animate-spin` utility runs with no motion-safe:/motion-reduce: variant — and nothing reads prefers-reduced-motion for it, so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Gate it on @media (prefers-reduced-motion: no-preference) or motion-safe:. (×2) — spring-boot-admin-server-ui/src/main/frontend/components/sba-action-button-scoped.vue:0, spring-boot-admin-server-ui/src/main/frontend/components/sba-loading-spinner.vue:0
- `.route-definition-content` sets color: #fff on background-color: #00d1b2 — 2.0:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — spring-boot-admin-server-ui/src/main/frontend/views/instances/gateway/route-definition.vue:124
- `.route-content` sets color: #fff on background-color: #00d1b2 — 2.0:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — spring-boot-admin-server-ui/src/main/frontend/views/instances/gateway/route.vue:100
- `.btn` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — spring-boot-admin-server-ui/src/main/frontend/components/sba-button.vue:104
- `.btn.is-warning` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — spring-boot-admin-server-ui/src/main/frontend/components/sba-button.vue:117
- `.btn.is-info` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — spring-boot-admin-server-ui/src/main/frontend/components/sba-button.vue:121
- `.btn.is-success` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — spring-boot-admin-server-ui/src/main/frontend/components/sba-button.vue:125
- `.btn.is-light` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — spring-boot-admin-server-ui/src/main/frontend/components/sba-button.vue:129
- `.btn.is-extra-light` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — spring-boot-admin-server-ui/src/main/frontend/components/sba-button.vue:137
- `.btn.is-black` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — spring-boot-admin-server-ui/src/main/frontend/components/sba-button.vue:145
- `.sba-navbar-toggle` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — spring-boot-admin-server-ui/src/main/frontend/components/sba-navbar/sba-navbar-toggle.vue:71
- `.submenu-items` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. (×2) — spring-boot-admin-server-ui/src/main/frontend/components/sba-nav/sba-nav-dropdown.vue:99, spring-boot-admin-server-ui/src/main/frontend/components/sba-dropdown/sba-dropdown.vue:78
- `.tree-item` moves (`transition-property: transform`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — spring-boot-admin-server-ui/src/main/frontend/views/instances/startup/tree-table.vue:218
- `.copyButton` moves (`transition: background-color 0.2s ease-in-out, transform 0.1s ease-in-out`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — spring-boot-admin-docs/src/site/src/components/CopyButton.module.css:13
What to do
- Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1.
AX1 · Captive dependencies
AX10 · Code composition
AX2 · Stateful singletons
- `SnapshottingInstanceRepository` is a singleton (@Bean: the container shares one instance across every request thread) but mutates instance state outside any lock (subscription; e.g. `subscription` in `start` at line 84). — spring-boot-admin-server/src/main/java/de/codecentric/boot/admin/server/domain/entities/SnapshottingInstanceRepository.java:42
- `FilteringNotifier` is a singleton (@Bean: the container shares one instance across every request thread) but mutates instance state outside any lock (lastCleanup; e.g. `lastCleanup` in `cleanUp` at line 90). — spring-boot-admin-server/src/main/java/de/codecentric/boot/admin/server/notify/filter/FilteringNotifier.java:45
- `RemindingNotifier` is a singleton (@Bean: the container shares one instance across every request thread) but mutates instance state outside any lock (reminderScheduler, subscription; e.g. `reminderScheduler` in `start` at line 84). — spring-boot-admin-server/src/main/java/de/codecentric/boot/admin/server/notify/RemindingNotifier.java:48
- `InfoUpdateTrigger` is a singleton (@Bean: the container shares one instance across every request thread) but mutates instance state outside any lock (startupSubscription; e.g. `startupSubscription` in `start` at line 78). — spring-boot-admin-server/src/main/java/de/codecentric/boot/admin/server/services/InfoUpdateTrigger.java:37
- `StatusUpdateTrigger` is a singleton (@Bean: the container shares one instance across every request thread) but mutates instance state outside any lock (startupSubscription; e.g. `startupSubscription` in `start` at line 81). — spring-boot-admin-server/src/main/java/de/codecentric/boot/admin/server/services/StatusUpdateTrigger.java:36
- `StatusUpdater` is a singleton (@Bean: the container shares one instance across every request thread) but mutates instance state outside any lock (timeout; e.g. `timeout` in `timeout` at line 78). — spring-boot-admin-server/src/main/java/de/codecentric/boot/admin/server/services/StatusUpdater.java:55
What to do
- Java/Kotlin: keep container singletons stateless — move per-request data into locals or a request-scoped bean — or back the state with java.util.concurrent types (ConcurrentHashMap, AtomicInteger/AtomicReference), guard it with synchronized / a Lock (Kotlin: withLock), or mark a flag that is only ever overwritten volatile (@Volatile).
AX3 · Project dependency cycles
AX4 · Dependency direction
AX6 · Interface segregation
M1 · Documentation (README)
What to do
- Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
M3 · Folder & project structure
M4 · Documentation accuracy
P1 · CI/CD gates
P10 · Library API & versioning
P2 · Observability
- Only 7/14 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `spring-boot-admin-samples/spring-boot-admin-sample-consul`, `spring-boot-admin-samples/spring-boot-admin-sample-eureka`, `spring-boot-admin-samples/spring-boot-admin-sample-mcp`, `spring-boot-admin-samples/spring-boot-admin-sample-reactive`, `spring-boot-admin-samples/spring-boot-admin-sample-servlet-graalvm` 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
- `REDACTED` run(s) a static-analysis scan, but no workflow that runs one is triggered by a pull request (or a merge queue, or an unfiltered push) — the scan fires on a schedule or a manual dispatch only. A vulnerable change therefore merges clean and is reported on the next scheduled run, by which time it is on the default branch and the only remedy is a follow-up fix. Add the pull-request trigger to the workflow that runs the scan so the finding arrives before the merge rather than after it.
What to do
- Trigger your SAST workflow on pull requests — a scan that only runs on a cron reports history, it does not 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. — REDACTED:114
What to do
- Add a `healthcheck:` to the served compose service — probing the endpoint it already answers on where it has one — with `depends_on: condition: service_healthy` on whatever waits for it, and keep the deployed image tag immutable and recorded so rolling back is re-pointing at the previous tag rather than rebuilding.
P6 · Release Hygiene
P7 · Outbound HTTP resilience
- `new RestTemplate(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout. — spring-boot-admin-server/src/main/java/de/codecentric/boot/admin/server/config/AdminServerNotifierAutoConfiguration.java:88
- `WebClient.builder(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout. — spring-boot-admin-server/src/main/java/de/codecentric/boot/admin/server/web/client/InstanceWebClient.java:79
What to do
- Set connect and read timeouts on every client (`RestTemplateBuilder.connectTimeout/readTimeout`, WebClient `responseTimeout`, `HttpRequest.Builder.timeout`, `HttpURLConnection.setReadTimeout`, Feign `connectTimeout`/`readTimeout` in configuration), and wrap calls to dependencies in resilience4j `@Retry`/`@CircuitBreaker`/`@TimeLimiter` (or Spring Retry).
PF3 · Async & latency hygiene
R1 · Type Safety
R10 · Code Duplication
- 23 duplicated blocks under spring-boot-admin-server-ui/src/main/frontend/views/instances/ have copies in at least two of the sibling directories auditevents, beans, caches, conditions, configprops, dependencies (+14 more sibling(s) not listed) — 13 of them are reported below, and 10 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 23 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 23 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 23 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. — spring-boot-admin-server-ui/src/main/frontend/views/instances/httpexchanges/Exchange.ts:20
- spring-boot-admin-server-ui/src/main/frontend/views/instances/details/cache-chart.vue:41 · spring-boot-admin-server-ui/src/main/frontend/views/instances/details/datasource-chart.vue:40 — 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. — spring-boot-admin-server-ui/src/main/frontend/views/instances/details/cache-chart.vue:41
- spring-boot-admin-server-ui/src/main/frontend/views/instances/httpexchanges/Exchange.ts:20 · spring-boot-admin-server-ui/src/main/frontend/views/instances/httptrace/index.vue:112 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — spring-boot-admin-server-ui/src/main/frontend/views/instances/httpexchanges/Exchange.ts:20
- spring-boot-admin-server-ui/src/main/frontend/views/instances/beans/index.vue:68 · spring-boot-admin-server-ui/src/main/frontend/views/instances/conditions/index.vue:115 — the two spans are one implementation copied and then locally edited — 329 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. — spring-boot-admin-server-ui/src/main/frontend/views/instances/beans/index.vue:68
- spring-boot-admin-server-ui/src/main/frontend/components/sba-input.vue:119 · spring-boot-admin-server-ui/src/main/frontend/components/sba-select.vue:93 — the two spans are one implementation copied and then locally edited — 193 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. — spring-boot-admin-server-ui/src/main/frontend/components/sba-input.vue:119
- spring-boot-admin-server-ui/src/main/frontend/services/application.ts:247 · spring-boot-admin-server-ui/src/main/frontend/services/instance.ts:467 — 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. — spring-boot-admin-server-ui/src/main/frontend/services/application.ts:247
- spring-boot-admin-server-ui/src/main/frontend/views/instances/gateway/global-filters.vue:78 · spring-boot-admin-server-ui/src/main/frontend/views/instances/gateway/routes.vue:89 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. — spring-boot-admin-server-ui/src/main/frontend/views/instances/gateway/global-filters.vue:78
- spring-boot-admin-server-ui/src/main/frontend/services/quartz-actuator.ts:232 · spring-boot-admin-server-ui/src/main/frontend/views/instances/quartz/trigger-row.vue:267 — the two spans are one implementation copied and then locally edited — 169 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. — spring-boot-admin-server-ui/src/main/frontend/services/quartz-actuator.ts:232
- spring-boot-admin-server-ui/src/main/frontend/views/instances/flyway/index.vue:76 · spring-boot-admin-server-ui/src/main/frontend/views/instances/liquibase/index.vue:124 — 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. — spring-boot-admin-server-ui/src/main/frontend/views/instances/flyway/index.vue:76
- spring-boot-admin-server-ui/src/main/frontend/services/quartz-actuator.ts:42 · spring-boot-admin-server-ui/src/main/frontend/services/quartz-actuator.ts:105 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — spring-boot-admin-server-ui/src/main/frontend/services/quartz-actuator.ts:42
- spring-boot-admin-server-ui/src/main/frontend/views/instances/beans/beans-list.vue:67 · spring-boot-admin-server-ui/src/main/frontend/views/instances/conditions/conditions-list.vue:83 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — spring-boot-admin-server-ui/src/main/frontend/views/instances/beans/beans-list.vue:67
- spring-boot-admin-server-ui/src/main/frontend/views/applications/ActionHandler.ts:20 · spring-boot-admin-server-ui/src/main/frontend/views/applications/ActionHandler.ts:48 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — spring-boot-admin-server-ui/src/main/frontend/views/applications/ActionHandler.ts:20
- spring-boot-admin-server-ui/src/main/frontend/views/instances/httpexchanges/exchanges-chart.vue:102 · spring-boot-admin-server-ui/src/main/frontend/views/instances/httptrace/traces-chart.vue:90 — 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. — spring-boot-admin-server-ui/src/main/frontend/views/instances/httpexchanges/exchanges-chart.vue:102
- spring-boot-admin-server-ui/src/main/frontend/views/instances/httpexchanges/index.vue:203 · spring-boot-admin-server-ui/src/main/frontend/views/instances/httptrace/index.vue:273 — 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. — spring-boot-admin-server-ui/src/main/frontend/views/instances/httpexchanges/index.vue:203
- spring-boot-admin-server-ui/src/main/frontend/views/instances/details/details-datasource.vue:142 · spring-boot-admin-server-ui/src/main/frontend/views/instances/details/details-threads.vue:146 — 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. — spring-boot-admin-server-ui/src/main/frontend/views/instances/details/details-datasource.vue:142
- spring-boot-admin-server-ui/src/main/frontend/views/instances/details/details-cache.vue:260 · spring-boot-admin-server-ui/src/main/frontend/views/instances/details/details-datasource.vue:153 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. — spring-boot-admin-server-ui/src/main/frontend/views/instances/details/details-cache.vue:260
- spring-boot-admin-server-ui/src/main/frontend/views/instances/details/details-datasource.vue:108 · spring-boot-admin-server-ui/src/main/frontend/views/instances/details/details-threads.vue:119 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. — spring-boot-admin-server-ui/src/main/frontend/views/instances/details/details-datasource.vue:108
- spring-boot-admin-server-ui/src/main/frontend/views/applications/ActionHandler.ts:141 · spring-boot-admin-server-ui/src/main/frontend/views/applications/ActionHandler.ts:173 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — spring-boot-admin-server-ui/src/main/frontend/views/applications/ActionHandler.ts:141
- spring-boot-admin-server-ui/src/main/frontend/views/instances/details/details-memory.vue:200 · spring-boot-admin-server-ui/src/main/frontend/views/instances/details/details-threads.vue:154 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. — spring-boot-admin-server-ui/src/main/frontend/views/instances/details/details-memory.vue:200
- spring-boot-admin-server-ui/src/main/frontend/views/instances/details/details-cache.vue:135 · spring-boot-admin-server-ui/src/main/frontend/views/instances/details/details-memory.vue:139 — 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. — spring-boot-admin-server-ui/src/main/frontend/views/instances/details/details-cache.vue:135
- spring-boot-admin-server-ui/src/main/frontend/views/instances/auditevents/auditevents-list.vue:108 · spring-boot-admin-server-ui/src/main/frontend/views/instances/sessions/sessions-list.vue:139 — the two spans are one implementation copied and then locally edited — 74 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. — spring-boot-admin-server-ui/src/main/frontend/views/instances/auditevents/auditevents-list.vue:108
- spring-boot-admin-server-ui/src/main/frontend/views/instances/httpexchanges/index.vue:168 · spring-boot-admin-server-ui/src/main/frontend/views/instances/httptrace/index.vue:249 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — spring-boot-admin-server-ui/src/main/frontend/views/instances/httpexchanges/index.vue:168
- spring-boot-admin-server-ui/src/main/frontend/views/instances/configprops/index.vue:161 · spring-boot-admin-server-ui/src/main/frontend/views/instances/env/index.vue:170 — 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. — spring-boot-admin-server-ui/src/main/frontend/views/instances/configprops/index.vue:161
- spring-boot-admin-server-ui/src/main/frontend/views/instances/details/details-cache.vue:184 · spring-boot-admin-server-ui/src/main/frontend/views/instances/details/details-cache.vue:202 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — spring-boot-admin-server-ui/src/main/frontend/views/instances/details/details-cache.vue:184
- spring-boot-admin-server-ui/src/main/frontend/views/instances/quartz/trigger-types/calendar-interval-details.vue:69 · spring-boot-admin-server-ui/src/main/frontend/views/instances/quartz/trigger-types/simple-details.vue:34 — 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. — spring-boot-admin-server-ui/src/main/frontend/views/instances/quartz/trigger-types/calendar-interval-details.vue:69
- spring-boot-admin-server-ui/src/main/frontend/views/instances/details/details-caches.vue:59 · spring-boot-admin-server-ui/src/main/frontend/views/instances/details/details-datasources.vue:57 — the two spans are one implementation copied and then locally edited — 158 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. — spring-boot-admin-server-ui/src/main/frontend/views/instances/details/details-caches.vue:59
- spring-boot-admin-server-ui/src/main/frontend/components/sba-input.vue:178 · spring-boot-admin-server-ui/src/main/frontend/components/sba-select.vue:148 — 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. — spring-boot-admin-server-ui/src/main/frontend/components/sba-input.vue:178
- spring-boot-admin-server-ui/src/main/frontend/views/applications/ActionHandler.ts:123 · spring-boot-admin-server-ui/src/main/frontend/views/applications/ActionHandler.ts:153 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — spring-boot-admin-server-ui/src/main/frontend/views/applications/ActionHandler.ts:123
- spring-boot-admin-server-ui/src/main/frontend/services/application.ts:225 · spring-boot-admin-server-ui/src/main/frontend/services/instance.ts:308 — 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. — spring-boot-admin-server-ui/src/main/frontend/services/application.ts:225
- spring-boot-admin-server-ui/src/main/frontend/views/instances/configprops/index.vue:70 · spring-boot-admin-server-ui/src/main/frontend/views/instances/env/index.vue:127 — 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. — spring-boot-admin-server-ui/src/main/frontend/views/instances/configprops/index.vue:70
- spring-boot-admin-server-ui/src/main/frontend/views/instances/details/details-caches.vue:57 · spring-boot-admin-server-ui/src/main/frontend/views/instances/details/details-datasources.vue:55 · spring-boot-admin-server-ui/src/main/frontend/views/instances/details/details-gc.vue:120 — the 3 copies are spread across 3 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — spring-boot-admin-server-ui/src/main/frontend/views/instances/details/details-caches.vue:57
- spring-boot-admin-server-ui/src/main/frontend/views/instances/httpexchanges/index.vue:256 · spring-boot-admin-server-ui/src/main/frontend/views/instances/httptrace/index.vue:313 — 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. — spring-boot-admin-server-ui/src/main/frontend/views/instances/httpexchanges/index.vue:256
- spring-boot-admin-server-ui/src/main/frontend/utils/logtail.ts:247 · spring-boot-admin-server-ui/src/main/frontend/utils/logtail.ts:259 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — spring-boot-admin-server-ui/src/main/frontend/utils/logtail.ts:247
- spring-boot-admin-server-ui/src/main/frontend/views/instances/configprops/index.vue:174 · spring-boot-admin-server-ui/src/main/frontend/views/instances/sbomdependencytrees/index.vue:96 · spring-boot-admin-server-ui/src/main/frontend/views/instances/scheduledtasks/index.vue:237 — the 3 copies are spread across 3 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — spring-boot-admin-server-ui/src/main/frontend/views/instances/configprops/index.vue:174
- spring-boot-admin-server-ui/src/main/frontend/views/instances/mappings/index.vue:111 · spring-boot-admin-server-ui/src/main/frontend/views/instances/metrics/index.vue:215 — the two spans are one implementation copied and then locally edited — 59 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. — spring-boot-admin-server-ui/src/main/frontend/views/instances/mappings/index.vue:111
- spring-boot-admin-server-ui/src/main/frontend/views/instances/quartz/job-row.vue:350 · spring-boot-admin-server-ui/src/main/frontend/views/instances/quartz/trigger-row.vue:336 — 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. — spring-boot-admin-server-ui/src/main/frontend/views/instances/quartz/job-row.vue:350
- spring-boot-admin-server-ui/src/main/frontend/services/application.ts:142 · spring-boot-admin-server-ui/src/main/frontend/services/instance.ts:97 — 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. — spring-boot-admin-server-ui/src/main/frontend/services/application.ts:142
- spring-boot-admin-server-ui/src/main/frontend/services/application.ts:182 · spring-boot-admin-server-ui/src/main/frontend/services/instance.ts:164 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — spring-boot-admin-server-ui/src/main/frontend/services/application.ts:182
- spring-boot-admin-server-ui/src/main/frontend/views/instances/quartz/trigger-types/daily-time-interval-details.vue:87 · spring-boot-admin-server-ui/src/main/frontend/views/instances/quartz/trigger-types/simple-details.vue:50 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. — spring-boot-admin-server-ui/src/main/frontend/views/instances/quartz/trigger-types/daily-time-interval-details.vue:87
- spring-boot-admin-server-ui/src/main/frontend/views/journal/utils.ts:27 · spring-boot-admin-server-ui/src/main/frontend/views/journal/utils.ts:41 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — spring-boot-admin-server-ui/src/main/frontend/views/journal/utils.ts:27
What to do
- Act on each finding's own remediation rather than one rule: the move depends on what recurs. Where the copies are executable blocks, give the shared part one home and call it from each site; where they are declarations, a listing, a specialisation already delegating to its base, or one shape repeated per entity, there is no call site and the move is a shared type, a generated set or a factory — sometimes there is nothing to extract.
R2 · Cyclomatic Complexity
- transformToJSON has cyclomatic complexity 17 and cognitive complexity 58; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — spring-boot-admin-server-ui/src/main/frontend/utils/transformToJSON.ts:71
- categoryOf has cyclomatic complexity 16 and cognitive complexity 15; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — spring-boot-admin-server-ui/src/main/frontend/views/mcp/mcp.service.ts:31
- formatWithDataTypes has cyclomatic complexity 13 and cognitive complexity 20; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — spring-boot-admin-server-ui/src/main/frontend/utils/formatWithDataTypes.ts:53
- shortFormat has cyclomatic complexity 12 and cognitive complexity 15; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — spring-boot-admin-server-ui/src/main/frontend/components/sba-time-ago.vue:21
- abbreviateLoggerName has cyclomatic complexity 12 and cognitive complexity 14; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — spring-boot-admin-server-ui/src/main/frontend/composables/useClassnameShortener.ts:26
R3 · Large Files
- spring-boot-admin-server-ui/src/main/frontend/mocks/instance/jolokia/data.ts has 2481 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — spring-boot-admin-server-ui/src/main/frontend/mocks/instance/jolokia/data.ts:1
- spring-boot-admin-server-ui/src/main/frontend/views/instances/logfile/index.vue has 889 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — spring-boot-admin-server-ui/src/main/frontend/views/instances/logfile/index.vue:1
- spring-boot-admin-server-ui/src/main/frontend/services/instance.ts has 505 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — spring-boot-admin-server-ui/src/main/frontend/services/instance.ts:1
- spring-boot-admin-server-ui/src/main/frontend/views/applications/index.vue has 470 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — spring-boot-admin-server-ui/src/main/frontend/views/applications/index.vue:1
What to do
- Split each oversized file along the responsibilities already in it, into smaller focused modules in the same package.
R4 · Test Coverage
- No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one. (×40) — spring-boot-admin-server-ui/src/main/frontend/views/instances/env/env-manager.vue:1, spring-boot-admin-server-ui/src/main/frontend/views/instances/loggers/loggers.vue:1, spring-boot-admin-server-ui/src/main/frontend/views/instances/metrics/index.vue:1, …
What to do
- Add tests that import the unreached modules (directly or through their public entry).
R5 · Dependency Freshness
R6 · Tooling
- The package in `spring-boot-admin-server-ui` declares the lint script `lint` (`eslint --ext .js,.ts,.vue src/main/frontend`), but no step of this repository's CI runs it, by name, through another script, a Makefile target or a workspace runner, and no CI step runs the linter over the package itself. The rules it sets are enforced nowhere a pull request can fail. Run it in CI: a step that runs `npm run lint` in `spring-boot-admin-server-ui` (or the workspace's task runner). — spring-boot-admin-server-ui/package.json:14
R7 · Dead Code
- Unreachable from the 28 application, 12 tooling and 158 test entry point(s) detected in this repo. Gate removals on `npm run typecheck` — an undetected custom entry would make these reachable.
- no import path from any entry point (28 application, 12 tooling, 158 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make — spring-boot-admin-server-ui/src/main/frontend/utils/toast.ts
- Nothing imports this binding — it is safe to review for removal. (×2) — spring-boot-admin-server-ui/src/main/frontend/plugins/modal/helpers.ts:3, spring-boot-admin-server-ui/src/main/frontend/utils/http-status.ts:101
What to do
- Delete the dead files and unused exports — every line is maintenance cost and rebuild-estimate inflation with zero runtime value.
R8 · Dependency Hygiene
R9 · Circular Imports
X1 · Async correctness
X12 · Unreachable branch
X16 · Unfloored truncation loop
X17 · Uncapped recursion over a caller-supplied document
- `createDependencyTree` is exported, takes a document from its caller (line 268) and hands it to `updateDependencyTree`, which calls itself at line 185 (`updateDependencyTree`) with a piece of `source` — and nowhere in `updateDependencyTree` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `updateDependencyTree` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — spring-boot-admin-server-ui/src/main/frontend/views/instances/sbomdependencytrees/dependencyTree.ts:185
- `filterTree` is exported and takes `treeData: DependencyTreeData | null` from its caller, and it calls itself at line 84 (`filterTree`) with a piece of `treeData` — and nowhere in `filterTree` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `filterTree` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — spring-boot-admin-server-ui/src/main/frontend/views/instances/sbomdependencytrees/sbomUtils.ts:84
- `sortObject` is exported and takes `input: any` from its caller, and it calls itself at line 3 (`sortObject`) with a piece of `input` (and at line 9) — and nowhere in `sortObject` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `sortObject` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — spring-boot-admin-server-ui/src/main/frontend/utils/sortObject.ts:3
What to do
- Each finding names the externally-callable member that accepts the document and the self-call that descends, and states that no depth parameter or counter exists anywhere in the walk. Confirm from the two, then thread a depth argument through the walk and reject documents past a fixed maximum, or rewrite it with an explicit stack.
X2 · Cancellation propagation
- Only 0/9 async functions that make a cancellable request (fetch, axios, ky, ofetch, got, undici, node:http) accept an AbortSignal or pass one on, so a request keeps running after whatever wanted it has given up — a page navigated away from, an unmounted component, a timed-out job. Take a `signal` (or an options object that carries one) and hand it to the request; where nothing could ever cancel the call, omitting it is a deliberate choice — judge against how the function is used.
- `fetchTools` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. — spring-boot-admin-server-ui/src/main/frontend/views/mcp/mcp.service.ts:57
- `initializeSession` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. — spring-boot-admin-server-ui/src/main/frontend/views/mcp/mcp.service.ts:80
- `refreshApplications` awaits `axios.post(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `axios.post(url, { signal })`. — spring-boot-admin-server-ui/src/main/frontend/services/application.ts:131
- `list` awaits `axios.get(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `axios.get(url, { signal })`. — spring-boot-admin-server-ui/src/main/frontend/services/application.ts:135
- `fetchEvents` awaits `axios.get(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `axios.get(url, { signal })`. — spring-boot-admin-server-ui/src/main/frontend/services/instance.ts:91
- `get` awaits `axios.get(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `axios.get(url, { signal })`. — spring-boot-admin-server-ui/src/main/frontend/services/instance.ts:115
- `delete` awaits `axios.delete(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `axios.delete(url, { signal })`. — spring-boot-admin-server-ui/src/main/frontend/services/notification-filter.ts:57
- `getFilters` awaits `axios.get(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `axios.get(url, { signal })`. — spring-boot-admin-server-ui/src/main/frontend/services/notification-filter.ts:65
- `addFilter` awaits `axios.post(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `axios.post(url, { signal })`. — spring-boot-admin-server-ui/src/main/frontend/services/notification-filter.ts:71
What to do
- Thread an AbortSignal through async functions that make requests, so the work stops when its caller gives up.
X21 · Side-effecting pattern guard
X23 · Unguarded diagnostic materialisation
X24 · Document value interpolated into markup unescaped
- `message` is text this program did not author, and it is written into the text of an element through Vue's `v-html` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — spring-boot-admin-server-ui/src/main/frontend/components/sba-alert.vue:30
- `formatted` is text this program did not author, and it is written into the text of an element through Vue's `v-html` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — spring-boot-admin-server-ui/src/main/frontend/components/sba-formatted-obj.vue:18
- `brand` is text this program did not author, and it is written into the text of an element through Vue's `v-html` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — spring-boot-admin-server-ui/src/main/frontend/components/sba-navbar/sba-navbar-brand.vue:2
- `$t('instances.auditevents.timestamp')` is text this program did not author, and it is written into the text of an element through Vue's `v-html` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — spring-boot-admin-server-ui/src/main/frontend/views/instances/auditevents/auditevents-list.vue:21
- `$t('instances.auditevents.event')` is text this program did not author, and it is written into the text of an element through Vue's `v-html` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — spring-boot-admin-server-ui/src/main/frontend/views/instances/auditevents/auditevents-list.vue:22
- `$t('instances.auditevents.principal')` is text this program did not author, and it is written into the text of an element through Vue's `v-html` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — spring-boot-admin-server-ui/src/main/frontend/views/instances/auditevents/auditevents-list.vue:23
- `$t('instances.auditevents.remote_address')` is text this program did not author, and it is written into the text of an element through Vue's `v-html` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — spring-boot-admin-server-ui/src/main/frontend/views/instances/auditevents/auditevents-list.vue:24
- `$t('instances.auditevents.session_id')` is text this program did not author, and it is written into the text of an element through Vue's `v-html` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — spring-boot-admin-server-ui/src/main/frontend/views/instances/auditevents/auditevents-list.vue:25
- `$t('instances.auditevents.loading_audit_events')` is text this program did not author, and it is written into the text of an element through Vue's `v-html` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — spring-boot-admin-server-ui/src/main/frontend/views/instances/auditevents/auditevents-list.vue:88
- `$t('instances.auditevents.no_audit_events_found')` is text this program did not author, and it is written into the text of an element through Vue's `v-html` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — spring-boot-admin-server-ui/src/main/frontend/views/instances/auditevents/auditevents-list.vue:92
- `$t('instances.caches.name')` is text this program did not author, and it is written into the text of an element through Vue's `v-html` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — spring-boot-admin-server-ui/src/main/frontend/views/instances/caches/caches-list.vue:21
- `$t('instances.caches.cache_manager')` is text this program did not author, and it is written into the text of an element through Vue's `v-html` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — spring-boot-admin-server-ui/src/main/frontend/views/instances/caches/caches-list.vue:22
- `autolink(sanitizeHtml(String(detail.value ?? '')))` is text this program did not author, and it is written into the text of an element through Vue's `v-html` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — spring-boot-admin-server-ui/src/main/frontend/views/instances/details/health-details.vue:138
- `$t('instances.env.refreshed_configurations')` is text this program did not author, and it is written into the text of an element through Vue's `v-html` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — spring-boot-admin-server-ui/src/main/frontend/views/instances/env/index.vue:75
- `renderLine(line.text)` is text this program did not author, and it is written into the text of an element through Vue's `v-html` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — spring-boot-admin-server-ui/src/main/frontend/views/instances/logfile/index.vue:154
- `$t('instances.sessions.session_id')` is text this program did not author, and it is written into the text of an element through Vue's `v-html` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — spring-boot-admin-server-ui/src/main/frontend/views/instances/sessions/sessions-list.vue:21
- `$t('instances.sessions.created_at')` is text this program did not author, and it is written into the text of an element through Vue's `v-html` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — spring-boot-admin-server-ui/src/main/frontend/views/instances/sessions/sessions-list.vue:22
- `$t('instances.sessions.last_accessed_at')` is text this program did not author, and it is written into the text of an element through Vue's `v-html` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — spring-boot-admin-server-ui/src/main/frontend/views/instances/sessions/sessions-list.vue:23
- `$t('instances.sessions.expiry')` is text this program did not author, and it is written into the text of an element through Vue's `v-html` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — spring-boot-admin-server-ui/src/main/frontend/views/instances/sessions/sessions-list.vue:24
- `$t('instances.sessions.max_inactive_interval')` is text this program did not author, and it is written into the text of an element through Vue's `v-html` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — spring-boot-admin-server-ui/src/main/frontend/views/instances/sessions/sessions-list.vue:25
- `$t('instances.sessions.attributes')` is text this program did not author, and it is written into the text of an element through Vue's `v-html` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — spring-boot-admin-server-ui/src/main/frontend/views/instances/sessions/sessions-list.vue:26
- `group.icon` is text this program did not author, and it is written into the text of an element through Vue's `v-html` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — spring-boot-admin-server-ui/src/main/frontend/views/instances/shell/sidebar.vue:62
- `html` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — spring-boot-admin-server-ui/src/main/frontend/views/instances/shell/sidebar.vue:299
What to do
- Each finding names the expression, the attribute it lands in and the line. Confirm the value's origin from the read this analyzer traced, then escape it at the sink or validate it against the shape the attribute accepts before interpolating.
X25 · Inert configuration knob
X29 · Per-element action decided by a fixed element
X3 · Exception handling
- An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it. (×3) — spring-boot-admin-server-ui/src/main/frontend/views/instances/details/health-details.vue:184, spring-boot-admin-server-ui/src/main/frontend/views/instances/details/health-details.vue:233, spring-boot-admin-server-ui/src/main/frontend/utils/formatWithDataTypes.ts:86
What to do
- Swallowed exception (empty catch)
X4 · Structured logging
- `warn` at line 121 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.warn("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — spring-boot-admin-server/src/main/java/de/codecentric/boot/admin/server/domain/values/Registration.java:121
What to do
- Interpolated log message defeats structured logging
X5 · Nullable reference types
- 2/4 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 |
|---|---|---|
| AC1 · Text alternatives | 1.1.1, 1.2.2, 1.2.5 | Partial signal |
| AC2 · Forms & labels | 1.3.1, 3.3.2, 4.1.2 | Partial signal |
| AC3 · Page structure | 1.4.4, 2.2.1, 2.4.1, 2.4.2, 3.1.1, 4.1.2 | Partial signal |
| AC4 · Keyboard semantics | 2.1.1, 2.4.3 | Partial signal |
| AC5 · ARIA correctness | 4.1.2 | Partial signal |
| AC6 · Visual & motion safety | 1.4.3, 2.4.7 | Partial — literal CSS only |
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 64.7 | Adequate | Acceptable, with room to improve. |
| Architecture | 76.2 | Strong | Solid. |
| Maturity | 77.5 | Strong | Solid. |
| Readiness | 65.5 | Adequate — gated by P7 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 71.8 | Adequate — gated by D29 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Accessibility | 36.3 | Weak — gated by AC1, AC4 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Performance | 100.0 | Exemplary | Strongest area. |
Unscored — 2 check(s) recorded observations but carry no score
- P12 CI test-gate honesty — 2 observation(s) recorded · Reported, not scored — this card publishes what the CI gate does with the test inventory rather than grading it. The findings above are its output.
- X10 Duplicated predicate — 3 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
- AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AX8 Test isolation — no test/production split to check
- AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXR1 Runtime accessibility — compose up failed (exit 18 — an image could not be pulled) — [DEPRECATION NOTICE] Docker Image Format v1 and Docker Image manifest version 2, schema 1 support is disabled by default and will be removed in an upcoming release. Suggest the author of docker.io/tutum/mongodb:latest to upgrade the image to the OCI Format or Docker Image manifest v2, schema 2. More information at https://docs.docker.com/go/deprecated-image-specs/; the earlier `compose pull` step reported: [DEPRECATION NOTICE] Docker Image Format v1 and Docker Image manifest version 2, schema 1 support is disabled by default and will be removed in an upcoming release. Suggest the author of docker.io/springcloud/stores:latest to upgrade the image to the OCI Format or Docker Image manifest v2, schema 2. More information at https://docs.docker.com/go/deprecated-image-specs/; the runtime sandbox reaches registries only through the in-fence pull-through mirror, so an image the mirror does not carry cannot be fetched — this is a limit of our sandbox, not of your stack; runtime evidence skipped This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
- C1 Data Protection — Not assessed: these personal data controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks personal data controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- C2 Access Controls — Not assessed: these authorization controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks authorization controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- D11 Test Reliability — Test reliability not measured — JavaScript/TypeScript suite did not run
- D12 Dependency Hygiene — Dependency currency not established — repo.spring.io did not answer
- 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 does not read html yet; not measured.
- D22 Internal API Consistency — The exposed public-API surface could not be collected — no C#/VB projects loaded.
- D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D25 ADR Conformance — no ADRs to check
- D32 Data Compliance (PII/GDPR) — 1 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
- D34 Knowledge Freshness — knowledge concentrated in recent work — freshness signal contradicted by repo activity
- 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: the JavaScript/TypeScript half could not be measured — spring-boot-admin-server-ui/ runs vitest but declares no coverage provider, so the suite can run and still produce no lcov — add `@vitest/coverage-v8` (or `@vitest/coverage-istanbul`) as a devDependency. Coverage is excluded from the score rather than counted as a near-zero. The named suite step is one the repository's maintainers can perform; once it passes, the real number is measured on the next scan.
- DM1 Domain Modelling — applicable but not scored (4 signals for this style, 3 needed — the count is met but a required primary signal is absent): 3 aggregate root(s) (entities that raise its domain events); 22 value object(s); 6 domain event(s); a Domain/Aggregates/ValueObjects layer; a top-level spring-boot-admin-samples/ tree: a library or framework whose examples are its consumers — these types are building blocks, not a domain
- 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.
- ES1 Event Sourcing — not scored — this repository shows only 1 of the 3 signals this lens looks for (an Axon event-sourcing framework (@Aggregate/@CommandHandler/@EventSourcingHandler annotations))
- GD1 Unfinished & placeholder code — no source files were read — this check reads C#, F#, JavaScript/TypeScript, Dart, Ruby, Scala, Rust and Java, and none was read for this repository's product. That is a limit of the analyzer, not a finding about your code.
- IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
- P9 Domain vs controller coverage — coverage not measured: this check compares the coverage of the analyzer's own test run across the domain and web layers, and that run measured none here — Test coverage (D8) says why
- PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for `@Benchmark` in a Java, Kotlin or Scala file importing JMH or kotlinx-benchmark, Jetpack Benchmark's `measureRepeated` in a file importing androidx.benchmark, or JMH/kotlinx-benchmark/androidx.benchmark in a REDACTED, Gradle or sbt build, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
- PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
- R11 Import Boundaries — No recognizable feature-sliced/layered src layout — boundary rules not applicable.
- 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.
- SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X13 Undrained process stream — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X14 Bypassable address classification — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X18 Disposal-pattern correctness — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X19 Unrestored process-global state — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X20 Mistyped argument guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X22 Contradicted release guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X26 Unsynchronised callback handoff — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X27 Collection changed while being enumerated — X27 reached only 32% of this repository's production lines — typescript (24,867 lines), javascript (15,099 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- X28 Index access outside its own emptiness guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X30 Support guard that admits what it rejects — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- 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 — 100 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
- No assertions (empty test): contextLoads spring-boot-admin-samples/spring-boot-admin-sample-consul/src/test/java/de/codecentric/boot/admin/sample/SpringBootAdminConsulApplicationTest.java:30
- No assertions (empty test): contextLoads spring-boot-admin-samples/spring-boot-admin-sample-hazelcast/src/test/java/de/codecentric/boot/admin/sample/SpringBootAdminHazelcastApplicationTest.java:29
- No assertions (empty test): contextLoads spring-boot-admin-samples/spring-boot-admin-sample-reactive/src/test/java/de/codecentric/boot/admin/sample/SpringBootAdminReactiveApplicationTest.java:29
- No assertions (empty test): contextLoads spring-boot-admin-samples/spring-boot-admin-sample-servlet/src/test/java/de/codecentric/boot/admin/sample/SpringBootAdminServletApplicationTest.java:29
- No assertions (empty test): contextLoads spring-boot-admin-samples/spring-boot-admin-sample-zookeeper/src/test/java/de/codecentric/boot/admin/sample/SpringBootAdminZookeeperApplicationTest.java:30
- No assertions (empty test): contextLoads spring-boot-admin-samples/spring-boot-admin-sample-eureka/src/test/java/de/codecentric/boot/admin/SpringBootAdminEurekaApplicationTest.java:29
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- <html> without a lang spring-boot-admin-server-ui/src/main/frontend/index.html:18
- <html> without a lang spring-boot-admin-server-ui/src/main/frontend/login.html:18
- <html> without a lang spring-boot-admin-server/src/main/resources/META-INF/spring-boot-admin-server/mail/status-changed.html:18
- <input> without a programmatic label spring-boot-admin-server-ui/src/main/frontend/views/instances/gateway/global-filters.vue:24
- <input> without a programmatic label spring-boot-admin-server-ui/src/main/frontend/views/instances/gateway/routes.vue:33
- <button> with no accessible text spring-boot-admin-server-ui/src/main/frontend/views/instances/quartz/job-row.vue:10
- <button> with no accessible text spring-boot-admin-server-ui/src/main/frontend/views/instances/quartz/trigger-row.vue:9
- Click handler on a non-interactive <div> spring-boot-admin-server-ui/src/main/frontend/components/sba-dropdown/sba-dropdown-item.vue:33
- Click handler on a non-interactive <div> spring-boot-admin-server-ui/src/main/frontend/views/instances/details/health-details.vue:25
- aria-expanded on a <div> with no role to carry it spring-boot-admin-server-ui/src/main/frontend/components/sba-panel.vue:18
- aria-expanded on a <div> with no role to carry it spring-boot-admin-server-ui/src/main/frontend/views/instances/details/health-details.vue:25
- <img> without a text alternative spring-boot-admin-server-ui/src/main/frontend/login/login.vue:11
- Clickable <a> with no accessible name spring-boot-admin-server-ui/src/main/frontend/views/instances/startup/tree-item.vue:25
- Document without a <title> spring-boot-admin-server/src/main/resources/META-INF/spring-boot-admin-server/mail/status-changed.html:18
- Click handler on a non-interactive <td> spring-boot-admin-server-ui/src/main/frontend/views/instances/httptrace/traces-list.vue:61
- Click handler on a non-interactive <header> spring-boot-admin-server-ui/src/main/frontend/views/instances/jolokia/index.vue:49
- REDACTED
- REDACTED
- REDACTED
- REDACTED
Serious — 353 finding(s)
- No assertions: should_not_register_instance_when_instanceMetadata_is_ignored spring-boot-admin-server-cloud/src/test/java/de/codecentric/boot/admin/server/cloud/discovery/InstanceDiscoveryListenerTest.java:107
- No assertions: should_not_register_instance_when_serviceId_is_ignored spring-boot-admin-server-cloud/src/test/java/de/codecentric/boot/admin/server/cloud/discovery/InstanceDiscoveryListenerTest.java:83
- No assertions: should_not_register_instance_when_serviceId_is_ignored_caseInsensitive spring-boot-admin-server-cloud/src/test/java/de/codecentric/boot/admin/server/cloud/discovery/InstanceDiscoveryListenerTest.java:95
- No assertions: should_register_instance_when_instanceMetadata_is_not_ignored spring-boot-admin-server-cloud/src/test/java/de/codecentric/boot/admin/server/cloud/discovery/InstanceDiscoveryListenerTest.java:131
- No assertions: should_register_instance_when_serviceId_is_not_ignored spring-boot-admin-server-cloud/src/test/java/de/codecentric/boot/admin/server/cloud/discovery/InstanceDiscoveryListenerTest.java:119
- No assertions: should_render_login_view_with_anonymous_user_model spring-boot-admin-server-ui/src/test/java/de/codecentric/boot/admin/server/ui/web/UiControllerTest.java:161
- No assertions: should_render_variables_css_with_public_url_and_ui_extensions spring-boot-admin-server-ui/src/test/java/de/codecentric/boot/admin/server/ui/web/UiControllerTest.java:178
- No assertions: should_use_default_url spring-boot-admin-server-ui/src/test/java/de/codecentric/boot/admin/server/ui/web/UiControllerTest.java:49
- No assertions: should_use_host_and_path_from_public_url spring-boot-admin-server-ui/src/test/java/de/codecentric/boot/admin/server/ui/web/UiControllerTest.java:69
- No assertions: should_use_path_from_public_url spring-boot-admin-server-ui/src/test/java/de/codecentric/boot/admin/server/ui/web/UiControllerTest.java:59
- No assertions: should_use_scheme_host_and_path_from_public_url spring-boot-admin-server-ui/src/test/java/de/codecentric/boot/admin/server/ui/web/UiControllerTest.java:79
- No assertions: should_not_return_index_for_logfile spring-boot-admin-server-ui/src/test/java/de/codecentric/boot/admin/server/ui/AbstractAdminUiApplicationTest.java:49
- No assertions: should_not_return_sba_settings_for_json_accept spring-boot-admin-server-ui/src/test/java/de/codecentric/boot/admin/server/ui/AbstractAdminUiApplicationTest.java:139
- No assertions: should_return_404_for_unknown_path spring-boot-admin-server-ui/src/test/java/de/codecentric/boot/admin/server/ui/AbstractAdminUiApplicationTest.java:88
- No assertions: should_return_correct_content_type_for_css_extensions spring-boot-admin-server-ui/src/test/java/de/codecentric/boot/admin/server/ui/AbstractAdminUiApplicationTest.java:113
- No assertions: should_return_correct_content_type_for_js_extensions spring-boot-admin-server-ui/src/test/java/de/codecentric/boot/admin/server/ui/AbstractAdminUiApplicationTest.java:99
- No assertions: should_not_return_sba_settings_for_json_accept_when_default_content_type_is_json spring-boot-admin-server-ui/src/test/java/de/codecentric/boot/admin/server/ui/AdminUiServletDefaultJsonContentTypeApplicationTest.java:101
- No assertions: should_computeIfPresent spring-boot-admin-server/src/test/java/de/codecentric/boot/admin/server/domain/entities/AbstractInstanceRepositoryTest.java:77
- No assertions: should_not_compute_if_not_present spring-boot-admin-server/src/test/java/de/codecentric/boot/admin/server/domain/entities/AbstractInstanceRepositoryTest.java:101
- No assertions: should_retry_compute spring-boot-admin-server/src/test/java/de/codecentric/boot/admin/server/domain/entities/AbstractInstanceRepositoryTest.java:137
- No assertions: should_save spring-boot-admin-server/src/test/java/de/codecentric/boot/admin/server/domain/entities/AbstractInstanceRepositoryTest.java:50
- No assertions: should_refresh_snapshots_eagerly_on_optimistic_locking_exception spring-boot-admin-server/src/test/java/de/codecentric/boot/admin/server/domain/entities/SnapshottingInstanceRepositoryTest.java:135
- No assertions: should_return_outdated_instance_not_present_in_cache spring-boot-admin-server/src/test/java/de/codecentric/boot/admin/server/domain/entities/SnapshottingInstanceRepositoryTest.java:125
- No assertions: should_prune_info_updated_events_if_enabled spring-boot-admin-server/src/test/java/de/codecentric/boot/admin/server/eventstore/AbstractEventStoreTest.java:160
- No assertions: should_shorten_log_on_exceeded_capacity spring-boot-admin-server/src/test/java/de/codecentric/boot/admin/server/eventstore/AbstractEventStoreTest.java:102
- No test reaches this file spring-boot-admin-server-ui/src/main/frontend/views/instances/env/env-manager.vue:1
- No test reaches this file spring-boot-admin-server-ui/src/main/frontend/views/instances/loggers/loggers.vue:1
- No test reaches this file spring-boot-admin-server-ui/src/main/frontend/views/instances/metrics/index.vue:1
- No test reaches this file spring-boot-admin-server-ui/src/main/frontend/views/instances/scheduledtasks/index.vue:1
- No test reaches this file spring-boot-admin-server-ui/src/main/frontend/views/instances/conditions/index.vue:1
- No test reaches this file spring-boot-admin-server-ui/src/main/frontend/views/instances/env/index.vue:1
- No test reaches this file spring-boot-admin-server-ui/src/main/frontend/views/instances/sessions/sessions-list.vue:1
- No test reaches this file spring-boot-admin-server-ui/src/main/frontend/views/instances/configprops/index.vue:1
- No test reaches this file spring-boot-admin-server-ui/src/main/frontend/views/instances/sessions/index.vue:1
- No test reaches this file spring-boot-admin-server-ui/src/main/frontend/views/instances/gateway/add-route.vue:1
- No test reaches this file spring-boot-admin-server-ui/src/main/frontend/views/instances/startup/index.vue:1
- No test reaches this file spring-boot-admin-server-ui/src/main/frontend/views/instances/liquibase/index.vue:1
- No test reaches this file spring-boot-admin-server-ui/src/main/frontend/views/instances/caches/index.vue:1
- No test reaches this file spring-boot-admin-server-ui/src/main/frontend/index.ts:1
- No test reaches this file spring-boot-admin-server-ui/src/main/frontend/views/instances/startup/tree-table.vue:1
- No test reaches this file spring-boot-admin-server-ui/src/main/frontend/views/instances/caches/caches-list.vue:1
- No test reaches this file spring-boot-admin-server-ui/src/main/frontend/views/instances/beans/index.vue:1
- No test reaches this file spring-boot-admin-server-ui/src/main/frontend/views/about/index.vue:1
- No test reaches this file spring-boot-admin-server-ui/src/main/frontend/views/instances/quartz/index.vue:1
- No test reaches this file spring-boot-admin-server-ui/src/main/frontend/views/instances/flyway/index.vue:1
- No test reaches this file spring-boot-admin-server-ui/src/main/frontend/views/instances/gateway/routes-list.vue:1
- No test reaches this file spring-boot-admin-server-ui/src/main/frontend/views/mcp/mcp.service.ts:1
- No test reaches this file spring-boot-admin-server-ui/src/main/frontend/views/instances/gateway/routes.vue:1
- No test reaches this file spring-boot-admin-server-ui/src/main/frontend/views/instances/gateway/global-filters.vue:1
- No test reaches this file spring-boot-admin-server-ui/src/main/frontend/views/instances/startup/tree-item.vue:1
- Untrusted text written into markup unescaped spring-boot-admin-server-ui/src/main/frontend/components/sba-alert.vue:30
- Untrusted text written into markup unescaped spring-boot-admin-server-ui/src/main/frontend/components/sba-formatted-obj.vue:18
- Untrusted text written into markup unescaped spring-boot-admin-server-ui/src/main/frontend/components/sba-navbar/sba-navbar-brand.vue:2
- Untrusted text written into markup unescaped spring-boot-admin-server-ui/src/main/frontend/views/instances/auditevents/auditevents-list.vue:21
- Untrusted text written into markup unescaped spring-boot-admin-server-ui/src/main/frontend/views/instances/auditevents/auditevents-list.vue:22
- Untrusted text written into markup unescaped spring-boot-admin-server-ui/src/main/frontend/views/instances/auditevents/auditevents-list.vue:23
- Untrusted text written into markup unescaped spring-boot-admin-server-ui/src/main/frontend/views/instances/auditevents/auditevents-list.vue:24
- Untrusted text written into markup unescaped spring-boot-admin-server-ui/src/main/frontend/views/instances/auditevents/auditevents-list.vue:25
- Untrusted text written into markup unescaped spring-boot-admin-server-ui/src/main/frontend/views/instances/auditevents/auditevents-list.vue:88
- Untrusted text written into markup unescaped spring-boot-admin-server-ui/src/main/frontend/views/instances/auditevents/auditevents-list.vue:92
- Untrusted text written into markup unescaped spring-boot-admin-server-ui/src/main/frontend/views/instances/caches/caches-list.vue:21
- Untrusted text written into markup unescaped spring-boot-admin-server-ui/src/main/frontend/views/instances/caches/caches-list.vue:22
- Untrusted text written into markup unescaped spring-boot-admin-server-ui/src/main/frontend/views/instances/details/health-details.vue:138
- Untrusted text written into markup unescaped spring-boot-admin-server-ui/src/main/frontend/views/instances/env/index.vue:75
- Untrusted text written into markup unescaped spring-boot-admin-server-ui/src/main/frontend/views/instances/logfile/index.vue:154
- Untrusted text written into markup unescaped spring-boot-admin-server-ui/src/main/frontend/views/instances/sessions/sessions-list.vue:21
- Untrusted text written into markup unescaped spring-boot-admin-server-ui/src/main/frontend/views/instances/sessions/sessions-list.vue:22
- Untrusted text written into markup unescaped spring-boot-admin-server-ui/src/main/frontend/views/instances/sessions/sessions-list.vue:23
- Untrusted text written into markup unescaped spring-boot-admin-server-ui/src/main/frontend/views/instances/sessions/sessions-list.vue:24
- Untrusted text written into markup unescaped spring-boot-admin-server-ui/src/main/frontend/views/instances/sessions/sessions-list.vue:25
- Untrusted text written into markup unescaped spring-boot-admin-server-ui/src/main/frontend/views/instances/sessions/sessions-list.vue:26
- Untrusted text written into markup unescaped spring-boot-admin-server-ui/src/main/frontend/views/instances/shell/sidebar.vue:62
- Untrusted text written into markup unescaped spring-boot-admin-server-ui/src/main/frontend/views/instances/shell/sidebar.vue:299
- 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
- Focus outline removed in CSS without a :focus replacement spring-boot-admin-server-ui/src/main/frontend/components/sba-button.vue:104
- Focus outline removed in CSS without a :focus replacement spring-boot-admin-server-ui/src/main/frontend/components/sba-button.vue:117
- Focus outline removed in CSS without a :focus replacement spring-boot-admin-server-ui/src/main/frontend/components/sba-button.vue:121
- Focus outline removed in CSS without a :focus replacement spring-boot-admin-server-ui/src/main/frontend/components/sba-button.vue:125
- Focus outline removed in CSS without a :focus replacement spring-boot-admin-server-ui/src/main/frontend/components/sba-button.vue:129
- Focus outline removed in CSS without a :focus replacement spring-boot-admin-server-ui/src/main/frontend/components/sba-button.vue:137
- Focus outline removed in CSS without a :focus replacement spring-boot-admin-server-ui/src/main/frontend/components/sba-button.vue:145
- Focus outline removed in CSS without a :focus replacement spring-boot-admin-server-ui/src/main/frontend/components/sba-navbar/sba-navbar-toggle.vue:71
- Focus outline removed in CSS without a :focus replacement spring-boot-admin-server-ui/src/main/frontend/components/sba-nav/sba-nav-dropdown.vue:99
- Focus outline removed in CSS without a :focus replacement spring-boot-admin-server-ui/src/main/frontend/components/sba-dropdown/sba-dropdown.vue:78
- Async function without AbortSignal: fetchTools spring-boot-admin-server-ui/src/main/frontend/views/mcp/mcp.service.ts:57
- Async function without AbortSignal: initializeSession spring-boot-admin-server-ui/src/main/frontend/views/mcp/mcp.service.ts:80
- Async function without AbortSignal: refreshApplications spring-boot-admin-server-ui/src/main/frontend/services/application.ts:131
- Async function without AbortSignal: list spring-boot-admin-server-ui/src/main/frontend/services/application.ts:135
- Async function without AbortSignal: fetchEvents spring-boot-admin-server-ui/src/main/frontend/services/instance.ts:91
- Async function without AbortSignal: get spring-boot-admin-server-ui/src/main/frontend/services/instance.ts:115
- Async function without AbortSignal: delete spring-boot-admin-server-ui/src/main/frontend/services/notification-filter.ts:57
- Async function without AbortSignal: getFilters spring-boot-admin-server-ui/src/main/frontend/services/notification-filter.ts:65
- Async function without AbortSignal: addFilter spring-boot-admin-server-ui/src/main/frontend/services/notification-filter.ts:71
- Anchor without href spring-boot-admin-server-ui/src/main/frontend/views/instances/details/instance-switcher.vue:48
- Anchor without href spring-boot-admin-server-ui/src/main/frontend/views/instances/details/instance-switcher.vue
- Anchor without href spring-boot-admin-server-ui/src/main/frontend/views/instances/jolokia/index.vue:77
- Anchor without href spring-boot-admin-server-ui/src/main/frontend/views/instances/jolokia/index.vue
- Anchor without href spring-boot-admin-server-ui/src/main/frontend/views/instances/jolokia/index.vue:87
- Anchor without href spring-boot-admin-server-ui/src/main/frontend/views/instances/shell/sidebar.vue:43
- Anchor without href spring-boot-admin-server-ui/src/main/frontend/views/instances/startup/tree-item.vue:25
- Stateful singleton: SnapshottingInstanceRepository spring-boot-admin-server/src/main/java/de/codecentric/boot/admin/server/domain/entities/SnapshottingInstanceRepository.java:42
- Stateful singleton: FilteringNotifier spring-boot-admin-server/src/main/java/de/codecentric/boot/admin/server/notify/filter/FilteringNotifier.java:45
- Stateful singleton: RemindingNotifier spring-boot-admin-server/src/main/java/de/codecentric/boot/admin/server/notify/RemindingNotifier.java:48
- Stateful singleton: InfoUpdateTrigger spring-boot-admin-server/src/main/java/de/codecentric/boot/admin/server/services/InfoUpdateTrigger.java:37
- Stateful singleton: StatusUpdateTrigger spring-boot-admin-server/src/main/java/de/codecentric/boot/admin/server/services/StatusUpdateTrigger.java:36
- Stateful singleton: StatusUpdater spring-boot-admin-server/src/main/java/de/codecentric/boot/admin/server/services/StatusUpdater.java:55
- Test project verifies nothing: spring-boot-admin-sample-consul spring-boot-admin-samples/spring-boot-admin-sample-consul/src/test/java/de/codecentric/boot/admin/sample/SpringBootAdminConsulApplicationTest.java:30
- Test project verifies nothing: spring-boot-admin-sample-eureka spring-boot-admin-samples/spring-boot-admin-sample-eureka/src/test/java/de/codecentric/boot/admin/SpringBootAdminEurekaApplicationTest.java:29
- Test project verifies nothing: spring-boot-admin-sample-hazelcast spring-boot-admin-samples/spring-boot-admin-sample-hazelcast/src/test/java/de/codecentric/boot/admin/sample/SpringBootAdminHazelcastApplicationTest.java:29
- Test project verifies nothing: spring-boot-admin-sample-reactive spring-boot-admin-samples/spring-boot-admin-sample-reactive/src/test/java/de/codecentric/boot/admin/sample/SpringBootAdminReactiveApplicationTest.java:29
- Test project verifies nothing: spring-boot-admin-sample-servlet spring-boot-admin-samples/spring-boot-admin-sample-servlet/src/test/java/de/codecentric/boot/admin/sample/SpringBootAdminServletApplicationTest.java:29
- Test project verifies nothing: spring-boot-admin-sample-zookeeper spring-boot-admin-samples/spring-boot-admin-sample-zookeeper/src/test/java/de/codecentric/boot/admin/sample/SpringBootAdminZookeeperApplicationTest.java:30
- Data table has no header cells spring-boot-admin-server-ui/src/main/frontend/views/instances/configprops/index.vue:42
- Data table has no header cells spring-boot-admin-server-ui/src/main/frontend/views/instances/logfile/index.vue:141
- Data table has no header cells spring-boot-admin-server-ui/src/main/frontend/views/instances/loggers/loggers-list.vue:18
- Data table has no header cells spring-boot-admin-server-ui/src/main/frontend/views/instances/threaddump/thread-list-item.vue:2
- Data table has no header cells spring-boot-admin-server/src/main/resources/META-INF/spring-boot-admin-server/mail/status-changed.html:87
- Animation without a prefers-reduced-motion guard spring-boot-admin-server-ui/src/main/frontend/components/sba-action-button-scoped.vue
- Animation without a prefers-reduced-motion guard spring-boot-admin-server-ui/src/main/frontend/components/sba-loading-spinner.vue
- Animation without a prefers-reduced-motion guard spring-boot-admin-server-ui/src/main/frontend/views/instances/startup/tree-table.vue:218
- Animation without a prefers-reduced-motion guard spring-boot-admin-docs/src/site/src/components/CopyButton.module.css:13
- Edited copy of a member (6 corresponding lines) spring-boot-admin-server/src/main/java/de/codecentric/boot/admin/server/web/client/LegacyEndpointConverters.java:320
- Edited copy of a member (6 corresponding lines) spring-boot-admin-server/src/main/java/de/codecentric/boot/admin/server/services/StatusUpdateTrigger.java:70
- Edited copy of a member (6 corresponding lines) spring-boot-admin-server/src/main/java/de/codecentric/boot/admin/server/notify/LetsChatNotifier.java:87
- Edited copy of a member (6 corresponding lines) spring-boot-admin-server/src/main/java/de/codecentric/boot/admin/server/domain/values/Endpoints.java:58
- REDACTED
- REDACTED
- REDACTED
- Edited copy of a member (7 corresponding lines) spring-boot-admin-server/src/main/java/de/codecentric/boot/admin/server/services/InfoUpdateTrigger.java:78
- Edited copy of a member (7 corresponding lines) spring-boot-admin-server/src/main/java/de/codecentric/boot/admin/server/config/AdminServerWebConfiguration.java:91
- Edited copy of a member (7 corresponding lines) spring-boot-admin-server/src/main/java/de/codecentric/boot/admin/server/notify/MicrosoftTeamsNotifier.java:239
- Duplicated block (10 lines × 2) spring-boot-admin-server-mcp/src/main/java/de/codecentric/boot/admin/server/mcp/tools/ScheduledTasksTools.java:87
- Duplicated block (10 lines × 2) spring-boot-admin-server/src/main/java/de/codecentric/boot/admin/server/notify/OpsGenieNotifier.java:164
- Duplicated block (10 lines × 2) spring-boot-admin-server/src/main/java/de/codecentric/boot/admin/server/services/AbstractEventHandler.java:70
- Duplicated block (6 lines × 2) spring-boot-admin-samples/spring-boot-admin-sample-hazelcast/src/main/java/de/codecentric/boot/admin/sample/SpringBootAdminHazelcastApplication.java:125
- Duplicated block (6 lines × 2) spring-boot-admin-server/src/main/java/de/codecentric/boot/admin/server/web/reactive/InstancesProxyController.java:71
- Duplicated block (6 lines × 2) spring-boot-admin-server/src/main/java/de/codecentric/boot/admin/server/services/InfoUpdateTrigger.java:55
- Duplicated block (5 lines × 2) spring-boot-admin-samples/spring-boot-admin-sample-eureka/src/main/java/de/codecentric/boot/admin/SpringBootAdminEurekaApplication.java:56
- Duplicated block (5 lines × 2) spring-boot-admin-client/src/main/java/de/codecentric/boot/admin/client/config/SpringBootAdminClientAutoConfiguration.java:154
- Duplicated block (5 lines × 2) spring-boot-admin-client/src/main/java/de/codecentric/boot/admin/client/config/SpringBootAdminClientEnabledCondition.java:57
- Recursive walk over a caller-supplied document has no depth cap spring-boot-admin-server-ui/src/main/frontend/views/instances/sbomdependencytrees/dependencyTree.ts:185
- Recursive walk over a caller-supplied document has no depth cap spring-boot-admin-server-ui/src/main/frontend/views/instances/sbomdependencytrees/sbomUtils.ts:84
- Recursive walk over a caller-supplied document has no depth cap spring-boot-admin-server-ui/src/main/frontend/utils/sortObject.ts:3
- Swallowed exception (empty catch) spring-boot-admin-server-ui/src/main/frontend/views/instances/details/health-details.vue:184
- Swallowed exception (empty catch) spring-boot-admin-server-ui/src/main/frontend/views/instances/details/health-details.vue:233
- Swallowed exception (empty catch) spring-boot-admin-server-ui/src/main/frontend/utils/formatWithDataTypes.ts:86
- Low contrast colour pair in CSS (2.0:1) spring-boot-admin-server-ui/src/main/frontend/views/instances/gateway/route-definition.vue:124
- Low contrast colour pair in CSS (2.0:1) spring-boot-admin-server-ui/src/main/frontend/views/instances/gateway/route.vue:100
- FunctionTooLong: HexMesh.HexMesh spring-boot-admin-docs/src/site/src/components/HexMesh.tsx:67
- FunctionTooLong: dependencyTree.updateDependencyTree spring-boot-admin-server-ui/src/main/frontend/views/instances/sbomdependencytrees/dependencyTree.ts:123
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Edited copy of a member (10 corresponding lines) spring-boot-admin-server/src/main/java/de/codecentric/boot/admin/server/web/reactive/InstancesProxyController.java:116
- Edited copy of a member (10 corresponding lines) spring-boot-admin-server-cloud/src/main/java/de/codecentric/boot/admin/server/cloud/discovery/DefaultServiceInstanceConverter.java:71
- Edited copy of a member (5 corresponding lines) spring-boot-admin-server/src/main/java/de/codecentric/boot/admin/server/notify/LetsChatNotifier.java:94
- Edited copy of a member (5 corresponding lines) spring-boot-admin-server/src/main/java/de/codecentric/boot/admin/server/notify/AbstractStatusChangeNotifier.java:81
- Duplicated block (8 lines × 2) spring-boot-admin-server/src/main/java/de/codecentric/boot/admin/server/domain/events/InstanceRegisteredEvent.java:42
- Duplicated block (8 lines × 2) spring-boot-admin-server/src/main/java/de/codecentric/boot/admin/server/services/InfoUpdateTrigger.java:87
- Off the main sequence: spring-boot-admin-client
- Off the main sequence: spring-boot-admin-server
- Low cohesion: StatusUpdater (LCOM4 5) spring-boot-admin-server/src/main/java/de/codecentric/boot/admin/server/services/StatusUpdater.java:55
- Low cohesion: SnapshottingInstanceRepository (LCOM4 4) spring-boot-admin-server/src/main/java/de/codecentric/boot/admin/server/domain/entities/SnapshottingInstanceRepository.java:42
- Outbound HTTP without resilience spring-boot-admin-server/src/main/java/de/codecentric/boot/admin/server/config/AdminServerNotifierAutoConfiguration.java:88
- Outbound HTTP without resilience spring-boot-admin-server/src/main/java/de/codecentric/boot/admin/server/web/client/InstanceWebClient.java:79
- Duplicated block (27 lines × 2 locations) spring-boot-admin-server-ui/src/main/frontend/views/applications/ActionHandler.ts:20
- Duplicated block (27 lines × 2 locations) spring-boot-admin-server-ui/src/main/frontend/views/instances/httpexchanges/exchanges-chart.vue:102
- Duplicated block (24 lines × 2 locations) spring-boot-admin-server-ui/src/main/frontend/views/instances/details/details-cache.vue:260
- Duplicated block (24 lines × 2 locations) spring-boot-admin-server-ui/src/main/frontend/views/instances/details/details-datasource.vue:108
- Duplicated block (23 lines × 2 locations) spring-boot-admin-server-ui/src/main/frontend/views/applications/ActionHandler.ts:141
- Duplicated block (23 lines × 2 locations) spring-boot-admin-server-ui/src/main/frontend/views/instances/details/details-memory.vue:200
- Duplicated block (18 lines × 2 locations) spring-boot-admin-server-ui/src/main/frontend/views/instances/details/details-cache.vue:184
- Duplicated block (18 lines × 2 locations) spring-boot-admin-server-ui/src/main/frontend/views/instances/quartz/trigger-types/calendar-interval-details.vue:69
- Duplicated block (14 lines × 2 locations) spring-boot-admin-server-ui/src/main/frontend/services/application.ts:225
- Duplicated block (14 lines × 2 locations) spring-boot-admin-server-ui/src/main/frontend/views/instances/configprops/index.vue:70
- Duplicated block (8 lines × 2 locations) spring-boot-admin-server-ui/src/main/frontend/views/instances/quartz/trigger-types/daily-time-interval-details.vue:87
- Duplicated block (8 lines × 2 locations) spring-boot-admin-server-ui/src/main/frontend/views/journal/utils.ts:27
- <canvas> without a text alternative spring-boot-admin-server-ui/src/main/frontend/views/instances/details/LineChart.vue:19
- Page without a main landmark spring-boot-admin-server/src/main/resources/META-INF/spring-boot-admin-server/mail/status-changed.html:18
- BeansTools.formatBeans (cyclomatic 23) spring-boot-admin-server-mcp/src/main/java/de/codecentric/boot/admin/server/mcp/tools/BeansTools.java:73
- EnvTools.formatEnv (cyclomatic 19) spring-boot-admin-server-mcp/src/main/java/de/codecentric/boot/admin/server/mcp/tools/EnvTools.java:104
- transformToJSON.transformToJSON (cyclomatic 18) spring-boot-admin-server-ui/src/main/frontend/utils/transformToJSON.ts:71
- ThreadDumpTools.formatThreadDump (cyclomatic 17) spring-boot-admin-server-mcp/src/main/java/de/codecentric/boot/admin/server/mcp/tools/ThreadDumpTools.java:81
- HexMesh.HexMesh (cyclomatic 17) spring-boot-admin-docs/src/site/src/components/HexMesh.tsx:67
- LoggersTools.formatLoggers (cyclomatic 16) spring-boot-admin-server-mcp/src/main/java/de/codecentric/boot/admin/server/mcp/tools/LoggersTools.java:146
- McpService.categoryOf (cyclomatic 16) spring-boot-admin-server-ui/src/main/frontend/views/mcp/mcp.service.ts:31
- Repeated repair: spring-boot-admin-server/src/main/java/de/codecentric/boot/admin/server/config/AdminServerHazelcastAutoConfiguration.java spring-boot-admin-server/src/main/java/de/codecentric/boot/admin/server/config/AdminServerHazelcastAutoConfiguration.java:69
- TodoComment spring-boot-admin-server/src/main/java/de/codecentric/boot/admin/server/services/ApplicationRegistry.java:128
- transformToJSON.transformToJSON (cognitive 47) spring-boot-admin-server-ui/src/main/frontend/utils/transformToJSON.ts:71
- ThreadDumpTools.formatThreadDump (cognitive 41) spring-boot-admin-server-mcp/src/main/java/de/codecentric/boot/admin/server/mcp/tools/ThreadDumpTools.java:81
- BeansTools.formatBeans (cognitive 38) spring-boot-admin-server-mcp/src/main/java/de/codecentric/boot/admin/server/mcp/tools/BeansTools.java:73
- EnvTools.formatEnv (cognitive 29) spring-boot-admin-server-mcp/src/main/java/de/codecentric/boot/admin/server/mcp/tools/EnvTools.java:104
- ScheduledTasksTools.formatScheduledTasks (cognitive 25) spring-boot-admin-server-mcp/src/main/java/de/codecentric/boot/admin/server/mcp/tools/ScheduledTasksTools.java:65
- CachesTools.formatCaches (cognitive 24) spring-boot-admin-server-mcp/src/main/java/de/codecentric/boot/admin/server/mcp/tools/CachesTools.java:63
- HttpExchangesTools.formatExchanges (cognitive 24) spring-boot-admin-server-mcp/src/main/java/de/codecentric/boot/admin/server/mcp/tools/HttpExchangesTools.java:75
- LoggersTools.formatLoggers (cognitive 21) spring-boot-admin-server-mcp/src/main/java/de/codecentric/boot/admin/server/mcp/tools/LoggersTools.java:146
- HexMesh.HexMesh (cognitive 20) spring-boot-admin-docs/src/site/src/components/HexMesh.tsx:67
- formatWithDataTypes.formatWithDataTypes (cognitive 20) spring-boot-admin-server-ui/src/main/frontend/utils/formatWithDataTypes.ts:53
- logtail.default (cognitive 17) spring-boot-admin-server-ui/src/main/frontend/utils/logtail.ts:136
- TooManyMethods: Instance spring-boot-admin-server-ui/src/main/frontend/services/instance.ts:47
- Change coupling: sba-config.ts ↔ AdminServerUiProperties.java spring-boot-admin-server-ui/src/main/frontend/sba-config.ts:1
- REDACTED
- REDACTED
- Near-duplicate member family (4 members, 13 shared lines) spring-boot-admin-samples/spring-boot-admin-sample-hazelcast/src/main/java/de/codecentric/boot/admin/sample/SpringBootAdminHazelcastApplication.java:149
- Members sharing a duplicated core (6 members, 50+ identical tokens) spring-boot-admin-samples/spring-boot-admin-sample-hazelcast/src/main/java/de/codecentric/boot/admin/sample/SpringBootAdminHazelcastApplication.java:123
- Edited copies of one member (3 members, 18+ corresponding lines) spring-boot-admin-client/src/main/java/de/codecentric/boot/admin/client/registration/DefaultApplicationFactory.java:77
- Edited copies of one member (4 members, 9+ corresponding lines) spring-boot-admin-server-mcp/src/main/java/de/codecentric/boot/admin/server/mcp/tools/ActuatorClient.java:109
- Edited copy of a member (13 corresponding lines) spring-boot-admin-server/src/main/java/de/codecentric/boot/admin/server/notify/DingTalkNotifier.java:97
- Edited copy of a member (11 corresponding lines) spring-boot-admin-server/src/main/java/de/codecentric/boot/admin/server/notify/DingTalkNotifier.java:79
- Edited copy of a member (9 corresponding lines) spring-boot-admin-server/src/main/java/de/codecentric/boot/admin/server/services/CloudFoundryInstanceIdGenerator.java:39
- Edited copies of one member (3 members, 10+ corresponding lines) spring-boot-admin-server-mcp/src/main/java/de/codecentric/boot/admin/server/mcp/tools/ActuatorClient.java:132
- Duplicated block (13 lines × 2) spring-boot-admin-client/src/main/java/de/codecentric/boot/admin/client/registration/DefaultApplicationFactory.java:80
- Duplicated block (18 lines × 2) spring-boot-admin-samples/spring-boot-admin-sample-eureka/src/main/java/de/codecentric/boot/admin/SpringBootAdminEurekaApplication.java:65
- Duplicated block (11 lines × 2) spring-boot-admin-samples/spring-boot-admin-sample-servlet/src/main/java/de/codecentric/boot/admin/sample/CustomNotifier.java:40
- Duplicated block (9–10 lines × 3) spring-boot-admin-samples/spring-boot-admin-sample-hazelcast/src/main/java/de/codecentric/boot/admin/sample/SpringBootAdminHazelcastApplication.java:154
- Duplicated block (9–10 lines × 2) spring-boot-admin-samples/spring-boot-admin-sample-consul/src/main/java/de/codecentric/boot/admin/sample/SpringBootAdminConsulApplication.java:60
- Duplicated block (8–10 lines × 2) spring-boot-admin-server-mcp/src/main/java/de/codecentric/boot/admin/server/mcp/tools/BeansTools.java:95
- Duplicated block (7–10 lines × 2) spring-boot-admin-server/src/main/java/de/codecentric/boot/admin/server/web/reactive/InstancesProxyController.java:119
- Duplicated block (7–8 lines × 4) spring-boot-admin-samples/spring-boot-admin-sample-hazelcast/src/main/java/de/codecentric/boot/admin/sample/SpringBootAdminHazelcastApplication.java:150
- Duplicated block (9 lines × 2) spring-boot-admin-server-mcp/src/main/java/de/codecentric/boot/admin/server/mcp/tools/EnvTools.java:126
- Duplicated block (6–7 lines × 4) spring-boot-admin-samples/spring-boot-admin-sample-hazelcast/src/main/java/de/codecentric/boot/admin/sample/SpringBootAdminHazelcastApplication.java:158
- Duplicated block (9 lines × 3) spring-boot-admin-server-mcp/src/main/java/de/codecentric/boot/admin/server/mcp/tools/ScheduledTasksTools.java:69
- Duplicated block (5 lines × 6) spring-boot-admin-samples/spring-boot-admin-sample-hazelcast/src/main/java/de/codecentric/boot/admin/sample/SpringBootAdminHazelcastApplication.java:129
- Duplicated block (5 lines × 3) spring-boot-admin-server-mcp/src/main/java/de/codecentric/boot/admin/server/mcp/tools/EnvTools.java:69
- Duplicated block (6 lines × 3) spring-boot-admin-server/src/main/java/de/codecentric/boot/admin/server/notify/DiscordNotifier.java:75
- Coverage not measured — JavaScript/TypeScript suite
- Coverage reaches no merge REDACTED:51
- Coverage collected but not gated
- SAST runs, but gates no merge
- Duplication concentrated across 20 sibling directories (23 clone groups) spring-boot-admin-server-ui/src/main/frontend/views/instances/httpexchanges/Exchange.ts:20
- Duplicated block (79 lines × 2 locations) spring-boot-admin-server-ui/src/main/frontend/views/instances/details/cache-chart.vue:41
- Duplicated block (70 lines × 2 locations) spring-boot-admin-server-ui/src/main/frontend/views/instances/httpexchanges/Exchange.ts:20
- Duplicated block with local edits (57 matched lines × 2 locations) spring-boot-admin-server-ui/src/main/frontend/views/instances/beans/index.vue:68
- Duplicated block with local edits (47 matched lines × 2 locations) spring-boot-admin-server-ui/src/main/frontend/components/sba-input.vue:119
- Duplicated block (40 lines × 2 locations) spring-boot-admin-server-ui/src/main/frontend/services/application.ts:247
- Duplicated block (33 lines × 2 locations) spring-boot-admin-server-ui/src/main/frontend/views/instances/gateway/global-filters.vue:78
- Duplicated block with local edits (32 matched lines × 2 locations) spring-boot-admin-server-ui/src/main/frontend/services/quartz-actuator.ts:232
- Duplicated block (32 lines × 2 locations) spring-boot-admin-server-ui/src/main/frontend/views/instances/flyway/index.vue:76
- Duplicated block (31 lines × 2 locations) spring-boot-admin-server-ui/src/main/frontend/services/quartz-actuator.ts:42
- Duplicated block (29 lines × 2 locations) spring-boot-admin-server-ui/src/main/frontend/views/instances/beans/beans-list.vue:67
- Duplicated block (26 lines × 2 locations) spring-boot-admin-server-ui/src/main/frontend/views/instances/httpexchanges/index.vue:203
- Duplicated block (25 lines × 2 locations) spring-boot-admin-server-ui/src/main/frontend/views/instances/details/details-datasource.vue:142
- Duplicated block (22 lines × 2 locations) spring-boot-admin-server-ui/src/main/frontend/views/instances/details/details-cache.vue:135
- Duplicated block with local edits (20 matched lines × 2 locations) spring-boot-admin-server-ui/src/main/frontend/views/instances/auditevents/auditevents-list.vue:108
- Duplicated block (20 lines × 2 locations) spring-boot-admin-server-ui/src/main/frontend/views/instances/httpexchanges/index.vue:168
- Duplicated block (19 lines × 2 locations) spring-boot-admin-server-ui/src/main/frontend/views/instances/configprops/index.vue:161
- Duplicated block with local edits (17 matched lines × 2 locations) spring-boot-admin-server-ui/src/main/frontend/views/instances/details/details-caches.vue:59
- Duplicated block (16 lines × 2 locations) spring-boot-admin-server-ui/src/main/frontend/components/sba-input.vue:178
- Duplicated block (15 lines × 2 locations) spring-boot-admin-server-ui/src/main/frontend/views/applications/ActionHandler.ts:123
- Duplicated block (13 lines × 3 locations) spring-boot-admin-server-ui/src/main/frontend/views/instances/details/details-caches.vue:57
- Duplicated block (13 lines × 2 locations) spring-boot-admin-server-ui/src/main/frontend/views/instances/httpexchanges/index.vue:256
- Duplicated block (12 lines × 2 locations) spring-boot-admin-server-ui/src/main/frontend/utils/logtail.ts:247
- Duplicated block (12 lines × 3 locations) spring-boot-admin-server-ui/src/main/frontend/views/instances/configprops/index.vue:174
- Duplicated block with local edits (12 matched lines × 2 locations) spring-boot-admin-server-ui/src/main/frontend/views/instances/mappings/index.vue:111
- Duplicated block (11 lines × 2 locations) spring-boot-admin-server-ui/src/main/frontend/views/instances/quartz/job-row.vue:350
- Duplicated block (10 lines × 2 locations) spring-boot-admin-server-ui/src/main/frontend/services/application.ts:142
- Duplicated block (9 lines × 2 locations) spring-boot-admin-server-ui/src/main/frontend/services/application.ts:182
- Complex function transformToJSON (cyclomatic 17, cognitive 58) spring-boot-admin-server-ui/src/main/frontend/utils/transformToJSON.ts:71
- Complex function categoryOf (cyclomatic 16, cognitive 15) spring-boot-admin-server-ui/src/main/frontend/views/mcp/mcp.service.ts:31
- Complex function formatWithDataTypes (cyclomatic 13, cognitive 20) spring-boot-admin-server-ui/src/main/frontend/utils/formatWithDataTypes.ts:53
- Complex function shortFormat (cyclomatic 12, cognitive 15) spring-boot-admin-server-ui/src/main/frontend/components/sba-time-ago.vue:21
- Complex function abbreviateLoggerName (cyclomatic 12, cognitive 14) spring-boot-admin-server-ui/src/main/frontend/composables/useClassnameShortener.ts:26
- spring-boot-admin-server-ui/src/main/frontend/mocks/instance/jolokia/data.ts: 2481 lines of code spring-boot-admin-server-ui/src/main/frontend/mocks/instance/jolokia/data.ts:1
- spring-boot-admin-server-ui/src/main/frontend/views/instances/logfile/index.vue: 889 lines of code spring-boot-admin-server-ui/src/main/frontend/views/instances/logfile/index.vue:1
- spring-boot-admin-server-ui/src/main/frontend/services/instance.ts: 505 lines of code spring-boot-admin-server-ui/src/main/frontend/services/instance.ts:1
- spring-boot-admin-server-ui/src/main/frontend/views/applications/index.vue: 470 lines of code spring-boot-admin-server-ui/src/main/frontend/views/applications/index.vue:1
- This package's lint script runs in no CI job spring-boot-admin-server-ui/package.json:14
- Dead file (~0 LoC) spring-boot-admin-server-ui/src/main/frontend/utils/toast.ts
Minor — 24 finding(s)
- redundant comment spring-boot-admin-server-ui/src/main/frontend/composables/ViewRegistry.ts:41
- redundant comment spring-boot-admin-server-ui/src/main/frontend/utils/axios.spec.ts:29
- redundant comment spring-boot-admin-server-ui/src/main/frontend/views/instances/httpexchanges/index.spec.ts:120
- Duplicated predicate spring-boot-admin-server/src/main/java/de/codecentric/boot/admin/server/services/CloudFoundryInstanceIdGenerator.java:43
- Duplicated predicate spring-boot-admin-server/src/main/java/de/codecentric/boot/admin/server/services/InfoUpdater.java:87
- Duplicated predicate spring-boot-admin-server-ui/src/main/frontend/mixins/subscribing.ts:40
- Projects may be oversized for their cohesion spring-boot-admin-server-ui/pom.xml:1
- Projects may be oversized for their cohesion REDACTED:1
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Off-boarding risk: anonymized user #1
- Further sole-owners (lower concentration)
- No ADRs found REDACTED:332
- REDACTED
- No ADRs
- Logging is not universal
- No rollback/health safety REDACTED:114
- Unused export 'removeElement' spring-boot-admin-server-ui/src/main/frontend/plugins/modal/helpers.ts:3
- Unused export 'getHttpStatus' spring-boot-admin-server-ui/src/main/frontend/utils/http-status.ts:101
- Not all async functions that make a request accept an AbortSignal
- Interpolated log message defeats structured logging spring-boot-admin-server/src/main/java/de/codecentric/boot/admin/server/domain/values/Registration.java:121
- Strict null checking is not enabled everywhere the repository type-checks
Minor — 1 finding(s)
- doc comments repeat the names spring-boot-admin-server-ui/src/main/frontend/services/quartz-actuator.ts:50
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 --log-opts "--full-history --all --skip=0 --max-count=200" --report-format json --report-path /tmp/watchdog-gitleaks-586d3cb92b9d4feab8f5dc65c682a504/history.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --log-opts "--full-history --all --skip=200 --max-count=800" --report-format json --report-path /tmp/watchdog-gitleaks-586d3cb92b9d4feab8f5dc65c682a504/history-1.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history-1.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --log-opts "--full-history --all --skip=1000 --max-count=3200" --report-format json --report-path /tmp/watchdog-gitleaks-586d3cb92b9d4feab8f5dc65c682a504/history-2.json --exit-code 0 --source . | 2 | artifacts/raw/gitleaks-history-2.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --log-opts "--full-history --all --skip=4200 --max-count=1361" --report-format json --report-path /tmp/watchdog-gitleaks-586d3cb92b9d4feab8f5dc65c682a504/history-3.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history-3.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-586d3cb92b9d4feab8f5dc65c682a504/tree.json --exit-code 0 --source . | 1 | 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 src/main . | 54 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . | 50 | artifacts/raw/trivy-fs.json |
| D31 · IaC & Container Security | trivy | — | trivy config --format json --quiet . | 13 | artifacts/raw/trivy-config.json |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. semgrep could not parse 1 file(s) — `spring-boot-admin-docs/src/site/docusaurus.config.ts` — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real. | 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/** . | 0 | artifacts/raw/trivy-fs.json |