Executive summary
devsisters/shardcake falls short of our standard for production, held back most by its Production Readiness lens, the way the code is tested, built, released and run. It scores 63 out of 100 and is rated Adequate, and all 12 of its critical findings are security problems in the build pipeline.
Production Readiness, at 55, is the weakest lens and counts most in the score. The best first step is adding automated security scanning, worth about 6 points. Adding a release approval comes next, worth about 4 points. Raising Production Readiness to 70 would lift the score to about 69.
Eleven pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. One secret can leak from the build pipeline. Pinning each tool to an exact version and limiting the secret to its own step would close both risks.
The product code is 3,190 lines, about €4,500 to rebuild. The check for the health of its packages couldn't finish, so that result is missing, not a clean pass.
If Production Readiness rose from 55 to 70, the lowest score rated Strong, the score would rise from 63 to about 69.
Rebuild cost: about €4,500 · Estimate
| Cost to rebuild | €1,500 to €7,600, for 25 to 80 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 63. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it. |
| Size | Small: 3,190 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 devsisters | 2 devsisters.shardcake.K8sPodsHealth | 3 devsisters.shardcake.LocalSharding | 4 devsisters.shardcake.Messenger | 5 devsisters.shardcake.interfaces.Pods | 6 devsisters.shardcake.LocalSharding.LocalQueueMessage | 7 devsisters.shardcake.Messenger.MessengerTimeout | 8 devsisters.shardcake.ShardManager | 9 devsisters.shardcake.errors | 10 devsisters.shardcake.interfaces | 11 devsisters.shardcake.internal | 12 devsisters.shardcake.Sharding | 13 devsisters.shardcake.internal.EntityManager | 14 devsisters.shardcake.internal.ReplyChannel | 15 devsisters.shardcake | 16 devsisters.shardcake.ShardManager.ShardingEvent | 17 devsisters.shardcake.ShardManagerClient | 18 devsisters.shardcake.Sharding.ShardingRegistrationEvent | 19 devsisters.shardcake.internal.GraphQLClient | 20 devsisters.shardcake.internal.SendChannel | 21 devsisters.shardcake.GraphQLApi |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 devsisters | |||||||||||||||||||||
| 2 devsisters.shardcake.K8sPodsHealth | |||||||||||||||||||||
| 3 devsisters.shardcake.LocalSharding | |||||||||||||||||||||
| 4 devsisters.shardcake.Messenger | |||||||||||||||||||||
| 5 devsisters.shardcake.interfaces.Pods | |||||||||||||||||||||
| 6 devsisters.shardcake.LocalSharding.LocalQueueMessage | 4 | 4 | |||||||||||||||||||
| 7 devsisters.shardcake.Messenger.MessengerTimeout | 3 | ||||||||||||||||||||
| 8 devsisters.shardcake.ShardManager | 2 | ||||||||||||||||||||
| 9 devsisters.shardcake.errors | 2 | ||||||||||||||||||||
| 10 devsisters.shardcake.interfaces | 1 | 4 | |||||||||||||||||||
| 11 devsisters.shardcake.internal | 1 | 2 | 1 | ||||||||||||||||||
| 12 devsisters.shardcake.Sharding | 1 | ||||||||||||||||||||
| 13 devsisters.shardcake.internal.EntityManager | 1 | 2 | |||||||||||||||||||
| 14 devsisters.shardcake.internal.ReplyChannel | 2 | ||||||||||||||||||||
| 15 devsisters.shardcake | 1 | 1 | 2 | 1 | 6 | 2 | 1 | ||||||||||||||
| 16 devsisters.shardcake.ShardManager.ShardingEvent | 5 | 5 | |||||||||||||||||||
| 17 devsisters.shardcake.ShardManagerClient | 2 | ||||||||||||||||||||
| 18 devsisters.shardcake.Sharding.ShardingRegistrationEvent | 3 | 2 | |||||||||||||||||||
| 19 devsisters.shardcake.internal.GraphQLClient | 4 | ||||||||||||||||||||
| 20 devsisters.shardcake.internal.SendChannel | 4 | 2 | 2 | ||||||||||||||||||
| 21 devsisters.shardcake.GraphQLApi | 1 | 6 | 1 |
6→3 devsisters.shardcake.LocalSharding.LocalQueueMessage uses devsisters.shardcake.LocalSharding✕
- Connections
- 4 pairs of types, where a type in devsisters.shardcake.LocalSharding.LocalQueueMessage uses a type in devsisters.shardcake.LocalSharding.
- The types involved
com.devsisters.shardcake.LocalSharding.LocalQueueMessage.SendMessage→com.devsisters.shardcake.LocalSharding.LocalQueueMessagecom.devsisters.shardcake.LocalSharding.LocalQueueMessage.SendMessageAndReceiveStream→com.devsisters.shardcake.LocalSharding.LocalQueueMessagecom.devsisters.shardcake.LocalSharding.LocalQueueMessage.SendStream→com.devsisters.shardcake.LocalSharding.LocalQueueMessagecom.devsisters.shardcake.LocalSharding.LocalQueueMessage.SendStreamAndReceiveStream→com.devsisters.shardcake.LocalSharding.LocalQueueMessage
- Direction
- devsisters.shardcake.LocalSharding.LocalQueueMessage uses devsisters.shardcake.LocalSharding, so a change to devsisters.shardcake.LocalSharding can break devsisters.shardcake.LocalSharding.LocalQueueMessage, while a change to devsisters.shardcake.LocalSharding.LocalQueueMessage can't break devsisters.shardcake.LocalSharding.
- Position
- Below the diagonal: devsisters.shardcake.LocalSharding.LocalQueueMessage uses a module listed above it, which is the healthy direction.
6→5 devsisters.shardcake.LocalSharding.LocalQueueMessage uses devsisters.shardcake.interfaces.Pods✕
- Connections
- 4 pairs of types, where a type in devsisters.shardcake.LocalSharding.LocalQueueMessage uses a type in devsisters.shardcake.interfaces.Pods.
- The types involved
com.devsisters.shardcake.LocalSharding.LocalQueueMessage.SendMessage→com.devsisters.shardcake.interfaces.Pods.BinaryMessagecom.devsisters.shardcake.LocalSharding.LocalQueueMessage.SendMessageAndReceiveStream→com.devsisters.shardcake.interfaces.Pods.BinaryMessagecom.devsisters.shardcake.LocalSharding.LocalQueueMessage.SendStream→com.devsisters.shardcake.interfaces.Pods.BinaryMessagecom.devsisters.shardcake.LocalSharding.LocalQueueMessage.SendStreamAndReceiveStream→com.devsisters.shardcake.interfaces.Pods.BinaryMessage
- Direction
- devsisters.shardcake.LocalSharding.LocalQueueMessage uses devsisters.shardcake.interfaces.Pods, so a change to devsisters.shardcake.interfaces.Pods can break devsisters.shardcake.LocalSharding.LocalQueueMessage, while a change to devsisters.shardcake.LocalSharding.LocalQueueMessage can't break devsisters.shardcake.interfaces.Pods.
- Position
- Below the diagonal: devsisters.shardcake.LocalSharding.LocalQueueMessage uses a module listed above it, which is the healthy direction.
7→4 devsisters.shardcake.Messenger.MessengerTimeout uses devsisters.shardcake.Messenger✕
- Connections
- 3 pairs of types, where a type in devsisters.shardcake.Messenger.MessengerTimeout uses a type in devsisters.shardcake.Messenger.
- The types involved
com.devsisters.shardcake.Messenger.MessengerTimeout.InheritConfigTimeout→com.devsisters.shardcake.Messenger.MessengerTimeoutcom.devsisters.shardcake.Messenger.MessengerTimeout.NoTimeout→com.devsisters.shardcake.Messenger.MessengerTimeoutcom.devsisters.shardcake.Messenger.MessengerTimeout.Timeout→com.devsisters.shardcake.Messenger.MessengerTimeout
- Direction
- devsisters.shardcake.Messenger.MessengerTimeout uses devsisters.shardcake.Messenger, so a change to devsisters.shardcake.Messenger can break devsisters.shardcake.Messenger.MessengerTimeout, while a change to devsisters.shardcake.Messenger.MessengerTimeout can't break devsisters.shardcake.Messenger.
- Position
- Below the diagonal: devsisters.shardcake.Messenger.MessengerTimeout uses a module listed above it, which is the healthy direction.
8→15 devsisters.shardcake.ShardManager uses devsisters.shardcake part of a loop✕
- Connections
- 2 pairs of types, where a type in devsisters.shardcake.ShardManager uses a type in devsisters.shardcake.
- The types involved
com.devsisters.shardcake.ShardManager.PodWithMetadata→com.devsisters.shardcake.Podcom.devsisters.shardcake.ShardManager.ShardManagerState→com.devsisters.shardcake.PodAddress
- Direction
- devsisters.shardcake.ShardManager uses devsisters.shardcake, so a change to devsisters.shardcake can break devsisters.shardcake.ShardManager, while a change to devsisters.shardcake.ShardManager can't break devsisters.shardcake.
- 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.
9→15 devsisters.shardcake.errors uses devsisters.shardcake part of a loop✕
- Connections
- 2 pairs of types, where a type in devsisters.shardcake.errors uses a type in devsisters.shardcake.
- The types involved
com.devsisters.shardcake.errors.PodUnavailable→com.devsisters.shardcake.PodAddresscom.devsisters.shardcake.errors.SendTimeoutException→com.devsisters.shardcake.EntityType
- Direction
- devsisters.shardcake.errors uses devsisters.shardcake, so a change to devsisters.shardcake can break devsisters.shardcake.errors, while a change to devsisters.shardcake.errors can't break devsisters.shardcake.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
10→5 devsisters.shardcake.interfaces uses devsisters.shardcake.interfaces.Pods✕
- Connections
- 1 pair of types, where a type in devsisters.shardcake.interfaces uses a type in devsisters.shardcake.interfaces.Pods.
- The types involved
com.devsisters.shardcake.interfaces.Pods→com.devsisters.shardcake.interfaces.Pods.BinaryMessage
- Direction
- devsisters.shardcake.interfaces uses devsisters.shardcake.interfaces.Pods, so a change to devsisters.shardcake.interfaces.Pods can break devsisters.shardcake.interfaces, while a change to devsisters.shardcake.interfaces can't break devsisters.shardcake.interfaces.Pods.
- Position
- Below the diagonal: devsisters.shardcake.interfaces uses a module listed above it, which is the healthy direction.
10→15 devsisters.shardcake.interfaces uses devsisters.shardcake part of a loop✕
- Connections
- 4 pairs of types, where a type in devsisters.shardcake.interfaces uses a type in devsisters.shardcake.
- The types involved
com.devsisters.shardcake.interfaces.Pods→com.devsisters.shardcake.PodAddresscom.devsisters.shardcake.interfaces.PodsHealth→com.devsisters.shardcake.PodAddresscom.devsisters.shardcake.interfaces.Storage→com.devsisters.shardcake.Podcom.devsisters.shardcake.interfaces.Storage→com.devsisters.shardcake.PodAddress
- Direction
- devsisters.shardcake.interfaces uses devsisters.shardcake, so a change to devsisters.shardcake can break devsisters.shardcake.interfaces, while a change to devsisters.shardcake.interfaces can't break devsisters.shardcake.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
11→9 devsisters.shardcake.internal uses devsisters.shardcake.errors✕
- Connections
- 1 pair of types, where a type in devsisters.shardcake.internal uses a type in devsisters.shardcake.errors.
- The types involved
com.devsisters.shardcake.internal.EntityManager→com.devsisters.shardcake.errors.EntityNotManagedByThisPod
- Direction
- devsisters.shardcake.internal uses devsisters.shardcake.errors, so a change to devsisters.shardcake.errors can break devsisters.shardcake.internal, while a change to devsisters.shardcake.internal can't break devsisters.shardcake.errors.
- Position
- Below the diagonal: devsisters.shardcake.internal uses a module listed above it, which is the healthy direction.
11→10 devsisters.shardcake.internal uses devsisters.shardcake.interfaces✕
- Connections
- 2 pairs of types, where a type in devsisters.shardcake.internal uses a type in devsisters.shardcake.interfaces.
- The types involved
com.devsisters.shardcake.internal.SendChannel→com.devsisters.shardcake.interfaces.Podscom.devsisters.shardcake.internal.SendChannel→com.devsisters.shardcake.interfaces.Serialization
- Direction
- devsisters.shardcake.internal uses devsisters.shardcake.interfaces, so a change to devsisters.shardcake.interfaces can break devsisters.shardcake.internal, while a change to devsisters.shardcake.internal can't break devsisters.shardcake.interfaces.
- Position
- Below the diagonal: devsisters.shardcake.internal uses a module listed above it, which is the healthy direction.
11→15 devsisters.shardcake.internal uses devsisters.shardcake part of a loop✕
- Connections
- 1 pair of types, where a type in devsisters.shardcake.internal uses a type in devsisters.shardcake.
- The types involved
com.devsisters.shardcake.internal.SendChannel→com.devsisters.shardcake.PodAddress
- Direction
- devsisters.shardcake.internal uses devsisters.shardcake, so a change to devsisters.shardcake can break devsisters.shardcake.internal, while a change to devsisters.shardcake.internal can't break devsisters.shardcake.
- 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.
12→11 devsisters.shardcake.Sharding uses devsisters.shardcake.internal✕
- Connections
- 1 pair of types, where a type in devsisters.shardcake.Sharding uses a type in devsisters.shardcake.internal.
- The types involved
com.devsisters.shardcake.Sharding.EntityState→com.devsisters.shardcake.internal.EntityManager
- Direction
- devsisters.shardcake.Sharding uses devsisters.shardcake.internal, so a change to devsisters.shardcake.internal can break devsisters.shardcake.Sharding, while a change to devsisters.shardcake.Sharding can't break devsisters.shardcake.internal.
- Position
- Below the diagonal: devsisters.shardcake.Sharding uses a module listed above it, which is the healthy direction.
13→9 devsisters.shardcake.internal.EntityManager uses devsisters.shardcake.errors✕
- Connections
- 1 pair of types, where a type in devsisters.shardcake.internal.EntityManager uses a type in devsisters.shardcake.errors.
- The types involved
com.devsisters.shardcake.internal.EntityManager.EntityManagerLive→com.devsisters.shardcake.errors.EntityNotManagedByThisPod
- Direction
- devsisters.shardcake.internal.EntityManager uses devsisters.shardcake.errors, so a change to devsisters.shardcake.errors can break devsisters.shardcake.internal.EntityManager, while a change to devsisters.shardcake.internal.EntityManager can't break devsisters.shardcake.errors.
- Position
- Below the diagonal: devsisters.shardcake.internal.EntityManager uses a module listed above it, which is the healthy direction.
13→11 devsisters.shardcake.internal.EntityManager uses devsisters.shardcake.internal✕
- Connections
- 2 pairs of types, where a type in devsisters.shardcake.internal.EntityManager uses a type in devsisters.shardcake.internal.
- The types involved
com.devsisters.shardcake.internal.EntityManager.EntityManagerLive→com.devsisters.shardcake.internal.EntityManagercom.devsisters.shardcake.internal.EntityManager.EntityManagerLive→com.devsisters.shardcake.internal.ReplyChannel
- Direction
- devsisters.shardcake.internal.EntityManager uses devsisters.shardcake.internal, so a change to devsisters.shardcake.internal can break devsisters.shardcake.internal.EntityManager, while a change to devsisters.shardcake.internal.EntityManager can't break devsisters.shardcake.internal.
- Position
- Below the diagonal: devsisters.shardcake.internal.EntityManager uses a module listed above it, which is the healthy direction.
14→11 devsisters.shardcake.internal.ReplyChannel uses devsisters.shardcake.internal✕
- Connections
- 2 pairs of types, where a type in devsisters.shardcake.internal.ReplyChannel uses a type in devsisters.shardcake.internal.
- The types involved
com.devsisters.shardcake.internal.ReplyChannel.FromPromise→com.devsisters.shardcake.internal.ReplyChannelcom.devsisters.shardcake.internal.ReplyChannel.FromQueue→com.devsisters.shardcake.internal.ReplyChannel
- Direction
- devsisters.shardcake.internal.ReplyChannel uses devsisters.shardcake.internal, so a change to devsisters.shardcake.internal can break devsisters.shardcake.internal.ReplyChannel, while a change to devsisters.shardcake.internal.ReplyChannel can't break devsisters.shardcake.internal.
- Position
- Below the diagonal: devsisters.shardcake.internal.ReplyChannel uses a module listed above it, which is the healthy direction.
15→3 devsisters.shardcake uses devsisters.shardcake.LocalSharding✕
- Connections
- 1 pair of types, where a type in devsisters.shardcake uses a type in devsisters.shardcake.LocalSharding.
- The types involved
com.devsisters.shardcake.LocalSharding→com.devsisters.shardcake.LocalSharding.LocalQueue
- Direction
- devsisters.shardcake uses devsisters.shardcake.LocalSharding, so a change to devsisters.shardcake.LocalSharding can break devsisters.shardcake, while a change to devsisters.shardcake can't break devsisters.shardcake.LocalSharding.
- Position
- Below the diagonal: devsisters.shardcake uses a module listed above it, which is the healthy direction.
15→4 devsisters.shardcake uses devsisters.shardcake.Messenger✕
- Connections
- 1 pair of types, where a type in devsisters.shardcake uses a type in devsisters.shardcake.Messenger.
- The types involved
com.devsisters.shardcake.Sharding→com.devsisters.shardcake.Messenger.MessengerTimeout
- Direction
- devsisters.shardcake uses devsisters.shardcake.Messenger, so a change to devsisters.shardcake.Messenger can break devsisters.shardcake, while a change to devsisters.shardcake can't break devsisters.shardcake.Messenger.
- Position
- Below the diagonal: devsisters.shardcake uses a module listed above it, which is the healthy direction.
15→5 devsisters.shardcake uses devsisters.shardcake.interfaces.Pods✕
- Connections
- 2 pairs of types, where a type in devsisters.shardcake uses a type in devsisters.shardcake.interfaces.Pods.
- The types involved
com.devsisters.shardcake.GrpcPods→com.devsisters.shardcake.interfaces.Pods.BinaryMessagecom.devsisters.shardcake.Sharding→com.devsisters.shardcake.interfaces.Pods.BinaryMessage
- Direction
- devsisters.shardcake uses devsisters.shardcake.interfaces.Pods, so a change to devsisters.shardcake.interfaces.Pods can break devsisters.shardcake, while a change to devsisters.shardcake can't break devsisters.shardcake.interfaces.Pods.
- Position
- Below the diagonal: devsisters.shardcake uses a module listed above it, which is the healthy direction.
15→8 devsisters.shardcake uses devsisters.shardcake.ShardManager✕
- Connections
- 1 pair of types, where a type in devsisters.shardcake uses a type in devsisters.shardcake.ShardManager.
- The types involved
com.devsisters.shardcake.ShardManager→com.devsisters.shardcake.ShardManager.ShardingEvent
- Direction
- devsisters.shardcake uses devsisters.shardcake.ShardManager, so a change to devsisters.shardcake.ShardManager can break devsisters.shardcake, while a change to devsisters.shardcake can't break devsisters.shardcake.ShardManager.
- Position
- Below the diagonal: devsisters.shardcake uses a module listed above it, which is the healthy direction.
15→10 devsisters.shardcake uses devsisters.shardcake.interfaces✕
- Connections
- 6 pairs of types, where a type in devsisters.shardcake uses a type in devsisters.shardcake.interfaces.
- The types involved
com.devsisters.shardcake.GrpcPods→com.devsisters.shardcake.interfaces.Podscom.devsisters.shardcake.K8sPodsHealth→com.devsisters.shardcake.interfaces.Podscom.devsisters.shardcake.K8sPodsHealth→com.devsisters.shardcake.interfaces.PodsHealthcom.devsisters.shardcake.KryoSerialization→com.devsisters.shardcake.interfaces.Serializationcom.devsisters.shardcake.LocalSharding→com.devsisters.shardcake.interfaces.Podscom.devsisters.shardcake.StorageRedis→com.devsisters.shardcake.interfaces.Storage
- Direction
- devsisters.shardcake uses devsisters.shardcake.interfaces, so a change to devsisters.shardcake.interfaces can break devsisters.shardcake, while a change to devsisters.shardcake can't break devsisters.shardcake.interfaces.
- Position
- Below the diagonal: devsisters.shardcake uses a module listed above it, which is the healthy direction.
15→11 devsisters.shardcake uses devsisters.shardcake.internal✕
- Connections
- 2 pairs of types, where a type in devsisters.shardcake uses a type in devsisters.shardcake.internal.
- The types involved
com.devsisters.shardcake.Sharding→com.devsisters.shardcake.internal.ReplyChannelcom.devsisters.shardcake.Sharding→com.devsisters.shardcake.internal.SendChannel
- Direction
- devsisters.shardcake uses devsisters.shardcake.internal, so a change to devsisters.shardcake.internal can break devsisters.shardcake, while a change to devsisters.shardcake can't break devsisters.shardcake.internal.
- Position
- Below the diagonal: devsisters.shardcake uses a module listed above it, which is the healthy direction.
15→12 devsisters.shardcake uses devsisters.shardcake.Sharding✕
- Connections
- 1 pair of types, where a type in devsisters.shardcake uses a type in devsisters.shardcake.Sharding.
- The types involved
com.devsisters.shardcake.Sharding→com.devsisters.shardcake.Sharding.ShardingRegistrationEvent
- Direction
- devsisters.shardcake uses devsisters.shardcake.Sharding, so a change to devsisters.shardcake.Sharding can break devsisters.shardcake, while a change to devsisters.shardcake can't break devsisters.shardcake.Sharding.
- Position
- Below the diagonal: devsisters.shardcake uses a module listed above it, which is the healthy direction.
16→8 devsisters.shardcake.ShardManager.ShardingEvent uses devsisters.shardcake.ShardManager✕
- Connections
- 5 pairs of types, where a type in devsisters.shardcake.ShardManager.ShardingEvent uses a type in devsisters.shardcake.ShardManager.
- The types involved
com.devsisters.shardcake.ShardManager.ShardingEvent.PodHealthChecked→com.devsisters.shardcake.ShardManager.ShardingEventcom.devsisters.shardcake.ShardManager.ShardingEvent.PodRegistered→com.devsisters.shardcake.ShardManager.ShardingEventcom.devsisters.shardcake.ShardManager.ShardingEvent.PodUnregistered→com.devsisters.shardcake.ShardManager.ShardingEventcom.devsisters.shardcake.ShardManager.ShardingEvent.ShardsAssigned→com.devsisters.shardcake.ShardManager.ShardingEventcom.devsisters.shardcake.ShardManager.ShardingEvent.ShardsUnassigned→com.devsisters.shardcake.ShardManager.ShardingEvent
- Direction
- devsisters.shardcake.ShardManager.ShardingEvent uses devsisters.shardcake.ShardManager, so a change to devsisters.shardcake.ShardManager can break devsisters.shardcake.ShardManager.ShardingEvent, while a change to devsisters.shardcake.ShardManager.ShardingEvent can't break devsisters.shardcake.ShardManager.
- Position
- Below the diagonal: devsisters.shardcake.ShardManager.ShardingEvent uses a module listed above it, which is the healthy direction.
16→15 devsisters.shardcake.ShardManager.ShardingEvent uses devsisters.shardcake✕
- Connections
- 5 pairs of types, where a type in devsisters.shardcake.ShardManager.ShardingEvent uses a type in devsisters.shardcake.
- The types involved
com.devsisters.shardcake.ShardManager.ShardingEvent.PodHealthChecked→com.devsisters.shardcake.PodAddresscom.devsisters.shardcake.ShardManager.ShardingEvent.PodRegistered→com.devsisters.shardcake.PodAddresscom.devsisters.shardcake.ShardManager.ShardingEvent.PodUnregistered→com.devsisters.shardcake.PodAddresscom.devsisters.shardcake.ShardManager.ShardingEvent.ShardsAssigned→com.devsisters.shardcake.PodAddresscom.devsisters.shardcake.ShardManager.ShardingEvent.ShardsUnassigned→com.devsisters.shardcake.PodAddress
- Direction
- devsisters.shardcake.ShardManager.ShardingEvent uses devsisters.shardcake, so a change to devsisters.shardcake can break devsisters.shardcake.ShardManager.ShardingEvent, while a change to devsisters.shardcake.ShardManager.ShardingEvent can't break devsisters.shardcake.
- Position
- Below the diagonal: devsisters.shardcake.ShardManager.ShardingEvent uses a module listed above it, which is the healthy direction.
17→15 devsisters.shardcake.ShardManagerClient uses devsisters.shardcake✕
- Connections
- 2 pairs of types, where a type in devsisters.shardcake.ShardManagerClient uses a type in devsisters.shardcake.
- The types involved
com.devsisters.shardcake.ShardManagerClient.ShardManagerClientLive→com.devsisters.shardcake.PodAddresscom.devsisters.shardcake.ShardManagerClient.ShardManagerClientLive→com.devsisters.shardcake.ShardManagerClient
- Direction
- devsisters.shardcake.ShardManagerClient uses devsisters.shardcake, so a change to devsisters.shardcake can break devsisters.shardcake.ShardManagerClient, while a change to devsisters.shardcake.ShardManagerClient can't break devsisters.shardcake.
- Position
- Below the diagonal: devsisters.shardcake.ShardManagerClient uses a module listed above it, which is the healthy direction.
18→12 devsisters.shardcake.Sharding.ShardingRegistrationEvent uses devsisters.shardcake.Sharding✕
- Connections
- 3 pairs of types, where a type in devsisters.shardcake.Sharding.ShardingRegistrationEvent uses a type in devsisters.shardcake.Sharding.
- The types involved
com.devsisters.shardcake.Sharding.ShardingRegistrationEvent.EntityRegistered→com.devsisters.shardcake.Sharding.ShardingRegistrationEventcom.devsisters.shardcake.Sharding.ShardingRegistrationEvent.SingletonRegistered→com.devsisters.shardcake.Sharding.ShardingRegistrationEventcom.devsisters.shardcake.Sharding.ShardingRegistrationEvent.TopicRegistered→com.devsisters.shardcake.Sharding.ShardingRegistrationEvent
- Direction
- devsisters.shardcake.Sharding.ShardingRegistrationEvent uses devsisters.shardcake.Sharding, so a change to devsisters.shardcake.Sharding can break devsisters.shardcake.Sharding.ShardingRegistrationEvent, while a change to devsisters.shardcake.Sharding.ShardingRegistrationEvent can't break devsisters.shardcake.Sharding.
- Position
- Below the diagonal: devsisters.shardcake.Sharding.ShardingRegistrationEvent uses a module listed above it, which is the healthy direction.
18→15 devsisters.shardcake.Sharding.ShardingRegistrationEvent uses devsisters.shardcake✕
- Connections
- 2 pairs of types, where a type in devsisters.shardcake.Sharding.ShardingRegistrationEvent uses a type in devsisters.shardcake.
- The types involved
com.devsisters.shardcake.Sharding.ShardingRegistrationEvent.EntityRegistered→com.devsisters.shardcake.EntityTypecom.devsisters.shardcake.Sharding.ShardingRegistrationEvent.TopicRegistered→com.devsisters.shardcake.TopicType
- Direction
- devsisters.shardcake.Sharding.ShardingRegistrationEvent uses devsisters.shardcake, so a change to devsisters.shardcake can break devsisters.shardcake.Sharding.ShardingRegistrationEvent, while a change to devsisters.shardcake.Sharding.ShardingRegistrationEvent can't break devsisters.shardcake.
- Position
- Below the diagonal: devsisters.shardcake.Sharding.ShardingRegistrationEvent uses a module listed above it, which is the healthy direction.
19→15 devsisters.shardcake.internal.GraphQLClient uses devsisters.shardcake✕
- Connections
- 4 pairs of types, where a type in devsisters.shardcake.internal.GraphQLClient uses a type in devsisters.shardcake.
- The types involved
com.devsisters.shardcake.internal.GraphQLClient.Assignment→com.devsisters.shardcake.PodAddresscom.devsisters.shardcake.internal.GraphQLClient.PodAddress→com.devsisters.shardcake.PodAddresscom.devsisters.shardcake.internal.GraphQLClient.ShardsAssigned→com.devsisters.shardcake.PodAddresscom.devsisters.shardcake.internal.GraphQLClient.ShardsUnassigned→com.devsisters.shardcake.PodAddress
- Direction
- devsisters.shardcake.internal.GraphQLClient uses devsisters.shardcake, so a change to devsisters.shardcake can break devsisters.shardcake.internal.GraphQLClient, while a change to devsisters.shardcake.internal.GraphQLClient can't break devsisters.shardcake.
- Position
- Below the diagonal: devsisters.shardcake.internal.GraphQLClient uses a module listed above it, which is the healthy direction.
20→10 devsisters.shardcake.internal.SendChannel uses devsisters.shardcake.interfaces✕
- Connections
- 4 pairs of types, where a type in devsisters.shardcake.internal.SendChannel uses a type in devsisters.shardcake.interfaces.
- The types involved
com.devsisters.shardcake.internal.SendChannel.Single→com.devsisters.shardcake.interfaces.Podscom.devsisters.shardcake.internal.SendChannel.Single→com.devsisters.shardcake.interfaces.Serializationcom.devsisters.shardcake.internal.SendChannel.Stream→com.devsisters.shardcake.interfaces.Podscom.devsisters.shardcake.internal.SendChannel.Stream→com.devsisters.shardcake.interfaces.Serialization
- Direction
- devsisters.shardcake.internal.SendChannel uses devsisters.shardcake.interfaces, so a change to devsisters.shardcake.interfaces can break devsisters.shardcake.internal.SendChannel, while a change to devsisters.shardcake.internal.SendChannel can't break devsisters.shardcake.interfaces.
- Position
- Below the diagonal: devsisters.shardcake.internal.SendChannel uses a module listed above it, which is the healthy direction.
20→11 devsisters.shardcake.internal.SendChannel uses devsisters.shardcake.internal✕
- Connections
- 2 pairs of types, where a type in devsisters.shardcake.internal.SendChannel uses a type in devsisters.shardcake.internal.
- The types involved
com.devsisters.shardcake.internal.SendChannel.Single→com.devsisters.shardcake.internal.SendChannelcom.devsisters.shardcake.internal.SendChannel.Stream→com.devsisters.shardcake.internal.SendChannel
- Direction
- devsisters.shardcake.internal.SendChannel uses devsisters.shardcake.internal, so a change to devsisters.shardcake.internal can break devsisters.shardcake.internal.SendChannel, while a change to devsisters.shardcake.internal.SendChannel can't break devsisters.shardcake.internal.
- Position
- Below the diagonal: devsisters.shardcake.internal.SendChannel uses a module listed above it, which is the healthy direction.
20→15 devsisters.shardcake.internal.SendChannel uses devsisters.shardcake✕
- Connections
- 2 pairs of types, where a type in devsisters.shardcake.internal.SendChannel uses a type in devsisters.shardcake.
- The types involved
com.devsisters.shardcake.internal.SendChannel.Single→com.devsisters.shardcake.PodAddresscom.devsisters.shardcake.internal.SendChannel.Stream→com.devsisters.shardcake.PodAddress
- Direction
- devsisters.shardcake.internal.SendChannel uses devsisters.shardcake, so a change to devsisters.shardcake can break devsisters.shardcake.internal.SendChannel, while a change to devsisters.shardcake.internal.SendChannel can't break devsisters.shardcake.
- Position
- Below the diagonal: devsisters.shardcake.internal.SendChannel uses a module listed above it, which is the healthy direction.
21→8 devsisters.shardcake.GraphQLApi uses devsisters.shardcake.ShardManager✕
- Connections
- 1 pair of types, where a type in devsisters.shardcake.GraphQLApi uses a type in devsisters.shardcake.ShardManager.
- The types involved
com.devsisters.shardcake.GraphQLApi.Subscriptions→com.devsisters.shardcake.ShardManager.ShardingEvent
- Direction
- devsisters.shardcake.GraphQLApi uses devsisters.shardcake.ShardManager, so a change to devsisters.shardcake.ShardManager can break devsisters.shardcake.GraphQLApi, while a change to devsisters.shardcake.GraphQLApi can't break devsisters.shardcake.ShardManager.
- Position
- Below the diagonal: devsisters.shardcake.GraphQLApi uses a module listed above it, which is the healthy direction.
21→15 devsisters.shardcake.GraphQLApi uses devsisters.shardcake✕
- Connections
- 6 pairs of types, where a type in devsisters.shardcake.GraphQLApi uses a type in devsisters.shardcake.
- The types involved
com.devsisters.shardcake.GraphQLApi.Assignment→com.devsisters.shardcake.PodAddresscom.devsisters.shardcake.GraphQLApi.Mutations→com.devsisters.shardcake.Podcom.devsisters.shardcake.GraphQLApi.Mutations→com.devsisters.shardcake.ShardManagercom.devsisters.shardcake.GraphQLApi.PodAddressArgs→com.devsisters.shardcake.PodAddresscom.devsisters.shardcake.GraphQLApi.Queries→com.devsisters.shardcake.ShardManagercom.devsisters.shardcake.GraphQLApi.Subscriptions→com.devsisters.shardcake.ShardManager
- Direction
- devsisters.shardcake.GraphQLApi uses devsisters.shardcake, so a change to devsisters.shardcake can break devsisters.shardcake.GraphQLApi, while a change to devsisters.shardcake.GraphQLApi can't break devsisters.shardcake.
- Position
- Below the diagonal: devsisters.shardcake.GraphQLApi uses a module listed above it, which is the healthy direction.
21→19 devsisters.shardcake.GraphQLApi uses devsisters.shardcake.internal.GraphQLClient✕
- Connections
- 1 pair of types, where a type in devsisters.shardcake.GraphQLApi uses a type in devsisters.shardcake.internal.GraphQLClient.
- The types involved
com.devsisters.shardcake.GraphQLApi.Queries→com.devsisters.shardcake.internal.GraphQLClient.Assignment
- Direction
- devsisters.shardcake.GraphQLApi uses devsisters.shardcake.internal.GraphQLClient, so a change to devsisters.shardcake.internal.GraphQLClient can break devsisters.shardcake.GraphQLApi, while a change to devsisters.shardcake.GraphQLApi can't break devsisters.shardcake.internal.GraphQLClient.
- Position
- Below the diagonal: devsisters.shardcake.GraphQLApi 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 | 12 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 6 | Medium |
Roadmap
Top priorities: Add a SAST step to CI running what this repository's stack ships: scalafix or scapegoat — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing; Nothing pauses a release for a human: publish as a draft release (or gate the release job on a protected tag/manual dispatch) so a bad build can be stopped before users can download it; Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Add a SAST step to CI running what this repository's stack ships: scalafix or scapegoat — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing. | +6.5 pts | Medium | Security & performance tooling |
| Nothing pauses a release for a human: publish as a draft release (or gate the release job on a protected tag/manual dispatch) so a bad build can be stopped before users can download it. | +3.7 pts | Medium | Deployment & Rollback |
| Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release. | +3.7 pts | Medium | Release Hygiene |
| Expand the README with getting-started, architecture overview and a project map. | +2.3 pts | Medium | Documentation (README) |
| Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them. | +2.2 pts | Medium | Architecture documentation |
| Resolve the 2 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED. | +0.6 pts | Low | Supply-chain Provenance & Signing |
| Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. | +0.6 pts | Low | Static Analysis (SAST) |
| On Scala 3, add `-Yexplicit-nulls` to `scalacOptions` so `String` and `String | Null` mean different things, and type each Java API's result as nullable where it can return null; on Scala 2 (or as a first step), enable WartRemover's `Null` wart (`wartremoverErrors += Wart.Null`) or Scalafix's `DisableSyntax.noNulls = true` so the code holds absence in `Option`. Then pay the assertions down rather than adding to them: each `.nn` is a null the compiler could not rule out — wrap the Java value in `Option(…)` at the boundary, pattern-match on `null` once there, or change the API so the null cannot arrive; an `unsafeNulls` import switches the checking off for everything after it. | +1.1 pts | Medium | Nullable reference types |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 2.3 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 3.0 | Slop | Static Analysis (SAST): High: REDACTED |
| manager/src/main/scala/com/devsisters/shardcake/ShardManager.scala | 7.2 | Mixed | Cyclomatic Complexity: ShardManager.rebalance (cyclomatic 16) |
| protocol-grpc/src/main/scala/com/devsisters/shardcake/GrpcPods.scala | 7.4 | Mixed | Cognitive Complexity: GrpcPods.getConnection (cognitive 24) |
| entities/src/main/scala/com/devsisters/shardcake/Sharding.scala | 7.4 | Mixed | God Classes: FileTooLong: shardcake/Sharding.scala |
| entities/src/main/scala/com/devsisters/shardcake/Messenger.scala | 8.5 | Near-clean | Code Duplication: Duplicated block (8 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 56 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 — 56 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, 30 of 38 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 MEASURED: test source is present (.scala) but the built-in coverage collector has no runner for this repository's ecosystem — so this suite was never executed by it. Not scored — this is a gap in the analyzer's language coverage, not a defect in the repo. To have real coverage read, produce a coverage report in a standard format (`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, 10 test files), but it was not re-run: the analyzer environment could not run it. Not scored — this is a gap in the analyzer's language coverage, not a finding about this repository.
- D12 Dependency Hygiene — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This repository's dependency manifests WERE read and their pinning discipline assessed; what went unanswered is the currency half, because repo1.maven.org — the registry that answers it — was asked and did not reply (HTTP 429 Too Many Requests from http://172.31.7.1:8790/maven/com/coralogix/zio-k8s-client_2.13/maven-metadata.xml). This is OUR side and it is an ENVIRONMENT fault, not a missing collector: the collector exists and ran. An HTTP 403 here is what this scan's egress allowlist returns for a host that is not on it, so the remedy is to add repo1.maven.org to the allowlist and re-run — not to build anything.
- D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Single-maintainer repository — bus factor is not applicable (25 contributor(s) across 225 commit(s) sampled, automation and bot accounts excluded). One of them holds 81% of the history; the other 24 hold 0.8% each on average, below the 5% at which there is somebody to hand the work to. That is a single maintainer with drive-by contributors, not a team whose knowledge has concentrated — so the bus factor is not applicable and there is nothing here for the owner to act on.
- 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. For npm the surface is what a published package.json's entry points (exports, main, module, types) export, followed through the source; an entry that names build output the tree does not commit (dist/, build/) is not followed back to source, because only a tsconfig outDir/rootDir pair states that mapping and a bundler's input lives in executable configuration this engine does not evaluate.
- D24 Comment Value — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Each source language's comment syntax, and the code a comment annotates in it, needs its own proof before D24 judges it. Until then those comments are left unread, not counted as clean.
- D27 Navigability — 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 (ZIO HTTP), 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.
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.
- 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.
- 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").
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
- P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
Dimensions
D1 · Cyclomatic Complexity
1 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was ShardManager.rebalance at 16.
What to do
- Bring the 1 body over 15 down to 15 or less in Cyclomatic Complexity — start with ShardManager.rebalance (cyclomatic 16). — Refactoring it lifts Cyclomatic Complexity from 9.9 to about 10.0/10.
- Enforce Cyclomatic Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D2 · Cognitive Complexity
4 method(s) exceeded the cognitive complexity threshold of 15; the worst was ShardManager.rebalance at 59.
What to do
- Bring the 4 bodies over 15 down to 15 or less in Cognitive Complexity — start with ShardManager.rebalance (cognitive 59), ShardManager.unregister (cognitive 50), GrpcPods.getConnection (cognitive 24). — 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.0 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
1 over-large unit(s) detected — types, modules or files that carry too much.
What to do
- Resolve the 1 FileTooLong finding(s) in God Classes — start with Sharding.scala. — One of this dimension's main actionable groups (1 warning-level).
- Enforce God Classes in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D4 · Code Duplication
5 duplicated block group(s) detected.
What to do
- Resolve the 2 Duplicated block (14 lines × 2) finding(s) in Code Duplication — start with Sharding.scala (2). — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 Duplicated block (12 lines × 2) finding(s) in Code Duplication — start with GrpcPods.scala. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Duplicated block (8 lines × 2) finding(s) in Code Duplication — start with Messenger.scala. — One of this dimension's main actionable groups (1 warning-level).
- Enforce Code Duplication in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D5 · Coupling
9 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 8 of the 9 (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).
D9 · Test Distribution
32 test methods: 31 unit, 0 integration, 0 BDD, 1 e2e. The Scala suite contributes 32 test case(s) across 10 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.
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window.
D17 · Explicit Debt
0 deducted task-comment markers across 3190 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.
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)
12 finding(s): 0 critical, 12 high, 0 medium, 0 low. 11 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. Separately, one or more rules could not re-parse an embedded snippet in 1 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.
What to do
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- No action in Static Analysis (SAST) — all 11 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 (11 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 16 of the 46 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
AX3 · Project dependency cycles
AX4 · Dependency direction
AX6 · Interface segregation
GD1 · Unfinished & placeholder code
IC1 · Incompleteness & stubs
M1 · Documentation (README)
- The root README is 89 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.
- Add a README to the 1 of 1 project(s) that lack one — worth up to 2 pts.
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
M3 · Folder & project structure
P1 · CI/CD gates
P10 · Library API & versioning
P3 · Security & performance tooling
- No static application security testing detected. For this repository's stack, add scalafix or scapegoat (or `semgrep --config=auto`, which runs on any language) as a CI step. What was searched, so you can tell an absence from a miss: the 2479 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner. — REDACTED:4
- `vuepress/package.json` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`. — vuepress/package.json:2
What to do
- Add a SAST step to CI running what this repository's stack ships: scalafix or scapegoat — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing.
- Enable Dependabot/Renovate or a dependency-review gate.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
- The release is automated and no gate that pauses it for a human is DECLARED IN THIS REPOSITORY'S PIPELINE FILES. What was read: every file under `.github/workflows/`, `.forgejo/workflows/`, `.gitea/workflows/`, `.azuredevops/` and `.azure-pipelines/`, plus `.gitlab-ci*` and `azure-pipelines*` — with comment text stripped, so documenting a gate is not declaring one. What would have counted: GitLab's `when: manual`, CircleCI's `type: approval`, an Azure `ManualValidation@` task or an `approvals:` block, a Jenkins `input` step, a `uses:` step naming an approval action, an `environment:` paired with `reviewers` / `required_reviewers` / `protection` / `wait-timer` / `deployment_branch_policy`, a draft-release step, a `workflow_dispatch` promotion, or a release-event gate. ★ What this cannot see, because none of it is a file: a GitHub environment whose required reviewers are configured in repo SETTINGS, a branch protection rule, or an organisation deployment policy — all of them real, enforced gates that live outside the repository. If yours is one of those, this row is wrong and nothing in the tree could have told us. Otherwise: whatever the release trigger points at is published to users unreviewed, so a mistagged or unverified commit ships and the only remedy is a follow-up release.
What to do
- Nothing pauses a release for a human: publish as a draft release (or gate the release job on a protected tag/manual dispatch) so a bad build can be stopped before users can download it.
P6 · Release Hygiene
- No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
What to do
- Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.
PF1 · Benchmark discipline
- A JMH/Jetpack Benchmark suite exists but nothing turns on its allocation measurement — allocations (the main way hot code pressures a garbage collector or allocator) aren't being measured. — benchmarks/src/main/scala/com/devsisters/shardcake/SendBenchmark.scala
What to do
- Run JMH with the GC profiler (`-prof gc`, or addProfiler(GCProfiler.class)) so allocation rate regressions are visible, not just time.
PF2 · Allocation hygiene
What to do
- None of the allocation-aware idioms this check reads was found in the Scala production code (Scala: value classes (AnyVal), @specialized, primitive collections, presized builders). If this code sits on a hot path, these reduce the allocation pressure it creates — a bonus, not a requirement.
- Scala: on hot paths, make small wrappers value classes (extends AnyVal), @specialized generic code over primitives, use primitive collections, and presize builders.
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
- No build over this repository's 41 Scala product file(s) passes `-Yexplicit-nulls`, enables WartRemover's `Null` wart or runs Scalafix's `DisableSyntax.noNulls`, so every reference type admits null and nothing reports a `null` written into the code or returned from a Java API — the first one to reach a method call is a `NullPointerException`. `Option` by convention is a habit no tool here holds the code to.
What to do
- On Scala 3, add `-Yexplicit-nulls` to `scalacOptions` so `String` and `String | Null` mean different things, and type each Java API's result as nullable where it can return null; on Scala 2 (or as a first step), enable WartRemover's `Null` wart (`wartremoverErrors += Wart.Null`) or Scalafix's `DisableSyntax.noNulls = true` so the code holds absence in `Option`. Then pay the assertions down rather than adding to them: each `.nn` is a null the compiler could not rule out — wrap the Java value in `Option(…)` at the boundary, pattern-match on `null` once there, or change the API so the null cannot arrive; an `unsafeNulls` import switches the checking off for everything after it.
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 74% | Adequate — gated by X5 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 99% | Exemplary | Strongest area. |
| Maturity | 64% | Adequate | Acceptable, with room to improve. |
| Readiness | 55% | Adequate — gated by P3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 70% | Adequate — gated by D36 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Performance | 76% | Strong | Solid. |
Unscored — 1 check(s) recorded observations but carry no score
- SC1 Supply-chain hygiene — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 1 control(s) we could not find positive evidence for
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 62 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 — ~846 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
- D12 Dependency Hygiene — Dependency currency not established — repo1.maven.org did not answer
- D14 License Compliance — Not scored — this repository's 17 pinned sbt dependency coordinate(s) were read from its 1 sbt build file(s), but Maven Central could not be asked for the licence of 17 of them (HTTP 429 Too Many Requests from http://172.31.7.1:8790/maven/com/coralogix/zio-k8s-client_2.13/3.2.0/zio-k8s-client_2.13-3.2.0.pom), and a licence verdict over part of a dependency graph is not a licence verdict. Nothing is asserted about this repository's licensing in either direction.
- D16 Bus Factor — single-maintainer repository — bus factor is not applicable
- D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
- 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.
- D20 ADR Quality — N/A — ADRs are expected on deployable products with a user-facing host, not consumed libraries; no ADR log is required 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; comments in this repository's .scala source were not judged.
- 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
- D6 Cohesion (LCOM4) — Cohesion (LCOM4) was not measured: of the 68 type(s) found, none both holds instance state and has two or more methods whose shared use of it could be read (48 with fewer than two methods, 17 stateless, 3 stub-like), so LCOM4 is undefined for every type in this repository. Not scored — the metric does not apply here, and this is not a finding about this repository.
- 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): 44 value object(s); 2 domain event(s); its domain events are published by services or handlers — no domain entity raises one
- ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
- ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- M4 Documentation accuracy — Not applicable: the 9 current-state document(s) make no claim of a kind M4 checks.
- P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
- P2 Observability — This repository's JVM source (1 module(s), 41 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, JavaScript/TypeScript 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
- S1 Web-Security Posture — No web surface: 41 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 (manager/src/main/scala/com/devsisters/shardcake/Server.scala:5 — `zio.http`) 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 — 12 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
Serious — 15 finding(s)
- REDACTED
- REDACTED
- Duplicated block (14 lines × 2) entities/src/main/scala/com/devsisters/shardcake/Sharding.scala:386
- Duplicated block (14 lines × 2) entities/src/main/scala/com/devsisters/shardcake/Sharding.scala:401
- ShardManager.rebalance (cyclomatic 16) manager/src/main/scala/com/devsisters/shardcake/ShardManager.scala:95
- ShardManager.rebalance (cognitive 59) manager/src/main/scala/com/devsisters/shardcake/ShardManager.scala:95
- ShardManager.unregister (cognitive 50) manager/src/main/scala/com/devsisters/shardcake/ShardManager.scala:67
- GrpcPods.getConnection (cognitive 24) protocol-grpc/src/main/scala/com/devsisters/shardcake/GrpcPods.scala:18
- ShardManager.register (cognitive 21) manager/src/main/scala/com/devsisters/shardcake/ShardManager.scala:33
- FileTooLong: shardcake/Sharding.scala entities/src/main/scala/com/devsisters/shardcake/Sharding.scala
- REDACTED
- Duplicated block (12 lines × 2) protocol-grpc/src/main/scala/com/devsisters/shardcake/GrpcPods.scala:99
- Duplicated block (8 lines × 2) entities/src/main/scala/com/devsisters/shardcake/Messenger.scala:60
- Duplicated block (6 lines × 2) protocol-grpc/src/main/scala/com/devsisters/shardcake/GrpcPods.scala:77
- JavaScript dependencies are not locked vuepress/package.json:2
Minor — 11 finding(s)
- REDACTED
- REDACTED
- REDACTED
- Thin README README.md:1
- No ADRs
- No SAST REDACTED:4
- No dependency-update automation vuepress/package.json:2
- No release approval gate
- No changelog
- Benchmarks don't track allocations benchmarks/src/main/scala/com/devsisters/shardcake/SendBenchmark.scala
- Scala's null is not held to the type system everywhere
Appendix B — Reproduction & audit trail
| Dimension | Tool | Version | Command | Findings | Raw output |
|---|---|---|---|---|---|
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-c40287e36a0841c59d86e47658242688/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-c40287e36a0841c59d86e47658242688/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 . | 12 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . --skip-db-update | 0 | artifacts/raw/trivy-fs.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 | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . --skip-db-update | 0 | artifacts/raw/trivy-fs.json |