Executive summary
fs-fio/fio meets our standard for a preview release. It scores 72 out of 100 and is rated Strong, and its one critical finding is a security problem in its automatic dependency updates.
Every lens scores high enough to be rated Strong, so no single lens holds the score back. The best first step is recording design decisions, worth about 6 points. Adding test instructions to the README comes next, worth about 3 points.
One automatic update takes new releases before a bad one can be spotted. Setting a waiting period for automatic updates would close this risk.
The product code is 10,735 lines, about €42,000 to rebuild.
Every lens already scores high enough to be rated Strong, so no single lens holds the score back.
Rebuild cost: about €42,000 · Estimate
| Cost to rebuild | €14,000 to €70,000, for 232 to 737 hours of work, about 0.3 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 | ×1.0 at a score of 72. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it. |
| Size | Small: 10,735 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 DSL | 2 Console.Console | 3 DSL.CE | 4 DSL.Extensions | 5 DSL.FIO | 6 DSL.Operators | 7 Runtime | 8 Sockets | 9 WebSockets | 10 App | 11 Runtime.Direct | 12 Runtime.Polling | 13 Runtime.Signaling | 14 Runtime.WorkStealing | 15 Sockets.ServerSocketConfigModule | 16 Sockets.ServerSocketModule | 17 Sockets.SocketClient | 18 Sockets.SocketConfigModule | 19 Sockets.SocketExtensions | 20 Sockets.SocketPoolConfigModule | 21 WebSockets.WebSocketClient | 22 WebSockets.WebSocketExtensions | 23 WebSockets.WebSocketServer | 24 Http | 25 Http.HttpErrorModule | 26 Http.HttpHandler | 27 Http.HttpMethodModule | 28 Http.HttpRequestModule | 29 Http.HttpResponseModule | 30 Http.KestrelBridge | 31 Http.Middleware | 32 Http.MiddlewareOperators | 33 Http.Response | 34 Http.Route | 35 Http.RouteBuilder | 36 Http.RouteOperators | 37 Http.RoutePathModule | 38 Http.Routes | 39 Http.Server | 40 Http.ServerBuilder |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 DSL | ||||||||||||||||||||||||||||||||||||||||
| 2 Console.Console | 1 | |||||||||||||||||||||||||||||||||||||||
| 3 DSL.CE | 1 | |||||||||||||||||||||||||||||||||||||||
| 4 DSL.Extensions | 1 | |||||||||||||||||||||||||||||||||||||||
| 5 DSL.FIO | 4 | |||||||||||||||||||||||||||||||||||||||
| 6 DSL.Operators | 1 | |||||||||||||||||||||||||||||||||||||||
| 7 Runtime | 9 | |||||||||||||||||||||||||||||||||||||||
| 8 Sockets | 1 | |||||||||||||||||||||||||||||||||||||||
| 9 WebSockets | 1 | |||||||||||||||||||||||||||||||||||||||
| 10 App | 2 | 1 | ||||||||||||||||||||||||||||||||||||||
| 11 Runtime.Direct | 3 | 1 | ||||||||||||||||||||||||||||||||||||||
| 12 Runtime.Polling | 10 | 2 | ||||||||||||||||||||||||||||||||||||||
| 13 Runtime.Signaling | 6 | 2 | ||||||||||||||||||||||||||||||||||||||
| 14 Runtime.WorkStealing | 8 | 2 | ||||||||||||||||||||||||||||||||||||||
| 15 Sockets.ServerSocketConfigModule | 1 | 3 | ||||||||||||||||||||||||||||||||||||||
| 16 Sockets.ServerSocketModule | 2 | 5 | ||||||||||||||||||||||||||||||||||||||
| 17 Sockets.SocketClient | 1 | 4 | ||||||||||||||||||||||||||||||||||||||
| 18 Sockets.SocketConfigModule | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 19 Sockets.SocketExtensions | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 20 Sockets.SocketPoolConfigModule | 1 | 3 | ||||||||||||||||||||||||||||||||||||||
| 21 WebSockets.WebSocketClient | 1 | 3 | ||||||||||||||||||||||||||||||||||||||
| 22 WebSockets.WebSocketExtensions | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 23 WebSockets.WebSocketServer | 3 | 6 | ||||||||||||||||||||||||||||||||||||||
| 24 Http | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 25 Http.HttpErrorModule | 1 | |||||||||||||||||||||||||||||||||||||||
| 26 Http.HttpHandler | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 27 Http.HttpMethodModule | 1 | |||||||||||||||||||||||||||||||||||||||
| 28 Http.HttpRequestModule | 3 | |||||||||||||||||||||||||||||||||||||||
| 29 Http.HttpResponseModule | 3 | |||||||||||||||||||||||||||||||||||||||
| 30 Http.KestrelBridge | 1 | 5 | ||||||||||||||||||||||||||||||||||||||
| 31 Http.Middleware | 1 | |||||||||||||||||||||||||||||||||||||||
| 32 Http.MiddlewareOperators | 1 | |||||||||||||||||||||||||||||||||||||||
| 33 Http.Response | 2 | |||||||||||||||||||||||||||||||||||||||
| 34 Http.Route | 1 | |||||||||||||||||||||||||||||||||||||||
| 35 Http.RouteBuilder | 1 | |||||||||||||||||||||||||||||||||||||||
| 36 Http.RouteOperators | 2 | |||||||||||||||||||||||||||||||||||||||
| 37 Http.RoutePathModule | 1 | |||||||||||||||||||||||||||||||||||||||
| 38 Http.Routes | 1 | 6 | ||||||||||||||||||||||||||||||||||||||
| 39 Http.Server | 1 | 1 | 3 | |||||||||||||||||||||||||||||||||||||
| 40 Http.ServerBuilder | 1 | 3 |
2→1 Console.Console uses DSL✕
- Connections
- 1 pair of types, where a type in Console.Console uses a type in DSL.
- The types involved
FIO.Console.Console.Console→FIO.DSL.FIO`2
- Direction
- Console.Console uses DSL, so a change to DSL can break Console.Console, while a change to Console.Console can't break DSL.
- Position
- Below the diagonal: Console.Console uses a module listed above it, which is the healthy direction.
3→1 DSL.CE uses DSL✕
- Connections
- 1 pair of types, where a type in DSL.CE uses a type in DSL.
- The types involved
FIO.DSL.CE.FIOBuilder→FIO.DSL.FIO`2
- Direction
- DSL.CE uses DSL, so a change to DSL can break DSL.CE, while a change to DSL.CE can't break DSL.
- Position
- Below the diagonal: DSL.CE uses a module listed above it, which is the healthy direction.
4→1 DSL.Extensions uses DSL✕
- Connections
- 1 pair of types, where a type in DSL.Extensions uses a type in DSL.
- The types involved
FIO.DSL.Extensions.Extensions→FIO.DSL.FIO`2
- Direction
- DSL.Extensions uses DSL, so a change to DSL can break DSL.Extensions, while a change to DSL.Extensions can't break DSL.
- Position
- Below the diagonal: DSL.Extensions uses a module listed above it, which is the healthy direction.
5→1 DSL.FIO uses DSL✕
- Connections
- 4 pairs of types, where a type in DSL.FIO uses a type in DSL.
- The types involved
FIO.DSL.FIO.FIO→FIO.DSL.FIO`2FIO.DSL.FIO.FIO→FIO.DSL.FiberContextFIO.DSL.FIO.FIO→FIO.DSL.Fiber`2FIO.DSL.FIO.FIO→FIO.DSL.InterruptionCause
- Direction
- DSL.FIO uses DSL, so a change to DSL can break DSL.FIO, while a change to DSL.FIO can't break DSL.
- Position
- Below the diagonal: DSL.FIO uses a module listed above it, which is the healthy direction.
6→1 DSL.Operators uses DSL✕
- Connections
- 1 pair of types, where a type in DSL.Operators uses a type in DSL.
- The types involved
FIO.DSL.Operators.Operators→FIO.DSL.FIO`2
- Direction
- DSL.Operators uses DSL, so a change to DSL can break DSL.Operators, while a change to DSL.Operators can't break DSL.
- Position
- Below the diagonal: DSL.Operators uses a module listed above it, which is the healthy direction.
7→1 Runtime uses DSL✕
- Connections
- 9 pairs of types, where a type in Runtime uses a type in DSL.
- The types involved
FIO.Runtime.ContStackPool→FIO.DSL.ContFIO.Runtime.FIORuntime→FIO.DSL.FIO`2FIO.Runtime.FIORuntime→FIO.DSL.FiberContextFIO.Runtime.FIORuntime→FIO.DSL.Fiber`2FIO.Runtime.WorkItemPool→FIO.DSL.ContFIO.Runtime.WorkItemPool→FIO.DSL.FIO`2FIO.Runtime.WorkItemPool→FIO.DSL.FiberContextFIO.Runtime.WorkItemPool→FIO.DSL.WorkItemFIO.Runtime.WorkStealingDeque→FIO.DSL.WorkItem
- Direction
- Runtime uses DSL, so a change to DSL can break Runtime, while a change to Runtime can't break DSL.
- Position
- Below the diagonal: Runtime uses a module listed above it, which is the healthy direction.
8→1 Sockets uses DSL✕
- Connections
- 1 pair of types, where a type in Sockets uses a type in DSL.
- The types involved
FIO.Sockets.Socket→FIO.DSL.FIO`2
- Direction
- Sockets uses DSL, so a change to DSL can break Sockets, while a change to Sockets can't break DSL.
- Position
- Below the diagonal: Sockets uses a module listed above it, which is the healthy direction.
9→1 WebSockets uses DSL✕
- Connections
- 1 pair of types, where a type in WebSockets uses a type in DSL.
- The types involved
FIO.WebSockets.WebSocket→FIO.DSL.FIO`2
- Direction
- WebSockets uses DSL, so a change to DSL can break WebSockets, while a change to WebSockets can't break DSL.
- Position
- Below the diagonal: WebSockets uses a module listed above it, which is the healthy direction.
10→1 App uses DSL✕
- Connections
- 2 pairs of types, where a type in App uses a type in DSL.
- The types involved
FIO.App.AppResult`2→FIO.DSL.FiberInterruptedExceptionFIO.App.FIOApp`2→FIO.DSL.FIO`2
- Direction
- App uses DSL, so a change to DSL can break App, while a change to App can't break DSL.
- Position
- Below the diagonal: App uses a module listed above it, which is the healthy direction.
10→7 App uses Runtime✕
- Connections
- 1 pair of types, where a type in App uses a type in Runtime.
- The types involved
FIO.App.FIOApp`2→FIO.Runtime.FIORuntime
- Direction
- App uses Runtime, so a change to Runtime can break App, while a change to App can't break Runtime.
- Position
- Below the diagonal: App uses a module listed above it, which is the healthy direction.
11→1 Runtime.Direct uses DSL✕
- Connections
- 3 pairs of types, where a type in Runtime.Direct uses a type in DSL.
- The types involved
FIO.Runtime.Direct.DirectRuntime→FIO.DSL.FIO`2FIO.Runtime.Direct.DirectRuntime→FIO.DSL.FiberContextFIO.Runtime.Direct.DirectRuntime→FIO.DSL.Fiber`2
- Direction
- Runtime.Direct uses DSL, so a change to DSL can break Runtime.Direct, while a change to Runtime.Direct can't break DSL.
- Position
- Below the diagonal: Runtime.Direct uses a module listed above it, which is the healthy direction.
11→7 Runtime.Direct uses Runtime✕
- Connections
- 1 pair of types, where a type in Runtime.Direct uses a type in Runtime.
- The types involved
FIO.Runtime.Direct.DirectRuntime→FIO.Runtime.FIORuntime
- Direction
- Runtime.Direct uses Runtime, so a change to Runtime can break Runtime.Direct, while a change to Runtime.Direct can't break Runtime.
- Position
- Below the diagonal: Runtime.Direct uses a module listed above it, which is the healthy direction.
12→1 Runtime.Polling uses DSL✕
- Connections
- 10 pairs of types, where a type in Runtime.Polling uses a type in DSL.
- The types involved
FIO.Runtime.Polling.BlockingEntry→FIO.DSL.BlockingItemFIO.Runtime.Polling.BlockingWorker→FIO.DSL.BlockingItemFIO.Runtime.Polling.BlockingWorkerConfig→FIO.DSL.MailboxQueue`1FIO.Runtime.Polling.BlockingWorkerConfig→FIO.DSL.WorkItemFIO.Runtime.Polling.EvaluationWorkerConfig→FIO.DSL.MailboxQueue`1FIO.Runtime.Polling.EvaluationWorkerConfig→FIO.DSL.WorkItemFIO.Runtime.Polling.PollingRuntime→FIO.DSL.FIO`2FIO.Runtime.Polling.PollingRuntime→FIO.DSL.Fiber`2FIO.Runtime.Polling.PollingRuntime→FIO.DSL.MailboxQueue`1FIO.Runtime.Polling.PollingRuntime→FIO.DSL.WorkItem
- Direction
- Runtime.Polling uses DSL, so a change to DSL can break Runtime.Polling, while a change to Runtime.Polling can't break DSL.
- Position
- Below the diagonal: Runtime.Polling uses a module listed above it, which is the healthy direction.
12→7 Runtime.Polling uses Runtime✕
- Connections
- 2 pairs of types, where a type in Runtime.Polling uses a type in Runtime.
- The types involved
FIO.Runtime.Polling.PollingRuntime→FIO.Runtime.FIOWorkerRuntimeFIO.Runtime.Polling.PollingRuntime→FIO.Runtime.WorkerConfig
- Direction
- Runtime.Polling uses Runtime, so a change to Runtime can break Runtime.Polling, while a change to Runtime.Polling can't break Runtime.
- Position
- Below the diagonal: Runtime.Polling uses a module listed above it, which is the healthy direction.
13→1 Runtime.Signaling uses DSL✕
- Connections
- 6 pairs of types, where a type in Runtime.Signaling uses a type in DSL.
- The types involved
FIO.Runtime.Signaling.EvaluationWorkerConfig→FIO.DSL.MailboxQueue`1FIO.Runtime.Signaling.EvaluationWorkerConfig→FIO.DSL.WorkItemFIO.Runtime.Signaling.SignalingRuntime→FIO.DSL.FIO`2FIO.Runtime.Signaling.SignalingRuntime→FIO.DSL.Fiber`2FIO.Runtime.Signaling.SignalingRuntime→FIO.DSL.MailboxQueue`1FIO.Runtime.Signaling.SignalingRuntime→FIO.DSL.WorkItem
- Direction
- Runtime.Signaling uses DSL, so a change to DSL can break Runtime.Signaling, while a change to Runtime.Signaling can't break DSL.
- Position
- Below the diagonal: Runtime.Signaling uses a module listed above it, which is the healthy direction.
13→7 Runtime.Signaling uses Runtime✕
- Connections
- 2 pairs of types, where a type in Runtime.Signaling uses a type in Runtime.
- The types involved
FIO.Runtime.Signaling.SignalingRuntime→FIO.Runtime.FIOWorkerRuntimeFIO.Runtime.Signaling.SignalingRuntime→FIO.Runtime.WorkerConfig
- Direction
- Runtime.Signaling uses Runtime, so a change to Runtime can break Runtime.Signaling, while a change to Runtime.Signaling can't break Runtime.
- Position
- Below the diagonal: Runtime.Signaling uses a module listed above it, which is the healthy direction.
14→1 Runtime.WorkStealing uses DSL✕
- Connections
- 8 pairs of types, where a type in Runtime.WorkStealing uses a type in DSL.
- The types involved
FIO.Runtime.WorkStealing.Scheduler→FIO.DSL.ContFIO.Runtime.WorkStealing.Scheduler→FIO.DSL.FIO`2FIO.Runtime.WorkStealing.Scheduler→FIO.DSL.FiberContextFIO.Runtime.WorkStealing.Scheduler→FIO.DSL.MailboxQueue`1FIO.Runtime.WorkStealing.Scheduler→FIO.DSL.WorkItemFIO.Runtime.WorkStealing.WorkStealingRuntime→FIO.DSL.FIO`2FIO.Runtime.WorkStealing.WorkStealingRuntime→FIO.DSL.Fiber`2FIO.Runtime.WorkStealing.WorkStealingRuntime→FIO.DSL.WorkItem
- Direction
- Runtime.WorkStealing uses DSL, so a change to DSL can break Runtime.WorkStealing, while a change to Runtime.WorkStealing can't break DSL.
- Position
- Below the diagonal: Runtime.WorkStealing uses a module listed above it, which is the healthy direction.
14→7 Runtime.WorkStealing uses Runtime✕
- Connections
- 2 pairs of types, where a type in Runtime.WorkStealing uses a type in Runtime.
- The types involved
FIO.Runtime.WorkStealing.WorkStealingRuntime→FIO.Runtime.FIOWorkerRuntimeFIO.Runtime.WorkStealing.WorkStealingRuntime→FIO.Runtime.WorkerConfig
- Direction
- Runtime.WorkStealing uses Runtime, so a change to Runtime can break Runtime.WorkStealing, while a change to Runtime.WorkStealing can't break Runtime.
- Position
- Below the diagonal: Runtime.WorkStealing uses a module listed above it, which is the healthy direction.
15→1 Sockets.ServerSocketConfigModule uses DSL✕
- Connections
- 1 pair of types, where a type in Sockets.ServerSocketConfigModule uses a type in DSL.
- The types involved
FIO.Sockets.ServerSocketConfigModule.ServerSocketConfigModule→FIO.DSL.FIO`2
- Direction
- Sockets.ServerSocketConfigModule uses DSL, so a change to DSL can break Sockets.ServerSocketConfigModule, while a change to Sockets.ServerSocketConfigModule can't break DSL.
- Position
- Below the diagonal: Sockets.ServerSocketConfigModule uses a module listed above it, which is the healthy direction.
15→8 Sockets.ServerSocketConfigModule uses Sockets✕
- Connections
- 3 pairs of types, where a type in Sockets.ServerSocketConfigModule uses a type in Sockets.
- The types involved
FIO.Sockets.ServerSocketConfigModule.ServerSocketConfigModule→FIO.Sockets.ServerSocketConfigFIO.Sockets.ServerSocketConfigModule.ServerSocketConfigModule→FIO.Sockets.SocketConfigFIO.Sockets.ServerSocketConfigModule.ServerSocketConfigModule→FIO.Sockets.SocketError
- Direction
- Sockets.ServerSocketConfigModule uses Sockets, so a change to Sockets can break Sockets.ServerSocketConfigModule, while a change to Sockets.ServerSocketConfigModule can't break Sockets.
- Position
- Below the diagonal: Sockets.ServerSocketConfigModule uses a module listed above it, which is the healthy direction.
16→1 Sockets.ServerSocketModule uses DSL✕
- Connections
- 2 pairs of types, where a type in Sockets.ServerSocketModule uses a type in DSL.
- The types involved
FIO.Sockets.ServerSocketModule.ServerSocketModule→FIO.DSL.FIO`2FIO.Sockets.ServerSocketModule.ServerSocketModule→FIO.DSL.Fiber`2
- Direction
- Sockets.ServerSocketModule uses DSL, so a change to DSL can break Sockets.ServerSocketModule, while a change to Sockets.ServerSocketModule can't break DSL.
- Position
- Below the diagonal: Sockets.ServerSocketModule uses a module listed above it, which is the healthy direction.
16→8 Sockets.ServerSocketModule uses Sockets✕
- Connections
- 5 pairs of types, where a type in Sockets.ServerSocketModule uses a type in Sockets.
- The types involved
FIO.Sockets.ServerSocketModule.ServerSocketModule→FIO.Sockets.ServerSocketFIO.Sockets.ServerSocketModule.ServerSocketModule→FIO.Sockets.ServerSocketConfigFIO.Sockets.ServerSocketModule.ServerSocketModule→FIO.Sockets.SocketFIO.Sockets.ServerSocketModule.ServerSocketModule→FIO.Sockets.SocketCodec`1FIO.Sockets.ServerSocketModule.ServerSocketModule→FIO.Sockets.SocketError
- Direction
- Sockets.ServerSocketModule uses Sockets, so a change to Sockets can break Sockets.ServerSocketModule, while a change to Sockets.ServerSocketModule can't break Sockets.
- Position
- Below the diagonal: Sockets.ServerSocketModule uses a module listed above it, which is the healthy direction.
17→1 Sockets.SocketClient uses DSL✕
- Connections
- 1 pair of types, where a type in Sockets.SocketClient uses a type in DSL.
- The types involved
FIO.Sockets.SocketClient.SocketClient→FIO.DSL.FIO`2
- Direction
- Sockets.SocketClient uses DSL, so a change to DSL can break Sockets.SocketClient, while a change to Sockets.SocketClient can't break DSL.
- Position
- Below the diagonal: Sockets.SocketClient uses a module listed above it, which is the healthy direction.
17→8 Sockets.SocketClient uses Sockets✕
- Connections
- 4 pairs of types, where a type in Sockets.SocketClient uses a type in Sockets.
- The types involved
FIO.Sockets.SocketClient.SocketClient→FIO.Sockets.SocketFIO.Sockets.SocketClient.SocketClient→FIO.Sockets.SocketCodec`1FIO.Sockets.SocketClient.SocketClient→FIO.Sockets.SocketConfigFIO.Sockets.SocketClient.SocketClient→FIO.Sockets.SocketError
- Direction
- Sockets.SocketClient uses Sockets, so a change to Sockets can break Sockets.SocketClient, while a change to Sockets.SocketClient can't break Sockets.
- Position
- Below the diagonal: Sockets.SocketClient uses a module listed above it, which is the healthy direction.
18→1 Sockets.SocketConfigModule uses DSL✕
- Connections
- 1 pair of types, where a type in Sockets.SocketConfigModule uses a type in DSL.
- The types involved
FIO.Sockets.SocketConfigModule.SocketConfigModule→FIO.DSL.FIO`2
- Direction
- Sockets.SocketConfigModule uses DSL, so a change to DSL can break Sockets.SocketConfigModule, while a change to Sockets.SocketConfigModule can't break DSL.
- Position
- Below the diagonal: Sockets.SocketConfigModule uses a module listed above it, which is the healthy direction.
18→8 Sockets.SocketConfigModule uses Sockets✕
- Connections
- 2 pairs of types, where a type in Sockets.SocketConfigModule uses a type in Sockets.
- The types involved
FIO.Sockets.SocketConfigModule.SocketConfigModule→FIO.Sockets.SocketConfigFIO.Sockets.SocketConfigModule.SocketConfigModule→FIO.Sockets.SocketError
- Direction
- Sockets.SocketConfigModule uses Sockets, so a change to Sockets can break Sockets.SocketConfigModule, while a change to Sockets.SocketConfigModule can't break Sockets.
- Position
- Below the diagonal: Sockets.SocketConfigModule uses a module listed above it, which is the healthy direction.
19→1 Sockets.SocketExtensions uses DSL✕
- Connections
- 1 pair of types, where a type in Sockets.SocketExtensions uses a type in DSL.
- The types involved
FIO.Sockets.SocketExtensions.SocketExtensions→FIO.DSL.FIO`2
- Direction
- Sockets.SocketExtensions uses DSL, so a change to DSL can break Sockets.SocketExtensions, while a change to Sockets.SocketExtensions can't break DSL.
- Position
- Below the diagonal: Sockets.SocketExtensions uses a module listed above it, which is the healthy direction.
19→8 Sockets.SocketExtensions uses Sockets✕
- Connections
- 1 pair of types, where a type in Sockets.SocketExtensions uses a type in Sockets.
- The types involved
FIO.Sockets.SocketExtensions.SocketExtensions→FIO.Sockets.SocketError
- Direction
- Sockets.SocketExtensions uses Sockets, so a change to Sockets can break Sockets.SocketExtensions, while a change to Sockets.SocketExtensions can't break Sockets.
- Position
- Below the diagonal: Sockets.SocketExtensions uses a module listed above it, which is the healthy direction.
20→1 Sockets.SocketPoolConfigModule uses DSL✕
- Connections
- 1 pair of types, where a type in Sockets.SocketPoolConfigModule uses a type in DSL.
- The types involved
FIO.Sockets.SocketPoolConfigModule.SocketPoolConfigModule→FIO.DSL.FIO`2
- Direction
- Sockets.SocketPoolConfigModule uses DSL, so a change to DSL can break Sockets.SocketPoolConfigModule, while a change to Sockets.SocketPoolConfigModule can't break DSL.
- Position
- Below the diagonal: Sockets.SocketPoolConfigModule uses a module listed above it, which is the healthy direction.
20→8 Sockets.SocketPoolConfigModule uses Sockets✕
- Connections
- 3 pairs of types, where a type in Sockets.SocketPoolConfigModule uses a type in Sockets.
- The types involved
FIO.Sockets.SocketPoolConfigModule.SocketPoolConfigModule→FIO.Sockets.SocketConfigFIO.Sockets.SocketPoolConfigModule.SocketPoolConfigModule→FIO.Sockets.SocketErrorFIO.Sockets.SocketPoolConfigModule.SocketPoolConfigModule→FIO.Sockets.SocketPoolConfig
- Direction
- Sockets.SocketPoolConfigModule uses Sockets, so a change to Sockets can break Sockets.SocketPoolConfigModule, while a change to Sockets.SocketPoolConfigModule can't break Sockets.
- Position
- Below the diagonal: Sockets.SocketPoolConfigModule uses a module listed above it, which is the healthy direction.
21→1 WebSockets.WebSocketClient uses DSL✕
- Connections
- 1 pair of types, where a type in WebSockets.WebSocketClient uses a type in DSL.
- The types involved
FIO.WebSockets.WebSocketClient.WebSocketClient→FIO.DSL.FIO`2
- Direction
- WebSockets.WebSocketClient uses DSL, so a change to DSL can break WebSockets.WebSocketClient, while a change to WebSockets.WebSocketClient can't break DSL.
- Position
- Below the diagonal: WebSockets.WebSocketClient uses a module listed above it, which is the healthy direction.
21→9 WebSockets.WebSocketClient uses WebSockets✕
- Connections
- 3 pairs of types, where a type in WebSockets.WebSocketClient uses a type in WebSockets.
- The types involved
FIO.WebSockets.WebSocketClient.WebSocketClient→FIO.WebSockets.WebSocketFIO.WebSockets.WebSocketClient.WebSocketClient→FIO.WebSockets.WebSocketConfigFIO.WebSockets.WebSocketClient.WebSocketClient→FIO.WebSockets.WsError
- Direction
- WebSockets.WebSocketClient uses WebSockets, so a change to WebSockets can break WebSockets.WebSocketClient, while a change to WebSockets.WebSocketClient can't break WebSockets.
- Position
- Below the diagonal: WebSockets.WebSocketClient uses a module listed above it, which is the healthy direction.
22→1 WebSockets.WebSocketExtensions uses DSL✕
- Connections
- 1 pair of types, where a type in WebSockets.WebSocketExtensions uses a type in DSL.
- The types involved
FIO.WebSockets.WebSocketExtensions.WebSocketExtensions→FIO.DSL.FIO`2
- Direction
- WebSockets.WebSocketExtensions uses DSL, so a change to DSL can break WebSockets.WebSocketExtensions, while a change to WebSockets.WebSocketExtensions can't break DSL.
- Position
- Below the diagonal: WebSockets.WebSocketExtensions uses a module listed above it, which is the healthy direction.
22→9 WebSockets.WebSocketExtensions uses WebSockets✕
- Connections
- 1 pair of types, where a type in WebSockets.WebSocketExtensions uses a type in WebSockets.
- The types involved
FIO.WebSockets.WebSocketExtensions.WebSocketExtensions→FIO.WebSockets.WsError
- Direction
- WebSockets.WebSocketExtensions uses WebSockets, so a change to WebSockets can break WebSockets.WebSocketExtensions, while a change to WebSockets.WebSocketExtensions can't break WebSockets.
- Position
- Below the diagonal: WebSockets.WebSocketExtensions uses a module listed above it, which is the healthy direction.
23→1 WebSockets.WebSocketServer uses DSL✕
- Connections
- 3 pairs of types, where a type in WebSockets.WebSocketServer uses a type in DSL.
- The types involved
FIO.WebSockets.WebSocketServer.Connection→FIO.DSL.Fiber`2FIO.WebSockets.WebSocketServer.WebSocketServer→FIO.DSL.FIO`2FIO.WebSockets.WebSocketServer.WebSocketServer→FIO.DSL.Fiber`2
- Direction
- WebSockets.WebSocketServer uses DSL, so a change to DSL can break WebSockets.WebSocketServer, while a change to WebSockets.WebSocketServer can't break DSL.
- Position
- Below the diagonal: WebSockets.WebSocketServer uses a module listed above it, which is the healthy direction.
23→9 WebSockets.WebSocketServer uses WebSockets✕
- Connections
- 6 pairs of types, where a type in WebSockets.WebSocketServer uses a type in WebSockets.
- The types involved
FIO.WebSockets.WebSocketServer.Connection→FIO.WebSockets.WebSocketFIO.WebSockets.WebSocketServer.Connection→FIO.WebSockets.WsErrorFIO.WebSockets.WebSocketServer.WebSocketServer→FIO.WebSockets.WebSocketFIO.WebSockets.WebSocketServer.WebSocketServer→FIO.WebSockets.WebSocketCodec`1FIO.WebSockets.WebSocketServer.WebSocketServer→FIO.WebSockets.WebSocketConfigFIO.WebSockets.WebSocketServer.WebSocketServer→FIO.WebSockets.WsError
- Direction
- WebSockets.WebSocketServer uses WebSockets, so a change to WebSockets can break WebSockets.WebSocketServer, while a change to WebSockets.WebSocketServer can't break WebSockets.
- Position
- Below the diagonal: WebSockets.WebSocketServer uses a module listed above it, which is the healthy direction.
24→1 Http uses DSL✕
- Connections
- 1 pair of types, where a type in Http uses a type in DSL.
- The types involved
FIO.Http.RequestTracker→FIO.DSL.Fiber`2
- Direction
- Http uses DSL, so a change to DSL can break Http, while a change to Http can't break DSL.
- Position
- Below the diagonal: Http uses a module listed above it, which is the healthy direction.
24→14 Http uses Runtime.WorkStealing✕
- Connections
- 2 pairs of types, where a type in Http uses a type in Runtime.WorkStealing.
- The types involved
FIO.Http.FIOServer→FIO.Runtime.WorkStealing.WorkStealingRuntimeFIO.Http.RequestTracker→FIO.Runtime.WorkStealing.WorkStealingRuntime
- Direction
- Http uses Runtime.WorkStealing, so a change to Runtime.WorkStealing can break Http, while a change to Http can't break Runtime.WorkStealing.
- Position
- Below the diagonal: Http uses a module listed above it, which is the healthy direction.
25→24 Http.HttpErrorModule uses Http✕
- Connections
- 1 pair of types, where a type in Http.HttpErrorModule uses a type in Http.
- The types involved
FIO.Http.HttpErrorModule.HttpErrorModule→FIO.Http.HttpError
- Direction
- Http.HttpErrorModule uses Http, so a change to Http can break Http.HttpErrorModule, while a change to Http.HttpErrorModule can't break Http.
- Position
- Below the diagonal: Http.HttpErrorModule uses a module listed above it, which is the healthy direction.
26→1 Http.HttpHandler uses DSL✕
- Connections
- 1 pair of types, where a type in Http.HttpHandler uses a type in DSL.
- The types involved
FIO.Http.HttpHandler.HttpHandler→FIO.DSL.FIO`2
- Direction
- Http.HttpHandler uses DSL, so a change to DSL can break Http.HttpHandler, while a change to Http.HttpHandler can't break DSL.
- Position
- Below the diagonal: Http.HttpHandler uses a module listed above it, which is the healthy direction.
26→24 Http.HttpHandler uses Http✕
- Connections
- 2 pairs of types, where a type in Http.HttpHandler uses a type in Http.
- The types involved
FIO.Http.HttpHandler.HttpHandler→FIO.Http.HttpRequestFIO.Http.HttpHandler.HttpHandler→FIO.Http.HttpResponse
- Direction
- Http.HttpHandler uses Http, so a change to Http can break Http.HttpHandler, while a change to Http.HttpHandler can't break Http.
- Position
- Below the diagonal: Http.HttpHandler uses a module listed above it, which is the healthy direction.
27→24 Http.HttpMethodModule uses Http✕
- Connections
- 1 pair of types, where a type in Http.HttpMethodModule uses a type in Http.
- The types involved
FIO.Http.HttpMethodModule.HttpMethodModule→FIO.Http.HttpMethod
- Direction
- Http.HttpMethodModule uses Http, so a change to Http can break Http.HttpMethodModule, while a change to Http.HttpMethodModule can't break Http.
- Position
- Below the diagonal: Http.HttpMethodModule uses a module listed above it, which is the healthy direction.
28→24 Http.HttpRequestModule uses Http✕
- Connections
- 3 pairs of types, where a type in Http.HttpRequestModule uses a type in Http.
- The types involved
FIO.Http.HttpRequestModule.HttpRequestModule→FIO.Http.HttpMethodFIO.Http.HttpRequestModule.HttpRequestModule→FIO.Http.HttpRequestFIO.Http.HttpRequestModule.HttpRequestModule→FIO.Http.RequestBody
- Direction
- Http.HttpRequestModule uses Http, so a change to Http can break Http.HttpRequestModule, while a change to Http.HttpRequestModule can't break Http.
- Position
- Below the diagonal: Http.HttpRequestModule uses a module listed above it, which is the healthy direction.
29→24 Http.HttpResponseModule uses Http✕
- Connections
- 3 pairs of types, where a type in Http.HttpResponseModule uses a type in Http.
- The types involved
FIO.Http.HttpResponseModule.HttpResponseModule→FIO.Http.HttpResponseFIO.Http.HttpResponseModule.HttpResponseModule→FIO.Http.HttpStatusCodeFIO.Http.HttpResponseModule.HttpResponseModule→FIO.Http.ResponseBody
- Direction
- Http.HttpResponseModule uses Http, so a change to Http can break Http.HttpResponseModule, while a change to Http.HttpResponseModule can't break Http.
- Position
- Below the diagonal: Http.HttpResponseModule uses a module listed above it, which is the healthy direction.
30→14 Http.KestrelBridge uses Runtime.WorkStealing✕
- Connections
- 1 pair of types, where a type in Http.KestrelBridge uses a type in Runtime.WorkStealing.
- The types involved
FIO.Http.KestrelBridge.KestrelBridge→FIO.Runtime.WorkStealing.WorkStealingRuntime
- Direction
- Http.KestrelBridge uses Runtime.WorkStealing, so a change to Runtime.WorkStealing can break Http.KestrelBridge, while a change to Http.KestrelBridge can't break Runtime.WorkStealing.
- Position
- Below the diagonal: Http.KestrelBridge uses a module listed above it, which is the healthy direction.
30→24 Http.KestrelBridge uses Http✕
- Connections
- 5 pairs of types, where a type in Http.KestrelBridge uses a type in Http.
- The types involved
FIO.Http.KestrelBridge.KestrelBridge→FIO.Http.HttpRequestFIO.Http.KestrelBridge.KestrelBridge→FIO.Http.HttpResponseFIO.Http.KestrelBridge.KestrelBridge→FIO.Http.RequestBodyFIO.Http.KestrelBridge.KestrelBridge→FIO.Http.RequestTrackerFIO.Http.KestrelBridge.KestrelBridge→FIO.Http.Routes`1
- Direction
- Http.KestrelBridge uses Http, so a change to Http can break Http.KestrelBridge, while a change to Http.KestrelBridge can't break Http.
- Position
- Below the diagonal: Http.KestrelBridge uses a module listed above it, which is the healthy direction.
31→24 Http.Middleware uses Http✕
- Connections
- 1 pair of types, where a type in Http.Middleware uses a type in Http.
- The types involved
FIO.Http.Middleware.Middleware→FIO.Http.Routes`1
- Direction
- Http.Middleware uses Http, so a change to Http can break Http.Middleware, while a change to Http.Middleware can't break Http.
- Position
- Below the diagonal: Http.Middleware uses a module listed above it, which is the healthy direction.
32→24 Http.MiddlewareOperators uses Http✕
- Connections
- 1 pair of types, where a type in Http.MiddlewareOperators uses a type in Http.
- The types involved
FIO.Http.MiddlewareOperators.MiddlewareOperators→FIO.Http.Routes`1
- Direction
- Http.MiddlewareOperators uses Http, so a change to Http can break Http.MiddlewareOperators, while a change to Http.MiddlewareOperators can't break Http.
- Position
- Below the diagonal: Http.MiddlewareOperators uses a module listed above it, which is the healthy direction.
33→24 Http.Response uses Http✕
- Connections
- 2 pairs of types, where a type in Http.Response uses a type in Http.
- The types involved
FIO.Http.Response.Response→FIO.Http.HttpResponseFIO.Http.Response.Response→FIO.Http.HttpStatusCode
- Direction
- Http.Response uses Http, so a change to Http can break Http.Response, while a change to Http.Response can't break Http.
- Position
- Below the diagonal: Http.Response uses a module listed above it, which is the healthy direction.
34→24 Http.Route uses Http✕
- Connections
- 1 pair of types, where a type in Http.Route uses a type in Http.
- The types involved
FIO.Http.Route.Route→FIO.Http.RoutePattern
- Direction
- Http.Route uses Http, so a change to Http can break Http.Route, while a change to Http.Route can't break Http.
- Position
- Below the diagonal: Http.Route uses a module listed above it, which is the healthy direction.
35→24 Http.RouteBuilder uses Http✕
- Connections
- 1 pair of types, where a type in Http.RouteBuilder uses a type in Http.
- The types involved
FIO.Http.RouteBuilder.RouteCollector`1→FIO.Http.Routes`1
- Direction
- Http.RouteBuilder uses Http, so a change to Http can break Http.RouteBuilder, while a change to Http.RouteBuilder can't break Http.
- Position
- Below the diagonal: Http.RouteBuilder uses a module listed above it, which is the healthy direction.
36→24 Http.RouteOperators uses Http✕
- Connections
- 2 pairs of types, where a type in Http.RouteOperators uses a type in Http.
- The types involved
FIO.Http.RouteOperators.RouteOperators→FIO.Http.HttpMethodFIO.Http.RouteOperators.RouteOperators→FIO.Http.RoutePattern
- Direction
- Http.RouteOperators uses Http, so a change to Http can break Http.RouteOperators, while a change to Http.RouteOperators can't break Http.
- Position
- Below the diagonal: Http.RouteOperators uses a module listed above it, which is the healthy direction.
37→24 Http.RoutePathModule uses Http✕
- Connections
- 1 pair of types, where a type in Http.RoutePathModule uses a type in Http.
- The types involved
FIO.Http.RoutePathModule.RoutePathModule→FIO.Http.RoutePath
- Direction
- Http.RoutePathModule uses Http, so a change to Http can break Http.RoutePathModule, while a change to Http.RoutePathModule can't break Http.
- Position
- Below the diagonal: Http.RoutePathModule uses a module listed above it, which is the healthy direction.
38→1 Http.Routes uses DSL✕
- Connections
- 1 pair of types, where a type in Http.Routes uses a type in DSL.
- The types involved
FIO.Http.Routes.Routes→FIO.DSL.FIO`2
- Direction
- Http.Routes uses DSL, so a change to DSL can break Http.Routes, while a change to Http.Routes can't break DSL.
- Position
- Below the diagonal: Http.Routes uses a module listed above it, which is the healthy direction.
38→24 Http.Routes uses Http✕
- Connections
- 6 pairs of types, where a type in Http.Routes uses a type in Http.
- The types involved
FIO.Http.Routes.Routes→FIO.Http.HttpMethodFIO.Http.Routes.Routes→FIO.Http.HttpRequestFIO.Http.Routes.Routes→FIO.Http.HttpResponseFIO.Http.Routes.Routes→FIO.Http.RoutePatternFIO.Http.Routes.Routes→FIO.Http.Route`1FIO.Http.Routes.Routes→FIO.Http.Routes`1
- Direction
- Http.Routes uses Http, so a change to Http can break Http.Routes, while a change to Http.Routes can't break Http.
- Position
- Below the diagonal: Http.Routes uses a module listed above it, which is the healthy direction.
39→1 Http.Server uses DSL✕
- Connections
- 1 pair of types, where a type in Http.Server uses a type in DSL.
- The types involved
FIO.Http.Server.Server→FIO.DSL.FIO`2
- Direction
- Http.Server uses DSL, so a change to DSL can break Http.Server, while a change to Http.Server can't break DSL.
- Position
- Below the diagonal: Http.Server uses a module listed above it, which is the healthy direction.
39→14 Http.Server uses Runtime.WorkStealing✕
- Connections
- 1 pair of types, where a type in Http.Server uses a type in Runtime.WorkStealing.
- The types involved
FIO.Http.Server.Server→FIO.Runtime.WorkStealing.WorkStealingRuntime
- Direction
- Http.Server uses Runtime.WorkStealing, so a change to Runtime.WorkStealing can break Http.Server, while a change to Http.Server can't break Runtime.WorkStealing.
- Position
- Below the diagonal: Http.Server uses a module listed above it, which is the healthy direction.
39→24 Http.Server uses Http✕
- Connections
- 3 pairs of types, where a type in Http.Server uses a type in Http.
- The types involved
FIO.Http.Server.Server→FIO.Http.FIOServerFIO.Http.Server.Server→FIO.Http.Routes`1FIO.Http.Server.Server→FIO.Http.ServerConfig
- Direction
- Http.Server uses Http, so a change to Http can break Http.Server, while a change to Http.Server can't break Http.
- Position
- Below the diagonal: Http.Server uses a module listed above it, which is the healthy direction.
40→1 Http.ServerBuilder uses DSL✕
- Connections
- 1 pair of types, where a type in Http.ServerBuilder uses a type in DSL.
- The types involved
FIO.Http.ServerBuilder.ServerBuilder→FIO.DSL.FIO`2
- Direction
- Http.ServerBuilder uses DSL, so a change to DSL can break Http.ServerBuilder, while a change to Http.ServerBuilder can't break DSL.
- Position
- Below the diagonal: Http.ServerBuilder uses a module listed above it, which is the healthy direction.
40→24 Http.ServerBuilder uses Http✕
- Connections
- 3 pairs of types, where a type in Http.ServerBuilder uses a type in Http.
- The types involved
FIO.Http.ServerBuilder.ServerBuilder→FIO.Http.FIOServerFIO.Http.ServerBuilder.ServerBuilder→FIO.Http.Routes`1FIO.Http.ServerBuilder.ServerBuilder→FIO.Http.ServerConfig
- Direction
- Http.ServerBuilder uses Http, so a change to Http can break Http.ServerBuilder, while a change to Http.ServerBuilder can't break Http.
- Position
- Below the diagonal: Http.ServerBuilder 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 |
|---|---|---|
| A03:2025 — Software Supply Chain Failures | 6 | Medium |
| A05:2025 — Injection | 2 | High / Critical |
Roadmap
Top priorities: 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; 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; Nothing pauses a release for a human: publish as a draft release (or gate the release job on a protected tag/manual dispatch) so a bad build can be stopped before users can download it.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| 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. | +5.8 pts | Medium | Architecture documentation |
| 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.6 pts | Medium | Documentation (README) |
| Nothing pauses a release for a human: publish as a draft release (or gate the release job on a protected tag/manual dispatch) so a bad build can be stopped before users can download it. | +2.2 pts | Medium | Deployment & Rollback |
| Resolve the 11 Hotspot finding(s) in Churn × Complexity Hotspots — start with SignalingRuntime.fs, WorkStealingRuntime.fs, DirectRuntime.fs. | +1.6 pts | High | Churn × Complexity Hotspots |
| Consider OpenTelemetry tracing/metrics (OpenTelemetry.Extensions.Hosting with the ASP.NET Core instrumentation) and a health-check endpoint (ASP.NET Core's MapHealthChecks, or a /health route in your Giraffe/Suave app) for operability. | +1.2 pts | Medium | Observability |
| Bring the 17 bodies over 15 down to 15 or less in Cognitive Complexity — start with DirectRuntime.InterpretAsync (cognitive 109), WorkStealingRuntime.InterpretAsync (cognitive 104), SignalingRuntime.InterpretAsync (cognitive 99). | +0.6 pts | High | Cognitive Complexity |
| Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. | +0.3 pts | Low | Static Analysis (SAST) |
| Resolve the 2 TooManyFunctions finding(s) in God Classes — start with Extensions.fs, Factories.fs. | +0.1 pts | Low | God Classes |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| src/FIO/Runtime/WorkStealingRuntime.fs | 6.3 | Mixed | Cyclomatic Complexity: WorkStealingRuntime.InterpretAsync (cyclomatic 37) |
| src/FIO/Runtime/InterpreterCore.fs | 6.6 | Mixed | Cyclomatic Complexity: InterpreterCore.processRegionCont (cyclomatic 31) |
| src/FIO/Runtime/PollingRuntime.fs | 7.0 | Near-clean | Cyclomatic Complexity: PollingRuntime.InterpretAsync (cyclomatic 31) |
| src/FIO.Http/KestrelBridge.fs | 7.1 | Near-clean | Cyclomatic Complexity: KestrelBridge.writeResponseWithOptions (cyclomatic 33) |
| src/FIO.WebSockets/WebSocket.fs | 7.1 | Near-clean | Cyclomatic Complexity: WebSocket.ReceiveMessage (cyclomatic 20) |
| src/FIO/DSL/Factories.fs | 7.1 | Near-clean | Cyclomatic Complexity: FIO.raceAll (cyclomatic 16) |
| src/FIO/Runtime/DirectRuntime.fs | 7.2 | Near-clean | Cyclomatic Complexity: DirectRuntime.InterpretAsync (cyclomatic 34) |
| src/FIO/DSL/Extensions.fs | 7.2 | Near-clean | God Classes: TooManyFunctions: Extensions |
| REDACTED | 7.2 | Near-clean | Static Analysis (SAST): High: REDACTED |
| src/FIO/DSL/Core.fs | 7.4 | Near-clean | God Classes: FileTooLong: DSL/Core.fs |
| src/FIO/Runtime/SignalingRuntime.fs | 7.8 | Near-clean | Cyclomatic Complexity: SignalingRuntime.InterpretAsync (cyclomatic 37) |
| src/FIO/App.fs | 7.8 | Near-clean | Cyclomatic Complexity: FIOApp`2.RunAsync (cyclomatic 23) |
| src/FIO.WebSockets/WebSocketServer.fs | 7.8 | Near-clean | Cyclomatic Complexity: WebSocketServer.acceptLoop (cyclomatic 17) |
| REDACTED | 7.9 | Near-clean | Static Analysis (SAST): Medium: REDACTED |
| src/FIO.Http/Middleware.fs | 8.5 | Near-clean | Code Duplication: Duplicated block (9 lines × 2) |
| examples/FIO.Examples.App/Program.fs | 8.5 | Near-clean | Code Duplication: Duplicated block (18 lines × 2) |
| examples/FIO.Examples.DSL/Program.fs | 8.5 | Near-clean | Code Duplication: Duplicated block (11 lines × 2) |
How the grades work
A definite problem that already costs you something and drags the score down: a missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here tends to cause failures elsewhere.
Likely wrong, but not failing yet. It degrades the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to carry for two years either.
Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.
Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.
Methodology & how to trust this report
Watchdog 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. 44 of 44 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); none rely on LLM judgement. Overall confidence is 0.9 — the weighted average across measured dimensions; it falls as more of the score leans on LLM-assisted judgement and rises when it's fully tool-backed.
What we checked — 44 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, 73 of 84 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, a scanner, or (for a handful of documentation/naming dimensions) an LLM labelled sampled · advisory — 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 |
| Watchdog 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 |
| LLM (sampled · advisory) | Documentation quality, ADR conformance, naming — sampled over a bounded sample; advisory, never a deterministic measurement | — | ◐ LLM · sampled · advisory |
Run transparency — what happened this run
- D15 Churn × Complexity Hotspots — measured, with a gap in what it reached — 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. Git history depth insufficient — this repository has 11 commit(s), too few for a reliable trend signal. The clone is complete, so there is no deeper history to fetch: the signal returns as the project accumulates history.
- D15 Churn × Complexity Hotspots — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. A hotspot's complexity is meant to be the worst body its churn actually touched. For src/FIO.Http/KestrelBridge.fs, src/FIO.WebSockets/WebSocket.fs, src/FIO.WebSockets/WebSocketServer.fs, src/FIO/App.fs, src/FIO/DSL/Core.fs, … that could not be established — the complexity reader for the file reports no body extents, or the history carries no per-line attribution — so the row quotes the file's worst body, which the counted changes may never have touched. The churn count is unaffected.
- D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Single-contributor repository — bus factor is not applicable (1 contributor(s) across 11 commit(s) sampled, automation and bot accounts excluded). Concentration needs a team to concentrate: with one contributor there is nobody to spread the knowledge to, so there is nothing here for the owner to act on.
- D21 Naming Consistency — not measured this run — Watchdog 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 — Watchdog 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's deterministic call-shape 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. This says nothing about whether that surface is consistent.
- D24 Comment Value — not measured this run — Watchdog 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.
- D34 Knowledge Freshness — 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. Too few commits to judge knowledge freshness (11 commit(s) sampled).
- D35 Change Coupling — measured, with a gap in what it reached — 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. Git history depth insufficient — this repository has 11 commit(s), too few for a reliable change-coupling signal. The clone is complete, so there is no deeper history to fetch: the signal returns as the project accumulates history.
- AX1 Captive dependencies — not measured this run — Watchdog 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 registrations in C# and Spring beans in Java/Kotlin only, and this repository's container is Microsoft.Extensions.DependencyInjection registered from F#, whose lifetimes are not modelled yet, 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.
- AX6 Interface segregation — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is computed over the public interfaces this run's compilations declare, and none was loaded, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- C1 Data Protection — not measured this run — Watchdog 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 — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These authorization controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks authorization controls.
- C3 Audit Trail — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These audit controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks audit controls.
- C4 Data Retention — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These retention controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks retention controls.
- C5 Data-Subject Rights — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These data-subject rights controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks data-subject rights controls.
- IC1 Incompleteness & stubs — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- M4 Documentation accuracy — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
- 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.
- S1 Web-Security Posture — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These web-security controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks web-security controls.
- X1 Async correctness — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X12 Unreachable branch — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X13 Undrained process stream — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X14 Bypassable address classification — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X15 Unvalidated length from an untrusted reader — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X16 Unfloored truncation loop — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X17 Uncapped recursion over a caller-supplied document — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X18 Disposal-pattern correctness — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X19 Unrestored process-global state — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X2 Cancellation propagation — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X21 Side-effecting pattern guard — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X22 Contradicted release guard — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X24 Document value interpolated into markup unescaped — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X25 Inert configuration knob — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X26 Unsynchronised callback handoff — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X29 Per-element action decided by a fixed element — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X3 Exception handling — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X30 Support guard that admits what it rejects — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X32 Type resolved by simple name across every loaded assembly — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X4 Structured logging — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X5 Nullable reference types — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X6 Hand-rolled structured-format parsing — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and Python, JavaScript/TypeScript, Go, Java/Kotlin/Scala, Ruby, PHP, Rust, Swift, Erlang, Elixir and Dart source only, and no C# was loaded and none of those languages was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
Limitations & what we did not check
Watchdog assesses the repository exactly as committed, and only the repository. By design it does 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.
- D8 Code Coverage: Coverage is measured by building and running the test suite inside Watchdog's isolated image — the target repo is never modified, and nothing on your systems runs. So coverage exists only when the suite builds and runs within the inline time budget; one that needs external services, can't build, or exceeds the budget yields no coverage (D8 then degrades to not-measured, not a low score). Line coverage also says nothing about assertion quality.
- D11 Test Reliability: Flakiness is inferred from history/markers — Watchdog runs the suite once (for coverage), not the repeated runs under varied conditions that reveal nondeterminism, so a flaky test never recorded as failing is invisible here.
- D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
- D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
- D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- 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.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- M4 Documentation accuracy: Onboarding quality is an LLM read of the docs/setup present — it cannot run the onboarding or measure how long a real new joiner takes; the verdict is sampled and advisory.
- P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
- P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
Dimensions
D1 · Cyclomatic Complexity
13 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was WorkStealingRuntime.InterpretAsync at 37. A further 4 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 HeaderHelpers.isValidHeaderName at 22 — they are counted neither in the figure above nor in this dimension's score. 2 files carry no cyclomatic complexity row at all for this reason — every one of their over-threshold methods was excluded, so the exclusion is disclosed nowhere in the file itself: src/FIO.Http/Types.fs (HeaderHelpers.isValidHeaderName at 22), src/FIO/DSL/Core.fs (FIO`2.UpcastBoth at 20). 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 13 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with WorkStealingRuntime.InterpretAsync (cyclomatic 37), SignalingRuntime.InterpretAsync (cyclomatic 37), DirectRuntime.InterpretAsync (cyclomatic 34). — 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 13 together lifts Cyclomatic Complexity from 8.0 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
17 method(s) exceeded the cognitive complexity threshold of 15; the worst was DirectRuntime.InterpretAsync at 109.
What to do
- Bring the 17 bodies over 15 down to 15 or less in Cognitive Complexity — start with DirectRuntime.InterpretAsync (cognitive 109), WorkStealingRuntime.InterpretAsync (cognitive 104), SignalingRuntime.InterpretAsync (cognitive 99). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 17 together lifts Cognitive Complexity from 6.6 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
- Enforce Cognitive Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D3 · God Classes
5 god class(es) detected.
What to do
- Resolve the 2 TooManyFunctions finding(s) in God Classes — start with Extensions.fs, Factories.fs. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 2 FileTooLong finding(s) in God Classes — start with Core.fs, InterpreterCore.fs. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 TooManyMethods finding(s) in God Classes — start with WebSocket.fs. — 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
17 duplicated block group(s) detected. One further row reports members as variants of one another; it aggregates block groups already counted above and is not itself counted. 2 of the 18 are in trees this repository does not ship — vendored, example/demo, project-template, fixture and benchmark code — and are ranked below the shipped groups rather than excluded from them: the duplication there is real and is still counted in this dimension's score. The dimensions that publish a production-file census leave those trees out of theirs, so this count is deliberately drawn over the wider population.
What to do
- Resolve the 1 Members sharing a duplicated core (4 members, 50+ identical tokens) finding(s) in Code Duplication — start with DirectRuntime.fs. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Duplicated block (71–78 lines × 2) finding(s) in Code Duplication — start with PollingRuntime.fs. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Duplicated block (59–61 lines × 2) finding(s) in Code Duplication — start with PollingRuntime.fs. — 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
14 projects, 0 dependency cycle(s), 0 unstable depended-on project(s).
D6 · Cohesion (LCOM4)
1 of 28 classes have LCOM4 above 3.
What to do
- Resolve the 1 Low cohesion finding(s) in Cohesion (LCOM4) — start with WorkStealingRuntime.fs. — 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.
D8 · Code Coverage
Line coverage 93.8%.
D11 · Test Reliability
0 flaky across 1 measured tier(s). unit: measured (0 flaky).
D12 · Dependency Hygiene
3 outdated, 0 vulnerable, 0 deprecated packages.
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D14 · License Compliance
0 of 132 packages use a banned license. ★ DEPTH: this repository's MSBuild projects declare 7 direct `PackageReference`(s), and 125 further package(s) were reached beyond them by closing the graph over nuget.org's own nuspec dependency graph — so a banned licence pulled in only by a dependency's OWN dependencies is inside this verdict. A package whose licence nuget.org could not be asked for is not graded, and version ranges are taken at their lower bound, so this is the closure as that graph states it rather than a restored consumer's exact resolution.
D15 · Churn × Complexity Hotspots
Top hotspots: src/FIO/Runtime/SignalingRuntime.fs (2×37=74); src/FIO/Runtime/WorkStealingRuntime.fs (2×37=74); src/FIO/Runtime/DirectRuntime.fs (2×34=68)
What to do
- Resolve the 11 Hotspot finding(s) in Churn × Complexity Hotspots — start with SignalingRuntime.fs, WorkStealingRuntime.fs, DirectRuntime.fs. — One of this dimension's main actionable groups (11 warning-level).
D26 · Project Cohesion
0 of 5 build units (MSBuild, checkout) flagged as possibly oversized/incoherent.
D27 · Navigability
88 % of calls cross a namespace and 2 % go through an interface, but 79 % of collaborators are co-located — so following a call takes several hops. Baseline: small — navigation cost is tolerated.
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
2 finding(s): 0 critical, 1 high, 1 medium, 0 low. Separately, one or more rules could not re-parse an embedded snippet in 2 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).
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
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 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).
D37 · Vulnerability-disclosure Policy
A vulnerability-disclosure policy (SECURITY.md) is published with a reporting contact.
D39 · IL Efficiency
6 of 2857 first-party methods have an oversized IL body.
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 14 platform declaration(s) and 0 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
Frontend & cross-cutting dimensions
AX10 · Code composition
What to do
- The domain core is a small share of production code, but most of the rest matched no layer vocabulary at all — so this is not yet an anemic-domain finding. The namespace/path convention could not place that code, which makes the composition above a statement about the naming, not about the design. Name the layers (or check that the repository's conventions differ from the ones this check knows) before reading a thin domain into it.
AX2 · Stateful singletons
AX3 · Project dependency cycles
AX4 · Dependency direction
AX8 · Test isolation
GD1 · Unfinished & placeholder code
M1 · Documentation (README)
What to do
- Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
- Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
M3 · Folder & project structure
M4 · Documentation accuracy
P1 · CI/CD gates
P2 · Observability
What to do
- Consider OpenTelemetry tracing/metrics (OpenTelemetry.Extensions.Hosting with the ASP.NET Core instrumentation) and a health-check endpoint (ASP.NET Core's MapHealthChecks, or a /health route in your Giraffe/Suave app) for operability.
P3 · Security & performance tooling
- No static application security testing detected. For this repository's stack, add `semgrep --config=auto` plus gitleaks for committed secrets (F# is not a CodeQL language and has no language-specific SAST engine) as a CI step. What was searched, so you can tell an absence from a miss: the 14810 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner. — .github/workflows/benchmark.yml:11
What to do
- Add a SAST step to CI running what this repository's stack ships: `semgrep --config=auto` plus gitleaks for committed secrets (F# is not a CodeQL language and has no language-specific SAST engine) — so a security regression fails the build instead of landing.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
- The release is automated and no gate that pauses it for a human is DECLARED IN THIS REPOSITORY'S PIPELINE FILES. What was read: every file under `.github/workflows/`, `.forgejo/workflows/`, `.gitea/workflows/`, `.azuredevops/` and `.azure-pipelines/`, plus `.gitlab-ci*` and `azure-pipelines*` — with comment text stripped, so documenting a gate is not declaring one. What would have counted: GitLab's `when: manual`, CircleCI's `type: approval`, an Azure `ManualValidation@` task or an `approvals:` block, a Jenkins `input` step, a `uses:` step naming an approval action, an `environment:` paired with `reviewers` / `required_reviewers` / `protection` / `wait-timer` / `deployment_branch_policy`, a draft-release step, a `workflow_dispatch` promotion, or a release-event gate. ★ What this cannot see, because none of it is a file: a GitHub environment whose required reviewers are configured in repo SETTINGS, a branch protection rule, or an organisation deployment policy — all of them real, enforced gates that live outside the repository. If yours is one of those, this row is wrong and nothing in the tree could have told us. Otherwise: whatever the release trigger points at is published to users unreviewed, so a mistagged or unverified commit ships and the only remedy is a follow-up release.
What to do
- Nothing pauses a release for a human: publish as a draft release (or gate the release job on a protected tag/manual dispatch) so a bad build can be stopped before users can download it.
P6 · Release Hygiene
PF1 · Benchmark discipline
PF2 · Allocation hygiene
PF3 · Async & latency hygiene
- `InterpretAsync` holds an async function that calls .GetAwaiter().GetResult() — a blocking call inside async code stalls the thread-pool thread the workflow runs on, and every continuation queued behind it for as long as it runs. — src/FIO/Runtime/SignalingRuntime.fs:179
What to do
- F#: inside async { } or task { }, bind with let! / do! (Async.AwaitTask for a Task) instead of Async.RunSynchronously, .Wait() or .GetAwaiter().GetResult(), and use do! Async.Sleep or Task.Delay instead of Thread.Sleep; Async.RunSynchronously belongs at the program's entry point, outside every workflow.
X20 · Mistyped argument guard
X23 · Unguarded diagnostic materialisation
X27 · Collection changed while being enumerated
X28 · Index access outside its own emptiness guard
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 84% | Strong | Solid. |
| Architecture | 92% | Exemplary | Solid. |
| Maturity | 65% | Adequate — gated by M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 68% | Strong | Solid. |
| Security | 84% | Adequate — gated by D36 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Performance | 94% | 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 — 4 control(s) we could not find positive evidence for
- C3 Audit Trail — Not assessed: these audit controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks audit controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- C4 Data Retention — Not assessed: these retention controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks retention controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- C5 Data-Subject Rights — Not assessed: these data-subject rights controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks data-subject rights controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 70 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 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
- AX6 Interface segregation — not assessed — interface segregation is computed over a type surface that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
- AXB1 Runtime evidence locked — no reproducible boot — This repository has nothing the runtime tiers could boot or serve — no markup, no UI framework or web-server dependency, no UI component source, no native UI project and no API definition — nothing here is a surface to boot — so runtime a11y/egress/header evidence has no subject here. Not applicable: this is neither a gap in the scan nor a finding about your code.
- C1 Data Protection — Not assessed: these personal data controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks personal data controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- C2 Access Controls — Not assessed: these authorization controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks authorization controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- D10 Test Quality — ~20007 lines of test source are present (.fs) but no test cases reached the test census for this repository — no test root we could resolve declared them, or the files we read declare no cases in a test framework we recognise — so skipped/assertion-free tests couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
- D16 Bus Factor — single-contributor repository — bus factor is not applicable
- D17 Explicit Debt — the C# workspace loaded 0 projects, so explicit-debt density could not be measured
- D18 Solution Shape — D18 scores the shape of a C#/VB .NET solution; this repository's .NET projects are all F# (.fsproj), which the C#/VB workspace does not load, so the dimension does not apply.
- D19 Documentation Quality — No runnable or published unit to look for an example in, and no multi-project root README to look for a map in; the other documentation kinds are withheld (see the gaps), so documentation quality is not applicable here.
- D20 ADR Quality — N/A — ADRs are expected on deployable products with a user-facing host, not consumed libraries; no ADR log is required here.
- D21 Naming Consistency — Naming consistency is measured on C# and TypeScript only; F#, Python not measured.
- D22 Internal API Consistency — API consistency is measured on C# only; the exposed F# surface was not measured.
- 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# and Visual Basic comments only — this repository's production source is .fs, .py, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D25 ADR Conformance — no ADRs to check
- D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
- D32 Data Compliance (PII/GDPR) — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
- D34 Knowledge Freshness — too few commits to judge knowledge freshness
- 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.
- D43 Malicious Dependencies — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Python pyproject.toml/requirements.txt (pip/uv/Poetry), a Swift Package.swift/Package.resolved, a Cargo manifest, a Go module (go.mod/go.sum), a Gradle version catalogue, a Maven POM, an sbt build (build.sbt), composer.json, package.json, a Dart pubspec.yaml, an Elixir mix.exs/mix.lock (Hex), a rebar.config / erlang.mk DEPS (Hex), a Ruby Gemfile/Gemfile.lock or .gemspec (Bundler/RubyGems) — not scanned yet).
- D7 Architectural Integrity — no checkable ADRs and no dependency cycles — architectural integrity not assessed
- D9 Test Distribution — Test source is present (.fs) but no test cases reached the test census for this repository — no test root we could resolve declared them, or the files we read declare no cases in a test framework we recognise — so its unit/integration/BDD/E2E split couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
- DM1 Domain Modelling — applicable but not scored (2 of 3 signals for this style — below the bar we score at): 14 value object(s); 13 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
- IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
- P7 Outbound HTTP resilience — not measured — the application kind could not be determined for this repo
- 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 (Cobertura — `dotnet test --collect:"XPlat Code Coverage"` with a `coverlet.collector` PackageReference) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures, or wire coverage collection into CI, to enable this cross-layer check
- S1 Web-Security Posture — Not assessed: these web-security controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks web-security controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X1 Async correctness — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X12 Unreachable branch — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X13 Undrained process stream — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X14 Bypassable address classification — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X15 Unvalidated length from an untrusted reader — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X16 Unfloored truncation loop — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X17 Uncapped recursion over a caller-supplied document — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X18 Disposal-pattern correctness — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X19 Unrestored process-global state — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X2 Cancellation propagation — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X21 Side-effecting pattern guard — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X22 Contradicted release guard — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X24 Document value interpolated into markup unescaped — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X25 Inert configuration knob — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X26 Unsynchronised callback handoff — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X29 Per-element action decided by a fixed element — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X3 Exception handling — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X30 Support guard that admits what it rejects — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X32 Type resolved by simple name across every loaded assembly — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X4 Structured logging — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X5 Nullable reference types — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X6 Hand-rolled structured-format parsing — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X7 Silent fallback defaults — 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 — 1 finding(s)
- REDACTED
Serious — 68 finding(s)
- Hotspot: src/FIO/Runtime/SignalingRuntime.fs src/FIO/Runtime/SignalingRuntime.fs:98
- Hotspot: src/FIO/Runtime/WorkStealingRuntime.fs src/FIO/Runtime/WorkStealingRuntime.fs:325
- Hotspot: src/FIO/Runtime/DirectRuntime.fs src/FIO/Runtime/DirectRuntime.fs:20
- Hotspot: src/FIO.Http/KestrelBridge.fs src/FIO.Http/KestrelBridge.fs:226
- Hotspot: src/FIO/Runtime/InterpreterCore.fs src/FIO/Runtime/InterpreterCore.fs:73
- Hotspot: src/FIO/Runtime/PollingRuntime.fs src/FIO/Runtime/PollingRuntime.fs:311
- Hotspot: src/FIO.WebSockets/WebSocket.fs src/FIO.WebSockets/WebSocket.fs:166
- Hotspot: src/FIO/DSL/Core.fs src/FIO/DSL/Core.fs:919
- Hotspot: src/FIO.WebSockets/WebSocketServer.fs src/FIO.WebSockets/WebSocketServer.fs:181
- Hotspot: src/FIO/DSL/Factories.fs src/FIO/DSL/Factories.fs:417
- Hotspot: src/FIO/App.fs src/FIO/App.fs:161
- TooManyFunctions: Extensions src/FIO/DSL/Extensions.fs:7
- TooManyFunctions: FIO src/FIO/DSL/Factories.fs:17
- FileTooLong: DSL/Core.fs src/FIO/DSL/Core.fs
- FileTooLong: Runtime/InterpreterCore.fs src/FIO/Runtime/InterpreterCore.fs
- WorkStealingRuntime.InterpretAsync (cyclomatic 37) src/FIO/Runtime/WorkStealingRuntime.fs:325
- SignalingRuntime.InterpretAsync (cyclomatic 37) src/FIO/Runtime/SignalingRuntime.fs:98
- DirectRuntime.InterpretAsync (cyclomatic 34) src/FIO/Runtime/DirectRuntime.fs:20
- KestrelBridge.writeResponseWithOptions (cyclomatic 33) src/FIO.Http/KestrelBridge.fs:226
- PollingRuntime.InterpretAsync (cyclomatic 31) src/FIO/Runtime/PollingRuntime.fs:311
- InterpreterCore.processRegionCont (cyclomatic 31) src/FIO/Runtime/InterpreterCore.fs:73
- InterpreterCore.handleSharedCase (cyclomatic 27) src/FIO/Runtime/InterpreterCore.fs:205
- KestrelBridge.handleTracked (cyclomatic 24) src/FIO.Http/KestrelBridge.fs:360
- FIOApp`2.RunAsync (cyclomatic 23) src/FIO/App.fs:161
- WebSocket.ReceiveMessage (cyclomatic 20) src/FIO.WebSockets/WebSocket.fs:166
- WebSocket.SendFrame (cyclomatic 19) src/FIO.WebSockets/WebSocket.fs:275
- WebSocketServer.acceptLoop (cyclomatic 17) src/FIO.WebSockets/WebSocketServer.fs:181
- FIO.raceAll (cyclomatic 16) src/FIO/DSL/Factories.fs:417
- DirectRuntime.InterpretAsync (cognitive 109) src/FIO/Runtime/DirectRuntime.fs:20
- WorkStealingRuntime.InterpretAsync (cognitive 104) src/FIO/Runtime/WorkStealingRuntime.fs:325
- SignalingRuntime.InterpretAsync (cognitive 99) src/FIO/Runtime/SignalingRuntime.fs:98
- PollingRuntime.InterpretAsync (cognitive 61) src/FIO/Runtime/PollingRuntime.fs:311
- KestrelBridge.handleTracked (cognitive 54) src/FIO.Http/KestrelBridge.fs:360
- InterpreterCore.processRegionCont (cognitive 34) src/FIO/Runtime/InterpreterCore.fs:73
- KestrelBridge.writeResponseWithOptions (cognitive 32) src/FIO.Http/KestrelBridge.fs:226
- WebSocket.ReceiveMessage (cognitive 30) src/FIO.WebSockets/WebSocket.fs:166
- InterpreterCore.processOutcome (cognitive 29) src/FIO/Runtime/InterpreterCore.fs:144
- FIOApp`2.RunAsync (cognitive 25) src/FIO/App.fs:161
- FIO.raceAll (cognitive 24) src/FIO/DSL/Factories.fs:417
- WebSocket.SendFrame (cognitive 24) src/FIO.WebSockets/WebSocket.fs:275
- KestrelBridge.readBodyAsync (cognitive 21) src/FIO.Http/KestrelBridge.fs:97
- WebSocketServer.acceptLoop (cognitive 21) src/FIO.WebSockets/WebSocketServer.fs:181
- InterpreterCore.handleSharedCase (cognitive 20) src/FIO/Runtime/InterpreterCore.fs:205
- KestrelBridge.convertRequestAsync (cognitive 20) src/FIO.Http/KestrelBridge.fs:154
- FIO.forEachPar (cognitive 17) src/FIO/DSL/Factories.fs:210
- REDACTED
- TooManyMethods: WebSocket src/FIO.WebSockets/WebSocket.fs:14
- REDACTED
- Members sharing a duplicated core (4 members, 50+ identical tokens) src/FIO/Runtime/DirectRuntime.fs:1
- Duplicated block (71–78 lines × 2) src/FIO/Runtime/PollingRuntime.fs:316
- Duplicated block (59–61 lines × 2) src/FIO/Runtime/PollingRuntime.fs:432
- Duplicated block (19–22 lines × 2) src/FIO/Runtime/PollingRuntime.fs:61
- Duplicated block (21 lines × 2) src/FIO/Runtime/PollingRuntime.fs:397
- Duplicated block (18–19 lines × 3) src/FIO/Runtime/PollingRuntime.fs:334
- Duplicated block (17 lines × 3) src/FIO/Runtime/PollingRuntime.fs:445
- Duplicated block (13–14 lines × 2) src/FIO/DSL/Core.fs:829
- Duplicated block (14 lines × 2) src/FIO/DSL/Core.fs:883
- Duplicated block (8 lines × 2) src/FIO/DSL/Extensions.fs:252
- Duplicated block (7 lines × 4) src/FIO/Runtime/DirectRuntime.fs:235
- Duplicated block (7 lines × 2) src/FIO/DSL/Factories.fs:370
- Duplicated block (5–6 lines × 2) src/FIO.WebSockets/WebSocket.fs:204
- Duplicated block (9 lines × 2) src/FIO.Http/Middleware.fs:144
- Duplicated block (6 lines × 2) src/FIO/DSL/Extensions.fs:241
- Duplicated block (5 lines × 2) src/FIO/DSL/Extensions.fs:492
- Duplicated block (18 lines × 2) examples/FIO.Examples.App/Program.fs:225
- Duplicated block (11 lines × 2) examples/FIO.Examples.DSL/Program.fs:16
- Low cohesion: Scheduler (LCOM4 4) src/FIO/Runtime/WorkStealingRuntime.fs:37
- Sync-over-async blocking src/FIO/Runtime/SignalingRuntime.fs:179
Minor — 12 finding(s)
- Duplicated predicate src/FIO/Runtime/PollingRuntime.fs:67
- Duplicated predicate src/FIO/Runtime/PollingRuntime.fs:70
- Duplicated predicate src/FIO/Runtime/PollingRuntime.fs:353
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- IL efficiency: 6 authored method(s) exceed the IL budget src/FIO/Runtime/InterpreterCore.fs:209
- No ADRs
- No SAST .github/workflows/benchmark.yml:11
- No release approval gate
Minor — 3 finding(s)
- Outdated: FSharp.Core
- Outdated: FsCheck
- Outdated: Microsoft.NET.Test.Sdk
Appendix B — Reproduction & audit trail
| Dimension | Tool | Version | Command | Findings | Raw output |
|---|---|---|---|---|---|
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-2574d1c6669240bd97dbf50a0d5e3b9b/history.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-2574d1c6669240bd97dbf50a0d5e3b9b/tree.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-tree.json |
| D29 · Static Analysis (SAST) | semgrep | — | semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/watchdog-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 . | 2 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | dotnet | — | dotnet list FIO.slnx package --vulnerable --include-transitive --format json | 0 | artifacts/raw/dotnet-vulnerable.json |
| D31 · IaC & Container Security | trivy | — | trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan. | 0 | — |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. | 0 | — |
| 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 | none (no readable dependency manifest) | — | none (no readable dependency manifest): not applicable — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Python pyproject.toml/requirements.txt (pip/uv/Poetry), a Swift Package.swift/Package.resolved, a Cargo manifest, a Go module (go.mod/go.sum), a Gradle version catalogue, a Maven POM, an sbt build (build.sbt), composer.json, package.json, a Dart pubspec.yaml, an Elixir mix.exs/mix.lock (Hex), a rebar.config / erlang.mk DEPS (Hex), a Ruby Gemfile/Gemfile.lock or .gemspec (Bundler/RubyGems) — not scanned yet). | 0 | — |