Executive summary
Horusiath/Akkling falls short of our standard for a preview release because 64 files are no longer known to anyone active in the project and we found no recorded design decisions and no architecture document or diagram. It scores 56 out of 100 and is rated Adequate, and it has no critical findings.
Maturity, at 41, is the weakest lens and counts most in the score. The best first step is having someone learn and document the 64 files no active contributor knows, worth about 12 points. Recording design decisions comes next, worth about 8 points. Raising Maturity to 62 would lift the score to about 62.
Most of the 68 serious findings are in Code Health.
The product code is 13,281 lines, about €15,000 to rebuild.
If Maturity rose from 41 to 62, the lowest score rated Strong, the score would rise from 56 to about 62.
New since the last survey: 3 findings
- Code Duplication · Edited copy of a member (126 corresponding lines) src/Akkling.Hocon/Cluster.FailureDetector.fs
- Code Duplication · Edited copy of a member (47 corresponding lines) src/Akkling.Hocon/Persistence.AtLeastOnceDelivery.fs
- Code Duplication · Edited copy of a member (23 corresponding lines) src/Akkling.Hocon/Actor.Inbox.fs
Fixed since the last survey: 9 findings
- Code Duplication · Duplicated block (11 lines × 2) src/Akkling.Persistence/PersistentActor.fs
- Code Duplication · Near-duplicate member pair (82 shared lines) src/Akkling.Streams.TestKit.Xunit/Library.fs
- Code Duplication · Near-duplicate member pair (80 shared lines) src/Akkling.TestKit.Xunit/TestKit.fs
- Code Duplication · Duplicated block (26 lines × 2) src/Akkling.TestKit.Xunit/TestKit.fs
- Code Duplication · Duplicated block (17 lines × 2) src/Akkling.Streams.TestKit.Xunit/Library.fs
- Code Duplication · Duplicated block (10 lines × 2) src/Akkling.Streams.TestKit.Xunit/Library.fs
- Code Duplication · Duplicated block (5 lines × 2) src/Akkling.TestKit.Xunit/TestKit.fs
- Code Duplication · Duplicated block (7 lines × 2) src/Akkling.TestKit.Xunit/TestKit.fs
- Code Coverage · Coverage not measured — no coverage collector is wired up
Rebuild cost: about €15,000 · Estimate
| Cost to rebuild | €5,000 to €25,000, for 84 to 267 hours of work, about 0.1 person-years for one engineer |
|---|---|
| Difficulty of the problem | Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.8 at a score of 56. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it. |
| Size | Small: 13,281 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 ActorRefs | 2 Hocon.Hocon | 3 Hocon.InternalHocon | 4 Hocon.SharedInternal | 5 Hocon.Types.MarkerClasses | 6 Props | 7 Actors | 8 Hocon.Debug | 9 Hocon.Pools | 10 Hocon.Types.MarkerClasses.Akka | 11 Hocon.Types.MarkerClasses.Akka.Actor | 12 Hocon.Types.MarkerClasses.Akka.Actor.Dispatcher | 13 Hocon.Types.MarkerClasses.Akka.Cluster | 14 Hocon.Types.MarkerClasses.Akka.Persistence | 15 Hocon.Types.MarkerClasses.Akka.Persistence.Plugin | 16 Hocon.Types.MarkerClasses.Akka.Remote | 17 Hocon.Types.MarkerClasses.Akka.Remote.Batching | 18 Hocon.Types.MarkerClasses.Akka.Remote.WorkerPool | 19 Hocon.Akka | 20 Hocon.Dispatcher | 21 Hocon.Metrics | 22 Hocon.Plugin | 23 Hocon.Protocols | 24 Hocon.Streams | 25 Persistence | 26 Cluster.Sharding.ClusterSharding | 27 Hocon.Cluster | 28 Hocon.Proxy | 29 Hocon.Tcp | 30 Hocon.Udp | 31 Hocon.Deployment | 32 Hocon.DotNetty | 33 Hocon.IO | 34 Hocon.Journal | 35 Hocon.PluginFallback | 36 Hocon.SnapshotStore | 37 Hocon.Actor | 38 Hocon.Persistence | 39 Hocon.Remote | 40 Hocon.Test |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 ActorRefs | ||||||||||||||||||||||||||||||||||||||||
| 2 Hocon.Hocon | ||||||||||||||||||||||||||||||||||||||||
| 3 Hocon.InternalHocon | ||||||||||||||||||||||||||||||||||||||||
| 4 Hocon.SharedInternal | ||||||||||||||||||||||||||||||||||||||||
| 5 Hocon.Types.MarkerClasses | ||||||||||||||||||||||||||||||||||||||||
| 6 Props | ||||||||||||||||||||||||||||||||||||||||
| 7 Actors | 3 | |||||||||||||||||||||||||||||||||||||||
| 8 Hocon.Debug | 1 | |||||||||||||||||||||||||||||||||||||||
| 9 Hocon.Pools | 2 | |||||||||||||||||||||||||||||||||||||||
| 10 Hocon.Types.MarkerClasses.Akka | 1 | |||||||||||||||||||||||||||||||||||||||
| 11 Hocon.Types.MarkerClasses.Akka.Actor | 1 | |||||||||||||||||||||||||||||||||||||||
| 12 Hocon.Types.MarkerClasses.Akka.Actor.Dispatcher | 1 | |||||||||||||||||||||||||||||||||||||||
| 13 Hocon.Types.MarkerClasses.Akka.Cluster | 1 | |||||||||||||||||||||||||||||||||||||||
| 14 Hocon.Types.MarkerClasses.Akka.Persistence | 1 | |||||||||||||||||||||||||||||||||||||||
| 15 Hocon.Types.MarkerClasses.Akka.Persistence.Plugin | 1 | |||||||||||||||||||||||||||||||||||||||
| 16 Hocon.Types.MarkerClasses.Akka.Remote | 1 | |||||||||||||||||||||||||||||||||||||||
| 17 Hocon.Types.MarkerClasses.Akka.Remote.Batching | 1 | |||||||||||||||||||||||||||||||||||||||
| 18 Hocon.Types.MarkerClasses.Akka.Remote.WorkerPool | 1 | |||||||||||||||||||||||||||||||||||||||
| 19 Hocon.Akka | 2 | 1 | 2 | |||||||||||||||||||||||||||||||||||||
| 20 Hocon.Dispatcher | 4 | 4 | 1 | |||||||||||||||||||||||||||||||||||||
| 21 Hocon.Metrics | 4 | 1 | ||||||||||||||||||||||||||||||||||||||
| 22 Hocon.Plugin | 2 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 23 Hocon.Protocols | 2 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 24 Hocon.Streams | 4 | 2 | ||||||||||||||||||||||||||||||||||||||
| 25 Persistence | 1 | 8 | ||||||||||||||||||||||||||||||||||||||
| 26 Cluster.Sharding.ClusterSharding | 1 | 1 | 3 | 1 | ||||||||||||||||||||||||||||||||||||
| 27 Hocon.Cluster | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 28 Hocon.Proxy | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 29 Hocon.Tcp | 3 | 1 | 2 | 1 | 1 | 2 | ||||||||||||||||||||||||||||||||||
| 30 Hocon.Udp | 3 | 1 | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||
| 31 Hocon.Deployment | 1 | 4 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 32 Hocon.DotNetty | 1 | 3 | 1 | 1 | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||
| 33 Hocon.IO | 1 | 2 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 34 Hocon.Journal | 1 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 35 Hocon.PluginFallback | 1 | 1 | 2 | 1 | ||||||||||||||||||||||||||||||||||||
| 36 Hocon.SnapshotStore | 3 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 37 Hocon.Actor | 1 | 1 | 1 | 2 | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||
| 38 Hocon.Persistence | 1 | 2 | 1 | 1 | 1 | 2 | 2 | |||||||||||||||||||||||||||||||||
| 39 Hocon.Remote | 1 | 2 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 40 Hocon.Test | 1 | 2 | 1 | 2 |
7→1 Actors uses ActorRefs✕
- Connections
- 3 pairs of types, where a type in Actors uses a type in ActorRefs.
- The types involved
Akkling.Actors.Actor`1→Akkling.ActorRefs.IActorRef`1Akkling.Actors.ExtContext→Akkling.ActorRefs.IActorRef`1Akkling.Actors.TypedContext`2→Akkling.ActorRefs.IActorRef`1
- Direction
- Actors uses ActorRefs, so a change to ActorRefs can break Actors, while a change to Actors can't break ActorRefs.
- Position
- Below the diagonal: Actors uses a module listed above it, which is the healthy direction.
8→4 Hocon.Debug uses Hocon.SharedInternal✕
- Connections
- 1 pair of types, where a type in Hocon.Debug uses a type in Hocon.SharedInternal.
- The types involved
Akkling.Hocon.Debug.DebugBuilder`1→Akkling.Hocon.SharedInternal.State`1
- Direction
- Hocon.Debug uses Hocon.SharedInternal, so a change to Hocon.SharedInternal can break Hocon.Debug, while a change to Hocon.Debug can't break Hocon.SharedInternal.
- Position
- Below the diagonal: Hocon.Debug uses a module listed above it, which is the healthy direction.
9→3 Hocon.Pools uses Hocon.InternalHocon✕
- Connections
- 2 pairs of types, where a type in Hocon.Pools uses a type in Hocon.InternalHocon.
- The types involved
Akkling.Hocon.Pools.DirectBufferPoolBuilder`1→Akkling.Hocon.InternalHocon.BaseBuilder`1Akkling.Hocon.Pools.DisabledBufferPoolBuilder`1→Akkling.Hocon.InternalHocon.BaseBuilder`1
- Direction
- Hocon.Pools uses Hocon.InternalHocon, so a change to Hocon.InternalHocon can break Hocon.Pools, while a change to Hocon.Pools can't break Hocon.InternalHocon.
- Position
- Below the diagonal: Hocon.Pools uses a module listed above it, which is the healthy direction.
10→5 Hocon.Types.MarkerClasses.Akka uses Hocon.Types.MarkerClasses✕
- Connections
- 1 pair of types, where a type in Hocon.Types.MarkerClasses.Akka uses a type in Hocon.Types.MarkerClasses.
- The types involved
Akkling.Hocon.Types.MarkerClasses.Akka.Field→Akkling.Hocon.Types.MarkerClasses.IField
- Direction
- Hocon.Types.MarkerClasses.Akka uses Hocon.Types.MarkerClasses, so a change to Hocon.Types.MarkerClasses can break Hocon.Types.MarkerClasses.Akka, while a change to Hocon.Types.MarkerClasses.Akka can't break Hocon.Types.MarkerClasses.
- Position
- Below the diagonal: Hocon.Types.MarkerClasses.Akka uses a module listed above it, which is the healthy direction.
11→5 Hocon.Types.MarkerClasses.Akka.Actor uses Hocon.Types.MarkerClasses✕
- Connections
- 1 pair of types, where a type in Hocon.Types.MarkerClasses.Akka.Actor uses a type in Hocon.Types.MarkerClasses.
- The types involved
Akkling.Hocon.Types.MarkerClasses.Akka.Actor.Field→Akkling.Hocon.Types.MarkerClasses.IField
- Direction
- Hocon.Types.MarkerClasses.Akka.Actor uses Hocon.Types.MarkerClasses, so a change to Hocon.Types.MarkerClasses can break Hocon.Types.MarkerClasses.Akka.Actor, while a change to Hocon.Types.MarkerClasses.Akka.Actor can't break Hocon.Types.MarkerClasses.
- Position
- Below the diagonal: Hocon.Types.MarkerClasses.Akka.Actor uses a module listed above it, which is the healthy direction.
12→5 Hocon.Types.MarkerClasses.Akka.Actor.Dispatcher uses Hocon.Types.MarkerClasses✕
- Connections
- 1 pair of types, where a type in Hocon.Types.MarkerClasses.Akka.Actor.Dispatcher uses a type in Hocon.Types.MarkerClasses.
- The types involved
Akkling.Hocon.Types.MarkerClasses.Akka.Actor.Dispatcher.Field→Akkling.Hocon.Types.MarkerClasses.IField
- Direction
- Hocon.Types.MarkerClasses.Akka.Actor.Dispatcher uses Hocon.Types.MarkerClasses, so a change to Hocon.Types.MarkerClasses can break Hocon.Types.MarkerClasses.Akka.Actor.Dispatcher, while a change to Hocon.Types.MarkerClasses.Akka.Actor.Dispatcher can't break Hocon.Types.MarkerClasses.
- Position
- Below the diagonal: Hocon.Types.MarkerClasses.Akka.Actor.Dispatcher uses a module listed above it, which is the healthy direction.
13→5 Hocon.Types.MarkerClasses.Akka.Cluster uses Hocon.Types.MarkerClasses✕
- Connections
- 1 pair of types, where a type in Hocon.Types.MarkerClasses.Akka.Cluster uses a type in Hocon.Types.MarkerClasses.
- The types involved
Akkling.Hocon.Types.MarkerClasses.Akka.Cluster.Field→Akkling.Hocon.Types.MarkerClasses.IField
- Direction
- Hocon.Types.MarkerClasses.Akka.Cluster uses Hocon.Types.MarkerClasses, so a change to Hocon.Types.MarkerClasses can break Hocon.Types.MarkerClasses.Akka.Cluster, while a change to Hocon.Types.MarkerClasses.Akka.Cluster can't break Hocon.Types.MarkerClasses.
- Position
- Below the diagonal: Hocon.Types.MarkerClasses.Akka.Cluster uses a module listed above it, which is the healthy direction.
14→5 Hocon.Types.MarkerClasses.Akka.Persistence uses Hocon.Types.MarkerClasses✕
- Connections
- 1 pair of types, where a type in Hocon.Types.MarkerClasses.Akka.Persistence uses a type in Hocon.Types.MarkerClasses.
- The types involved
Akkling.Hocon.Types.MarkerClasses.Akka.Persistence.Field→Akkling.Hocon.Types.MarkerClasses.IField
- Direction
- Hocon.Types.MarkerClasses.Akka.Persistence uses Hocon.Types.MarkerClasses, so a change to Hocon.Types.MarkerClasses can break Hocon.Types.MarkerClasses.Akka.Persistence, while a change to Hocon.Types.MarkerClasses.Akka.Persistence can't break Hocon.Types.MarkerClasses.
- Position
- Below the diagonal: Hocon.Types.MarkerClasses.Akka.Persistence uses a module listed above it, which is the healthy direction.
15→5 Hocon.Types.MarkerClasses.Akka.Persistence.Plugin uses Hocon.Types.MarkerClasses✕
- Connections
- 1 pair of types, where a type in Hocon.Types.MarkerClasses.Akka.Persistence.Plugin uses a type in Hocon.Types.MarkerClasses.
- The types involved
Akkling.Hocon.Types.MarkerClasses.Akka.Persistence.Plugin.Field→Akkling.Hocon.Types.MarkerClasses.IField
- Direction
- Hocon.Types.MarkerClasses.Akka.Persistence.Plugin uses Hocon.Types.MarkerClasses, so a change to Hocon.Types.MarkerClasses can break Hocon.Types.MarkerClasses.Akka.Persistence.Plugin, while a change to Hocon.Types.MarkerClasses.Akka.Persistence.Plugin can't break Hocon.Types.MarkerClasses.
- Position
- Below the diagonal: Hocon.Types.MarkerClasses.Akka.Persistence.Plugin uses a module listed above it, which is the healthy direction.
16→5 Hocon.Types.MarkerClasses.Akka.Remote uses Hocon.Types.MarkerClasses✕
- Connections
- 1 pair of types, where a type in Hocon.Types.MarkerClasses.Akka.Remote uses a type in Hocon.Types.MarkerClasses.
- The types involved
Akkling.Hocon.Types.MarkerClasses.Akka.Remote.Field→Akkling.Hocon.Types.MarkerClasses.IField
- Direction
- Hocon.Types.MarkerClasses.Akka.Remote uses Hocon.Types.MarkerClasses, so a change to Hocon.Types.MarkerClasses can break Hocon.Types.MarkerClasses.Akka.Remote, while a change to Hocon.Types.MarkerClasses.Akka.Remote can't break Hocon.Types.MarkerClasses.
- Position
- Below the diagonal: Hocon.Types.MarkerClasses.Akka.Remote uses a module listed above it, which is the healthy direction.
17→5 Hocon.Types.MarkerClasses.Akka.Remote.Batching uses Hocon.Types.MarkerClasses✕
- Connections
- 1 pair of types, where a type in Hocon.Types.MarkerClasses.Akka.Remote.Batching uses a type in Hocon.Types.MarkerClasses.
- The types involved
Akkling.Hocon.Types.MarkerClasses.Akka.Remote.Batching.Field→Akkling.Hocon.Types.MarkerClasses.IField
- Direction
- Hocon.Types.MarkerClasses.Akka.Remote.Batching uses Hocon.Types.MarkerClasses, so a change to Hocon.Types.MarkerClasses can break Hocon.Types.MarkerClasses.Akka.Remote.Batching, while a change to Hocon.Types.MarkerClasses.Akka.Remote.Batching can't break Hocon.Types.MarkerClasses.
- Position
- Below the diagonal: Hocon.Types.MarkerClasses.Akka.Remote.Batching uses a module listed above it, which is the healthy direction.
18→5 Hocon.Types.MarkerClasses.Akka.Remote.WorkerPool uses Hocon.Types.MarkerClasses✕
- Connections
- 1 pair of types, where a type in Hocon.Types.MarkerClasses.Akka.Remote.WorkerPool uses a type in Hocon.Types.MarkerClasses.
- The types involved
Akkling.Hocon.Types.MarkerClasses.Akka.Remote.WorkerPool.Field→Akkling.Hocon.Types.MarkerClasses.IField
- Direction
- Hocon.Types.MarkerClasses.Akka.Remote.WorkerPool uses Hocon.Types.MarkerClasses, so a change to Hocon.Types.MarkerClasses can break Hocon.Types.MarkerClasses.Akka.Remote.WorkerPool, while a change to Hocon.Types.MarkerClasses.Akka.Remote.WorkerPool can't break Hocon.Types.MarkerClasses.
- Position
- Below the diagonal: Hocon.Types.MarkerClasses.Akka.Remote.WorkerPool uses a module listed above it, which is the healthy direction.
19→2 Hocon.Akka uses Hocon.Hocon✕
- Connections
- 2 pairs of types, where a type in Hocon.Akka uses a type in Hocon.Hocon.
- The types involved
Akkling.Hocon.Akka.AkkaBuilder→Akkling.Hocon.Hocon.InfiniteAkkling.Hocon.Akka.AkkaBuilder→Akkling.Hocon.Hocon.LogLevel
- Direction
- Hocon.Akka uses Hocon.Hocon, so a change to Hocon.Hocon can break Hocon.Akka, while a change to Hocon.Akka can't break Hocon.Hocon.
- Position
- Below the diagonal: Hocon.Akka uses a module listed above it, which is the healthy direction.
19→3 Hocon.Akka uses Hocon.InternalHocon✕
- Connections
- 1 pair of types, where a type in Hocon.Akka uses a type in Hocon.InternalHocon.
- The types involved
Akkling.Hocon.Akka.SslConfigBuilder`1→Akkling.Hocon.InternalHocon.BaseBuilder`1
- Direction
- Hocon.Akka uses Hocon.InternalHocon, so a change to Hocon.InternalHocon can break Hocon.Akka, while a change to Hocon.Akka can't break Hocon.InternalHocon.
- Position
- Below the diagonal: Hocon.Akka uses a module listed above it, which is the healthy direction.
19→10 Hocon.Akka uses Hocon.Types.MarkerClasses.Akka✕
- Connections
- 2 pairs of types, where a type in Hocon.Akka uses a type in Hocon.Types.MarkerClasses.Akka.
- The types involved
Akkling.Hocon.Akka.Akka→Akkling.Hocon.Types.MarkerClasses.Akka.FieldAkkling.Hocon.Akka.AkkaBuilder→Akkling.Hocon.Types.MarkerClasses.Akka.Field
- Direction
- Hocon.Akka uses Hocon.Types.MarkerClasses.Akka, so a change to Hocon.Types.MarkerClasses.Akka can break Hocon.Akka, while a change to Hocon.Akka can't break Hocon.Types.MarkerClasses.Akka.
- Position
- Below the diagonal: Hocon.Akka uses a module listed above it, which is the healthy direction.
20→2 Hocon.Dispatcher uses Hocon.Hocon✕
- Connections
- 4 pairs of types, where a type in Hocon.Dispatcher uses a type in Hocon.Hocon.
- The types involved
Akkling.Hocon.Dispatcher.DedicatedThreadPoolBuilder`1→Akkling.Hocon.Hocon.ThreadTypeAkkling.Hocon.Dispatcher.DispatcherBuilder`1→Akkling.Hocon.Hocon.DispatcherAkkling.Hocon.Dispatcher.DispatcherBuilder`1→Akkling.Hocon.Hocon.ExecutorAkkling.Hocon.Dispatcher.ForkJoinExecutorBuilder`1→Akkling.Hocon.Hocon.TaskPeekingMode
- Direction
- Hocon.Dispatcher uses Hocon.Hocon, so a change to Hocon.Hocon can break Hocon.Dispatcher, while a change to Hocon.Dispatcher can't break Hocon.Hocon.
- Position
- Below the diagonal: Hocon.Dispatcher uses a module listed above it, which is the healthy direction.
20→3 Hocon.Dispatcher uses Hocon.InternalHocon✕
- Connections
- 4 pairs of types, where a type in Hocon.Dispatcher uses a type in Hocon.InternalHocon.
- The types involved
Akkling.Hocon.Dispatcher.DedicatedThreadPoolBuilder`1→Akkling.Hocon.InternalHocon.BaseBuilder`1Akkling.Hocon.Dispatcher.Dispatcher→Akkling.Hocon.InternalHocon.BaseBuilder`1Akkling.Hocon.Dispatcher.DispatcherBuilder`1→Akkling.Hocon.InternalHocon.BaseBuilder`1Akkling.Hocon.Dispatcher.ForkJoinExecutorBuilder`1→Akkling.Hocon.InternalHocon.BaseBuilder`1
- Direction
- Hocon.Dispatcher uses Hocon.InternalHocon, so a change to Hocon.InternalHocon can break Hocon.Dispatcher, while a change to Hocon.Dispatcher can't break Hocon.InternalHocon.
- Position
- Below the diagonal: Hocon.Dispatcher uses a module listed above it, which is the healthy direction.
20→12 Hocon.Dispatcher uses Hocon.Types.MarkerClasses.Akka.Actor.Dispatcher✕
- Connections
- 1 pair of types, where a type in Hocon.Dispatcher uses a type in Hocon.Types.MarkerClasses.Akka.Actor.Dispatcher.
- The types involved
Akkling.Hocon.Dispatcher.Dispatcher→Akkling.Hocon.Types.MarkerClasses.Akka.Actor.Dispatcher.Field
- Direction
- Hocon.Dispatcher uses Hocon.Types.MarkerClasses.Akka.Actor.Dispatcher, so a change to Hocon.Types.MarkerClasses.Akka.Actor.Dispatcher can break Hocon.Dispatcher, while a change to Hocon.Dispatcher can't break Hocon.Types.MarkerClasses.Akka.Actor.Dispatcher.
- Position
- Below the diagonal: Hocon.Dispatcher uses a module listed above it, which is the healthy direction.
21→3 Hocon.Metrics uses Hocon.InternalHocon✕
- Connections
- 4 pairs of types, where a type in Hocon.Metrics uses a type in Hocon.InternalHocon.
- The types involved
Akkling.Hocon.Metrics.ConfigurationBuilder`1→Akkling.Hocon.InternalHocon.BaseBuilder`1Akkling.Hocon.Metrics.MetricsBuilder`1→Akkling.Hocon.InternalHocon.BaseBuilder`1Akkling.Hocon.Metrics.StrategyBuilder`1→Akkling.Hocon.InternalHocon.BaseBuilder`1Akkling.Hocon.Metrics.SupervisorBuilder`1→Akkling.Hocon.InternalHocon.BaseBuilder`1
- Direction
- Hocon.Metrics uses Hocon.InternalHocon, so a change to Hocon.InternalHocon can break Hocon.Metrics, while a change to Hocon.Metrics can't break Hocon.InternalHocon.
- Position
- Below the diagonal: Hocon.Metrics uses a module listed above it, which is the healthy direction.
21→13 Hocon.Metrics uses Hocon.Types.MarkerClasses.Akka.Cluster✕
- Connections
- 1 pair of types, where a type in Hocon.Metrics uses a type in Hocon.Types.MarkerClasses.Akka.Cluster.
- The types involved
Akkling.Hocon.Metrics.Metrics→Akkling.Hocon.Types.MarkerClasses.Akka.Cluster.Field
- Direction
- Hocon.Metrics uses Hocon.Types.MarkerClasses.Akka.Cluster, so a change to Hocon.Types.MarkerClasses.Akka.Cluster can break Hocon.Metrics, while a change to Hocon.Metrics can't break Hocon.Types.MarkerClasses.Akka.Cluster.
- Position
- Below the diagonal: Hocon.Metrics uses a module listed above it, which is the healthy direction.
22→3 Hocon.Plugin uses Hocon.InternalHocon✕
- Connections
- 2 pairs of types, where a type in Hocon.Plugin uses a type in Hocon.InternalHocon.
- The types involved
Akkling.Hocon.Plugin.CircuitBreakerBuilder`1→Akkling.Hocon.InternalHocon.BaseBuilder`1Akkling.Hocon.Plugin.ReplayFilterBuilder`1→Akkling.Hocon.InternalHocon.BaseBuilder`1
- Direction
- Hocon.Plugin uses Hocon.InternalHocon, so a change to Hocon.InternalHocon can break Hocon.Plugin, while a change to Hocon.Plugin can't break Hocon.InternalHocon.
- Position
- Below the diagonal: Hocon.Plugin uses a module listed above it, which is the healthy direction.
22→4 Hocon.Plugin uses Hocon.SharedInternal✕
- Connections
- 1 pair of types, where a type in Hocon.Plugin uses a type in Hocon.SharedInternal.
- The types involved
Akkling.Hocon.Plugin.PluginBuilder`1→Akkling.Hocon.SharedInternal.State`1
- Direction
- Hocon.Plugin uses Hocon.SharedInternal, so a change to Hocon.SharedInternal can break Hocon.Plugin, while a change to Hocon.Plugin can't break Hocon.SharedInternal.
- Position
- Below the diagonal: Hocon.Plugin uses a module listed above it, which is the healthy direction.
22→15 Hocon.Plugin uses Hocon.Types.MarkerClasses.Akka.Persistence.Plugin✕
- Connections
- 1 pair of types, where a type in Hocon.Plugin uses a type in Hocon.Types.MarkerClasses.Akka.Persistence.Plugin.
- The types involved
Akkling.Hocon.Plugin.Plugin→Akkling.Hocon.Types.MarkerClasses.Akka.Persistence.Plugin.Field
- Direction
- Hocon.Plugin uses Hocon.Types.MarkerClasses.Akka.Persistence.Plugin, so a change to Hocon.Types.MarkerClasses.Akka.Persistence.Plugin can break Hocon.Plugin, while a change to Hocon.Plugin can't break Hocon.Types.MarkerClasses.Akka.Persistence.Plugin.
- Position
- Below the diagonal: Hocon.Plugin uses a module listed above it, which is the healthy direction.
23→3 Hocon.Protocols uses Hocon.InternalHocon✕
- Connections
- 2 pairs of types, where a type in Hocon.Protocols uses a type in Hocon.InternalHocon.
- The types involved
Akkling.Hocon.Protocols.BatchingBuilder`1→Akkling.Hocon.InternalHocon.BaseBuilder`1Akkling.Hocon.Protocols.WorkerPoolBuilder`1→Akkling.Hocon.InternalHocon.BaseBuilder`1
- Direction
- Hocon.Protocols uses Hocon.InternalHocon, so a change to Hocon.InternalHocon can break Hocon.Protocols, while a change to Hocon.Protocols can't break Hocon.InternalHocon.
- Position
- Below the diagonal: Hocon.Protocols uses a module listed above it, which is the healthy direction.
23→17 Hocon.Protocols uses Hocon.Types.MarkerClasses.Akka.Remote.Batching✕
- Connections
- 1 pair of types, where a type in Hocon.Protocols uses a type in Hocon.Types.MarkerClasses.Akka.Remote.Batching.
- The types involved
Akkling.Hocon.Protocols.Protocols→Akkling.Hocon.Types.MarkerClasses.Akka.Remote.Batching.Field
- Direction
- Hocon.Protocols uses Hocon.Types.MarkerClasses.Akka.Remote.Batching, so a change to Hocon.Types.MarkerClasses.Akka.Remote.Batching can break Hocon.Protocols, while a change to Hocon.Protocols can't break Hocon.Types.MarkerClasses.Akka.Remote.Batching.
- Position
- Below the diagonal: Hocon.Protocols uses a module listed above it, which is the healthy direction.
23→18 Hocon.Protocols uses Hocon.Types.MarkerClasses.Akka.Remote.WorkerPool✕
- Connections
- 1 pair of types, where a type in Hocon.Protocols uses a type in Hocon.Types.MarkerClasses.Akka.Remote.WorkerPool.
- The types involved
Akkling.Hocon.Protocols.Protocols→Akkling.Hocon.Types.MarkerClasses.Akka.Remote.WorkerPool.Field
- Direction
- Hocon.Protocols uses Hocon.Types.MarkerClasses.Akka.Remote.WorkerPool, so a change to Hocon.Types.MarkerClasses.Akka.Remote.WorkerPool can break Hocon.Protocols, while a change to Hocon.Protocols can't break Hocon.Types.MarkerClasses.Akka.Remote.WorkerPool.
- Position
- Below the diagonal: Hocon.Protocols uses a module listed above it, which is the healthy direction.
24→3 Hocon.Streams uses Hocon.InternalHocon✕
- Connections
- 4 pairs of types, where a type in Hocon.Streams uses a type in Hocon.InternalHocon.
- The types involved
Akkling.Hocon.Streams.MaterializerBuilder`1→Akkling.Hocon.InternalHocon.BaseBuilder`1Akkling.Hocon.Streams.StreamBuilder`1→Akkling.Hocon.InternalHocon.BaseBuilder`1Akkling.Hocon.Streams.StreamRefBuilder`1→Akkling.Hocon.InternalHocon.BaseBuilder`1Akkling.Hocon.Streams.SubscriptionTimeoutBuilder`1→Akkling.Hocon.InternalHocon.BaseBuilder`1
- Direction
- Hocon.Streams uses Hocon.InternalHocon, so a change to Hocon.InternalHocon can break Hocon.Streams, while a change to Hocon.Streams can't break Hocon.InternalHocon.
- Position
- Below the diagonal: Hocon.Streams uses a module listed above it, which is the healthy direction.
24→10 Hocon.Streams uses Hocon.Types.MarkerClasses.Akka✕
- Connections
- 2 pairs of types, where a type in Hocon.Streams uses a type in Hocon.Types.MarkerClasses.Akka.
- The types involved
Akkling.Hocon.Streams.StreamBuilder`1→Akkling.Hocon.Types.MarkerClasses.Akka.FieldAkkling.Hocon.Streams.Streams→Akkling.Hocon.Types.MarkerClasses.Akka.Field
- Direction
- Hocon.Streams uses Hocon.Types.MarkerClasses.Akka, so a change to Hocon.Types.MarkerClasses.Akka can break Hocon.Streams, while a change to Hocon.Streams can't break Hocon.Types.MarkerClasses.Akka.
- Position
- Below the diagonal: Hocon.Streams uses a module listed above it, which is the healthy direction.
25→1 Persistence uses ActorRefs✕
- Connections
- 1 pair of types, where a type in Persistence uses a type in ActorRefs.
- The types involved
Akkling.Persistence.TypedPersistentContext`2→Akkling.ActorRefs.IActorRef`1
- Direction
- Persistence uses ActorRefs, so a change to ActorRefs can break Persistence, while a change to Persistence can't break ActorRefs.
- Position
- Below the diagonal: Persistence uses a module listed above it, which is the healthy direction.
25→7 Persistence uses Actors✕
- Connections
- 8 pairs of types, where a type in Persistence uses a type in Actors.
- The types involved
Akkling.Persistence.Eventsourced`1→Akkling.Actors.Actor`1Akkling.Persistence.ExtEventsourced`1→Akkling.Actors.ExtActor`1Akkling.Persistence.FunPersistentActor`1→Akkling.Actors.Effect`1Akkling.Persistence.PersistentEffect`1→Akkling.Actors.Effect`1Akkling.Persistence.PersistentEffect`1→Akkling.Actors.ExtActor`1Akkling.Persistence.PersistentLifecycleEvent→Akkling.Actors.UnhandledSuppressionAkkling.Persistence.TypedPersistentContext`2→Akkling.Actors.Effect`1Akkling.Persistence.TypedPersistentContext`2→Akkling.Actors.IO`1
- Direction
- Persistence uses Actors, so a change to Actors can break Persistence, while a change to Persistence can't break Actors.
- Position
- Below the diagonal: Persistence uses a module listed above it, which is the healthy direction.
26→1 Cluster.Sharding.ClusterSharding uses ActorRefs✕
- Connections
- 1 pair of types, where a type in Cluster.Sharding.ClusterSharding uses a type in ActorRefs.
- The types involved
Akkling.Cluster.Sharding.ClusterSharding.ClusterSharding→Akkling.ActorRefs.IActorRef`1
- Direction
- Cluster.Sharding.ClusterSharding uses ActorRefs, so a change to ActorRefs can break Cluster.Sharding.ClusterSharding, while a change to Cluster.Sharding.ClusterSharding can't break ActorRefs.
- Position
- Below the diagonal: Cluster.Sharding.ClusterSharding uses a module listed above it, which is the healthy direction.
26→6 Cluster.Sharding.ClusterSharding uses Props✕
- Connections
- 1 pair of types, where a type in Cluster.Sharding.ClusterSharding uses a type in Props.
- The types involved
Akkling.Cluster.Sharding.ClusterSharding.ClusterSharding→Akkling.Props.Props`1
- Direction
- Cluster.Sharding.ClusterSharding uses Props, so a change to Props can break Cluster.Sharding.ClusterSharding, while a change to Cluster.Sharding.ClusterSharding can't break Props.
- Position
- Below the diagonal: Cluster.Sharding.ClusterSharding uses a module listed above it, which is the healthy direction.
26→7 Cluster.Sharding.ClusterSharding uses Actors✕
- Connections
- 3 pairs of types, where a type in Cluster.Sharding.ClusterSharding uses a type in Actors.
- The types involved
Akkling.Cluster.Sharding.ClusterSharding.ClusterSharding→Akkling.Actors.Effect`1Akkling.Cluster.Sharding.ClusterSharding.ClusterShardingEffect`1→Akkling.Actors.Effect`1Akkling.Cluster.Sharding.ClusterSharding.ClusterShardingEffect`1→Akkling.Actors.ExtActor`1
- Direction
- Cluster.Sharding.ClusterSharding uses Actors, so a change to Actors can break Cluster.Sharding.ClusterSharding, while a change to Cluster.Sharding.ClusterSharding can't break Actors.
- Position
- Below the diagonal: Cluster.Sharding.ClusterSharding uses a module listed above it, which is the healthy direction.
26→25 Cluster.Sharding.ClusterSharding uses Persistence✕
- Connections
- 1 pair of types, where a type in Cluster.Sharding.ClusterSharding uses a type in Persistence.
- The types involved
Akkling.Cluster.Sharding.ClusterSharding.FunPersistentShardingActor`1→Akkling.Persistence.FunPersistentActor`1
- Direction
- Cluster.Sharding.ClusterSharding uses Persistence, so a change to Persistence can break Cluster.Sharding.ClusterSharding, while a change to Cluster.Sharding.ClusterSharding can't break Persistence.
- Position
- Below the diagonal: Cluster.Sharding.ClusterSharding uses a module listed above it, which is the healthy direction.
27→4 Hocon.Cluster uses Hocon.SharedInternal✕
- Connections
- 1 pair of types, where a type in Hocon.Cluster uses a type in Hocon.SharedInternal.
- The types involved
Akkling.Hocon.Cluster.ClusterBuilder`1→Akkling.Hocon.SharedInternal.State`1
- Direction
- Hocon.Cluster uses Hocon.SharedInternal, so a change to Hocon.SharedInternal can break Hocon.Cluster, while a change to Hocon.Cluster can't break Hocon.SharedInternal.
- Position
- Below the diagonal: Hocon.Cluster uses a module listed above it, which is the healthy direction.
27→8 Hocon.Cluster uses Hocon.Debug✕
- Connections
- 1 pair of types, where a type in Hocon.Cluster uses a type in Hocon.Debug.
- The types involved
Akkling.Hocon.Cluster.ClusterBuilder`1→Akkling.Hocon.Debug.DebugBuilder`1
- Direction
- Hocon.Cluster uses Hocon.Debug, so a change to Hocon.Debug can break Hocon.Cluster, while a change to Hocon.Cluster can't break Hocon.Debug.
- Position
- Below the diagonal: Hocon.Cluster uses a module listed above it, which is the healthy direction.
27→13 Hocon.Cluster uses Hocon.Types.MarkerClasses.Akka.Cluster✕
- Connections
- 1 pair of types, where a type in Hocon.Cluster uses a type in Hocon.Types.MarkerClasses.Akka.Cluster.
- The types involved
Akkling.Hocon.Cluster.ClusterBuilder`1→Akkling.Hocon.Types.MarkerClasses.Akka.Cluster.Field
- Direction
- Hocon.Cluster uses Hocon.Types.MarkerClasses.Akka.Cluster, so a change to Hocon.Types.MarkerClasses.Akka.Cluster can break Hocon.Cluster, while a change to Hocon.Cluster can't break Hocon.Types.MarkerClasses.Akka.Cluster.
- Position
- Below the diagonal: Hocon.Cluster uses a module listed above it, which is the healthy direction.
27→21 Hocon.Cluster uses Hocon.Metrics✕
- Connections
- 1 pair of types, where a type in Hocon.Cluster uses a type in Hocon.Metrics.
- The types involved
Akkling.Hocon.Cluster.ClusterBuilder`1→Akkling.Hocon.Metrics.MetricsBuilder`1
- Direction
- Hocon.Cluster uses Hocon.Metrics, so a change to Hocon.Metrics can break Hocon.Cluster, while a change to Hocon.Cluster can't break Hocon.Metrics.
- Position
- Below the diagonal: Hocon.Cluster uses a module listed above it, which is the healthy direction.
28→4 Hocon.Proxy uses Hocon.SharedInternal✕
- Connections
- 1 pair of types, where a type in Hocon.Proxy uses a type in Hocon.SharedInternal.
- The types involved
Akkling.Hocon.Proxy.ProxyBuilder`1→Akkling.Hocon.SharedInternal.State`1
- Direction
- Hocon.Proxy uses Hocon.SharedInternal, so a change to Hocon.SharedInternal can break Hocon.Proxy, while a change to Hocon.Proxy can't break Hocon.SharedInternal.
- Position
- Below the diagonal: Hocon.Proxy uses a module listed above it, which is the healthy direction.
28→15 Hocon.Proxy uses Hocon.Types.MarkerClasses.Akka.Persistence.Plugin✕
- Connections
- 1 pair of types, where a type in Hocon.Proxy uses a type in Hocon.Types.MarkerClasses.Akka.Persistence.Plugin.
- The types involved
Akkling.Hocon.Proxy.Proxy→Akkling.Hocon.Types.MarkerClasses.Akka.Persistence.Plugin.Field
- Direction
- Hocon.Proxy uses Hocon.Types.MarkerClasses.Akka.Persistence.Plugin, so a change to Hocon.Types.MarkerClasses.Akka.Persistence.Plugin can break Hocon.Proxy, while a change to Hocon.Proxy can't break Hocon.Types.MarkerClasses.Akka.Persistence.Plugin.
- Position
- Below the diagonal: Hocon.Proxy uses a module listed above it, which is the healthy direction.
28→22 Hocon.Proxy uses Hocon.Plugin✕
- Connections
- 1 pair of types, where a type in Hocon.Proxy uses a type in Hocon.Plugin.
- The types involved
Akkling.Hocon.Proxy.ProxyBuilder`1→Akkling.Hocon.Plugin.PluginBuilder`1
- Direction
- Hocon.Proxy uses Hocon.Plugin, so a change to Hocon.Plugin can break Hocon.Proxy, while a change to Hocon.Proxy can't break Hocon.Plugin.
- Position
- Below the diagonal: Hocon.Proxy uses a module listed above it, which is the healthy direction.
29→2 Hocon.Tcp uses Hocon.Hocon✕
- Connections
- 3 pairs of types, where a type in Hocon.Tcp uses a type in Hocon.Hocon.
- The types involved
Akkling.Hocon.Tcp.TcpBuilder`1→Akkling.Hocon.Hocon.ByteOrderAkkling.Hocon.Tcp.TcpBuilder`1→Akkling.Hocon.Hocon.OffForWindowsAkkling.Hocon.Tcp.TcpBuilder`1→Akkling.Hocon.Hocon.Unlimited
- Direction
- Hocon.Tcp uses Hocon.Hocon, so a change to Hocon.Hocon can break Hocon.Tcp, while a change to Hocon.Tcp can't break Hocon.Hocon.
- Position
- Below the diagonal: Hocon.Tcp uses a module listed above it, which is the healthy direction.
29→4 Hocon.Tcp uses Hocon.SharedInternal✕
- Connections
- 1 pair of types, where a type in Hocon.Tcp uses a type in Hocon.SharedInternal.
- The types involved
Akkling.Hocon.Tcp.TcpBuilder`1→Akkling.Hocon.SharedInternal.State`1
- Direction
- Hocon.Tcp uses Hocon.SharedInternal, so a change to Hocon.SharedInternal can break Hocon.Tcp, while a change to Hocon.Tcp can't break Hocon.SharedInternal.
- Position
- Below the diagonal: Hocon.Tcp uses a module listed above it, which is the healthy direction.
29→9 Hocon.Tcp uses Hocon.Pools✕
- Connections
- 2 pairs of types, where a type in Hocon.Tcp uses a type in Hocon.Pools.
- The types involved
Akkling.Hocon.Tcp.TcpBuilder`1→Akkling.Hocon.Pools.DirectBufferPoolBuilder`1Akkling.Hocon.Tcp.TcpBuilder`1→Akkling.Hocon.Pools.DisabledBufferPoolBuilder`1
- Direction
- Hocon.Tcp uses Hocon.Pools, so a change to Hocon.Pools can break Hocon.Tcp, while a change to Hocon.Tcp can't break Hocon.Pools.
- Position
- Below the diagonal: Hocon.Tcp uses a module listed above it, which is the healthy direction.
29→17 Hocon.Tcp uses Hocon.Types.MarkerClasses.Akka.Remote.Batching✕
- Connections
- 1 pair of types, where a type in Hocon.Tcp uses a type in Hocon.Types.MarkerClasses.Akka.Remote.Batching.
- The types involved
Akkling.Hocon.Tcp.TcpBuilder`1→Akkling.Hocon.Types.MarkerClasses.Akka.Remote.Batching.Field
- Direction
- Hocon.Tcp uses Hocon.Types.MarkerClasses.Akka.Remote.Batching, so a change to Hocon.Types.MarkerClasses.Akka.Remote.Batching can break Hocon.Tcp, while a change to Hocon.Tcp can't break Hocon.Types.MarkerClasses.Akka.Remote.Batching.
- Position
- Below the diagonal: Hocon.Tcp uses a module listed above it, which is the healthy direction.
29→18 Hocon.Tcp uses Hocon.Types.MarkerClasses.Akka.Remote.WorkerPool✕
- Connections
- 1 pair of types, where a type in Hocon.Tcp uses a type in Hocon.Types.MarkerClasses.Akka.Remote.WorkerPool.
- The types involved
Akkling.Hocon.Tcp.TcpBuilder`1→Akkling.Hocon.Types.MarkerClasses.Akka.Remote.WorkerPool.Field
- Direction
- Hocon.Tcp uses Hocon.Types.MarkerClasses.Akka.Remote.WorkerPool, so a change to Hocon.Types.MarkerClasses.Akka.Remote.WorkerPool can break Hocon.Tcp, while a change to Hocon.Tcp can't break Hocon.Types.MarkerClasses.Akka.Remote.WorkerPool.
- Position
- Below the diagonal: Hocon.Tcp uses a module listed above it, which is the healthy direction.
29→23 Hocon.Tcp uses Hocon.Protocols✕
- Connections
- 2 pairs of types, where a type in Hocon.Tcp uses a type in Hocon.Protocols.
- The types involved
Akkling.Hocon.Tcp.TcpBuilder`1→Akkling.Hocon.Protocols.BatchingBuilder`1Akkling.Hocon.Tcp.TcpBuilder`1→Akkling.Hocon.Protocols.WorkerPoolBuilder`1
- Direction
- Hocon.Tcp uses Hocon.Protocols, so a change to Hocon.Protocols can break Hocon.Tcp, while a change to Hocon.Tcp can't break Hocon.Protocols.
- Position
- Below the diagonal: Hocon.Tcp uses a module listed above it, which is the healthy direction.
30→2 Hocon.Udp uses Hocon.Hocon✕
- Connections
- 3 pairs of types, where a type in Hocon.Udp uses a type in Hocon.Hocon.
- The types involved
Akkling.Hocon.Udp.UdpBuilder`1→Akkling.Hocon.Hocon.ByteOrderAkkling.Hocon.Udp.UdpBuilder`1→Akkling.Hocon.Hocon.InfiniteAkkling.Hocon.Udp.UdpBuilder`1→Akkling.Hocon.Hocon.Unlimited
- Direction
- Hocon.Udp uses Hocon.Hocon, so a change to Hocon.Hocon can break Hocon.Udp, while a change to Hocon.Udp can't break Hocon.Hocon.
- Position
- Below the diagonal: Hocon.Udp uses a module listed above it, which is the healthy direction.
30→4 Hocon.Udp uses Hocon.SharedInternal✕
- Connections
- 1 pair of types, where a type in Hocon.Udp uses a type in Hocon.SharedInternal.
- The types involved
Akkling.Hocon.Udp.UdpBuilder`1→Akkling.Hocon.SharedInternal.State`1
- Direction
- Hocon.Udp uses Hocon.SharedInternal, so a change to Hocon.SharedInternal can break Hocon.Udp, while a change to Hocon.Udp can't break Hocon.SharedInternal.
- Position
- Below the diagonal: Hocon.Udp uses a module listed above it, which is the healthy direction.
30→9 Hocon.Udp uses Hocon.Pools✕
- Connections
- 1 pair of types, where a type in Hocon.Udp uses a type in Hocon.Pools.
- The types involved
Akkling.Hocon.Udp.UdpBuilder`1→Akkling.Hocon.Pools.DirectBufferPoolBuilder`1
- Direction
- Hocon.Udp uses Hocon.Pools, so a change to Hocon.Pools can break Hocon.Udp, while a change to Hocon.Udp can't break Hocon.Pools.
- Position
- Below the diagonal: Hocon.Udp uses a module listed above it, which is the healthy direction.
30→17 Hocon.Udp uses Hocon.Types.MarkerClasses.Akka.Remote.Batching✕
- Connections
- 1 pair of types, where a type in Hocon.Udp uses a type in Hocon.Types.MarkerClasses.Akka.Remote.Batching.
- The types involved
Akkling.Hocon.Udp.UdpBuilder`1→Akkling.Hocon.Types.MarkerClasses.Akka.Remote.Batching.Field
- Direction
- Hocon.Udp uses Hocon.Types.MarkerClasses.Akka.Remote.Batching, so a change to Hocon.Types.MarkerClasses.Akka.Remote.Batching can break Hocon.Udp, while a change to Hocon.Udp can't break Hocon.Types.MarkerClasses.Akka.Remote.Batching.
- Position
- Below the diagonal: Hocon.Udp uses a module listed above it, which is the healthy direction.
30→18 Hocon.Udp uses Hocon.Types.MarkerClasses.Akka.Remote.WorkerPool✕
- Connections
- 1 pair of types, where a type in Hocon.Udp uses a type in Hocon.Types.MarkerClasses.Akka.Remote.WorkerPool.
- The types involved
Akkling.Hocon.Udp.UdpBuilder`1→Akkling.Hocon.Types.MarkerClasses.Akka.Remote.WorkerPool.Field
- Direction
- Hocon.Udp uses Hocon.Types.MarkerClasses.Akka.Remote.WorkerPool, so a change to Hocon.Types.MarkerClasses.Akka.Remote.WorkerPool can break Hocon.Udp, while a change to Hocon.Udp can't break Hocon.Types.MarkerClasses.Akka.Remote.WorkerPool.
- Position
- Below the diagonal: Hocon.Udp uses a module listed above it, which is the healthy direction.
30→23 Hocon.Udp uses Hocon.Protocols✕
- Connections
- 1 pair of types, where a type in Hocon.Udp uses a type in Hocon.Protocols.
- The types involved
Akkling.Hocon.Udp.UdpBuilder`1→Akkling.Hocon.Protocols.WorkerPoolBuilder`1
- Direction
- Hocon.Udp uses Hocon.Protocols, so a change to Hocon.Protocols can break Hocon.Udp, while a change to Hocon.Udp can't break Hocon.Protocols.
- Position
- Below the diagonal: Hocon.Udp uses a module listed above it, which is the healthy direction.
31→2 Hocon.Deployment uses Hocon.Hocon✕
- Connections
- 1 pair of types, where a type in Hocon.Deployment uses a type in Hocon.Hocon.
- The types involved
Akkling.Hocon.Deployment.DeployeeBuilder`1→Akkling.Hocon.Hocon.MetricSelection
- Direction
- Hocon.Deployment uses Hocon.Hocon, so a change to Hocon.Hocon can break Hocon.Deployment, while a change to Hocon.Deployment can't break Hocon.Hocon.
- Position
- Below the diagonal: Hocon.Deployment uses a module listed above it, which is the healthy direction.
31→3 Hocon.Deployment uses Hocon.InternalHocon✕
- Connections
- 4 pairs of types, where a type in Hocon.Deployment uses a type in Hocon.InternalHocon.
- The types involved
Akkling.Hocon.Deployment.DeployeeBuilder`1→Akkling.Hocon.InternalHocon.BaseBuilder`1Akkling.Hocon.Deployment.DeploymentBuilder`1→Akkling.Hocon.InternalHocon.BaseBuilder`1Akkling.Hocon.Deployment.ResizerBuilder`1→Akkling.Hocon.InternalHocon.BaseBuilder`1Akkling.Hocon.Deployment.RouteesBuilder`1→Akkling.Hocon.InternalHocon.BaseBuilder`1
- Direction
- Hocon.Deployment uses Hocon.InternalHocon, so a change to Hocon.InternalHocon can break Hocon.Deployment, while a change to Hocon.Deployment can't break Hocon.InternalHocon.
- Position
- Below the diagonal: Hocon.Deployment uses a module listed above it, which is the healthy direction.
31→11 Hocon.Deployment uses Hocon.Types.MarkerClasses.Akka.Actor✕
- Connections
- 1 pair of types, where a type in Hocon.Deployment uses a type in Hocon.Types.MarkerClasses.Akka.Actor.
- The types involved
Akkling.Hocon.Deployment.Deployment→Akkling.Hocon.Types.MarkerClasses.Akka.Actor.Field
- Direction
- Hocon.Deployment uses Hocon.Types.MarkerClasses.Akka.Actor, so a change to Hocon.Types.MarkerClasses.Akka.Actor can break Hocon.Deployment, while a change to Hocon.Deployment can't break Hocon.Types.MarkerClasses.Akka.Actor.
- Position
- Below the diagonal: Hocon.Deployment uses a module listed above it, which is the healthy direction.
31→27 Hocon.Deployment uses Hocon.Cluster✕
- Connections
- 1 pair of types, where a type in Hocon.Deployment uses a type in Hocon.Cluster.
- The types involved
Akkling.Hocon.Deployment.DeployeeBuilder`1→Akkling.Hocon.Cluster.ClusterBuilder`1
- Direction
- Hocon.Deployment uses Hocon.Cluster, so a change to Hocon.Cluster can break Hocon.Deployment, while a change to Hocon.Deployment can't break Hocon.Cluster.
- Position
- Below the diagonal: Hocon.Deployment uses a module listed above it, which is the healthy direction.
32→2 Hocon.DotNetty uses Hocon.Hocon✕
- Connections
- 1 pair of types, where a type in Hocon.DotNetty uses a type in Hocon.Hocon.
- The types involved
Akkling.Hocon.DotNetty.SslProtocolBuilder`1→Akkling.Hocon.Hocon.ByteOrder
- Direction
- Hocon.DotNetty uses Hocon.Hocon, so a change to Hocon.Hocon can break Hocon.DotNetty, while a change to Hocon.DotNetty can't break Hocon.Hocon.
- Position
- Below the diagonal: Hocon.DotNetty uses a module listed above it, which is the healthy direction.
32→3 Hocon.DotNetty uses Hocon.InternalHocon✕
- Connections
- 3 pairs of types, where a type in Hocon.DotNetty uses a type in Hocon.InternalHocon.
- The types involved
Akkling.Hocon.DotNetty.CertificateBuilder`1→Akkling.Hocon.InternalHocon.BaseBuilder`1Akkling.Hocon.DotNetty.DotNettyBuilder`1→Akkling.Hocon.InternalHocon.BaseBuilder`1Akkling.Hocon.DotNetty.SslProtocolBuilder`1→Akkling.Hocon.InternalHocon.BaseBuilder`1
- Direction
- Hocon.DotNetty uses Hocon.InternalHocon, so a change to Hocon.InternalHocon can break Hocon.DotNetty, while a change to Hocon.DotNetty can't break Hocon.InternalHocon.
- Position
- Below the diagonal: Hocon.DotNetty uses a module listed above it, which is the healthy direction.
32→16 Hocon.DotNetty uses Hocon.Types.MarkerClasses.Akka.Remote✕
- Connections
- 1 pair of types, where a type in Hocon.DotNetty uses a type in Hocon.Types.MarkerClasses.Akka.Remote.
- The types involved
Akkling.Hocon.DotNetty.DotNetty→Akkling.Hocon.Types.MarkerClasses.Akka.Remote.Field
- Direction
- Hocon.DotNetty uses Hocon.Types.MarkerClasses.Akka.Remote, so a change to Hocon.Types.MarkerClasses.Akka.Remote can break Hocon.DotNetty, while a change to Hocon.DotNetty can't break Hocon.Types.MarkerClasses.Akka.Remote.
- Position
- Below the diagonal: Hocon.DotNetty uses a module listed above it, which is the healthy direction.
32→17 Hocon.DotNetty uses Hocon.Types.MarkerClasses.Akka.Remote.Batching✕
- Connections
- 1 pair of types, where a type in Hocon.DotNetty uses a type in Hocon.Types.MarkerClasses.Akka.Remote.Batching.
- The types involved
Akkling.Hocon.DotNetty.SslProtocolBuilder`1→Akkling.Hocon.Types.MarkerClasses.Akka.Remote.Batching.Field
- Direction
- Hocon.DotNetty uses Hocon.Types.MarkerClasses.Akka.Remote.Batching, so a change to Hocon.Types.MarkerClasses.Akka.Remote.Batching can break Hocon.DotNetty, while a change to Hocon.DotNetty can't break Hocon.Types.MarkerClasses.Akka.Remote.Batching.
- Position
- Below the diagonal: Hocon.DotNetty uses a module listed above it, which is the healthy direction.
32→18 Hocon.DotNetty uses Hocon.Types.MarkerClasses.Akka.Remote.WorkerPool✕
- Connections
- 1 pair of types, where a type in Hocon.DotNetty uses a type in Hocon.Types.MarkerClasses.Akka.Remote.WorkerPool.
- The types involved
Akkling.Hocon.DotNetty.SslProtocolBuilder`1→Akkling.Hocon.Types.MarkerClasses.Akka.Remote.WorkerPool.Field
- Direction
- Hocon.DotNetty uses Hocon.Types.MarkerClasses.Akka.Remote.WorkerPool, so a change to Hocon.Types.MarkerClasses.Akka.Remote.WorkerPool can break Hocon.DotNetty, while a change to Hocon.DotNetty can't break Hocon.Types.MarkerClasses.Akka.Remote.WorkerPool.
- Position
- Below the diagonal: Hocon.DotNetty uses a module listed above it, which is the healthy direction.
32→23 Hocon.DotNetty uses Hocon.Protocols✕
- Connections
- 1 pair of types, where a type in Hocon.DotNetty uses a type in Hocon.Protocols.
- The types involved
Akkling.Hocon.DotNetty.SslProtocolBuilder`1→Akkling.Hocon.Protocols.WorkerPoolBuilder`1
- Direction
- Hocon.DotNetty uses Hocon.Protocols, so a change to Hocon.Protocols can break Hocon.DotNetty, while a change to Hocon.DotNetty can't break Hocon.Protocols.
- Position
- Below the diagonal: Hocon.DotNetty uses a module listed above it, which is the healthy direction.
32→29 Hocon.DotNetty uses Hocon.Tcp✕
- Connections
- 1 pair of types, where a type in Hocon.DotNetty uses a type in Hocon.Tcp.
- The types involved
Akkling.Hocon.DotNetty.DotNettyBuilder`1→Akkling.Hocon.Tcp.TcpBuilder`1
- Direction
- Hocon.DotNetty uses Hocon.Tcp, so a change to Hocon.Tcp can break Hocon.DotNetty, while a change to Hocon.DotNetty can't break Hocon.Tcp.
- Position
- Below the diagonal: Hocon.DotNetty uses a module listed above it, which is the healthy direction.
32→30 Hocon.DotNetty uses Hocon.Udp✕
- Connections
- 1 pair of types, where a type in Hocon.DotNetty uses a type in Hocon.Udp.
- The types involved
Akkling.Hocon.DotNetty.DotNettyBuilder`1→Akkling.Hocon.Udp.UdpBuilder`1
- Direction
- Hocon.DotNetty uses Hocon.Udp, so a change to Hocon.Udp can break Hocon.DotNetty, while a change to Hocon.DotNetty can't break Hocon.Udp.
- Position
- Below the diagonal: Hocon.DotNetty uses a module listed above it, which is the healthy direction.
33→3 Hocon.IO uses Hocon.InternalHocon✕
- Connections
- 1 pair of types, where a type in Hocon.IO uses a type in Hocon.InternalHocon.
- The types involved
Akkling.Hocon.IO.IOBuilder`1→Akkling.Hocon.InternalHocon.BaseBuilder`1
- Direction
- Hocon.IO uses Hocon.InternalHocon, so a change to Hocon.InternalHocon can break Hocon.IO, while a change to Hocon.IO can't break Hocon.InternalHocon.
- Position
- Below the diagonal: Hocon.IO uses a module listed above it, which is the healthy direction.
33→10 Hocon.IO uses Hocon.Types.MarkerClasses.Akka✕
- Connections
- 2 pairs of types, where a type in Hocon.IO uses a type in Hocon.Types.MarkerClasses.Akka.
- The types involved
Akkling.Hocon.IO.IO→Akkling.Hocon.Types.MarkerClasses.Akka.FieldAkkling.Hocon.IO.IOBuilder`1→Akkling.Hocon.Types.MarkerClasses.Akka.Field
- Direction
- Hocon.IO uses Hocon.Types.MarkerClasses.Akka, so a change to Hocon.Types.MarkerClasses.Akka can break Hocon.IO, while a change to Hocon.IO can't break Hocon.Types.MarkerClasses.Akka.
- Position
- Below the diagonal: Hocon.IO uses a module listed above it, which is the healthy direction.
33→12 Hocon.IO uses Hocon.Types.MarkerClasses.Akka.Actor.Dispatcher✕
- Connections
- 1 pair of types, where a type in Hocon.IO uses a type in Hocon.Types.MarkerClasses.Akka.Actor.Dispatcher.
- The types involved
Akkling.Hocon.IO.IOBuilder`1→Akkling.Hocon.Types.MarkerClasses.Akka.Actor.Dispatcher.Field
- Direction
- Hocon.IO uses Hocon.Types.MarkerClasses.Akka.Actor.Dispatcher, so a change to Hocon.Types.MarkerClasses.Akka.Actor.Dispatcher can break Hocon.IO, while a change to Hocon.IO can't break Hocon.Types.MarkerClasses.Akka.Actor.Dispatcher.
- Position
- Below the diagonal: Hocon.IO uses a module listed above it, which is the healthy direction.
33→29 Hocon.IO uses Hocon.Tcp✕
- Connections
- 1 pair of types, where a type in Hocon.IO uses a type in Hocon.Tcp.
- The types involved
Akkling.Hocon.IO.IOBuilder`1→Akkling.Hocon.Tcp.TcpBuilder`1
- Direction
- Hocon.IO uses Hocon.Tcp, so a change to Hocon.Tcp can break Hocon.IO, while a change to Hocon.IO can't break Hocon.Tcp.
- Position
- Below the diagonal: Hocon.IO uses a module listed above it, which is the healthy direction.
33→30 Hocon.IO uses Hocon.Udp✕
- Connections
- 1 pair of types, where a type in Hocon.IO uses a type in Hocon.Udp.
- The types involved
Akkling.Hocon.IO.IOBuilder`1→Akkling.Hocon.Udp.UdpBuilder`1
- Direction
- Hocon.IO uses Hocon.Udp, so a change to Hocon.Udp can break Hocon.IO, while a change to Hocon.IO can't break Hocon.Udp.
- Position
- Below the diagonal: Hocon.IO uses a module listed above it, which is the healthy direction.
34→3 Hocon.Journal uses Hocon.InternalHocon✕
- Connections
- 1 pair of types, where a type in Hocon.Journal uses a type in Hocon.InternalHocon.
- The types involved
Akkling.Hocon.Journal.JournalBuilder`1→Akkling.Hocon.InternalHocon.BaseBuilder`1
- Direction
- Hocon.Journal uses Hocon.InternalHocon, so a change to Hocon.InternalHocon can break Hocon.Journal, while a change to Hocon.Journal can't break Hocon.InternalHocon.
- Position
- Below the diagonal: Hocon.Journal uses a module listed above it, which is the healthy direction.
34→14 Hocon.Journal uses Hocon.Types.MarkerClasses.Akka.Persistence✕
- Connections
- 1 pair of types, where a type in Hocon.Journal uses a type in Hocon.Types.MarkerClasses.Akka.Persistence.
- The types involved
Akkling.Hocon.Journal.Journal→Akkling.Hocon.Types.MarkerClasses.Akka.Persistence.Field
- Direction
- Hocon.Journal uses Hocon.Types.MarkerClasses.Akka.Persistence, so a change to Hocon.Types.MarkerClasses.Akka.Persistence can break Hocon.Journal, while a change to Hocon.Journal can't break Hocon.Types.MarkerClasses.Akka.Persistence.
- Position
- Below the diagonal: Hocon.Journal uses a module listed above it, which is the healthy direction.
34→15 Hocon.Journal uses Hocon.Types.MarkerClasses.Akka.Persistence.Plugin✕
- Connections
- 1 pair of types, where a type in Hocon.Journal uses a type in Hocon.Types.MarkerClasses.Akka.Persistence.Plugin.
- The types involved
Akkling.Hocon.Journal.JournalBuilder`1→Akkling.Hocon.Types.MarkerClasses.Akka.Persistence.Plugin.Field
- Direction
- Hocon.Journal uses Hocon.Types.MarkerClasses.Akka.Persistence.Plugin, so a change to Hocon.Types.MarkerClasses.Akka.Persistence.Plugin can break Hocon.Journal, while a change to Hocon.Journal can't break Hocon.Types.MarkerClasses.Akka.Persistence.Plugin.
- Position
- Below the diagonal: Hocon.Journal uses a module listed above it, which is the healthy direction.
34→22 Hocon.Journal uses Hocon.Plugin✕
- Connections
- 1 pair of types, where a type in Hocon.Journal uses a type in Hocon.Plugin.
- The types involved
Akkling.Hocon.Journal.JournalBuilder`1→Akkling.Hocon.Plugin.PluginBuilder`1
- Direction
- Hocon.Journal uses Hocon.Plugin, so a change to Hocon.Plugin can break Hocon.Journal, while a change to Hocon.Journal can't break Hocon.Plugin.
- Position
- Below the diagonal: Hocon.Journal uses a module listed above it, which is the healthy direction.
34→28 Hocon.Journal uses Hocon.Proxy✕
- Connections
- 1 pair of types, where a type in Hocon.Journal uses a type in Hocon.Proxy.
- The types involved
Akkling.Hocon.Journal.JournalBuilder`1→Akkling.Hocon.Proxy.ProxyBuilder`1
- Direction
- Hocon.Journal uses Hocon.Proxy, so a change to Hocon.Proxy can break Hocon.Journal, while a change to Hocon.Journal can't break Hocon.Proxy.
- Position
- Below the diagonal: Hocon.Journal uses a module listed above it, which is the healthy direction.
35→3 Hocon.PluginFallback uses Hocon.InternalHocon✕
- Connections
- 1 pair of types, where a type in Hocon.PluginFallback uses a type in Hocon.InternalHocon.
- The types involved
Akkling.Hocon.PluginFallback.PluginFallbackBuilder`1→Akkling.Hocon.InternalHocon.BaseBuilder`1
- Direction
- Hocon.PluginFallback uses Hocon.InternalHocon, so a change to Hocon.InternalHocon can break Hocon.PluginFallback, while a change to Hocon.PluginFallback can't break Hocon.InternalHocon.
- Position
- Below the diagonal: Hocon.PluginFallback uses a module listed above it, which is the healthy direction.
35→14 Hocon.PluginFallback uses Hocon.Types.MarkerClasses.Akka.Persistence✕
- Connections
- 1 pair of types, where a type in Hocon.PluginFallback uses a type in Hocon.Types.MarkerClasses.Akka.Persistence.
- The types involved
Akkling.Hocon.PluginFallback.PluginFallback→Akkling.Hocon.Types.MarkerClasses.Akka.Persistence.Field
- Direction
- Hocon.PluginFallback uses Hocon.Types.MarkerClasses.Akka.Persistence, so a change to Hocon.Types.MarkerClasses.Akka.Persistence can break Hocon.PluginFallback, while a change to Hocon.PluginFallback can't break Hocon.Types.MarkerClasses.Akka.Persistence.
- Position
- Below the diagonal: Hocon.PluginFallback uses a module listed above it, which is the healthy direction.
35→22 Hocon.PluginFallback uses Hocon.Plugin✕
- Connections
- 2 pairs of types, where a type in Hocon.PluginFallback uses a type in Hocon.Plugin.
- The types involved
Akkling.Hocon.PluginFallback.JournalPluginFallbackBuilder`1→Akkling.Hocon.Plugin.ReplayFilterBuilder`1Akkling.Hocon.PluginFallback.PluginFallbackBuilder`1→Akkling.Hocon.Plugin.CircuitBreakerBuilder`1
- Direction
- Hocon.PluginFallback uses Hocon.Plugin, so a change to Hocon.Plugin can break Hocon.PluginFallback, while a change to Hocon.PluginFallback can't break Hocon.Plugin.
- Position
- Below the diagonal: Hocon.PluginFallback uses a module listed above it, which is the healthy direction.
35→28 Hocon.PluginFallback uses Hocon.Proxy✕
- Connections
- 1 pair of types, where a type in Hocon.PluginFallback uses a type in Hocon.Proxy.
- The types involved
Akkling.Hocon.PluginFallback.PluginFallbackBuilder`1→Akkling.Hocon.Proxy.ProxyBuilder`1
- Direction
- Hocon.PluginFallback uses Hocon.Proxy, so a change to Hocon.Proxy can break Hocon.PluginFallback, while a change to Hocon.PluginFallback can't break Hocon.Proxy.
- Position
- Below the diagonal: Hocon.PluginFallback uses a module listed above it, which is the healthy direction.
36→3 Hocon.SnapshotStore uses Hocon.InternalHocon✕
- Connections
- 3 pairs of types, where a type in Hocon.SnapshotStore uses a type in Hocon.InternalHocon.
- The types involved
Akkling.Hocon.SnapshotStore.LocalBuilder`1→Akkling.Hocon.InternalHocon.BaseBuilder`1Akkling.Hocon.SnapshotStore.NoSnapshotStoreBuilder`1→Akkling.Hocon.InternalHocon.BaseBuilder`1Akkling.Hocon.SnapshotStore.SnapshotStoreBuilder`1→Akkling.Hocon.InternalHocon.BaseBuilder`1
- Direction
- Hocon.SnapshotStore uses Hocon.InternalHocon, so a change to Hocon.InternalHocon can break Hocon.SnapshotStore, while a change to Hocon.SnapshotStore can't break Hocon.InternalHocon.
- Position
- Below the diagonal: Hocon.SnapshotStore uses a module listed above it, which is the healthy direction.
36→14 Hocon.SnapshotStore uses Hocon.Types.MarkerClasses.Akka.Persistence✕
- Connections
- 1 pair of types, where a type in Hocon.SnapshotStore uses a type in Hocon.Types.MarkerClasses.Akka.Persistence.
- The types involved
Akkling.Hocon.SnapshotStore.SnapshotStore→Akkling.Hocon.Types.MarkerClasses.Akka.Persistence.Field
- Direction
- Hocon.SnapshotStore uses Hocon.Types.MarkerClasses.Akka.Persistence, so a change to Hocon.Types.MarkerClasses.Akka.Persistence can break Hocon.SnapshotStore, while a change to Hocon.SnapshotStore can't break Hocon.Types.MarkerClasses.Akka.Persistence.
- Position
- Below the diagonal: Hocon.SnapshotStore uses a module listed above it, which is the healthy direction.
36→15 Hocon.SnapshotStore uses Hocon.Types.MarkerClasses.Akka.Persistence.Plugin✕
- Connections
- 1 pair of types, where a type in Hocon.SnapshotStore uses a type in Hocon.Types.MarkerClasses.Akka.Persistence.Plugin.
- The types involved
Akkling.Hocon.SnapshotStore.SnapshotStoreBuilder`1→Akkling.Hocon.Types.MarkerClasses.Akka.Persistence.Plugin.Field
- Direction
- Hocon.SnapshotStore uses Hocon.Types.MarkerClasses.Akka.Persistence.Plugin, so a change to Hocon.Types.MarkerClasses.Akka.Persistence.Plugin can break Hocon.SnapshotStore, while a change to Hocon.SnapshotStore can't break Hocon.Types.MarkerClasses.Akka.Persistence.Plugin.
- Position
- Below the diagonal: Hocon.SnapshotStore uses a module listed above it, which is the healthy direction.
36→22 Hocon.SnapshotStore uses Hocon.Plugin✕
- Connections
- 1 pair of types, where a type in Hocon.SnapshotStore uses a type in Hocon.Plugin.
- The types involved
Akkling.Hocon.SnapshotStore.SnapshotStoreBuilder`1→Akkling.Hocon.Plugin.PluginBuilder`1
- Direction
- Hocon.SnapshotStore uses Hocon.Plugin, so a change to Hocon.Plugin can break Hocon.SnapshotStore, while a change to Hocon.SnapshotStore can't break Hocon.Plugin.
- Position
- Below the diagonal: Hocon.SnapshotStore uses a module listed above it, which is the healthy direction.
36→28 Hocon.SnapshotStore uses Hocon.Proxy✕
- Connections
- 1 pair of types, where a type in Hocon.SnapshotStore uses a type in Hocon.Proxy.
- The types involved
Akkling.Hocon.SnapshotStore.SnapshotStoreBuilder`1→Akkling.Hocon.Proxy.ProxyBuilder`1
- Direction
- Hocon.SnapshotStore uses Hocon.Proxy, so a change to Hocon.Proxy can break Hocon.SnapshotStore, while a change to Hocon.SnapshotStore can't break Hocon.Proxy.
- Position
- Below the diagonal: Hocon.SnapshotStore uses a module listed above it, which is the healthy direction.
37→2 Hocon.Actor uses Hocon.Hocon✕
- Connections
- 1 pair of types, where a type in Hocon.Actor uses a type in Hocon.Hocon.
- The types involved
Akkling.Hocon.Actor.ActorBuilder`1→Akkling.Hocon.Hocon.Infinite
- Direction
- Hocon.Actor uses Hocon.Hocon, so a change to Hocon.Hocon can break Hocon.Actor, while a change to Hocon.Actor can't break Hocon.Hocon.
- Position
- Below the diagonal: Hocon.Actor uses a module listed above it, which is the healthy direction.
37→3 Hocon.Actor uses Hocon.InternalHocon✕
- Connections
- 1 pair of types, where a type in Hocon.Actor uses a type in Hocon.InternalHocon.
- The types involved
Akkling.Hocon.Actor.ActorBuilder`1→Akkling.Hocon.InternalHocon.BaseBuilder`1
- Direction
- Hocon.Actor uses Hocon.InternalHocon, so a change to Hocon.InternalHocon can break Hocon.Actor, while a change to Hocon.Actor can't break Hocon.InternalHocon.
- Position
- Below the diagonal: Hocon.Actor uses a module listed above it, which is the healthy direction.
37→8 Hocon.Actor uses Hocon.Debug✕
- Connections
- 1 pair of types, where a type in Hocon.Actor uses a type in Hocon.Debug.
- The types involved
Akkling.Hocon.Actor.ActorBuilder`1→Akkling.Hocon.Debug.DebugBuilder`1
- Direction
- Hocon.Actor uses Hocon.Debug, so a change to Hocon.Debug can break Hocon.Actor, while a change to Hocon.Actor can't break Hocon.Debug.
- Position
- Below the diagonal: Hocon.Actor uses a module listed above it, which is the healthy direction.
37→10 Hocon.Actor uses Hocon.Types.MarkerClasses.Akka✕
- Connections
- 2 pairs of types, where a type in Hocon.Actor uses a type in Hocon.Types.MarkerClasses.Akka.
- The types involved
Akkling.Hocon.Actor.Actor→Akkling.Hocon.Types.MarkerClasses.Akka.FieldAkkling.Hocon.Actor.ActorBuilder`1→Akkling.Hocon.Types.MarkerClasses.Akka.Field
- Direction
- Hocon.Actor uses Hocon.Types.MarkerClasses.Akka, so a change to Hocon.Types.MarkerClasses.Akka can break Hocon.Actor, while a change to Hocon.Actor can't break Hocon.Types.MarkerClasses.Akka.
- Position
- Below the diagonal: Hocon.Actor uses a module listed above it, which is the healthy direction.
37→11 Hocon.Actor uses Hocon.Types.MarkerClasses.Akka.Actor✕
- Connections
- 1 pair of types, where a type in Hocon.Actor uses a type in Hocon.Types.MarkerClasses.Akka.Actor.
- The types involved
Akkling.Hocon.Actor.ActorBuilder`1→Akkling.Hocon.Types.MarkerClasses.Akka.Actor.Field
- Direction
- Hocon.Actor uses Hocon.Types.MarkerClasses.Akka.Actor, so a change to Hocon.Types.MarkerClasses.Akka.Actor can break Hocon.Actor, while a change to Hocon.Actor can't break Hocon.Types.MarkerClasses.Akka.Actor.
- Position
- Below the diagonal: Hocon.Actor uses a module listed above it, which is the healthy direction.
37→12 Hocon.Actor uses Hocon.Types.MarkerClasses.Akka.Actor.Dispatcher✕
- Connections
- 1 pair of types, where a type in Hocon.Actor uses a type in Hocon.Types.MarkerClasses.Akka.Actor.Dispatcher.
- The types involved
Akkling.Hocon.Actor.ActorBuilder`1→Akkling.Hocon.Types.MarkerClasses.Akka.Actor.Dispatcher.Field
- Direction
- Hocon.Actor uses Hocon.Types.MarkerClasses.Akka.Actor.Dispatcher, so a change to Hocon.Types.MarkerClasses.Akka.Actor.Dispatcher can break Hocon.Actor, while a change to Hocon.Actor can't break Hocon.Types.MarkerClasses.Akka.Actor.Dispatcher.
- Position
- Below the diagonal: Hocon.Actor uses a module listed above it, which is the healthy direction.
37→20 Hocon.Actor uses Hocon.Dispatcher✕
- Connections
- 1 pair of types, where a type in Hocon.Actor uses a type in Hocon.Dispatcher.
- The types involved
Akkling.Hocon.Actor.ActorBuilder`1→Akkling.Hocon.Dispatcher.DispatcherBuilder`1
- Direction
- Hocon.Actor uses Hocon.Dispatcher, so a change to Hocon.Dispatcher can break Hocon.Actor, while a change to Hocon.Actor can't break Hocon.Dispatcher.
- Position
- Below the diagonal: Hocon.Actor uses a module listed above it, which is the healthy direction.
37→31 Hocon.Actor uses Hocon.Deployment✕
- Connections
- 1 pair of types, where a type in Hocon.Actor uses a type in Hocon.Deployment.
- The types involved
Akkling.Hocon.Actor.ActorBuilder`1→Akkling.Hocon.Deployment.DeploymentBuilder`1
- Direction
- Hocon.Actor uses Hocon.Deployment, so a change to Hocon.Deployment can break Hocon.Actor, while a change to Hocon.Actor can't break Hocon.Deployment.
- Position
- Below the diagonal: Hocon.Actor uses a module listed above it, which is the healthy direction.
38→3 Hocon.Persistence uses Hocon.InternalHocon✕
- Connections
- 1 pair of types, where a type in Hocon.Persistence uses a type in Hocon.InternalHocon.
- The types involved
Akkling.Hocon.Persistence.PersistenceBuilder`1→Akkling.Hocon.InternalHocon.BaseBuilder`1
- Direction
- Hocon.Persistence uses Hocon.InternalHocon, so a change to Hocon.InternalHocon can break Hocon.Persistence, while a change to Hocon.Persistence can't break Hocon.InternalHocon.
- Position
- Below the diagonal: Hocon.Persistence uses a module listed above it, which is the healthy direction.
38→10 Hocon.Persistence uses Hocon.Types.MarkerClasses.Akka✕
- Connections
- 2 pairs of types, where a type in Hocon.Persistence uses a type in Hocon.Types.MarkerClasses.Akka.
- The types involved
Akkling.Hocon.Persistence.Persistence→Akkling.Hocon.Types.MarkerClasses.Akka.FieldAkkling.Hocon.Persistence.PersistenceBuilder`1→Akkling.Hocon.Types.MarkerClasses.Akka.Field
- Direction
- Hocon.Persistence uses Hocon.Types.MarkerClasses.Akka, so a change to Hocon.Types.MarkerClasses.Akka can break Hocon.Persistence, while a change to Hocon.Persistence can't break Hocon.Types.MarkerClasses.Akka.
- Position
- Below the diagonal: Hocon.Persistence uses a module listed above it, which is the healthy direction.
38→12 Hocon.Persistence uses Hocon.Types.MarkerClasses.Akka.Actor.Dispatcher✕
- Connections
- 1 pair of types, where a type in Hocon.Persistence uses a type in Hocon.Types.MarkerClasses.Akka.Actor.Dispatcher.
- The types involved
Akkling.Hocon.Persistence.PersistenceBuilder`1→Akkling.Hocon.Types.MarkerClasses.Akka.Actor.Dispatcher.Field
- Direction
- Hocon.Persistence uses Hocon.Types.MarkerClasses.Akka.Actor.Dispatcher, so a change to Hocon.Types.MarkerClasses.Akka.Actor.Dispatcher can break Hocon.Persistence, while a change to Hocon.Persistence can't break Hocon.Types.MarkerClasses.Akka.Actor.Dispatcher.
- Position
- Below the diagonal: Hocon.Persistence uses a module listed above it, which is the healthy direction.
38→14 Hocon.Persistence uses Hocon.Types.MarkerClasses.Akka.Persistence✕
- Connections
- 1 pair of types, where a type in Hocon.Persistence uses a type in Hocon.Types.MarkerClasses.Akka.Persistence.
- The types involved
Akkling.Hocon.Persistence.PersistenceBuilder`1→Akkling.Hocon.Types.MarkerClasses.Akka.Persistence.Field
- Direction
- Hocon.Persistence uses Hocon.Types.MarkerClasses.Akka.Persistence, so a change to Hocon.Types.MarkerClasses.Akka.Persistence can break Hocon.Persistence, while a change to Hocon.Persistence can't break Hocon.Types.MarkerClasses.Akka.Persistence.
- Position
- Below the diagonal: Hocon.Persistence uses a module listed above it, which is the healthy direction.
38→34 Hocon.Persistence uses Hocon.Journal✕
- Connections
- 1 pair of types, where a type in Hocon.Persistence uses a type in Hocon.Journal.
- The types involved
Akkling.Hocon.Persistence.PersistenceBuilder`1→Akkling.Hocon.Journal.JournalBuilder`1
- Direction
- Hocon.Persistence uses Hocon.Journal, so a change to Hocon.Journal can break Hocon.Persistence, while a change to Hocon.Persistence can't break Hocon.Journal.
- Position
- Below the diagonal: Hocon.Persistence uses a module listed above it, which is the healthy direction.
38→35 Hocon.Persistence uses Hocon.PluginFallback✕
- Connections
- 2 pairs of types, where a type in Hocon.Persistence uses a type in Hocon.PluginFallback.
- The types involved
Akkling.Hocon.Persistence.PersistenceBuilder`1→Akkling.Hocon.PluginFallback.JournalPluginFallbackBuilder`1Akkling.Hocon.Persistence.PersistenceBuilder`1→Akkling.Hocon.PluginFallback.PluginFallbackBuilder`1
- Direction
- Hocon.Persistence uses Hocon.PluginFallback, so a change to Hocon.PluginFallback can break Hocon.Persistence, while a change to Hocon.Persistence can't break Hocon.PluginFallback.
- Position
- Below the diagonal: Hocon.Persistence uses a module listed above it, which is the healthy direction.
38→36 Hocon.Persistence uses Hocon.SnapshotStore✕
- Connections
- 2 pairs of types, where a type in Hocon.Persistence uses a type in Hocon.SnapshotStore.
- The types involved
Akkling.Hocon.Persistence.PersistenceBuilder`1→Akkling.Hocon.SnapshotStore.NoSnapshotStoreBuilder`1Akkling.Hocon.Persistence.PersistenceBuilder`1→Akkling.Hocon.SnapshotStore.SnapshotStoreBuilder`1
- Direction
- Hocon.Persistence uses Hocon.SnapshotStore, so a change to Hocon.SnapshotStore can break Hocon.Persistence, while a change to Hocon.Persistence can't break Hocon.SnapshotStore.
- Position
- Below the diagonal: Hocon.Persistence uses a module listed above it, which is the healthy direction.
39→3 Hocon.Remote uses Hocon.InternalHocon✕
- Connections
- 1 pair of types, where a type in Hocon.Remote uses a type in Hocon.InternalHocon.
- The types involved
Akkling.Hocon.Remote.RemoteBuilder`1→Akkling.Hocon.InternalHocon.BaseBuilder`1
- Direction
- Hocon.Remote uses Hocon.InternalHocon, so a change to Hocon.InternalHocon can break Hocon.Remote, while a change to Hocon.Remote can't break Hocon.InternalHocon.
- Position
- Below the diagonal: Hocon.Remote uses a module listed above it, which is the healthy direction.
39→10 Hocon.Remote uses Hocon.Types.MarkerClasses.Akka✕
- Connections
- 2 pairs of types, where a type in Hocon.Remote uses a type in Hocon.Types.MarkerClasses.Akka.
- The types involved
Akkling.Hocon.Remote.Remote→Akkling.Hocon.Types.MarkerClasses.Akka.FieldAkkling.Hocon.Remote.RemoteBuilder`1→Akkling.Hocon.Types.MarkerClasses.Akka.Field
- Direction
- Hocon.Remote uses Hocon.Types.MarkerClasses.Akka, so a change to Hocon.Types.MarkerClasses.Akka can break Hocon.Remote, while a change to Hocon.Remote can't break Hocon.Types.MarkerClasses.Akka.
- Position
- Below the diagonal: Hocon.Remote uses a module listed above it, which is the healthy direction.
39→12 Hocon.Remote uses Hocon.Types.MarkerClasses.Akka.Actor.Dispatcher✕
- Connections
- 1 pair of types, where a type in Hocon.Remote uses a type in Hocon.Types.MarkerClasses.Akka.Actor.Dispatcher.
- The types involved
Akkling.Hocon.Remote.RemoteBuilder`1→Akkling.Hocon.Types.MarkerClasses.Akka.Actor.Dispatcher.Field
- Direction
- Hocon.Remote uses Hocon.Types.MarkerClasses.Akka.Actor.Dispatcher, so a change to Hocon.Types.MarkerClasses.Akka.Actor.Dispatcher can break Hocon.Remote, while a change to Hocon.Remote can't break Hocon.Types.MarkerClasses.Akka.Actor.Dispatcher.
- Position
- Below the diagonal: Hocon.Remote uses a module listed above it, which is the healthy direction.
39→16 Hocon.Remote uses Hocon.Types.MarkerClasses.Akka.Remote✕
- Connections
- 1 pair of types, where a type in Hocon.Remote uses a type in Hocon.Types.MarkerClasses.Akka.Remote.
- The types involved
Akkling.Hocon.Remote.RemoteBuilder`1→Akkling.Hocon.Types.MarkerClasses.Akka.Remote.Field
- Direction
- Hocon.Remote uses Hocon.Types.MarkerClasses.Akka.Remote, so a change to Hocon.Types.MarkerClasses.Akka.Remote can break Hocon.Remote, while a change to Hocon.Remote can't break Hocon.Types.MarkerClasses.Akka.Remote.
- Position
- Below the diagonal: Hocon.Remote uses a module listed above it, which is the healthy direction.
39→32 Hocon.Remote uses Hocon.DotNetty✕
- Connections
- 1 pair of types, where a type in Hocon.Remote uses a type in Hocon.DotNetty.
- The types involved
Akkling.Hocon.Remote.RemoteBuilder`1→Akkling.Hocon.DotNetty.DotNettyBuilder`1
- Direction
- Hocon.Remote uses Hocon.DotNetty, so a change to Hocon.DotNetty can break Hocon.Remote, while a change to Hocon.Remote can't break Hocon.DotNetty.
- Position
- Below the diagonal: Hocon.Remote uses a module listed above it, which is the healthy direction.
40→3 Hocon.Test uses Hocon.InternalHocon✕
- Connections
- 1 pair of types, where a type in Hocon.Test uses a type in Hocon.InternalHocon.
- The types involved
Akkling.Hocon.Test.TestBuilder`1→Akkling.Hocon.InternalHocon.BaseBuilder`1
- Direction
- Hocon.Test uses Hocon.InternalHocon, so a change to Hocon.InternalHocon can break Hocon.Test, while a change to Hocon.Test can't break Hocon.InternalHocon.
- Position
- Below the diagonal: Hocon.Test uses a module listed above it, which is the healthy direction.
40→10 Hocon.Test uses Hocon.Types.MarkerClasses.Akka✕
- Connections
- 2 pairs of types, where a type in Hocon.Test uses a type in Hocon.Types.MarkerClasses.Akka.
- The types involved
Akkling.Hocon.Test.Test→Akkling.Hocon.Types.MarkerClasses.Akka.FieldAkkling.Hocon.Test.TestBuilder`1→Akkling.Hocon.Types.MarkerClasses.Akka.Field
- Direction
- Hocon.Test uses Hocon.Types.MarkerClasses.Akka, so a change to Hocon.Types.MarkerClasses.Akka can break Hocon.Test, while a change to Hocon.Test can't break Hocon.Types.MarkerClasses.Akka.
- Position
- Below the diagonal: Hocon.Test uses a module listed above it, which is the healthy direction.
40→12 Hocon.Test uses Hocon.Types.MarkerClasses.Akka.Actor.Dispatcher✕
- Connections
- 1 pair of types, where a type in Hocon.Test uses a type in Hocon.Types.MarkerClasses.Akka.Actor.Dispatcher.
- The types involved
Akkling.Hocon.Test.TestBuilder`1→Akkling.Hocon.Types.MarkerClasses.Akka.Actor.Dispatcher.Field
- Direction
- Hocon.Test uses Hocon.Types.MarkerClasses.Akka.Actor.Dispatcher, so a change to Hocon.Types.MarkerClasses.Akka.Actor.Dispatcher can break Hocon.Test, while a change to Hocon.Test can't break Hocon.Types.MarkerClasses.Akka.Actor.Dispatcher.
- Position
- Below the diagonal: Hocon.Test uses a module listed above it, which is the healthy direction.
40→37 Hocon.Test uses Hocon.Actor✕
- Connections
- 2 pairs of types, where a type in Hocon.Test uses a type in Hocon.Actor.
- The types involved
Akkling.Hocon.Test.Test→Akkling.Hocon.Actor.ActorBuilder`1Akkling.Hocon.Test.TestBuilder`1→Akkling.Hocon.Actor.ActorBuilder`1
- Direction
- Hocon.Test uses Hocon.Actor, so a change to Hocon.Actor can break Hocon.Test, while a change to Hocon.Test can't break Hocon.Actor.
- Position
- Below the diagonal: Hocon.Test uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
At a glance — Performance
Roadmap
Top priorities: Resolve the 64 Orphaned file finding(s) in Knowledge Freshness — start with Library.fs (2), TestKit.fs (2), Shared.Tcp.fs; Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them; Add a CI workflow that builds and runs the test suite on every push/PR.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 64 Orphaned file finding(s) in Knowledge Freshness — start with Library.fs (2), TestKit.fs (2), Shared.Tcp.fs. | +11.6 pts | Medium | Knowledge Freshness |
| Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them. | +8.3 pts | Medium | Architecture documentation |
| Add a CI workflow that builds and runs the test suite on every push/PR. | +5.7 pts | Medium | CI/CD gates |
| Add a build/run (quick start) section to the root README — the first thing a newcomer needs. | +2.9 pts | Medium | Documentation (README) |
| Resolve the 3 Most significant orphaned file finding(s) in Knowledge Freshness — start with Source.fs, Flow.fs, Shared.Cluster.fs. | +1.0 pts | Low | Knowledge Freshness |
| Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion. | +0.4 pts | Low | Project Cohesion |
| Resolve the 3 TooManyFunctions finding(s) in God Classes — start with Source.fs, Flow.fs, SubFlow.fs. | +0.3 pts | Low | God Classes |
| Resolve the 1 Dormant codebase finding(s) in Knowledge Freshness. | +0.3 pts | Low | Knowledge Freshness |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| src/Akkling.Hocon/Common.fs | 7.0 | Near-clean | Cyclomatic Complexity: BytesToText.op_AmpDot (cyclomatic 18) |
| src/Akkling.Streams/Flow.fs | 7.1 | Near-clean | God Classes: TooManyFunctions: Flow |
| src/Akkling.Hocon/Cluster.FailureDetector.fs | 7.1 | Near-clean | Code Duplication: Edited copy of a member (126 corresponding lines) |
| src/Akkling.Hocon/Shared.Cluster.fs | 7.2 | Near-clean | God Classes: TooManyMethods: ClusterBuilder`1 |
| src/Akkling.Persistence/PersistentActor.fs | 7.2 | Near-clean | God Classes: TooManyMethods: TypedPersistentContext`2 |
| src/Akkling.Hocon/Actor.Deployment.fs | 7.4 | Near-clean | Code Duplication: Members sharing a duplicated core (10 members, 50+ identical tokens) |
| src/Akkling/Configuration.fs | 7.8 | Near-clean | Cyclomatic Complexity: HoconExtensions.op_Dynamic (cyclomatic 19) |
| src/Akkling.Hocon/Shared.Tcp.fs | 7.8 | Near-clean | God Classes: TooManyMethods: TcpBuilder`1 |
| src/Akkling.Hocon/Persistence.PluginFallback.fs | 7.8 | Near-clean | Code Duplication: Duplicated block (26–34 lines × 2) |
| src/Akkling.Hocon/Persistence.Journal.fs | 7.8 | Near-clean | Code Duplication: Duplicated block (14 lines × 2) |
| src/Akkling/ActorRefs.fs | 7.8 | Near-clean | Code Duplication: Duplicated block (14 lines × 2) |
| src/Akkling.Hocon/Akka.fs | 7.8 | Near-clean | Code Duplication: Duplicated block (13 lines × 2) |
| src/Akkling.Streams/Source.fs | 8.5 | Near-clean | God Classes: TooManyFunctions: Source |
| src/Akkling.Hocon/Shared.Udp.fs | 8.5 | Near-clean | God Classes: TooManyMethods: UdpBuilder`1 |
| src/Akkling.Streams/SubFlow.fs | 8.5 | Near-clean | God Classes: TooManyFunctions: SubFlow |
| src/Akkling.Hocon/Remote.fs | 8.5 | Near-clean | God Classes: TooManyMethods: RemoteBuilder`1 |
| src/Akkling.Hocon/Remote.DotNetty.fs | 8.5 | Near-clean | God Classes: TooManyMethods: SslProtocolBuilder`1 |
| src/Akkling.Hocon/Actor.Router.fs | 8.5 | Near-clean | God Classes: TooManyMethods: TypeMappingBuilder`1 |
| src/Akkling.Hocon/Actor.Serializers.fs | 8.5 | Near-clean | God Classes: TooManyMethods: SerializersBuilder`1 |
| src/Akkling.Hocon/Persistence.AtLeastOnceDelivery.fs | 8.5 | Near-clean | Code Duplication: Edited copy of a member (47 corresponding lines) |
How the grades work
A definite problem that already costs you something and drags the score down: a missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here tends to cause failures elsewhere.
Likely wrong, but not failing yet. It degrades the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to carry for two years either.
Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.
Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.
Methodology & how to trust this report
This survey is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. All 33 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.9, the weighted average across measured dimensions.
What we checked — 33 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, 134 of 155 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Canine Code Analyzer duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 | ✓ deterministic |
Run transparency — what happened this run
- D8 Code Coverage — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Coverage NOT MEASURED: `--collect:"XPlat Code Coverage"` names a data collector that ships in the `coverlet.collector` package, and this repository wires up none — no test project references it and no runsettings declares one. The absence of coverage here is therefore not evidence about the suite or about our analyzer environment: without a collector, `--collect` produces nothing even from a suite that builds and passes. Add a `coverlet.collector` PackageReference to the test project(s) (or commit the Cobertura/OpenCover/lcov report your CI produces) and real coverage will be measured. It is excluded from the score rather than counted as a near-zero defect. You can widen what we reach: add the `coverlet.collector` package to the test projects to enable coverage (or commit the Cobertura/OpenCover/lcov report your CI produces).
- D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. All 67 significant source file(s) were last meaningfully changed so long ago that no living knowledge remains — nothing since has been substantial enough to re-establish ownership (a broad, mechanical sweep that touches many files shallowly does not count, and neither does no activity at all). There is no concentration to measure, so the bus factor is not scored. This is not a clean bill: nobody currently holds working knowledge of this code (see D34 Knowledge Freshness). Counted over 67 of the 99 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
- 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 — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. This repository's source is written only in languages whose packages are published through a manifest, and no manifest in the tree makes a publication act: either there is no package manifest of any ecosystem (no package.json, pyproject.toml, setup.py, gemspec, Cargo.toml, pom.xml, build.gradle, composer.json, pubspec.yaml or mix.exs), or every one present declares in its package manager's own terms that it is not published (an npm package marked "private": true, a Cargo package with publish = false, a pubspec with publish_to: none, a Composer "project", a Poetry project with package-mode = false, or the "Private :: Do Not Upload" classifier). With no publication act there is no intentionally-exposed surface for API consistency to be judged over.
- D24 Comment Value — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
- AX6 Interface segregation — 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 is computed over the public interfaces this run's compilations declare, and none was loaded, so it had nothing 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.
- C3 Audit Trail — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These audit controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks audit controls.
- C4 Data Retention — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These retention controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks retention controls.
- C5 Data-Subject Rights — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These data-subject rights controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks data-subject rights controls.
- ED5 Idempotency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check decides whether a handler's mutation is safe to re-run by recognising its persistence writes (a database save, a repository write, an event publish) and its guards. Those markers are .NET member names, so in this repository's language a write such as `repository.save(order)` is not recognised and a same-named call on an unrelated library type could be. The handlers were found; their idempotency was neither confirmed nor ruled out.
- IC1 Incompleteness & stubs — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing 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.
- P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
- P8 Schema migrations — 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 EF Core usage in C# and the schema tooling its file scan recognises only, and no .NET project was loaded, and this repository's language is not one the scan models, 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.
- S1 Web-Security Posture — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These web-security controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks web-security controls.
- X1 Async correctness — 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 is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing 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.
- X12 Unreachable branch — 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 is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing 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.
- X13 Undrained process stream — 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 is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing 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.
- X14 Bypassable address classification — 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 is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing 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.
- X15 Unvalidated length from an untrusted reader — 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 is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing 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.
- X16 Unfloored truncation loop — 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 is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing 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.
- X17 Uncapped recursion over a caller-supplied document — 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 is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing 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.
- X18 Disposal-pattern correctness — 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 is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing 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.
- X19 Unrestored process-global state — 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 is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing 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.
- X2 Cancellation propagation — 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 is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing 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.
- X21 Side-effecting pattern guard — 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 is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing 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.
- X22 Contradicted release guard — 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 is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing 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.
- X24 Document value interpolated into markup unescaped — 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 is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing 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.
- X25 Inert configuration knob — 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 is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing 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.
- X26 Unsynchronised callback handoff — 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 is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing 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.
- X29 Per-element action decided by a fixed element — 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 is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing 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.
- X3 Exception handling — 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 is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing 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.
- X30 Support guard that admits what it rejects — 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 is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing 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.
- X32 Type resolved by simple name across every loaded assembly — 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 is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing 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.
- X4 Structured logging — 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 is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing 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.
- X5 Nullable reference types — 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 is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing 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.
- X6 Hand-rolled structured-format parsing — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and Python, JavaScript/TypeScript, Go, Java/Kotlin/Scala, Ruby, PHP, Rust, Swift, Erlang, Elixir and Dart source only, and no C# was loaded and none of those languages was found in this repository, 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.
- X7 Silent fallback defaults — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C#, Python, TypeScript/JavaScript, Rust, Go, Java, Kotlin, Scala, PHP, Ruby, Swift and Dart syntax only, and no C#, Python, TypeScript/JavaScript, Rust, Go, Java, Kotlin, Scala, PHP, Ruby, Swift or Dart was loaded for this repository, 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.
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.
- D11 Test Reliability: Flakiness is inferred from history/markers — we run the suite once (for coverage), not the repeated runs under varied conditions that reveal nondeterminism, so a flaky test never recorded as failing is invisible here.
- D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
- D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
- D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- 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.
- 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
4 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was HoconExtensions.op_Dynamic at 19.
What to do
- Bring the 4 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with HoconExtensions.op_Dynamic (cyclomatic 19), BytesToText.op_AmpDot (cyclomatic 18), BytesToText.op_AmpDot (cyclomatic 17). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 4 together lifts Cyclomatic Complexity from 9.4 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
D2 · Cognitive Complexity
17 method(s) exceeded the cognitive complexity threshold of 15; the worst was BytesToText.op_AmpDot at 153.
What to do
- Bring the 17 bodies over 15 down to 15 or less in Cognitive Complexity — start with BytesToText.op_AmpDot (cognitive 153), BytesToText.op_AmpDot (cognitive 136), BytesToText.op_AmpDot (cognitive 120). — 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 17 together lifts Cognitive Complexity from 6.2 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
D3 · God Classes
11 god class(es) detected.
What to do
- Resolve the 8 TooManyMethods finding(s) in God Classes — start with Shared.Tcp.fs, Shared.Cluster.fs, Shared.Udp.fs. — One of this dimension's main actionable groups (8 warning-level).
- Resolve the 3 TooManyFunctions finding(s) in God Classes — start with Source.fs, Flow.fs, SubFlow.fs. — One of this dimension's main actionable groups (3 warning-level).
D4 · Code Duplication
29 duplicated block group(s) detected. A further 5 rows report members as variants of one another; they aggregate block groups already counted above and are not themselves counted. 2 of the 34 are in trees this repository does not ship — vendored, example/demo, project-template, fixture and benchmark code — and are ranked below the shipped groups rather than excluded from them: the duplication there is real and is still counted in this dimension's score. The dimensions that publish a production-file census leave those trees out of theirs, so this count is deliberately drawn over the wider population.
What to do
- Resolve the 3 Duplicated block (14 lines × 2) finding(s) in Code Duplication — start with Persistence.Journal.fs, PersistentActor.fs, ActorRefs.fs. — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 3 Duplicated block (11 lines × 2) finding(s) in Code Duplication — start with Actor.Deployment.fs, Shared.Tcp.fs, ActorRefs.fs. — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 2 Duplicated block (13 lines × 2) finding(s) in Code Duplication — start with Akka.fs, Persistence.Journal.fs. — One of this dimension's main actionable groups (2 warning-level).
D5 · Coupling
11 projects, 0 dependency cycle(s), 0 unstable depended-on project(s).
D6 · Cohesion (LCOM4)
0 of 8 classes have LCOM4 above 3.
D11 · Test Reliability
0 flaky across 2 measured tier(s). unit: measured (0 flaky); other: measured (0 flaky).
D12 · Dependency Hygiene
14 outdated, 0 vulnerable, 0 deprecated packages.
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D14 · License Compliance
0 of 177 packages use a banned license. ★ DEPTH: this repository's MSBuild projects declare 13 direct `PackageReference`(s), and 162 further package(s) were reached beyond them by closing the graph over nuget.org's own nuspec dependency graph — so a banned licence pulled in only by a dependency's OWN dependencies is inside this verdict. A package whose licence nuget.org could not be asked for is not graded, and version ranges are taken at their lower bound, so this is the closure as that graph states it rather than a restored consumer's exact resolution.
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window.
D26 · Project Cohesion
1 of 6 build units (MSBuild) 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).
D27 · Navigability
92 % of calls cross a namespace and 8 % go through an interface, but 100 % of collaborators are co-located — so a call's collaborators sit together and tracing stays easy. Baseline: small — navigation cost is tolerated.
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
semgrep found no security issues.
D30 · Dependency Vulnerabilities
No known-vulnerable dependencies in any ecosystem this repository declares.
D34 · Knowledge Freshness
67 of 67 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is src/Akkling.Streams/Source.fs. Counted over 67 of the 99 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
What to do
- Resolve the 64 Orphaned file finding(s) in Knowledge Freshness — start with Library.fs (2), TestKit.fs (2), Shared.Tcp.fs. — One of this dimension's main actionable groups (64 recommendation-level).
- Resolve the 3 Most significant orphaned file finding(s) in Knowledge Freshness — start with Source.fs, Flow.fs, Shared.Cluster.fs. — One of this dimension's main actionable groups (3 recommendation-level).
- Resolve the 1 Dormant codebase finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
D35 · Change Coupling
No strong hidden change-coupling between production files.
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 1 platform declaration(s) and 0 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
Frontend & cross-cutting dimensions
AX10 · Code composition
AX3 · Project dependency cycles
AX4 · Dependency direction
AX8 · Test isolation
GD1 · Unfinished & placeholder code
M1 · Documentation (README)
What to do
- Add a build/run (quick start) section to the root README — the first thing a newcomer needs.
- Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
- No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
- Add a C4 context/container diagram (Structurizr, PlantUML or Mermaid) or an architecture.md overview.
M3 · Folder & project structure
P1 · CI/CD gates
- No CI workflow found (.github/workflows, azure-pipelines.yml, .gitlab-ci.yml, …) — changes aren't gated by an automated build/test.
What to do
- Add a CI workflow that builds and runs the test suite on every push/PR.
P3 · Security & performance tooling
- No static application security testing detected. For this repository's stack, add `semgrep --config=auto` plus gitleaks for committed secrets (F# is not a CodeQL language and has no language-specific SAST engine) — this repository has no CI pipeline yet, so run it locally to clear the existing findings, then make it a step of the first workflow you add so a regression fails the build. What was searched, so you can tell an absence from a miss: the 0 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.
- `src/Akkling.Cluster.Sharding/Akkling.Cluster.Sharding.fsproj` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`. — src/Akkling.Cluster.Sharding/Akkling.Cluster.Sharding.fsproj:21
What to do
- Run what this repository's stack ships: `semgrep --config=auto` plus gitleaks for committed secrets (F# is not a CodeQL language and has no language-specific SAST engine) — locally for now, since there is no CI pipeline here yet, and as a step of the first workflow you add so a security regression fails the build instead of landing.
- Enable Dependabot/Renovate or a dependency-review gate.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P6 · Release Hygiene
PF3 · Async & latency hygiene
X23 · Unguarded diagnostic materialisation
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 78% | Checked 4 of 11 | Solid. |
| Architecture | 94% | Exemplary | Solid. |
| Maturity | 41% | Weak — gated by D34, M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 46% | Adequate — gated by P1, P3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 100% | Checked 3 of 9 | Strongest area. |
| Performance | 100% | Exemplary | Solid. |
Unscored — 1 check(s) recorded observations but carry no score
- SC1 Supply-chain hygiene — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Not evidenced — 5 control(s) we could not find positive evidence for
- C3 Audit Trail — Not assessed: these audit controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks audit controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- C4 Data Retention — Not assessed: these retention controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks retention controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- C5 Data-Subject Rights — Not assessed: these data-subject rights controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks data-subject rights controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- P4 Deployment & Rollback — not evidenced — no deploy/rollback/approval signal in the repo; absence of evidence is not evidence of a manual release
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 78 check(s) not relevant to this codebase
- AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
- AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
- AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
- AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
- AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
- AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
- AX1 Captive dependencies — Not applicable: this repository's F# 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 — No container singleton was found, so there is no shared instance for concurrent requests to race on. No F# function in this code takes an ASP.NET Core or Suave HttpContext (a Giraffe, Saturn, Falco, Oxpecker or Suave handler) and no F# class is an ASP.NET Core controller, so no request handler shares module state between request threads.
- 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
- AX6 Interface segregation — not assessed — interface segregation is computed over a type surface 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.
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- 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.
- D10 Test Quality — ~1824 lines of test source are present (.fs) 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.
- D16 Bus Factor — dormant codebase — no living knowledge left to concentrate
- D17 Explicit Debt — the C# workspace loaded 0 projects, so explicit-debt density could not be measured
- D18 Solution Shape — D18 scores the shape of a C#/VB .NET solution; this repository's .NET projects are all F# (.fsproj), which the C#/VB workspace does not load, 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; F# not measured.
- D22 Internal API Consistency — No intentionally-exposed public API to evaluate for consistency.
- D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D24 Comment Value — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only — this repository's production source is .fs, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D25 ADR Conformance — no ADRs to check
- D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
- D32 Data Compliance (PII/GDPR) — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
- D36 Supply-chain Provenance & Signing — No CI/build pipeline found (.github/.forgejo/.gitea workflows, .circleci, .buildkite, .woodpecker, .teamcity, .gitlab-ci.yml, .travis.yml, bitbucket-pipelines.yml, .drone.yml, .cirrus.yml, .woodpecker.yml, appveyor.yml, azure-pipelines*.yml, .pipelines/, .vsts-ci/, .azuredevops/, Jenkinsfile); there is no build to attest provenance for.
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D7 Architectural Integrity — no checkable ADRs and no dependency cycles — architectural integrity not assessed
- D8 Code Coverage — Coverage not measured — no coverage collector is wired up
- DM1 Domain Modelling — applicable but not scored (2 of 3 signals for this style — below the bar we score at): 8 value object(s); 2 domain event(s); its domain events are published by services or handlers — no domain entity raises one
- ED1 Event-Driven — not scored — this repository shows only 1 of the 3 signals this lens looks for (1 event handler(s))
- ED5 Idempotency — Not assessed, and this one is on us: 10 command handler(s) or message consumer(s) were found here, but this check does not yet recognise persistence writes in this repository's language. Idempotency was neither confirmed nor ruled out — this is a limit of the analyzer, not a finding about your code.
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- M4 Documentation accuracy — Not applicable: the 2 current-state document(s) make no claim of a kind M4 checks.
- P12 CI test-gate honesty — no CI workflow found
- P2 Observability — This repository's F# source (10 module(s), 99 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 measured — the application kind could not be determined for this repo
- P8 Schema migrations — 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
- P9 Domain vs controller coverage — coverage not measured: this check compares the coverage of the analyzer's own test run across the domain and web layers, and that run measured none here — Test coverage (D8) says why
- PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for a BenchmarkDotNet reference in an .fsproj or .vbproj, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
- PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
- S1 Web-Security Posture — Not assessed: these web-security controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks web-security controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- X1 Async correctness — 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
- X10 Duplicated predicate — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X12 Unreachable branch — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X13 Undrained process stream — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X14 Bypassable address classification — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X15 Unvalidated length from an untrusted reader — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X16 Unfloored truncation loop — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X17 Uncapped recursion over a caller-supplied document — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X18 Disposal-pattern correctness — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X19 Unrestored process-global state — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X2 Cancellation propagation — 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
- X20 Mistyped argument guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X21 Side-effecting pattern guard — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X22 Contradicted release guard — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X24 Document value interpolated into markup unescaped — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X25 Inert configuration knob — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X26 Unsynchronised callback handoff — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X27 Collection changed while being enumerated — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X28 Index access outside its own emptiness guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X29 Per-element action decided by a fixed element — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X3 Exception handling — 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
- X30 Support guard that admits what it rejects — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X32 Type resolved by simple name across every loaded assembly — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X4 Structured logging — 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
- X5 Nullable reference types — 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
- X6 Hand-rolled structured-format parsing — 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
- X7 Silent fallback defaults — 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
- X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
Serious — 68 finding(s)
- TooManyMethods: TcpBuilder`1 src/Akkling.Hocon/Shared.Tcp.fs:32
- TooManyMethods: ClusterBuilder`1 src/Akkling.Hocon/Shared.Cluster.fs:32
- TooManyMethods: UdpBuilder`1 src/Akkling.Hocon/Shared.Udp.fs:32
- TooManyMethods: RemoteBuilder`1 src/Akkling.Hocon/Remote.fs:10
- TooManyMethods: SslProtocolBuilder`1 src/Akkling.Hocon/Remote.DotNetty.fs:91
- TooManyMethods: TypedPersistentContext`2 src/Akkling.Persistence/PersistentActor.fs:164
- TooManyMethods: TypeMappingBuilder`1 src/Akkling.Hocon/Actor.Router.fs:10
- TooManyMethods: SerializersBuilder`1 src/Akkling.Hocon/Actor.Serializers.fs:56
- TooManyFunctions: Source src/Akkling.Streams/Source.fs:23
- TooManyFunctions: Flow src/Akkling.Streams/Flow.fs:26
- TooManyFunctions: SubFlow src/Akkling.Streams/SubFlow.fs:17
- Duplicated block (14 lines × 2) src/Akkling.Hocon/Persistence.Journal.fs:50
- Duplicated block (14 lines × 2) src/Akkling.Persistence/PersistentActor.fs:286
- Duplicated block (14 lines × 2) src/Akkling/ActorRefs.fs:111
- Duplicated block (11 lines × 2) src/Akkling.Hocon/Actor.Deployment.fs:166
- Duplicated block (11 lines × 2) src/Akkling.Hocon/Shared.Tcp.fs:701
- Duplicated block (11 lines × 2) src/Akkling/ActorRefs.fs:98
- DurationToText.op_AmpDot (cognitive 28) src/Akkling.Hocon/Common.fs:85
- DurationToText.op_AmpDot (cognitive 28) src/Akkling.Hocon/Common.fs:88
- DurationToText.op_AmpDot (cognitive 21) src/Akkling.Hocon/Common.fs:79
- DurationToText.op_AmpDot (cognitive 21) src/Akkling.Hocon/Common.fs:82
- Duplicated block (13 lines × 2) src/Akkling.Hocon/Akka.fs:44
- Duplicated block (13 lines × 2) src/Akkling.Hocon/Persistence.Journal.fs:12
- Duplicated block (7 lines × 2) src/Akkling.Hocon/Akka.fs:26
- Duplicated block (7 lines × 2) src/Akkling.Hocon/IO.fs:13
- Duplicated block (8 lines × 2) src/Akkling.Streams/Flow.fs:699
- Duplicated block (8 lines × 2) src/Akkling.Streams/Flow.fs:847
- Duplicated block (6 lines × 2) src/Akkling.Hocon/Cluster.SplitBrainResolver.fs:15
- Duplicated block (6 lines × 2) src/Akkling.Streams/Flow.fs:315
- Duplicated block (5 lines × 2) src/Akkling.Streams/Flow.fs:347
- Duplicated block (5 lines × 2) src/Akkling.Hocon/Shared.Cluster.fs:368
- HoconExtensions.op_Dynamic (cyclomatic 19) src/Akkling/Configuration.fs:38
- BytesToText.op_AmpDot (cyclomatic 18) src/Akkling.Hocon/Common.fs:147
- BytesToText.op_AmpDot (cyclomatic 17) src/Akkling.Hocon/Common.fs:144
- BytesToText.op_AmpDot (cyclomatic 16) src/Akkling.Hocon/Common.fs:141
- BytesToText.op_AmpDot (cognitive 153) src/Akkling.Hocon/Common.fs:147
- BytesToText.op_AmpDot (cognitive 136) src/Akkling.Hocon/Common.fs:144
- BytesToText.op_AmpDot (cognitive 120) src/Akkling.Hocon/Common.fs:141
- BytesToText.op_AmpDot (cognitive 105) src/Akkling.Hocon/Common.fs:138
- BytesToText.op_AmpDot (cognitive 91) src/Akkling.Hocon/Common.fs:135
- BytesToText.op_AmpDot (cognitive 78) src/Akkling.Hocon/Common.fs:132
- BytesToText.op_AmpDot (cognitive 66) src/Akkling.Hocon/Common.fs:129
- BytesToText.op_AmpDot (cognitive 55) src/Akkling.Hocon/Common.fs:126
- BytesToText.op_AmpDot (cognitive 45) src/Akkling.Hocon/Common.fs:123
- BytesToText.op_AmpDot (cognitive 36) src/Akkling.Hocon/Common.fs:120
- BytesToText.op_AmpDot (cognitive 28) src/Akkling.Hocon/Common.fs:117
- BytesToText.op_AmpDot (cognitive 21) src/Akkling.Hocon/Common.fs:114
- HoconExtensions.op_Dynamic (cognitive 19) src/Akkling/Configuration.fs:38
- Members sharing a duplicated core (10 members, 50+ identical tokens) src/Akkling.Hocon/Actor.Deployment.fs:1
- Members sharing a duplicated core (4 members, 50+ identical tokens) src/Akkling.Hocon/Shared.Cluster.fs:1
- Edited copy of a member (126 corresponding lines) src/Akkling.Hocon/Cluster.FailureDetector.fs:1
- Edited copy of a member (47 corresponding lines) src/Akkling.Hocon/Persistence.AtLeastOnceDelivery.fs:1
- Edited copy of a member (23 corresponding lines) src/Akkling.Hocon/Actor.Inbox.fs:1
- Duplicated block (68 lines × 2) src/Akkling.Hocon/Cluster.FailureDetector.fs:32
- Duplicated block (53 lines × 2) src/Akkling.Hocon/Actor.DefaultMailbox.fs:24
- Duplicated block (26–34 lines × 2) src/Akkling.Hocon/Persistence.PluginFallback.fs:17
- Duplicated block (32 lines × 3) src/Akkling.Hocon/Cluster.FailureDetector.fs:13
- Duplicated block (18–19 lines × 2) src/Akkling.Hocon/Cluster.FailureDetector.fs:106
- Duplicated block (18 lines × 3) src/Akkling.Hocon/Cluster.FailureDetector.fs:78
- Duplicated block (18 lines × 2) src/Akkling.Hocon/Persistence.PluginFallback.fs:92
- Duplicated block (15 lines × 2) src/Akkling.Persistence/PersistentActor.fs:314
- Duplicated block (14 lines × 4) src/Akkling.Hocon/Shared.Cluster.fs:18
- Duplicated block (31 lines × 2) src/Akkling.Persistence/PersistentActor.fs:195
- Duplicated block (5 lines × 12) src/Akkling.Hocon/Actor.Deployment.fs:152
- Duplicated block (109 lines × 2) src/Akkling.Streams.TestKit.Xunit/Library.fs:14
- Duplicated block (98 lines × 2) src/Akkling.TestKit.Xunit/TestKit.fs:16
- No CI pipeline
- NuGet dependencies are not locked
Minor — 73 finding(s)
- Orphaned file src/Akkling.Hocon/Shared.Tcp.fs:1
- Orphaned file src/Akkling.Hocon/Shared.Udp.fs:1
- Orphaned file src/Akkling.Streams/SubFlow.fs:1
- Orphaned file src/Akkling.Hocon/Remote.fs:1
- Orphaned file src/Akkling.Hocon/Remote.DotNetty.fs:1
- Orphaned file src/Akkling.Hocon/Streams.fs:1
- Orphaned file src/Akkling.Hocon/Actor.Deployment.fs:1
- Orphaned file src/Akkling.Hocon/Types.fs:1
- Orphaned file src/Akkling.Hocon/Actor.Dispatcher.fs:1
- Orphaned file src/Akkling.Hocon/Actor.fs:1
- Orphaned file src/Akkling.Persistence/PersistentActor.fs:1
- Orphaned file src/Akkling.Hocon/Cluster.Client.fs:1
- Orphaned file src/Akkling.Hocon/CoordinatedShutdown.fs:1
- Orphaned file src/Akkling.Streams/Sink.fs:1
- Orphaned file src/Akkling.DistributedData/Collections.fs:1
- Orphaned file src/Akkling.Hocon/Persistence.Plugin.fs:1
- Orphaned file src/Akkling/ActorRefs.fs:1
- Orphaned file src/Akkling/Actors.fs:1
- Orphaned file src/Akkling.Hocon/Common.fs:1
- Orphaned file src/Akkling.Hocon/Shared.Debug.fs:1
- Orphaned file src/Akkling.Hocon/Persistence.SnapshotStore.fs:1
- Orphaned file src/Akkling.Cluster.Sharding/ClusterSharding.fs:1
- Orphaned file src/Akkling.Hocon/Akka.fs:1
- Orphaned file src/Akkling.Hocon/Remote.Protocols.fs:1
- Orphaned file src/Akkling.Streams/Graph.fs:1
- Most significant orphaned file src/Akkling.Streams/Source.fs:1
- Most significant orphaned file src/Akkling.Streams/Flow.fs:1
- Most significant orphaned file src/Akkling.Hocon/Shared.Cluster.fs:1
- Projects may be oversized for their cohesion
- Dormant codebase
- No ADRs
- No architecture diagram/doc
- No SAST
- No dependency-update automation src/Akkling.Cluster.Sharding/Akkling.Cluster.Sharding.fsproj:21
Minor — 14 finding(s)
- Outdated: Akka
- Outdated: Akka.Serialization.Hyperion
- Outdated: FSharp.Core
- Outdated: Akka.Streams
- Outdated: Akka.Persistence
- Outdated: Akka.TestKit.Xunit2
- Outdated: Akka.DistributedData
- Outdated: Akka.Cluster.Sharding
- Outdated: FsCheck.Xunit.v3
- Outdated: Microsoft.NET.Test.Sdk
- Outdated: xunit.runner.visualstudio
- Outdated: xunit.v3
- Outdated: Akka.Streams.TestKit
- Outdated: Akka.TestKit.Xunit
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-41ba20f71343443abb710b5fe39b8d6e/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-41ba20f71343443abb710b5fe39b8d6e/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 . | 0 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | dotnet | — | dotnet list Akkling.sln package --vulnerable --include-transitive --format json | 0 | artifacts/raw/dotnet-vulnerable.json |
| D31 · IaC & Container Security | trivy | — | trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan. | 0 | — |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. | 0 | — |
| D36 · Supply-chain Provenance & Signing | provenance | — | provenance: not applicable — No CI/build pipeline found (.github/.forgejo/.gitea workflows, .circleci, .buildkite, .woodpecker, .teamcity, .gitlab-ci.yml, .travis.yml, bitbucket-pipelines.yml, .drone.yml, .cirrus.yml, .woodpecker.yml, appveyor.yml, azure-pipelines*.yml, .pipelines/, .vsts-ci/, .azuredevops/, Jenkinsfile); there is no build to attest provenance for. | 0 | — |
| D37 · Vulnerability-disclosure Policy | disclosure | — | disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . /tmp/codehealth-osv-sbom-05a1aabe24ae4dd58714b1ac78e03e29 | 0 | artifacts/raw/osv-scanner.json |