Executive summary
paypal/squbs falls short of our standard for production because 72 files are no longer known to anyone active in the project and the project keeps no record of its design decisions. It scores 56 out of 100 and is rated Adequate, and all 13 of its critical findings are security problems.
Maturity, at 43, is the weakest lens and counts most in the score. The best first step is recording design decisions, worth about 12 points. Having someone learn and document the 72 files no active contributor knows comes next, worth about 11 points. Raising Maturity to 70 would lift the score to about 65.
Five pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Three known security holes in the packages the code depends on can be used by attackers, and three secrets can leak from the build pipeline. Pinning each tool to an exact version, updating the vulnerable packages and limiting each secret to its own step would close these risks. The two passwords or keys in the code's history need replacing, with the old ones switched off.
The product code is 12,983 lines, about €39,000 to rebuild.
If Maturity rose from 43 to 70, the lowest score rated Strong, the score would rise from 56 to about 65.
New since the last survey: 6 findings
- Code Duplication · Edited copy of a member (15 corresponding lines) squbs-pattern/src/main/scala/org/squbs/pattern/orchestration/Aggregator.scala
- Code Duplication · Edited copy of a member (16 corresponding lines) squbs-pattern/src/main/scala/org/squbs/pattern/orchestration/OFuture.scala
- Code Duplication · Edited copy of a member (13 corresponding lines) squbs-ext/src/main/scala/org/squbs/marshallers/json/XLangJsonSupport.scala
- Code Duplication · Edited copy of a member (17 corresponding lines) squbs-pattern/src/main/scala/org/squbs/pattern/orchestration/OFuture.scala
- Code Duplication · Edited copy of a member (7 corresponding lines) squbs-ext/src/main/scala/org/squbs/env/Environment.scala
- Code Duplication · Edited copy of a member (4 corresponding lines) squbs-unicomplex/src/main/scala/org/squbs/stream/LifecycleEventSource.scala
Rebuild cost: about €39,000 · Estimate
| Cost to rebuild | €13,000 to €65,000, for 217 to 688 hours of work, about 0.3 person-years for one engineer |
|---|---|
| Difficulty of the problem | Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.8 at a score of 56. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it. |
| Size | Small: 12,983 lines of product code |
| What it is not | Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one. |
Top priorities
Diagnosis: what the measurements show together
Architecture: which parts of the code depend on which
| uses → | 1 apache.pekko.http.org.squbs.util | 2 squbs | 3 squbs.actorregistry.japi | 4 squbs.admin.MBeanUtil | 5 squbs.cluster.rebalance | 6 squbs.dispatcher | 7 squbs.dispatcher.AdaptedThreadFactory | 8 squbs.dispatcher.ForkJoinConfigurator | 9 squbs.env | 10 squbs.httpclient.CircuitBreakerMetrics | 11 squbs.marshallers | 12 squbs.marshallers.json | 13 squbs.metrics | 14 squbs.pattern.orchestration | 15 squbs.pipeline | 16 squbs.streams.circuitbreaker | 17 squbs.cluster | 18 squbs.httpclient.ClientFlow | 19 squbs.pattern.orchestration.impl | 20 squbs.pattern.orchestration.japi | 21 squbs.pipeline.japi | 22 squbs.resolver | 23 squbs.streams.circuitbreaker.CircuitBreakerState | 24 squbs.streams.circuitbreaker.impl | 25 squbs.streams.circuitbreaker.japi | 26 squbs.unicomplex.UnicomplexBoot | 27 squbs.cluster.ZkClusterActor | 28 squbs.httpclient | 29 squbs.pattern.orchestration.impl.OPromise | 30 squbs.unicomplex | 31 squbs.admin | 32 squbs.lifecycle | 33 squbs.testkit | 34 squbs.unicomplex.CubeSupervisor | 35 squbs.unicomplex.Unicomplex | 36 squbs.actormonitor | 37 squbs.actorregistry | 38 squbs.stream | 39 squbs.testkit.japi | 40 squbs.actorregistry.ActorRegistry |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 apache.pekko.http.org.squbs.util | ||||||||||||||||||||||||||||||||||||||||
| 2 squbs | ||||||||||||||||||||||||||||||||||||||||
| 3 squbs.actorregistry.japi | ||||||||||||||||||||||||||||||||||||||||
| 4 squbs.admin.MBeanUtil | ||||||||||||||||||||||||||||||||||||||||
| 5 squbs.cluster.rebalance | ||||||||||||||||||||||||||||||||||||||||
| 6 squbs.dispatcher | ||||||||||||||||||||||||||||||||||||||||
| 7 squbs.dispatcher.AdaptedThreadFactory | ||||||||||||||||||||||||||||||||||||||||
| 8 squbs.dispatcher.ForkJoinConfigurator | ||||||||||||||||||||||||||||||||||||||||
| 9 squbs.env | ||||||||||||||||||||||||||||||||||||||||
| 10 squbs.httpclient.CircuitBreakerMetrics | ||||||||||||||||||||||||||||||||||||||||
| 11 squbs.marshallers | ||||||||||||||||||||||||||||||||||||||||
| 12 squbs.marshallers.json | ||||||||||||||||||||||||||||||||||||||||
| 13 squbs.metrics | ||||||||||||||||||||||||||||||||||||||||
| 14 squbs.pattern.orchestration | ||||||||||||||||||||||||||||||||||||||||
| 15 squbs.pipeline | ||||||||||||||||||||||||||||||||||||||||
| 16 squbs.streams.circuitbreaker | ||||||||||||||||||||||||||||||||||||||||
| 17 squbs.cluster | 1 | |||||||||||||||||||||||||||||||||||||||
| 18 squbs.httpclient.ClientFlow | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 19 squbs.pattern.orchestration.impl | 1 | |||||||||||||||||||||||||||||||||||||||
| 20 squbs.pattern.orchestration.japi | 1 | |||||||||||||||||||||||||||||||||||||||
| 21 squbs.pipeline.japi | 2 | |||||||||||||||||||||||||||||||||||||||
| 22 squbs.resolver | 4 | |||||||||||||||||||||||||||||||||||||||
| 23 squbs.streams.circuitbreaker.CircuitBreakerState | 1 | |||||||||||||||||||||||||||||||||||||||
| 24 squbs.streams.circuitbreaker.impl | 1 | |||||||||||||||||||||||||||||||||||||||
| 25 squbs.streams.circuitbreaker.japi | 1 | |||||||||||||||||||||||||||||||||||||||
| 26 squbs.unicomplex.UnicomplexBoot | 1 | |||||||||||||||||||||||||||||||||||||||
| 27 squbs.cluster.ZkClusterActor | 3 | |||||||||||||||||||||||||||||||||||||||
| 28 squbs.httpclient | 6 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 29 squbs.pattern.orchestration.impl.OPromise | 2 | |||||||||||||||||||||||||||||||||||||||
| 30 squbs.unicomplex | 1 | 1 | 2 | |||||||||||||||||||||||||||||||||||||
| 31 squbs.admin | 2 | |||||||||||||||||||||||||||||||||||||||
| 32 squbs.lifecycle | 1 | |||||||||||||||||||||||||||||||||||||||
| 33 squbs.testkit | 2 | |||||||||||||||||||||||||||||||||||||||
| 34 squbs.unicomplex.CubeSupervisor | 3 | |||||||||||||||||||||||||||||||||||||||
| 35 squbs.unicomplex.Unicomplex | 5 | |||||||||||||||||||||||||||||||||||||||
| 36 squbs.actormonitor | 2 | |||||||||||||||||||||||||||||||||||||||
| 37 squbs.actorregistry | 1 | |||||||||||||||||||||||||||||||||||||||
| 38 squbs.stream | 3 | 1 | ||||||||||||||||||||||||||||||||||||||
| 39 squbs.testkit.japi | 3 | 6 | ||||||||||||||||||||||||||||||||||||||
| 40 squbs.actorregistry.ActorRegistry | 1 |
17→5 squbs.cluster uses squbs.cluster.rebalance✕
- Connections
- 1 pair of types, where a type in squbs.cluster uses a type in squbs.cluster.rebalance.
- The types involved
org.squbs.cluster.ZkCluster→org.squbs.cluster.rebalance.RebalanceLogic
- Direction
- squbs.cluster uses squbs.cluster.rebalance, so a change to squbs.cluster.rebalance can break squbs.cluster, while a change to squbs.cluster can't break squbs.cluster.rebalance.
- Position
- Below the diagonal: squbs.cluster uses a module listed above it, which is the healthy direction.
18→9 squbs.httpclient.ClientFlow uses squbs.env✕
- Connections
- 1 pair of types, where a type in squbs.httpclient.ClientFlow uses a type in squbs.env.
- The types involved
org.squbs.httpclient.ClientFlow.Builder→org.squbs.env.Environment
- Direction
- squbs.httpclient.ClientFlow uses squbs.env, so a change to squbs.env can break squbs.httpclient.ClientFlow, while a change to squbs.httpclient.ClientFlow can't break squbs.env.
- Position
- Below the diagonal: squbs.httpclient.ClientFlow uses a module listed above it, which is the healthy direction.
18→16 squbs.httpclient.ClientFlow uses squbs.streams.circuitbreaker✕
- Connections
- 1 pair of types, where a type in squbs.httpclient.ClientFlow uses a type in squbs.streams.circuitbreaker.
- The types involved
org.squbs.httpclient.ClientFlow.Builder→org.squbs.streams.circuitbreaker.CircuitBreakerSettings
- Direction
- squbs.httpclient.ClientFlow uses squbs.streams.circuitbreaker, so a change to squbs.streams.circuitbreaker can break squbs.httpclient.ClientFlow, while a change to squbs.httpclient.ClientFlow can't break squbs.streams.circuitbreaker.
- Position
- Below the diagonal: squbs.httpclient.ClientFlow uses a module listed above it, which is the healthy direction.
19→14 squbs.pattern.orchestration.impl uses squbs.pattern.orchestration✕
- Connections
- 1 pair of types, where a type in squbs.pattern.orchestration.impl uses a type in squbs.pattern.orchestration.
- The types involved
org.squbs.pattern.orchestration.impl.OPromise→org.squbs.pattern.orchestration.OFuture
- Direction
- squbs.pattern.orchestration.impl uses squbs.pattern.orchestration, so a change to squbs.pattern.orchestration can break squbs.pattern.orchestration.impl, while a change to squbs.pattern.orchestration.impl can't break squbs.pattern.orchestration.
- Position
- Below the diagonal: squbs.pattern.orchestration.impl uses a module listed above it, which is the healthy direction.
20→14 squbs.pattern.orchestration.japi uses squbs.pattern.orchestration✕
- Connections
- 1 pair of types, where a type in squbs.pattern.orchestration.japi uses a type in squbs.pattern.orchestration.
- The types involved
org.squbs.pattern.orchestration.japi.AbstractOrchestrator→org.squbs.pattern.orchestration.Orchestrator
- Direction
- squbs.pattern.orchestration.japi uses squbs.pattern.orchestration, so a change to squbs.pattern.orchestration can break squbs.pattern.orchestration.japi, while a change to squbs.pattern.orchestration.japi can't break squbs.pattern.orchestration.
- Position
- Below the diagonal: squbs.pattern.orchestration.japi uses a module listed above it, which is the healthy direction.
21→15 squbs.pipeline.japi uses squbs.pipeline✕
- Connections
- 2 pairs of types, where a type in squbs.pipeline.japi uses a type in squbs.pipeline.
- The types involved
org.squbs.pipeline.japi.PipelineFlowFactory→org.squbs.pipeline.Contextorg.squbs.pipeline.japi.PipelineFlowFactory→org.squbs.pipeline.RequestContext
- Direction
- squbs.pipeline.japi uses squbs.pipeline, so a change to squbs.pipeline can break squbs.pipeline.japi, while a change to squbs.pipeline.japi can't break squbs.pipeline.
- Position
- Below the diagonal: squbs.pipeline.japi uses a module listed above it, which is the healthy direction.
22→9 squbs.resolver uses squbs.env✕
- Connections
- 4 pairs of types, where a type in squbs.resolver uses a type in squbs.env.
- The types involved
org.squbs.resolver.AbstractResolver→org.squbs.env.Environmentorg.squbs.resolver.EndpointNotExistsException→org.squbs.env.Environmentorg.squbs.resolver.Resolver→org.squbs.env.Environmentorg.squbs.resolver.ResolverRegistryExtension→org.squbs.env.Environment
- Direction
- squbs.resolver uses squbs.env, so a change to squbs.env can break squbs.resolver, while a change to squbs.resolver can't break squbs.env.
- Position
- Below the diagonal: squbs.resolver uses a module listed above it, which is the healthy direction.
23→16 squbs.streams.circuitbreaker.CircuitBreakerState uses squbs.streams.circuitbreaker✕
- Connections
- 1 pair of types, where a type in squbs.streams.circuitbreaker.CircuitBreakerState uses a type in squbs.streams.circuitbreaker.
- The types involved
org.squbs.streams.circuitbreaker.CircuitBreakerState.StateGauge→org.squbs.streams.circuitbreaker.State
- Direction
- squbs.streams.circuitbreaker.CircuitBreakerState uses squbs.streams.circuitbreaker, so a change to squbs.streams.circuitbreaker can break squbs.streams.circuitbreaker.CircuitBreakerState, while a change to squbs.streams.circuitbreaker.CircuitBreakerState can't break squbs.streams.circuitbreaker.
- Position
- Below the diagonal: squbs.streams.circuitbreaker.CircuitBreakerState uses a module listed above it, which is the healthy direction.
24→16 squbs.streams.circuitbreaker.impl uses squbs.streams.circuitbreaker✕
- Connections
- 1 pair of types, where a type in squbs.streams.circuitbreaker.impl uses a type in squbs.streams.circuitbreaker.
- The types involved
org.squbs.streams.circuitbreaker.impl.AtomicCircuitBreakerState→org.squbs.streams.circuitbreaker.CircuitBreakerState
- Direction
- squbs.streams.circuitbreaker.impl uses squbs.streams.circuitbreaker, so a change to squbs.streams.circuitbreaker can break squbs.streams.circuitbreaker.impl, while a change to squbs.streams.circuitbreaker.impl can't break squbs.streams.circuitbreaker.
- Position
- Below the diagonal: squbs.streams.circuitbreaker.impl uses a module listed above it, which is the healthy direction.
25→16 squbs.streams.circuitbreaker.japi uses squbs.streams.circuitbreaker✕
- Connections
- 1 pair of types, where a type in squbs.streams.circuitbreaker.japi uses a type in squbs.streams.circuitbreaker.
- The types involved
org.squbs.streams.circuitbreaker.japi.CircuitBreakerSettings→org.squbs.streams.circuitbreaker.CircuitBreakerState
- Direction
- squbs.streams.circuitbreaker.japi uses squbs.streams.circuitbreaker, so a change to squbs.streams.circuitbreaker can break squbs.streams.circuitbreaker.japi, while a change to squbs.streams.circuitbreaker.japi can't break squbs.streams.circuitbreaker.
- Position
- Below the diagonal: squbs.streams.circuitbreaker.japi uses a module listed above it, which is the healthy direction.
26→30 squbs.unicomplex.UnicomplexBoot uses squbs.unicomplex part of a loop✕
- Connections
- 1 pair of types, where a type in squbs.unicomplex.UnicomplexBoot uses a type in squbs.unicomplex.
- The types involved
org.squbs.unicomplex.UnicomplexBoot.CubeInit→org.squbs.unicomplex.Cube
- Direction
- squbs.unicomplex.UnicomplexBoot uses squbs.unicomplex, so a change to squbs.unicomplex can break squbs.unicomplex.UnicomplexBoot, while a change to squbs.unicomplex.UnicomplexBoot can't break squbs.unicomplex.
- 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.
27→17 squbs.cluster.ZkClusterActor uses squbs.cluster✕
- Connections
- 3 pairs of types, where a type in squbs.cluster.ZkClusterActor uses a type in squbs.cluster.
- The types involved
org.squbs.cluster.ZkClusterActor.MembersInfoBean→org.squbs.cluster.MembersInfoMXBeanorg.squbs.cluster.ZkClusterActor.PartitionsInfoBean→org.squbs.cluster.PartitionInfoorg.squbs.cluster.ZkClusterActor.PartitionsInfoBean→org.squbs.cluster.PartitionsInfoMXBean
- Direction
- squbs.cluster.ZkClusterActor uses squbs.cluster, so a change to squbs.cluster can break squbs.cluster.ZkClusterActor, while a change to squbs.cluster.ZkClusterActor can't break squbs.cluster.
- Position
- Below the diagonal: squbs.cluster.ZkClusterActor uses a module listed above it, which is the healthy direction.
28→9 squbs.httpclient uses squbs.env✕
- Connections
- 6 pairs of types, where a type in squbs.httpclient uses a type in squbs.env.
- The types involved
org.squbs.httpclient.ClientFlow→org.squbs.env.Environmentorg.squbs.httpclient.DefaultHttpEndpointResolver→org.squbs.env.Environmentorg.squbs.httpclient.HttpClientEndpointNotExistException→org.squbs.env.Environmentorg.squbs.httpclient.HttpClientExistException→org.squbs.env.Environmentorg.squbs.httpclient.HttpClientMarkDownException→org.squbs.env.Environmentorg.squbs.httpclient.HttpClientNotExistException→org.squbs.env.Environment
- Direction
- squbs.httpclient uses squbs.env, so a change to squbs.env can break squbs.httpclient, while a change to squbs.httpclient can't break squbs.env.
- Position
- Below the diagonal: squbs.httpclient uses a module listed above it, which is the healthy direction.
28→15 squbs.httpclient uses squbs.pipeline✕
- Connections
- 1 pair of types, where a type in squbs.httpclient uses a type in squbs.pipeline.
- The types involved
org.squbs.httpclient.ClientFlow→org.squbs.pipeline.RequestContext
- Direction
- squbs.httpclient uses squbs.pipeline, so a change to squbs.pipeline can break squbs.httpclient, while a change to squbs.httpclient can't break squbs.pipeline.
- Position
- Below the diagonal: squbs.httpclient uses a module listed above it, which is the healthy direction.
28→16 squbs.httpclient uses squbs.streams.circuitbreaker✕
- Connections
- 1 pair of types, where a type in squbs.httpclient uses a type in squbs.streams.circuitbreaker.
- The types involved
org.squbs.httpclient.ClientFlow→org.squbs.streams.circuitbreaker.CircuitBreakerSettings
- Direction
- squbs.httpclient uses squbs.streams.circuitbreaker, so a change to squbs.streams.circuitbreaker can break squbs.httpclient, while a change to squbs.httpclient can't break squbs.streams.circuitbreaker.
- Position
- Below the diagonal: squbs.httpclient uses a module listed above it, which is the healthy direction.
28→22 squbs.httpclient uses squbs.resolver✕
- Connections
- 1 pair of types, where a type in squbs.httpclient uses a type in squbs.resolver.
- The types involved
org.squbs.httpclient.DefaultHttpEndpointResolver→org.squbs.resolver.Resolver
- Direction
- squbs.httpclient uses squbs.resolver, so a change to squbs.resolver can break squbs.httpclient, while a change to squbs.httpclient can't break squbs.resolver.
- Position
- Below the diagonal: squbs.httpclient uses a module listed above it, which is the healthy direction.
29→19 squbs.pattern.orchestration.impl.OPromise uses squbs.pattern.orchestration.impl✕
- Connections
- 2 pairs of types, where a type in squbs.pattern.orchestration.impl.OPromise uses a type in squbs.pattern.orchestration.impl.
- The types involved
org.squbs.pattern.orchestration.impl.OPromise.DefaultOPromise→org.squbs.pattern.orchestration.impl.AbstractOPromiseorg.squbs.pattern.orchestration.impl.OPromise.DefaultOPromise→org.squbs.pattern.orchestration.impl.OPromise
- Direction
- squbs.pattern.orchestration.impl.OPromise uses squbs.pattern.orchestration.impl, so a change to squbs.pattern.orchestration.impl can break squbs.pattern.orchestration.impl.OPromise, while a change to squbs.pattern.orchestration.impl.OPromise can't break squbs.pattern.orchestration.impl.
- Position
- Below the diagonal: squbs.pattern.orchestration.impl.OPromise uses a module listed above it, which is the healthy direction.
30→15 squbs.unicomplex uses squbs.pipeline✕
- Connections
- 1 pair of types, where a type in squbs.unicomplex uses a type in squbs.pipeline.
- The types involved
org.squbs.unicomplex.RequestContextFlow→org.squbs.pipeline.RequestContext
- Direction
- squbs.unicomplex uses squbs.pipeline, so a change to squbs.pipeline can break squbs.unicomplex, while a change to squbs.unicomplex can't break squbs.pipeline.
- Position
- Below the diagonal: squbs.unicomplex uses a module listed above it, which is the healthy direction.
30→26 squbs.unicomplex uses squbs.unicomplex.UnicomplexBoot✕
- Connections
- 1 pair of types, where a type in squbs.unicomplex uses a type in squbs.unicomplex.UnicomplexBoot.
- The types involved
org.squbs.unicomplex.UnicomplexBoot→org.squbs.unicomplex.UnicomplexBoot.CubeInit
- Direction
- squbs.unicomplex uses squbs.unicomplex.UnicomplexBoot, so a change to squbs.unicomplex.UnicomplexBoot can break squbs.unicomplex, while a change to squbs.unicomplex can't break squbs.unicomplex.UnicomplexBoot.
- Position
- Below the diagonal: squbs.unicomplex uses a module listed above it, which is the healthy direction.
30→32 squbs.unicomplex uses squbs.lifecycle part of a loop✕
- Connections
- 2 pairs of types, where a type in squbs.unicomplex uses a type in squbs.lifecycle.
- The types involved
org.squbs.unicomplex.CubeSupervisor→org.squbs.lifecycle.GracefulStopHelperorg.squbs.unicomplex.Extension→org.squbs.lifecycle.ExtensionLifecycle
- Direction
- squbs.unicomplex uses squbs.lifecycle, so a change to squbs.lifecycle can break squbs.unicomplex, while a change to squbs.unicomplex can't break squbs.lifecycle.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
31→30 squbs.admin uses squbs.unicomplex✕
- Connections
- 2 pairs of types, where a type in squbs.admin uses a type in squbs.unicomplex.
- The types involved
org.squbs.admin.AdminSvc→org.squbs.unicomplex.RouteDefinitionorg.squbs.admin.AdminSvc→org.squbs.unicomplex.WebContext
- Direction
- squbs.admin uses squbs.unicomplex, so a change to squbs.unicomplex can break squbs.admin, while a change to squbs.admin can't break squbs.unicomplex.
- Position
- Below the diagonal: squbs.admin uses a module listed above it, which is the healthy direction.
32→30 squbs.lifecycle uses squbs.unicomplex✕
- Connections
- 1 pair of types, where a type in squbs.lifecycle uses a type in squbs.unicomplex.
- The types involved
org.squbs.lifecycle.ExtensionLifecycle→org.squbs.unicomplex.UnicomplexBoot
- Direction
- squbs.lifecycle uses squbs.unicomplex, so a change to squbs.unicomplex can break squbs.lifecycle, while a change to squbs.lifecycle can't break squbs.unicomplex.
- Position
- Below the diagonal: squbs.lifecycle uses a module listed above it, which is the healthy direction.
33→30 squbs.testkit uses squbs.unicomplex✕
- Connections
- 2 pairs of types, where a type in squbs.testkit uses a type in squbs.unicomplex.
- The types involved
org.squbs.testkit.CustomRouteTestKit→org.squbs.unicomplex.UnicomplexBootorg.squbs.testkit.CustomTestKit→org.squbs.unicomplex.UnicomplexBoot
- Direction
- squbs.testkit uses squbs.unicomplex, so a change to squbs.unicomplex can break squbs.testkit, while a change to squbs.testkit can't break squbs.unicomplex.
- Position
- Below the diagonal: squbs.testkit uses a module listed above it, which is the healthy direction.
34→30 squbs.unicomplex.CubeSupervisor uses squbs.unicomplex✕
- Connections
- 3 pairs of types, where a type in squbs.unicomplex.CubeSupervisor uses a type in squbs.unicomplex.
- The types involved
org.squbs.unicomplex.CubeSupervisor.ContextRegistrationResult→org.squbs.unicomplex.RegisterContextorg.squbs.unicomplex.CubeSupervisor.CubeStateBean→org.squbs.unicomplex.ActorErrorStateorg.squbs.unicomplex.CubeSupervisor.CubeStateBean→org.squbs.unicomplex.CubeStateMXBean
- Direction
- squbs.unicomplex.CubeSupervisor uses squbs.unicomplex, so a change to squbs.unicomplex can break squbs.unicomplex.CubeSupervisor, while a change to squbs.unicomplex.CubeSupervisor can't break squbs.unicomplex.
- Position
- Below the diagonal: squbs.unicomplex.CubeSupervisor uses a module listed above it, which is the healthy direction.
35→30 squbs.unicomplex.Unicomplex uses squbs.unicomplex✕
- Connections
- 5 pairs of types, where a type in squbs.unicomplex.Unicomplex uses a type in squbs.unicomplex.
- The types involved
org.squbs.unicomplex.Unicomplex.CubesBean→org.squbs.unicomplex.CubeInfoorg.squbs.unicomplex.Unicomplex.CubesBean→org.squbs.unicomplex.CubesMXBeanorg.squbs.unicomplex.Unicomplex.ExtensionsBean→org.squbs.unicomplex.ExtensionInfoorg.squbs.unicomplex.Unicomplex.ExtensionsBean→org.squbs.unicomplex.ExtensionsMXBeanorg.squbs.unicomplex.Unicomplex.SystemStateBean→org.squbs.unicomplex.SystemStateMXBean
- Direction
- squbs.unicomplex.Unicomplex uses squbs.unicomplex, so a change to squbs.unicomplex can break squbs.unicomplex.Unicomplex, while a change to squbs.unicomplex.Unicomplex can't break squbs.unicomplex.
- Position
- Below the diagonal: squbs.unicomplex.Unicomplex uses a module listed above it, which is the healthy direction.
36→32 squbs.actormonitor uses squbs.lifecycle✕
- Connections
- 2 pairs of types, where a type in squbs.actormonitor uses a type in squbs.lifecycle.
- The types involved
org.squbs.actormonitor.ActorMonitor→org.squbs.lifecycle.GracefulStopHelperorg.squbs.actormonitor.ActorMonitorInit→org.squbs.lifecycle.ExtensionLifecycle
- Direction
- squbs.actormonitor uses squbs.lifecycle, so a change to squbs.lifecycle can break squbs.actormonitor, while a change to squbs.actormonitor can't break squbs.lifecycle.
- Position
- Below the diagonal: squbs.actormonitor uses a module listed above it, which is the healthy direction.
37→32 squbs.actorregistry uses squbs.lifecycle✕
- Connections
- 1 pair of types, where a type in squbs.actorregistry uses a type in squbs.lifecycle.
- The types involved
org.squbs.actorregistry.ActorRegistryInit→org.squbs.lifecycle.ExtensionLifecycle
- Direction
- squbs.actorregistry uses squbs.lifecycle, so a change to squbs.lifecycle can break squbs.actorregistry, while a change to squbs.actorregistry can't break squbs.lifecycle.
- Position
- Below the diagonal: squbs.actorregistry uses a module listed above it, which is the healthy direction.
38→30 squbs.stream uses squbs.unicomplex✕
- Connections
- 3 pairs of types, where a type in squbs.stream uses a type in squbs.unicomplex.
- The types involved
org.squbs.stream.FlowToPerpetualStream→org.squbs.unicomplex.AbstractFlowDefinitionorg.squbs.stream.LifecycleEventSource→org.squbs.unicomplex.LifecycleStateorg.squbs.stream.PerpetualStreamBase→org.squbs.unicomplex.LifecycleState
- Direction
- squbs.stream uses squbs.unicomplex, so a change to squbs.unicomplex can break squbs.stream, while a change to squbs.stream can't break squbs.unicomplex.
- Position
- Below the diagonal: squbs.stream uses a module listed above it, which is the healthy direction.
38→32 squbs.stream uses squbs.lifecycle✕
- Connections
- 1 pair of types, where a type in squbs.stream uses a type in squbs.lifecycle.
- The types involved
org.squbs.stream.PerpetualStreamBase→org.squbs.lifecycle.GracefulStopHelper
- Direction
- squbs.stream uses squbs.lifecycle, so a change to squbs.lifecycle can break squbs.stream, while a change to squbs.stream can't break squbs.lifecycle.
- Position
- Below the diagonal: squbs.stream uses a module listed above it, which is the healthy direction.
39→30 squbs.testkit.japi uses squbs.unicomplex✕
- Connections
- 3 pairs of types, where a type in squbs.testkit.japi uses a type in squbs.unicomplex.
- The types involved
org.squbs.testkit.japi.CustomTestKit→org.squbs.unicomplex.UnicomplexBootorg.squbs.testkit.japi.JUnitCustomRouteTestKit→org.squbs.unicomplex.UnicomplexBootorg.squbs.testkit.japi.TestNGCustomRouteTestKit→org.squbs.unicomplex.UnicomplexBoot
- Direction
- squbs.testkit.japi uses squbs.unicomplex, so a change to squbs.unicomplex can break squbs.testkit.japi, while a change to squbs.testkit.japi can't break squbs.unicomplex.
- Position
- Below the diagonal: squbs.testkit.japi uses a module listed above it, which is the healthy direction.
39→33 squbs.testkit.japi uses squbs.testkit✕
- Connections
- 6 pairs of types, where a type in squbs.testkit.japi uses a type in squbs.testkit.
- The types involved
org.squbs.testkit.japi.CustomTestKit→org.squbs.testkit.PortGetterorg.squbs.testkit.japi.JUnitCustomRouteTestKit→org.squbs.testkit.DebugTimingorg.squbs.testkit.japi.JUnitCustomRouteTestKit→org.squbs.testkit.PortGetterorg.squbs.testkit.japi.RouteDefinitionTest→org.squbs.testkit.TestRouteorg.squbs.testkit.japi.TestNGCustomRouteTestKit→org.squbs.testkit.DebugTimingorg.squbs.testkit.japi.TestNGCustomRouteTestKit→org.squbs.testkit.PortGetter
- Direction
- squbs.testkit.japi uses squbs.testkit, so a change to squbs.testkit can break squbs.testkit.japi, while a change to squbs.testkit.japi can't break squbs.testkit.
- Position
- Below the diagonal: squbs.testkit.japi uses a module listed above it, which is the healthy direction.
40→37 squbs.actorregistry.ActorRegistry uses squbs.actorregistry✕
- Connections
- 1 pair of types, where a type in squbs.actorregistry.ActorRegistry uses a type in squbs.actorregistry.
- The types involved
org.squbs.actorregistry.ActorRegistry.ActorRegistryBean→org.squbs.actorregistry.ActorRegistryMXBean
- Direction
- squbs.actorregistry.ActorRegistry uses squbs.actorregistry, so a change to squbs.actorregistry can break squbs.actorregistry.ActorRegistry, while a change to squbs.actorregistry.ActorRegistry can't break squbs.actorregistry.
- Position
- Below the diagonal: squbs.actorregistry.ActorRegistry 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 — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A03:2025 — Software Supply Chain Failures | 10 | High / Critical |
| A05:2025 — Injection | 8 | High / Critical |
| A07:2025 — Authentication Failures | 3 | High / Critical |
Roadmap
Top priorities: Resolve the 1 No ADRs found finding(s) in ADR Quality — start with REDACTED; Resolve the 72 Orphaned file finding(s) in Knowledge Freshness — start with JMX.scala (2), ActorLookup.scala (2), OPromise.scala (2); Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 1 No ADRs found finding(s) in ADR Quality — start with REDACTED. | +11.9 pts | Low | ADR Quality |
| Resolve the 72 Orphaned file finding(s) in Knowledge Freshness — start with JMX.scala (2), ActorLookup.scala (2), OPromise.scala (2). | +11.1 pts | Medium | Knowledge Freshness |
| Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them. | +9.7 pts | Medium | Architecture documentation |
| 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. | +3.1 pts | Medium | Documentation (README) |
| Your ecosystem's static analyzer is declared as a dependency but is not wired into CI — run it as a required step on push/PR (e.g. `composer phpstan` / `mix sobelow` / `bundle exec brakeman` / the spotbugs Gradle task / `sbt scalafixAll --check` / `golangci-lint run` / `rebar3 lint`) so a regression fails the build instead of relying on someone running it locally. | +2.6 pts | Medium | Security & performance tooling |
| Resolve the 3 Most significant orphaned file finding(s) in Knowledge Freshness — start with UnicomplexBoot.scala, Unicomplex.scala, Retry.scala. | +0.9 pts | Low | Knowledge Freshness |
| On Scala 3, add `-Yexplicit-nulls` to `scalacOptions` so `String` and `String | Null` mean different things, and type each Java API's result as nullable where it can return null; on Scala 2 (or as a first step), enable WartRemover's `Null` wart (`wartremoverErrors += Wart.Null`) or Scalafix's `DisableSyntax.noNulls = true` so the code holds absence in `Option`. Then pay the assertions down rather than adding to them: each `.nn` is a null the compiler could not rule out — wrap the Java value in `Option(…)` at the boundary, pattern-match on `null` once there, or change the API so the null cannot arrive; an `unsafeNulls` import switches the checking off for everything after it. | +1.8 pts | Medium | Nullable reference types |
| Nothing pauses a release for a human: publish as a draft release (or gate the release job on a protected tag/manual dispatch) so a bad build can be stopped before users can download it. | +1.6 pts | Medium | Deployment & Rollback |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 2.4 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 3.7 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.1 | Mixed | Dependency Vulnerabilities: High CVE: REDACTED |
| REDACTED | 5.8 | Mixed | Secrets (history): REDACTED: REDACTED |
| REDACTED | 5.8 | Mixed | Dependency Vulnerabilities: High CVE: REDACTED |
| squbs-httpclient/src/test/scala/org/squbs/httpclient/HttpClientSpec.scala | 6.4 | Mixed | Explicit Debt: TodoComment |
| squbs-unicomplex/src/main/scala/org/squbs/unicomplex/Unicomplex.scala | 7.0 | Mixed | Cyclomatic Complexity: Unicomplex.receive (cyclomatic 29) |
| squbs-unicomplex/src/main/scala/org/squbs/unicomplex/ServiceRegistry.scala | 7.3 | Mixed | Explicit Debt: TodoComment |
| squbs-httpclient/src/main/scala/org/squbs/httpclient/HttpClientJMX.scala | 7.3 | Mixed | Explicit Debt: TodoComment |
| squbs-ext/src/main/scala/org/squbs/streams/Retry.scala | 7.8 | Mixed | Cyclomatic Complexity: Retry.createLogic (cyclomatic 33) |
| squbs-pattern/src/main/scala/org/squbs/pattern/orchestration/OFuture.scala | 7.8 | Mixed | Code Duplication: Edited copy of a member (16 corresponding lines) |
| squbs-unicomplex/src/test/scala/org/squbs/unicomplex/UnicomplexTimeoutSpec.scala | 8.2 | Near-clean | Explicit Debt: TodoComment |
| squbs-unicomplex/src/test/scala/org/squbs/unicomplex/dummysvcactor/DummySvcActor.scala | 8.2 | Near-clean | Explicit Debt: TodoComment |
| squbs-unicomplex/src/test/scala/org/squbs/stream/PerpetualStreamMatValueSpec.scala | 8.2 | Near-clean | Explicit Debt: TodoComment |
| squbs-unicomplex/src/main/scala/org/squbs/unicomplex/ServiceRegistryBase.scala | 8.2 | Near-clean | Explicit Debt: TodoComment |
| squbs-pattern/src/main/scala/org/squbs/pattern/timeoutpolicy/TimeoutPolicy.scala | 8.2 | Near-clean | Explicit Debt: TodoComment |
| squbs-pattern/src/main/scala/org/squbs/pattern/stream/QueueSerializer.scala | 8.2 | Near-clean | Explicit Debt: TodoComment |
| squbs-httpclient/src/test/scala/org/squbs/httpclient/ClientFlowPipelineSpec.scala | 8.2 | Near-clean | Explicit Debt: TodoComment |
| squbs-httpclient/src/main/scala/org/squbs/httpclient/ClientFlow.scala | 8.2 | Near-clean | Explicit Debt: TodoComment |
| squbs-ext/src/test/scala/org/squbs/streams/RetrySpec.scala | 8.2 | Near-clean | Explicit Debt: TodoComment |
How the grades work
A definite problem that already costs you something and drags the score down: a missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here tends to cause failures elsewhere.
Likely wrong, but not failing yet. It degrades the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to carry for two years either.
Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.
Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.
Methodology & how to trust this report
This survey is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. All 46 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.8, the weighted average across measured dimensions.
What we checked — 46 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, 135 of 159 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 | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 | ✓ deterministic |
Run transparency — what happened this run
- D8 Code Coverage — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT READ here — but this repository measures it: a coverage step in CI (`sbt ++$SCALA_VERSION coverageReport`) shows that coverage is collected and tracked in your own CI. The built-in collector has no runner for this ecosystem (.scala, .java), so the analyzer could not read the number — a gap in the analyzer's language coverage, not an unmeasured repo. Not scored.
- D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test source is present (.scala, .java) and this repository declares an sbt build (repository root, 166 test files), but it was not re-run: the analyzer environment could not run it. Not scored — this is a gap in the analyzer's language coverage, not a finding about this repository.
- D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. All 75 significant source file(s) were last meaningfully changed so long ago that no living knowledge remains — nothing since has been substantial enough to re-establish ownership (a broad, mechanical sweep that touches many files shallowly does not count, and neither does no activity at all). There is no concentration to measure, so the bus factor is not scored. This is not a clean bill: nobody currently holds working knowledge of this code (see D34 Knowledge Freshness). Counted over 69 of the 123 production source files in this repository: 48 are under the ~2,400-byte size floor this dimension measures over, and the remaining 6 have no attributable history left to measure.
- D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22 identifies the intentionally-exposed surface from `IsPackable` and `.Contracts` project names, MSBuild conventions read off the loaded project set. This target exposed no such projects, so the probe never ran; this says nothing about whether the repository has a public API. This repository commits no C#/VB source at all, so there was never an MSBuild project set to read these conventions off. That is OUR side and it is an ADMISSION gap, not an environment fault: no published-package marker D22 reads admitted any project here. D22 DOES collect the public API of every language in this tree, and admits a project only when its manifest makes that ecosystem's publication act in a form the marker recognises — so what is missing is not a collector but an admission rule for the publication act this repository makes, if it makes one. The remedy is a better discriminator for that marker — not a collector, and no change to the scan image can close it. The marker's rules are measured to refuse applications, so one refused repository is the rule working as calibrated; several are the evidence that it is too strict.
- D24 Comment Value — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
- D27 Navigability — 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. Navigability is taken over call sites whose callee resolved. For C# that population includes calls into referenced assemblies; for this language only calls declared inside the repository count, so the abstention threshold reads the repository's use of its standard library as a resolution failure. That is a limit of this analyzer, not a build problem in this repository.
- D32 Data Compliance (PII/GDPR) — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `squbs-unicomplex/src/main/scala/org/squbs/unicomplex/UnicomplexBoot.scala` 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.
- D44 Platform End-of-Life — 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 dimension reads a project's own statement about the platform it runs on: a TargetFramework in a .NET project file, a .nvmrc or .python-version, a capped requires-python, a Rust toolchain file or Cargo.toml rust-version, a .go-version, .java-version, .ruby-version, .tool-versions or .sdkmanrc, a go.mod go directive, a Maven or Gradle Java level or toolchain, a Gemfile's ruby directive, a mix.exs elixir requirement, a rebar.config minimum_otp_vsn, a pubspec.yaml SDK constraint, a REDACTED scalaVersion, or a framework major pinned by a dependency constraint. This repository carries none of them, so nothing about its platform was established. That is a gap in this analyzer's coverage, NOT a finding that the platform is supported — a language whose runtime is declared elsewhere (Package.swift, a Dockerfile) is simply not read here yet.
- AX1 Captive dependencies — 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 Microsoft.Extensions.DependencyInjection registrations in C# and Spring beans in Java/Kotlin only, and this repository defines its own container in squbs-zkcluster/src/main/scala/org/squbs/cluster/JMX.scala, whose lifetimes are not modelled 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.
- 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.
- P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
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.
- D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
- D13 REDACTED Scanning: REDACTED detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
- D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
- 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.
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
- 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
3 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was Retry.createLogic at 33.
What to do
- Bring the 3 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with Retry.createLogic (cyclomatic 33), Unicomplex.receive (cyclomatic 29), CubeSupervisor.startupReceive (cyclomatic 23). — 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 3 together lifts Cyclomatic Complexity from 8.9 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
D2 · Cognitive Complexity
8 method(s) exceeded the cognitive complexity threshold of 15; the worst was Retry.createLogic at 55.
What to do
- Bring the 2 bodies over 30 down to 30 or less in Cognitive Complexity — start with Retry.createLogic (cognitive 55), Unicomplex.receive (cognitive 32). — 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 2 together lifts Cognitive Complexity from 8.0 to about 8.6/10, projected with the scoring formula itself and assuming each lands exactly at 30; a cleaner split scores higher.
D3 · God Classes
1 over-large unit(s) detected — types, modules or files that carry too much.
What to do
- Resolve the 1 FileTooLong finding(s) in God Classes — start with Unicomplex.scala. — One of this dimension's main actionable groups (1 warning-level).
D4 · Code Duplication
3 duplicated block group(s) detected. 1.5 % of the production lines (189 of 12,983) are in a reported copy. A further 6 rows report members as variants of one another; the share counts each copied line once, however many rows cite it.
What to do
- Resolve the 2 Duplicated block (7 lines × 2) finding(s) in Code Duplication — start with MathUtil.scala, BroadcastBuffer.scala. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 Edited copy of a member (15 corresponding lines) finding(s) in Code Duplication — start with Aggregator.scala. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Edited copy of a member (16 corresponding lines) finding(s) in Code Duplication — start with OFuture.scala. — One of this dimension's main actionable groups (1 warning-level).
D5 · Coupling
10 production modules (sbt), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; a dependsOn spread (deps: _*) and a project whose directory a helper computes are not visible there; 0 module(s) off the main sequence.
D6 · Cohesion (LCOM4)
0 of 31 classes have LCOM4 above 3.
D12 · Dependency Hygiene
11 outdated direct sbt declarations. An sbt declaration names an EXACT version, so the remedy is an edit to the build file — there is no lockfile refresh that would move it. Test-, Provided- and it-scoped declarations are excluded, because a consumer of this project never receives them. A version held in a Scala val is read only when the val is one string literal: sbt is a program rather than a manifest, and evaluating a computed version would invent the measurement rather than take it. Whether any artifact is DEPRECATED or ABANDONED is not graded and cannot be — Maven Central publishes no such marker, and release age does not stand in for one: the most widely depended-upon libraries are routinely the stalest, being finished rather than abandoned. Known CVEs in this dependency graph are D30's question.
D13 · REDACTED Scanning
REDACTED scan ran and found no leaked secrets.
D14 · License Compliance
0 of 11 declared sbt dependency artifact(s) use a banned license. Licences were resolved from the POMs Maven Central publishes, over the production coordinates this repository's 13 sbt build file(s) (REDACTED and project/*.scala) declare with a literal version, directly or through a string-literal val — `%%` resolved to the Scala binary suffix Central publishes under, test-scoped declarations excluded — the same declaration-site closure this analysis reads for dependency currency. sbt has no lockfile a checkout carries, so this is deliberately NOT the transitive closure. 21 further production coordinate(s) are declared with a version the build computes rather than writes as a literal — sbt is a program, and this pass does not run it — and are NOT graded: this verdict covers what the build pins literally or through a string-literal val, not the full graph.
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window.
D17 · Explicit Debt
21 deducted task-comment markers across 12983 LoC (0.1/KLoC) → score 9.7. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
What to do
- Resolve the 21 TodoComment finding(s) in Explicit Debt — start with HttpClientSpec.scala (7), ServiceRegistry.scala (2), HttpClientJMX.scala (2). — One of this dimension's main actionable groups (21 warning-level).
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).
D26 · Project Cohesion
0 of 11 build units (sbt) flagged as possibly oversized/incoherent.
D28 · Secrets (history)
2 finding(s): 0 critical, 2 high, 0 medium, 0 low. Remediation for historically-committed secrets is credential rotation — they remain in history regardless of later deletion.
What to do
- Resolve the 2 REDACTED finding(s) in Secrets (history) — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
- Resolve the 1 Rotate the exposed credentials finding(s) in Secrets (history). — One of this dimension's main actionable groups (1 recommendation-level).
D29 · Static Analysis (SAST)
8 finding(s): 0 critical, 8 high, 0 medium, 0 low. 5 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. semgrep hit a parse error in 1 file(s) — `squbs-unicomplex/src/main/scala/org/squbs/unicomplex/UnicomplexBoot.scala` — so no absence of findings in them is evidence of anything, and nothing in them was analysed. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them.
What to do
- Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2). — One of this dimension's main actionable groups (2 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 5 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 (5 issue-level, 0 of them charged here).
D30 · Dependency Vulnerabilities
4 finding(s): 0 critical, 3 high, 1 medium, 0 low.
What to do
- Resolve the 3 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (3). — One of this dimension's main actionable groups (3 issue-level).
- Resolve the 1 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
D34 · Knowledge Freshness
75 of 75 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is squbs-unicomplex/src/main/scala/org/squbs/unicomplex/UnicomplexBoot.scala. Counted over 75 of the 123 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
What to do
- Resolve the 72 Orphaned file finding(s) in Knowledge Freshness — start with JMX.scala (2), ActorLookup.scala (2), OPromise.scala (2). — One of this dimension's main actionable groups (72 recommendation-level).
- Resolve the 3 Most significant orphaned file finding(s) in Knowledge Freshness — start with UnicomplexBoot.scala, Unicomplex.scala, Retry.scala. — One of this dimension's main actionable groups (3 recommendation-level).
- Resolve the 1 Dormant codebase finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
D35 · Change Coupling
No strong hidden change-coupling between production files.
D36 · Supply-chain Provenance & Signing
1/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).
What to do
- 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).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
Frontend & cross-cutting dimensions
AX10 · Code composition
AX2 · Stateful singletons
AX3 · Project dependency cycles
AX4 · Dependency direction
AX6 · Interface segregation
- `HttpClientConfigMXBean` declares 48 abstract members: `getName`, `getEndpointUri`, `getEndpointPort`, `getEnvironment`, `getPipeline`, `getDefaultPipeline`, `getCircuitBreakerStateName`, `getMaxConnections`, `getMinConnections`, `getMaxRetries`, `getMaxOpenRequests`, `getPipeliningLimit`, `getConnectionPoolIdleTimeout`, `getUserAgentHeader`, `getConnectingTimeout`, `getConnectionIdleTimeout`, `getRequestHeaderSizeHint`, `getSoReceiveBufferSize`, `getSoSendBufferSize`, `getSoReuseAddress`, `getSoTrafficClass`, `getTcpKeepAlive`, `getTcpOobInline`, `getTcpNoDelay`, `getMaxUriLength`, `getMaxMethodLength`, `getMaxResponseReasonLength`, `getMaxHeaderNameLength`, `getMaxHeaderValueLength`, `getMaxHeaderCount`, `getMaxContentLength`, `getMaxChunkExtLength`, `getMaxChunkSize`, `getUriParsingMode`, `getCookieParsingMode`, `getIllegalHeaderWarnings`, `getErrorLoggingVerbosity`, `getIllegalResponseHeaderValueProcessingMode`, `getHeaderCacheDefault`, `getHeaderCacheContentMD5`, and 8 more. Counted over its ABSTRACT members — a `def` with no body or a `val`/`var` with no initializer, once per signature; concrete members, private and protected members, and members of a companion `object` are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — squbs-httpclient/src/main/scala/org/squbs/httpclient/HttpClientJMX.scala:25
What to do
- Split fat interfaces into focused role-interfaces so clients depend only on what they use.
GD1 · Unfinished & placeholder code
IC1 · Incompleteness & stubs
M1 · Documentation (README)
What to do
- Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
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.
- No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.
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.
- Add a C4 context/container diagram (Structurizr, PlantUML or Mermaid) or an architecture.md overview.
M3 · Folder & project structure
P1 · CI/CD gates
P10 · Library API & versioning
P2 · Observability
- Only 7/10 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `squbs-admin`, `squbs-pipeline`, `squbs-testkit`.
What to do
- Extend structured logging to the remaining runnable modules so everything you run is diagnosable in production.
- Add a health-check endpoint (Spring Boot Actuator's /actuator/health, or a /health route) so orchestrators and load balancers can probe liveness/readiness.
P3 · Security & performance tooling
What to do
- Your ecosystem's static analyzer is declared as a dependency but is not wired into CI — run it as a required step on push/PR (e.g. `composer phpstan` / `mix sobelow` / `bundle exec brakeman` / the spotbugs Gradle task / `sbt scalafixAll --check` / `golangci-lint run` / `rebar3 lint`) so a regression fails the build instead of relying on someone running it locally.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
- The release is automated and no gate that pauses it for a human is DECLARED IN THIS REPOSITORY'S PIPELINE FILES. What was read: every file under `.github/workflows/`, `.forgejo/workflows/`, `.gitea/workflows/`, `.azuredevops/` and `.azure-pipelines/`, plus `.gitlab-ci*` and `azure-pipelines*` — with comment text stripped, so documenting a gate is not declaring one. What would have counted: GitLab's `when: manual`, CircleCI's `type: approval`, an Azure `ManualValidation@` task or an `approvals:` block, a Jenkins `input` step, a `uses:` step naming an approval action, an `environment:` paired with `reviewers` / `required_reviewers` / `protection` / `wait-timer` / `deployment_branch_policy`, a draft-release step, a `workflow_dispatch` promotion, or a release-event gate. ★ What this cannot see, because none of it is a file: a GitHub environment whose required reviewers are configured in repo SETTINGS, a branch protection rule, or an organisation deployment policy — all of them real, enforced gates that live outside the repository. If yours is one of those, this row is wrong and nothing in the tree could have told us. Otherwise: whatever the release trigger points at is published to users unreviewed, so a mistagged or unverified commit ships and the only remedy is a follow-up release.
What to do
- Nothing pauses a release for a human: publish as a draft release (or gate the release job on a protected tag/manual dispatch) so a bad build can be stopped before users can download it.
P6 · Release Hygiene
- No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
What to do
- Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.
PF3 · Async & latency hygiene
S1 · Web-Security Posture
- None of the 11 security response headers the OWASP Secure Headers Project recommends (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options, …) is set on a response this repository's Scala server sends — defense in depth, even when a proxy could set them. (−2.0 on this card.) The server: squbs-unicomplex/src/main/scala/org/squbs/unicomplex/ServiceRegistry.scala:96 — `newServerAt`.
What to do
- Set security response headers on what the server sends — keep Play's `SecurityHeadersFilter` enabled, wrap akka/pekko-http routes in `respondWithHeaders(RawHeader("X-Content-Type-Options", "nosniff"), …)`, or add an http4s middleware that sets `Content-Security-Policy`, `X-Content-Type-Options` and a frame policy on every response.
X1 · Async correctness
X12 · Unreachable branch
X18 · Disposal-pattern correctness
X21 · Side-effecting pattern guard
X23 · Unguarded diagnostic materialisation
X27 · Collection changed while being enumerated
X3 · Exception handling
X5 · Nullable reference types
- No build over this repository's 101 Scala product file(s) passes `-Yexplicit-nulls`, enables WartRemover's `Null` wart or runs Scalafix's `DisableSyntax.noNulls`, so every reference type admits null and nothing reports a `null` written into the code or returned from a Java API — the first one to reach a method call is a `NullPointerException`. `Option` by convention is a habit no tool here holds the code to.
What to do
- On Scala 3, add `-Yexplicit-nulls` to `scalacOptions` so `String` and `String | Null` mean different things, and type each Java API's result as nullable where it can return null; on Scala 2 (or as a first step), enable WartRemover's `Null` wart (`wartremoverErrors += Wart.Null`) or Scalafix's `DisableSyntax.noNulls = true` so the code holds absence in `Option`. Then pay the assertions down rather than adding to them: each `.nn` is a null the compiler could not rule out — wrap the Java value in `Option(…)` at the boundary, pattern-match on `null` once there, or change the API so the null cannot arrive; an `unsafeNulls` import switches the checking off for everything after it.
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 73% | Adequate — gated by X5 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 100% | Exemplary | Solid. |
| Maturity | 43% | Weak — gated by D34, M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 57% | Adequate — gated by P3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 66% | Adequate — gated by D36 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Performance | 100% | Exemplary | Strongest area. |
Not evidenced — 1 control(s) we could not find positive evidence for
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 69 check(s) not relevant to this codebase
- AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
- AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
- AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
- AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
- AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
- AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
- AX1 Captive dependencies — 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
- 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
- AXB1 Runtime evidence locked — no reproducible boot — This repository has nothing the runtime tiers could boot or serve — no markup, no UI framework or web-server dependency, no UI component source, no native UI project and no API definition — nothing here is a surface to boot — so runtime a11y/egress/header evidence has no subject here. Not applicable: this is neither a gap in the scan nor a finding about your code.
- 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.
- C3 Audit Trail — No personal data detected in a persisted data model — no PII-named column (email, first_name, date_of_birth, phone_number, …) or stored credential on a Slick table or in a SQL migration's CREATE TABLE or ALTER TABLE — and no database client (Slick, Doobie, Quill, ScalikeJDBC, Anorm, Skunk, a MongoDB or Cassandra driver, JDBC) imported either, so this repository keeps no sensitive data whose changes an audit trail would record. If it does (through a store configured outside this repository, for instance), the trail belongs to wherever that data is stored.
- C4 Data Retention — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a Slick table or in a SQL migration's CREATE TABLE or ALTER TABLE — and no database or data-store client (Slick, Doobie, Quill, ScalikeJDBC, Anorm, Skunk, JDBC, MongoDB, Cassandra, …) imported either, so this repository keeps no personal data whose lifetime a retention limit would bound.
- C5 Data-Subject Rights — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a Slick table or in a SQL migration's CREATE TABLE or ALTER TABLE — and no database or data-store client (Slick, Doobie, Quill, ScalikeJDBC, Anorm, Skunk, JDBC, MongoDB, Cassandra, …) imported either, so this repository keeps no personal data for a data subject to erase, export or consent over.
- D10 Test Quality — ~25857 lines of test source are present (.scala, .java) but no test cases reached the test census for this repository — no test root we could resolve declared them, or the files we read declare no cases in a test framework we recognise — so skipped/assertion-free tests couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
- D11 Test Reliability — Test reliability not included — the .scala suite was found but not re-run
- D16 Bus Factor — dormant codebase — no living knowledge left to concentrate
- 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.
- D19 Documentation Quality — No runnable or published unit to look for an example in, and no multi-project root README to look for a map in; the other documentation kinds are withheld (see the gaps), so documentation quality is not applicable here.
- D21 Naming Consistency — N/A — too few peers to establish a naming convention (2739 declarations, no unit with a dominant convention).
- D22 Internal API Consistency — The exposed public-API surface could not be collected — no C#/VB projects loaded.
- D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D24 Comment Value — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only — this repository's production source is .java, .scala, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D25 ADR Conformance — no ADRs to check
- D27 Navigability — D27 counts a call into the standard library or a dependency as unresolved for this repository's language (.scala), so too few call sites counted as resolved to assess navigability. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
- D32 Data Compliance (PII/GDPR) — 1 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- 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.
- D44 Platform End-of-Life — Platform end-of-life not assessed — this repository declares no platform this pass reads
- D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
- D8 Code Coverage — Coverage not included — suite not readable by the collector
- DM1 Domain Modelling — applicable but not scored (2 signals for this style, 2 needed — the count is met but a required primary signal is absent): 137 value object(s); 1 domain event(s); its domain events are published by services or handlers — no domain entity raises one
- ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
- ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- M4 Documentation accuracy — Not applicable: the 35 current-state document(s) make no claim of a kind M4 checks. 2 claim(s) of kinds M4 does not check were not checked (path 2); M4 checks only links and versions and artefact counts.
- P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
- P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the JVM source, so there is no service whose uptime a failing dependency could take down
- 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 pom.xml, Gradle or sbt build, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
- PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
- X10 Duplicated predicate — 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
- X16 Unfloored truncation loop — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X17 Uncapped recursion over a caller-supplied document — 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
- X2 Cancellation propagation — no C# was loaded; this repository's Scala and Java were read, and no request in it can be cancelled by a caller — a Scala request takes no token: a Future cannot be cancelled, and cats-effect, ZIO and Monix interrupt the fiber that made the request from outside the call, not through a parameter; a Java request off Android takes no token: it is cancelled through the handle it returns (Future.cancel, Call.cancel, a Disposable), ambiently (io.grpc.Context) or by interrupting its thread, not through a parameter
- 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
- X24 Document value interpolated into markup unescaped — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X25 Inert configuration knob — 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
- 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
- X29 Per-element action decided by a fixed element — 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.
- X4 Structured logging — This check asks whether log calls keep a message's values apart from its text, which needs a logger that can carry them as fields. This repository's Java was read, and it logs through none that an assembled message defeats: java.util.logging's level methods, log4j 1, commons-logging, JBoss Logging and Flogger take one finished message (as log4net does in C#), or it makes no call through a named logger at all. Calls made through SLF4J or log4j 2 (`org.slf4j.Logger`, `org.apache.logging.log4j.Logger`, Lombok's `@Slf4j`) would be judged.
- 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 — 13 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
Serious — 47 finding(s)
- TodoComment squbs-unicomplex/src/test/scala/org/squbs/unicomplex/UnicomplexTimeoutSpec.scala:76
- TodoComment squbs-unicomplex/src/test/scala/org/squbs/unicomplex/dummysvcactor/DummySvcActor.scala:65
- TodoComment squbs-unicomplex/src/test/scala/org/squbs/stream/PerpetualStreamMatValueSpec.scala:175
- TodoComment squbs-unicomplex/src/main/scala/org/squbs/unicomplex/ServiceRegistry.scala:161
- TodoComment squbs-unicomplex/src/main/scala/org/squbs/unicomplex/ServiceRegistry.scala:163
- TodoComment squbs-unicomplex/src/main/scala/org/squbs/unicomplex/ServiceRegistryBase.scala:180
- TodoComment squbs-pattern/src/main/scala/org/squbs/pattern/timeoutpolicy/TimeoutPolicy.scala:69
- TodoComment squbs-pattern/src/main/scala/org/squbs/pattern/stream/QueueSerializer.scala:79
- TodoComment squbs-httpclient/src/test/scala/org/squbs/httpclient/ClientFlowPipelineSpec.scala:152
- TodoComment squbs-httpclient/src/test/scala/org/squbs/httpclient/HttpClientSpec.scala:156
- TodoComment squbs-httpclient/src/test/scala/org/squbs/httpclient/HttpClientSpec.scala:209
- TodoComment squbs-httpclient/src/test/scala/org/squbs/httpclient/HttpClientSpec.scala:225
- TodoComment squbs-httpclient/src/test/scala/org/squbs/httpclient/HttpClientSpec.scala:241
- TodoComment squbs-httpclient/src/test/scala/org/squbs/httpclient/HttpClientSpec.scala:248
- TodoComment squbs-httpclient/src/test/scala/org/squbs/httpclient/HttpClientSpec.scala:427
- TodoComment squbs-httpclient/src/test/scala/org/squbs/httpclient/HttpClientSpec.scala:495
- TodoComment squbs-httpclient/src/main/scala/org/squbs/httpclient/ClientFlow.scala:276
- TodoComment squbs-httpclient/src/main/scala/org/squbs/httpclient/HttpClientJMX.scala:76
- TodoComment squbs-httpclient/src/main/scala/org/squbs/httpclient/HttpClientJMX.scala:79
- TodoComment squbs-ext/src/test/scala/org/squbs/streams/RetrySpec.scala:469
- TodoComment squbs-ext/src/main/scala/org/squbs/marshallers/json/ReflectHelper.scala:23
- REDACTED
- REDACTED
- Duplicated block (7 lines × 2) squbs-pattern/src/main/scala/org/squbs/pattern/timeoutpolicy/MathUtil.scala:32
- Duplicated block (7 lines × 2) squbs-pattern/src/main/scala/org/squbs/pattern/stream/BroadcastBuffer.scala:100
- Retry.createLogic (cyclomatic 33) squbs-ext/src/main/scala/org/squbs/streams/Retry.scala:166
- Unicomplex.receive (cyclomatic 29) squbs-unicomplex/src/main/scala/org/squbs/unicomplex/Unicomplex.scala:401
- CubeSupervisor.startupReceive (cyclomatic 23) squbs-unicomplex/src/main/scala/org/squbs/unicomplex/Unicomplex.scala:659
- Retry.createLogic (cognitive 55) squbs-ext/src/main/scala/org/squbs/streams/Retry.scala:166
- Unicomplex.receive (cognitive 32) squbs-unicomplex/src/main/scala/org/squbs/unicomplex/Unicomplex.scala:401
- CubeSupervisor.startupReceive (cognitive 25) squbs-unicomplex/src/main/scala/org/squbs/unicomplex/Unicomplex.scala:659
- CircuitBreaker.createLogic (cognitive 23) squbs-ext/src/main/scala/org/squbs/streams/circuitbreaker/CircuitBreaker.scala:95
- Unicomplex.stopAndStartCube (cognitive 23) squbs-unicomplex/src/main/scala/org/squbs/unicomplex/Unicomplex.scala:336
- CubeSupervisor.receive (cognitive 20) squbs-unicomplex/src/main/scala/org/squbs/unicomplex/Unicomplex.scala:737
- LoadActor.runLoad (cognitive 19) squbs-testkit/src/main/scala/org/squbs/testkit/stress/LoadActor.scala:47
- TriggerMerge.createLogic (cognitive 19) squbs-unicomplex/src/main/scala/org/squbs/stream/TriggerMerge.scala:40
- FileTooLong: unicomplex/Unicomplex.scala squbs-unicomplex/src/main/scala/org/squbs/unicomplex/Unicomplex.scala
- REDACTED
- REDACTED
- REDACTED
- Edited copy of a member (15 corresponding lines) squbs-pattern/src/main/scala/org/squbs/pattern/orchestration/Aggregator.scala:157
- Edited copy of a member (16 corresponding lines) squbs-pattern/src/main/scala/org/squbs/pattern/orchestration/OFuture.scala:309
- Edited copy of a member (13 corresponding lines) squbs-ext/src/main/scala/org/squbs/marshallers/json/XLangJsonSupport.scala:192
- Edited copy of a member (17 corresponding lines) squbs-pattern/src/main/scala/org/squbs/pattern/orchestration/OFuture.scala:225
- Edited copy of a member (7 corresponding lines) squbs-ext/src/main/scala/org/squbs/env/Environment.scala:107
- Edited copy of a member (4 corresponding lines) squbs-unicomplex/src/main/scala/org/squbs/stream/LifecycleEventSource.scala:101
- Duplicated block (20 lines × 2) squbs-testkit/src/main/scala/org/squbs/testkit/japi/JUnitCustomRouteTestKit.scala:37
Minor — 88 finding(s)
- Orphaned file squbs-pattern/src/main/scala/org/squbs/pattern/orchestration/OFuture.scala:1
- Orphaned file squbs-zkcluster/src/main/scala/org/squbs/cluster/ZkClusterActor.scala:1
- Orphaned file squbs-ext/src/main/scala/org/squbs/streams/Timeout.scala:1
- Orphaned file squbs-httpclient/src/main/scala/org/squbs/httpclient/ClientFlow.scala:1
- Orphaned file squbs-ext/src/main/scala/org/squbs/streams/circuitbreaker/impl/AtomicCircuitBreakerState.scala:1
- Orphaned file squbs-unicomplex/src/main/scala/org/squbs/unicomplex/ServiceRegistry.scala:1
- Orphaned file squbs-ext/src/main/scala/org/squbs/streams/circuitbreaker/CircuitBreaker.scala:1
- Orphaned file squbs-pattern/src/main/scala/org/squbs/pattern/timeoutpolicy/TimeoutPolicy.scala:1
- Orphaned file squbs-zkcluster/src/main/scala/org/squbs/cluster/ZkPartitionsManager.scala:1
- Orphaned file squbs-httpclient/src/main/scala/org/squbs/httpclient/HttpClientJMX.scala:1
- Orphaned file squbs-ext/src/main/scala/org/squbs/streams/circuitbreaker/CircuitBreakerState.scala:1
- Orphaned file squbs-unicomplex/src/main/scala/org/squbs/unicomplex/JMX.scala:1
- Orphaned file squbs-zkcluster/src/main/scala/org/squbs/cluster/ZkCluster.scala:1
- Orphaned file squbs-ext/src/main/scala/org/squbs/streams/BoundedOrdering.scala:1
- Orphaned file squbs-pattern/src/main/scala/org/squbs/pattern/stream/PersistentQueue.scala:1
- Orphaned file squbs-ext/src/main/scala/org/squbs/marshallers/json/XLangJsonSupport.scala:1
- Orphaned file squbs-zkcluster/src/main/scala/org/squbs/cluster/rebalance/DataCenterAwareness.scala:1
- Orphaned file squbs-ext/src/main/scala/org/squbs/util/ConfigUtil.scala:1
- Orphaned file squbs-ext/src/main/scala/org/squbs/resolver/Resolver.scala:1
- Orphaned file squbs-zkcluster/src/main/scala/org/squbs/cluster/ZkMessages.scala:1
- Orphaned file squbs-testkit/src/main/scala/org/squbs/testkit/CustomTestKit.scala:1
- Orphaned file squbs-actorregistry/src/main/scala/org/squbs/actorregistry/ActorLookup.scala:1
- Orphaned file squbs-pattern/src/main/scala/org/squbs/pattern/orchestration/Aggregator.scala:1
- Orphaned file squbs-unicomplex/src/main/scala/org/squbs/unicomplex/ServiceRegistryBase.scala:1
- Orphaned file squbs-unicomplex/src/main/scala/org/squbs/lifecycle/GracefulStopHelper.scala:1
- Most significant orphaned file squbs-unicomplex/src/main/scala/org/squbs/unicomplex/UnicomplexBoot.scala:1
- Most significant orphaned file squbs-unicomplex/src/main/scala/org/squbs/unicomplex/Unicomplex.scala:1
- Most significant orphaned file squbs-ext/src/main/scala/org/squbs/streams/Retry.scala:1
- Fat interface: HttpClientConfigMXBean (48 abstract members) squbs-httpclient/src/main/scala/org/squbs/httpclient/HttpClientJMX.scala:25
- No ADRs found squbs-admin/build.sbt:26
- REDACTED
- Dormant codebase
- REDACTED
- REDACTED
- No ADRs
- No architecture diagram/doc
- Logging is not universal
- No release approval gate
- No changelog
- No security response headers detected
- Scala's null is not held to the type system everywhere
Minor — 11 finding(s)
- Outdated: com.fasterxml.jackson.core:jackson-core
- Outdated: com.fasterxml.jackson.core:jackson-databind
- Outdated: com.fasterxml.jackson.module:jackson-module-parameter-names
- Outdated: io.dropwizard.metrics:metrics-core
- Outdated: io.dropwizard.metrics:metrics-jmx
- Outdated: junit:junit
- Outdated: net.openhft:chronicle-queue
- Outdated: org.apache.curator:curator-framework
- Outdated: org.apache.curator:curator-recipes
- Outdated: org.slf4j:slf4j-api
- Outdated: org.testng:testng
Appendix B — Reproduction & audit trail
| Dimension | Tool | Version | Command | Findings | Raw output |
|---|---|---|---|---|---|
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-d2642d47282b444db14270455e415418/history.json --exit-code 0 --source . | 2 | artifacts/raw/gitleaks-history.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-d2642d47282b444db14270455e415418/tree.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-tree.json |
| D29 · Static Analysis (SAST) | semgrep | — | semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/canine-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt . | 8 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . /tmp/codehealth-osv-sbom-f9778cba13384e80b2508503cc15b933 | 4 | artifacts/raw/osv-scanner.json |
| D31 · IaC & Container Security | trivy | — | trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan. | 0 | — |
| 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) — `squbs-unicomplex/src/main/scala/org/squbs/unicomplex/UnicomplexBoot.scala` — so the PII/GDPR sweep did not cover them at all. | 0 | — |
| D37 · Vulnerability-disclosure Policy | disclosure | — | disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . /tmp/codehealth-osv-sbom-f9778cba13384e80b2508503cc15b933 | 0 | artifacts/raw/osv-scanner.json |