Executive summary
endless4s/endless falls short of our standard for production because it has pipeline tools referenced by a changeable name. It scores 66 out of 100 and is rated Adequate, and all 16 of its critical findings are security problems in the build pipeline.
Security and Compliance, at 58, is the weakest lens and counts most in the score. The best first step is recording design decisions, worth about 6 points. Stopping the four pipeline steps that hand secrets to unpinned tools would lift Security and Compliance itself, worth about 3 points. Raising Security and Compliance to 70 would lift the score to about 70.
Twelve pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Four secrets can leak from the build pipeline. Pinning each tool to an exact version and limiting each secret to its own step would close both risks.
The product code is 4,490 lines, about €7,400 to rebuild.
If Security and Compliance rose from 58 to 70, the lowest score rated Strong, the score would rise from 66 to about 70.
Rebuild cost: about €7,400 · Estimate
| Cost to rebuild | €2,400 to €12,000, for 41 to 129 hours of work, under 0.1 person-years for one engineer |
|---|---|
| Difficulty of the problem | Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.9 at a score of 66. 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: 4,490 lines of product code |
| What it is not | Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one. |
Top priorities
Diagnosis: what the measurements show together
Architecture — module dependency graph
Architecture: which parts of the code depend on which
| uses → | 1 (global) | 2 endless.circe.CirceDecoder | 3 endless.core | 4 endless.core.entity.Effector | 5 endless.core.entity.SideEffect | 6 endless.core.event | 7 endless.core.interpret.DurableEntityT | 8 endless.core.protocol | 9 endless.runtime.akka.data | 10 endless.runtime.akka.deploy.internal.EventSourcedShardedRepositoryDeployer | 11 endless.runtime.akka.protobuf | 12 endless.runtime.akka.serializer | 13 endless.runtime.pekko.data | 14 endless.runtime.pekko.deploy.internal.EventSourcedShardedEntityDeployer | 15 endless.runtime.pekko.protobuf | 16 endless.runtime.pekko.serializer | 17 endless.circe | 18 endless.core.data | 19 endless.core.entity.Effector.PassivationState | 20 endless.core.entity.SideEffect.RunMode | 21 endless.core.entity.SideEffect.Trigger | 22 endless.core.interpret.DurableEntityT.State | 23 endless.protobuf | 24 endless.runtime.akka | 25 endless.runtime.akka.deploy.AkkaDurableDeployer | 26 endless.runtime.pekko | 27 endless.runtime.pekko.deploy.PekkoDeployer | 28 endless.runtime.pekko.deploy.PekkoDurableDeployer | 29 endless.core.interpret | 30 endless.core.entity | 31 endless.runtime.akka.deploy | 32 endless.runtime.pekko.deploy | 33 endless.runtime.akka.deploy.AkkaDeployer | 34 endless.runtime.akka.deploy.internal | 35 endless.runtime.akka.syntax | 36 endless.runtime.pekko.deploy.internal | 37 endless.runtime.pekko.syntax |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 (global) | |||||||||||||||||||||||||||||||||||||
| 2 endless.circe.CirceDecoder | |||||||||||||||||||||||||||||||||||||
| 3 endless.core | |||||||||||||||||||||||||||||||||||||
| 4 endless.core.entity.Effector | |||||||||||||||||||||||||||||||||||||
| 5 endless.core.entity.SideEffect | |||||||||||||||||||||||||||||||||||||
| 6 endless.core.event | |||||||||||||||||||||||||||||||||||||
| 7 endless.core.interpret.DurableEntityT | |||||||||||||||||||||||||||||||||||||
| 8 endless.core.protocol | |||||||||||||||||||||||||||||||||||||
| 9 endless.runtime.akka.data | |||||||||||||||||||||||||||||||||||||
| 10 endless.runtime.akka.deploy.internal.EventSourcedShardedRepositoryDeployer | |||||||||||||||||||||||||||||||||||||
| 11 endless.runtime.akka.protobuf | |||||||||||||||||||||||||||||||||||||
| 12 endless.runtime.akka.serializer | |||||||||||||||||||||||||||||||||||||
| 13 endless.runtime.pekko.data | |||||||||||||||||||||||||||||||||||||
| 14 endless.runtime.pekko.deploy.internal.EventSourcedShardedEntityDeployer | |||||||||||||||||||||||||||||||||||||
| 15 endless.runtime.pekko.protobuf | |||||||||||||||||||||||||||||||||||||
| 16 endless.runtime.pekko.serializer | |||||||||||||||||||||||||||||||||||||
| 17 endless.circe | 8 | ||||||||||||||||||||||||||||||||||||
| 18 endless.core.data | 1 | ||||||||||||||||||||||||||||||||||||
| 19 endless.core.entity.Effector.PassivationState | 3 | ||||||||||||||||||||||||||||||||||||
| 20 endless.core.entity.SideEffect.RunMode | 2 | ||||||||||||||||||||||||||||||||||||
| 21 endless.core.entity.SideEffect.Trigger | 3 | ||||||||||||||||||||||||||||||||||||
| 22 endless.core.interpret.DurableEntityT.State | 3 | ||||||||||||||||||||||||||||||||||||
| 23 endless.protobuf | 9 | ||||||||||||||||||||||||||||||||||||
| 24 endless.runtime.akka | 1 | 2 | |||||||||||||||||||||||||||||||||||
| 25 endless.runtime.akka.deploy.AkkaDurableDeployer | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 26 endless.runtime.pekko | 1 | 2 | |||||||||||||||||||||||||||||||||||
| 27 endless.runtime.pekko.deploy.PekkoDeployer | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 28 endless.runtime.pekko.deploy.PekkoDurableDeployer | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 29 endless.core.interpret | 1 | 2 | 6 | ||||||||||||||||||||||||||||||||||
| 30 endless.core.entity | 1 | 2 | 2 | 6 | |||||||||||||||||||||||||||||||||
| 31 endless.runtime.akka.deploy | 1 | 2 | 2 | 6 | 4 | ||||||||||||||||||||||||||||||||
| 32 endless.runtime.pekko.deploy | 1 | 2 | 2 | 2 | 6 | 4 | |||||||||||||||||||||||||||||||
| 33 endless.runtime.akka.deploy.AkkaDeployer | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 34 endless.runtime.akka.deploy.internal | 2 | 3 | 2 | 1 | 5 | 1 | |||||||||||||||||||||||||||||||
| 35 endless.runtime.akka.syntax | 2 | ||||||||||||||||||||||||||||||||||||
| 36 endless.runtime.pekko.deploy.internal | 2 | 3 | 2 | 1 | 5 | 1 | |||||||||||||||||||||||||||||||
| 37 endless.runtime.pekko.syntax | 2 |
17→8 endless.circe uses endless.core.protocol✕
- Connections
- 8 pairs of types, where a type in endless.circe uses a type in endless.core.protocol.
- The types involved
endless.circe.CirceCommandProtocol→endless.core.protocol.CommandProtocolendless.circe.CirceCommandProtocol→endless.core.protocol.CommandSenderendless.circe.CirceCommandProtocol→endless.core.protocol.IncomingCommandendless.circe.CirceDecoder→endless.core.protocol.Decoderendless.circe.CirceEncoder→endless.core.protocol.Encoderendless.circe.CirceIncomingCommand→endless.core.protocol.IncomingCommandendless.circe.CirceOutgoingCommand→endless.core.protocol.Decoderendless.circe.CirceOutgoingCommand→endless.core.protocol.OutgoingCommand
- Direction
- endless.circe uses endless.core.protocol, so a change to endless.core.protocol can break endless.circe, while a change to endless.circe can't break endless.core.protocol.
- Position
- Below the diagonal: endless.circe uses a module listed above it, which is the healthy direction.
18→6 endless.core.data uses endless.core.event✕
- Connections
- 1 pair of types, where a type in endless.core.data uses a type in endless.core.event.
- The types involved
endless.core.data.EventsFolder→endless.core.event.EventApplier
- Direction
- endless.core.data uses endless.core.event, so a change to endless.core.event can break endless.core.data, while a change to endless.core.data can't break endless.core.event.
- Position
- Below the diagonal: endless.core.data uses a module listed above it, which is the healthy direction.
19→4 endless.core.entity.Effector.PassivationState uses endless.core.entity.Effector✕
- Connections
- 3 pairs of types, where a type in endless.core.entity.Effector.PassivationState uses a type in endless.core.entity.Effector.
- The types involved
endless.core.entity.Effector.PassivationState.After→endless.core.entity.Effector.PassivationStateendless.core.entity.Effector.PassivationState.Disabled→endless.core.entity.Effector.PassivationStateendless.core.entity.Effector.PassivationState.Unchanged→endless.core.entity.Effector.PassivationState
- Direction
- endless.core.entity.Effector.PassivationState uses endless.core.entity.Effector, so a change to endless.core.entity.Effector can break endless.core.entity.Effector.PassivationState, while a change to endless.core.entity.Effector.PassivationState can't break endless.core.entity.Effector.
- Position
- Below the diagonal: endless.core.entity.Effector.PassivationState uses a module listed above it, which is the healthy direction.
20→5 endless.core.entity.SideEffect.RunMode uses endless.core.entity.SideEffect✕
- Connections
- 2 pairs of types, where a type in endless.core.entity.SideEffect.RunMode uses a type in endless.core.entity.SideEffect.
- The types involved
endless.core.entity.SideEffect.RunMode.Async→endless.core.entity.SideEffect.RunModeendless.core.entity.SideEffect.RunMode.Sync→endless.core.entity.SideEffect.RunMode
- Direction
- endless.core.entity.SideEffect.RunMode uses endless.core.entity.SideEffect, so a change to endless.core.entity.SideEffect can break endless.core.entity.SideEffect.RunMode, while a change to endless.core.entity.SideEffect.RunMode can't break endless.core.entity.SideEffect.
- Position
- Below the diagonal: endless.core.entity.SideEffect.RunMode uses a module listed above it, which is the healthy direction.
21→5 endless.core.entity.SideEffect.Trigger uses endless.core.entity.SideEffect✕
- Connections
- 3 pairs of types, where a type in endless.core.entity.SideEffect.Trigger uses a type in endless.core.entity.SideEffect.
- The types involved
endless.core.entity.SideEffect.Trigger.AfterPersistence→endless.core.entity.SideEffect.Triggerendless.core.entity.SideEffect.Trigger.AfterRead→endless.core.entity.SideEffect.Triggerendless.core.entity.SideEffect.Trigger.AfterRecovery→endless.core.entity.SideEffect.Trigger
- Direction
- endless.core.entity.SideEffect.Trigger uses endless.core.entity.SideEffect, so a change to endless.core.entity.SideEffect can break endless.core.entity.SideEffect.Trigger, while a change to endless.core.entity.SideEffect.Trigger can't break endless.core.entity.SideEffect.
- Position
- Below the diagonal: endless.core.entity.SideEffect.Trigger uses a module listed above it, which is the healthy direction.
22→7 endless.core.interpret.DurableEntityT.State uses endless.core.interpret.DurableEntityT✕
- Connections
- 3 pairs of types, where a type in endless.core.interpret.DurableEntityT.State uses a type in endless.core.interpret.DurableEntityT.
- The types involved
endless.core.interpret.DurableEntityT.State.Existing→endless.core.interpret.DurableEntityT.Stateendless.core.interpret.DurableEntityT.State.None→endless.core.interpret.DurableEntityT.Stateendless.core.interpret.DurableEntityT.State.Updated→endless.core.interpret.DurableEntityT.State
- Direction
- endless.core.interpret.DurableEntityT.State uses endless.core.interpret.DurableEntityT, so a change to endless.core.interpret.DurableEntityT can break endless.core.interpret.DurableEntityT.State, while a change to endless.core.interpret.DurableEntityT.State can't break endless.core.interpret.DurableEntityT.
- Position
- Below the diagonal: endless.core.interpret.DurableEntityT.State uses a module listed above it, which is the healthy direction.
23→8 endless.protobuf uses endless.core.protocol✕
- Connections
- 9 pairs of types, where a type in endless.protobuf uses a type in endless.core.protocol.
- The types involved
endless.protobuf.ProtobufCommandProtocol→endless.core.protocol.CommandProtocolendless.protobuf.ProtobufCommandProtocol→endless.core.protocol.CommandSenderendless.protobuf.ProtobufCommandProtocol→endless.core.protocol.IncomingCommandendless.protobuf.ProtobufDecoder→endless.core.protocol.Decoderendless.protobuf.ProtobufEncoder→endless.core.protocol.Encoderendless.protobuf.ProtobufIncomingCommand→endless.core.protocol.Encoderendless.protobuf.ProtobufIncomingCommand→endless.core.protocol.IncomingCommandendless.protobuf.ProtobufOutgoingCommand→endless.core.protocol.Decoderendless.protobuf.ProtobufOutgoingCommand→endless.core.protocol.OutgoingCommand
- Direction
- endless.protobuf uses endless.core.protocol, so a change to endless.core.protocol can break endless.protobuf, while a change to endless.protobuf can't break endless.core.protocol.
- Position
- Below the diagonal: endless.protobuf uses a module listed above it, which is the healthy direction.
24→4 endless.runtime.akka uses endless.core.entity.Effector✕
- Connections
- 1 pair of types, where a type in endless.runtime.akka uses a type in endless.core.entity.Effector.
- The types involved
endless.runtime.akka.EntityPassivator→endless.core.entity.Effector.PassivationState
- Direction
- endless.runtime.akka uses endless.core.entity.Effector, so a change to endless.core.entity.Effector can break endless.runtime.akka, while a change to endless.runtime.akka can't break endless.core.entity.Effector.
- Position
- Below the diagonal: endless.runtime.akka uses a module listed above it, which is the healthy direction.
24→8 endless.runtime.akka uses endless.core.protocol✕
- Connections
- 2 pairs of types, where a type in endless.runtime.akka uses a type in endless.core.protocol.
- The types involved
endless.runtime.akka.ShardingCommandSender→endless.core.protocol.CommandSenderendless.runtime.akka.ShardingCommandSender→endless.core.protocol.OutgoingCommand
- Direction
- endless.runtime.akka uses endless.core.protocol, so a change to endless.core.protocol can break endless.runtime.akka, while a change to endless.runtime.akka can't break endless.core.protocol.
- Position
- Below the diagonal: endless.runtime.akka uses a module listed above it, which is the healthy direction.
25→9 endless.runtime.akka.deploy.AkkaDurableDeployer uses endless.runtime.akka.data✕
- Connections
- 1 pair of types, where a type in endless.runtime.akka.deploy.AkkaDurableDeployer uses a type in endless.runtime.akka.data.
- The types involved
endless.runtime.akka.deploy.AkkaDurableDeployer.DeployedAkkaDurableRepository→endless.runtime.akka.data.Command
- Direction
- endless.runtime.akka.deploy.AkkaDurableDeployer uses endless.runtime.akka.data, so a change to endless.runtime.akka.data can break endless.runtime.akka.deploy.AkkaDurableDeployer, while a change to endless.runtime.akka.deploy.AkkaDurableDeployer can't break endless.runtime.akka.data.
- Position
- Below the diagonal: endless.runtime.akka.deploy.AkkaDurableDeployer uses a module listed above it, which is the healthy direction.
25→31 endless.runtime.akka.deploy.AkkaDurableDeployer uses endless.runtime.akka.deploy part of a loop✕
- Connections
- 1 pair of types, where a type in endless.runtime.akka.deploy.AkkaDurableDeployer uses a type in endless.runtime.akka.deploy.
- The types involved
endless.runtime.akka.deploy.AkkaDurableDeployer.AkkaDurableDeploymentParameters→endless.runtime.akka.deploy.AkkaCluster
- Direction
- endless.runtime.akka.deploy.AkkaDurableDeployer uses endless.runtime.akka.deploy, so a change to endless.runtime.akka.deploy can break endless.runtime.akka.deploy.AkkaDurableDeployer, while a change to endless.runtime.akka.deploy.AkkaDurableDeployer can't break endless.runtime.akka.deploy.
- 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.
26→4 endless.runtime.pekko uses endless.core.entity.Effector✕
- Connections
- 1 pair of types, where a type in endless.runtime.pekko uses a type in endless.core.entity.Effector.
- The types involved
endless.runtime.pekko.EntityPassivator→endless.core.entity.Effector.PassivationState
- Direction
- endless.runtime.pekko uses endless.core.entity.Effector, so a change to endless.core.entity.Effector can break endless.runtime.pekko, while a change to endless.runtime.pekko can't break endless.core.entity.Effector.
- Position
- Below the diagonal: endless.runtime.pekko uses a module listed above it, which is the healthy direction.
26→8 endless.runtime.pekko uses endless.core.protocol✕
- Connections
- 2 pairs of types, where a type in endless.runtime.pekko uses a type in endless.core.protocol.
- The types involved
endless.runtime.pekko.ShardingCommandSender→endless.core.protocol.CommandSenderendless.runtime.pekko.ShardingCommandSender→endless.core.protocol.OutgoingCommand
- Direction
- endless.runtime.pekko uses endless.core.protocol, so a change to endless.core.protocol can break endless.runtime.pekko, while a change to endless.runtime.pekko can't break endless.core.protocol.
- Position
- Below the diagonal: endless.runtime.pekko uses a module listed above it, which is the healthy direction.
27→13 endless.runtime.pekko.deploy.PekkoDeployer uses endless.runtime.pekko.data✕
- Connections
- 1 pair of types, where a type in endless.runtime.pekko.deploy.PekkoDeployer uses a type in endless.runtime.pekko.data.
- The types involved
endless.runtime.pekko.deploy.PekkoDeployer.DeployedPekkoRepository→endless.runtime.pekko.data.Command
- Direction
- endless.runtime.pekko.deploy.PekkoDeployer uses endless.runtime.pekko.data, so a change to endless.runtime.pekko.data can break endless.runtime.pekko.deploy.PekkoDeployer, while a change to endless.runtime.pekko.deploy.PekkoDeployer can't break endless.runtime.pekko.data.
- Position
- Below the diagonal: endless.runtime.pekko.deploy.PekkoDeployer uses a module listed above it, which is the healthy direction.
27→32 endless.runtime.pekko.deploy.PekkoDeployer uses endless.runtime.pekko.deploy part of a loop✕
- Connections
- 1 pair of types, where a type in endless.runtime.pekko.deploy.PekkoDeployer uses a type in endless.runtime.pekko.deploy.
- The types involved
endless.runtime.pekko.deploy.PekkoDeployer.PekkoDeploymentParameters→endless.runtime.pekko.deploy.PekkoCluster
- Direction
- endless.runtime.pekko.deploy.PekkoDeployer uses endless.runtime.pekko.deploy, so a change to endless.runtime.pekko.deploy can break endless.runtime.pekko.deploy.PekkoDeployer, while a change to endless.runtime.pekko.deploy.PekkoDeployer can't break endless.runtime.pekko.deploy.
- 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.
28→13 endless.runtime.pekko.deploy.PekkoDurableDeployer uses endless.runtime.pekko.data✕
- Connections
- 1 pair of types, where a type in endless.runtime.pekko.deploy.PekkoDurableDeployer uses a type in endless.runtime.pekko.data.
- The types involved
endless.runtime.pekko.deploy.PekkoDurableDeployer.DeployedPekkoDurableRepository→endless.runtime.pekko.data.Command
- Direction
- endless.runtime.pekko.deploy.PekkoDurableDeployer uses endless.runtime.pekko.data, so a change to endless.runtime.pekko.data can break endless.runtime.pekko.deploy.PekkoDurableDeployer, while a change to endless.runtime.pekko.deploy.PekkoDurableDeployer can't break endless.runtime.pekko.data.
- Position
- Below the diagonal: endless.runtime.pekko.deploy.PekkoDurableDeployer uses a module listed above it, which is the healthy direction.
28→32 endless.runtime.pekko.deploy.PekkoDurableDeployer uses endless.runtime.pekko.deploy part of a loop✕
- Connections
- 1 pair of types, where a type in endless.runtime.pekko.deploy.PekkoDurableDeployer uses a type in endless.runtime.pekko.deploy.
- The types involved
endless.runtime.pekko.deploy.PekkoDurableDeployer.PekkoDurableDeploymentParameters→endless.runtime.pekko.deploy.PekkoCluster
- Direction
- endless.runtime.pekko.deploy.PekkoDurableDeployer uses endless.runtime.pekko.deploy, so a change to endless.runtime.pekko.deploy can break endless.runtime.pekko.deploy.PekkoDurableDeployer, while a change to endless.runtime.pekko.deploy.PekkoDurableDeployer can't break endless.runtime.pekko.deploy.
- 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.
29→6 endless.core.interpret uses endless.core.event✕
- Connections
- 1 pair of types, where a type in endless.core.interpret uses a type in endless.core.event.
- The types involved
endless.core.interpret.EntityT→endless.core.event.EventApplier
- Direction
- endless.core.interpret uses endless.core.event, so a change to endless.core.event can break endless.core.interpret, while a change to endless.core.interpret can't break endless.core.event.
- Position
- Below the diagonal: endless.core.interpret uses a module listed above it, which is the healthy direction.
29→18 endless.core.interpret uses endless.core.data✕
- Connections
- 2 pairs of types, where a type in endless.core.interpret uses a type in endless.core.data.
- The types involved
endless.core.interpret.EntityRunFunctions→endless.core.data.EventsFolderendless.core.interpret.EntityT→endless.core.data.EventsFolder
- Direction
- endless.core.interpret uses endless.core.data, so a change to endless.core.data can break endless.core.interpret, while a change to endless.core.interpret can't break endless.core.data.
- Position
- Below the diagonal: endless.core.interpret uses a module listed above it, which is the healthy direction.
29→30 endless.core.interpret uses endless.core.entity part of a loop✕
- Connections
- 6 pairs of types, where a type in endless.core.interpret uses a type in endless.core.entity.
- The types involved
endless.core.interpret.BehaviorInterpreter→endless.core.entity.Entityendless.core.interpret.DurableBehaviorInterpreter→endless.core.entity.DurableEntityendless.core.interpret.DurableEntityT→endless.core.entity.DurableEntityendless.core.interpret.EntityTLiftInstance→endless.core.entity.Entityendless.core.interpret.RepositoryInterpreter→endless.core.entity.Shardingendless.core.interpret.SideEffectInterpreter→endless.core.entity.SideEffect
- Direction
- endless.core.interpret uses endless.core.entity, so a change to endless.core.entity can break endless.core.interpret, while a change to endless.core.interpret can't break endless.core.entity.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
30→4 endless.core.entity uses endless.core.entity.Effector✕
- Connections
- 1 pair of types, where a type in endless.core.entity uses a type in endless.core.entity.Effector.
- The types involved
endless.core.entity.Passivator→endless.core.entity.Effector.PassivationState
- Direction
- endless.core.entity uses endless.core.entity.Effector, so a change to endless.core.entity.Effector can break endless.core.entity, while a change to endless.core.entity can't break endless.core.entity.Effector.
- Position
- Below the diagonal: endless.core.entity uses a module listed above it, which is the healthy direction.
30→6 endless.core.entity uses endless.core.event✕
- Connections
- 2 pairs of types, where a type in endless.core.entity uses a type in endless.core.event.
- The types involved
endless.core.entity.Deployer→endless.core.event.EventApplierendless.core.entity.Entity→endless.core.event.EventWriter
- Direction
- endless.core.entity uses endless.core.event, so a change to endless.core.event can break endless.core.entity, while a change to endless.core.entity can't break endless.core.event.
- Position
- Below the diagonal: endless.core.entity uses a module listed above it, which is the healthy direction.
30→8 endless.core.entity uses endless.core.protocol✕
- Connections
- 2 pairs of types, where a type in endless.core.entity uses a type in endless.core.protocol.
- The types involved
endless.core.entity.Deployer→endless.core.protocol.CommandProtocolendless.core.entity.DurableDeployer→endless.core.protocol.CommandProtocol
- Direction
- endless.core.entity uses endless.core.protocol, so a change to endless.core.protocol can break endless.core.entity, while a change to endless.core.entity can't break endless.core.protocol.
- Position
- Below the diagonal: endless.core.entity uses a module listed above it, which is the healthy direction.
30→29 endless.core.entity uses endless.core.interpret✕
- Connections
- 6 pairs of types, where a type in endless.core.entity uses a type in endless.core.interpret.
- The types involved
endless.core.entity.Deployer→endless.core.interpret.BehaviorInterpreterendless.core.entity.Deployer→endless.core.interpret.RepositoryInterpreterendless.core.entity.Deployer→endless.core.interpret.SideEffectInterpreterendless.core.entity.DurableDeployer→endless.core.interpret.DurableBehaviorInterpreterendless.core.entity.DurableDeployer→endless.core.interpret.RepositoryInterpreterendless.core.entity.DurableDeployer→endless.core.interpret.SideEffectInterpreter
- Direction
- endless.core.entity uses endless.core.interpret, so a change to endless.core.interpret can break endless.core.entity, while a change to endless.core.entity can't break endless.core.interpret.
- Position
- Below the diagonal: endless.core.entity uses a module listed above it, which is the healthy direction.
31→6 endless.runtime.akka.deploy uses endless.core.event✕
- Connections
- 1 pair of types, where a type in endless.runtime.akka.deploy uses a type in endless.core.event.
- The types involved
endless.runtime.akka.deploy.AkkaDeployer→endless.core.event.EventApplier
- Direction
- endless.runtime.akka.deploy uses endless.core.event, so a change to endless.core.event can break endless.runtime.akka.deploy, while a change to endless.runtime.akka.deploy can't break endless.core.event.
- Position
- Below the diagonal: endless.runtime.akka.deploy uses a module listed above it, which is the healthy direction.
31→8 endless.runtime.akka.deploy uses endless.core.protocol✕
- Connections
- 2 pairs of types, where a type in endless.runtime.akka.deploy uses a type in endless.core.protocol.
- The types involved
endless.runtime.akka.deploy.AkkaDeployer→endless.core.protocol.CommandProtocolendless.runtime.akka.deploy.AkkaDurableDeployer→endless.core.protocol.CommandProtocol
- Direction
- endless.runtime.akka.deploy uses endless.core.protocol, so a change to endless.core.protocol can break endless.runtime.akka.deploy, while a change to endless.runtime.akka.deploy can't break endless.core.protocol.
- Position
- Below the diagonal: endless.runtime.akka.deploy uses a module listed above it, which is the healthy direction.
31→25 endless.runtime.akka.deploy uses endless.runtime.akka.deploy.AkkaDurableDeployer✕
- Connections
- 2 pairs of types, where a type in endless.runtime.akka.deploy uses a type in endless.runtime.akka.deploy.AkkaDurableDeployer.
- The types involved
endless.runtime.akka.deploy.AkkaDurableDeployer→endless.runtime.akka.deploy.AkkaDurableDeployer.AkkaDurableDeploymentParametersendless.runtime.akka.deploy.AkkaDurableDeployer→endless.runtime.akka.deploy.AkkaDurableDeployer.DeployedAkkaDurableRepository
- Direction
- endless.runtime.akka.deploy uses endless.runtime.akka.deploy.AkkaDurableDeployer, so a change to endless.runtime.akka.deploy.AkkaDurableDeployer can break endless.runtime.akka.deploy, while a change to endless.runtime.akka.deploy can't break endless.runtime.akka.deploy.AkkaDurableDeployer.
- Position
- Below the diagonal: endless.runtime.akka.deploy uses a module listed above it, which is the healthy direction.
31→29 endless.runtime.akka.deploy uses endless.core.interpret✕
- Connections
- 6 pairs of types, where a type in endless.runtime.akka.deploy uses a type in endless.core.interpret.
- The types involved
endless.runtime.akka.deploy.AkkaDeployer→endless.core.interpret.BehaviorInterpreterendless.runtime.akka.deploy.AkkaDeployer→endless.core.interpret.RepositoryInterpreterendless.runtime.akka.deploy.AkkaDeployer→endless.core.interpret.SideEffectInterpreterendless.runtime.akka.deploy.AkkaDurableDeployer→endless.core.interpret.DurableBehaviorInterpreterendless.runtime.akka.deploy.AkkaDurableDeployer→endless.core.interpret.RepositoryInterpreterendless.runtime.akka.deploy.AkkaDurableDeployer→endless.core.interpret.SideEffectInterpreter
- Direction
- endless.runtime.akka.deploy uses endless.core.interpret, so a change to endless.core.interpret can break endless.runtime.akka.deploy, while a change to endless.runtime.akka.deploy can't break endless.core.interpret.
- Position
- Below the diagonal: endless.runtime.akka.deploy uses a module listed above it, which is the healthy direction.
31→30 endless.runtime.akka.deploy uses endless.core.entity✕
- Connections
- 4 pairs of types, where a type in endless.runtime.akka.deploy uses a type in endless.core.entity.
- The types involved
endless.runtime.akka.deploy.AkkaDeployer→endless.core.entity.Deployerendless.runtime.akka.deploy.AkkaDeployer→endless.core.entity.EntityNameProviderendless.runtime.akka.deploy.AkkaDurableDeployer→endless.core.entity.DurableDeployerendless.runtime.akka.deploy.AkkaDurableDeployer→endless.core.entity.EntityNameProvider
- Direction
- endless.runtime.akka.deploy uses endless.core.entity, so a change to endless.core.entity can break endless.runtime.akka.deploy, while a change to endless.runtime.akka.deploy can't break endless.core.entity.
- Position
- Below the diagonal: endless.runtime.akka.deploy uses a module listed above it, which is the healthy direction.
32→6 endless.runtime.pekko.deploy uses endless.core.event✕
- Connections
- 1 pair of types, where a type in endless.runtime.pekko.deploy uses a type in endless.core.event.
- The types involved
endless.runtime.pekko.deploy.PekkoDeployer→endless.core.event.EventApplier
- Direction
- endless.runtime.pekko.deploy uses endless.core.event, so a change to endless.core.event can break endless.runtime.pekko.deploy, while a change to endless.runtime.pekko.deploy can't break endless.core.event.
- Position
- Below the diagonal: endless.runtime.pekko.deploy uses a module listed above it, which is the healthy direction.
32→8 endless.runtime.pekko.deploy uses endless.core.protocol✕
- Connections
- 2 pairs of types, where a type in endless.runtime.pekko.deploy uses a type in endless.core.protocol.
- The types involved
endless.runtime.pekko.deploy.PekkoDeployer→endless.core.protocol.CommandProtocolendless.runtime.pekko.deploy.PekkoDurableDeployer→endless.core.protocol.CommandProtocol
- Direction
- endless.runtime.pekko.deploy uses endless.core.protocol, so a change to endless.core.protocol can break endless.runtime.pekko.deploy, while a change to endless.runtime.pekko.deploy can't break endless.core.protocol.
- Position
- Below the diagonal: endless.runtime.pekko.deploy uses a module listed above it, which is the healthy direction.
32→27 endless.runtime.pekko.deploy uses endless.runtime.pekko.deploy.PekkoDeployer✕
- Connections
- 2 pairs of types, where a type in endless.runtime.pekko.deploy uses a type in endless.runtime.pekko.deploy.PekkoDeployer.
- The types involved
endless.runtime.pekko.deploy.PekkoDeployer→endless.runtime.pekko.deploy.PekkoDeployer.DeployedPekkoRepositoryendless.runtime.pekko.deploy.PekkoDeployer→endless.runtime.pekko.deploy.PekkoDeployer.PekkoDeploymentParameters
- Direction
- endless.runtime.pekko.deploy uses endless.runtime.pekko.deploy.PekkoDeployer, so a change to endless.runtime.pekko.deploy.PekkoDeployer can break endless.runtime.pekko.deploy, while a change to endless.runtime.pekko.deploy can't break endless.runtime.pekko.deploy.PekkoDeployer.
- Position
- Below the diagonal: endless.runtime.pekko.deploy uses a module listed above it, which is the healthy direction.
32→28 endless.runtime.pekko.deploy uses endless.runtime.pekko.deploy.PekkoDurableDeployer✕
- Connections
- 2 pairs of types, where a type in endless.runtime.pekko.deploy uses a type in endless.runtime.pekko.deploy.PekkoDurableDeployer.
- The types involved
endless.runtime.pekko.deploy.PekkoDurableDeployer→endless.runtime.pekko.deploy.PekkoDurableDeployer.DeployedPekkoDurableRepositoryendless.runtime.pekko.deploy.PekkoDurableDeployer→endless.runtime.pekko.deploy.PekkoDurableDeployer.PekkoDurableDeploymentParameters
- Direction
- endless.runtime.pekko.deploy uses endless.runtime.pekko.deploy.PekkoDurableDeployer, so a change to endless.runtime.pekko.deploy.PekkoDurableDeployer can break endless.runtime.pekko.deploy, while a change to endless.runtime.pekko.deploy can't break endless.runtime.pekko.deploy.PekkoDurableDeployer.
- Position
- Below the diagonal: endless.runtime.pekko.deploy uses a module listed above it, which is the healthy direction.
32→29 endless.runtime.pekko.deploy uses endless.core.interpret✕
- Connections
- 6 pairs of types, where a type in endless.runtime.pekko.deploy uses a type in endless.core.interpret.
- The types involved
endless.runtime.pekko.deploy.PekkoDeployer→endless.core.interpret.BehaviorInterpreterendless.runtime.pekko.deploy.PekkoDeployer→endless.core.interpret.RepositoryInterpreterendless.runtime.pekko.deploy.PekkoDeployer→endless.core.interpret.SideEffectInterpreterendless.runtime.pekko.deploy.PekkoDurableDeployer→endless.core.interpret.DurableBehaviorInterpreterendless.runtime.pekko.deploy.PekkoDurableDeployer→endless.core.interpret.RepositoryInterpreterendless.runtime.pekko.deploy.PekkoDurableDeployer→endless.core.interpret.SideEffectInterpreter
- Direction
- endless.runtime.pekko.deploy uses endless.core.interpret, so a change to endless.core.interpret can break endless.runtime.pekko.deploy, while a change to endless.runtime.pekko.deploy can't break endless.core.interpret.
- Position
- Below the diagonal: endless.runtime.pekko.deploy uses a module listed above it, which is the healthy direction.
32→30 endless.runtime.pekko.deploy uses endless.core.entity✕
- Connections
- 4 pairs of types, where a type in endless.runtime.pekko.deploy uses a type in endless.core.entity.
- The types involved
endless.runtime.pekko.deploy.PekkoDeployer→endless.core.entity.Deployerendless.runtime.pekko.deploy.PekkoDeployer→endless.core.entity.EntityNameProviderendless.runtime.pekko.deploy.PekkoDurableDeployer→endless.core.entity.DurableDeployerendless.runtime.pekko.deploy.PekkoDurableDeployer→endless.core.entity.EntityNameProvider
- Direction
- endless.runtime.pekko.deploy uses endless.core.entity, so a change to endless.core.entity can break endless.runtime.pekko.deploy, while a change to endless.runtime.pekko.deploy can't break endless.core.entity.
- Position
- Below the diagonal: endless.runtime.pekko.deploy uses a module listed above it, which is the healthy direction.
33→9 endless.runtime.akka.deploy.AkkaDeployer uses endless.runtime.akka.data✕
- Connections
- 1 pair of types, where a type in endless.runtime.akka.deploy.AkkaDeployer uses a type in endless.runtime.akka.data.
- The types involved
endless.runtime.akka.deploy.AkkaDeployer.DeployedAkkaRepository→endless.runtime.akka.data.Command
- Direction
- endless.runtime.akka.deploy.AkkaDeployer uses endless.runtime.akka.data, so a change to endless.runtime.akka.data can break endless.runtime.akka.deploy.AkkaDeployer, while a change to endless.runtime.akka.deploy.AkkaDeployer can't break endless.runtime.akka.data.
- Position
- Below the diagonal: endless.runtime.akka.deploy.AkkaDeployer uses a module listed above it, which is the healthy direction.
33→31 endless.runtime.akka.deploy.AkkaDeployer uses endless.runtime.akka.deploy✕
- Connections
- 1 pair of types, where a type in endless.runtime.akka.deploy.AkkaDeployer uses a type in endless.runtime.akka.deploy.
- The types involved
endless.runtime.akka.deploy.AkkaDeployer.AkkaDeploymentParameters→endless.runtime.akka.deploy.AkkaCluster
- Direction
- endless.runtime.akka.deploy.AkkaDeployer uses endless.runtime.akka.deploy, so a change to endless.runtime.akka.deploy can break endless.runtime.akka.deploy.AkkaDeployer, while a change to endless.runtime.akka.deploy.AkkaDeployer can't break endless.runtime.akka.deploy.
- Position
- Below the diagonal: endless.runtime.akka.deploy.AkkaDeployer uses a module listed above it, which is the healthy direction.
34→8 endless.runtime.akka.deploy.internal uses endless.core.protocol✕
- Connections
- 2 pairs of types, where a type in endless.runtime.akka.deploy.internal uses a type in endless.core.protocol.
- The types involved
endless.runtime.akka.deploy.internal.ShardedRepositoryDeployer→endless.core.protocol.CommandProtocolendless.runtime.akka.deploy.internal.ShardedRepositoryDeployer→endless.core.protocol.EntityIDEncoder
- Direction
- endless.runtime.akka.deploy.internal uses endless.core.protocol, so a change to endless.core.protocol can break endless.runtime.akka.deploy.internal, while a change to endless.runtime.akka.deploy.internal can't break endless.core.protocol.
- Position
- Below the diagonal: endless.runtime.akka.deploy.internal uses a module listed above it, which is the healthy direction.
34→9 endless.runtime.akka.deploy.internal uses endless.runtime.akka.data✕
- Connections
- 3 pairs of types, where a type in endless.runtime.akka.deploy.internal uses a type in endless.runtime.akka.data.
- The types involved
endless.runtime.akka.deploy.internal.DurableShardedRepositoryDeployer→endless.runtime.akka.data.Commandendless.runtime.akka.deploy.internal.EventSourcedShardedRepositoryDeployer→endless.runtime.akka.data.Commandendless.runtime.akka.deploy.internal.ShardedRepositoryDeployer→endless.runtime.akka.data.Command
- Direction
- endless.runtime.akka.deploy.internal uses endless.runtime.akka.data, so a change to endless.runtime.akka.data can break endless.runtime.akka.deploy.internal, while a change to endless.runtime.akka.deploy.internal can't break endless.runtime.akka.data.
- Position
- Below the diagonal: endless.runtime.akka.deploy.internal uses a module listed above it, which is the healthy direction.
34→24 endless.runtime.akka.deploy.internal uses endless.runtime.akka✕
- Connections
- 2 pairs of types, where a type in endless.runtime.akka.deploy.internal uses a type in endless.runtime.akka.
- The types involved
endless.runtime.akka.deploy.internal.DurableShardedRepositoryDeployer→endless.runtime.akka.EntityPassivatorendless.runtime.akka.deploy.internal.EventSourcedShardedRepositoryDeployer→endless.runtime.akka.EntityPassivator
- Direction
- endless.runtime.akka.deploy.internal uses endless.runtime.akka, so a change to endless.runtime.akka can break endless.runtime.akka.deploy.internal, while a change to endless.runtime.akka.deploy.internal can't break endless.runtime.akka.
- Position
- Below the diagonal: endless.runtime.akka.deploy.internal uses a module listed above it, which is the healthy direction.
34→29 endless.runtime.akka.deploy.internal uses endless.core.interpret✕
- Connections
- 1 pair of types, where a type in endless.runtime.akka.deploy.internal uses a type in endless.core.interpret.
- The types involved
endless.runtime.akka.deploy.internal.ShardedRepositoryDeployer→endless.core.interpret.RepositoryInterpreter
- Direction
- endless.runtime.akka.deploy.internal uses endless.core.interpret, so a change to endless.core.interpret can break endless.runtime.akka.deploy.internal, while a change to endless.runtime.akka.deploy.internal can't break endless.core.interpret.
- Position
- Below the diagonal: endless.runtime.akka.deploy.internal uses a module listed above it, which is the healthy direction.
34→30 endless.runtime.akka.deploy.internal uses endless.core.entity✕
- Connections
- 5 pairs of types, where a type in endless.runtime.akka.deploy.internal uses a type in endless.core.entity.
- The types involved
endless.runtime.akka.deploy.internal.DurableShardedRepositoryDeployer→endless.core.entity.EntityNameProviderendless.runtime.akka.deploy.internal.DurableShardedRepositoryDeployer→endless.core.entity.SideEffectendless.runtime.akka.deploy.internal.EventSourcedShardedRepositoryDeployer→endless.core.entity.EntityNameProviderendless.runtime.akka.deploy.internal.EventSourcedShardedRepositoryDeployer→endless.core.entity.SideEffectendless.runtime.akka.deploy.internal.ShardedRepositoryDeployer→endless.core.entity.EntityNameProvider
- Direction
- endless.runtime.akka.deploy.internal uses endless.core.entity, so a change to endless.core.entity can break endless.runtime.akka.deploy.internal, while a change to endless.runtime.akka.deploy.internal can't break endless.core.entity.
- Position
- Below the diagonal: endless.runtime.akka.deploy.internal uses a module listed above it, which is the healthy direction.
34→31 endless.runtime.akka.deploy.internal uses endless.runtime.akka.deploy✕
- Connections
- 1 pair of types, where a type in endless.runtime.akka.deploy.internal uses a type in endless.runtime.akka.deploy.
- The types involved
endless.runtime.akka.deploy.internal.ShardedRepositoryDeployer→endless.runtime.akka.deploy.AkkaCluster
- Direction
- endless.runtime.akka.deploy.internal uses endless.runtime.akka.deploy, so a change to endless.runtime.akka.deploy can break endless.runtime.akka.deploy.internal, while a change to endless.runtime.akka.deploy.internal can't break endless.runtime.akka.deploy.
- Position
- Below the diagonal: endless.runtime.akka.deploy.internal uses a module listed above it, which is the healthy direction.
35→31 endless.runtime.akka.syntax uses endless.runtime.akka.deploy✕
- Connections
- 2 pairs of types, where a type in endless.runtime.akka.syntax uses a type in endless.runtime.akka.deploy.
- The types involved
endless.runtime.akka.syntax.deploy→endless.runtime.akka.deploy.AkkaDeployerendless.runtime.akka.syntax.deploy→endless.runtime.akka.deploy.AkkaDurableDeployer
- Direction
- endless.runtime.akka.syntax uses endless.runtime.akka.deploy, so a change to endless.runtime.akka.deploy can break endless.runtime.akka.syntax, while a change to endless.runtime.akka.syntax can't break endless.runtime.akka.deploy.
- Position
- Below the diagonal: endless.runtime.akka.syntax uses a module listed above it, which is the healthy direction.
36→8 endless.runtime.pekko.deploy.internal uses endless.core.protocol✕
- Connections
- 2 pairs of types, where a type in endless.runtime.pekko.deploy.internal uses a type in endless.core.protocol.
- The types involved
endless.runtime.pekko.deploy.internal.ShardedRepositoryDeployer→endless.core.protocol.CommandProtocolendless.runtime.pekko.deploy.internal.ShardedRepositoryDeployer→endless.core.protocol.EntityIDEncoder
- Direction
- endless.runtime.pekko.deploy.internal uses endless.core.protocol, so a change to endless.core.protocol can break endless.runtime.pekko.deploy.internal, while a change to endless.runtime.pekko.deploy.internal can't break endless.core.protocol.
- Position
- Below the diagonal: endless.runtime.pekko.deploy.internal uses a module listed above it, which is the healthy direction.
36→13 endless.runtime.pekko.deploy.internal uses endless.runtime.pekko.data✕
- Connections
- 3 pairs of types, where a type in endless.runtime.pekko.deploy.internal uses a type in endless.runtime.pekko.data.
- The types involved
endless.runtime.pekko.deploy.internal.DurableShardedEntityDeployer→endless.runtime.pekko.data.Commandendless.runtime.pekko.deploy.internal.EventSourcedShardedEntityDeployer→endless.runtime.pekko.data.Commandendless.runtime.pekko.deploy.internal.ShardedRepositoryDeployer→endless.runtime.pekko.data.Command
- Direction
- endless.runtime.pekko.deploy.internal uses endless.runtime.pekko.data, so a change to endless.runtime.pekko.data can break endless.runtime.pekko.deploy.internal, while a change to endless.runtime.pekko.deploy.internal can't break endless.runtime.pekko.data.
- Position
- Below the diagonal: endless.runtime.pekko.deploy.internal uses a module listed above it, which is the healthy direction.
36→26 endless.runtime.pekko.deploy.internal uses endless.runtime.pekko✕
- Connections
- 2 pairs of types, where a type in endless.runtime.pekko.deploy.internal uses a type in endless.runtime.pekko.
- The types involved
endless.runtime.pekko.deploy.internal.DurableShardedEntityDeployer→endless.runtime.pekko.EntityPassivatorendless.runtime.pekko.deploy.internal.EventSourcedShardedEntityDeployer→endless.runtime.pekko.EntityPassivator
- Direction
- endless.runtime.pekko.deploy.internal uses endless.runtime.pekko, so a change to endless.runtime.pekko can break endless.runtime.pekko.deploy.internal, while a change to endless.runtime.pekko.deploy.internal can't break endless.runtime.pekko.
- Position
- Below the diagonal: endless.runtime.pekko.deploy.internal uses a module listed above it, which is the healthy direction.
36→29 endless.runtime.pekko.deploy.internal uses endless.core.interpret✕
- Connections
- 1 pair of types, where a type in endless.runtime.pekko.deploy.internal uses a type in endless.core.interpret.
- The types involved
endless.runtime.pekko.deploy.internal.ShardedRepositoryDeployer→endless.core.interpret.RepositoryInterpreter
- Direction
- endless.runtime.pekko.deploy.internal uses endless.core.interpret, so a change to endless.core.interpret can break endless.runtime.pekko.deploy.internal, while a change to endless.runtime.pekko.deploy.internal can't break endless.core.interpret.
- Position
- Below the diagonal: endless.runtime.pekko.deploy.internal uses a module listed above it, which is the healthy direction.
36→30 endless.runtime.pekko.deploy.internal uses endless.core.entity✕
- Connections
- 5 pairs of types, where a type in endless.runtime.pekko.deploy.internal uses a type in endless.core.entity.
- The types involved
endless.runtime.pekko.deploy.internal.DurableShardedEntityDeployer→endless.core.entity.EntityNameProviderendless.runtime.pekko.deploy.internal.DurableShardedEntityDeployer→endless.core.entity.SideEffectendless.runtime.pekko.deploy.internal.EventSourcedShardedEntityDeployer→endless.core.entity.EntityNameProviderendless.runtime.pekko.deploy.internal.EventSourcedShardedEntityDeployer→endless.core.entity.SideEffectendless.runtime.pekko.deploy.internal.ShardedRepositoryDeployer→endless.core.entity.EntityNameProvider
- Direction
- endless.runtime.pekko.deploy.internal uses endless.core.entity, so a change to endless.core.entity can break endless.runtime.pekko.deploy.internal, while a change to endless.runtime.pekko.deploy.internal can't break endless.core.entity.
- Position
- Below the diagonal: endless.runtime.pekko.deploy.internal uses a module listed above it, which is the healthy direction.
36→32 endless.runtime.pekko.deploy.internal uses endless.runtime.pekko.deploy✕
- Connections
- 1 pair of types, where a type in endless.runtime.pekko.deploy.internal uses a type in endless.runtime.pekko.deploy.
- The types involved
endless.runtime.pekko.deploy.internal.ShardedRepositoryDeployer→endless.runtime.pekko.deploy.PekkoCluster
- Direction
- endless.runtime.pekko.deploy.internal uses endless.runtime.pekko.deploy, so a change to endless.runtime.pekko.deploy can break endless.runtime.pekko.deploy.internal, while a change to endless.runtime.pekko.deploy.internal can't break endless.runtime.pekko.deploy.
- Position
- Below the diagonal: endless.runtime.pekko.deploy.internal uses a module listed above it, which is the healthy direction.
37→32 endless.runtime.pekko.syntax uses endless.runtime.pekko.deploy✕
- Connections
- 2 pairs of types, where a type in endless.runtime.pekko.syntax uses a type in endless.runtime.pekko.deploy.
- The types involved
endless.runtime.pekko.syntax.deploy→endless.runtime.pekko.deploy.PekkoDeployerendless.runtime.pekko.syntax.deploy→endless.runtime.pekko.deploy.PekkoDurableDeployer
- Direction
- endless.runtime.pekko.syntax uses endless.runtime.pekko.deploy, so a change to endless.runtime.pekko.deploy can break endless.runtime.pekko.syntax, while a change to endless.runtime.pekko.syntax can't break endless.runtime.pekko.deploy.
- Position
- Below the diagonal: endless.runtime.pekko.syntax 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 |
|---|---|---|
| A05:2025 — Injection | 16 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 5 | Medium |
Roadmap
Top priorities: Resolve the 1 No ADRs found finding(s) in ADR Quality; Resolve the 4 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (3), REDACTED; 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. | +5.8 pts | Low | ADR Quality |
| Resolve the 4 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (3), REDACTED. | +3.3 pts | Low | Static Analysis (SAST) |
| Resolve the 2 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED. | +2.3 pts | Low | Supply-chain Provenance & Signing |
| Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them. | +3.2 pts | Medium | Architecture documentation |
| Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. | +1.4 pts | Low | Supply-chain Provenance & Signing |
| Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. | +1.4 pts | Low | Supply-chain Provenance & Signing |
| Expand the README with getting-started, architecture overview and a project map. | +2.7 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.3 pts | Medium | Security & performance tooling |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 2.3 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.7 | Slop | Static Analysis (SAST): High: REDACTED |
| akka-runtime/src/main/scala/endless/runtime/akka/deploy/internal/DurableShardedRepositoryDeployer.scala | 7.0 | Mixed | Code Duplication: Members sharing a duplicated core (4 members, 50+ identical tokens) |
| akka-runtime/src/main/scala/endless/runtime/akka/deploy/AkkaCluster.scala | 7.2 | Mixed | Cognitive Complexity: AkkaCluster.managedResource (cognitive 31) |
| akka-runtime/src/main/scala/endless/runtime/akka/deploy/internal/EventSourcedShardedRepositoryDeployer.scala | 7.2 | Mixed | Code Duplication: Duplicated block (24 lines × 2) |
| pekko-runtime/src/main/scala/endless/runtime/pekko/deploy/PekkoCluster.scala | 7.8 | Mixed | Cognitive Complexity: PekkoCluster.managedResource (cognitive 31) |
| akka-runtime/src/main/scala/endless/runtime/akka/protobuf/ScalaPbSerializer.scala | 8.5 | Near-clean | Code Duplication: Duplicated block (36 lines × 2) |
| akka-runtime/src/main/scala/endless/runtime/akka/ShardingCommandSender.scala | 8.5 | Near-clean | Code Duplication: Duplicated block (20 lines × 2) |
| akka-runtime/src/main/scala/endless/runtime/akka/EntityPassivator.scala | 8.5 | Near-clean | Code Duplication: Duplicated block (24 lines × 2) |
| akka-runtime/src/main/scala/endless/runtime/akka/serializer/CommandSerializer.scala | 8.5 | Near-clean | Code Duplication: Duplicated block (32 lines × 2) |
| akka-runtime/src/main/scala/endless/runtime/akka/serializer/ReplySerializer.scala | 8.5 | Near-clean | Code Duplication: Duplicated block (21 lines × 2) |
| example/src/main/scala/endless/example/app/akka/AkkaApp.scala | 8.5 | Near-clean | Code Duplication: Duplicated block (17 lines × 2) |
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 59 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 — 59 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, 42 of 55 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 scalafmtCheckAll clean compile coverage +test coverageRe…`) shows that coverage is collected and tracked in your own CI. The built-in collector has no runner for this ecosystem (.scala), so the analyzer could not read the number — a gap in the analyzer's language coverage, not an unmeasured repo. Not scored. To have the real number read, produce a coverage report in a standard format (`addSbtPlugin("org.scoverage" % "sbt-scoverage" % "<version>")` in `project/plugins.sbt`, then `sbt clean coverage test coverageReport`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures. You can widen what we reach: optional: produce a coverage report in a standard format (`addSbtPlugin("org.scoverage" % "sbt-scoverage" % "<version>")` in `project/plugins.sbt`, then `sbt clean coverage test coverageReport`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures — then the real number is read on the next scan.
- D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test source is present (.scala) and this repository declares an sbt build (repository root, 19 test files), but it was not re-run: no test result was produced. Not scored — this is a gap in the analyzer's language coverage, not a finding about this repository.
- D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D21's deterministic naming rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. Until then its declarations carry no naming verdict this run — this says nothing about whether its names are consistent.
- D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22 identifies the intentionally-exposed surface from `IsPackable` and `.Contracts` project names, MSBuild conventions read off the loaded project set. This target exposed no such projects, so the probe never ran; this says nothing about whether the repository has a public API. This repository commits no C#/VB source at all, so there was never an MSBuild project set to read these conventions off. That is OUR side and it is an ADMISSION gap, not an environment fault: it declares a published package (project/plugins.sbt), but no published-package marker D22 reads admitted any project here. D22 DOES collect the public API of every language in this tree, and admits a project only when its manifest makes that ecosystem's publication act in a form the marker recognises — so what is missing is not a collector but an admission rule for the publication act this repository makes, if it makes one. The remedy is a better discriminator for that marker — not a collector, and no change to the scan image can close it. The marker's rules are measured to refuse applications, so one refused repository is the rule working as calibrated; several are the evidence that it is too strict.
- 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.
- 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 build.sbt 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.
- AX2 Stateful singletons — 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 singletons in C#, Spring/JSR-330/CDI singletons in Java and Kotlin, module state in Python request handlers, handler state in Go and Swift, Play controllers, Cask routes, Scalatra servlets, Finatra controllers, Akka/Pekko HTTP routes and JSR-330 singletons in Scala, Rails, Sinatra, Grape, Roda and Hanami handlers and Rack apps in Ruby, and module state in F# request handlers (Giraffe, Saturn, Falco, Oxpecker and Suave handlers and ASP.NET Core controllers) only, and this repository's product is written in Scala (http4s), which was left unread, 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.
- D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
- 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 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- 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.
- M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
- P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
Dimensions
D1 · Cyclomatic Complexity
0 method(s) exceeded the cyclomatic complexity threshold of 15.
D2 · Cognitive Complexity
4 method(s) exceeded the cognitive complexity threshold of 15; the worst was AkkaCluster.managedResource at 31.
What to do
- Bring the 4 bodies over 15 down to 15 or less in Cognitive Complexity — start with AkkaCluster.managedResource (cognitive 31), PekkoCluster.managedResource (cognitive 31), AkkaCluster.createCluster (cognitive 21). — 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 4 together lifts Cognitive Complexity from 8.7 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
- Enforce Cognitive Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D3 · God Classes
0 god class(es) detected.
D4 · Code Duplication
17 duplicated block group(s) detected. A further 2 rows report members as variants of one another; they aggregate block groups already counted above and are not themselves counted. 1 of the 19 are in trees this repository does not ship — vendored, example/demo, project-template, fixture and benchmark code — and are ranked below the shipped groups rather than excluded from them: the duplication there is real and is still counted in this dimension's score. The dimensions that publish a production-file census leave those trees out of theirs, so this count is deliberately drawn over the wider population.
What to do
- Resolve the 2 Members sharing a duplicated core (4 members, 50+ identical tokens) finding(s) in Code Duplication — start with DurableShardedRepositoryDeployer.scala (2). — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 2 Duplicated block (24 lines × 2) finding(s) in Code Duplication — start with EventSourcedShardedRepositoryDeployer.scala, EntityPassivator.scala. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 2 Duplicated block (21 lines × 2) finding(s) in Code Duplication — start with DurableShardedRepositoryDeployer.scala, ReplySerializer.scala. — One of this dimension's main actionable groups (2 warning-level).
- Enforce Code Duplication in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D5 · Coupling
6 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, with abstractness counted on 5 of the 6 (the rest declare no modelled class or interface, export only macros, declare types in source no model reads, or have no source directory of their own).
D6 · Cohesion (LCOM4)
0 of 10 classes have LCOM4 above 3.
D9 · Test Distribution
99 test methods: 99 unit, 0 integration, 0 BDD, 0 e2e. The Scala suite contributes 99 test case(s) across 15 file(s) in a test source set declaring at least one — every `test("…")`, `it("…")`, `property("…")` and `"…" in {…}` registration and every JUnit `@Test`, which is how munit, ScalaTest, utest, ZIO Test and specs2 declare a case; a case registered under a computed name is not counted, so this is a floor. Its tier split is INFERRED from paths and file names, except sbt's src/it source set, which the build declares.
D12 · Dependency Hygiene
5 outdated direct sbt declarations. 20 of 21 direct declarations were graded against Maven Central (1 not published there, which is what a private Nexus or Artifactory artifact looks like, 0 declaring a version range rather than an exact version). 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 · Secret Scanning
Secret scan ran and found no leaked secrets.
D14 · License Compliance
0 of 20 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 2 sbt build file(s) (build.sbt 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. 1 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. A further 1 coordinate(s) are not published to Maven Central — another repository (Google's Maven hosts androidx), a SNAPSHOT, or a private artifact — so their licences are not readable from here and they are outside this verdict.
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window.
D16 · Bus Factor
1 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is project/Dependencies.scala. Counted over 21 of the 77 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
D17 · Explicit Debt
0 deducted task-comment markers across 4490 LoC (0.0/KLoC) → score 10.0. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
D20 · ADR Quality
No architecture decision records were found.
What to do
- Resolve the 1 No ADRs found finding(s) in ADR Quality. — One of this dimension's main actionable groups (1 recommendation-level).
D26 · Project Cohesion
0 of 1 build units (sbt) flagged as possibly oversized/incoherent.
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
16 finding(s): 0 critical, 16 high, 0 medium, 0 low. 12 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens.
What to do
- Resolve the 4 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (3), REDACTED. — One of this dimension's main actionable groups (4 issue-level).
- No action in Static Analysis (SAST) — all 12 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 (12 issue-level, 0 of them charged here).
D30 · Dependency Vulnerabilities
No known-vulnerable dependencies in any ecosystem this repository declares.
D34 · Knowledge Freshness
Every significant source file has living knowledge — recently and meaningfully worked. Counted over 21 of the 77 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
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 recommendation-level).
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
Frontend & cross-cutting dimensions
AX10 · Code composition
What to do
- The domain core is a small share of production code, but most of the rest matched no layer vocabulary at all — so this is not yet an anemic-domain finding. The namespace/path convention could not place that code, which makes the composition above a statement about the naming, not about the design. Name the layers (or check that the repository's conventions differ from the ones this check knows) before reading a thin domain into it.
AX3 · Project dependency cycles
AX4 · Dependency direction
AX6 · Interface segregation
GD1 · Unfinished & placeholder code
IC1 · Incompleteness & stubs
M1 · Documentation (README)
- The root README is 80 words, against a bar of 120. Of the three newcomer-critical sections this check looks for by heading, in the README and in the repository documents it links, it found no a build/run or getting-started section, no a testing section, no an architecture or project-map section. Sections are matched on HEADING text only, so material written under a heading this check does not recognise — or with no heading at all — is not seen and this row may understate what the document covers. — README.md:1
What to do
- Expand the README with getting-started, architecture overview and a project map.
- Add a build/run (quick start) section to the root README — the first thing a newcomer needs.
- Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
- Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
M3 · Folder & project structure
M4 · Documentation accuracy
P1 · CI/CD gates
P10 · Library API & versioning
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.
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
X1 · Async correctness
X12 · Unreachable branch
X13 · Undrained process stream
X14 · Bypassable address classification
X15 · Unvalidated length from an untrusted reader
X16 · Unfloored truncation loop
X17 · Uncapped recursion over a caller-supplied document
X18 · Disposal-pattern correctness
X19 · Unrestored process-global state
X20 · Mistyped argument guard
X21 · Side-effecting pattern guard
X22 · Contradicted release guard
X23 · Unguarded diagnostic materialisation
X24 · Document value interpolated into markup unescaped
X25 · Inert configuration knob
X26 · Unsynchronised callback handoff
X27 · Collection changed while being enumerated
X28 · Index access outside its own emptiness guard
X29 · Per-element action decided by a fixed element
X3 · Exception handling
X30 · Support guard that admits what it rejects
X5 · Nullable reference types
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 98% | Exemplary | Solid. |
| Architecture | 98% | Exemplary | Solid. |
| Maturity | 62% | Adequate — gated by M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 68% | Adequate — gated by P3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 58% | Adequate — gated by D36 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Performance | 100% | Exemplary | Strongest area. |
Unscored — 1 check(s) recorded observations but carry no score
- P12 CI test-gate honesty — 1 observation(s) recorded · Reported, not scored — this card publishes what the CI gate does with the test inventory rather than grading it. The findings above are its output.
Not evidenced — 2 control(s) we could not find positive evidence for
- P4 Deployment & Rollback — not evidenced — no deploy/rollback/approval signal in the repo; absence of evidence is not evidence of a manual release
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 57 check(s) not relevant to this codebase
- AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
- AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
- AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
- AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
- AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
- AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
- AC7 A11y enforcement — No web markup found — accessibility is not applicable to this repository.
- AX1 Captive dependencies — Not applicable: this repository's Scala imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's.
- AX2 Stateful singletons — 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 — ~1618 lines of test source are present (.scala) 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
- 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 — Naming consistency is measured on C# and TypeScript only; Scala not measured.
- D22 Internal API Consistency — The exposed public-API surface could not be collected — no C#/VB projects loaded.
- D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D24 Comment Value — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only — this repository's production source is .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) — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- D39 IL Efficiency — D39 measures the IL emitted by a .NET build; this repository has no .NET solution or project files, so the dimension does not apply.
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- 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): 35 value object(s); 4 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
- P2 Observability — This repository's JVM source (1 module(s), 74 file(s) read) declares no entry point and bootstraps no server, and nothing here deploys a service — it is a library, run inside whatever hosts it, so production observability (structured logging, tracing/metrics, health checks) is N/A. If it grows a binary or a service, the dimension reactivates.
- 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 — no coverage report found on disk — produce a coverage report in a standard format (`addSbtPlugin("org.scoverage" % "sbt-scoverage" % "<version>")` in `project/plugins.sbt`, then `sbt clean coverage test coverageReport`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures, or wire coverage collection into CI, to enable this cross-layer check
- PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for `@Benchmark` in a Java, Kotlin or Scala file importing JMH or kotlinx-benchmark, Jetpack Benchmark's `measureRepeated` in a file importing androidx.benchmark, or JMH/kotlinx-benchmark/androidx.benchmark in a 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.
- S1 Web-Security Posture — No web surface: 73 Scala file(s) were read for weak hashes and ciphers, key material fixed in the source, disabled TLS certificate validation and obsolete TLS versions, and none was found. This repository builds on an HTTP-server library (project/Dependencies.scala:60 — depends on `http4s-dsl`) but serves no HTTP of its own: its production source starts no server (no `newServerAt`/`bindAndHandle`, server builder, `Server.serve`, `Http.serve`, tapir server interpreter or Netty HTTP pipeline), declares no application one runs (no Play application, servlet, cask `MainRoutes`, `HttpApp` or twitter-server), so it is a library whose server controls belong to the application that serves it — HTTPS enforcement, HSTS, cookie flags and input validation are N/A here, as they are for a C# library. If this codebase starts serving HTTP, the dimension reactivates automatically.
- X10 Duplicated predicate — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X2 Cancellation propagation — no C# was loaded; this repository's Scala was 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
- 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 Scala was read, and it logs through none that an interpolated message defeats: scala-logging takes an `s"…"` message apart into SLF4J's pattern and arguments at compile time, and log4s, grizzled-slf4j, Play's Logger, Akka's LoggingAdapter, sbt's Logger and Spark's Logging take one finished message (as log4net does in C#). Calls made straight through SLF4J (`org.slf4j.Logger`) 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 — 16 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
Serious — 27 finding(s)
- REDACTED
- REDACTED
- Members sharing a duplicated core (4 members, 50+ identical tokens) akka-runtime/src/main/scala/endless/runtime/akka/deploy/internal/DurableShardedRepositoryDeployer.scala:45
- Members sharing a duplicated core (4 members, 50+ identical tokens) akka-runtime/src/main/scala/endless/runtime/akka/deploy/internal/DurableShardedRepositoryDeployer.scala:85
- Duplicated block (24 lines × 2) akka-runtime/src/main/scala/endless/runtime/akka/deploy/internal/EventSourcedShardedRepositoryDeployer.scala:112
- Duplicated block (24 lines × 2) akka-runtime/src/main/scala/endless/runtime/akka/EntityPassivator.scala:27
- Duplicated block (21 lines × 2) akka-runtime/src/main/scala/endless/runtime/akka/deploy/internal/DurableShardedRepositoryDeployer.scala:49
- Duplicated block (21 lines × 2) akka-runtime/src/main/scala/endless/runtime/akka/serializer/ReplySerializer.scala:16
- AkkaCluster.managedResource (cognitive 31) akka-runtime/src/main/scala/endless/runtime/akka/deploy/AkkaCluster.scala:71
- PekkoCluster.managedResource (cognitive 31) pekko-runtime/src/main/scala/endless/runtime/pekko/deploy/PekkoCluster.scala:67
- AkkaCluster.createCluster (cognitive 21) akka-runtime/src/main/scala/endless/runtime/akka/deploy/AkkaCluster.scala:121
- PekkoCluster.createCluster (cognitive 21) pekko-runtime/src/main/scala/endless/runtime/pekko/deploy/PekkoCluster.scala:117
- REDACTED
- Duplicated block (36 lines × 2) akka-runtime/src/main/scala/endless/runtime/akka/protobuf/ScalaPbSerializer.scala:32
- Duplicated block (33 lines × 2) akka-runtime/src/main/scala/endless/runtime/akka/deploy/internal/DurableShardedRepositoryDeployer.scala:104
- Duplicated block (29 lines × 2) akka-runtime/src/main/scala/endless/runtime/akka/deploy/AkkaCluster.scala:80
- Duplicated block (21–22 lines × 2) akka-runtime/src/main/scala/endless/runtime/akka/deploy/internal/EventSourcedShardedRepositoryDeployer.scala:49
- Duplicated block (20 lines × 2) akka-runtime/src/main/scala/endless/runtime/akka/ShardingCommandSender.scala:40
- Duplicated block (17–18 lines × 4) akka-runtime/src/main/scala/endless/runtime/akka/deploy/internal/DurableShardedRepositoryDeployer.scala:59
- Duplicated block (11 lines × 4) akka-runtime/src/main/scala/endless/runtime/akka/deploy/internal/DurableShardedRepositoryDeployer.scala:86
- Duplicated block (7 lines × 2) akka-runtime/src/main/scala/endless/runtime/akka/deploy/internal/EventSourcedShardedRepositoryDeployer.scala:136
- Duplicated block (5 lines × 3) akka-runtime/src/main/scala/endless/runtime/akka/deploy/internal/DurableShardedRepositoryDeployer.scala:49
- Duplicated block (5 lines × 2) akka-runtime/src/main/scala/endless/runtime/akka/deploy/AkkaCluster.scala:124
- Duplicated block (32 lines × 2) akka-runtime/src/main/scala/endless/runtime/akka/serializer/CommandSerializer.scala:22
- Duplicated block (6 lines × 2) akka-runtime/src/main/scala/endless/runtime/akka/deploy/internal/EventSourcedShardedRepositoryDeployer.scala:99
- Duplicated block (17 lines × 2) example/src/main/scala/endless/example/app/akka/AkkaApp.scala:91
- Coverage collected but not gated
Minor — 7 finding(s)
- Off-boarding risk: anonymized user #1
- No ADRs found
- REDACTED
- REDACTED
- Thin README README.md:1
- No ADRs
- No changelog
Minor — 5 finding(s)
- Outdated: ch.qos.logback:logback-classic
- Outdated: org.http4s:http4s-blaze-client_2.13
- Outdated: org.http4s:http4s-blaze-server_2.13
- Outdated: org.http4s:http4s-circe_2.13
- Outdated: org.http4s:http4s-dsl_2.13
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-69ba0306b39a4389983a36ae25ca4df8/history.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-69ba0306b39a4389983a36ae25ca4df8/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 . | 16 | 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-e49ce3934c1b490589939d16bf8d8cd3 | 0 | 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. | 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-e49ce3934c1b490589939d16bf8d8cd3 | 0 | artifacts/raw/osv-scanner.json |