Executive summary
zio/zio-redis falls short of our standard for production, in part because it has pipeline tools referenced by a changeable name. It scores 65 out of 100 and is rated Adequate, and all 51 of its critical findings are security problems.
Security and Compliance, at 59, is the weakest lens and counts most in the score. The best first step is restoring certificate checks, worth about 4 points. Stopping the 12 pipeline steps that hand secrets to unpinned tools would lift Security and Compliance itself, also worth about 4. Raising Security and Compliance to 70 would lift the score to about 69.
Thirty-seven pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Thirteen secrets can leak from the build pipeline. Pinning each tool to an exact version and limiting each secret to its own step would close both risks. Switching the validation back on would fix the security check on connections or logins switched off.
The product code is 10,387 lines, about €33,000 to rebuild. The check for the health of its packages couldn't finish, so that result is missing, not a clean pass.
If Security and Compliance rose from 59 to 70, the lowest score rated Strong, the score would rise from 65 to about 69.
Rebuild cost: about €33,000 · Estimate
| Cost to rebuild | €11,000 to €54,000, for 181 to 573 hours of work, about 0.2 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 65. 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: 10,387 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 internal.PubSub | 2 internal.RespValue.internal | 3 internal.SingleNodeSubscriptionExecutor | 4 options.Geo | 5 options.Keys | 6 options.Lists | 7 options.Scripting | 8 options.Shared | 9 options.SortedSets | 10 options.Streams | 11 options.Strings | 12 ResultBuilder | 13 internal.PubSub.SubscriptionKey | 14 options.Cluster | 15 options.Geo.RadiusUnit | 16 options.Keys.RedisType | 17 options.Lists.Position | 18 options.Lists.Side | 19 options.Scripting.DebugMode | 20 options.Scripting.FlushMode | 21 options.Shared.Order | 22 options.Shared.Update | 23 options.SortedSets.Aggregate | 24 options.Strings.BitFieldCommand | 25 internal | 26 options.Cluster.SetSlotSubCommand | 27 zio.redis | 28 internal.PubSub.PushMessage | 29 internal.RespCommandArgument | 30 internal.RespValue.internal.State | 31 Input | 32 Output | 33 Redis | 34 RedisError | 35 RedisSubscription | 36 api | 37 embedded | 38 internal.RespValue | 39 internal.SingleNodeExecutor | 40 internal.SingleNodeSubscriptionExecutor.Request |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 internal.PubSub | ||||||||||||||||||||||||||||||||||||||||
| 2 internal.RespValue.internal | ||||||||||||||||||||||||||||||||||||||||
| 3 internal.SingleNodeSubscriptionExecutor | ||||||||||||||||||||||||||||||||||||||||
| 4 options.Geo | ||||||||||||||||||||||||||||||||||||||||
| 5 options.Keys | ||||||||||||||||||||||||||||||||||||||||
| 6 options.Lists | ||||||||||||||||||||||||||||||||||||||||
| 7 options.Scripting | ||||||||||||||||||||||||||||||||||||||||
| 8 options.Shared | ||||||||||||||||||||||||||||||||||||||||
| 9 options.SortedSets | ||||||||||||||||||||||||||||||||||||||||
| 10 options.Streams | ||||||||||||||||||||||||||||||||||||||||
| 11 options.Strings | ||||||||||||||||||||||||||||||||||||||||
| 12 ResultBuilder | 6 | |||||||||||||||||||||||||||||||||||||||
| 13 internal.PubSub.SubscriptionKey | 2 | |||||||||||||||||||||||||||||||||||||||
| 14 options.Cluster | 2 | |||||||||||||||||||||||||||||||||||||||
| 15 options.Geo.RadiusUnit | 4 | |||||||||||||||||||||||||||||||||||||||
| 16 options.Keys.RedisType | 6 | |||||||||||||||||||||||||||||||||||||||
| 17 options.Lists.Position | 2 | |||||||||||||||||||||||||||||||||||||||
| 18 options.Lists.Side | 2 | |||||||||||||||||||||||||||||||||||||||
| 19 options.Scripting.DebugMode | 3 | |||||||||||||||||||||||||||||||||||||||
| 20 options.Scripting.FlushMode | 2 | |||||||||||||||||||||||||||||||||||||||
| 21 options.Shared.Order | 2 | |||||||||||||||||||||||||||||||||||||||
| 22 options.Shared.Update | 4 | |||||||||||||||||||||||||||||||||||||||
| 23 options.SortedSets.Aggregate | 3 | |||||||||||||||||||||||||||||||||||||||
| 24 options.Strings.BitFieldCommand | 7 | |||||||||||||||||||||||||||||||||||||||
| 25 internal | 3 | 3 | 14 | |||||||||||||||||||||||||||||||||||||
| 26 options.Cluster.SetSlotSubCommand | 4 | |||||||||||||||||||||||||||||||||||||||
| 27 zio.redis | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 28 internal.PubSub.PushMessage | 6 | 1 | ||||||||||||||||||||||||||||||||||||||
| 29 internal.RespCommandArgument | 4 | |||||||||||||||||||||||||||||||||||||||
| 30 internal.RespValue.internal.State | 5 | 2 | ||||||||||||||||||||||||||||||||||||||
| 31 Input | 106 | 106 | ||||||||||||||||||||||||||||||||||||||
| 32 Output | 1 | 2 | 43 | 43 | ||||||||||||||||||||||||||||||||||||
| 33 Redis | 2 | 5 | ||||||||||||||||||||||||||||||||||||||
| 34 RedisError | 1 | 2 | 13 | |||||||||||||||||||||||||||||||||||||
| 35 RedisSubscription | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 36 api | 12 | 2 | 14 | 1 | ||||||||||||||||||||||||||||||||||||
| 37 embedded | 1 | |||||||||||||||||||||||||||||||||||||||
| 38 internal.RespValue | 8 | 1 | ||||||||||||||||||||||||||||||||||||||
| 39 internal.SingleNodeExecutor | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 40 internal.SingleNodeSubscriptionExecutor.Request | 1 | 2 | 2 |
12→27 ResultBuilder uses zio.redis part of a loop✕
- Connections
- 6 pairs of types, where a type in ResultBuilder uses a type in zio.redis.
- The types involved
zio.redis.ResultBuilder.ResultBuilder1→zio.redis.ResultBuilderzio.redis.ResultBuilder.ResultBuilder2→zio.redis.ResultBuilderzio.redis.ResultBuilder.ResultBuilder3→zio.redis.ResultBuilderzio.redis.ResultBuilder.ResultOutputBuilder→zio.redis.ResultBuilderzio.redis.ResultBuilder.ResultStreamBuilder1→zio.redis.RedisErrorzio.redis.ResultBuilder.ResultStreamBuilder1→zio.redis.ResultBuilder
- Direction
- ResultBuilder uses zio.redis, so a change to zio.redis can break ResultBuilder, while a change to ResultBuilder can't break zio.redis.
- 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.
13→1 internal.PubSub.SubscriptionKey uses internal.PubSub✕
- Connections
- 2 pairs of types, where a type in internal.PubSub.SubscriptionKey uses a type in internal.PubSub.
- The types involved
zio.redis.internal.PubSub.SubscriptionKey.Channel→zio.redis.internal.PubSub.SubscriptionKeyzio.redis.internal.PubSub.SubscriptionKey.Pattern→zio.redis.internal.PubSub.SubscriptionKey
- Direction
- internal.PubSub.SubscriptionKey uses internal.PubSub, so a change to internal.PubSub can break internal.PubSub.SubscriptionKey, while a change to internal.PubSub.SubscriptionKey can't break internal.PubSub.
- Position
- Below the diagonal: internal.PubSub.SubscriptionKey uses a module listed above it, which is the healthy direction.
14→27 options.Cluster uses zio.redis part of a loop✕
- Connections
- 2 pairs of types, where a type in options.Cluster uses a type in zio.redis.
- The types involved
zio.redis.options.Cluster.Node→zio.redis.RedisUrizio.redis.options.Cluster.Partition→zio.redis.RedisUri
- Direction
- options.Cluster uses zio.redis, so a change to zio.redis can break options.Cluster, while a change to options.Cluster can't break zio.redis.
- 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.
15→4 options.Geo.RadiusUnit uses options.Geo✕
- Connections
- 4 pairs of types, where a type in options.Geo.RadiusUnit uses a type in options.Geo.
- The types involved
zio.redis.options.Geo.RadiusUnit.Feet→zio.redis.options.Geo.RadiusUnitzio.redis.options.Geo.RadiusUnit.Kilometers→zio.redis.options.Geo.RadiusUnitzio.redis.options.Geo.RadiusUnit.Meters→zio.redis.options.Geo.RadiusUnitzio.redis.options.Geo.RadiusUnit.Miles→zio.redis.options.Geo.RadiusUnit
- Direction
- options.Geo.RadiusUnit uses options.Geo, so a change to options.Geo can break options.Geo.RadiusUnit, while a change to options.Geo.RadiusUnit can't break options.Geo.
- Position
- Below the diagonal: options.Geo.RadiusUnit uses a module listed above it, which is the healthy direction.
16→5 options.Keys.RedisType uses options.Keys✕
- Connections
- 6 pairs of types, where a type in options.Keys.RedisType uses a type in options.Keys.
- The types involved
zio.redis.options.Keys.RedisType.Hash→zio.redis.options.Keys.RedisTypezio.redis.options.Keys.RedisType.List→zio.redis.options.Keys.RedisTypezio.redis.options.Keys.RedisType.Set→zio.redis.options.Keys.RedisTypezio.redis.options.Keys.RedisType.SortedSet→zio.redis.options.Keys.RedisTypezio.redis.options.Keys.RedisType.Stream→zio.redis.options.Keys.RedisTypezio.redis.options.Keys.RedisType.String→zio.redis.options.Keys.RedisType
- Direction
- options.Keys.RedisType uses options.Keys, so a change to options.Keys can break options.Keys.RedisType, while a change to options.Keys.RedisType can't break options.Keys.
- Position
- Below the diagonal: options.Keys.RedisType uses a module listed above it, which is the healthy direction.
17→6 options.Lists.Position uses options.Lists✕
- Connections
- 2 pairs of types, where a type in options.Lists.Position uses a type in options.Lists.
- The types involved
zio.redis.options.Lists.Position.After→zio.redis.options.Lists.Positionzio.redis.options.Lists.Position.Before→zio.redis.options.Lists.Position
- Direction
- options.Lists.Position uses options.Lists, so a change to options.Lists can break options.Lists.Position, while a change to options.Lists.Position can't break options.Lists.
- Position
- Below the diagonal: options.Lists.Position uses a module listed above it, which is the healthy direction.
18→6 options.Lists.Side uses options.Lists✕
- Connections
- 2 pairs of types, where a type in options.Lists.Side uses a type in options.Lists.
- The types involved
zio.redis.options.Lists.Side.Left→zio.redis.options.Lists.Sidezio.redis.options.Lists.Side.Right→zio.redis.options.Lists.Side
- Direction
- options.Lists.Side uses options.Lists, so a change to options.Lists can break options.Lists.Side, while a change to options.Lists.Side can't break options.Lists.
- Position
- Below the diagonal: options.Lists.Side uses a module listed above it, which is the healthy direction.
19→7 options.Scripting.DebugMode uses options.Scripting✕
- Connections
- 3 pairs of types, where a type in options.Scripting.DebugMode uses a type in options.Scripting.
- The types involved
zio.redis.options.Scripting.DebugMode.No→zio.redis.options.Scripting.DebugModezio.redis.options.Scripting.DebugMode.Sync→zio.redis.options.Scripting.DebugModezio.redis.options.Scripting.DebugMode.Yes→zio.redis.options.Scripting.DebugMode
- Direction
- options.Scripting.DebugMode uses options.Scripting, so a change to options.Scripting can break options.Scripting.DebugMode, while a change to options.Scripting.DebugMode can't break options.Scripting.
- Position
- Below the diagonal: options.Scripting.DebugMode uses a module listed above it, which is the healthy direction.
20→7 options.Scripting.FlushMode uses options.Scripting✕
- Connections
- 2 pairs of types, where a type in options.Scripting.FlushMode uses a type in options.Scripting.
- The types involved
zio.redis.options.Scripting.FlushMode.Async→zio.redis.options.Scripting.FlushModezio.redis.options.Scripting.FlushMode.Sync→zio.redis.options.Scripting.FlushMode
- Direction
- options.Scripting.FlushMode uses options.Scripting, so a change to options.Scripting can break options.Scripting.FlushMode, while a change to options.Scripting.FlushMode can't break options.Scripting.
- Position
- Below the diagonal: options.Scripting.FlushMode uses a module listed above it, which is the healthy direction.
21→8 options.Shared.Order uses options.Shared✕
- Connections
- 2 pairs of types, where a type in options.Shared.Order uses a type in options.Shared.
- The types involved
zio.redis.options.Shared.Order.Ascending→zio.redis.options.Shared.Orderzio.redis.options.Shared.Order.Descending→zio.redis.options.Shared.Order
- Direction
- options.Shared.Order uses options.Shared, so a change to options.Shared can break options.Shared.Order, while a change to options.Shared.Order can't break options.Shared.
- Position
- Below the diagonal: options.Shared.Order uses a module listed above it, which is the healthy direction.
22→8 options.Shared.Update uses options.Shared✕
- Connections
- 4 pairs of types, where a type in options.Shared.Update uses a type in options.Shared.
- The types involved
zio.redis.options.Shared.Update.SetExisting→zio.redis.options.Shared.Updatezio.redis.options.Shared.Update.SetGreaterThan→zio.redis.options.Shared.Updatezio.redis.options.Shared.Update.SetLessThan→zio.redis.options.Shared.Updatezio.redis.options.Shared.Update.SetNew→zio.redis.options.Shared.Update
- Direction
- options.Shared.Update uses options.Shared, so a change to options.Shared can break options.Shared.Update, while a change to options.Shared.Update can't break options.Shared.
- Position
- Below the diagonal: options.Shared.Update uses a module listed above it, which is the healthy direction.
23→9 options.SortedSets.Aggregate uses options.SortedSets✕
- Connections
- 3 pairs of types, where a type in options.SortedSets.Aggregate uses a type in options.SortedSets.
- The types involved
zio.redis.options.SortedSets.Aggregate.Max→zio.redis.options.SortedSets.Aggregatezio.redis.options.SortedSets.Aggregate.Min→zio.redis.options.SortedSets.Aggregatezio.redis.options.SortedSets.Aggregate.Sum→zio.redis.options.SortedSets.Aggregate
- Direction
- options.SortedSets.Aggregate uses options.SortedSets, so a change to options.SortedSets can break options.SortedSets.Aggregate, while a change to options.SortedSets.Aggregate can't break options.SortedSets.
- Position
- Below the diagonal: options.SortedSets.Aggregate uses a module listed above it, which is the healthy direction.
24→11 options.Strings.BitFieldCommand uses options.Strings✕
- Connections
- 7 pairs of types, where a type in options.Strings.BitFieldCommand uses a type in options.Strings.
- The types involved
zio.redis.options.Strings.BitFieldCommand.BitFieldGet→zio.redis.options.Strings.BitFieldCommandzio.redis.options.Strings.BitFieldCommand.BitFieldGet→zio.redis.options.Strings.BitFieldTypezio.redis.options.Strings.BitFieldCommand.BitFieldIncr→zio.redis.options.Strings.BitFieldCommandzio.redis.options.Strings.BitFieldCommand.BitFieldIncr→zio.redis.options.Strings.BitFieldTypezio.redis.options.Strings.BitFieldCommand.BitFieldOverflow→zio.redis.options.Strings.BitFieldCommandzio.redis.options.Strings.BitFieldCommand.BitFieldSet→zio.redis.options.Strings.BitFieldCommandzio.redis.options.Strings.BitFieldCommand.BitFieldSet→zio.redis.options.Strings.BitFieldType
- Direction
- options.Strings.BitFieldCommand uses options.Strings, so a change to options.Strings can break options.Strings.BitFieldCommand, while a change to options.Strings.BitFieldCommand can't break options.Strings.
- Position
- Below the diagonal: options.Strings.BitFieldCommand uses a module listed above it, which is the healthy direction.
25→1 internal uses internal.PubSub✕
- Connections
- 3 pairs of types, where a type in internal uses a type in internal.PubSub.
- The types involved
zio.redis.internal.SingleNodeSubscriptionExecutor→zio.redis.internal.PubSub.PushMessagezio.redis.internal.SingleNodeSubscriptionExecutor→zio.redis.internal.PubSub.SubscriptionKeyzio.redis.internal.SubscriptionExecutor→zio.redis.internal.PubSub.PushMessage
- Direction
- internal uses internal.PubSub, so a change to internal.PubSub can break internal, while a change to internal can't break internal.PubSub.
- Position
- Below the diagonal: internal uses a module listed above it, which is the healthy direction.
25→14 internal uses options.Cluster✕
- Connections
- 3 pairs of types, where a type in internal uses a type in options.Cluster.
- The types involved
zio.redis.internal.ClusterConnection→zio.redis.options.Cluster.Partitionzio.redis.internal.ClusterConnection→zio.redis.options.Cluster.Slotzio.redis.internal.ClusterExecutor→zio.redis.options.Cluster.Slot
- Direction
- internal uses options.Cluster, so a change to options.Cluster can break internal, while a change to internal can't break options.Cluster.
- Position
- Below the diagonal: internal uses a module listed above it, which is the healthy direction.
25→27 internal uses zio.redis part of a loop✕
- Connections
- 14 pairs of types, where a type in internal uses a type in zio.redis.
- The types involved
zio.redis.internal.ClusterConnection→zio.redis.RedisUrizio.redis.internal.ClusterExecutor→zio.redis.RedisErrorzio.redis.internal.ClusterExecutor→zio.redis.RedisUrizio.redis.internal.RedisCommand→zio.redis.Inputzio.redis.internal.RedisCommand→zio.redis.Outputzio.redis.internal.RedisEnvironment→zio.redis.CodecSupplierzio.redis.internal.RedisEnvironment→zio.redis.RedisErrorzio.redis.internal.RedisExecutor→zio.redis.RedisErrorzio.redis.internal.RedisSubscriptionCommand→zio.redis.RedisErrorzio.redis.internal.SingleNodeExecutor→zio.redis.RedisErrorzio.redis.internal.SingleNodeRunner→zio.redis.RedisErrorzio.redis.internal.SingleNodeSubscriptionExecutor→zio.redis.RedisErrorzio.redis.internal.SubscribeEnvironment→zio.redis.CodecSupplierzio.redis.internal.SubscriptionExecutor→zio.redis.RedisError
- Direction
- internal uses zio.redis, so a change to zio.redis can break internal, while a change to internal can't break zio.redis.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
26→14 options.Cluster.SetSlotSubCommand uses options.Cluster✕
- Connections
- 4 pairs of types, where a type in options.Cluster.SetSlotSubCommand uses a type in options.Cluster.
- The types involved
zio.redis.options.Cluster.SetSlotSubCommand.Importing→zio.redis.options.Cluster.SetSlotSubCommandzio.redis.options.Cluster.SetSlotSubCommand.Migrating→zio.redis.options.Cluster.SetSlotSubCommandzio.redis.options.Cluster.SetSlotSubCommand.Node→zio.redis.options.Cluster.SetSlotSubCommandzio.redis.options.Cluster.SetSlotSubCommand.Stable→zio.redis.options.Cluster.SetSlotSubCommand
- Direction
- options.Cluster.SetSlotSubCommand uses options.Cluster, so a change to options.Cluster can break options.Cluster.SetSlotSubCommand, while a change to options.Cluster.SetSlotSubCommand can't break options.Cluster.
- Position
- Below the diagonal: options.Cluster.SetSlotSubCommand uses a module listed above it, which is the healthy direction.
27→12 zio.redis uses ResultBuilder✕
- Connections
- 1 pair of types, where a type in zio.redis uses a type in ResultBuilder.
- The types involved
zio.redis.ResultBuilder→zio.redis.ResultBuilder.NeedsReturnType
- Direction
- zio.redis uses ResultBuilder, so a change to ResultBuilder can break zio.redis, while a change to zio.redis can't break ResultBuilder.
- Position
- Below the diagonal: zio.redis uses a module listed above it, which is the healthy direction.
27→25 zio.redis uses internal✕
- Connections
- 2 pairs of types, where a type in zio.redis uses a type in internal.
- The types involved
zio.redis.Input→zio.redis.internal.RespCommandzio.redis.Output→zio.redis.internal.RespValue
- Direction
- zio.redis uses internal, so a change to internal can break zio.redis, while a change to zio.redis can't break internal.
- Position
- Below the diagonal: zio.redis uses a module listed above it, which is the healthy direction.
28→1 internal.PubSub.PushMessage uses internal.PubSub✕
- Connections
- 6 pairs of types, where a type in internal.PubSub.PushMessage uses a type in internal.PubSub.
- The types involved
zio.redis.internal.PubSub.PushMessage.Message→zio.redis.internal.PubSub.PushMessagezio.redis.internal.PubSub.PushMessage.Message→zio.redis.internal.PubSub.SubscriptionKeyzio.redis.internal.PubSub.PushMessage.Subscribed→zio.redis.internal.PubSub.PushMessagezio.redis.internal.PubSub.PushMessage.Subscribed→zio.redis.internal.PubSub.SubscriptionKeyzio.redis.internal.PubSub.PushMessage.Unsubscribed→zio.redis.internal.PubSub.PushMessagezio.redis.internal.PubSub.PushMessage.Unsubscribed→zio.redis.internal.PubSub.SubscriptionKey
- Direction
- internal.PubSub.PushMessage uses internal.PubSub, so a change to internal.PubSub can break internal.PubSub.PushMessage, while a change to internal.PubSub.PushMessage can't break internal.PubSub.
- Position
- Below the diagonal: internal.PubSub.PushMessage uses a module listed above it, which is the healthy direction.
28→25 internal.PubSub.PushMessage uses internal✕
- Connections
- 1 pair of types, where a type in internal.PubSub.PushMessage uses a type in internal.
- The types involved
zio.redis.internal.PubSub.PushMessage.Message→zio.redis.internal.RespValue
- Direction
- internal.PubSub.PushMessage uses internal, so a change to internal can break internal.PubSub.PushMessage, while a change to internal.PubSub.PushMessage can't break internal.
- Position
- Below the diagonal: internal.PubSub.PushMessage uses a module listed above it, which is the healthy direction.
29→25 internal.RespCommandArgument uses internal✕
- Connections
- 4 pairs of types, where a type in internal.RespCommandArgument uses a type in internal.
- The types involved
zio.redis.internal.RespCommandArgument.CommandName→zio.redis.internal.RespCommandArgumentzio.redis.internal.RespCommandArgument.Key→zio.redis.internal.RespCommandArgumentzio.redis.internal.RespCommandArgument.Literal→zio.redis.internal.RespCommandArgumentzio.redis.internal.RespCommandArgument.Value→zio.redis.internal.RespCommandArgument
- Direction
- internal.RespCommandArgument uses internal, so a change to internal can break internal.RespCommandArgument, while a change to internal.RespCommandArgument can't break internal.
- Position
- Below the diagonal: internal.RespCommandArgument uses a module listed above it, which is the healthy direction.
30→2 internal.RespValue.internal.State uses internal.RespValue.internal✕
- Connections
- 5 pairs of types, where a type in internal.RespValue.internal.State uses a type in internal.RespValue.internal.
- The types involved
zio.redis.internal.RespValue.internal.State.CollectingArray→zio.redis.internal.RespValue.internal.Statezio.redis.internal.RespValue.internal.State.CollectingBulkString→zio.redis.internal.RespValue.internal.Statezio.redis.internal.RespValue.internal.State.Done→zio.redis.internal.RespValue.internal.Statezio.redis.internal.RespValue.internal.State.Failed→zio.redis.internal.RespValue.internal.Statezio.redis.internal.RespValue.internal.State.Start→zio.redis.internal.RespValue.internal.State
- Direction
- internal.RespValue.internal.State uses internal.RespValue.internal, so a change to internal.RespValue.internal can break internal.RespValue.internal.State, while a change to internal.RespValue.internal.State can't break internal.RespValue.internal.
- Position
- Below the diagonal: internal.RespValue.internal.State uses a module listed above it, which is the healthy direction.
30→25 internal.RespValue.internal.State uses internal✕
- Connections
- 2 pairs of types, where a type in internal.RespValue.internal.State uses a type in internal.
- The types involved
zio.redis.internal.RespValue.internal.State.CollectingArray→zio.redis.internal.RespValuezio.redis.internal.RespValue.internal.State.Done→zio.redis.internal.RespValue
- Direction
- internal.RespValue.internal.State uses internal, so a change to internal can break internal.RespValue.internal.State, while a change to internal.RespValue.internal.State can't break internal.
- Position
- Below the diagonal: internal.RespValue.internal.State uses a module listed above it, which is the healthy direction.
31→25 Input uses internal✕
- Connections
- 106 pairs of types, where a type in Input uses a type in internal. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
zio.redis.Input.AbsTtlInput→zio.redis.internal.RespCommandzio.redis.Input.AddressInput→zio.redis.internal.RespCommandzio.redis.Input.AggregateInput→zio.redis.internal.RespCommandzio.redis.Input.AlphaInput→zio.redis.internal.RespCommandzio.redis.Input.ArbitraryKeyInput→zio.redis.internal.RespCommandzio.redis.Input.ArbitraryValueInput→zio.redis.internal.RespCommandzio.redis.Input.AuthInput→zio.redis.internal.RespCommandzio.redis.Input.BitFieldCommandInput→zio.redis.internal.RespCommandzio.redis.Input.BitOperationInput→zio.redis.internal.RespCommandzio.redis.Input.BitPosRangeInput→zio.redis.internal.RespCommandzio.redis.Input.BlockInput→zio.redis.internal.RespCommandzio.redis.Input.BoolInput→zio.redis.internal.RespCommandzio.redis.Input.ByInput→zio.redis.internal.RespCommandzio.redis.Input.ByRadiusInput→zio.redis.internal.RespCommandzio.redis.Input.ChangedInput→zio.redis.internal.RespCommandzio.redis.Input.CommandNameInput→zio.redis.internal.RespCommandzio.redis.Input.CopyInput→zio.redis.internal.RespCommandzio.redis.Input.CountInput→zio.redis.internal.RespCommandzio.redis.Input.DbInput→zio.redis.internal.RespCommandzio.redis.Input.DoubleInput→zio.redis.internal.RespCommandzio.redis.Input.DurationMillisecondsInput→zio.redis.internal.RespCommandzio.redis.Input.DurationSecondsInput→zio.redis.internal.RespCommandzio.redis.Input.DurationTtlInput→zio.redis.internal.RespCommandzio.redis.Input.EvalInput→zio.redis.internal.RespCommandzio.redis.Input.FreqInput→zio.redis.internal.RespCommand
- Direction
- Input uses internal, so a change to internal can break Input, while a change to Input can't break internal.
- Position
- Below the diagonal: Input uses a module listed above it, which is the healthy direction.
31→27 Input uses zio.redis✕
- Connections
- 106 pairs of types, where a type in Input uses a type in zio.redis. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
zio.redis.Input.AbsTtlInput→zio.redis.Inputzio.redis.Input.AddressInput→zio.redis.Inputzio.redis.Input.AggregateInput→zio.redis.Inputzio.redis.Input.AlphaInput→zio.redis.Inputzio.redis.Input.ArbitraryKeyInput→zio.redis.Inputzio.redis.Input.ArbitraryValueInput→zio.redis.Inputzio.redis.Input.AuthInput→zio.redis.Inputzio.redis.Input.BitFieldCommandInput→zio.redis.Inputzio.redis.Input.BitOperationInput→zio.redis.Inputzio.redis.Input.BitPosRangeInput→zio.redis.Inputzio.redis.Input.BlockInput→zio.redis.Inputzio.redis.Input.BoolInput→zio.redis.Inputzio.redis.Input.ByInput→zio.redis.Inputzio.redis.Input.ByRadiusInput→zio.redis.Inputzio.redis.Input.ChangedInput→zio.redis.Inputzio.redis.Input.CommandNameInput→zio.redis.Inputzio.redis.Input.CopyInput→zio.redis.Inputzio.redis.Input.CountInput→zio.redis.Inputzio.redis.Input.DbInput→zio.redis.Inputzio.redis.Input.DoubleInput→zio.redis.Inputzio.redis.Input.DurationMillisecondsInput→zio.redis.Inputzio.redis.Input.DurationSecondsInput→zio.redis.Inputzio.redis.Input.DurationTtlInput→zio.redis.Inputzio.redis.Input.EvalInput→zio.redis.Inputzio.redis.Input.FreqInput→zio.redis.Input
- Direction
- Input uses zio.redis, so a change to zio.redis can break Input, while a change to Input can't break zio.redis.
- Position
- Below the diagonal: Input uses a module listed above it, which is the healthy direction.
32→1 Output uses internal.PubSub✕
- Connections
- 1 pair of types, where a type in Output uses a type in internal.PubSub.
- The types involved
zio.redis.Output.PushMessageOutput→zio.redis.internal.PubSub.PushMessage
- Direction
- Output uses internal.PubSub, so a change to internal.PubSub can break Output, while a change to Output can't break internal.PubSub.
- Position
- Below the diagonal: Output uses a module listed above it, which is the healthy direction.
32→14 Output uses options.Cluster✕
- Connections
- 2 pairs of types, where a type in Output uses a type in options.Cluster.
- The types involved
zio.redis.Output.ClusterPartitionNodeOutput→zio.redis.options.Cluster.Nodezio.redis.Output.ClusterPartitionOutput→zio.redis.options.Cluster.Partition
- Direction
- Output uses options.Cluster, so a change to options.Cluster can break Output, while a change to Output can't break options.Cluster.
- Position
- Below the diagonal: Output uses a module listed above it, which is the healthy direction.
32→25 Output uses internal✕
- Connections
- 43 pairs of types, where a type in Output uses a type in internal. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
zio.redis.Output.ArbitraryOutput→zio.redis.internal.RespValuezio.redis.Output.BoolOutput→zio.redis.internal.RespValuezio.redis.Output.BulkStringOutput→zio.redis.internal.RespValuezio.redis.Output.ChunkOutput→zio.redis.internal.RespValuezio.redis.Output.ChunkTuple2Output→zio.redis.internal.RespValuezio.redis.Output.ClusterPartitionNodeOutput→zio.redis.internal.RespValuezio.redis.Output.ClusterPartitionOutput→zio.redis.internal.RespValuezio.redis.Output.DoubleOrInfinity→zio.redis.internal.RespValuezio.redis.Output.DoubleOutput→zio.redis.internal.RespValuezio.redis.Output.DurationOutput→zio.redis.internal.RespValuezio.redis.Output.GeoOutput→zio.redis.internal.RespValuezio.redis.Output.GeoRadiusOutput→zio.redis.internal.RespValuezio.redis.Output.KeyElemOutput→zio.redis.internal.RespValuezio.redis.Output.KeyValueOutput→zio.redis.internal.RespValuezio.redis.Output.LcsOutput→zio.redis.internal.RespValuezio.redis.Output.LongOutput→zio.redis.internal.RespValuezio.redis.Output.MultiStringChunkOutput→zio.redis.internal.RespValuezio.redis.Output.MultiStringOutput→zio.redis.internal.RespValuezio.redis.Output.NumSubResponseOutput→zio.redis.internal.RespValuezio.redis.Output.OptionalOutput→zio.redis.internal.RespValuezio.redis.Output.PendingMessagesOutput→zio.redis.internal.RespValuezio.redis.Output.PushMessageOutput→zio.redis.internal.RespValuezio.redis.Output.ResetOutput→zio.redis.internal.RespValuezio.redis.Output.RespValueOutput→zio.redis.internal.RespValuezio.redis.Output.ScanOutput→zio.redis.internal.RespValue
- Direction
- Output uses internal, so a change to internal can break Output, while a change to Output can't break internal.
- Position
- Below the diagonal: Output uses a module listed above it, which is the healthy direction.
32→27 Output uses zio.redis✕
- Connections
- 43 pairs of types, where a type in Output uses a type in zio.redis. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
zio.redis.Output.ArbitraryOutput→zio.redis.Outputzio.redis.Output.BoolOutput→zio.redis.Outputzio.redis.Output.BulkStringOutput→zio.redis.Outputzio.redis.Output.ChunkOutput→zio.redis.Outputzio.redis.Output.ChunkTuple2Output→zio.redis.Outputzio.redis.Output.ClusterPartitionNodeOutput→zio.redis.Outputzio.redis.Output.ClusterPartitionOutput→zio.redis.Outputzio.redis.Output.DoubleOrInfinity→zio.redis.Outputzio.redis.Output.DoubleOutput→zio.redis.Outputzio.redis.Output.DurationOutput→zio.redis.Outputzio.redis.Output.GeoOutput→zio.redis.Outputzio.redis.Output.GeoRadiusOutput→zio.redis.Outputzio.redis.Output.KeyElemOutput→zio.redis.Outputzio.redis.Output.KeyValueOutput→zio.redis.Outputzio.redis.Output.LcsOutput→zio.redis.Outputzio.redis.Output.LongOutput→zio.redis.Outputzio.redis.Output.MultiStringChunkOutput→zio.redis.Outputzio.redis.Output.MultiStringOutput→zio.redis.Outputzio.redis.Output.NumSubResponseOutput→zio.redis.Outputzio.redis.Output.OptionalOutput→zio.redis.Outputzio.redis.Output.PendingMessagesOutput→zio.redis.Outputzio.redis.Output.PushMessageOutput→zio.redis.Outputzio.redis.Output.ResetOutput→zio.redis.Outputzio.redis.Output.RespValueOutput→zio.redis.Outputzio.redis.Output.ScanOutput→zio.redis.Output
- Direction
- Output uses zio.redis, so a change to zio.redis can break Output, while a change to Output can't break zio.redis.
- Position
- Below the diagonal: Output uses a module listed above it, which is the healthy direction.
33→25 Redis uses internal✕
- Connections
- 2 pairs of types, where a type in Redis uses a type in internal.
- The types involved
zio.redis.Redis.AsyncLive→zio.redis.internal.RedisExecutorzio.redis.Redis.SyncLive→zio.redis.internal.RedisExecutor
- Direction
- Redis uses internal, so a change to internal can break Redis, while a change to Redis can't break internal.
- Position
- Below the diagonal: Redis uses a module listed above it, which is the healthy direction.
33→27 Redis uses zio.redis✕
- Connections
- 5 pairs of types, where a type in Redis uses a type in zio.redis.
- The types involved
zio.redis.Redis.AsyncLive→zio.redis.CodecSupplierzio.redis.Redis.AsyncLive→zio.redis.RedisErrorzio.redis.Redis.SyncLive→zio.redis.CodecSupplierzio.redis.Redis.SyncLive→zio.redis.Rediszio.redis.Redis.SyncLive→zio.redis.RedisError
- Direction
- Redis uses zio.redis, so a change to zio.redis can break Redis, while a change to Redis can't break zio.redis.
- Position
- Below the diagonal: Redis uses a module listed above it, which is the healthy direction.
34→1 RedisError uses internal.PubSub✕
- Connections
- 1 pair of types, where a type in RedisError uses a type in internal.PubSub.
- The types involved
zio.redis.RedisError.SubscriptionStreamAlreadyClosed→zio.redis.internal.PubSub.SubscriptionKey
- Direction
- RedisError uses internal.PubSub, so a change to internal.PubSub can break RedisError, while a change to RedisError can't break internal.PubSub.
- Position
- Below the diagonal: RedisError uses a module listed above it, which is the healthy direction.
34→14 RedisError uses options.Cluster✕
- Connections
- 2 pairs of types, where a type in RedisError uses a type in options.Cluster.
- The types involved
zio.redis.RedisError.Ask→zio.redis.options.Cluster.Slotzio.redis.RedisError.Moved→zio.redis.options.Cluster.Slot
- Direction
- RedisError uses options.Cluster, so a change to options.Cluster can break RedisError, while a change to RedisError can't break options.Cluster.
- Position
- Below the diagonal: RedisError uses a module listed above it, which is the healthy direction.
34→27 RedisError uses zio.redis✕
- Connections
- 13 pairs of types, where a type in RedisError uses a type in zio.redis.
- The types involved
zio.redis.RedisError.Ask→zio.redis.RedisUrizio.redis.RedisError.BusyGroup→zio.redis.RedisErrorzio.redis.RedisError.ClusterRedisError→zio.redis.RedisErrorzio.redis.RedisError.CodecError→zio.redis.RedisErrorzio.redis.RedisError.CommandNameNotFound→zio.redis.RedisErrorzio.redis.RedisError.IOError→zio.redis.RedisErrorzio.redis.RedisError.Moved→zio.redis.RedisUrizio.redis.RedisError.NoGroup→zio.redis.RedisErrorzio.redis.RedisError.NoScript→zio.redis.RedisErrorzio.redis.RedisError.NotBusy→zio.redis.RedisErrorzio.redis.RedisError.ProtocolError→zio.redis.RedisErrorzio.redis.RedisError.PubSubError→zio.redis.RedisErrorzio.redis.RedisError.WrongType→zio.redis.RedisError
- Direction
- RedisError uses zio.redis, so a change to zio.redis can break RedisError, while a change to RedisError can't break zio.redis.
- Position
- Below the diagonal: RedisError uses a module listed above it, which is the healthy direction.
35→25 RedisSubscription uses internal✕
- Connections
- 1 pair of types, where a type in RedisSubscription uses a type in internal.
- The types involved
zio.redis.RedisSubscription.Live→zio.redis.internal.SubscriptionExecutor
- Direction
- RedisSubscription uses internal, so a change to internal can break RedisSubscription, while a change to RedisSubscription can't break internal.
- Position
- Below the diagonal: RedisSubscription uses a module listed above it, which is the healthy direction.
35→27 RedisSubscription uses zio.redis✕
- Connections
- 2 pairs of types, where a type in RedisSubscription uses a type in zio.redis.
- The types involved
zio.redis.RedisSubscription.Live→zio.redis.CodecSupplierzio.redis.RedisSubscription.Live→zio.redis.RedisSubscription
- Direction
- RedisSubscription uses zio.redis, so a change to zio.redis can break RedisSubscription, while a change to RedisSubscription can't break zio.redis.
- Position
- Below the diagonal: RedisSubscription uses a module listed above it, which is the healthy direction.
36→12 api uses ResultBuilder✕
- Connections
- 12 pairs of types, where a type in api uses a type in ResultBuilder.
- The types involved
zio.redis.api.Hashes→zio.redis.ResultBuilder.ResultBuilder1zio.redis.api.Hashes→zio.redis.ResultBuilder.ResultBuilder2zio.redis.api.Keys→zio.redis.ResultBuilder.ResultBuilder1zio.redis.api.Lists→zio.redis.ResultBuilder.ResultBuilder1zio.redis.api.Scripting→zio.redis.ResultBuilder.ResultOutputBuilderzio.redis.api.Sets→zio.redis.ResultBuilder.ResultBuilder1zio.redis.api.SortedSets→zio.redis.ResultBuilder.ResultBuilder1zio.redis.api.Streams→zio.redis.ResultBuilder.ResultBuilder1zio.redis.api.Streams→zio.redis.ResultBuilder.ResultBuilder2zio.redis.api.Streams→zio.redis.ResultBuilder.ResultBuilder3zio.redis.api.Strings→zio.redis.ResultBuilder.ResultBuilder1zio.redis.api.Subscription→zio.redis.ResultBuilder.ResultStreamBuilder1
- Direction
- api uses ResultBuilder, so a change to ResultBuilder can break api, while a change to api can't break ResultBuilder.
- Position
- Below the diagonal: api uses a module listed above it, which is the healthy direction.
36→14 api uses options.Cluster✕
- Connections
- 2 pairs of types, where a type in api uses a type in options.Cluster.
- The types involved
zio.redis.api.Cluster→zio.redis.options.Cluster.Partitionzio.redis.api.Cluster→zio.redis.options.Cluster.Slot
- Direction
- api uses options.Cluster, so a change to options.Cluster can break api, while a change to api can't break options.Cluster.
- Position
- Below the diagonal: api uses a module listed above it, which is the healthy direction.
36→25 api uses internal✕
- Connections
- 14 pairs of types, where a type in api uses a type in internal.
- The types involved
zio.redis.api.Cluster→zio.redis.internal.RedisEnvironmentzio.redis.api.Connection→zio.redis.internal.RedisEnvironmentzio.redis.api.Geo→zio.redis.internal.RedisEnvironmentzio.redis.api.Hashes→zio.redis.internal.RedisEnvironmentzio.redis.api.HyperLogLog→zio.redis.internal.RedisEnvironmentzio.redis.api.Keys→zio.redis.internal.RedisEnvironmentzio.redis.api.Lists→zio.redis.internal.RedisEnvironmentzio.redis.api.Publishing→zio.redis.internal.RedisEnvironmentzio.redis.api.Scripting→zio.redis.internal.RedisEnvironmentzio.redis.api.Sets→zio.redis.internal.RedisEnvironmentzio.redis.api.SortedSets→zio.redis.internal.RedisEnvironmentzio.redis.api.Streams→zio.redis.internal.RedisEnvironmentzio.redis.api.Strings→zio.redis.internal.RedisEnvironmentzio.redis.api.Subscription→zio.redis.internal.SubscribeEnvironment
- Direction
- api uses internal, so a change to internal can break api, while a change to api can't break internal.
- Position
- Below the diagonal: api uses a module listed above it, which is the healthy direction.
36→27 api uses zio.redis✕
- Connections
- 1 pair of types, where a type in api uses a type in zio.redis.
- The types involved
zio.redis.api.Subscription→zio.redis.RedisError
- Direction
- api uses zio.redis, so a change to zio.redis can break api, while a change to api can't break zio.redis.
- Position
- Below the diagonal: api uses a module listed above it, which is the healthy direction.
37→27 embedded uses zio.redis✕
- Connections
- 1 pair of types, where a type in embedded uses a type in zio.redis.
- The types involved
zio.redis.embedded.EmbeddedRedis→zio.redis.RedisConfig
- Direction
- embedded uses zio.redis, so a change to zio.redis can break embedded, while a change to embedded can't break zio.redis.
- Position
- Below the diagonal: embedded uses a module listed above it, which is the healthy direction.
38→25 internal.RespValue uses internal✕
- Connections
- 8 pairs of types, where a type in internal.RespValue uses a type in internal.
- The types involved
zio.redis.internal.RespValue.Array→zio.redis.internal.RespValuezio.redis.internal.RespValue.ArrayValues→zio.redis.internal.RespValuezio.redis.internal.RespValue.BulkString→zio.redis.internal.RespValuezio.redis.internal.RespValue.Error→zio.redis.internal.RespValuezio.redis.internal.RespValue.Integer→zio.redis.internal.RespValuezio.redis.internal.RespValue.NullArray→zio.redis.internal.RespValuezio.redis.internal.RespValue.NullBulkString→zio.redis.internal.RespValuezio.redis.internal.RespValue.SimpleString→zio.redis.internal.RespValue
- Direction
- internal.RespValue uses internal, so a change to internal can break internal.RespValue, while a change to internal.RespValue can't break internal.
- Position
- Below the diagonal: internal.RespValue uses a module listed above it, which is the healthy direction.
38→27 internal.RespValue uses zio.redis✕
- Connections
- 1 pair of types, where a type in internal.RespValue uses a type in zio.redis.
- The types involved
zio.redis.internal.RespValue.Error→zio.redis.RedisError
- Direction
- internal.RespValue uses zio.redis, so a change to zio.redis can break internal.RespValue, while a change to internal.RespValue can't break zio.redis.
- Position
- Below the diagonal: internal.RespValue uses a module listed above it, which is the healthy direction.
39→25 internal.SingleNodeExecutor uses internal✕
- Connections
- 1 pair of types, where a type in internal.SingleNodeExecutor uses a type in internal.
- The types involved
zio.redis.internal.SingleNodeExecutor.Request→zio.redis.internal.RespValue
- Direction
- internal.SingleNodeExecutor uses internal, so a change to internal can break internal.SingleNodeExecutor, while a change to internal.SingleNodeExecutor can't break internal.
- Position
- Below the diagonal: internal.SingleNodeExecutor uses a module listed above it, which is the healthy direction.
39→27 internal.SingleNodeExecutor uses zio.redis✕
- Connections
- 1 pair of types, where a type in internal.SingleNodeExecutor uses a type in zio.redis.
- The types involved
zio.redis.internal.SingleNodeExecutor.Request→zio.redis.RedisError
- Direction
- internal.SingleNodeExecutor uses zio.redis, so a change to zio.redis can break internal.SingleNodeExecutor, while a change to internal.SingleNodeExecutor can't break zio.redis.
- Position
- Below the diagonal: internal.SingleNodeExecutor uses a module listed above it, which is the healthy direction.
40→1 internal.SingleNodeSubscriptionExecutor.Request uses internal.PubSub✕
- Connections
- 1 pair of types, where a type in internal.SingleNodeSubscriptionExecutor.Request uses a type in internal.PubSub.
- The types involved
zio.redis.internal.SingleNodeSubscriptionExecutor.Request.Subscribe→zio.redis.internal.PubSub.PushMessage
- Direction
- internal.SingleNodeSubscriptionExecutor.Request uses internal.PubSub, so a change to internal.PubSub can break internal.SingleNodeSubscriptionExecutor.Request, while a change to internal.SingleNodeSubscriptionExecutor.Request can't break internal.PubSub.
- Position
- Below the diagonal: internal.SingleNodeSubscriptionExecutor.Request uses a module listed above it, which is the healthy direction.
40→3 internal.SingleNodeSubscriptionExecutor.Request uses internal.SingleNodeSubscriptionExecutor✕
- Connections
- 2 pairs of types, where a type in internal.SingleNodeSubscriptionExecutor.Request uses a type in internal.SingleNodeSubscriptionExecutor.
- The types involved
zio.redis.internal.SingleNodeSubscriptionExecutor.Request.Subscribe→zio.redis.internal.SingleNodeSubscriptionExecutor.Requestzio.redis.internal.SingleNodeSubscriptionExecutor.Request.Unsubscribe→zio.redis.internal.SingleNodeSubscriptionExecutor.Request
- Direction
- internal.SingleNodeSubscriptionExecutor.Request uses internal.SingleNodeSubscriptionExecutor, so a change to internal.SingleNodeSubscriptionExecutor can break internal.SingleNodeSubscriptionExecutor.Request, while a change to internal.SingleNodeSubscriptionExecutor.Request can't break internal.SingleNodeSubscriptionExecutor.
- Position
- Below the diagonal: internal.SingleNodeSubscriptionExecutor.Request uses a module listed above it, which is the healthy direction.
40→27 internal.SingleNodeSubscriptionExecutor.Request uses zio.redis✕
- Connections
- 2 pairs of types, where a type in internal.SingleNodeSubscriptionExecutor.Request uses a type in zio.redis.
- The types involved
zio.redis.internal.SingleNodeSubscriptionExecutor.Request.Subscribe→zio.redis.RedisErrorzio.redis.internal.SingleNodeSubscriptionExecutor.Request.Unsubscribe→zio.redis.RedisError
- Direction
- internal.SingleNodeSubscriptionExecutor.Request uses zio.redis, so a change to zio.redis can break internal.SingleNodeSubscriptionExecutor.Request, while a change to internal.SingleNodeSubscriptionExecutor.Request can't break zio.redis.
- Position
- Below the diagonal: internal.SingleNodeSubscriptionExecutor.Request uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
At a glance — Domain Modelling
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A05:2025 — Injection | 50 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 4 | Medium |
Roadmap
Top priorities: Stop accepting every TLS certificate: delete the trust manager whose `checkServerTrusted` is empty, the `HostnameVerifier` that returns `true`, `InsecureTrustManagerFactory` / `NoopHostnameVerifier` and `acceptAnyCertificate`, and trust a self-signed or private server by giving the client a trust store holding its CA — never by switching verification off; Resolve the 12 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (4), REDACTED (3), REDACTED (2); Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Stop accepting every TLS certificate: delete the trust manager whose `checkServerTrusted` is empty, the `HostnameVerifier` that returns `true`, `InsecureTrustManagerFactory` / `NoopHostnameVerifier` and `acceptAnyCertificate`, and trust a self-signed or private server by giving the client a trust store holding its CA — never by switching verification off. | +4.2 pts | Medium | Web-Security Posture |
| Resolve the 12 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (4), REDACTED (3), REDACTED (2). | +4.0 pts | Medium | Static Analysis (SAST) |
| Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them. | +3.6 pts | Medium | Architecture documentation |
| Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. | +1.5 pts | Low | Static Analysis (SAST) |
| Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. | +1.4 pts | Low | Supply-chain Provenance & Signing |
| Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. | +1.4 pts | Low | Supply-chain Provenance & Signing |
| Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. | +1.4 pts | Low | Supply-chain Provenance & Signing |
| Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion. | +1.4 pts | Low | Project Cohesion |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 4.4 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.4 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.8 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.8 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.8 | Mixed | Static Analysis (SAST): High: REDACTED |
| modules/redis/src/main/scala/zio/redis/internal/ClusterExecutor.scala | 6.7 | Mixed | Explicit Debt: TodoComment |
| modules/redis/src/main/scala/zio/redis/Output.scala | 7.0 | Mixed | Cyclomatic Complexity: StreamInfoOutput.tryDecode (cyclomatic 17) |
| modules/redis/src/main/scala/zio/redis/internal/SingleNodeSubscriptionExecutor.scala | 7.0 | Mixed | Cognitive Complexity: SingleNodeSubscriptionExecutor.create (cognitive 21) |
| modules/redis/src/main/scala/zio/redis/Input.scala | 7.0 | Mixed | God Classes: FileTooLong: redis/Input.scala |
| modules/redis/src/main/scala/zio/redis/api/SortedSets.scala | 7.0 | Mixed | God Classes: TooManyMethods: SortedSets |
| modules/redis/src/main/scala/zio/redis/api/Streams.scala | 7.2 | Mixed | God Classes: TooManyMethods: Streams |
| modules/redis-it/src/test/scala/zio/redis/StreamsSpec.scala | 8.2 | Near-clean | Explicit Debt: TodoComment |
| modules/redis/src/main/scala/zio/redis/internal/RespValue.scala | 8.5 | Near-clean | Cyclomatic Complexity: State.feed (cyclomatic 16) |
| modules/redis/src/main/scala/zio/redis/internal/RedisConnection.scala | 8.5 | Near-clean | Cognitive Complexity: RedisConnection.create (cognitive 51) |
| modules/redis/src/main/scala/zio/redis/internal/SingleNodeExecutor.scala | 8.5 | Near-clean | Cognitive Complexity: SingleNodeExecutor.create (cognitive 28) |
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 64 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 — 64 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, 94 of 103 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Canine Code Analyzer duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy · checkov | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 · 3.2.533 | ✓ deterministic |
Run transparency — what happened this run
- D8 Code Coverage — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: 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, 25 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/github/kstyrc/embedded-redis/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.
- 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.
- D34 Knowledge Freshness — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. File-level freshness contradicts repo activity: 46 commits in the last 90 days, yet 26 of 29 significant files carry no living knowledge. Those two readings cannot both be true, so the per-file recency signal is treated as unreliable here and freshness is not scored for this run.
- 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.
- DM8 Value-object opportunities — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check finds primitive parameters that travel together through several signatures of the domain (a missing value object). Its deterministic rule has not yet shown 95 % precision on adjudicated rows, so the clumps it finds are counted here and not published as findings, and the card carries no score. That is a limit of the analyzer, not a finding about your code.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
- D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
- 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.
- D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- 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.
- D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- 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.
- DM6 Domain ↔ infrastructure boundary: Infrastructure reached through a hand-rolled wrapper, a domain-named facade, reflection, or a string-keyed service locator resolves to a non-infra type and isn't seen; the body scan is symbol resolution over syntax, not full dataflow. A clean result means "no resolved infra reference in a domain body", not a proof of purity.
- P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
- P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
Dimensions
D1 · Cyclomatic Complexity
2 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was StreamInfoOutput.tryDecode at 17.
What to do
- Bring the 2 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with StreamInfoOutput.tryDecode (cyclomatic 17), State.feed (cyclomatic 16). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 2 together lifts Cyclomatic Complexity from 9.7 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
- 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
11 method(s) exceeded the cognitive complexity threshold of 15; the worst was RedisConnection.create at 51.
What to do
- Bring the 1 body over 30 down to 30 or less in Cognitive Complexity — start with RedisConnection.create (cognitive 51). — Refactoring it lifts Cognitive Complexity from 7.8 to about 8.4/10.
- 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
5 god class(es) detected.
What to do
- Resolve the 3 FileTooLong finding(s) in God Classes — start with Output.scala, SortedSets.scala, Input.scala. — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 2 TooManyMethods finding(s) in God Classes — start with SortedSets.scala, Streams.scala. — One of this dimension's main actionable groups (2 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
10 duplicated block group(s) detected. One further row reports members as variants of one another; it aggregates block groups already counted above and is not itself counted.
What to do
- Resolve the 2 Duplicated block (11 lines × 2) finding(s) in Code Duplication — start with Streams.scala (2). — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 2 Duplicated block (10 lines × 2) finding(s) in Code Duplication — start with SortedSets.scala, Streams.scala. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 2 Duplicated block (7 lines × 2) finding(s) in Code Duplication — start with SortedSets.scala (2). — One of this dimension's main actionable groups (2 warning-level).
- Enforce Code Duplication in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D5 · Coupling
4 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; 1 module(s) off the main sequence, with abstractness counted on 2 of the 4 (the rest declare no modelled class or interface, export only macros, declare types in source no model reads, or have no source directory of their own).
What to do
- Resolve the 1 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (1 warning-level).
- Enforce Coupling in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D6 · Cohesion (LCOM4)
1 of 4 classes have LCOM4 above 3.
What to do
- Resolve the 1 Low cohesion finding(s) in Cohesion (LCOM4) — start with SingleNodeSubscriptionExecutor.scala. — One of this dimension's main actionable groups (1 warning-level).
- Enforce Cohesion (LCOM4) in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D9 · Test Distribution
1246 test methods: 1246 unit, 0 integration, 0 BDD, 0 e2e. The Scala suite contributes 1246 test case(s) across 21 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.
D16 · Bus Factor
2 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is modules/redis/src/main/scala/zio/redis/internal/SingleNodeSubscriptionExecutor.scala. Counted over 29 of the 62 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
D17 · Explicit Debt
2 deducted task-comment markers across 10387 LoC (0.0/KLoC) → score 10.0. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
What to do
- Resolve the 2 TodoComment finding(s) in Explicit Debt — start with StreamsSpec.scala, ClusterExecutor.scala. — One of this dimension's main actionable groups (2 warning-level).
- Enforce Explicit Debt in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D26 · Project Cohesion
1 of 1 build units (sbt) flagged as possibly oversized/incoherent.
What to do
- Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion. — One of this dimension's main actionable groups (1 recommendation-level).
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
50 finding(s): 0 critical, 50 high, 0 medium, 0 low. 37 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. semgrep hit a parse error in 1 file(s) — `sbt` (line 71, lines 601–664) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them.
What to do
- Resolve the 12 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (4), REDACTED (3), REDACTED (2). — One of this dimension's main actionable groups (12 issue-level).
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- No action in Static Analysis (SAST) — all 37 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 (37 issue-level, 0 of them charged here).
D30 · Dependency Vulnerabilities
No known-vulnerable dependencies in any ecosystem this repository declares.
D31 · IaC & Container Security
trivy and checkov found no infrastructure-as-code or container misconfigurations.
D35 · Change Coupling
Strongest change-coupling: Input.scala↔Output.scala 50%
What to do
- Resolve the 1 Change coupling finding(s) in Change Coupling — start with Input.scala. — One of this dimension's main actionable groups (1 warning-level).
D36 · Supply-chain Provenance & Signing
1/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).
What to do
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
Frontend & cross-cutting dimensions
AX10 · Code composition
What to do
- The domain core is a small share of production code, but most of the rest matched no layer vocabulary at all — so this is not yet an anemic-domain finding. The namespace/path convention could not place that code, which makes the composition above a statement about the naming, not about the design. Name the layers (or check that the repository's conventions differ from the ones this check knows) before reading a thin domain into it.
AX3 · Project dependency cycles
AX4 · Dependency direction
AX6 · Interface segregation
AX8 · Test isolation
DM1 · Aggregate boundaries
DM11 · Constructible invalid state
DM12 · Ambient inputs in the domain
DM6 · Domain ↔ infrastructure boundary
DM9 · Scattered domain decisions
GD1 · Unfinished & placeholder code
IC1 · Incompleteness & stubs
- A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something. (×8) — modules/redis-it/src/test/scala/zio/redis/KeysSpec.scala:176, modules/redis-it/src/test/scala/zio/redis/KeysSpec.scala:188, modules/redis-it/src/test/scala/zio/redis/StreamsSpec.scala:1543, …
What to do
- Clear the softer debt: re-enable or delete `ignore`d and `pending` tests, decide whether each empty method or UnsupportedOperationException is deliberate (and say so in a comment), and replace a bare `// scalastyle:off` or `@nowarn` with targeted, justified suppressions.
M1 · Documentation (README)
What to do
- 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
- `.github/dependabot.yml` schedules updates, but no `package-ecosystem` entry covers `npm`, which this tree depends on — so those dependencies get no update pull requests and no advisory pressure, however complete the dep-scan credit looks. Add the missing entry to the `updates:` list. — .github/dependabot.yml:5
What to do
- Your ecosystem's static analyzer is declared as a dependency but is not wired into CI — run it as a required step on push/PR (e.g. `composer phpstan` / `mix sobelow` / `bundle exec brakeman` / the spotbugs Gradle task / `sbt scalafixAll --check` / `golangci-lint run` / `rebar3 lint`) so a regression fails the build instead of relying on someone running it locally.
- Dependabot is configured but does not watch `npm` — add that `package-ecosystem` entry to .github/dependabot.yml so those dependencies get the same automatic update and advisory pressure as the ones it already covers.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
P6 · Release Hygiene
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. — modules/benchmarks/src/main/scala/zio/redis/benchmarks/SetGetBenchmark.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.
PF3 · Async & latency hygiene
S1 · Web-Security Posture
- an `X509TrustManager` whose `checkServerTrusted` accepts every chain (through `TrustAllCertificates`) is set on a TLS client, so every peer certificate is accepted — including one an attacker presents. Chain, expiry, revocation and hostname are all skipped, so an attacker on the network path can present any certificate and read or rewrite the traffic — the connection is encrypted to the attacker, not to the intended host. Remove the override so the JVM's default trust manager and hostname check apply — that is what `SSLContext.getDefault`, Netty's `SslContextBuilder.forClient()`, sttp, Play WS and ssl-config use when nothing is set. If the server presents a self-signed or privately-issued certificate, trust THAT issuer rather than every certificate: load its CA into a `KeyStore` and build a `TrustManagerFactory` from it (ssl-config: `trustManager.stores`), which keeps the chain and hostname checks on. — modules/redis/src/main/scala/zio/redis/internal/RedisConnection.scala:184
What to do
- Stop accepting every TLS certificate: delete the trust manager whose `checkServerTrusted` is empty, the `HostnameVerifier` that returns `true`, `InsecureTrustManagerFactory` / `NoopHostnameVerifier` and `acceptAnyCertificate`, and trust a self-signed or private server by giving the client a trust store holding its CA — never by switching verification off.
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 56 Scala product file(s) passes `-Yexplicit-nulls`, enables WartRemover's `Null` wart or runs Scalafix's `DisableSyntax.noNulls`, so every reference type admits null and nothing reports a `null` written into the code or returned from a Java API — the first one to reach a method call is a `NullPointerException`. `Option` by convention is a habit no tool here holds the code to.
What to do
- On Scala 3, add `-Yexplicit-nulls` to `scalacOptions` so `String` and `String | Null` mean different things, and type each Java API's result as nullable where it can return null; on Scala 2 (or as a first step), enable WartRemover's `Null` wart (`wartremoverErrors += Wart.Null`) or Scalafix's `DisableSyntax.noNulls = true` so the code holds absence in `Option`. Then pay the assertions down rather than adding to them: each `.nn` is a null the compiler could not rule out — wrap the Java value in `Option(…)` at the boundary, pattern-match on `null` once there, or change the API so the null cannot arrive; an `unsafeNulls` import switches the checking off for everything after it.
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 73% | Adequate — gated by X5 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 72% | Adequate — gated by D26 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Maturity | 62% | Adequate — gated by M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 85% | Strong | Solid. |
| Security | 59% | Adequate — gated by D29, D36 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Domain Modelling | 100% | Exemplary | Strongest area. |
| Performance | 89% | Strong | Solid. |
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 — 65 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
- 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 — ~13640 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 2 pinned sbt dependency coordinate(s) were read from its 2 sbt build file(s), but Maven Central could not be asked for the licence of 2 of them (HTTP 429 Too Many Requests from http://172.31.7.1:8790/maven/com/github/kstyrc/embedded-redis/0.6/embedded-redis-0.6.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.
- 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. Aggregate roots were found in only one source directory (redis), which is a layered codebase, not two contexts. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D24 Comment Value — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only; comments in this repository's .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.
- 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.
- D34 Knowledge Freshness — knowledge concentrated in recent work — freshness signal contradicted by repo activity
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- D39 IL Efficiency — D39 measures the IL emitted by a .NET build; this repository has no .NET solution or project files, so the dimension does not apply.
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D44 Platform End-of-Life — Platform end-of-life not assessed — this repository declares no platform this pass reads
- D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
- D8 Code Coverage — Coverage not included — suite not readable by the collector
- DM10 One transaction, one aggregate — no repository writes detected — no operation to judge against the one-aggregate rule
- DM2 Strongly-typed ids — no id-bearing domain types detected — strongly-typed-id adoption not assessable
- DM3 Integration-event coupling — no integration events detected — coupling check not applicable
- DM4 Rich vs anemic model — no data-bearing entities detected — rich-vs-anemic model not assessable
- DM5 Encapsulated state — no domain entities found — DM5 grades how entities protect their state, and this repository declares none
- DM7 Repository granularity — no repository abstraction detected (e.g. uses a document session)
- DM8 Value-object opportunities — not scored — the deterministic rule found 0 candidate clump(s); its rows are withheld until it has a measured precision of 95 % (a sample of fewer than 10 rows cannot show one)
- ED1 Event-Driven — not scored — this repository shows 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 23 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, JavaScript/TypeScript source (2 module(s), 58 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
- PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
- X10 Duplicated predicate — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- 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 — 51 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- TLS certificate validation disabled modules/redis/src/main/scala/zio/redis/internal/RedisConnection.scala:184
Serious — 36 finding(s)
- FileTooLong: redis/Output.scala modules/redis/src/main/scala/zio/redis/Output.scala
- FileTooLong: api/SortedSets.scala modules/redis/src/main/scala/zio/redis/api/SortedSets.scala
- FileTooLong: redis/Input.scala modules/redis/src/main/scala/zio/redis/Input.scala
- TodoComment modules/redis-it/src/test/scala/zio/redis/StreamsSpec.scala:1535
- TodoComment modules/redis/src/main/scala/zio/redis/internal/ClusterExecutor.scala:71
- TooManyMethods: SortedSets modules/redis/src/main/scala/zio/redis/api/SortedSets.scala:27
- TooManyMethods: Streams modules/redis/src/main/scala/zio/redis/api/Streams.scala:26
- Duplicated block (11 lines × 2) modules/redis/src/main/scala/zio/redis/api/Streams.scala:821
- Duplicated block (11 lines × 2) modules/redis/src/main/scala/zio/redis/api/Streams.scala:973
- Duplicated block (10 lines × 2) modules/redis/src/main/scala/zio/redis/api/SortedSets.scala:125
- Duplicated block (10 lines × 2) modules/redis/src/main/scala/zio/redis/api/Streams.scala:130
- Duplicated block (7 lines × 2) modules/redis/src/main/scala/zio/redis/api/SortedSets.scala:241
- Duplicated block (7 lines × 2) modules/redis/src/main/scala/zio/redis/api/SortedSets.scala:656
- Duplicated block (5 lines × 2) modules/redis/src/main/scala/zio/redis/Output.scala:89
- Duplicated block (5 lines × 2) modules/redis/src/main/scala/zio/redis/api/SortedSets.scala:1018
- StreamInfoOutput.tryDecode (cyclomatic 17) modules/redis/src/main/scala/zio/redis/Output.scala:556
- State.feed (cyclomatic 16) modules/redis/src/main/scala/zio/redis/internal/RespValue.scala:175
- RedisConnection.create (cognitive 51) modules/redis/src/main/scala/zio/redis/internal/RedisConnection.scala:48
- Output.extractXInfoFullGroup (cognitive 29) modules/redis/src/main/scala/zio/redis/Output.scala:780
- SingleNodeExecutor.create (cognitive 28) modules/redis/src/main/scala/zio/redis/internal/SingleNodeExecutor.scala:84
- StreamGroupsInfoOutput.tryDecode (cognitive 27) modules/redis/src/main/scala/zio/redis/Output.scala:459
- StreamInfoOutput.tryDecode (cognitive 27) modules/redis/src/main/scala/zio/redis/Output.scala:556
- LcsOutput.tryDecode (cognitive 21) modules/redis/src/main/scala/zio/redis/Output.scala:322
- SingleNodeSubscriptionExecutor.create (cognitive 21) modules/redis/src/main/scala/zio/redis/internal/SingleNodeSubscriptionExecutor.scala:244
- StreamConsumersInfoOutput.tryDecode (cognitive 20) modules/redis/src/main/scala/zio/redis/Output.scala:353
- Output.extractXInfoFullConsumer (cognitive 18) modules/redis/src/main/scala/zio/redis/Output.scala:840
- StreamInfoFullOutput.tryDecode (cognitive 18) modules/redis/src/main/scala/zio/redis/Output.scala:503
- ClusterExecutor.execute (cognitive 16) modules/redis/src/main/scala/zio/redis/internal/ClusterExecutor.scala:33
- Change coupling: Input.scala ↔ Output.scala modules/redis/src/main/scala/zio/redis/Input.scala:1
- REDACTED
- REDACTED
- Members sharing a duplicated core (4 members, 50+ identical tokens) modules/redis/src/main/scala/zio/redis/api/SortedSets.scala:48
- Duplicated block (6 lines × 2) modules/redis/src/main/scala/zio/redis/api/SortedSets.scala:52
- Duplicated block (5 lines × 4) modules/redis/src/main/scala/zio/redis/api/SortedSets.scala:52
- Off the main sequence: client
- Low cohesion: SingleNodeSubscriptionExecutor (LCOM4 4) modules/redis/src/main/scala/zio/redis/internal/SingleNodeSubscriptionExecutor.scala:30
Minor — 16 finding(s)
- Disabled test modules/redis-it/src/test/scala/zio/redis/KeysSpec.scala:176
- Disabled test modules/redis-it/src/test/scala/zio/redis/KeysSpec.scala:188
- Disabled test modules/redis-it/src/test/scala/zio/redis/StreamsSpec.scala:1543
- Disabled test modules/redis-it/src/test/scala/zio/redis/StreamsSpec.scala:1551
- Disabled test modules/redis-it/src/test/scala/zio/redis/StreamsSpec.scala:1559
- Disabled test modules/redis-it/src/test/scala/zio/redis/StringsSpec.scala:1580
- Disabled test modules/redis-it/src/test/scala/zio/redis/StringsSpec.scala:1589
- Disabled test modules/redis-it/src/test/scala/zio/redis/StringsSpec.scala:1598
- Off-boarding risk: anonymized user #1
- Projects may be oversized for their cohesion
- REDACTED
- REDACTED
- No ADRs
- Dependabot does not watch npm .github/dependabot.yml:5
- Benchmarks don't track allocations modules/benchmarks/src/main/scala/zio/redis/benchmarks/SetGetBenchmark.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-a959f043da8342a4a0f216912c9bef45/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-a959f043da8342a4a0f216912c9bef45/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 . | 50 | 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 config --format json --quiet . | 0 | artifacts/raw/trivy-config.json |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. | 0 | — |
| D37 · Vulnerability-disclosure Policy | disclosure | — | disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . --skip-db-update | 0 | artifacts/raw/trivy-fs.json |