Executive summary
parapet-io/parapet falls short of our standard for a preview release because we found no automated security scanning of the code, its secrets or its dependencies. It scores 62 out of 100 and is rated Adequate, and all ten of its critical findings are security problems in the build pipeline.
Production Readiness, at 54, is the weakest lens and counts most in the score. The best first step is declaring which values may be missing, worth about 4 points. Keeping a changelog would lift Production Readiness itself, worth about 3 points. Raising Production Readiness to 62 would lift the score to about 65.
Ten pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Pinning each tool to an exact version would close this risk.
The product code is 7,871 lines, about €18,000 to rebuild. The check for the health of its packages couldn't finish, so that result is missing, not a clean pass.
If Production Readiness rose from 54 to 62, the lowest score rated Strong, the score would rise from 62 to about 65.
Rebuild cost: about €18,000 · Estimate
| Cost to rebuild | €6,000 to €30,000, for 101 to 319 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.9 at a score of 62. 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: 7,871 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 effect | 2 net.transport | 3 snapshot | 4 Event | 5 EventCodec | 6 dsl | 7 effect.Backoff | 8 effect.Clock | 9 effect.Outcome | 10 net.transport.zmq | 11 net.transport.zmq.ZmqTcpDuplexTransport.Command | 12 net.transport.zmq.ZmqTcpServer.Command | 13 runtime.Scheduler | 14 snapshot.SnapshotManager.Item | 15 EventCodec.Schema | 16 dsl.Coproduct | 17 dsl.Free | 18 journal | 19 runtime.Context | 20 runtime.DslInterpreter | 21 runtime | 22 dsl.Dsl | 23 effect.Fiber | 24 fault | 25 syntax | 26 io.parapet | 27 fault.FaultPolicy | 28 Channel | 29 DeadLetterProcess | 30 EventCodecAvailability | 31 Process | 32 cats | 33 dsl.Dsl.FlowOps | 34 net.processes.ClientProcess | 35 net.processes.DatagramProcess | 36 net.processes.DuplexProcess | 37 net.processes.ServerProcess | 38 runtime.Scheduler.SchedulerImpl | 39 testutils | 40 net.processes |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 effect | ||||||||||||||||||||||||||||||||||||||||
| 2 net.transport | ||||||||||||||||||||||||||||||||||||||||
| 3 snapshot | ||||||||||||||||||||||||||||||||||||||||
| 4 Event | 3 | |||||||||||||||||||||||||||||||||||||||
| 5 EventCodec | 1 | |||||||||||||||||||||||||||||||||||||||
| 6 dsl | 1 | |||||||||||||||||||||||||||||||||||||||
| 7 effect.Backoff | 2 | |||||||||||||||||||||||||||||||||||||||
| 8 effect.Clock | 2 | |||||||||||||||||||||||||||||||||||||||
| 9 effect.Outcome | 3 | |||||||||||||||||||||||||||||||||||||||
| 10 net.transport.zmq | 15 | |||||||||||||||||||||||||||||||||||||||
| 11 net.transport.zmq.ZmqTcpDuplexTransport.Command | 1 | |||||||||||||||||||||||||||||||||||||||
| 12 net.transport.zmq.ZmqTcpServer.Command | 2 | |||||||||||||||||||||||||||||||||||||||
| 13 runtime.Scheduler | 2 | 1 | 3 | 2 | ||||||||||||||||||||||||||||||||||||
| 14 snapshot.SnapshotManager.Item | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 15 EventCodec.Schema | 2 | |||||||||||||||||||||||||||||||||||||||
| 16 dsl.Coproduct | 2 | |||||||||||||||||||||||||||||||||||||||
| 17 dsl.Free | 3 | |||||||||||||||||||||||||||||||||||||||
| 18 journal | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 19 runtime.Context | 5 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 20 runtime.DslInterpreter | 2 | 2 | ||||||||||||||||||||||||||||||||||||||
| 21 runtime | 2 | 2 | 1 | 4 | 4 | 1 | 1 | 12 | ||||||||||||||||||||||||||||||||
| 22 dsl.Dsl | 1 | 6 | 3 | 4 | ||||||||||||||||||||||||||||||||||||
| 23 effect.Fiber | 4 | 2 | ||||||||||||||||||||||||||||||||||||||
| 24 fault | 1 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 25 syntax | 1 | |||||||||||||||||||||||||||||||||||||||
| 26 io.parapet | 7 | 2 | 1 | 2 | 1 | 2 | 1 | 5 | 1 | 1 | 3 | |||||||||||||||||||||||||||||
| 27 fault.FaultPolicy | 1 | 3 | ||||||||||||||||||||||||||||||||||||||
| 28 Channel | 2 | 2 | ||||||||||||||||||||||||||||||||||||||
| 29 DeadLetterProcess | 1 | |||||||||||||||||||||||||||||||||||||||
| 30 EventCodecAvailability | 4 | |||||||||||||||||||||||||||||||||||||||
| 31 Process | 3 | |||||||||||||||||||||||||||||||||||||||
| 32 cats | 3 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 33 dsl.Dsl.FlowOps | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 34 net.processes.ClientProcess | 1 | 3 | ||||||||||||||||||||||||||||||||||||||
| 35 net.processes.DatagramProcess | 1 | 3 | ||||||||||||||||||||||||||||||||||||||
| 36 net.processes.DuplexProcess | 1 | 3 | ||||||||||||||||||||||||||||||||||||||
| 37 net.processes.ServerProcess | 1 | 3 | ||||||||||||||||||||||||||||||||||||||
| 38 runtime.Scheduler.SchedulerImpl | 3 | 2 | 1 | 1 | 2 | 2 | ||||||||||||||||||||||||||||||||||
| 39 testutils | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 40 net.processes | 2 | 8 | 1 |
4→26 Event uses io.parapet part of a loop✕
- Connections
- 3 pairs of types, where a type in Event uses a type in io.parapet.
- The types involved
io.parapet.Event.DeadLetter→io.parapet.Eventio.parapet.Event.Failure→io.parapet.Eventio.parapet.Event.SystemEvent→io.parapet.Event
- Direction
- Event uses io.parapet, so a change to io.parapet can break Event, while a change to Event can't break io.parapet.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
5→26 EventCodec uses io.parapet part of a loop✕
- Connections
- 1 pair of types, where a type in EventCodec uses a type in io.parapet.
- The types involved
io.parapet.EventCodec.Simple→io.parapet.EventCodec
- Direction
- EventCodec uses io.parapet, so a change to io.parapet can break EventCodec, while a change to EventCodec can't break io.parapet.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
6→1 dsl uses effect✕
- Connections
- 1 pair of types, where a type in dsl uses a type in effect.
- The types involved
io.parapet.dsl.Free→io.parapet.effect.Monad
- Direction
- dsl uses effect, so a change to effect can break dsl, while a change to dsl can't break effect.
- Position
- Below the diagonal: dsl uses a module listed above it, which is the healthy direction.
7→1 effect.Backoff uses effect✕
- Connections
- 2 pairs of types, where a type in effect.Backoff uses a type in effect.
- The types involved
io.parapet.effect.Backoff.Exp→io.parapet.effect.Backoffio.parapet.effect.Backoff.Fixed→io.parapet.effect.Backoff
- Direction
- effect.Backoff uses effect, so a change to effect can break effect.Backoff, while a change to effect.Backoff can't break effect.
- Position
- Below the diagonal: effect.Backoff uses a module listed above it, which is the healthy direction.
8→1 effect.Clock uses effect✕
- Connections
- 2 pairs of types, where a type in effect.Clock uses a type in effect.
- The types involved
io.parapet.effect.Clock.Mock→io.parapet.effect.Clockio.parapet.effect.Clock.SystemClock→io.parapet.effect.Clock
- Direction
- effect.Clock uses effect, so a change to effect can break effect.Clock, while a change to effect.Clock can't break effect.
- Position
- Below the diagonal: effect.Clock uses a module listed above it, which is the healthy direction.
9→1 effect.Outcome uses effect✕
- Connections
- 3 pairs of types, where a type in effect.Outcome uses a type in effect.
- The types involved
io.parapet.effect.Outcome.Canceled→io.parapet.effect.Outcomeio.parapet.effect.Outcome.Failed→io.parapet.effect.Outcomeio.parapet.effect.Outcome.Succeeded→io.parapet.effect.Outcome
- Direction
- effect.Outcome uses effect, so a change to effect can break effect.Outcome, while a change to effect.Outcome can't break effect.
- Position
- Below the diagonal: effect.Outcome uses a module listed above it, which is the healthy direction.
10→2 net.transport.zmq uses net.transport✕
- Connections
- 15 pairs of types, where a type in net.transport.zmq uses a type in net.transport.
- The types involved
io.parapet.net.transport.zmq.ZmqSocketWorker→io.parapet.net.transport.ReceiveResultio.parapet.net.transport.zmq.ZmqSocketWorker→io.parapet.net.transport.TransportErrorio.parapet.net.transport.zmq.ZmqTcpClient→io.parapet.net.transport.ClientTransportio.parapet.net.transport.zmq.ZmqTcpClient→io.parapet.net.transport.Messageio.parapet.net.transport.zmq.ZmqTcpClient→io.parapet.net.transport.TransportErrorio.parapet.net.transport.zmq.ZmqTcpDuplexTransport→io.parapet.net.transport.DuplexTransportio.parapet.net.transport.zmq.ZmqTcpDuplexTransport→io.parapet.net.transport.Messageio.parapet.net.transport.zmq.ZmqTcpDuplexTransport→io.parapet.net.transport.ReceiveResultio.parapet.net.transport.zmq.ZmqTcpDuplexTransport→io.parapet.net.transport.TransportErrorio.parapet.net.transport.zmq.ZmqTcpServer→io.parapet.net.transport.Messageio.parapet.net.transport.zmq.ZmqTcpServer→io.parapet.net.transport.ReceiveResultio.parapet.net.transport.zmq.ZmqTcpServer→io.parapet.net.transport.RoutedMessageio.parapet.net.transport.zmq.ZmqTcpServer→io.parapet.net.transport.RoutingIdio.parapet.net.transport.zmq.ZmqTcpServer→io.parapet.net.transport.ServerTransportio.parapet.net.transport.zmq.ZmqTcpServer→io.parapet.net.transport.TransportError
- Direction
- net.transport.zmq uses net.transport, so a change to net.transport can break net.transport.zmq, while a change to net.transport.zmq can't break net.transport.
- Position
- Below the diagonal: net.transport.zmq uses a module listed above it, which is the healthy direction.
11→2 net.transport.zmq.ZmqTcpDuplexTransport.Command uses net.transport✕
- Connections
- 1 pair of types, where a type in net.transport.zmq.ZmqTcpDuplexTransport.Command uses a type in net.transport.
- The types involved
io.parapet.net.transport.zmq.ZmqTcpDuplexTransport.Command.Send→io.parapet.net.transport.Message
- Direction
- net.transport.zmq.ZmqTcpDuplexTransport.Command uses net.transport, so a change to net.transport can break net.transport.zmq.ZmqTcpDuplexTransport.Command, while a change to net.transport.zmq.ZmqTcpDuplexTransport.Command can't break net.transport.
- Position
- Below the diagonal: net.transport.zmq.ZmqTcpDuplexTransport.Command uses a module listed above it, which is the healthy direction.
12→2 net.transport.zmq.ZmqTcpServer.Command uses net.transport✕
- Connections
- 2 pairs of types, where a type in net.transport.zmq.ZmqTcpServer.Command uses a type in net.transport.
- The types involved
io.parapet.net.transport.zmq.ZmqTcpServer.Command.Reply→io.parapet.net.transport.Messageio.parapet.net.transport.zmq.ZmqTcpServer.Command.Reply→io.parapet.net.transport.RoutingId
- Direction
- net.transport.zmq.ZmqTcpServer.Command uses net.transport, so a change to net.transport can break net.transport.zmq.ZmqTcpServer.Command, while a change to net.transport.zmq.ZmqTcpServer.Command can't break net.transport.
- Position
- Below the diagonal: net.transport.zmq.ZmqTcpServer.Command uses a module listed above it, which is the healthy direction.
13→1 runtime.Scheduler uses effect✕
- Connections
- 2 pairs of types, where a type in runtime.Scheduler uses a type in effect.
- The types involved
io.parapet.runtime.Scheduler.LoggerWrapper→io.parapet.effect.Effectio.parapet.runtime.Scheduler.SchedulerImpl→io.parapet.effect.Queue
- Direction
- runtime.Scheduler uses effect, so a change to effect can break runtime.Scheduler, while a change to runtime.Scheduler can't break effect.
- Position
- Below the diagonal: runtime.Scheduler uses a module listed above it, which is the healthy direction.
13→19 runtime.Scheduler uses runtime.Context part of a loop✕
- Connections
- 1 pair of types, where a type in runtime.Scheduler uses a type in runtime.Context.
- The types involved
io.parapet.runtime.Scheduler.SchedulerImpl→io.parapet.runtime.Context.ProcessState
- Direction
- runtime.Scheduler uses runtime.Context, so a change to runtime.Context can break runtime.Scheduler, while a change to runtime.Scheduler can't break runtime.Context.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
13→21 runtime.Scheduler uses runtime part of a loop✕
- Connections
- 3 pairs of types, where a type in runtime.Scheduler uses a type in runtime.
- The types involved
io.parapet.runtime.Scheduler.Deliver→io.parapet.runtime.Envelopeio.parapet.runtime.Scheduler.SchedulerImpl→io.parapet.runtime.Schedulerio.parapet.runtime.Scheduler.Signal→io.parapet.runtime.Envelope
- Direction
- runtime.Scheduler uses runtime, so a change to runtime can break runtime.Scheduler, while a change to runtime.Scheduler can't break runtime.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
13→26 runtime.Scheduler uses io.parapet part of a loop✕
- Connections
- 2 pairs of types, where a type in runtime.Scheduler uses a type in io.parapet.
- The types involved
io.parapet.runtime.Scheduler.Inbox→io.parapet.Eventio.parapet.runtime.Scheduler.NotifyEvent→io.parapet.Event
- Direction
- runtime.Scheduler uses io.parapet, so a change to io.parapet can break runtime.Scheduler, while a change to runtime.Scheduler can't break io.parapet.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
14→1 snapshot.SnapshotManager.Item uses effect✕
- Connections
- 1 pair of types, where a type in snapshot.SnapshotManager.Item uses a type in effect.
- The types involved
io.parapet.snapshot.SnapshotManager.Item.Flush→io.parapet.effect.Deferred
- Direction
- snapshot.SnapshotManager.Item uses effect, so a change to effect can break snapshot.SnapshotManager.Item, while a change to snapshot.SnapshotManager.Item can't break effect.
- Position
- Below the diagonal: snapshot.SnapshotManager.Item uses a module listed above it, which is the healthy direction.
14→3 snapshot.SnapshotManager.Item uses snapshot✕
- Connections
- 1 pair of types, where a type in snapshot.SnapshotManager.Item uses a type in snapshot.
- The types involved
io.parapet.snapshot.SnapshotManager.Item.Store→io.parapet.snapshot.Snapshot
- Direction
- snapshot.SnapshotManager.Item uses snapshot, so a change to snapshot can break snapshot.SnapshotManager.Item, while a change to snapshot.SnapshotManager.Item can't break snapshot.
- Position
- Below the diagonal: snapshot.SnapshotManager.Item uses a module listed above it, which is the healthy direction.
15→5 EventCodec.Schema uses EventCodec✕
- Connections
- 2 pairs of types, where a type in EventCodec.Schema uses a type in EventCodec.
- The types involved
io.parapet.EventCodec.Schema.Simple→io.parapet.EventCodec.Schemaio.parapet.EventCodec.Schema.Union→io.parapet.EventCodec.Schema
- Direction
- EventCodec.Schema uses EventCodec, so a change to EventCodec can break EventCodec.Schema, while a change to EventCodec.Schema can't break EventCodec.
- Position
- Below the diagonal: EventCodec.Schema uses a module listed above it, which is the healthy direction.
16→6 dsl.Coproduct uses dsl✕
- Connections
- 2 pairs of types, where a type in dsl.Coproduct uses a type in dsl.
- The types involved
io.parapet.dsl.Coproduct.Left→io.parapet.dsl.Coproductio.parapet.dsl.Coproduct.Right→io.parapet.dsl.Coproduct
- Direction
- dsl.Coproduct uses dsl, so a change to dsl can break dsl.Coproduct, while a change to dsl.Coproduct can't break dsl.
- Position
- Below the diagonal: dsl.Coproduct uses a module listed above it, which is the healthy direction.
17→6 dsl.Free uses dsl✕
- Connections
- 3 pairs of types, where a type in dsl.Free uses a type in dsl.
- The types involved
io.parapet.dsl.Free.FlatMapped→io.parapet.dsl.Freeio.parapet.dsl.Free.Pure→io.parapet.dsl.Freeio.parapet.dsl.Free.Suspend→io.parapet.dsl.Free
- Direction
- dsl.Free uses dsl, so a change to dsl can break dsl.Free, while a change to dsl.Free can't break dsl.
- Position
- Below the diagonal: dsl.Free uses a module listed above it, which is the healthy direction.
18→4 journal uses Event✕
- Connections
- 1 pair of types, where a type in journal uses a type in Event.
- The types involved
io.parapet.journal.RegisteredEventCodec→io.parapet.Event.Registered
- Direction
- journal uses Event, so a change to Event can break journal, while a change to journal can't break Event.
- Position
- Below the diagonal: journal uses a module listed above it, which is the healthy direction.
18→5 journal uses EventCodec✕
- Connections
- 2 pairs of types, where a type in journal uses a type in EventCodec.
- The types involved
io.parapet.journal.JournalDraft→io.parapet.EventCodec.EncodedEventio.parapet.journal.JournalEntry→io.parapet.EventCodec.EncodedEvent
- Direction
- journal uses EventCodec, so a change to EventCodec can break journal, while a change to journal can't break EventCodec.
- Position
- Below the diagonal: journal uses a module listed above it, which is the healthy direction.
19→1 runtime.Context uses effect✕
- Connections
- 5 pairs of types, where a type in runtime.Context uses a type in effect.
- The types involved
io.parapet.runtime.Context.OffloadHandle→io.parapet.effect.Deferredio.parapet.runtime.Context.OffloadHandle→io.parapet.effect.EffectFiberio.parapet.runtime.Context.OffloadTracker→io.parapet.effect.Deferredio.parapet.runtime.Context.OffloadTracker→io.parapet.effect.EffectFiberio.parapet.runtime.Context.ProcessState→io.parapet.effect.Deferred
- Direction
- runtime.Context uses effect, so a change to effect can break runtime.Context, while a change to runtime.Context can't break effect.
- Position
- Below the diagonal: runtime.Context uses a module listed above it, which is the healthy direction.
19→13 runtime.Context uses runtime.Scheduler✕
- Connections
- 1 pair of types, where a type in runtime.Context uses a type in runtime.Scheduler.
- The types involved
io.parapet.runtime.Context.ProcessState→io.parapet.runtime.Scheduler.Task
- Direction
- runtime.Context uses runtime.Scheduler, so a change to runtime.Scheduler can break runtime.Context, while a change to runtime.Context can't break runtime.Scheduler.
- Position
- Below the diagonal: runtime.Context uses a module listed above it, which is the healthy direction.
19→26 runtime.Context uses io.parapet part of a loop✕
- Connections
- 1 pair of types, where a type in runtime.Context uses a type in io.parapet.
- The types involved
io.parapet.runtime.Context.ProcessState→io.parapet.Process
- Direction
- runtime.Context uses io.parapet, so a change to io.parapet can break runtime.Context, while a change to runtime.Context can't break io.parapet.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
20→19 runtime.DslInterpreter uses runtime.Context✕
- Connections
- 2 pairs of types, where a type in runtime.DslInterpreter uses a type in runtime.Context.
- The types involved
io.parapet.runtime.DslInterpreter.Impl→io.parapet.runtime.Context.ProcessStateio.parapet.runtime.DslInterpreter.Interpreter→io.parapet.runtime.Context.ProcessState
- Direction
- runtime.DslInterpreter uses runtime.Context, so a change to runtime.Context can break runtime.DslInterpreter, while a change to runtime.DslInterpreter can't break runtime.Context.
- Position
- Below the diagonal: runtime.DslInterpreter uses a module listed above it, which is the healthy direction.
20→21 runtime.DslInterpreter uses runtime part of a loop✕
- Connections
- 2 pairs of types, where a type in runtime.DslInterpreter uses a type in runtime.
- The types involved
io.parapet.runtime.DslInterpreter.Impl→io.parapet.runtime.Scopeio.parapet.runtime.DslInterpreter.Interpreter→io.parapet.runtime.Scope
- Direction
- runtime.DslInterpreter uses runtime, so a change to runtime can break runtime.DslInterpreter, while a change to runtime.DslInterpreter can't break runtime.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
21→1 runtime uses effect✕
- Connections
- 2 pairs of types, where a type in runtime uses a type in effect.
- The types involved
io.parapet.runtime.Context→io.parapet.effect.Clockio.parapet.runtime.DslInterpreter→io.parapet.effect.Effect
- Direction
- runtime uses effect, so a change to effect can break runtime, while a change to runtime can't break effect.
- Position
- Below the diagonal: runtime uses a module listed above it, which is the healthy direction.
21→3 runtime uses snapshot✕
- Connections
- 2 pairs of types, where a type in runtime uses a type in snapshot.
- The types involved
io.parapet.runtime.Context→io.parapet.snapshot.SnapshotManagerio.parapet.runtime.Context→io.parapet.snapshot.Snapshotable
- Direction
- runtime uses snapshot, so a change to snapshot can break runtime, while a change to runtime can't break snapshot.
- Position
- Below the diagonal: runtime uses a module listed above it, which is the healthy direction.
21→5 runtime uses EventCodec✕
- Connections
- 1 pair of types, where a type in runtime uses a type in EventCodec.
- The types involved
io.parapet.runtime.Context→io.parapet.EventCodec.EncodedEvent
- Direction
- runtime uses EventCodec, so a change to EventCodec can break runtime, while a change to runtime can't break EventCodec.
- Position
- Below the diagonal: runtime uses a module listed above it, which is the healthy direction.
21→13 runtime uses runtime.Scheduler✕
- Connections
- 4 pairs of types, where a type in runtime uses a type in runtime.Scheduler.
- The types involved
io.parapet.runtime.Context→io.parapet.runtime.Scheduler.SubmissionResultio.parapet.runtime.Context→io.parapet.runtime.Scheduler.Taskio.parapet.runtime.Scheduler→io.parapet.runtime.Scheduler.SubmissionResultio.parapet.runtime.Scheduler→io.parapet.runtime.Scheduler.Task
- Direction
- runtime uses runtime.Scheduler, so a change to runtime.Scheduler can break runtime, while a change to runtime can't break runtime.Scheduler.
- Position
- Below the diagonal: runtime uses a module listed above it, which is the healthy direction.
21→18 runtime uses journal✕
- Connections
- 4 pairs of types, where a type in runtime uses a type in journal.
- The types involved
io.parapet.runtime.Context→io.parapet.journal.DeliveryRecorderio.parapet.runtime.Context→io.parapet.journal.JournalDraftio.parapet.runtime.Context→io.parapet.journal.JournalEntryio.parapet.runtime.Recovery→io.parapet.journal.JournalEntry
- Direction
- runtime uses journal, so a change to journal can break runtime, while a change to runtime can't break journal.
- Position
- Below the diagonal: runtime uses a module listed above it, which is the healthy direction.
21→19 runtime uses runtime.Context✕
- Connections
- 1 pair of types, where a type in runtime uses a type in runtime.Context.
- The types involved
io.parapet.runtime.Context→io.parapet.runtime.Context.ProcessState
- Direction
- runtime uses runtime.Context, so a change to runtime.Context can break runtime, while a change to runtime can't break runtime.Context.
- Position
- Below the diagonal: runtime uses a module listed above it, which is the healthy direction.
21→20 runtime uses runtime.DslInterpreter✕
- Connections
- 1 pair of types, where a type in runtime uses a type in runtime.DslInterpreter.
- The types involved
io.parapet.runtime.Context→io.parapet.runtime.DslInterpreter.Interpreter
- Direction
- runtime uses runtime.DslInterpreter, so a change to runtime.DslInterpreter can break runtime, while a change to runtime can't break runtime.DslInterpreter.
- Position
- Below the diagonal: runtime uses a module listed above it, which is the healthy direction.
21→26 runtime uses io.parapet part of a loop✕
- Connections
- 12 pairs of types, where a type in runtime uses a type in io.parapet.
- The types involved
io.parapet.runtime.Context→io.parapet.EventCodecio.parapet.runtime.Context→io.parapet.Processio.parapet.runtime.Envelope→io.parapet.Eventio.parapet.runtime.EventTransformer→io.parapet.Eventio.parapet.runtime.Noop→io.parapet.Eventio.parapet.runtime.Noop→io.parapet.Processio.parapet.runtime.Noop→io.parapet.ProcessRefio.parapet.runtime.Recovery→io.parapet.Eventio.parapet.runtime.Recovery→io.parapet.Processio.parapet.runtime.SystemProcess→io.parapet.Eventio.parapet.runtime.SystemProcess→io.parapet.Processio.parapet.runtime.SystemProcess→io.parapet.ProcessRef
- Direction
- runtime uses io.parapet, so a change to io.parapet can break runtime, while a change to runtime can't break io.parapet.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
22→1 dsl.Dsl uses effect✕
- Connections
- 1 pair of types, where a type in dsl.Dsl uses a type in effect.
- The types involved
io.parapet.dsl.Dsl.FlowOps→io.parapet.effect.Fiber
- Direction
- dsl.Dsl uses effect, so a change to effect can break dsl.Dsl, while a change to dsl.Dsl can't break effect.
- Position
- Below the diagonal: dsl.Dsl uses a module listed above it, which is the healthy direction.
22→6 dsl.Dsl uses dsl✕
- Connections
- 6 pairs of types, where a type in dsl.Dsl uses a type in dsl.
- The types involved
io.parapet.dsl.Dsl.FlowOps→io.parapet.dsl.Freeio.parapet.dsl.Dsl.Fork→io.parapet.dsl.Freeio.parapet.dsl.Dsl.MapScope→io.parapet.dsl.Freeio.parapet.dsl.Dsl.Par→io.parapet.dsl.Freeio.parapet.dsl.Dsl.Race→io.parapet.dsl.Freeio.parapet.dsl.Dsl.RuntimeOps→io.parapet.dsl.Free
- Direction
- dsl.Dsl uses dsl, so a change to dsl can break dsl.Dsl, while a change to dsl.Dsl can't break dsl.
- Position
- Below the diagonal: dsl.Dsl uses a module listed above it, which is the healthy direction.
22→21 dsl.Dsl uses runtime✕
- Connections
- 3 pairs of types, where a type in dsl.Dsl uses a type in runtime.
- The types involved
io.parapet.dsl.Dsl.FlowOps→io.parapet.runtime.Scopeio.parapet.dsl.Dsl.MapScope→io.parapet.runtime.Scopeio.parapet.dsl.Dsl.WithScope→io.parapet.runtime.Scope
- Direction
- dsl.Dsl uses runtime, so a change to runtime can break dsl.Dsl, while a change to dsl.Dsl can't break runtime.
- Position
- Below the diagonal: dsl.Dsl uses a module listed above it, which is the healthy direction.
22→26 dsl.Dsl uses io.parapet part of a loop✕
- Connections
- 4 pairs of types, where a type in dsl.Dsl uses a type in io.parapet.
- The types involved
io.parapet.dsl.Dsl.FlowOps→io.parapet.Eventio.parapet.dsl.Dsl.FlowOps→io.parapet.ProcessRefio.parapet.dsl.Dsl.Register→io.parapet.Processio.parapet.dsl.Dsl.WithSender→io.parapet.ProcessRef
- Direction
- dsl.Dsl uses io.parapet, so a change to io.parapet can break dsl.Dsl, while a change to dsl.Dsl can't break io.parapet.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
23→1 effect.Fiber uses effect✕
- Connections
- 4 pairs of types, where a type in effect.Fiber uses a type in effect.
- The types involved
io.parapet.effect.Fiber.IdFiber→io.parapet.effect.Fiberio.parapet.effect.Fiber.IdFiber→io.parapet.effect.Outcomeio.parapet.effect.Fiber.RuntimeFiber→io.parapet.effect.Fiberio.parapet.effect.Fiber.RuntimeFiber→io.parapet.effect.Outcome
- Direction
- effect.Fiber uses effect, so a change to effect can break effect.Fiber, while a change to effect.Fiber can't break effect.
- Position
- Below the diagonal: effect.Fiber uses a module listed above it, which is the healthy direction.
23→22 effect.Fiber uses dsl.Dsl✕
- Connections
- 2 pairs of types, where a type in effect.Fiber uses a type in dsl.Dsl.
- The types involved
io.parapet.effect.Fiber.IdFiber→io.parapet.dsl.Dsl.WithDslio.parapet.effect.Fiber.RuntimeFiber→io.parapet.dsl.Dsl.WithDsl
- Direction
- effect.Fiber uses dsl.Dsl, so a change to dsl.Dsl can break effect.Fiber, while a change to effect.Fiber can't break dsl.Dsl.
- Position
- Below the diagonal: effect.Fiber uses a module listed above it, which is the healthy direction.
24→19 fault uses runtime.Context✕
- Connections
- 1 pair of types, where a type in fault uses a type in runtime.Context.
- The types involved
io.parapet.fault.FaultInjector→io.parapet.runtime.Context.ProcessState
- Direction
- fault uses runtime.Context, so a change to runtime.Context can break fault, while a change to fault can't break runtime.Context.
- Position
- Below the diagonal: fault uses a module listed above it, which is the healthy direction.
24→20 fault uses runtime.DslInterpreter✕
- Connections
- 1 pair of types, where a type in fault uses a type in runtime.DslInterpreter.
- The types involved
io.parapet.fault.FaultInjector→io.parapet.runtime.DslInterpreter.Interpreter
- Direction
- fault uses runtime.DslInterpreter, so a change to runtime.DslInterpreter can break fault, while a change to fault can't break runtime.DslInterpreter.
- Position
- Below the diagonal: fault uses a module listed above it, which is the healthy direction.
24→21 fault uses runtime✕
- Connections
- 1 pair of types, where a type in fault uses a type in runtime.
- The types involved
io.parapet.fault.FaultInjector→io.parapet.runtime.Scope
- Direction
- fault uses runtime, so a change to runtime can break fault, while a change to fault can't break runtime.
- Position
- Below the diagonal: fault uses a module listed above it, which is the healthy direction.
24→22 fault uses dsl.Dsl✕
- Connections
- 1 pair of types, where a type in fault uses a type in dsl.Dsl.
- The types involved
io.parapet.fault.FaultPolicy→io.parapet.dsl.Dsl.FlowOp
- Direction
- fault uses dsl.Dsl, so a change to dsl.Dsl can break fault, while a change to fault can't break dsl.Dsl.
- Position
- Below the diagonal: fault uses a module listed above it, which is the healthy direction.
24→26 fault uses io.parapet part of a loop✕
- Connections
- 1 pair of types, where a type in fault uses a type in io.parapet.
- The types involved
io.parapet.fault.Sent→io.parapet.Event
- Direction
- fault uses io.parapet, so a change to io.parapet can break fault, while a change to fault can't break io.parapet.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
25→22 syntax uses dsl.Dsl✕
- Connections
- 1 pair of types, where a type in syntax uses a type in dsl.Dsl.
- The types involved
io.parapet.syntax.FlowSyntax→io.parapet.dsl.Dsl.WithDsl
- Direction
- syntax uses dsl.Dsl, so a change to dsl.Dsl can break syntax, while a change to syntax can't break dsl.Dsl.
- Position
- Below the diagonal: syntax uses a module listed above it, which is the healthy direction.
26→1 io.parapet uses effect✕
- Connections
- 7 pairs of types, where a type in io.parapet uses a type in effect.
- The types involved
io.parapet.ParApp→io.parapet.effect.Effectio.parapet.ParApp→io.parapet.effect.Parallelio.parapet.ParIOApp→io.parapet.effect.Effectio.parapet.ParIOApp→io.parapet.effect.ParIOio.parapet.ParIOApp→io.parapet.effect.ParIORuntimeio.parapet.ParIOApp→io.parapet.effect.Parallelio.parapet.Process→io.parapet.effect.Effect
- Direction
- io.parapet uses effect, so a change to effect can break io.parapet, while a change to io.parapet can't break effect.
- Position
- Below the diagonal: io.parapet uses a module listed above it, which is the healthy direction.
26→3 io.parapet uses snapshot✕
- Connections
- 2 pairs of types, where a type in io.parapet uses a type in snapshot.
- The types involved
io.parapet.ParApp→io.parapet.snapshot.SnapshotStorageio.parapet.ParConfig→io.parapet.snapshot.SnapshotConfig
- Direction
- io.parapet uses snapshot, so a change to snapshot can break io.parapet, while a change to io.parapet can't break snapshot.
- Position
- Below the diagonal: io.parapet uses a module listed above it, which is the healthy direction.
26→4 io.parapet uses Event✕
- Connections
- 1 pair of types, where a type in io.parapet uses a type in Event.
- The types involved
io.parapet.DeadLetterProcess→io.parapet.Event.DeadLetter
- Direction
- io.parapet uses Event, so a change to Event can break io.parapet, while a change to io.parapet can't break Event.
- Position
- Below the diagonal: io.parapet uses a module listed above it, which is the healthy direction.
26→5 io.parapet uses EventCodec✕
- Connections
- 2 pairs of types, where a type in io.parapet uses a type in EventCodec.
- The types involved
io.parapet.EventCodec→io.parapet.EventCodec.EncodedEventio.parapet.EventCodec→io.parapet.EventCodec.Schema
- Direction
- io.parapet uses EventCodec, so a change to EventCodec can break io.parapet, while a change to io.parapet can't break EventCodec.
- Position
- Below the diagonal: io.parapet uses a module listed above it, which is the healthy direction.
26→13 io.parapet uses runtime.Scheduler✕
- Connections
- 1 pair of types, where a type in io.parapet uses a type in runtime.Scheduler.
- The types involved
io.parapet.ParConfig→io.parapet.runtime.Scheduler.SchedulerConfig
- Direction
- io.parapet uses runtime.Scheduler, so a change to runtime.Scheduler can break io.parapet, while a change to io.parapet can't break runtime.Scheduler.
- Position
- Below the diagonal: io.parapet uses a module listed above it, which is the healthy direction.
26→18 io.parapet uses journal✕
- Connections
- 2 pairs of types, where a type in io.parapet uses a type in journal.
- The types involved
io.parapet.ParApp→io.parapet.journal.JournalStoreio.parapet.ParConfig→io.parapet.journal.JournalConfig
- Direction
- io.parapet uses journal, so a change to journal can break io.parapet, while a change to io.parapet can't break journal.
- Position
- Below the diagonal: io.parapet uses a module listed above it, which is the healthy direction.
26→20 io.parapet uses runtime.DslInterpreter✕
- Connections
- 1 pair of types, where a type in io.parapet uses a type in runtime.DslInterpreter.
- The types involved
io.parapet.ParApp→io.parapet.runtime.DslInterpreter.Interpreter
- Direction
- io.parapet uses runtime.DslInterpreter, so a change to runtime.DslInterpreter can break io.parapet, while a change to io.parapet can't break runtime.DslInterpreter.
- Position
- Below the diagonal: io.parapet uses a module listed above it, which is the healthy direction.
26→21 io.parapet uses runtime✕
- Connections
- 5 pairs of types, where a type in io.parapet uses a type in runtime.
- The types involved
io.parapet.ParApp→io.parapet.runtime.Contextio.parapet.ParApp→io.parapet.runtime.EventTransformerio.parapet.ParApp→io.parapet.runtime.SchedulerRuntimeio.parapet.ParIOApp→io.parapet.runtime.SchedulerRuntimeio.parapet.Process→io.parapet.runtime.Context
- Direction
- io.parapet uses runtime, so a change to runtime can break io.parapet, while a change to io.parapet can't break runtime.
- Position
- Below the diagonal: io.parapet uses a module listed above it, which is the healthy direction.
26→22 io.parapet uses dsl.Dsl✕
- Connections
- 1 pair of types, where a type in io.parapet uses a type in dsl.Dsl.
- The types involved
io.parapet.Process→io.parapet.dsl.Dsl.WithDsl
- Direction
- io.parapet uses dsl.Dsl, so a change to dsl.Dsl can break io.parapet, while a change to io.parapet can't break dsl.Dsl.
- Position
- Below the diagonal: io.parapet uses a module listed above it, which is the healthy direction.
26→24 io.parapet uses fault✕
- Connections
- 1 pair of types, where a type in io.parapet uses a type in fault.
- The types involved
io.parapet.ParApp→io.parapet.fault.FaultPolicy
- Direction
- io.parapet uses fault, so a change to fault can break io.parapet, while a change to io.parapet can't break fault.
- Position
- Below the diagonal: io.parapet uses a module listed above it, which is the healthy direction.
26→25 io.parapet uses syntax✕
- Connections
- 3 pairs of types, where a type in io.parapet uses a type in syntax.
- The types involved
io.parapet.ParApp→io.parapet.syntax.FlowSyntaxio.parapet.Process→io.parapet.syntax.FlowSyntaxio.parapet.implicits→io.parapet.syntax.AllSyntax
- Direction
- io.parapet uses syntax, so a change to syntax can break io.parapet, while a change to io.parapet can't break syntax.
- Position
- Below the diagonal: io.parapet uses a module listed above it, which is the healthy direction.
27→22 fault.FaultPolicy uses dsl.Dsl✕
- Connections
- 1 pair of types, where a type in fault.FaultPolicy uses a type in dsl.Dsl.
- The types involved
io.parapet.fault.FaultPolicy.Builder→io.parapet.dsl.Dsl.FlowOp
- Direction
- fault.FaultPolicy uses dsl.Dsl, so a change to dsl.Dsl can break fault.FaultPolicy, while a change to fault.FaultPolicy can't break dsl.Dsl.
- Position
- Below the diagonal: fault.FaultPolicy uses a module listed above it, which is the healthy direction.
27→24 fault.FaultPolicy uses fault✕
- Connections
- 3 pairs of types, where a type in fault.FaultPolicy uses a type in fault.
- The types involved
io.parapet.fault.FaultPolicy.Builder→io.parapet.fault.Faultio.parapet.fault.FaultPolicy.Builder→io.parapet.fault.FaultPolicyio.parapet.fault.FaultPolicy.Builder→io.parapet.fault.Sent
- Direction
- fault.FaultPolicy uses fault, so a change to fault can break fault.FaultPolicy, while a change to fault.FaultPolicy can't break fault.
- Position
- Below the diagonal: fault.FaultPolicy uses a module listed above it, which is the healthy direction.
28→1 Channel uses effect✕
- Connections
- 2 pairs of types, where a type in Channel uses a type in effect.
- The types involved
io.parapet.Channel.InFlight→io.parapet.effect.Deferredio.parapet.Channel.Request→io.parapet.effect.Deferred
- Direction
- Channel uses effect, so a change to effect can break Channel, while a change to Channel can't break effect.
- Position
- Below the diagonal: Channel uses a module listed above it, which is the healthy direction.
28→26 Channel uses io.parapet✕
- Connections
- 2 pairs of types, where a type in Channel uses a type in io.parapet.
- The types involved
io.parapet.Channel.Request→io.parapet.Eventio.parapet.Channel.Timeout→io.parapet.Event
- Direction
- Channel uses io.parapet, so a change to io.parapet can break Channel, while a change to Channel can't break io.parapet.
- Position
- Below the diagonal: Channel uses a module listed above it, which is the healthy direction.
29→26 DeadLetterProcess uses io.parapet✕
- Connections
- 1 pair of types, where a type in DeadLetterProcess uses a type in io.parapet.
- The types involved
io.parapet.DeadLetterProcess.DeadLetterLoggingProcess→io.parapet.DeadLetterProcess
- Direction
- DeadLetterProcess uses io.parapet, so a change to io.parapet can break DeadLetterProcess, while a change to DeadLetterProcess can't break io.parapet.
- Position
- Below the diagonal: DeadLetterProcess uses a module listed above it, which is the healthy direction.
30→26 EventCodecAvailability uses io.parapet✕
- Connections
- 4 pairs of types, where a type in EventCodecAvailability uses a type in io.parapet.
- The types involved
io.parapet.EventCodecAvailability.Available→io.parapet.EventCodecio.parapet.EventCodecAvailability.Available→io.parapet.EventCodecAvailabilityio.parapet.EventCodecAvailability.Missing→io.parapet.EventCodecio.parapet.EventCodecAvailability.Missing→io.parapet.EventCodecAvailability
- Direction
- EventCodecAvailability uses io.parapet, so a change to io.parapet can break EventCodecAvailability, while a change to EventCodecAvailability can't break io.parapet.
- Position
- Below the diagonal: EventCodecAvailability uses a module listed above it, which is the healthy direction.
31→26 Process uses io.parapet✕
- Connections
- 3 pairs of types, where a type in Process uses a type in io.parapet.
- The types involved
io.parapet.Process.AskOps→io.parapet.ProcessRefio.parapet.Process.Builder→io.parapet.Processio.parapet.Process.Builder→io.parapet.ProcessRef
- Direction
- Process uses io.parapet, so a change to io.parapet can break Process, while a change to Process can't break io.parapet.
- Position
- Below the diagonal: Process uses a module listed above it, which is the healthy direction.
32→1 cats uses effect✕
- Connections
- 3 pairs of types, where a type in cats uses a type in effect.
- The types involved
io.parapet.cats.CatsEffectParApp→io.parapet.effect.Effectio.parapet.cats.CatsEffectParApp→io.parapet.effect.Parallelio.parapet.cats.CatsEffectParapetRuntime→io.parapet.effect.EffectFiber
- Direction
- cats uses effect, so a change to effect can break cats, while a change to cats can't break effect.
- Position
- Below the diagonal: cats uses a module listed above it, which is the healthy direction.
32→21 cats uses runtime✕
- Connections
- 1 pair of types, where a type in cats uses a type in runtime.
- The types involved
io.parapet.cats.CatsEffectParApp→io.parapet.runtime.SchedulerRuntime
- Direction
- cats uses runtime, so a change to runtime can break cats, while a change to cats can't break runtime.
- Position
- Below the diagonal: cats uses a module listed above it, which is the healthy direction.
32→26 cats uses io.parapet✕
- Connections
- 1 pair of types, where a type in cats uses a type in io.parapet.
- The types involved
io.parapet.cats.CatsEffectParApp→io.parapet.ParApp
- Direction
- cats uses io.parapet, so a change to io.parapet can break cats, while a change to cats can't break io.parapet.
- Position
- Below the diagonal: cats uses a module listed above it, which is the healthy direction.
33→6 dsl.Dsl.FlowOps uses dsl✕
- Connections
- 1 pair of types, where a type in dsl.Dsl.FlowOps uses a type in dsl.
- The types involved
io.parapet.dsl.Dsl.FlowOps.unsafe→io.parapet.dsl.Free
- Direction
- dsl.Dsl.FlowOps uses dsl, so a change to dsl can break dsl.Dsl.FlowOps, while a change to dsl.Dsl.FlowOps can't break dsl.
- Position
- Below the diagonal: dsl.Dsl.FlowOps uses a module listed above it, which is the healthy direction.
33→26 dsl.Dsl.FlowOps uses io.parapet✕
- Connections
- 1 pair of types, where a type in dsl.Dsl.FlowOps uses a type in io.parapet.
- The types involved
io.parapet.dsl.Dsl.FlowOps.unsafe→io.parapet.ProcessRef
- Direction
- dsl.Dsl.FlowOps uses io.parapet, so a change to io.parapet can break dsl.Dsl.FlowOps, while a change to dsl.Dsl.FlowOps can't break io.parapet.
- Position
- Below the diagonal: dsl.Dsl.FlowOps uses a module listed above it, which is the healthy direction.
34→2 net.processes.ClientProcess uses net.transport✕
- Connections
- 1 pair of types, where a type in net.processes.ClientProcess uses a type in net.transport.
- The types involved
io.parapet.net.processes.ClientProcess.Failed→io.parapet.net.transport.TransportError
- Direction
- net.processes.ClientProcess uses net.transport, so a change to net.transport can break net.processes.ClientProcess, while a change to net.processes.ClientProcess can't break net.transport.
- Position
- Below the diagonal: net.processes.ClientProcess uses a module listed above it, which is the healthy direction.
34→26 net.processes.ClientProcess uses io.parapet✕
- Connections
- 3 pairs of types, where a type in net.processes.ClientProcess uses a type in io.parapet.
- The types involved
io.parapet.net.processes.ClientProcess.Failed→io.parapet.Eventio.parapet.net.processes.ClientProcess.Request→io.parapet.Eventio.parapet.net.processes.ClientProcess.Response→io.parapet.Event
- Direction
- net.processes.ClientProcess uses io.parapet, so a change to io.parapet can break net.processes.ClientProcess, while a change to net.processes.ClientProcess can't break io.parapet.
- Position
- Below the diagonal: net.processes.ClientProcess uses a module listed above it, which is the healthy direction.
35→2 net.processes.DatagramProcess uses net.transport✕
- Connections
- 1 pair of types, where a type in net.processes.DatagramProcess uses a type in net.transport.
- The types involved
io.parapet.net.processes.DatagramProcess.Failed→io.parapet.net.transport.TransportError
- Direction
- net.processes.DatagramProcess uses net.transport, so a change to net.transport can break net.processes.DatagramProcess, while a change to net.processes.DatagramProcess can't break net.transport.
- Position
- Below the diagonal: net.processes.DatagramProcess uses a module listed above it, which is the healthy direction.
35→26 net.processes.DatagramProcess uses io.parapet✕
- Connections
- 3 pairs of types, where a type in net.processes.DatagramProcess uses a type in io.parapet.
- The types involved
io.parapet.net.processes.DatagramProcess.Failed→io.parapet.Eventio.parapet.net.processes.DatagramProcess.Publish→io.parapet.Eventio.parapet.net.processes.DatagramProcess.Received→io.parapet.Event
- Direction
- net.processes.DatagramProcess uses io.parapet, so a change to io.parapet can break net.processes.DatagramProcess, while a change to net.processes.DatagramProcess can't break io.parapet.
- Position
- Below the diagonal: net.processes.DatagramProcess uses a module listed above it, which is the healthy direction.
36→2 net.processes.DuplexProcess uses net.transport✕
- Connections
- 1 pair of types, where a type in net.processes.DuplexProcess uses a type in net.transport.
- The types involved
io.parapet.net.processes.DuplexProcess.Failed→io.parapet.net.transport.TransportError
- Direction
- net.processes.DuplexProcess uses net.transport, so a change to net.transport can break net.processes.DuplexProcess, while a change to net.processes.DuplexProcess can't break net.transport.
- Position
- Below the diagonal: net.processes.DuplexProcess uses a module listed above it, which is the healthy direction.
36→26 net.processes.DuplexProcess uses io.parapet✕
- Connections
- 3 pairs of types, where a type in net.processes.DuplexProcess uses a type in io.parapet.
- The types involved
io.parapet.net.processes.DuplexProcess.Failed→io.parapet.Eventio.parapet.net.processes.DuplexProcess.Request→io.parapet.Eventio.parapet.net.processes.DuplexProcess.Response→io.parapet.Event
- Direction
- net.processes.DuplexProcess uses io.parapet, so a change to io.parapet can break net.processes.DuplexProcess, while a change to net.processes.DuplexProcess can't break io.parapet.
- Position
- Below the diagonal: net.processes.DuplexProcess uses a module listed above it, which is the healthy direction.
37→2 net.processes.ServerProcess uses net.transport✕
- Connections
- 1 pair of types, where a type in net.processes.ServerProcess uses a type in net.transport.
- The types involved
io.parapet.net.processes.ServerProcess.Failed→io.parapet.net.transport.TransportError
- Direction
- net.processes.ServerProcess uses net.transport, so a change to net.transport can break net.processes.ServerProcess, while a change to net.processes.ServerProcess can't break net.transport.
- Position
- Below the diagonal: net.processes.ServerProcess uses a module listed above it, which is the healthy direction.
37→26 net.processes.ServerProcess uses io.parapet✕
- Connections
- 3 pairs of types, where a type in net.processes.ServerProcess uses a type in io.parapet.
- The types involved
io.parapet.net.processes.ServerProcess.Failed→io.parapet.Eventio.parapet.net.processes.ServerProcess.Received→io.parapet.Eventio.parapet.net.processes.ServerProcess.Reply→io.parapet.Event
- Direction
- net.processes.ServerProcess uses io.parapet, so a change to io.parapet can break net.processes.ServerProcess, while a change to net.processes.ServerProcess can't break io.parapet.
- Position
- Below the diagonal: net.processes.ServerProcess uses a module listed above it, which is the healthy direction.
38→1 runtime.Scheduler.SchedulerImpl uses effect✕
- Connections
- 3 pairs of types, where a type in runtime.Scheduler.SchedulerImpl uses a type in effect.
- The types involved
io.parapet.runtime.Scheduler.SchedulerImpl.Worker→io.parapet.effect.Effectio.parapet.runtime.Scheduler.SchedulerImpl.Worker→io.parapet.effect.Parallelio.parapet.runtime.Scheduler.SchedulerImpl.Worker→io.parapet.effect.Queue
- Direction
- runtime.Scheduler.SchedulerImpl uses effect, so a change to effect can break runtime.Scheduler.SchedulerImpl, while a change to runtime.Scheduler.SchedulerImpl can't break effect.
- Position
- Below the diagonal: runtime.Scheduler.SchedulerImpl uses a module listed above it, which is the healthy direction.
38→13 runtime.Scheduler.SchedulerImpl uses runtime.Scheduler✕
- Connections
- 2 pairs of types, where a type in runtime.Scheduler.SchedulerImpl uses a type in runtime.Scheduler.
- The types involved
io.parapet.runtime.Scheduler.SchedulerImpl.Worker→io.parapet.runtime.Scheduler.Deliverio.parapet.runtime.Scheduler.SchedulerImpl.Worker→io.parapet.runtime.Scheduler.Signal
- Direction
- runtime.Scheduler.SchedulerImpl uses runtime.Scheduler, so a change to runtime.Scheduler can break runtime.Scheduler.SchedulerImpl, while a change to runtime.Scheduler.SchedulerImpl can't break runtime.Scheduler.
- Position
- Below the diagonal: runtime.Scheduler.SchedulerImpl uses a module listed above it, which is the healthy direction.
38→19 runtime.Scheduler.SchedulerImpl uses runtime.Context✕
- Connections
- 1 pair of types, where a type in runtime.Scheduler.SchedulerImpl uses a type in runtime.Context.
- The types involved
io.parapet.runtime.Scheduler.SchedulerImpl.Worker→io.parapet.runtime.Context.ProcessState
- Direction
- runtime.Scheduler.SchedulerImpl uses runtime.Context, so a change to runtime.Context can break runtime.Scheduler.SchedulerImpl, while a change to runtime.Scheduler.SchedulerImpl can't break runtime.Context.
- Position
- Below the diagonal: runtime.Scheduler.SchedulerImpl uses a module listed above it, which is the healthy direction.
38→20 runtime.Scheduler.SchedulerImpl uses runtime.DslInterpreter✕
- Connections
- 1 pair of types, where a type in runtime.Scheduler.SchedulerImpl uses a type in runtime.DslInterpreter.
- The types involved
io.parapet.runtime.Scheduler.SchedulerImpl.Worker→io.parapet.runtime.DslInterpreter.Interpreter
- Direction
- runtime.Scheduler.SchedulerImpl uses runtime.DslInterpreter, so a change to runtime.DslInterpreter can break runtime.Scheduler.SchedulerImpl, while a change to runtime.Scheduler.SchedulerImpl can't break runtime.DslInterpreter.
- Position
- Below the diagonal: runtime.Scheduler.SchedulerImpl uses a module listed above it, which is the healthy direction.
38→21 runtime.Scheduler.SchedulerImpl uses runtime✕
- Connections
- 2 pairs of types, where a type in runtime.Scheduler.SchedulerImpl uses a type in runtime.
- The types involved
io.parapet.runtime.Scheduler.SchedulerImpl.Worker→io.parapet.runtime.Contextio.parapet.runtime.Scheduler.SchedulerImpl.Worker→io.parapet.runtime.Envelope
- Direction
- runtime.Scheduler.SchedulerImpl uses runtime, so a change to runtime can break runtime.Scheduler.SchedulerImpl, while a change to runtime.Scheduler.SchedulerImpl can't break runtime.
- Position
- Below the diagonal: runtime.Scheduler.SchedulerImpl uses a module listed above it, which is the healthy direction.
38→26 runtime.Scheduler.SchedulerImpl uses io.parapet✕
- Connections
- 2 pairs of types, where a type in runtime.Scheduler.SchedulerImpl uses a type in io.parapet.
- The types involved
io.parapet.runtime.Scheduler.SchedulerImpl.Worker→io.parapet.Eventio.parapet.runtime.Scheduler.SchedulerImpl.Worker→io.parapet.EventCodec
- Direction
- runtime.Scheduler.SchedulerImpl uses io.parapet, so a change to io.parapet can break runtime.Scheduler.SchedulerImpl, while a change to runtime.Scheduler.SchedulerImpl can't break io.parapet.
- Position
- Below the diagonal: runtime.Scheduler.SchedulerImpl uses a module listed above it, which is the healthy direction.
39→1 testutils uses effect✕
- Connections
- 1 pair of types, where a type in testutils uses a type in effect.
- The types involved
io.parapet.testutils.EventStore→io.parapet.effect.EffectFiber
- Direction
- testutils uses effect, so a change to effect can break testutils, while a change to testutils can't break effect.
- Position
- Below the diagonal: testutils uses a module listed above it, which is the healthy direction.
39→26 testutils uses io.parapet✕
- Connections
- 1 pair of types, where a type in testutils uses a type in io.parapet.
- The types involved
io.parapet.testutils.EventStore→io.parapet.ProcessRef
- Direction
- testutils uses io.parapet, so a change to io.parapet can break testutils, while a change to testutils can't break io.parapet.
- Position
- Below the diagonal: testutils uses a module listed above it, which is the healthy direction.
40→2 net.processes uses net.transport✕
- Connections
- 2 pairs of types, where a type in net.processes uses a type in net.transport.
- The types involved
io.parapet.net.processes.DuplexProcess→io.parapet.net.transport.Messageio.parapet.net.processes.DuplexProcess→io.parapet.net.transport.TransportError
- Direction
- net.processes uses net.transport, so a change to net.transport can break net.processes, while a change to net.processes can't break net.transport.
- Position
- Below the diagonal: net.processes uses a module listed above it, which is the healthy direction.
40→26 net.processes uses io.parapet✕
- Connections
- 8 pairs of types, where a type in net.processes uses a type in io.parapet.
- The types involved
io.parapet.net.processes.ClientProcess→io.parapet.Processio.parapet.net.processes.ClientProcess→io.parapet.ProcessRefio.parapet.net.processes.DatagramProcess→io.parapet.Processio.parapet.net.processes.DatagramProcess→io.parapet.ProcessRefio.parapet.net.processes.DuplexProcess→io.parapet.Processio.parapet.net.processes.DuplexProcess→io.parapet.ProcessRefio.parapet.net.processes.ServerProcess→io.parapet.Processio.parapet.net.processes.ServerProcess→io.parapet.ProcessRef
- Direction
- net.processes uses io.parapet, so a change to io.parapet can break net.processes, while a change to net.processes can't break io.parapet.
- Position
- Below the diagonal: net.processes uses a module listed above it, which is the healthy direction.
40→36 net.processes uses net.processes.DuplexProcess✕
- Connections
- 1 pair of types, where a type in net.processes uses a type in net.processes.DuplexProcess.
- The types involved
io.parapet.net.processes.DuplexProcess→io.parapet.net.processes.DuplexProcess.Request
- Direction
- net.processes uses net.processes.DuplexProcess, so a change to net.processes.DuplexProcess can break net.processes, while a change to net.processes can't break net.processes.DuplexProcess.
- Position
- Below the diagonal: net.processes uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A05:2025 — Injection | 10 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 4 | Medium |
Roadmap
Top priorities: On Scala 3, add `-Yexplicit-nulls` to `scalacOptions` so `String` and `String | Null` mean different things, and type each Java API's result as nullable where it can return null; on Scala 2 (or as a first step), enable WartRemover's `Null` wart (`wartremoverErrors += Wart.Null`) or Scalafix's `DisableSyntax.noNulls = true` so the code holds absence in `Option`. Then pay the assertions down rather than adding to them: each `.nn` is a null the compiler could not rule out — wrap the Java value in `Option(…)` at the boundary, pattern-match on `null` once there, or change the API so the null cannot arrive; an `unsafeNulls` import switches the checking off for everything after it; Interpolated log message defeats structured logging; Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| On Scala 3, add `-Yexplicit-nulls` to `scalacOptions` so `String` and `String | Null` mean different things, and type each Java API's result as nullable where it can return null; on Scala 2 (or as a first step), enable WartRemover's `Null` wart (`wartremoverErrors += Wart.Null`) or Scalafix's `DisableSyntax.noNulls = true` so the code holds absence in `Option`. Then pay the assertions down rather than adding to them: each `.nn` is a null the compiler could not rule out — wrap the Java value in `Option(…)` at the boundary, pattern-match on `null` once there, or change the API so the null cannot arrive; an `unsafeNulls` import switches the checking off for everything after it. | +4.0 pts | Medium | Nullable reference types |
| Interpolated log message defeats structured logging | +3.9 pts | Medium | Structured logging |
| Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release. | +2.8 pts | Medium | Release Hygiene |
| 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. | +1.7 pts | Medium | Architecture documentation |
| Bring the 2 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with ParIORuntime.unsafeRunLoop (cyclomatic 45), Impl.interpret (cyclomatic 36). | +0.8 pts | Medium | Cyclomatic Complexity |
| 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. | +1.2 pts | Medium | Documentation (README) |
| Bring the 7 bodies over 15 down to 15 or less in Cognitive Complexity — start with ParApp.run (cognitive 49), ParIORuntime.unsafeRunLoop (cognitive 46), Worker.deliver (cognitive 36). | +1.1 pts | High | Cognitive Complexity |
| Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion. | +0.4 pts | Low | Project Cohesion |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 2.7 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.5 | Mixed | Static Analysis (SAST): High: REDACTED |
| parapet-core/src/main/scala/io/parapet/runtime/DslInterpreter.scala | 6.0 | Mixed | Explicit Debt: FixmeComment |
| parapet-testkit/src/main/scala/io/parapet/tests/intg/ProcessLifecycleSpec.scala | 6.9 | Mixed | Explicit Debt: TodoComment |
| parapet-pario/src/main/scala/io/parapet/effect/ParIORuntime.scala | 7.2 | Near-clean | Cyclomatic Complexity: ParIORuntime.unsafeRunLoop (cyclomatic 45) |
| parapet-core/src/main/scala/io/parapet/journal/DeliveryLog.scala | 7.4 | Near-clean | Cognitive Complexity: DeliveryLog.scanSegment (cognitive 26) |
| parapet-core/src/main/scala/io/parapet/runtime/Scheduler.scala | 7.8 | Near-clean | Cognitive Complexity: Worker.deliver (cognitive 36) |
| parapet-testkit/src/main/scala/io/parapet/tests/intg/DslSpec.scala | 8.2 | Near-clean | Explicit Debt: TodoComment |
| parapet-testkit/src/main/scala/io/parapet/tests/intg/scheduler/SchedulerSpec.scala | 8.2 | Near-clean | Explicit Debt: TodoComment |
| parapet-core/src/main/scala/io/parapet/ParApp.scala | 8.5 | Near-clean | Cognitive Complexity: ParApp.run (cognitive 49) |
| parapet-core/src/main/scala/io/parapet/Channel.scala | 8.5 | Near-clean | Cognitive Complexity: Channel.waitForResponse (cognitive 17) |
| parapet-core/src/main/scala/io/parapet/runtime/Context.scala | 8.5 | Near-clean | God Classes: TooManyMethods: Context |
| parapet-core/src/main/scala/io/parapet/journal/Recorder.scala | 8.5 | Near-clean | Code Duplication: Duplicated block (9 lines × 2) |
| parapet-cats-effect/src/main/scala/io/parapet/cats/CatsEffectParapetRuntime.scala | 8.5 | Near-clean | Code Duplication: Duplicated block (8 lines × 2) |
| parapet-core/src/main/scala/io/parapet/journal/JournalEntryBinaryFormat.scala | 8.5 | Near-clean | Code Duplication: Duplicated block (5 lines × 2) |
| parapet-net/src/main/scala/io/parapet/net/transport/zmq/ZmqTcpClient.scala | 8.5 | Near-clean | Code Duplication: Duplicated block (6 lines × 2) |
How the grades work
A definite problem that already costs you something and drags the score down: a missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here tends to cause failures elsewhere.
Likely wrong, but not failing yet. It degrades the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to carry for two years either.
Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.
Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.
Methodology & how to trust this report
This survey is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. All 59 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.8, the weighted average across measured dimensions.
What we checked — 59 dimensions across the health lenses
- Can you open the finding? Real findings cite a repo-relative file and line you can open at the cited line — never an absolute scratch path. Here, 46 of 54 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Canine Code Analyzer duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 | ✓ deterministic |
Run transparency — what happened this run
- D8 Code Coverage — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: test source is present (.scala) but the built-in coverage collector has no runner for this repository's ecosystem — so this suite was never executed by it. Not scored — this is a gap in the analyzer's language coverage, not a defect in the repo. To have real coverage read, produce a coverage report in a standard format (`addSbtPlugin("org.scoverage" % "sbt-scoverage" % "<version>")` in `project/plugins.sbt`, then `sbt clean coverage test coverageReport`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures. You can widen what we reach: optional: produce a coverage report in a standard format (`addSbtPlugin("org.scoverage" % "sbt-scoverage" % "<version>")` in `project/plugins.sbt`, then `sbt clean coverage test coverageReport`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures — then the real number is read on the next scan.
- D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test source is present (.scala) and this repository declares an sbt build (repository root, 54 test files), but it was not re-run: the analyzer environment could not run it. Not scored — this is a gap in the analyzer's language coverage, not a finding about this repository.
- D12 Dependency Hygiene — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This repository's dependency manifests WERE read and their pinning discipline assessed; what went unanswered is the currency half, because repo1.maven.org — the registry that answers it — was asked and did not reply (HTTP 429 Too Many Requests from http://172.31.7.1:8790/maven/com/lihaoyi/sourcecode_3/maven-metadata.xml). This is OUR side and it is an ENVIRONMENT fault, not a missing collector: the collector exists and ran. An HTTP 403 here is what this scan's egress allowlist returns for a host that is not on it, so the remedy is to add repo1.maven.org to the allowlist and re-run — not to build anything.
- D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Single-maintainer repository — bus factor is not applicable (5 contributor(s) across 373 commit(s) sampled, automation and bot accounts excluded). One of them holds 89% of the history; the other 4 hold 2.8% each on average, below the 5% at which there is somebody to hand the work to. That is a single maintainer with drive-by contributors, not a team whose knowledge has concentrated — so the bus factor is not applicable and there is nothing here for the owner to act on.
- D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D21's deterministic naming rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. Until then its declarations carry no naming verdict this run — this says nothing about whether its names are consistent.
- D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22 identifies the intentionally-exposed surface from `IsPackable` and `.Contracts` project names, MSBuild conventions read off the loaded project set. This target exposed no such projects, so the probe never ran; this says nothing about whether the repository has a public API. This repository commits no C#/VB source at all, so there was never an MSBuild project set to read these conventions off. That is OUR side and it is an ADMISSION gap, not an environment fault: it declares a published package (project/plugins.sbt), but no published-package marker D22 reads admitted any project here. D22 DOES collect the public API of every language in this tree, and admits a project only when its manifest makes that ecosystem's publication act in a form the marker recognises — so what is missing is not a collector but an admission rule for the publication act this repository makes, if it makes one. The remedy is a better discriminator for that marker — not a collector, and no change to the scan image can close it. The marker's rules are measured to refuse applications, so one refused repository is the rule working as calibrated; several are the evidence that it is too strict.
- D24 Comment Value — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
- D27 Navigability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Navigability is taken over call sites whose callee resolved. For C# that population includes calls into referenced assemblies; for this language only calls declared inside the repository count, so the abstention threshold reads the repository's use of its standard library as a resolution failure. That is a limit of this analyzer, not a build problem in this repository.
- D32 Data Compliance (PII/GDPR) — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `parapet-core/src/main/scala/io/parapet/Process.scala`, `parapet-core/src/main/scala/io/parapet/fault/FaultInjector.scala`, `parapet-core/src/main/scala/io/parapet/journal/DeliveryLog.scala`, `parapet-core/src/main/scala/io/parapet/runtime/Scheduler.scala`, `parapet-core/src/main/scala/io/parapet/syntax/LoggerSyntax.scala`, … (+3 more) produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
- C1 Data Protection — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These personal data controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks personal data controls.
- C2 Access Controls — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These authorization controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks authorization controls.
- P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
- D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
- D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- 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.
- P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
- P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
Dimensions
D1 · Cyclomatic Complexity
2 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was ParIORuntime.unsafeRunLoop at 45.
What to do
- Bring the 2 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with ParIORuntime.unsafeRunLoop (cyclomatic 45), Impl.interpret (cyclomatic 36). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 2 together lifts Cyclomatic Complexity from 8.7 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
- Enforce Cyclomatic Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D2 · Cognitive Complexity
7 method(s) exceeded the cognitive complexity threshold of 15; the worst was ParApp.run at 49.
What to do
- Bring the 7 bodies over 15 down to 15 or less in Cognitive Complexity — start with ParApp.run (cognitive 49), ParIORuntime.unsafeRunLoop (cognitive 46), Worker.deliver (cognitive 36). — 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 7 together lifts Cognitive Complexity from 8.2 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
- Enforce Cognitive Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D3 · God Classes
5 god class(es) detected.
What to do
- Resolve the 3 FileTooLong finding(s) in God Classes — start with DeliveryLog.scala, Scheduler.scala, ParIORuntime.scala. — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 2 TooManyMethods finding(s) in God Classes — start with DeliveryLog.scala, Context.scala. — One of this dimension's main actionable groups (2 warning-level).
- Enforce God Classes in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D4 · Code Duplication
4 duplicated block group(s) detected.
What to do
- Resolve the 1 Duplicated block (9 lines × 2) finding(s) in Code Duplication — start with Recorder.scala. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Duplicated block (8 lines × 2) finding(s) in Code Duplication — start with CatsEffectParapetRuntime.scala. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Duplicated block (5 lines × 2) finding(s) in Code Duplication — start with JournalEntryBinaryFormat.scala. — One of this dimension's main actionable groups (1 warning-level).
- Enforce Code Duplication in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D5 · Coupling
6 production modules (sbt), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; a dependsOn spread (deps: _*) and a project whose directory a helper computes are not visible there; 1 module(s) off the main sequence, with abstractness counted on 5 of the 6 (the rest declare no modelled class or interface, export only macros, declare types in source no model reads, or have no source directory of their own).
What to do
- Resolve the 1 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (1 warning-level).
- Enforce Coupling in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D6 · Cohesion (LCOM4)
0 of 24 classes have LCOM4 above 3.
D9 · Test Distribution
228 test methods: 217 unit, 11 integration, 0 BDD, 0 e2e. The Scala suite contributes 228 test case(s) across 32 file(s) in a test source set declaring at least one — every `test("…")`, `it("…")`, `property("…")` and `"…" in {…}` registration and every JUnit `@Test`, which is how munit, ScalaTest, utest, ZIO Test and specs2 declare a case; a case registered under a computed name is not counted, so this is a floor. Its tier split is INFERRED from paths and file names, except sbt's src/it source set, which the build declares.
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D15 · Churn × Complexity Hotspots
Top hotspots: parapet-core/src/main/scala/io/parapet/runtime/DslInterpreter.scala (7×36=252); parapet-pario/src/main/scala/io/parapet/effect/ParIORuntime.scala (4×45=180); parapet-core/src/main/scala/io/parapet/runtime/Scheduler.scala (11×15=165)
What to do
- Resolve the 3 Hotspot finding(s) in Churn × Complexity Hotspots — start with DslInterpreter.scala, ParIORuntime.scala, Scheduler.scala. — One of this dimension's main actionable groups (3 warning-level).
D17 · Explicit Debt
6 deducted task-comment markers across 7871 LoC (0.1/KLoC) → score 9.9. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
What to do
- Resolve the 5 TodoComment finding(s) in Explicit Debt — start with ProcessLifecycleSpec.scala (3), DslSpec.scala, SchedulerSpec.scala. — One of this dimension's main actionable groups (5 warning-level).
- Resolve the 1 FixmeComment finding(s) in Explicit Debt — start with DslInterpreter.scala. — One of this dimension's main actionable groups (1 warning-level).
- Enforce Explicit Debt in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D26 · Project Cohesion
1 of 1 build units (sbt) flagged as possibly oversized/incoherent.
What to do
- Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion. — One of this dimension's main actionable groups (1 recommendation-level).
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
10 finding(s): 0 critical, 10 high, 0 medium, 0 low. 10 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. semgrep hit a parse error in 5 file(s) — `parapet-core/src/main/scala/io/parapet/Process.scala`, `parapet-core/src/main/scala/io/parapet/fault/FaultInjector.scala`, `parapet-core/src/main/scala/io/parapet/journal/DeliveryLog.scala`, `parapet-core/src/main/scala/io/parapet/runtime/Scheduler.scala`, `parapet-pario/src/main/scala/io/parapet/effect/ParIORuntime.scala` — so no absence of findings in them is evidence of anything, and nothing in them was analysed. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them.
What to do
- No action in Static Analysis (SAST) — all 10 REDACTED finding(s) are reported here at file:line but scored by D36 (supply-chain provenance), so none is charged to this dimension. — One of this dimension's main actionable groups (10 issue-level, 0 of them charged here).
D30 · Dependency Vulnerabilities
No known-vulnerable dependencies in any ecosystem this repository declares.
D34 · Knowledge Freshness
Every significant source file has living knowledge — recently and meaningfully worked. Counted over 37 of the 97 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
D35 · Change Coupling
No strong hidden change-coupling between production files.
D36 · Supply-chain Provenance & Signing
1/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).
What to do
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
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
What to do
- The domain core is a small share of production code, but most of the rest matched no layer vocabulary at all — so this is not yet an anemic-domain finding. The namespace/path convention could not place that code, which makes the composition above a statement about the naming, not about the design. Name the layers (or check that the repository's conventions differ from the ones this check knows) before reading a thin domain into it.
AX3 · Project dependency cycles
AX4 · Dependency direction
AX6 · Interface segregation
AX8 · Test isolation
GD1 · Unfinished & placeholder code
IC1 · Incompleteness & stubs
- A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something. (×3) — parapet-pario/src/test/scala/io/parapet/tests/intg/pario/ParIOSpecs.scala:25, parapet-pario/src/test/scala/io/parapet/tests/intg/pario/ParIOSpecs.scala:90, parapet-testkit/src/main/scala/io/parapet/tests/intg/scheduler/SchedulerSpec.scala:78
What to do
- Clear the softer debt: re-enable or delete `ignore`d and `pending` tests, decide whether each empty method or UnsupportedOperationException is deliberate (and say so in a comment), and replace a bare `// scalastyle:off` or `@nowarn` with targeted, justified suppressions.
M1 · Documentation (README)
What to do
- Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
- Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
M3 · Folder & project structure
P1 · CI/CD gates
P10 · Library API & versioning
P2 · Observability
P3 · Security & performance tooling
- No static application security testing detected. For this repository's stack, add scalafix or scapegoat (or `semgrep --config=auto`, which runs on any language) as a CI step. What was searched, so you can tell an absence from a miss: the 3999 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner. — REDACTED:6
What to do
- Add a SAST step to CI running what this repository's stack ships: scalafix or scapegoat — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
P6 · Release Hygiene
- No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
What to do
- Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.
PF3 · Async & latency hygiene
X1 · Async correctness
X12 · Unreachable branch
X13 · Undrained process stream
X14 · Bypassable address classification
X15 · Unvalidated length from an untrusted reader
X16 · Unfloored truncation loop
X17 · Uncapped recursion over a caller-supplied document
X18 · Disposal-pattern correctness
X19 · Unrestored process-global state
X20 · Mistyped argument guard
X21 · Side-effecting pattern guard
X22 · Contradicted release guard
X23 · Unguarded diagnostic materialisation
X24 · Document value interpolated into markup unescaped
X25 · Inert configuration knob
X26 · Unsynchronised callback handoff
X27 · Collection changed while being enumerated
X28 · Index access outside its own emptiness guard
X29 · Per-element action decided by a fixed element
X3 · Exception handling
X30 · Support guard that admits what it rejects
X4 · Structured logging
- `debug` at line 29 is handed an interpolated string as its message through SLF4J, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix. — parapet-core/src/main/scala/io/parapet/snapshot/SnapshotStorageLocal.scala:29
- `warn` at line 130 is handed an interpolated string as its message through SLF4J, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.warn("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix. — parapet-core/src/main/scala/io/parapet/runtime/Recovery.scala:130
- `debug` at line 24 is handed an interpolated string as its message through SLF4J, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix. — parapet-core/src/main/scala/io/parapet/journal/JournalStoreLocal.scala:24
What to do
- Interpolated log message defeats structured logging
X5 · Nullable reference types
- No build over this repository's 103 Scala product file(s) passes `-Yexplicit-nulls`, enables WartRemover's `Null` wart or runs Scalafix's `DisableSyntax.noNulls`, so every reference type admits null and nothing reports a `null` written into the code or returned from a Java API — the first one to reach a method call is a `NullPointerException`. `Option` by convention is a habit no tool here holds the code to.
What to do
- On Scala 3, add `-Yexplicit-nulls` to `scalacOptions` so `String` and `String | Null` mean different things, and type each Java API's result as nullable where it can return null; on Scala 2 (or as a first step), enable WartRemover's `Null` wart (`wartremoverErrors += Wart.Null`) or Scalafix's `DisableSyntax.noNulls = true` so the code holds absence in `Option`. Then pay the assertions down rather than adding to them: each `.nn` is a null the compiler could not rule out — wrap the Java value in `Option(…)` at the boundary, pattern-match on `null` once there, or change the API so the null cannot arrive; an `unsafeNulls` import switches the checking off for everything after it.
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 58% | Adequate — gated by X4, X5 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 91% | Adequate — gated by D26 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Maturity | 72% | Strong | Solid. |
| Readiness | 54% | Adequate — gated by P3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 81% | Adequate — gated by D36 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Performance | 100% | Exemplary | Strongest area. |
Unscored — 1 check(s) recorded observations but carry no score
- X10 Duplicated predicate — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 1 control(s) we could not find positive evidence for
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 58 check(s) not relevant to this codebase
- AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
- AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
- AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
- AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
- AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
- AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
- AC7 A11y enforcement — No web markup found — accessibility is not applicable to this repository.
- AX1 Captive dependencies — Not applicable: this repository's Scala imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's.
- AX2 Stateful singletons — No container singleton was found, so there is no shared instance for concurrent requests to race on. No class in this Scala code is a Play controller, a Cask routes object, a Scalatra servlet, a Finatra controller, an Akka/Pekko HTTP routes holder or a JSR-330/Spring singleton, so no instance is shared 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
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
- AXB1 Runtime evidence locked — no reproducible boot — This repository has nothing the runtime tiers could boot or serve — no markup, no UI framework or web-server dependency, no UI component source, no native UI project and no API definition — nothing here is a surface to boot — so runtime a11y/egress/header evidence has no subject here. Not applicable: this is neither a gap in the scan nor a finding about your code.
- C1 Data Protection — Not assessed: these personal data controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks personal data controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- C2 Access Controls — Not assessed: these authorization controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks authorization controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- C3 Audit Trail — No personal data detected in a persisted data model — no PII-named column (email, first_name, date_of_birth, phone_number, …) or stored credential on a Slick table or in a SQL migration's CREATE TABLE or ALTER TABLE — and no database client (Slick, Doobie, Quill, ScalikeJDBC, Anorm, Skunk, a MongoDB or Cassandra driver, JDBC) imported either, so this repository keeps no sensitive data whose changes an audit trail would record. If it does (through a store configured outside this repository, for instance), the trail belongs to wherever that data is stored.
- C4 Data Retention — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a Slick table or in a SQL migration's CREATE TABLE or ALTER TABLE — and no database or data-store client (Slick, Doobie, Quill, ScalikeJDBC, Anorm, Skunk, JDBC, MongoDB, Cassandra, …) imported either, so this repository keeps no personal data whose lifetime a retention limit would bound.
- C5 Data-Subject Rights — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a Slick table or in a SQL migration's CREATE TABLE or ALTER TABLE — and no database or data-store client (Slick, Doobie, Quill, ScalikeJDBC, Anorm, Skunk, JDBC, MongoDB, Cassandra, …) imported either, so this repository keeps no personal data for a data subject to erase, export or consent over.
- D10 Test Quality — ~8427 lines of test source are present (.scala) but no test cases reached the test census for this repository — no test root we could resolve declared them, or the files we read declare no cases in a test framework we recognise — so skipped/assertion-free tests couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
- D11 Test Reliability — Test reliability not included — the .scala suite was found but not re-run
- D12 Dependency Hygiene — Dependency currency not established — repo1.maven.org did not answer
- D14 License Compliance — Not scored — this repository's 7 pinned sbt dependency coordinate(s) were read from its 1 sbt build file(s), but Maven Central could not be asked for the licence of 6 of them (HTTP 429 Too Many Requests from http://172.31.7.1:8790/maven/com/lihaoyi/sourcecode_3/0.4.2/sourcecode_3-0.4.2.pom), and a licence verdict over part of a dependency graph is not a licence verdict. Nothing is asserted about this repository's licensing in either direction.
- D16 Bus Factor — single-maintainer repository — bus factor is not applicable
- D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
- D19 Documentation Quality — No runnable or published unit to look for an example in, and no multi-project root README to look for a map in; the other documentation kinds are withheld (see the gaps), so documentation quality is not applicable here.
- D20 ADR Quality — N/A — ADRs are expected on deployable products with a user-facing host, not consumed libraries; no ADR log is required here.
- D21 Naming Consistency — Naming consistency is measured on C# and TypeScript only; Scala not measured.
- D22 Internal API Consistency — The exposed public-API surface could not be collected — no C#/VB projects loaded.
- D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D24 Comment Value — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only — this repository's production source is .scala, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D25 ADR Conformance — no ADRs to check
- D27 Navigability — D27 counts a call into the standard library or a dependency as unresolved for this repository's language (.scala), so too few call sites counted as resolved to assess navigability. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
- D32 Data Compliance (PII/GDPR) — 8 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- D39 IL Efficiency — D39 measures the IL emitted by a .NET build; this repository has no .NET solution or project files, so the dimension does not apply.
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
- D8 Code Coverage — Coverage not included — suite not readable by the collector
- DM1 Domain Modelling — applicable but not scored (2 signals for this style, 2 needed — the count is met but a required primary signal is absent): 121 value object(s); 11 domain event(s); its domain events are published by services or handlers — no domain entity raises one
- ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
- ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- M4 Documentation accuracy — Not applicable: the 12 current-state document(s) make no claim of a kind M4 checks. 5 claim(s) of kinds M4 does not check were not checked (path 5); M4 checks only links and versions and artefact counts.
- P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
- P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the JVM source, so there is no service whose uptime a failing dependency could take down
- P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
- P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (`addSbtPlugin("org.scoverage" % "sbt-scoverage" % "<version>")` in `project/plugins.sbt`, then `sbt clean coverage test coverageReport`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures, or wire coverage collection into CI, to enable this cross-layer check
- PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for `@Benchmark` in a Java, Kotlin or Scala file importing JMH or kotlinx-benchmark, Jetpack Benchmark's `measureRepeated` in a file importing androidx.benchmark, or JMH/kotlinx-benchmark/androidx.benchmark in a pom.xml, Gradle or sbt build, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
- PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
- S1 Web-Security Posture — No web surface: 95 Scala file(s) were read for weak hashes and ciphers, key material fixed in the source, disabled TLS certificate validation and obsolete TLS versions, and none was found. This repository serves no HTTP of its own — no HTTP-server artifact (akka-http, pekko-http, http4s, Play, Finagle, zio-http, cask, Scalatra, a tapir server, Jetty, Undertow, …) outside test scope in its build, and no server package imported or server bound in its production source — so HTTPS enforcement, HSTS, cookie flags and input validation are N/A here, as they are for a C# library or worker. If this codebase starts serving HTTP, the dimension reactivates automatically.
- X2 Cancellation propagation — no C# was loaded; this repository's Scala was read, and no request in it can be cancelled by a caller — a Scala request takes no token: a Future cannot be cancelled, and cats-effect, ZIO and Monix interrupt the fiber that made the request from outside the call, not through a parameter
- X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X7 Silent fallback defaults — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
Critical — 10 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
Serious — 30 finding(s)
- TodoComment parapet-testkit/src/main/scala/io/parapet/tests/intg/DslSpec.scala:221
- TodoComment parapet-testkit/src/main/scala/io/parapet/tests/intg/ProcessLifecycleSpec.scala:136
- TodoComment parapet-testkit/src/main/scala/io/parapet/tests/intg/ProcessLifecycleSpec.scala:179
- TodoComment parapet-testkit/src/main/scala/io/parapet/tests/intg/ProcessLifecycleSpec.scala:209
- TodoComment parapet-testkit/src/main/scala/io/parapet/tests/intg/scheduler/SchedulerSpec.scala:75
- Hotspot: parapet-core/src/main/scala/io/parapet/runtime/DslInterpreter.scala parapet-core/src/main/scala/io/parapet/runtime/DslInterpreter.scala:66
- Hotspot: parapet-pario/src/main/scala/io/parapet/effect/ParIORuntime.scala parapet-pario/src/main/scala/io/parapet/effect/ParIORuntime.scala:275
- Hotspot: parapet-core/src/main/scala/io/parapet/runtime/Scheduler.scala parapet-core/src/main/scala/io/parapet/runtime/Scheduler.scala:539
- FileTooLong: journal/DeliveryLog.scala parapet-core/src/main/scala/io/parapet/journal/DeliveryLog.scala
- FileTooLong: runtime/Scheduler.scala parapet-core/src/main/scala/io/parapet/runtime/Scheduler.scala
- FileTooLong: effect/ParIORuntime.scala parapet-pario/src/main/scala/io/parapet/effect/ParIORuntime.scala
- TooManyMethods: DeliveryLog parapet-core/src/main/scala/io/parapet/journal/DeliveryLog.scala:35
- TooManyMethods: Context parapet-core/src/main/scala/io/parapet/runtime/Context.scala:36
- ParIORuntime.unsafeRunLoop (cyclomatic 45) parapet-pario/src/main/scala/io/parapet/effect/ParIORuntime.scala:275
- Impl.interpret (cyclomatic 36) parapet-core/src/main/scala/io/parapet/runtime/DslInterpreter.scala:66
- FixmeComment parapet-core/src/main/scala/io/parapet/runtime/DslInterpreter.scala:163
- ParApp.run (cognitive 49) parapet-core/src/main/scala/io/parapet/ParApp.scala:149
- ParIORuntime.unsafeRunLoop (cognitive 46) parapet-pario/src/main/scala/io/parapet/effect/ParIORuntime.scala:275
- Worker.deliver (cognitive 36) parapet-core/src/main/scala/io/parapet/runtime/Scheduler.scala:539
- Impl.interpret (cognitive 29) parapet-core/src/main/scala/io/parapet/runtime/DslInterpreter.scala:66
- DeliveryLog.scanSegment (cognitive 26) parapet-core/src/main/scala/io/parapet/journal/DeliveryLog.scala:371
- Channel.waitForResponse (cognitive 17) parapet-core/src/main/scala/io/parapet/Channel.scala:57
- ParIORuntime.racePrograms (cognitive 16) parapet-pario/src/main/scala/io/parapet/effect/ParIORuntime.scala:491
- REDACTED
- REDACTED
- Duplicated block (9 lines × 2) parapet-core/src/main/scala/io/parapet/journal/Recorder.scala:78
- Duplicated block (8 lines × 2) parapet-cats-effect/src/main/scala/io/parapet/cats/CatsEffectParapetRuntime.scala:118
- Duplicated block (5 lines × 2) parapet-core/src/main/scala/io/parapet/journal/JournalEntryBinaryFormat.scala:131
- Duplicated block (6 lines × 2) parapet-net/src/main/scala/io/parapet/net/transport/zmq/ZmqTcpClient.scala:65
- Off the main sequence: parapetCore
Minor — 14 finding(s)
- Disabled test parapet-pario/src/test/scala/io/parapet/tests/intg/pario/ParIOSpecs.scala:25
- Disabled test parapet-pario/src/test/scala/io/parapet/tests/intg/pario/ParIOSpecs.scala:90
- Disabled test parapet-testkit/src/main/scala/io/parapet/tests/intg/scheduler/SchedulerSpec.scala:78
- Interpolated log message defeats structured logging parapet-core/src/main/scala/io/parapet/snapshot/SnapshotStorageLocal.scala:29
- Interpolated log message defeats structured logging parapet-core/src/main/scala/io/parapet/runtime/Recovery.scala:130
- Interpolated log message defeats structured logging parapet-core/src/main/scala/io/parapet/journal/JournalStoreLocal.scala:24
- Projects may be oversized for their cohesion
- REDACTED
- REDACTED
- No ADRs
- No SAST REDACTED:6
- No changelog
- Duplicated predicate parapet-core/src/main/scala/io/parapet/journal/JournalEntryBinaryFormat.scala:132
- Scala's null is not held to the type system everywhere
Appendix B — Reproduction & audit trail
| Dimension | Tool | Version | Command | Findings | Raw output |
|---|---|---|---|---|---|
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-49b5f395f59544748004c4d84a58c92e/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-49b5f395f59544748004c4d84a58c92e/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 . | 10 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . /tmp/codehealth-osv-sbom-dad4fe244ba34f28844689c37faf2734 | 0 | artifacts/raw/osv-scanner.json |
| D31 · IaC & Container Security | trivy | — | trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan. | 0 | — |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. semgrep could not parse 8 file(s) — `parapet-core/src/main/scala/io/parapet/Process.scala`, `parapet-core/src/main/scala/io/parapet/fault/FaultInjector.scala`, `parapet-core/src/main/scala/io/parapet/journal/DeliveryLog.scala`, `parapet-core/src/main/scala/io/parapet/runtime/Scheduler.scala`, `parapet-core/src/main/scala/io/parapet/syntax/LoggerSyntax.scala`, … (+3 more) — so the PII/GDPR sweep did not cover them at all. | 0 | — |
| D37 · Vulnerability-disclosure Policy | disclosure | — | disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . /tmp/codehealth-osv-sbom-dad4fe244ba34f28844689c37faf2734 | 0 | artifacts/raw/osv-scanner.json |