Executive summary
http4s/blaze falls short of our standard for production because its Security dimensions are rated Critical, and six passwords or keys sit in the current code. It scores 51 out of 100, which alone would earn Adequate, but it is rated Weak: a rating can't sit more than one step above its weakest group.
Production Readiness, at 42, is the weakest lens and counts most in the score. The best first step is replacing the six exposed passwords or keys and switching the old ones off, worth about 9 points. Recording design decisions comes next, worth about 5 points. Raising Production Readiness to 70 would lift the score to about 58.
Seventeen pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Six passwords or keys in the code and six in the code's history are open to anyone who can read the repository. Pinning each tool to an exact version and replacing each exposed password or key would close both risks. Switching the validation back on would fix the two security checks on connections or logins switched off, and correcting the flagged pipeline settings would deal with the weakness in the build pipeline's configuration.
The product code is 17,950 lines, about €28,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 42 to 70, the lowest score rated Strong, the score would rise from 51 to about 58.
Rebuild cost: about €28,000 · Estimate
| Cost to rebuild | €9,400 to €47,000, for 157 to 498 hours of work, about 0.2 person-years for one engineer |
|---|---|
| Difficulty of the problem | Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.7 at a score of 51. 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: 17,950 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 blaze.channel.nio1.NIO1HeadStage | 2 blaze.client.Http1Connection | 3 blaze.http.http2.FlowStrategy | 4 blaze.pipeline | 5 blaze.util.TaskQueue | 6 blaze.channel.ServerChannel | 7 blaze.client.ConnectionManager | 8 blaze.http.http2.HeaderAggregatingFrameListener | 9 blaze.http.http2.Http2Settings | 10 blaze.http.http2.PingManager | 11 blaze.http.http2.Priority | 12 blaze.http.http2.WriteControllerImpl | 13 blaze.util.TickWheelExecutor | 14 blazecore.util.CachingStaticWriter | 15 blazecore.websocket | 16 blaze.channel | 17 blaze.client.PoolManager | 18 blaze.http.http2.Connection | 19 blaze.http.http2.SettingsDecoder | 20 blaze.util | 21 blazecore.util | 22 org.http4s | 23 blaze.channel.nio1 | 24 blaze.channel.nio2 | 25 blaze.http | 26 blaze.pipeline.stages | 27 blazecore | 28 blazecore.IdleTimeoutStage | 29 blaze.channel.nio1.NIO1Channel | 30 blaze.channel.nio1.NIO1SocketServerGroup | 31 blaze.http.BodyReader | 32 blaze.http.HttpClientSession | 33 blaze.client | 34 blaze.client.ParserMode | 35 blaze.http.http2 | 36 blaze.http.http2.Http2Exception | 37 blaze.http.http2.SessionFlowControlImpl | 38 blaze.http.http2.StreamManagerImpl | 39 blaze.http.http2.server | 40 blaze.server |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 blaze.channel.nio1.NIO1HeadStage | ||||||||||||||||||||||||||||||||||||||||
| 2 blaze.client.Http1Connection | ||||||||||||||||||||||||||||||||||||||||
| 3 blaze.http.http2.FlowStrategy | ||||||||||||||||||||||||||||||||||||||||
| 4 blaze.pipeline | ||||||||||||||||||||||||||||||||||||||||
| 5 blaze.util.TaskQueue | ||||||||||||||||||||||||||||||||||||||||
| 6 blaze.channel.ServerChannel | 3 | |||||||||||||||||||||||||||||||||||||||
| 7 blaze.client.ConnectionManager | 2 | |||||||||||||||||||||||||||||||||||||||
| 8 blaze.http.http2.HeaderAggregatingFrameListener | 1 | |||||||||||||||||||||||||||||||||||||||
| 9 blaze.http.http2.Http2Settings | 1 | |||||||||||||||||||||||||||||||||||||||
| 10 blaze.http.http2.PingManager | 3 | |||||||||||||||||||||||||||||||||||||||
| 11 blaze.http.http2.Priority | 2 | |||||||||||||||||||||||||||||||||||||||
| 12 blaze.http.http2.WriteControllerImpl | 4 | |||||||||||||||||||||||||||||||||||||||
| 13 blaze.util.TickWheelExecutor | 1 | |||||||||||||||||||||||||||||||||||||||
| 14 blazecore.util.CachingStaticWriter | 1 | |||||||||||||||||||||||||||||||||||||||
| 15 blazecore.websocket | 4 | |||||||||||||||||||||||||||||||||||||||
| 16 blaze.channel | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 17 blaze.client.PoolManager | 1 | |||||||||||||||||||||||||||||||||||||||
| 18 blaze.http.http2.Connection | 2 | 2 | ||||||||||||||||||||||||||||||||||||||
| 19 blaze.http.http2.SettingsDecoder | 1 | |||||||||||||||||||||||||||||||||||||||
| 20 blaze.util | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 21 blazecore.util | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 22 org.http4s | 1 | |||||||||||||||||||||||||||||||||||||||
| 23 blaze.channel.nio1 | 1 | 5 | ||||||||||||||||||||||||||||||||||||||
| 24 blaze.channel.nio2 | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 25 blaze.http | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 26 blaze.pipeline.stages | 4 | 2 | ||||||||||||||||||||||||||||||||||||||
| 27 blazecore | 2 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 28 blazecore.IdleTimeoutStage | 3 | 1 | ||||||||||||||||||||||||||||||||||||||
| 29 blaze.channel.nio1.NIO1Channel | 1 | |||||||||||||||||||||||||||||||||||||||
| 30 blaze.channel.nio1.NIO1SocketServerGroup | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 31 blaze.http.BodyReader | 1 | |||||||||||||||||||||||||||||||||||||||
| 32 blaze.http.HttpClientSession | 1 | |||||||||||||||||||||||||||||||||||||||
| 33 blaze.client | 2 | 5 | 1 | 2 | 2 | 1 | 1 | 4 | 1 | |||||||||||||||||||||||||||||||
| 34 blaze.client.ParserMode | 2 | |||||||||||||||||||||||||||||||||||||||
| 35 blaze.http.http2 | 5 | 2 | 4 | 8 | 1 | 6 | 3 | 1 | 1 | 2 | 1 | |||||||||||||||||||||||||||||
| 36 blaze.http.http2.Http2Exception | 3 | |||||||||||||||||||||||||||||||||||||||
| 37 blaze.http.http2.SessionFlowControlImpl | 3 | |||||||||||||||||||||||||||||||||||||||
| 38 blaze.http.http2.StreamManagerImpl | 1 | |||||||||||||||||||||||||||||||||||||||
| 39 blaze.http.http2.server | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 40 blaze.server | 3 | 2 | 3 | 1 | 2 | 1 |
6→2 blaze.channel.ServerChannel uses blaze.client.Http1Connection✕
- Connections
- 3 pairs of types, where a type in blaze.channel.ServerChannel uses a type in blaze.client.Http1Connection.
- The types involved
org.http4s.blaze.channel.ServerChannel.Closed→org.http4s.blaze.client.Http1Connection.Stateorg.http4s.blaze.channel.ServerChannel.Closing→org.http4s.blaze.client.Http1Connection.Stateorg.http4s.blaze.channel.ServerChannel.Open→org.http4s.blaze.client.Http1Connection.State
- Direction
- blaze.channel.ServerChannel uses blaze.client.Http1Connection, so a change to blaze.client.Http1Connection can break blaze.channel.ServerChannel, while a change to blaze.channel.ServerChannel can't break blaze.client.Http1Connection.
- Position
- Below the diagonal: blaze.channel.ServerChannel uses a module listed above it, which is the healthy direction.
7→33 blaze.client.ConnectionManager uses blaze.client part of a loop✕
- Connections
- 2 pairs of types, where a type in blaze.client.ConnectionManager uses a type in blaze.client.
- The types involved
org.http4s.blaze.client.ConnectionManager.Stateful→org.http4s.blaze.client.BlazeClientStateorg.http4s.blaze.client.ConnectionManager.Stateful→org.http4s.blaze.client.ConnectionManager
- Direction
- blaze.client.ConnectionManager uses blaze.client, so a change to blaze.client can break blaze.client.ConnectionManager, while a change to blaze.client.ConnectionManager can't break blaze.client.
- 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.
8→35 blaze.http.http2.HeaderAggregatingFrameListener uses blaze.http.http2 part of a loop✕
- Connections
- 1 pair of types, where a type in blaze.http.http2.HeaderAggregatingFrameListener uses a type in blaze.http.http2.
- The types involved
org.http4s.blaze.http.http2.HeaderAggregatingFrameListener.PHeaders→org.http4s.blaze.http.http2.Priority
- Direction
- blaze.http.http2.HeaderAggregatingFrameListener uses blaze.http.http2, so a change to blaze.http.http2 can break blaze.http.http2.HeaderAggregatingFrameListener, while a change to blaze.http.http2.HeaderAggregatingFrameListener can't break blaze.http.http2.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
9→35 blaze.http.http2.Http2Settings uses blaze.http.http2 part of a loop✕
- Connections
- 1 pair of types, where a type in blaze.http.http2.Http2Settings uses a type in blaze.http.http2.
- The types involved
org.http4s.blaze.http.http2.Http2Settings.InvalidSetting→org.http4s.blaze.http.http2.Http2Exception
- Direction
- blaze.http.http2.Http2Settings uses blaze.http.http2, so a change to blaze.http.http2 can break blaze.http.http2.Http2Settings, while a change to blaze.http.http2.Http2Settings can't break blaze.http.http2.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
10→2 blaze.http.http2.PingManager uses blaze.client.Http1Connection✕
- Connections
- 3 pairs of types, where a type in blaze.http.http2.PingManager uses a type in blaze.client.Http1Connection.
- The types involved
org.http4s.blaze.http.http2.PingManager.Closed→org.http4s.blaze.client.Http1Connection.Stateorg.http4s.blaze.http.http2.PingManager.Idle→org.http4s.blaze.client.Http1Connection.Stateorg.http4s.blaze.http.http2.PingManager.Pinging→org.http4s.blaze.client.Http1Connection.State
- Direction
- blaze.http.http2.PingManager uses blaze.client.Http1Connection, so a change to blaze.client.Http1Connection can break blaze.http.http2.PingManager, while a change to blaze.http.http2.PingManager can't break blaze.client.Http1Connection.
- Position
- Below the diagonal: blaze.http.http2.PingManager uses a module listed above it, which is the healthy direction.
11→35 blaze.http.http2.Priority uses blaze.http.http2 part of a loop✕
- Connections
- 2 pairs of types, where a type in blaze.http.http2.Priority uses a type in blaze.http.http2.
- The types involved
org.http4s.blaze.http.http2.Priority.Dependent→org.http4s.blaze.http.http2.Priorityorg.http4s.blaze.http.http2.Priority.NoPriority→org.http4s.blaze.http.http2.Priority
- Direction
- blaze.http.http2.Priority uses blaze.http.http2, so a change to blaze.http.http2 can break blaze.http.http2.Priority, while a change to blaze.http.http2.Priority can't break blaze.http.http2.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
12→2 blaze.http.http2.WriteControllerImpl uses blaze.client.Http1Connection✕
- Connections
- 4 pairs of types, where a type in blaze.http.http2.WriteControllerImpl uses a type in blaze.client.Http1Connection.
- The types involved
org.http4s.blaze.http.http2.WriteControllerImpl.Closed→org.http4s.blaze.client.Http1Connection.Stateorg.http4s.blaze.http.http2.WriteControllerImpl.Closing→org.http4s.blaze.client.Http1Connection.Stateorg.http4s.blaze.http.http2.WriteControllerImpl.Flushing→org.http4s.blaze.client.Http1Connection.Stateorg.http4s.blaze.http.http2.WriteControllerImpl.Idle→org.http4s.blaze.client.Http1Connection.State
- Direction
- blaze.http.http2.WriteControllerImpl uses blaze.client.Http1Connection, so a change to blaze.client.Http1Connection can break blaze.http.http2.WriteControllerImpl, while a change to blaze.http.http2.WriteControllerImpl can't break blaze.client.Http1Connection.
- Position
- Below the diagonal: blaze.http.http2.WriteControllerImpl uses a module listed above it, which is the healthy direction.
13→20 blaze.util.TickWheelExecutor uses blaze.util part of a loop✕
- Connections
- 1 pair of types, where a type in blaze.util.TickWheelExecutor uses a type in blaze.util.
- The types involved
org.http4s.blaze.util.TickWheelExecutor.Node→org.http4s.blaze.util.Cancelable
- Direction
- blaze.util.TickWheelExecutor uses blaze.util, so a change to blaze.util can break blaze.util.TickWheelExecutor, while a change to blaze.util.TickWheelExecutor can't break blaze.util.
- 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→21 blazecore.util.CachingStaticWriter uses blazecore.util part of a loop✕
- Connections
- 1 pair of types, where a type in blazecore.util.CachingStaticWriter uses a type in blazecore.util.
- The types involved
org.http4s.blazecore.util.CachingStaticWriter.InnerWriter→org.http4s.blazecore.util.IdentityWriter
- Direction
- blazecore.util.CachingStaticWriter uses blazecore.util, so a change to blazecore.util can break blazecore.util.CachingStaticWriter, while a change to blazecore.util.CachingStaticWriter can't break blazecore.util.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
15→4 blazecore.websocket uses blaze.pipeline✕
- Connections
- 4 pairs of types, where a type in blazecore.websocket uses a type in blaze.pipeline.
- The types involved
org.http4s.blazecore.websocket.Http4sWSStage→org.http4s.blaze.pipeline.TailStageorg.http4s.blazecore.websocket.PassThrough→org.http4s.blaze.pipeline.MidStageorg.http4s.blazecore.websocket.ReadSerializer→org.http4s.blaze.pipeline.TailStageorg.http4s.blazecore.websocket.WriteSerializer→org.http4s.blaze.pipeline.TailStage
- Direction
- blazecore.websocket uses blaze.pipeline, so a change to blaze.pipeline can break blazecore.websocket, while a change to blazecore.websocket can't break blaze.pipeline.
- Position
- Below the diagonal: blazecore.websocket uses a module listed above it, which is the healthy direction.
16→2 blaze.channel uses blaze.client.Http1Connection✕
- Connections
- 1 pair of types, where a type in blaze.channel uses a type in blaze.client.Http1Connection.
- The types involved
org.http4s.blaze.channel.ServerChannel→org.http4s.blaze.client.Http1Connection.State
- Direction
- blaze.channel uses blaze.client.Http1Connection, so a change to blaze.client.Http1Connection can break blaze.channel, while a change to blaze.channel can't break blaze.client.Http1Connection.
- Position
- Below the diagonal: blaze.channel uses a module listed above it, which is the healthy direction.
16→4 blaze.channel uses blaze.pipeline✕
- Connections
- 1 pair of types, where a type in blaze.channel uses a type in blaze.pipeline.
- The types involved
org.http4s.blaze.channel.ChannelHead→org.http4s.blaze.pipeline.HeadStage
- Direction
- blaze.channel uses blaze.pipeline, so a change to blaze.pipeline can break blaze.channel, while a change to blaze.channel can't break blaze.pipeline.
- Position
- Below the diagonal: blaze.channel uses a module listed above it, which is the healthy direction.
16→6 blaze.channel uses blaze.channel.ServerChannel✕
- Connections
- 1 pair of types, where a type in blaze.channel uses a type in blaze.channel.ServerChannel.
- The types involved
org.http4s.blaze.channel.ServerChannel→org.http4s.blaze.channel.ServerChannel.Hook
- Direction
- blaze.channel uses blaze.channel.ServerChannel, so a change to blaze.channel.ServerChannel can break blaze.channel, while a change to blaze.channel can't break blaze.channel.ServerChannel.
- Position
- Below the diagonal: blaze.channel uses a module listed above it, which is the healthy direction.
17→7 blaze.client.PoolManager uses blaze.client.ConnectionManager✕
- Connections
- 1 pair of types, where a type in blaze.client.PoolManager uses a type in blaze.client.ConnectionManager.
- The types involved
org.http4s.blaze.client.PoolManager.Waiting→org.http4s.blaze.client.ConnectionManager.NextConnection
- Direction
- blaze.client.PoolManager uses blaze.client.ConnectionManager, so a change to blaze.client.ConnectionManager can break blaze.client.PoolManager, while a change to blaze.client.PoolManager can't break blaze.client.ConnectionManager.
- Position
- Below the diagonal: blaze.client.PoolManager uses a module listed above it, which is the healthy direction.
18→2 blaze.http.http2.Connection uses blaze.client.Http1Connection✕
- Connections
- 2 pairs of types, where a type in blaze.http.http2.Connection uses a type in blaze.client.Http1Connection.
- The types involved
org.http4s.blaze.http.http2.Connection.Closing→org.http4s.blaze.client.Http1Connection.Stateorg.http4s.blaze.http.http2.Connection.Running→org.http4s.blaze.client.Http1Connection.State
- Direction
- blaze.http.http2.Connection uses blaze.client.Http1Connection, so a change to blaze.client.Http1Connection can break blaze.http.http2.Connection, while a change to blaze.http.http2.Connection can't break blaze.client.Http1Connection.
- Position
- Below the diagonal: blaze.http.http2.Connection uses a module listed above it, which is the healthy direction.
18→6 blaze.http.http2.Connection uses blaze.channel.ServerChannel✕
- Connections
- 2 pairs of types, where a type in blaze.http.http2.Connection uses a type in blaze.channel.ServerChannel.
- The types involved
org.http4s.blaze.http.http2.Connection.Closed→org.http4s.blaze.channel.ServerChannel.Closingorg.http4s.blaze.http.http2.Connection.Draining→org.http4s.blaze.channel.ServerChannel.Closing
- Direction
- blaze.http.http2.Connection uses blaze.channel.ServerChannel, so a change to blaze.channel.ServerChannel can break blaze.http.http2.Connection, while a change to blaze.http.http2.Connection can't break blaze.channel.ServerChannel.
- Position
- Below the diagonal: blaze.http.http2.Connection uses a module listed above it, which is the healthy direction.
19→9 blaze.http.http2.SettingsDecoder uses blaze.http.http2.Http2Settings✕
- Connections
- 1 pair of types, where a type in blaze.http.http2.SettingsDecoder uses a type in blaze.http.http2.Http2Settings.
- The types involved
org.http4s.blaze.http.http2.SettingsDecoder.SettingsFrame→org.http4s.blaze.http.http2.Http2Settings.Setting
- Direction
- blaze.http.http2.SettingsDecoder uses blaze.http.http2.Http2Settings, so a change to blaze.http.http2.Http2Settings can break blaze.http.http2.SettingsDecoder, while a change to blaze.http.http2.SettingsDecoder can't break blaze.http.http2.Http2Settings.
- Position
- Below the diagonal: blaze.http.http2.SettingsDecoder uses a module listed above it, which is the healthy direction.
20→4 blaze.util uses blaze.pipeline✕
- Connections
- 1 pair of types, where a type in blaze.util uses a type in blaze.pipeline.
- The types involved
org.http4s.blaze.util.StageTools→org.http4s.blaze.pipeline.TailStage
- Direction
- blaze.util uses blaze.pipeline, so a change to blaze.pipeline can break blaze.util, while a change to blaze.util can't break blaze.pipeline.
- Position
- Below the diagonal: blaze.util uses a module listed above it, which is the healthy direction.
20→5 blaze.util uses blaze.util.TaskQueue✕
- Connections
- 1 pair of types, where a type in blaze.util uses a type in blaze.util.TaskQueue.
- The types involved
org.http4s.blaze.util.TaskQueue→org.http4s.blaze.util.TaskQueue.Result
- Direction
- blaze.util uses blaze.util.TaskQueue, so a change to blaze.util.TaskQueue can break blaze.util, while a change to blaze.util can't break blaze.util.TaskQueue.
- Position
- Below the diagonal: blaze.util uses a module listed above it, which is the healthy direction.
20→13 blaze.util uses blaze.util.TickWheelExecutor✕
- Connections
- 1 pair of types, where a type in blaze.util uses a type in blaze.util.TickWheelExecutor.
- The types involved
org.http4s.blaze.util.TickWheelExecutor→org.http4s.blaze.util.TickWheelExecutor.Bucket
- Direction
- blaze.util uses blaze.util.TickWheelExecutor, so a change to blaze.util.TickWheelExecutor can break blaze.util, while a change to blaze.util can't break blaze.util.TickWheelExecutor.
- Position
- Below the diagonal: blaze.util uses a module listed above it, which is the healthy direction.
21→4 blazecore.util uses blaze.pipeline✕
- Connections
- 1 pair of types, where a type in blazecore.util uses a type in blaze.pipeline.
- The types involved
org.http4s.blazecore.util.ChunkWriter→org.http4s.blaze.pipeline.TailStage
- Direction
- blazecore.util uses blaze.pipeline, so a change to blaze.pipeline can break blazecore.util, while a change to blazecore.util can't break blaze.pipeline.
- Position
- Below the diagonal: blazecore.util uses a module listed above it, which is the healthy direction.
21→14 blazecore.util uses blazecore.util.CachingStaticWriter✕
- Connections
- 1 pair of types, where a type in blazecore.util uses a type in blazecore.util.CachingStaticWriter.
- The types involved
org.http4s.blazecore.util.CachingStaticWriter→org.http4s.blazecore.util.CachingStaticWriter.InnerWriter
- Direction
- blazecore.util uses blazecore.util.CachingStaticWriter, so a change to blazecore.util.CachingStaticWriter can break blazecore.util, while a change to blazecore.util can't break blazecore.util.CachingStaticWriter.
- Position
- Below the diagonal: blazecore.util uses a module listed above it, which is the healthy direction.
22→20 org.http4s uses blaze.util✕
- Connections
- 1 pair of types, where a type in org.http4s uses a type in blaze.util.
- The types involved
org.http4s.blazecore→org.http4s.blaze.util.TickWheelExecutor
- Direction
- org.http4s uses blaze.util, so a change to blaze.util can break org.http4s, while a change to org.http4s can't break blaze.util.
- Position
- Below the diagonal: org.http4s uses a module listed above it, which is the healthy direction.
23→1 blaze.channel.nio1 uses blaze.channel.nio1.NIO1HeadStage✕
- Connections
- 1 pair of types, where a type in blaze.channel.nio1 uses a type in blaze.channel.nio1.NIO1HeadStage.
- The types involved
org.http4s.blaze.channel.nio1.NIO1HeadStage→org.http4s.blaze.channel.nio1.NIO1HeadStage.WriteResult
- Direction
- blaze.channel.nio1 uses blaze.channel.nio1.NIO1HeadStage, so a change to blaze.channel.nio1.NIO1HeadStage can break blaze.channel.nio1, while a change to blaze.channel.nio1 can't break blaze.channel.nio1.NIO1HeadStage.
- Position
- Below the diagonal: blaze.channel.nio1 uses a module listed above it, which is the healthy direction.
23→16 blaze.channel.nio1 uses blaze.channel✕
- Connections
- 5 pairs of types, where a type in blaze.channel.nio1 uses a type in blaze.channel.
- The types involved
org.http4s.blaze.channel.nio1.NIO1ClientChannel→org.http4s.blaze.channel.ChannelOptionsorg.http4s.blaze.channel.nio1.NIO1Connection→org.http4s.blaze.channel.SocketConnectionorg.http4s.blaze.channel.nio1.NIO1SocketConnection→org.http4s.blaze.channel.SocketConnectionorg.http4s.blaze.channel.nio1.NIO1SocketServerGroup→org.http4s.blaze.channel.ChannelOptionsorg.http4s.blaze.channel.nio1.NIO1SocketServerGroup→org.http4s.blaze.channel.ServerChannelGroup
- Direction
- blaze.channel.nio1 uses blaze.channel, so a change to blaze.channel can break blaze.channel.nio1, while a change to blaze.channel.nio1 can't break blaze.channel.
- Position
- Below the diagonal: blaze.channel.nio1 uses a module listed above it, which is the healthy direction.
24→4 blaze.channel.nio2 uses blaze.pipeline✕
- Connections
- 1 pair of types, where a type in blaze.channel.nio2 uses a type in blaze.pipeline.
- The types involved
org.http4s.blaze.channel.nio2.ClientChannelFactory→org.http4s.blaze.pipeline.HeadStage
- Direction
- blaze.channel.nio2 uses blaze.pipeline, so a change to blaze.pipeline can break blaze.channel.nio2, while a change to blaze.channel.nio2 can't break blaze.pipeline.
- Position
- Below the diagonal: blaze.channel.nio2 uses a module listed above it, which is the healthy direction.
24→16 blaze.channel.nio2 uses blaze.channel✕
- Connections
- 2 pairs of types, where a type in blaze.channel.nio2 uses a type in blaze.channel.
- The types involved
org.http4s.blaze.channel.nio2.ByteBufferHead→org.http4s.blaze.channel.ChannelHeadorg.http4s.blaze.channel.nio2.ClientChannelFactory→org.http4s.blaze.channel.ChannelOptions
- Direction
- blaze.channel.nio2 uses blaze.channel, so a change to blaze.channel can break blaze.channel.nio2, while a change to blaze.channel.nio2 can't break blaze.channel.
- Position
- Below the diagonal: blaze.channel.nio2 uses a module listed above it, which is the healthy direction.
25→20 blaze.http uses blaze.util✕
- Connections
- 1 pair of types, where a type in blaze.http uses a type in blaze.util.
- The types involved
org.http4s.blaze.http.logsensitiveinfo→org.http4s.blaze.util.Property
- Direction
- blaze.http uses blaze.util, so a change to blaze.util can break blaze.http, while a change to blaze.http can't break blaze.util.
- Position
- Below the diagonal: blaze.http uses a module listed above it, which is the healthy direction.
25→32 blaze.http uses blaze.http.HttpClientSession part of a loop✕
- Connections
- 2 pairs of types, where a type in blaze.http uses a type in blaze.http.HttpClientSession.
- The types involved
org.http4s.blaze.http.HttpClientSession→org.http4s.blaze.http.HttpClientSession.ReleaseableResponseorg.http4s.blaze.http.HttpClientSession→org.http4s.blaze.http.HttpClientSession.Status
- Direction
- blaze.http uses blaze.http.HttpClientSession, so a change to blaze.http.HttpClientSession can break blaze.http, while a change to blaze.http can't break blaze.http.HttpClientSession.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
26→4 blaze.pipeline.stages uses blaze.pipeline✕
- Connections
- 4 pairs of types, where a type in blaze.pipeline.stages uses a type in blaze.pipeline.
- The types involved
org.http4s.blaze.pipeline.stages.BasicTail→org.http4s.blaze.pipeline.TailStageorg.http4s.blaze.pipeline.stages.ByteToObjectStage→org.http4s.blaze.pipeline.MidStageorg.http4s.blaze.pipeline.stages.OneMessageStage→org.http4s.blaze.pipeline.MidStageorg.http4s.blaze.pipeline.stages.TimeoutStageBase→org.http4s.blaze.pipeline.MidStage
- Direction
- blaze.pipeline.stages uses blaze.pipeline, so a change to blaze.pipeline can break blaze.pipeline.stages, while a change to blaze.pipeline.stages can't break blaze.pipeline.
- Position
- Below the diagonal: blaze.pipeline.stages uses a module listed above it, which is the healthy direction.
26→20 blaze.pipeline.stages uses blaze.util✕
- Connections
- 2 pairs of types, where a type in blaze.pipeline.stages uses a type in blaze.util.
- The types involved
org.http4s.blaze.pipeline.stages.SSLStage→org.http4s.blaze.util.ThreadLocalScratchBufferorg.http4s.blaze.pipeline.stages.TimeoutStageBase→org.http4s.blaze.util.Cancelable
- Direction
- blaze.pipeline.stages uses blaze.util, so a change to blaze.util can break blaze.pipeline.stages, while a change to blaze.pipeline.stages can't break blaze.util.
- Position
- Below the diagonal: blaze.pipeline.stages uses a module listed above it, which is the healthy direction.
27→4 blazecore uses blaze.pipeline✕
- Connections
- 2 pairs of types, where a type in blazecore uses a type in blaze.pipeline.
- The types involved
org.http4s.blazecore.IdleTimeoutStage→org.http4s.blaze.pipeline.MidStageorg.http4s.blazecore.ResponseHeaderTimeoutStage→org.http4s.blaze.pipeline.MidStage
- Direction
- blazecore uses blaze.pipeline, so a change to blaze.pipeline can break blazecore, while a change to blazecore can't break blaze.pipeline.
- Position
- Below the diagonal: blazecore uses a module listed above it, which is the healthy direction.
27→16 blazecore uses blaze.channel✕
- Connections
- 1 pair of types, where a type in blazecore uses a type in blaze.channel.
- The types involved
org.http4s.blazecore.BlazeBackendBuilder→org.http4s.blaze.channel.ChannelOptions
- Direction
- blazecore uses blaze.channel, so a change to blaze.channel can break blazecore, while a change to blazecore can't break blaze.channel.
- Position
- Below the diagonal: blazecore uses a module listed above it, which is the healthy direction.
27→20 blazecore uses blaze.util✕
- Connections
- 1 pair of types, where a type in blazecore uses a type in blaze.util.
- The types involved
org.http4s.blazecore.IdleTimeoutStage→org.http4s.blaze.util.Cancelable
- Direction
- blazecore uses blaze.util, so a change to blaze.util can break blazecore, while a change to blazecore can't break blaze.util.
- Position
- Below the diagonal: blazecore uses a module listed above it, which is the healthy direction.
27→21 blazecore uses blazecore.util✕
- Connections
- 1 pair of types, where a type in blazecore uses a type in blazecore.util.
- The types involved
org.http4s.blazecore.Http1Stage→org.http4s.blazecore.util.Http1Writer
- Direction
- blazecore uses blazecore.util, so a change to blazecore.util can break blazecore, while a change to blazecore can't break blazecore.util.
- Position
- Below the diagonal: blazecore uses a module listed above it, which is the healthy direction.
27→33 blazecore uses blaze.client part of a loop✕
- Connections
- 1 pair of types, where a type in blazecore uses a type in blaze.client.
- The types involved
org.http4s.blazecore.Http1Stage→org.http4s.blaze.client.Connection
- Direction
- blazecore uses blaze.client, so a change to blaze.client can break blazecore, while a change to blazecore can't break blaze.client.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
28→2 blazecore.IdleTimeoutStage uses blaze.client.Http1Connection✕
- Connections
- 3 pairs of types, where a type in blazecore.IdleTimeoutStage uses a type in blaze.client.Http1Connection.
- The types involved
org.http4s.blazecore.IdleTimeoutStage.Disabled→org.http4s.blaze.client.Http1Connection.Stateorg.http4s.blazecore.IdleTimeoutStage.Enabled→org.http4s.blaze.client.Http1Connection.Stateorg.http4s.blazecore.IdleTimeoutStage.ShutDown→org.http4s.blaze.client.Http1Connection.State
- Direction
- blazecore.IdleTimeoutStage uses blaze.client.Http1Connection, so a change to blaze.client.Http1Connection can break blazecore.IdleTimeoutStage, while a change to blazecore.IdleTimeoutStage can't break blaze.client.Http1Connection.
- Position
- Below the diagonal: blazecore.IdleTimeoutStage uses a module listed above it, which is the healthy direction.
28→20 blazecore.IdleTimeoutStage uses blaze.util✕
- Connections
- 1 pair of types, where a type in blazecore.IdleTimeoutStage uses a type in blaze.util.
- The types involved
org.http4s.blazecore.IdleTimeoutStage.Enabled→org.http4s.blaze.util.Cancelable
- Direction
- blazecore.IdleTimeoutStage uses blaze.util, so a change to blaze.util can break blazecore.IdleTimeoutStage, while a change to blazecore.IdleTimeoutStage can't break blaze.util.
- Position
- Below the diagonal: blazecore.IdleTimeoutStage uses a module listed above it, which is the healthy direction.
29→23 blaze.channel.nio1.NIO1Channel uses blaze.channel.nio1✕
- Connections
- 1 pair of types, where a type in blaze.channel.nio1.NIO1Channel uses a type in blaze.channel.nio1.
- The types involved
org.http4s.blaze.channel.nio1.NIO1Channel.Impl→org.http4s.blaze.channel.nio1.NIO1Channel
- Direction
- blaze.channel.nio1.NIO1Channel uses blaze.channel.nio1, so a change to blaze.channel.nio1 can break blaze.channel.nio1.NIO1Channel, while a change to blaze.channel.nio1.NIO1Channel can't break blaze.channel.nio1.
- Position
- Below the diagonal: blaze.channel.nio1.NIO1Channel uses a module listed above it, which is the healthy direction.
30→16 blaze.channel.nio1.NIO1SocketServerGroup uses blaze.channel✕
- Connections
- 1 pair of types, where a type in blaze.channel.nio1.NIO1SocketServerGroup uses a type in blaze.channel.
- The types involved
org.http4s.blaze.channel.nio1.NIO1SocketServerGroup.ServerChannelImpl→org.http4s.blaze.channel.ServerChannel
- Direction
- blaze.channel.nio1.NIO1SocketServerGroup uses blaze.channel, so a change to blaze.channel can break blaze.channel.nio1.NIO1SocketServerGroup, while a change to blaze.channel.nio1.NIO1SocketServerGroup can't break blaze.channel.
- Position
- Below the diagonal: blaze.channel.nio1.NIO1SocketServerGroup uses a module listed above it, which is the healthy direction.
30→23 blaze.channel.nio1.NIO1SocketServerGroup uses blaze.channel.nio1✕
- Connections
- 2 pairs of types, where a type in blaze.channel.nio1.NIO1SocketServerGroup uses a type in blaze.channel.nio1.
- The types involved
org.http4s.blaze.channel.nio1.NIO1SocketServerGroup.ServerChannelImpl→org.http4s.blaze.channel.nio1.NIO1Channelorg.http4s.blaze.channel.nio1.NIO1SocketServerGroup.SocketAcceptor→org.http4s.blaze.channel.nio1.Selectable
- Direction
- blaze.channel.nio1.NIO1SocketServerGroup uses blaze.channel.nio1, so a change to blaze.channel.nio1 can break blaze.channel.nio1.NIO1SocketServerGroup, while a change to blaze.channel.nio1.NIO1SocketServerGroup can't break blaze.channel.nio1.
- Position
- Below the diagonal: blaze.channel.nio1.NIO1SocketServerGroup uses a module listed above it, which is the healthy direction.
31→25 blaze.http.BodyReader uses blaze.http✕
- Connections
- 1 pair of types, where a type in blaze.http.BodyReader uses a type in blaze.http.
- The types involved
org.http4s.blaze.http.BodyReader.Proxy→org.http4s.blaze.http.BodyReader
- Direction
- blaze.http.BodyReader uses blaze.http, so a change to blaze.http can break blaze.http.BodyReader, while a change to blaze.http.BodyReader can't break blaze.http.
- Position
- Below the diagonal: blaze.http.BodyReader uses a module listed above it, which is the healthy direction.
32→25 blaze.http.HttpClientSession uses blaze.http✕
- Connections
- 1 pair of types, where a type in blaze.http.HttpClientSession uses a type in blaze.http.
- The types involved
org.http4s.blaze.http.HttpClientSession.ReleaseableResponse→org.http4s.blaze.http.ClientResponse
- Direction
- blaze.http.HttpClientSession uses blaze.http, so a change to blaze.http can break blaze.http.HttpClientSession, while a change to blaze.http.HttpClientSession can't break blaze.http.
- Position
- Below the diagonal: blaze.http.HttpClientSession uses a module listed above it, which is the healthy direction.
33→4 blaze.client uses blaze.pipeline✕
- Connections
- 2 pairs of types, where a type in blaze.client uses a type in blaze.pipeline.
- The types involved
org.http4s.blaze.client.BlazeConnection→org.http4s.blaze.pipeline.TailStageorg.http4s.blaze.client.Http1Support→org.http4s.blaze.pipeline.HeadStage
- Direction
- blaze.client uses blaze.pipeline, so a change to blaze.pipeline can break blaze.client, while a change to blaze.client can't break blaze.pipeline.
- Position
- Below the diagonal: blaze.client uses a module listed above it, which is the healthy direction.
33→7 blaze.client uses blaze.client.ConnectionManager✕
- Connections
- 5 pairs of types, where a type in blaze.client uses a type in blaze.client.ConnectionManager.
- The types involved
org.http4s.blaze.client.BasicManager→org.http4s.blaze.client.ConnectionManager.NextConnectionorg.http4s.blaze.client.BlazeClientBuilder→org.http4s.blaze.client.ConnectionManager.Statefulorg.http4s.blaze.client.ConnectionManager→org.http4s.blaze.client.ConnectionManager.NextConnectionorg.http4s.blaze.client.PoolManager→org.http4s.blaze.client.ConnectionManager.NextConnectionorg.http4s.blaze.client.PoolManager→org.http4s.blaze.client.ConnectionManager.Stateful
- Direction
- blaze.client uses blaze.client.ConnectionManager, so a change to blaze.client.ConnectionManager can break blaze.client, while a change to blaze.client can't break blaze.client.ConnectionManager.
- Position
- Below the diagonal: blaze.client uses a module listed above it, which is the healthy direction.
33→16 blaze.client uses blaze.channel✕
- Connections
- 1 pair of types, where a type in blaze.client uses a type in blaze.channel.
- The types involved
org.http4s.blaze.client.BlazeClientBuilder→org.http4s.blaze.channel.ChannelOptions
- Direction
- blaze.client uses blaze.channel, so a change to blaze.channel can break blaze.client, while a change to blaze.client can't break blaze.channel.
- Position
- Below the diagonal: blaze.client uses a module listed above it, which is the healthy direction.
33→17 blaze.client uses blaze.client.PoolManager✕
- Connections
- 2 pairs of types, where a type in blaze.client uses a type in blaze.client.PoolManager.
- The types involved
org.http4s.blaze.client.PoolManager→org.http4s.blaze.client.PoolManager.PooledConnectionorg.http4s.blaze.client.PoolManager→org.http4s.blaze.client.PoolManager.Waiting
- Direction
- blaze.client uses blaze.client.PoolManager, so a change to blaze.client.PoolManager can break blaze.client, while a change to blaze.client can't break blaze.client.PoolManager.
- Position
- Below the diagonal: blaze.client uses a module listed above it, which is the healthy direction.
33→20 blaze.client uses blaze.util✕
- Connections
- 2 pairs of types, where a type in blaze.client uses a type in blaze.util.
- The types involved
org.http4s.blaze.client.BlazeClient→org.http4s.blaze.util.TickWheelExecutororg.http4s.blaze.client.BlazeClientBuilder→org.http4s.blaze.util.TickWheelExecutor
- Direction
- blaze.client uses blaze.util, so a change to blaze.util can break blaze.client, while a change to blaze.client can't break blaze.util.
- Position
- Below the diagonal: blaze.client uses a module listed above it, which is the healthy direction.
33→21 blaze.client uses blazecore.util✕
- Connections
- 1 pair of types, where a type in blaze.client uses a type in blazecore.util.
- The types involved
org.http4s.blaze.client.Http1Connection→org.http4s.blazecore.util.Http1Writer
- Direction
- blaze.client uses blazecore.util, so a change to blazecore.util can break blaze.client, while a change to blaze.client can't break blazecore.util.
- Position
- Below the diagonal: blaze.client uses a module listed above it, which is the healthy direction.
33→26 blaze.client uses blaze.pipeline.stages✕
- Connections
- 1 pair of types, where a type in blaze.client uses a type in blaze.pipeline.stages.
- The types involved
org.http4s.blaze.client.Http1Support→org.http4s.blaze.pipeline.stages.SSLStage
- Direction
- blaze.client uses blaze.pipeline.stages, so a change to blaze.pipeline.stages can break blaze.client, while a change to blaze.client can't break blaze.pipeline.stages.
- Position
- Below the diagonal: blaze.client uses a module listed above it, which is the healthy direction.
33→27 blaze.client uses blazecore✕
- Connections
- 4 pairs of types, where a type in blaze.client uses a type in blazecore.
- The types involved
org.http4s.blaze.client.BlazeClientBuilder→org.http4s.blazecore.BlazeBackendBuilderorg.http4s.blaze.client.BlazeClientBuilder→org.http4s.blazecore.ExecutionContextConfigorg.http4s.blaze.client.Http1Connection→org.http4s.blazecore.Http1Stageorg.http4s.blaze.client.Http1Support→org.http4s.blazecore.IdleTimeoutStage
- Direction
- blaze.client uses blazecore, so a change to blazecore can break blaze.client, while a change to blaze.client can't break blazecore.
- Position
- Below the diagonal: blaze.client uses a module listed above it, which is the healthy direction.
33→32 blaze.client uses blaze.http.HttpClientSession✕
- Connections
- 1 pair of types, where a type in blaze.client uses a type in blaze.http.HttpClientSession.
- The types involved
org.http4s.blaze.client.BlazeHttp1ClientParser→org.http4s.blaze.http.HttpClientSession.Status
- Direction
- blaze.client uses blaze.http.HttpClientSession, so a change to blaze.http.HttpClientSession can break blaze.client, while a change to blaze.client can't break blaze.http.HttpClientSession.
- Position
- Below the diagonal: blaze.client uses a module listed above it, which is the healthy direction.
34→33 blaze.client.ParserMode uses blaze.client✕
- Connections
- 2 pairs of types, where a type in blaze.client.ParserMode uses a type in blaze.client.
- The types involved
org.http4s.blaze.client.ParserMode.Lenient→org.http4s.blaze.client.ParserModeorg.http4s.blaze.client.ParserMode.Strict→org.http4s.blaze.client.ParserMode
- Direction
- blaze.client.ParserMode uses blaze.client, so a change to blaze.client can break blaze.client.ParserMode, while a change to blaze.client.ParserMode can't break blaze.client.
- Position
- Below the diagonal: blaze.client.ParserMode uses a module listed above it, which is the healthy direction.
35→2 blaze.http.http2 uses blaze.client.Http1Connection✕
- Connections
- 5 pairs of types, where a type in blaze.http.http2 uses a type in blaze.client.Http1Connection.
- The types involved
org.http4s.blaze.http.http2.ConnectionImpl→org.http4s.blaze.client.Http1Connection.Stateorg.http4s.blaze.http.http2.HeaderAggregatingFrameListener→org.http4s.blaze.client.Http1Connection.Errororg.http4s.blaze.http.http2.PingManager→org.http4s.blaze.client.Http1Connection.Stateorg.http4s.blaze.http.http2.SessionCore→org.http4s.blaze.client.Http1Connection.Stateorg.http4s.blaze.http.http2.WriteControllerImpl→org.http4s.blaze.client.Http1Connection.State
- Direction
- blaze.http.http2 uses blaze.client.Http1Connection, so a change to blaze.client.Http1Connection can break blaze.http.http2, while a change to blaze.http.http2 can't break blaze.client.Http1Connection.
- Position
- Below the diagonal: blaze.http.http2 uses a module listed above it, which is the healthy direction.
35→3 blaze.http.http2 uses blaze.http.http2.FlowStrategy✕
- Connections
- 2 pairs of types, where a type in blaze.http.http2 uses a type in blaze.http.http2.FlowStrategy.
- The types involved
org.http4s.blaze.http.http2.DefaultFlowStrategy→org.http4s.blaze.http.http2.FlowStrategy.Incrementorg.http4s.blaze.http.http2.FlowStrategy→org.http4s.blaze.http.http2.FlowStrategy.Increment
- Direction
- blaze.http.http2 uses blaze.http.http2.FlowStrategy, so a change to blaze.http.http2.FlowStrategy can break blaze.http.http2, while a change to blaze.http.http2 can't break blaze.http.http2.FlowStrategy.
- Position
- Below the diagonal: blaze.http.http2 uses a module listed above it, which is the healthy direction.
35→4 blaze.http.http2 uses blaze.pipeline✕
- Connections
- 4 pairs of types, where a type in blaze.http.http2 uses a type in blaze.pipeline.
- The types involved
org.http4s.blaze.http.http2.Connection→org.http4s.blaze.pipeline.HeadStageorg.http4s.blaze.http.http2.ConnectionImpl→org.http4s.blaze.pipeline.HeadStageorg.http4s.blaze.http.http2.PriorKnowledgeHandshaker→org.http4s.blaze.pipeline.TailStageorg.http4s.blaze.http.http2.StreamState→org.http4s.blaze.pipeline.HeadStage
- Direction
- blaze.http.http2 uses blaze.pipeline, so a change to blaze.pipeline can break blaze.http.http2, while a change to blaze.http.http2 can't break blaze.pipeline.
- Position
- Below the diagonal: blaze.http.http2 uses a module listed above it, which is the healthy direction.
35→5 blaze.http.http2 uses blaze.util.TaskQueue✕
- Connections
- 8 pairs of types, where a type in blaze.http.http2 uses a type in blaze.util.TaskQueue.
- The types involved
org.http4s.blaze.http.http2.BufferUnderflow→org.http4s.blaze.util.TaskQueue.Resultorg.http4s.blaze.http.http2.FrameDecoder→org.http4s.blaze.util.TaskQueue.Resultorg.http4s.blaze.http.http2.FrameListener→org.http4s.blaze.util.TaskQueue.Resultorg.http4s.blaze.http.http2.HeaderAggregatingFrameListener→org.http4s.blaze.util.TaskQueue.Resultorg.http4s.blaze.http.http2.MaybeError→org.http4s.blaze.util.TaskQueue.Resultorg.http4s.blaze.http.http2.SessionFrameListener→org.http4s.blaze.util.TaskQueue.Resultorg.http4s.blaze.http.http2.StreamManager→org.http4s.blaze.util.TaskQueue.Resultorg.http4s.blaze.http.http2.StreamManagerImpl→org.http4s.blaze.util.TaskQueue.Result
- Direction
- blaze.http.http2 uses blaze.util.TaskQueue, so a change to blaze.util.TaskQueue can break blaze.http.http2, while a change to blaze.http.http2 can't break blaze.util.TaskQueue.
- Position
- Below the diagonal: blaze.http.http2 uses a module listed above it, which is the healthy direction.
35→8 blaze.http.http2 uses blaze.http.http2.HeaderAggregatingFrameListener✕
- Connections
- 1 pair of types, where a type in blaze.http.http2 uses a type in blaze.http.http2.HeaderAggregatingFrameListener.
- The types involved
org.http4s.blaze.http.http2.HeaderAggregatingFrameListener→org.http4s.blaze.http.http2.HeaderAggregatingFrameListener.PartialFrame
- Direction
- blaze.http.http2 uses blaze.http.http2.HeaderAggregatingFrameListener, so a change to blaze.http.http2.HeaderAggregatingFrameListener can break blaze.http.http2, while a change to blaze.http.http2 can't break blaze.http.http2.HeaderAggregatingFrameListener.
- Position
- Below the diagonal: blaze.http.http2 uses a module listed above it, which is the healthy direction.
35→9 blaze.http.http2 uses blaze.http.http2.Http2Settings✕
- Connections
- 6 pairs of types, where a type in blaze.http.http2 uses a type in blaze.http.http2.Http2Settings.
- The types involved
org.http4s.blaze.http.http2.FrameListener→org.http4s.blaze.http.http2.Http2Settings.Settingorg.http4s.blaze.http.http2.FrameSerializer→org.http4s.blaze.http.http2.Http2Settings.Settingorg.http4s.blaze.http.http2.Http2Settings→org.http4s.blaze.http.http2.Http2Settings.Settingorg.http4s.blaze.http.http2.MutableHttp2Settings→org.http4s.blaze.http.http2.Http2Settings.Settingorg.http4s.blaze.http.http2.SessionFrameListener→org.http4s.blaze.http.http2.Http2Settings.Settingorg.http4s.blaze.http.http2.SettingsDecoder→org.http4s.blaze.http.http2.Http2Settings.Setting
- Direction
- blaze.http.http2 uses blaze.http.http2.Http2Settings, so a change to blaze.http.http2.Http2Settings can break blaze.http.http2, while a change to blaze.http.http2 can't break blaze.http.http2.Http2Settings.
- Position
- Below the diagonal: blaze.http.http2 uses a module listed above it, which is the healthy direction.
35→11 blaze.http.http2 uses blaze.http.http2.Priority✕
- Connections
- 3 pairs of types, where a type in blaze.http.http2 uses a type in blaze.http.http2.Priority.
- The types involved
org.http4s.blaze.http.http2.FrameListener→org.http4s.blaze.http.http2.Priority.Dependentorg.http4s.blaze.http.http2.FrameSerializer→org.http4s.blaze.http.http2.Priority.Dependentorg.http4s.blaze.http.http2.SessionFrameListener→org.http4s.blaze.http.http2.Priority.Dependent
- Direction
- blaze.http.http2 uses blaze.http.http2.Priority, so a change to blaze.http.http2.Priority can break blaze.http.http2, while a change to blaze.http.http2 can't break blaze.http.http2.Priority.
- Position
- Below the diagonal: blaze.http.http2 uses a module listed above it, which is the healthy direction.
35→19 blaze.http.http2 uses blaze.http.http2.SettingsDecoder✕
- Connections
- 1 pair of types, where a type in blaze.http.http2 uses a type in blaze.http.http2.SettingsDecoder.
- The types involved
org.http4s.blaze.http.http2.SettingsDecoder→org.http4s.blaze.http.http2.SettingsDecoder.SettingsFrame
- Direction
- blaze.http.http2 uses blaze.http.http2.SettingsDecoder, so a change to blaze.http.http2.SettingsDecoder can break blaze.http.http2, while a change to blaze.http.http2 can't break blaze.http.http2.SettingsDecoder.
- Position
- Below the diagonal: blaze.http.http2 uses a module listed above it, which is the healthy direction.
35→20 blaze.http.http2 uses blaze.util✕
- Connections
- 1 pair of types, where a type in blaze.http.http2 uses a type in blaze.util.
- The types involved
org.http4s.blaze.http.http2.ConnectionImpl→org.http4s.blaze.util.SerialExecutionContext
- Direction
- blaze.http.http2 uses blaze.util, so a change to blaze.util can break blaze.http.http2, while a change to blaze.http.http2 can't break blaze.util.
- Position
- Below the diagonal: blaze.http.http2 uses a module listed above it, which is the healthy direction.
35→32 blaze.http.http2 uses blaze.http.HttpClientSession✕
- Connections
- 2 pairs of types, where a type in blaze.http.http2 uses a type in blaze.http.HttpClientSession.
- The types involved
org.http4s.blaze.http.http2.Connection→org.http4s.blaze.http.HttpClientSession.Statusorg.http4s.blaze.http.http2.ConnectionImpl→org.http4s.blaze.http.HttpClientSession.Status
- Direction
- blaze.http.http2 uses blaze.http.HttpClientSession, so a change to blaze.http.HttpClientSession can break blaze.http.http2, while a change to blaze.http.http2 can't break blaze.http.HttpClientSession.
- Position
- Below the diagonal: blaze.http.http2 uses a module listed above it, which is the healthy direction.
35→33 blaze.http.http2 uses blaze.client✕
- Connections
- 1 pair of types, where a type in blaze.http.http2 uses a type in blaze.client.
- The types involved
org.http4s.blaze.http.http2.ConnectionImpl→org.http4s.blaze.client.Connection
- Direction
- blaze.http.http2 uses blaze.client, so a change to blaze.client can break blaze.http.http2, while a change to blaze.http.http2 can't break blaze.client.
- Position
- Below the diagonal: blaze.http.http2 uses a module listed above it, which is the healthy direction.
36→35 blaze.http.http2.Http2Exception uses blaze.http.http2✕
- Connections
- 3 pairs of types, where a type in blaze.http.http2.Http2Exception uses a type in blaze.http.http2.
- The types involved
org.http4s.blaze.http.http2.Http2Exception.ErrorGenerator→org.http4s.blaze.http.http2.Http2Exceptionorg.http4s.blaze.http.http2.Http2Exception.ErrorGenerator→org.http4s.blaze.http.http2.Http2SessionExceptionorg.http4s.blaze.http.http2.Http2Exception.ErrorGenerator→org.http4s.blaze.http.http2.Http2StreamException
- Direction
- blaze.http.http2.Http2Exception uses blaze.http.http2, so a change to blaze.http.http2 can break blaze.http.http2.Http2Exception, while a change to blaze.http.http2.Http2Exception can't break blaze.http.http2.
- Position
- Below the diagonal: blaze.http.http2.Http2Exception uses a module listed above it, which is the healthy direction.
37→35 blaze.http.http2.SessionFlowControlImpl uses blaze.http.http2✕
- Connections
- 3 pairs of types, where a type in blaze.http.http2.SessionFlowControlImpl uses a type in blaze.http.http2.
- The types involved
org.http4s.blaze.http.http2.SessionFlowControlImpl.StreamFlowWindowImpl→org.http4s.blaze.http.http2.Http2Exceptionorg.http4s.blaze.http.http2.SessionFlowControlImpl.StreamFlowWindowImpl→org.http4s.blaze.http.http2.SessionFlowControlorg.http4s.blaze.http.http2.SessionFlowControlImpl.StreamFlowWindowImpl→org.http4s.blaze.http.http2.StreamFlowWindow
- Direction
- blaze.http.http2.SessionFlowControlImpl uses blaze.http.http2, so a change to blaze.http.http2 can break blaze.http.http2.SessionFlowControlImpl, while a change to blaze.http.http2.SessionFlowControlImpl can't break blaze.http.http2.
- Position
- Below the diagonal: blaze.http.http2.SessionFlowControlImpl uses a module listed above it, which is the healthy direction.
38→35 blaze.http.http2.StreamManagerImpl uses blaze.http.http2✕
- Connections
- 1 pair of types, where a type in blaze.http.http2.StreamManagerImpl uses a type in blaze.http.http2.
- The types involved
org.http4s.blaze.http.http2.StreamManagerImpl.OutboundStreamStateImpl→org.http4s.blaze.http.http2.OutboundStreamStateImpl
- Direction
- blaze.http.http2.StreamManagerImpl uses blaze.http.http2, so a change to blaze.http.http2 can break blaze.http.http2.StreamManagerImpl, while a change to blaze.http.http2.StreamManagerImpl can't break blaze.http.http2.
- Position
- Below the diagonal: blaze.http.http2.StreamManagerImpl uses a module listed above it, which is the healthy direction.
39→4 blaze.http.http2.server uses blaze.pipeline✕
- Connections
- 1 pair of types, where a type in blaze.http.http2.server uses a type in blaze.pipeline.
- The types involved
org.http4s.blaze.http.http2.server.ALPNServerSelector→org.http4s.blaze.pipeline.TailStage
- Direction
- blaze.http.http2.server uses blaze.pipeline, so a change to blaze.pipeline can break blaze.http.http2.server, while a change to blaze.http.http2.server can't break blaze.pipeline.
- Position
- Below the diagonal: blaze.http.http2.server uses a module listed above it, which is the healthy direction.
39→35 blaze.http.http2.server uses blaze.http.http2✕
- Connections
- 2 pairs of types, where a type in blaze.http.http2.server uses a type in blaze.http.http2.
- The types involved
org.http4s.blaze.http.http2.server.ServerPriorKnowledgeHandshaker→org.http4s.blaze.http.http2.MutableHttp2Settingsorg.http4s.blaze.http.http2.server.ServerPriorKnowledgeHandshaker→org.http4s.blaze.http.http2.PriorKnowledgeHandshaker
- Direction
- blaze.http.http2.server uses blaze.http.http2, so a change to blaze.http.http2 can break blaze.http.http2.server, while a change to blaze.http.http2.server can't break blaze.http.http2.
- Position
- Below the diagonal: blaze.http.http2.server uses a module listed above it, which is the healthy direction.
40→4 blaze.server uses blaze.pipeline✕
- Connections
- 3 pairs of types, where a type in blaze.server uses a type in blaze.pipeline.
- The types involved
org.http4s.blaze.server.BlazeServerBuilder→org.http4s.blaze.pipeline.LeafBuilderorg.http4s.blaze.server.Http2NodeStage→org.http4s.blaze.pipeline.TailStageorg.http4s.blaze.server.WSFrameAggregator→org.http4s.blaze.pipeline.MidStage
- Direction
- blaze.server uses blaze.pipeline, so a change to blaze.pipeline can break blaze.server, while a change to blaze.server can't break blaze.pipeline.
- Position
- Below the diagonal: blaze.server uses a module listed above it, which is the healthy direction.
40→16 blaze.server uses blaze.channel✕
- Connections
- 2 pairs of types, where a type in blaze.server uses a type in blaze.channel.
- The types involved
org.http4s.blaze.server.BlazeServerBuilder→org.http4s.blaze.channel.ChannelOptionsorg.http4s.blaze.server.BlazeServerBuilder→org.http4s.blaze.channel.SocketConnection
- Direction
- blaze.server uses blaze.channel, so a change to blaze.channel can break blaze.server, while a change to blaze.server can't break blaze.channel.
- Position
- Below the diagonal: blaze.server uses a module listed above it, which is the healthy direction.
40→20 blaze.server uses blaze.util✕
- Connections
- 3 pairs of types, where a type in blaze.server uses a type in blaze.util.
- The types involved
org.http4s.blaze.server.BlazeServerBuilder→org.http4s.blaze.util.TickWheelExecutororg.http4s.blaze.server.Http1ServerStage→org.http4s.blaze.util.TickWheelExecutororg.http4s.blaze.server.ProtocolSelector→org.http4s.blaze.util.TickWheelExecutor
- Direction
- blaze.server uses blaze.util, so a change to blaze.util can break blaze.server, while a change to blaze.server can't break blaze.util.
- Position
- Below the diagonal: blaze.server uses a module listed above it, which is the healthy direction.
40→26 blaze.server uses blaze.pipeline.stages✕
- Connections
- 1 pair of types, where a type in blaze.server uses a type in blaze.pipeline.stages.
- The types involved
org.http4s.blaze.server.WebSocketDecoder→org.http4s.blaze.pipeline.stages.ByteToObjectStage
- Direction
- blaze.server uses blaze.pipeline.stages, so a change to blaze.pipeline.stages can break blaze.server, while a change to blaze.server can't break blaze.pipeline.stages.
- Position
- Below the diagonal: blaze.server uses a module listed above it, which is the healthy direction.
40→27 blaze.server uses blazecore✕
- Connections
- 2 pairs of types, where a type in blaze.server uses a type in blazecore.
- The types involved
org.http4s.blaze.server.BlazeServerBuilder→org.http4s.blazecore.BlazeBackendBuilderorg.http4s.blaze.server.BlazeServerBuilder→org.http4s.blazecore.ExecutionContextConfig
- Direction
- blaze.server uses blazecore, so a change to blazecore can break blaze.server, while a change to blaze.server can't break blazecore.
- Position
- Below the diagonal: blaze.server uses a module listed above it, which is the healthy direction.
40→39 blaze.server uses blaze.http.http2.server✕
- Connections
- 1 pair of types, where a type in blaze.server uses a type in blaze.http.http2.server.
- The types involved
org.http4s.blaze.server.ProtocolSelector→org.http4s.blaze.http.http2.server.ALPNServerSelector
- Direction
- blaze.server uses blaze.http.http2.server, so a change to blaze.http.http2.server can break blaze.server, while a change to blaze.server can't break blaze.http.http2.server.
- Position
- Below the diagonal: blaze.server 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 | 18 | High / Critical |
| A07:2025 — Authentication Failures | 13 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 6 | Medium |
Roadmap
Top priorities: Resolve the 6 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED (2), REDACTED (2), REDACTED; Resolve the 1 No ADRs found finding(s) in ADR Quality; Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 6 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED (2), REDACTED (2), REDACTED. | +8.5 pts | Low | REDACTED Scanning |
| Resolve the 1 No ADRs found finding(s) in ADR Quality. | +5.1 pts | Low | ADR Quality |
| 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. | +4.3 pts | Medium | Architecture documentation |
| Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets. | +3.8 pts | Medium | Security & performance tooling |
| Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release. | +3.2 pts | Medium | Release Hygiene |
| Stop accepting every TLS certificate: delete the trust manager whose `checkServerTrusted` is empty, the `HostnameVerifier` that returns `true`, `InsecureTrustManagerFactory` / `NoopHostnameVerifier` and `acceptAnyCertificate`, and trust a self-signed or private server by giving the client a trust store holding its CA — never by switching verification off. This repository constructs a TLS client that accepts any certificate at 2 sites, not one: `blaze-client/src/main/scala/org/http4s/blaze/client/bits.scala:49` (an `X509TrustManager` whose `checkServerTrusted` accepts every chain), `core/src/main/scala/org/http4s/blaze/util/GenericSSLContext.scala:29` (an `X509TrustManager` whose `checkServerTrusted` accepts every chain). Each is a separate decision — fixing only the line this row cites leaves the others in place. | +2.4 pts | Medium | Web-Security Posture |
| Keep implementation types off the public surface (Java: package-private (no modifier), or leave its package out of `module-info` exports) so internals can change without breaking consumers. | +2.4 pts | Medium | Library API & versioning |
| 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. | +2.3 pts | Medium | Documentation (README) |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 2.3 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 3.0 | Slop | REDACTED Scanning: Leaked secret: REDACTED |
| REDACTED | 4.4 | Mixed | REDACTED Scanning: Leaked secret: REDACTED |
| REDACTED | 4.4 | Mixed | REDACTED Scanning: Leaked secret: REDACTED |
| REDACTED | 4.4 | Mixed | REDACTED Scanning: Leaked secret: REDACTED |
| REDACTED | 4.4 | Mixed | REDACTED Scanning: Leaked secret: REDACTED |
| blaze-server/src/main/scala/org/http4s/blaze/server/Http2NodeStage.scala | 6.0 | Mixed | Explicit Debt: TodoComment |
| http/src/main/java/org/http4s/blaze/http/parser/BodyAndHeaderParser.java | 6.0 | Mixed | Explicit Debt: TodoComment |
| blaze-server/src/main/scala/org/http4s/blaze/server/Http1ServerStage.scala | 6.0 | Mixed | Explicit Debt: TodoComment |
| http/src/main/scala/org/http4s/blaze/http/http2/FrameDecoder.scala | 6.7 | Mixed | Explicit Debt: TodoComment |
| blaze-core/src/main/scala/org/http4s/blazecore/Http1Stage.scala | 6.7 | Mixed | Explicit Debt: TodoComment |
| blaze-client/src/main/scala/org/http4s/blaze/client/Http1Connection.scala | 6.7 | Mixed | Explicit Debt: TodoComment |
| http/src/main/scala/org/http4s/blaze/http/http2/StreamManagerImpl.scala | 6.9 | Mixed | Explicit Debt: TodoComment |
| blaze-server/src/main/scala/org/http4s/blaze/server/BlazeServerBuilder.scala | 7.1 | Mixed | Cognitive Complexity: BlazeServerBuilder.pipelineFactory (cognitive 25) |
| REDACTED | 7.2 | Mixed | Secrets (history): REDACTED: REDACTED |
| http/src/main/scala/org/http4s/blaze/http/http2/SessionFrameListener.scala | 7.3 | Mixed | Explicit Debt: TodoComment |
| blaze-client/src/main/scala/org/http4s/blaze/client/BlazeClientBuilder.scala | 7.4 | Mixed | Cognitive Complexity: BlazeClientBuilder.resourceWithState (cognitive 21) |
| http/src/main/java/org/http4s/blaze/http/parser/Http1ClientParser.java | 7.8 | Mixed | Cyclomatic Complexity: Http1ClientParser.parseResponseLine (cyclomatic 32) |
| http/src/main/java/org/http4s/blaze/http/parser/Http1ServerParser.java | 7.8 | Mixed | Cyclomatic Complexity: Http1ServerParser.parseRequestLine (cyclomatic 28) |
| core/src/main/scala/org/http4s/blaze/pipeline/stages/SSLStage.scala | 7.8 | Mixed | Cyclomatic Complexity: SSLStage.sslHandshake (cyclomatic 21) |
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 57 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 — 57 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, 95 of 111 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, 92 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/twitter/hpack/maven-metadata.xml). This is OUR side and it is an ENVIRONMENT fault, not a missing collector: the collector exists and ran. An HTTP 403 here is what this scan's egress allowlist returns for a host that is not on it, so the remedy is to add repo1.maven.org to the allowlist and re-run — not to build anything.
- D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D21's deterministic naming rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. Until then its declarations carry no naming verdict this run — this says nothing about whether its names are consistent.
- D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22 identifies the intentionally-exposed surface from `IsPackable` and `.Contracts` project names, MSBuild conventions read off the loaded project set. This target exposed no such projects, so the probe never ran; this says nothing about whether the repository has a public API. This repository commits no C#/VB source at all, so there was never an MSBuild project set to read these conventions off. That is OUR side and it is a COLLECTOR gap, not an environment fault: it declares a published package (build.sbt), but no published-package marker D22 reads admitted any project here, so this ecosystem's public API has no collector, and the remedy is to write one — no change to the scan image can close it.
- 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.
- D34 Knowledge Freshness — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. File-level freshness contradicts repo activity: 30 commits in the last 90 days, yet 74 of 82 significant files carry no living knowledge. Those two readings cannot both be true, so the per-file recency signal is treated as unreliable here and freshness is not scored for this run.
- D44 Platform End-of-Life — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This dimension reads a project's own statement about the platform it runs on: a TargetFramework in a .NET project file, a .nvmrc or .python-version, a capped requires-python, a Rust toolchain file or Cargo.toml rust-version, a .go-version, .java-version, .ruby-version, .tool-versions or .sdkmanrc, a go.mod go directive, a Maven or Gradle Java level or toolchain, a Gemfile's ruby directive, a mix.exs elixir requirement, a rebar.config minimum_otp_vsn, a pubspec.yaml SDK constraint, a build.sbt scalaVersion, or a framework major pinned by a dependency constraint. This repository carries none of them, so nothing about its platform was established. That is a gap in this analyzer's coverage, NOT a finding that the platform is supported — a language whose runtime is declared elsewhere (Package.swift, a Dockerfile) is simply not read here yet.
- AX2 Stateful singletons — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads Microsoft.Extensions.DependencyInjection singletons in C#, Spring/JSR-330/CDI singletons in Java and Kotlin, module state in Python request handlers, handler state in Go and Swift, Play controllers, Cask routes, Scalatra servlets, Finatra controllers, Akka/Pekko HTTP routes and JSR-330 singletons in Scala, Rails, Sinatra, Grape, Roda and Hanami handlers and Rack apps in Ruby, and module state in F# request handlers (Giraffe, Saturn, Falco, Oxpecker and Suave handlers and ASP.NET Core controllers) only, and this repository's product is written in Scala (http4s), which was left unread, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- C1 Data Protection — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These personal data controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks personal data controls.
- C2 Access Controls — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These authorization controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks authorization controls.
- P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
- D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
- D13 REDACTED Scanning: REDACTED detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
- D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- 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
8 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was Http2NodeStage.checkAndRunRequest at 33. A further 1 method(s) were over the threshold but excluded as flat dispatchers (a long switch/match over independent cases: many branches, almost no nesting), the largest being HttpTokens.isTchar at 21 — they are counted neither in the figure above nor in this dimension's score. 1 file carries no cyclomatic complexity row at all for this reason — every one of its over-threshold methods was excluded, so the exclusion is disclosed nowhere in the file itself: http/src/main/java/org/http4s/blaze/http/parser/HttpTokens.java (HttpTokens.isTchar at 21). They are named here because the per-file figures other dimensions report are taken BEFORE this exclusion, so such a file can show a high maximum complexity elsewhere in this report and nothing here, with nothing to reconcile the two.
What to do
- Bring the 8 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with Http2NodeStage.checkAndRunRequest (cyclomatic 33), Http1ClientParser.parseResponseLine (cyclomatic 32), BodyAndHeaderParser.parseHeaders (cyclomatic 31). — 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 8 together lifts Cyclomatic Complexity from 8.5 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
15 method(s) exceeded the cognitive complexity threshold of 15; the worst was BodyAndHeaderParser.parseHeaders at 76.
What to do
- Bring the 5 bodies over 30 down to 30 or less in Cognitive Complexity — start with BodyAndHeaderParser.parseHeaders (cognitive 76), Http1ClientParser.parseResponseLine (cognitive 62), BodyAndHeaderParser.chunkedContent (cognitive 54). — 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 5 together lifts Cognitive Complexity from 7.1 to about 8.1/10, projected with the scoring formula itself and assuming each lands exactly at 30; a cleaner split scores higher.
- 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
4 god class(es) detected.
What to do
- Resolve the 3 MethodTooLong finding(s) in God Classes — start with BlazeServerBuilder.scala (3). — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 1 TooManyMethods finding(s) in God Classes — start with BlazeClientBuilder.scala. — One of this dimension's main actionable groups (1 warning-level).
- Enforce God Classes in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D4 · Code Duplication
2 duplicated block group(s) detected.
What to do
- Resolve the 1 Duplicated block (21 lines × 2) finding(s) in Code Duplication — start with BlazeClientBuilder.scala. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Duplicated block (12–13 lines × 2) finding(s) in Code Duplication — start with GenericSSLContext.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
7 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 6 of the 7 (the rest declare no modelled class or interface, export only macros, declare types in source no model reads, or have no source directory of their own).
What to do
- Resolve the 1 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (1 warning-level).
- Enforce Coupling in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D6 · Cohesion (LCOM4)
1 of 59 classes have LCOM4 above 3.
What to do
- Resolve the 1 Low cohesion finding(s) in Cohesion (LCOM4) — start with ConnectionMonitor.scala. — One of this dimension's main actionable groups (1 warning-level).
- Enforce Cohesion (LCOM4) in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D9 · Test Distribution
539 test methods: 539 unit, 0 integration, 0 BDD, 0 e2e. The Scala suite contributes 539 test case(s) across 53 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 · REDACTED Scanning
6 secret(s) detected.
What to do
- Resolve the 6 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED (2), REDACTED (2), REDACTED. — One of this dimension's main actionable groups (6 issue-level).
- Enforce REDACTED Scanning in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window.
D16 · Bus Factor
5 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is http/src/main/java/org/http4s/blaze/http/parser/BodyAndHeaderParser.java. Counted over 73 of the 163 production source files in this repository: 81 are under the ~2,400-byte size floor this dimension measures over, and the remaining 9 have no attributable history left to measure.
D17 · Explicit Debt
27 deducted task-comment markers across 17950 LoC (0.1/KLoC) → score 9.7. 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 27 TodoComment finding(s) in Explicit Debt — start with StreamManagerImpl.scala (3), SessionFrameListener.scala (2), ProtocolFrame.scala. — One of this dimension's main actionable groups (27 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.
D20 · ADR Quality
No architecture decision records were found.
What to do
- Resolve the 1 No ADRs found finding(s) in ADR Quality. — One of this dimension's main actionable groups (1 recommendation-level).
D26 · Project Cohesion
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)
6 finding(s): 0 critical, 6 high, 0 medium, 0 low. Remediation for historically-committed secrets is credential rotation — they remain in history regardless of later deletion.
What to do
- Resolve the 4 High secret finding(s) in Secrets (history) — start with REDACTED (2), REDACTED, REDACTED. — One of this dimension's main actionable groups (4 issue-level).
- Resolve the 2 REDACTED finding(s) in Secrets (history) — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
- Resolve the 1 Rotate the exposed credentials finding(s) in Secrets (history). — One of this dimension's main actionable groups (1 recommendation-level).
D29 · Static Analysis (SAST)
18 finding(s): 0 critical, 18 high, 0 medium, 0 low. 17 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. Separately, one or more rules could not re-parse an embedded snippet in 1 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.
What to do
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- No action in Static Analysis (SAST) — all 17 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 (17 issue-level, 0 of them charged here).
D30 · Dependency Vulnerabilities
No known-vulnerable dependencies in any ecosystem this repository declares.
D35 · Change Coupling
No strong hidden change-coupling between production files.
D36 · Supply-chain Provenance & Signing
1/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).
What to do
- Resolve the 2 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
Frontend & cross-cutting dimensions
AX10 · Code composition
What to do
- The domain core is a small share of production code, but most of the rest matched no layer vocabulary at all — so this is not yet an anemic-domain finding. The namespace/path convention could not place that code, which makes the composition above a statement about the naming, not about the design. Name the layers (or check that the repository's conventions differ from the ones this check knows) before reading a thin domain into it.
AX3 · Project dependency cycles
AX4 · Dependency direction
AX6 · Interface segregation
GD1 · Unfinished & placeholder code
IC1 · Incompleteness & stubs
- A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something. — blaze-client/src/test/scala/org/http4s/blaze/client/Http1ClientStageSuite.scala:246
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)
- 56 code files changed in the last 6 months but the README was not touched — it may no longer reflect the system.
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.
- Review the README against recent changes; refresh the parts that drifted.
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
- No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
- Add a C4 context/container diagram (Structurizr, PlantUML or Mermaid) or an architecture.md overview.
M3 · Folder & project structure
P1 · CI/CD gates
P10 · Library API & versioning
- 12/16 types (75%) declared in the published library are public. For a library, every public type is a stability contract — keep implementation types off the surface and expose only the intended API.
What to do
- Keep implementation types off the public surface (Java: package-private (no modifier), or leave its package out of `module-info` exports) so internals can change without breaking consumers.
P3 · Security & performance tooling
What to do
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P6 · Release Hygiene
- No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
What to do
- Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.
PF2 · Allocation hygiene
PF3 · Async & latency hygiene
S1 · Web-Security Posture
- an `X509TrustManager` whose `checkServerTrusted` accepts every chain is set on a TLS client, so every peer certificate is accepted — including one an attacker presents. Chain, expiry, revocation and hostname are all skipped, so an attacker on the network path can present any certificate and read or rewrite the traffic — the connection is encrypted to the attacker, not to the intended host. Remove the override so the JVM's default trust manager and hostname check apply — that is what `SSLContext.getDefault`, Netty's `SslContextBuilder.forClient()`, sttp, Play WS and ssl-config use when nothing is set. If the server presents a self-signed or privately-issued certificate, trust THAT issuer rather than every certificate: load its CA into a `KeyStore` and build a `TrustManagerFactory` from it (ssl-config: `trustManager.stores`), which keeps the chain and hostname checks on. (×2) — blaze-client/src/main/scala/org/http4s/blaze/client/bits.scala:49, core/src/main/scala/org/http4s/blaze/util/GenericSSLContext.scala:29
What to do
- Stop accepting every TLS certificate: delete the trust manager whose `checkServerTrusted` is empty, the `HostnameVerifier` that returns `true`, `InsecureTrustManagerFactory` / `NoopHostnameVerifier` and `acceptAnyCertificate`, and trust a self-signed or private server by giving the client a trust store holding its CA — never by switching verification off. This repository constructs a TLS client that accepts any certificate at 2 sites, not one: `blaze-client/src/main/scala/org/http4s/blaze/client/bits.scala:49` (an `X509TrustManager` whose `checkServerTrusted` accepts every chain), `core/src/main/scala/org/http4s/blaze/util/GenericSSLContext.scala:29` (an `X509TrustManager` whose `checkServerTrusted` accepts every chain). Each is a separate decision — fixing only the line this row cites leaves the others in place.
X1 · Async correctness
X12 · Unreachable branch
X13 · Undrained process stream
X14 · Bypassable address classification
X15 · Unvalidated length from an untrusted reader
X16 · Unfloored truncation loop
X17 · Uncapped recursion over a caller-supplied document
X18 · Disposal-pattern correctness
X19 · Unrestored process-global state
X20 · Mistyped argument guard
X21 · Side-effecting pattern guard
X22 · Contradicted release guard
X23 · Unguarded diagnostic materialisation
X24 · Document value interpolated into markup unescaped
X25 · Inert configuration knob
X26 · Unsynchronised callback handoff
X27 · Collection changed while being enumerated
X28 · Index access outside its own emptiness guard
X29 · Per-element action decided by a fixed element
X3 · Exception handling
X30 · Support guard that admits what it rejects
X5 · Nullable reference types
- No build over this repository's 153 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 | 72% | Adequate — gated by X5 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 79% | Adequate — gated by D26 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Maturity | 50% | Weak — gated by M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 42% | Weak — gated by D13 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 54% | 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 — 3 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 2 control(s) we could not find positive evidence for
- P4 Deployment & Rollback — not evidenced — no deploy/rollback/approval signal in the repo; absence of evidence is not evidence of a manual release
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 59 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 Java 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; this repository's Scala imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's.
- AX2 Stateful singletons — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AX8 Test isolation — no test/production split to check
- AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
- AXB1 Runtime evidence locked — no reproducible boot — This repository has nothing the runtime tiers could boot or serve — no markup, no UI framework or web-server dependency, no UI component source, no native UI project and no API definition — nothing here is a surface to boot — so runtime a11y/egress/header evidence has no subject here. Not applicable: this is neither a gap in the scan nor a finding about your code.
- C1 Data Protection — Not assessed: these personal data controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks personal data controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- C2 Access Controls — Not assessed: these authorization controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks authorization controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- C3 Audit Trail — No personal data detected in a persisted data model — no PII-named column (email, first_name, date_of_birth, phone_number, …) or stored credential on a Slick table or in a SQL migration's CREATE TABLE or ALTER TABLE — and no database client (Slick, Doobie, Quill, ScalikeJDBC, Anorm, Skunk, a MongoDB or Cassandra driver, JDBC) imported either, so this repository keeps no sensitive data whose changes an audit trail would record. If it does (through a store configured outside this repository, for instance), the trail belongs to wherever that data is stored.
- C4 Data Retention — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a Slick table or in a SQL migration's CREATE TABLE or ALTER TABLE — and no database or data-store client (Slick, Doobie, Quill, ScalikeJDBC, Anorm, Skunk, JDBC, MongoDB, Cassandra, …) imported either, so this repository keeps no personal data whose lifetime a retention limit would bound.
- C5 Data-Subject Rights — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a Slick table or in a SQL migration's CREATE TABLE or ALTER TABLE — and no database or data-store client (Slick, Doobie, Quill, ScalikeJDBC, Anorm, Skunk, JDBC, MongoDB, Cassandra, …) imported either, so this repository keeps no personal data for a data subject to erase, export or consent over.
- D10 Test Quality — ~11986 lines of test source are present (.scala) but no test cases reached the test census for this repository — no test root we could resolve declared them, or the files we read declare no cases in a test framework we recognise — so skipped/assertion-free tests couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
- D11 Test Reliability — Test reliability not included — the .scala suite was found but not re-run
- D12 Dependency Hygiene — Dependency currency not established — repo1.maven.org did not answer
- D14 License Compliance — Not scored — this repository's 2 pinned sbt dependency coordinate(s) were read from its 2 sbt build file(s), but Maven Central could not be asked for the licence of 2 of them (HTTP 429 Too Many Requests from http://172.31.7.1:8790/maven/com/twitter/hpack/1.0.2/hpack-1.0.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.
- D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
- D19 Documentation Quality — No runnable or published unit to look for an example in, and no multi-project root README to look for a map in; the other documentation kinds are withheld (see the gaps), so documentation quality is not applicable here.
- D21 Naming Consistency — Naming consistency is measured on C# and TypeScript only; Java, 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 .java, .scala, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D25 ADR Conformance — no ADRs to check
- D27 Navigability — D27 counts a call into the standard library or a dependency as unresolved for this repository's language (.scala), so too few call sites counted as resolved to assess navigability. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
- D32 Data Compliance (PII/GDPR) — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
- D34 Knowledge Freshness — knowledge concentrated in recent work — freshness signal contradicted by repo activity
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- D39 IL Efficiency — D39 measures the IL emitted by a .NET build; this repository has no .NET solution or project files, so the dimension does not apply.
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D44 Platform End-of-Life — Platform end-of-life not assessed — this repository declares no platform this pass reads
- D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
- D8 Code Coverage — Coverage not included — suite not readable by the collector
- 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): 61 value object(s); 5 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 1 current-state document(s) make no claim of a kind M4 checks.
- P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
- P2 Observability — This repository's JVM source (1 module(s), 160 file(s) read) declares no entry point and bootstraps no server, and nothing here deploys a service — it is a library, run inside whatever hosts it, so production observability (structured logging, tracing/metrics, health checks) is N/A. If it grows a binary or a service, the dimension reactivates.
- P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the JVM source, so there is no service whose uptime a failing dependency could take down
- P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
- P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (`addSbtPlugin("org.scoverage" % "sbt-scoverage" % "<version>")` in `project/plugins.sbt`, then `sbt clean coverage test coverageReport`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures, or wire coverage collection into CI, to enable this cross-layer check
- PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for `@Benchmark` in a Java, Kotlin or Scala file importing JMH or kotlinx-benchmark, Jetpack Benchmark's `measureRepeated` in a file importing androidx.benchmark, or JMH/kotlinx-benchmark/androidx.benchmark in a pom.xml, Gradle or sbt build, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
- X2 Cancellation propagation — no C# was loaded; this repository's Scala and Java were 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; a Java request off Android takes no token: it is cancelled through the handle it returns (Future.cancel, Call.cancel, a Disposable), ambiently (io.grpc.Context) or by interrupting its thread, not through a parameter
- X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X4 Structured logging — This check asks whether log calls keep a message's values apart from its text, which needs a logger that can carry them as fields. This repository's Java was read, and it logs through none that an assembled message defeats: java.util.logging's level methods, log4j 1, commons-logging, JBoss Logging and Flogger take one finished message (as log4net does in C#), or it makes no call through a named logger at all. Calls made through SLF4J or log4j 2 (`org.slf4j.Logger`, `org.apache.logging.log4j.Logger`, Lombok's `@Slf4j`) would be judged.
- X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X7 Silent fallback defaults — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
Critical — 32 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- TLS certificate validation disabled blaze-client/src/main/scala/org/http4s/blaze/client/bits.scala:49
- TLS certificate validation disabled core/src/main/scala/org/http4s/blaze/util/GenericSSLContext.scala:29
- REDACTED
Serious — 63 finding(s)
- TodoComment http/src/test/scala/org/http4s/blaze/http/http2/ProtocolFrame.scala:21
- TodoComment http/src/main/scala/org/http4s/blaze/http/util/UrlTools.scala:24
- TodoComment http/src/main/scala/org/http4s/blaze/http/http2/Connection.scala:75
- TodoComment http/src/main/scala/org/http4s/blaze/http/http2/FrameDecoder.scala:356
- TodoComment http/src/main/scala/org/http4s/blaze/http/http2/PingManager.scala:42
- TodoComment http/src/main/scala/org/http4s/blaze/http/http2/SessionFrameListener.scala:103
- TodoComment http/src/main/scala/org/http4s/blaze/http/http2/SessionFrameListener.scala:117
- TodoComment http/src/main/scala/org/http4s/blaze/http/http2/StreamManager.scala:54
- TodoComment http/src/main/scala/org/http4s/blaze/http/http2/StreamManagerImpl.scala:49
- TodoComment http/src/main/scala/org/http4s/blaze/http/http2/StreamManagerImpl.scala:184
- TodoComment http/src/main/scala/org/http4s/blaze/http/http2/StreamManagerImpl.scala:211
- TodoComment http/src/main/scala/org/http4s/blaze/http/http2/StreamStateImpl.scala:168
- TodoComment http/src/main/scala/org/http4s/blaze/http/http2/WriteController.scala:23
- TodoComment http/src/main/scala/org/http4s/blaze/http/http2/WriteControllerImpl.scala:49
- TodoComment http/src/main/java/org/http4s/blaze/http/parser/BodyAndHeaderParser.java:441
- TodoComment examples/src/main/scala/com/example/http4s/HeaderExamples.scala:25
- TodoComment blaze-server/src/test/scala/org/http4s/blaze/server/AutoClosableResource.scala:21
- TodoComment blaze-server/src/test/scala/org/http4s/blaze/server/Http1ServerStageSpec.scala:54
- TodoComment blaze-server/src/main/scala/org/http4s/blaze/server/Http1ServerStage.scala:292
- TodoComment blaze-server/src/main/scala/org/http4s/blaze/server/Http2NodeStage.scala:200
- TodoComment blaze-server/src/main/scala/org/http4s/blaze/server/ProtocolSelector.scala:79
- TodoComment blaze-server/src/main/scala/org/http4s/blaze/server/WebSocketSupport.scala:117
- TodoComment blaze-core/src/main/scala/org/http4s/blazecore/Http1Stage.scala:246
- TodoComment blaze-client/src/test/scala/org/http4s/blaze/client/BlazeClientConnectionReuseSuite.scala:177
- TodoComment blaze-client/src/test/scala/org/http4s/blaze/client/Http1ClientStageSuite.scala:245
- MethodTooLong: BlazeServerBuilder.enableHttp2 blaze-server/src/main/scala/org/http4s/blaze/server/BlazeServerBuilder.scala:246
- MethodTooLong: BlazeServerBuilder.withHttpApp blaze-server/src/main/scala/org/http4s/blaze/server/BlazeServerBuilder.scala:249
- MethodTooLong: BlazeServerBuilder.withHttpWebSocketApp blaze-server/src/main/scala/org/http4s/blaze/server/BlazeServerBuilder.scala:252
- REDACTED
- REDACTED
- Http2NodeStage.checkAndRunRequest (cyclomatic 33) blaze-server/src/main/scala/org/http4s/blaze/server/Http2NodeStage.scala:169
- Http1ClientParser.parseResponseLine (cyclomatic 32) http/src/main/java/org/http4s/blaze/http/parser/Http1ClientParser.java:112
- BodyAndHeaderParser.parseHeaders (cyclomatic 31) http/src/main/java/org/http4s/blaze/http/parser/BodyAndHeaderParser.java:169
- Http1ServerParser.parseRequestLine (cyclomatic 28) http/src/main/java/org/http4s/blaze/http/parser/Http1ServerParser.java:121
- BodyAndHeaderParser.chunkedContent (cyclomatic 23) http/src/main/java/org/http4s/blaze/http/parser/BodyAndHeaderParser.java:347
- SSLStage.sslHandshake (cyclomatic 21) core/src/main/scala/org/http4s/blaze/pipeline/stages/SSLStage.scala:183
- Http1ServerStage.renderResponse (cyclomatic 20) blaze-server/src/main/scala/org/http4s/blaze/server/Http1ServerStage.scala:231
- FrameDecoder.doDecodeBuffer (cyclomatic 18) http/src/main/scala/org/http4s/blaze/http/http2/FrameDecoder.scala:37
- BodyAndHeaderParser.parseHeaders (cognitive 76) http/src/main/java/org/http4s/blaze/http/parser/BodyAndHeaderParser.java:169
- Http1ClientParser.parseResponseLine (cognitive 62) http/src/main/java/org/http4s/blaze/http/parser/Http1ClientParser.java:112
- BodyAndHeaderParser.chunkedContent (cognitive 54) http/src/main/java/org/http4s/blaze/http/parser/BodyAndHeaderParser.java:347
- Http2NodeStage.checkAndRunRequest (cognitive 52) blaze-server/src/main/scala/org/http4s/blaze/server/Http2NodeStage.scala:169
- Http1ServerParser.parseRequestLine (cognitive 52) http/src/main/java/org/http4s/blaze/http/parser/Http1ServerParser.java:121
- Http1ServerStage.renderResponse (cognitive 27) blaze-server/src/main/scala/org/http4s/blaze/server/Http1ServerStage.scala:231
- Http1Stage.getEncoder (cognitive 25) blaze-core/src/main/scala/org/http4s/blazecore/Http1Stage.scala:139
- BlazeServerBuilder.pipelineFactory (cognitive 25) blaze-server/src/main/scala/org/http4s/blaze/server/BlazeServerBuilder.scala:279
- BlazeServerBuilder.resource (cognitive 24) blaze-server/src/main/scala/org/http4s/blaze/server/BlazeServerBuilder.scala:388
- BlazeClientBuilder.resourceWithState (cognitive 21) blaze-client/src/main/scala/org/http4s/blaze/client/BlazeClientBuilder.scala:338
- SSLStage.sslHandshake (cognitive 20) core/src/main/scala/org/http4s/blaze/pipeline/stages/SSLStage.scala:183
- HeaderAggregatingFrameListener.onContinuationFrame (cognitive 19) http/src/main/scala/org/http4s/blaze/http/http2/HeaderAggregatingFrameListener.scala:144
- TickWheelExecutor.schedule (cognitive 17) core/src/main/scala/org/http4s/blaze/util/TickWheelExecutor.scala:116
- Http1Connection.parsePreludeFinished (cognitive 16) blaze-client/src/main/scala/org/http4s/blaze/client/Http1Connection.scala:335
- ParserBase.getTrimmedString (cognitive 16) http/src/main/java/org/http4s/blaze/http/parser/ParserBase.java:95
- TooManyMethods: BlazeClientBuilder blaze-client/src/main/scala/org/http4s/blaze/client/BlazeClientBuilder.scala:72
- REDACTED
- REDACTED
- Duplicated block (21 lines × 2) blaze-client/src/main/scala/org/http4s/blaze/client/BlazeClientBuilder.scala:128
- Duplicated block (12–13 lines × 2) core/src/main/scala/org/http4s/blaze/util/GenericSSLContext.scala:51
- Off the main sequence: blaze-core
- Low cohesion: ServerStatusStage (LCOM4 5) core/src/main/scala/org/http4s/blaze/pipeline/stages/monitors/ConnectionMonitor.scala:40
- README may be stale
Minor — 16 finding(s)
- Duplicated predicate http/src/main/java/org/http4s/blaze/http/parser/Http1ClientParser.java:125
- Duplicated predicate http/src/main/java/org/http4s/blaze/http/parser/Http1ClientParser.java:156
- Duplicated predicate blaze-client/src/main/scala/org/http4s/blaze/client/BlazeClientBuilder.scala:392
- Off-boarding risk: anonymized user #1
- Further sole-owners (lower concentration)
- No ADRs found
- Projects may be oversized for their cohesion
- REDACTED
- REDACTED
- REDACTED
- Disabled test blaze-client/src/test/scala/org/http4s/blaze/client/Http1ClientStageSuite.scala:246
- No ADRs
- No architecture diagram/doc
- Large public API surface
- No changelog
- 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-a10dc66c572a48b58d9997cd4b4bdd0c/history.json --exit-code 0 --source . | 1 | 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-a10dc66c572a48b58d9997cd4b4bdd0c/tree.json --exit-code 0 --source . | 1 | 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 . | 18 | 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-3f68d8647704476caedd3964d081bc96 | 0 | artifacts/raw/osv-scanner.json |
| D31 · IaC & Container Security | trivy | — | trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan. | 0 | — |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. | 0 | — |
| D37 · Vulnerability-disclosure Policy | disclosure | — | disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . /tmp/codehealth-osv-sbom-3f68d8647704476caedd3964d081bc96 | 0 | artifacts/raw/osv-scanner.json |