Executive summary
eger-geger/FryProxy falls short of our standard for production because 16 files are no longer known to anyone active in the project and we found no recorded design decisions and no architecture document or diagram. It scores 57 out of 100 and is rated Adequate, and seven of its eight critical findings are security problems in the build pipeline.
Maturity, at 41, is the weakest lens and counts most in the score. The best first step is having someone learn and document the 16 files no active contributor knows, worth about 12 points. Recording design decisions comes next, worth about 10 points. Raising Maturity to 70 would lift the score to about 67.
Six pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. One secret can leak from the build pipeline, and one part of the code is no longer understood by anyone working on it. Having someone learn the forgotten files, pinning each tool to an exact version and limiting the secret to its own step would close these risks.
The product code is 3,448 lines, about €4,800 to rebuild.
If Maturity rose from 41 to 70, the lowest score rated Strong, the score would rise from 57 to about 67.
New since the last survey: 4 findings
- Code Coverage · Low coverage: FryProxy/IO/IByteBuffer.fs FryProxy/IO/IByteBuffer.fs
- Code Coverage · Low coverage: FryProxy/Http/Fields/Comment.fs FryProxy/Http/Fields/Comment.fs
- Code Coverage · Low coverage: FryProxy/Extension/Error.fs FryProxy/Extension/Error.fs
- Code Coverage · No test project references FryProxy.Demo FryProxy.Demo/FryProxy.Demo.csproj
Rebuild cost: about €4,800 · Estimate
| Cost to rebuild | €1,600 to €8,000, for 27 to 85 hours of work, under 0.1 person-years for one engineer |
|---|---|
| Difficulty of the problem | Low, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.8 at a score of 57. 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: 3,448 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 IO | 2 Http | 3 IO.BufferedParser | 4 IO.Connection | 5 Http.ChunkHeaderModule | 6 Http.ChunkModule | 7 Http.FieldModule | 8 Http.Fields | 9 Http.Hpack | 10 Http.Message | 11 Http.MessageBodyModule | 12 Http.Request | 13 Http.RequestLineModule | 14 Http.Response | 15 Http.StartLineModule | 16 Http.StatusLineModule | 17 Http.TargetModule | 18 IO.BufferedParser.Global | 19 IO.BufferedParser.ParseResult | 20 IO.BufferedParser.Parser | 21 Pipeline | 22 Pipeline.RequestHandler | 23 ProxyClient | 24 FryProxy | 25 Http.Fields.ConnectionModule | 26 Http.Fields.FieldModel | 27 Http.Fields.ViaModule | 28 Http.Hpack.CommandModule | 29 Http.Hpack.Decoder | 30 Http.Hpack.FieldPackModule | 31 Http.Hpack.Global | 32 Http.Hpack.NumericLitModule | 33 Http.Hpack.StringLitModule | 34 Http.Hpack.Table | 35 Pipeline.Handlers | 36 Pipeline.Middleware | 37 Pipeline.RequestHandlerExtensions | 38 OpaqueTunnel | 39 SocketExtensions | 40 TransparentTunnel |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 IO | ||||||||||||||||||||||||||||||||||||||||
| 2 Http | 2 | |||||||||||||||||||||||||||||||||||||||
| 3 IO.BufferedParser | 3 | |||||||||||||||||||||||||||||||||||||||
| 4 IO.Connection | 1 | |||||||||||||||||||||||||||||||||||||||
| 5 Http.ChunkHeaderModule | 1 | |||||||||||||||||||||||||||||||||||||||
| 6 Http.ChunkModule | 1 | |||||||||||||||||||||||||||||||||||||||
| 7 Http.FieldModule | 1 | |||||||||||||||||||||||||||||||||||||||
| 8 Http.Fields | 1 | |||||||||||||||||||||||||||||||||||||||
| 9 Http.Hpack | 2 | |||||||||||||||||||||||||||||||||||||||
| 10 Http.Message | 5 | |||||||||||||||||||||||||||||||||||||||
| 11 Http.MessageBodyModule | 2 | |||||||||||||||||||||||||||||||||||||||
| 12 Http.Request | 3 | |||||||||||||||||||||||||||||||||||||||
| 13 Http.RequestLineModule | 1 | |||||||||||||||||||||||||||||||||||||||
| 14 Http.Response | 3 | |||||||||||||||||||||||||||||||||||||||
| 15 Http.StartLineModule | 1 | |||||||||||||||||||||||||||||||||||||||
| 16 Http.StatusLineModule | 1 | |||||||||||||||||||||||||||||||||||||||
| 17 Http.TargetModule | 1 | |||||||||||||||||||||||||||||||||||||||
| 18 IO.BufferedParser.Global | 1 | |||||||||||||||||||||||||||||||||||||||
| 19 IO.BufferedParser.ParseResult | 1 | |||||||||||||||||||||||||||||||||||||||
| 20 IO.BufferedParser.Parser | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 21 Pipeline | 4 | |||||||||||||||||||||||||||||||||||||||
| 22 Pipeline.RequestHandler | 2 | |||||||||||||||||||||||||||||||||||||||
| 23 ProxyClient | 2 | |||||||||||||||||||||||||||||||||||||||
| 24 FryProxy | 2 | 2 | 5 | |||||||||||||||||||||||||||||||||||||
| 25 Http.Fields.ConnectionModule | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 26 Http.Fields.FieldModel | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 27 Http.Fields.ViaModule | 1 | |||||||||||||||||||||||||||||||||||||||
| 28 Http.Hpack.CommandModule | 2 | |||||||||||||||||||||||||||||||||||||||
| 29 Http.Hpack.Decoder | 1 | |||||||||||||||||||||||||||||||||||||||
| 30 Http.Hpack.FieldPackModule | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 31 Http.Hpack.Global | 1 | |||||||||||||||||||||||||||||||||||||||
| 32 Http.Hpack.NumericLitModule | 2 | |||||||||||||||||||||||||||||||||||||||
| 33 Http.Hpack.StringLitModule | 2 | |||||||||||||||||||||||||||||||||||||||
| 34 Http.Hpack.Table | 1 | 7 | ||||||||||||||||||||||||||||||||||||||
| 35 Pipeline.Handlers | 1 | 3 | 2 | |||||||||||||||||||||||||||||||||||||
| 36 Pipeline.Middleware | 2 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 37 Pipeline.RequestHandlerExtensions | 2 | |||||||||||||||||||||||||||||||||||||||
| 38 OpaqueTunnel | 2 | 1 | 3 | |||||||||||||||||||||||||||||||||||||
| 39 SocketExtensions | 1 | |||||||||||||||||||||||||||||||||||||||
| 40 TransparentTunnel | 1 | 1 | 1 | 3 |
2→1 Http uses IO✕
- Connections
- 2 pairs of types, where a type in Http uses a type in IO.
- The types involved
FryProxy.Http.ChunkBody→FryProxy.IO.IByteBufferFryProxy.Http.MessageBody→FryProxy.IO.IByteBuffer
- Direction
- Http uses IO, so a change to IO can break Http, while a change to Http can't break IO.
- Position
- Below the diagonal: Http uses a module listed above it, which is the healthy direction.
3→1 IO.BufferedParser uses IO✕
- Connections
- 3 pairs of types, where a type in IO.BufferedParser uses a type in IO.
- The types involved
FryProxy.IO.BufferedParser.LazyIter`1→FryProxy.IO.IConsumableFryProxy.IO.BufferedParser.LazyIter`1→FryProxy.IO.ReadBufferFryProxy.IO.BufferedParser.ParseState→FryProxy.IO.IConsumable
- Direction
- IO.BufferedParser uses IO, so a change to IO can break IO.BufferedParser, while a change to IO.BufferedParser can't break IO.
- Position
- Below the diagonal: IO.BufferedParser uses a module listed above it, which is the healthy direction.
4→1 IO.Connection uses IO✕
- Connections
- 1 pair of types, where a type in IO.Connection uses a type in IO.
- The types involved
FryProxy.IO.Connection.Connection→FryProxy.IO.IConnection
- Direction
- IO.Connection uses IO, so a change to IO can break IO.Connection, while a change to IO.Connection can't break IO.
- Position
- Below the diagonal: IO.Connection uses a module listed above it, which is the healthy direction.
5→2 Http.ChunkHeaderModule uses Http✕
- Connections
- 1 pair of types, where a type in Http.ChunkHeaderModule uses a type in Http.
- The types involved
FryProxy.Http.ChunkHeaderModule.ChunkHeaderModule→FryProxy.Http.ChunkHeader
- Direction
- Http.ChunkHeaderModule uses Http, so a change to Http can break Http.ChunkHeaderModule, while a change to Http.ChunkHeaderModule can't break Http.
- Position
- Below the diagonal: Http.ChunkHeaderModule uses a module listed above it, which is the healthy direction.
6→2 Http.ChunkModule uses Http✕
- Connections
- 1 pair of types, where a type in Http.ChunkModule uses a type in Http.
- The types involved
FryProxy.Http.ChunkModule.ChunkModule→FryProxy.Http.Chunk
- Direction
- Http.ChunkModule uses Http, so a change to Http can break Http.ChunkModule, while a change to Http.ChunkModule can't break Http.
- Position
- Below the diagonal: Http.ChunkModule uses a module listed above it, which is the healthy direction.
7→2 Http.FieldModule uses Http✕
- Connections
- 1 pair of types, where a type in Http.FieldModule uses a type in Http.
- The types involved
FryProxy.Http.FieldModule.FieldModule→FryProxy.Http.Field
- Direction
- Http.FieldModule uses Http, so a change to Http can break Http.FieldModule, while a change to Http.FieldModule can't break Http.
- Position
- Below the diagonal: Http.FieldModule uses a module listed above it, which is the healthy direction.
8→2 Http.Fields uses Http✕
- Connections
- 1 pair of types, where a type in Http.Fields uses a type in Http.
- The types involved
FryProxy.Http.Fields.Connection→FryProxy.Http.Field
- Direction
- Http.Fields uses Http, so a change to Http can break Http.Fields, while a change to Http.Fields can't break Http.
- Position
- Below the diagonal: Http.Fields uses a module listed above it, which is the healthy direction.
9→2 Http.Hpack uses Http✕
- Connections
- 2 pairs of types, where a type in Http.Hpack uses a type in Http.
- The types involved
FryProxy.Http.Hpack.FieldPack→FryProxy.Http.FieldFryProxy.Http.Hpack.TableEntry→FryProxy.Http.Field
- Direction
- Http.Hpack uses Http, so a change to Http can break Http.Hpack, while a change to Http.Hpack can't break Http.
- Position
- Below the diagonal: Http.Hpack uses a module listed above it, which is the healthy direction.
10→2 Http.Message uses Http✕
- Connections
- 5 pairs of types, where a type in Http.Message uses a type in Http.
- The types involved
FryProxy.Http.Message.Message→FryProxy.Http.ChunkFryProxy.Http.Message.Message→FryProxy.Http.FieldFryProxy.Http.Message.Message→FryProxy.Http.MessageBodyFryProxy.Http.Message.Message→FryProxy.Http.MessageHeader`1FryProxy.Http.Message.Message→FryProxy.Http.Message`1
- Direction
- Http.Message uses Http, so a change to Http can break Http.Message, while a change to Http.Message can't break Http.
- Position
- Below the diagonal: Http.Message uses a module listed above it, which is the healthy direction.
11→2 Http.MessageBodyModule uses Http✕
- Connections
- 2 pairs of types, where a type in Http.MessageBodyModule uses a type in Http.
- The types involved
FryProxy.Http.MessageBodyModule.MessageBodyModule→FryProxy.Http.ChunkFryProxy.Http.MessageBodyModule.MessageBodyModule→FryProxy.Http.MessageBody
- Direction
- Http.MessageBodyModule uses Http, so a change to Http can break Http.MessageBodyModule, while a change to Http.MessageBodyModule can't break Http.
- Position
- Below the diagonal: Http.MessageBodyModule uses a module listed above it, which is the healthy direction.
12→2 Http.Request uses Http✕
- Connections
- 3 pairs of types, where a type in Http.Request uses a type in Http.
- The types involved
FryProxy.Http.Request.Request→FryProxy.Http.MessageHeader`1FryProxy.Http.Request.Request→FryProxy.Http.RequestLineFryProxy.Http.Request.Request→FryProxy.Http.Target
- Direction
- Http.Request uses Http, so a change to Http can break Http.Request, while a change to Http.Request can't break Http.
- Position
- Below the diagonal: Http.Request uses a module listed above it, which is the healthy direction.
13→2 Http.RequestLineModule uses Http✕
- Connections
- 1 pair of types, where a type in Http.RequestLineModule uses a type in Http.
- The types involved
FryProxy.Http.RequestLineModule.RequestLineModule→FryProxy.Http.RequestLine
- Direction
- Http.RequestLineModule uses Http, so a change to Http can break Http.RequestLineModule, while a change to Http.RequestLineModule can't break Http.
- Position
- Below the diagonal: Http.RequestLineModule uses a module listed above it, which is the healthy direction.
14→2 Http.Response uses Http✕
- Connections
- 3 pairs of types, where a type in Http.Response uses a type in Http.
- The types involved
FryProxy.Http.Response.Response→FryProxy.Http.Message`1FryProxy.Http.Response.Response→FryProxy.Http.RequestLineFryProxy.Http.Response.Response→FryProxy.Http.StatusLine
- 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.
15→2 Http.StartLineModule uses Http✕
- Connections
- 1 pair of types, where a type in Http.StartLineModule uses a type in Http.
- The types involved
FryProxy.Http.StartLineModule.StartLineModule→FryProxy.Http.StartLine
- Direction
- Http.StartLineModule uses Http, so a change to Http can break Http.StartLineModule, while a change to Http.StartLineModule can't break Http.
- Position
- Below the diagonal: Http.StartLineModule uses a module listed above it, which is the healthy direction.
16→2 Http.StatusLineModule uses Http✕
- Connections
- 1 pair of types, where a type in Http.StatusLineModule uses a type in Http.
- The types involved
FryProxy.Http.StatusLineModule.StatusLineModule→FryProxy.Http.StatusLine
- Direction
- Http.StatusLineModule uses Http, so a change to Http can break Http.StatusLineModule, while a change to Http.StatusLineModule can't break Http.
- Position
- Below the diagonal: Http.StatusLineModule uses a module listed above it, which is the healthy direction.
17→2 Http.TargetModule uses Http✕
- Connections
- 1 pair of types, where a type in Http.TargetModule uses a type in Http.
- The types involved
FryProxy.Http.TargetModule.TargetModule→FryProxy.Http.Target
- Direction
- Http.TargetModule uses Http, so a change to Http can break Http.TargetModule, while a change to Http.TargetModule can't break Http.
- Position
- Below the diagonal: Http.TargetModule uses a module listed above it, which is the healthy direction.
18→3 IO.BufferedParser.Global uses IO.BufferedParser✕
- Connections
- 1 pair of types, where a type in IO.BufferedParser.Global uses a type in IO.BufferedParser.
- The types involved
FryProxy.IO.BufferedParser.Global.Global→FryProxy.IO.BufferedParser.BufferedParserBuilder
- Direction
- IO.BufferedParser.Global uses IO.BufferedParser, so a change to IO.BufferedParser can break IO.BufferedParser.Global, while a change to IO.BufferedParser.Global can't break IO.BufferedParser.
- Position
- Below the diagonal: IO.BufferedParser.Global uses a module listed above it, which is the healthy direction.
19→3 IO.BufferedParser.ParseResult uses IO.BufferedParser✕
- Connections
- 1 pair of types, where a type in IO.BufferedParser.ParseResult uses a type in IO.BufferedParser.
- The types involved
FryProxy.IO.BufferedParser.ParseResult.ParseResult→FryProxy.IO.BufferedParser.ParseState
- Direction
- IO.BufferedParser.ParseResult uses IO.BufferedParser, so a change to IO.BufferedParser can break IO.BufferedParser.ParseResult, while a change to IO.BufferedParser.ParseResult can't break IO.BufferedParser.
- Position
- Below the diagonal: IO.BufferedParser.ParseResult uses a module listed above it, which is the healthy direction.
20→1 IO.BufferedParser.Parser uses IO✕
- Connections
- 1 pair of types, where a type in IO.BufferedParser.Parser uses a type in IO.
- The types involved
FryProxy.IO.BufferedParser.Parser.Parser→FryProxy.IO.ReadBuffer
- Direction
- IO.BufferedParser.Parser uses IO, so a change to IO can break IO.BufferedParser.Parser, while a change to IO.BufferedParser.Parser can't break IO.
- Position
- Below the diagonal: IO.BufferedParser.Parser uses a module listed above it, which is the healthy direction.
20→3 IO.BufferedParser.Parser uses IO.BufferedParser✕
- Connections
- 1 pair of types, where a type in IO.BufferedParser.Parser uses a type in IO.BufferedParser.
- The types involved
FryProxy.IO.BufferedParser.Parser.Parser→FryProxy.IO.BufferedParser.ParseState
- Direction
- IO.BufferedParser.Parser uses IO.BufferedParser, so a change to IO.BufferedParser can break IO.BufferedParser.Parser, while a change to IO.BufferedParser.Parser can't break IO.BufferedParser.
- Position
- Below the diagonal: IO.BufferedParser.Parser uses a module listed above it, which is the healthy direction.
21→2 Pipeline uses Http✕
- Connections
- 4 pairs of types, where a type in Pipeline uses a type in Http.
- The types involved
FryProxy.Pipeline.RequestHandlerChain`1→FryProxy.Http.Message`1FryProxy.Pipeline.RequestHandlerChain`1→FryProxy.Http.RequestLineFryProxy.Pipeline.RequestHandler`1→FryProxy.Http.Message`1FryProxy.Pipeline.RequestHandler`1→FryProxy.Http.RequestLine
- Direction
- Pipeline uses Http, so a change to Http can break Pipeline, while a change to Pipeline can't break Http.
- Position
- Below the diagonal: Pipeline uses a module listed above it, which is the healthy direction.
22→2 Pipeline.RequestHandler uses Http✕
- Connections
- 2 pairs of types, where a type in Pipeline.RequestHandler uses a type in Http.
- The types involved
FryProxy.Pipeline.RequestHandler.RequestHandler→FryProxy.Http.Message`1FryProxy.Pipeline.RequestHandler.RequestHandler→FryProxy.Http.StatusLine
- Direction
- Pipeline.RequestHandler uses Http, so a change to Http can break Pipeline.RequestHandler, while a change to Pipeline.RequestHandler can't break Http.
- Position
- Below the diagonal: Pipeline.RequestHandler uses a module listed above it, which is the healthy direction.
23→2 ProxyClient uses Http✕
- Connections
- 2 pairs of types, where a type in ProxyClient uses a type in Http.
- The types involved
FryProxy.ProxyClient.ProxyClient→FryProxy.Http.Message`1FryProxy.ProxyClient.ProxyClient→FryProxy.Http.RequestLine
- Direction
- ProxyClient uses Http, so a change to Http can break ProxyClient, while a change to ProxyClient can't break Http.
- Position
- Below the diagonal: ProxyClient uses a module listed above it, which is the healthy direction.
24→1 FryProxy uses IO✕
- Connections
- 2 pairs of types, where a type in FryProxy uses a type in IO.
- The types involved
FryProxy.TunnelConnectionFactory→FryProxy.IO.IConnectionFryProxy.TunnelFactory`1→FryProxy.IO.ReadBuffer
- Direction
- FryProxy uses IO, so a change to IO can break FryProxy, while a change to FryProxy can't break IO.
- Position
- Below the diagonal: FryProxy uses a module listed above it, which is the healthy direction.
24→2 FryProxy uses Http✕
- Connections
- 2 pairs of types, where a type in FryProxy uses a type in Http.
- The types involved
FryProxy.TunnelConnectionFactory→FryProxy.Http.TargetFryProxy.TunnelFactory`1→FryProxy.Http.Target
- Direction
- FryProxy uses Http, so a change to Http can break FryProxy, while a change to FryProxy can't break Http.
- Position
- Below the diagonal: FryProxy uses a module listed above it, which is the healthy direction.
24→21 FryProxy uses Pipeline✕
- Connections
- 5 pairs of types, where a type in FryProxy uses a type in Pipeline.
- The types involved
FryProxy.HttpProxy`1→FryProxy.Pipeline.RequestHandlerChain`1FryProxy.IResponseContext`1→FryProxy.Pipeline.IClientConnectionAware`1FryProxy.IResponseContext`1→FryProxy.Pipeline.ITunnelAware`2FryProxy.IResponseContext`1→FryProxy.Pipeline.IUpstreamConnectionAware`1FryProxy.Tunnel`1→FryProxy.Pipeline.RequestHandlerChain`1
- Direction
- FryProxy uses Pipeline, so a change to Pipeline can break FryProxy, while a change to FryProxy can't break Pipeline.
- Position
- Below the diagonal: FryProxy uses a module listed above it, which is the healthy direction.
25→2 Http.Fields.ConnectionModule uses Http✕
- Connections
- 1 pair of types, where a type in Http.Fields.ConnectionModule uses a type in Http.
- The types involved
FryProxy.Http.Fields.ConnectionModule.ConnectionModule→FryProxy.Http.Field
- Direction
- Http.Fields.ConnectionModule uses Http, so a change to Http can break Http.Fields.ConnectionModule, while a change to Http.Fields.ConnectionModule can't break Http.
- Position
- Below the diagonal: Http.Fields.ConnectionModule uses a module listed above it, which is the healthy direction.
25→8 Http.Fields.ConnectionModule uses Http.Fields✕
- Connections
- 1 pair of types, where a type in Http.Fields.ConnectionModule uses a type in Http.Fields.
- The types involved
FryProxy.Http.Fields.ConnectionModule.ConnectionModule→FryProxy.Http.Fields.Connection
- Direction
- Http.Fields.ConnectionModule uses Http.Fields, so a change to Http.Fields can break Http.Fields.ConnectionModule, while a change to Http.Fields.ConnectionModule can't break Http.Fields.
- Position
- Below the diagonal: Http.Fields.ConnectionModule uses a module listed above it, which is the healthy direction.
26→2 Http.Fields.FieldModel uses Http✕
- Connections
- 1 pair of types, where a type in Http.Fields.FieldModel uses a type in Http.
- The types involved
FryProxy.Http.Fields.FieldModel.FieldModel→FryProxy.Http.Field
- Direction
- Http.Fields.FieldModel uses Http, so a change to Http can break Http.Fields.FieldModel, while a change to Http.Fields.FieldModel can't break Http.
- Position
- Below the diagonal: Http.Fields.FieldModel uses a module listed above it, which is the healthy direction.
26→8 Http.Fields.FieldModel uses Http.Fields✕
- Connections
- 1 pair of types, where a type in Http.Fields.FieldModel uses a type in Http.Fields.
- The types involved
FryProxy.Http.Fields.FieldModel.FieldModel→FryProxy.Http.Fields.IFieldModel`1
- Direction
- Http.Fields.FieldModel uses Http.Fields, so a change to Http.Fields can break Http.Fields.FieldModel, while a change to Http.Fields.FieldModel can't break Http.Fields.
- Position
- Below the diagonal: Http.Fields.FieldModel uses a module listed above it, which is the healthy direction.
27→8 Http.Fields.ViaModule uses Http.Fields✕
- Connections
- 1 pair of types, where a type in Http.Fields.ViaModule uses a type in Http.Fields.
- The types involved
FryProxy.Http.Fields.ViaModule.ViaModule→FryProxy.Http.Fields.Hop
- Direction
- Http.Fields.ViaModule uses Http.Fields, so a change to Http.Fields can break Http.Fields.ViaModule, while a change to Http.Fields.ViaModule can't break Http.Fields.
- Position
- Below the diagonal: Http.Fields.ViaModule uses a module listed above it, which is the healthy direction.
28→9 Http.Hpack.CommandModule uses Http.Hpack✕
- Connections
- 2 pairs of types, where a type in Http.Hpack.CommandModule uses a type in Http.Hpack.
- The types involved
FryProxy.Http.Hpack.CommandModule.CommandModule→FryProxy.Http.Hpack.CommandFryProxy.Http.Hpack.CommandModule.CommandModule→FryProxy.Http.Hpack.Decoder`1
- Direction
- Http.Hpack.CommandModule uses Http.Hpack, so a change to Http.Hpack can break Http.Hpack.CommandModule, while a change to Http.Hpack.CommandModule can't break Http.Hpack.
- Position
- Below the diagonal: Http.Hpack.CommandModule uses a module listed above it, which is the healthy direction.
29→9 Http.Hpack.Decoder uses Http.Hpack✕
- Connections
- 1 pair of types, where a type in Http.Hpack.Decoder uses a type in Http.Hpack.
- The types involved
FryProxy.Http.Hpack.Decoder.Decoder→FryProxy.Http.Hpack.Decoder`1
- Direction
- Http.Hpack.Decoder uses Http.Hpack, so a change to Http.Hpack can break Http.Hpack.Decoder, while a change to Http.Hpack.Decoder can't break Http.Hpack.
- Position
- Below the diagonal: Http.Hpack.Decoder uses a module listed above it, which is the healthy direction.
30→2 Http.Hpack.FieldPackModule uses Http✕
- Connections
- 1 pair of types, where a type in Http.Hpack.FieldPackModule uses a type in Http.
- The types involved
FryProxy.Http.Hpack.FieldPackModule.FieldPackModule→FryProxy.Http.Field
- Direction
- Http.Hpack.FieldPackModule uses Http, so a change to Http can break Http.Hpack.FieldPackModule, while a change to Http.Hpack.FieldPackModule can't break Http.
- Position
- Below the diagonal: Http.Hpack.FieldPackModule uses a module listed above it, which is the healthy direction.
30→9 Http.Hpack.FieldPackModule uses Http.Hpack✕
- Connections
- 2 pairs of types, where a type in Http.Hpack.FieldPackModule uses a type in Http.Hpack.
- The types involved
FryProxy.Http.Hpack.FieldPackModule.FieldPackModule→FryProxy.Http.Hpack.FieldPackFryProxy.Http.Hpack.FieldPackModule.FieldPackModule→FryProxy.Http.Hpack.PackOpts
- Direction
- Http.Hpack.FieldPackModule uses Http.Hpack, so a change to Http.Hpack can break Http.Hpack.FieldPackModule, while a change to Http.Hpack.FieldPackModule can't break Http.Hpack.
- Position
- Below the diagonal: Http.Hpack.FieldPackModule uses a module listed above it, which is the healthy direction.
31→9 Http.Hpack.Global uses Http.Hpack✕
- Connections
- 1 pair of types, where a type in Http.Hpack.Global uses a type in Http.Hpack.
- The types involved
FryProxy.Http.Hpack.Global.Global→FryProxy.Http.Hpack.DecoderBuilder
- Direction
- Http.Hpack.Global uses Http.Hpack, so a change to Http.Hpack can break Http.Hpack.Global, while a change to Http.Hpack.Global can't break Http.Hpack.
- Position
- Below the diagonal: Http.Hpack.Global uses a module listed above it, which is the healthy direction.
32→9 Http.Hpack.NumericLitModule uses Http.Hpack✕
- Connections
- 2 pairs of types, where a type in Http.Hpack.NumericLitModule uses a type in Http.Hpack.
- The types involved
FryProxy.Http.Hpack.NumericLitModule.NumericLitModule→FryProxy.Http.Hpack.Decoder`1FryProxy.Http.Hpack.NumericLitModule.NumericLitModule→FryProxy.Http.Hpack.NumericLit
- Direction
- Http.Hpack.NumericLitModule uses Http.Hpack, so a change to Http.Hpack can break Http.Hpack.NumericLitModule, while a change to Http.Hpack.NumericLitModule can't break Http.Hpack.
- Position
- Below the diagonal: Http.Hpack.NumericLitModule uses a module listed above it, which is the healthy direction.
33→9 Http.Hpack.StringLitModule uses Http.Hpack✕
- Connections
- 2 pairs of types, where a type in Http.Hpack.StringLitModule uses a type in Http.Hpack.
- The types involved
FryProxy.Http.Hpack.StringLitModule.StringLitModule→FryProxy.Http.Hpack.Decoder`1FryProxy.Http.Hpack.StringLitModule.StringLitModule→FryProxy.Http.Hpack.StringLit
- Direction
- Http.Hpack.StringLitModule uses Http.Hpack, so a change to Http.Hpack can break Http.Hpack.StringLitModule, while a change to Http.Hpack.StringLitModule can't break Http.Hpack.
- Position
- Below the diagonal: Http.Hpack.StringLitModule uses a module listed above it, which is the healthy direction.
34→2 Http.Hpack.Table uses Http✕
- Connections
- 1 pair of types, where a type in Http.Hpack.Table uses a type in Http.
- The types involved
FryProxy.Http.Hpack.Table.Table→FryProxy.Http.Field
- Direction
- Http.Hpack.Table uses Http, so a change to Http can break Http.Hpack.Table, while a change to Http.Hpack.Table can't break Http.
- Position
- Below the diagonal: Http.Hpack.Table uses a module listed above it, which is the healthy direction.
34→9 Http.Hpack.Table uses Http.Hpack✕
- Connections
- 7 pairs of types, where a type in Http.Hpack.Table uses a type in Http.Hpack.
- The types involved
FryProxy.Http.Hpack.Table.Table→FryProxy.Http.Hpack.CommandFryProxy.Http.Hpack.Table.Table→FryProxy.Http.Hpack.DynamicTableFryProxy.Http.Hpack.Table.Table→FryProxy.Http.Hpack.FieldPackFryProxy.Http.Hpack.Table.Table→FryProxy.Http.Hpack.LiteralFieldNameFryProxy.Http.Hpack.Table.Table→FryProxy.Http.Hpack.PackOptsFryProxy.Http.Hpack.Table.Table→FryProxy.Http.Hpack.StringLitFryProxy.Http.Hpack.Table.Table→FryProxy.Http.Hpack.TableEntry
- Direction
- Http.Hpack.Table uses Http.Hpack, so a change to Http.Hpack can break Http.Hpack.Table, while a change to Http.Hpack.Table can't break Http.Hpack.
- Position
- Below the diagonal: Http.Hpack.Table uses a module listed above it, which is the healthy direction.
35→1 Pipeline.Handlers uses IO✕
- Connections
- 1 pair of types, where a type in Pipeline.Handlers uses a type in IO.
- The types involved
FryProxy.Pipeline.Handlers.Handlers→FryProxy.IO.ReadBuffer
- Direction
- Pipeline.Handlers uses IO, so a change to IO can break Pipeline.Handlers, while a change to Pipeline.Handlers can't break IO.
- Position
- Below the diagonal: Pipeline.Handlers uses a module listed above it, which is the healthy direction.
35→2 Pipeline.Handlers uses Http✕
- Connections
- 3 pairs of types, where a type in Pipeline.Handlers uses a type in Http.
- The types involved
FryProxy.Pipeline.Handlers.Handlers→FryProxy.Http.Message`1FryProxy.Pipeline.Handlers.Handlers→FryProxy.Http.RequestLineFryProxy.Pipeline.Handlers.Handlers→FryProxy.Http.StatusLine
- Direction
- Pipeline.Handlers uses Http, so a change to Http can break Pipeline.Handlers, while a change to Pipeline.Handlers can't break Http.
- Position
- Below the diagonal: Pipeline.Handlers uses a module listed above it, which is the healthy direction.
35→21 Pipeline.Handlers uses Pipeline✕
- Connections
- 2 pairs of types, where a type in Pipeline.Handlers uses a type in Pipeline.
- The types involved
FryProxy.Pipeline.Handlers.Handlers→FryProxy.Pipeline.RequestHandlerChain`1FryProxy.Pipeline.Handlers.Handlers→FryProxy.Pipeline.RequestHandler`1
- Direction
- Pipeline.Handlers uses Pipeline, so a change to Pipeline can break Pipeline.Handlers, while a change to Pipeline.Handlers can't break Pipeline.
- Position
- Below the diagonal: Pipeline.Handlers uses a module listed above it, which is the healthy direction.
36→2 Pipeline.Middleware uses Http✕
- Connections
- 2 pairs of types, where a type in Pipeline.Middleware uses a type in Http.
- The types involved
FryProxy.Pipeline.Middleware.Middleware→FryProxy.Http.Message`1FryProxy.Pipeline.Middleware.Middleware→FryProxy.Http.RequestLine
- Direction
- Pipeline.Middleware uses Http, so a change to Http can break Pipeline.Middleware, while a change to Pipeline.Middleware can't break Http.
- Position
- Below the diagonal: Pipeline.Middleware uses a module listed above it, which is the healthy direction.
36→8 Pipeline.Middleware uses Http.Fields✕
- Connections
- 1 pair of types, where a type in Pipeline.Middleware uses a type in Http.Fields.
- The types involved
FryProxy.Pipeline.Middleware.Middleware→FryProxy.Http.Fields.Hop
- Direction
- Pipeline.Middleware uses Http.Fields, so a change to Http.Fields can break Pipeline.Middleware, while a change to Pipeline.Middleware can't break Http.Fields.
- Position
- Below the diagonal: Pipeline.Middleware uses a module listed above it, which is the healthy direction.
36→21 Pipeline.Middleware uses Pipeline✕
- Connections
- 1 pair of types, where a type in Pipeline.Middleware uses a type in Pipeline.
- The types involved
FryProxy.Pipeline.Middleware.Middleware→FryProxy.Pipeline.RequestHandler`1
- Direction
- Pipeline.Middleware uses Pipeline, so a change to Pipeline can break Pipeline.Middleware, while a change to Pipeline.Middleware can't break Pipeline.
- Position
- Below the diagonal: Pipeline.Middleware uses a module listed above it, which is the healthy direction.
37→21 Pipeline.RequestHandlerExtensions uses Pipeline✕
- Connections
- 2 pairs of types, where a type in Pipeline.RequestHandlerExtensions uses a type in Pipeline.
- The types involved
FryProxy.Pipeline.RequestHandlerExtensions.RequestHandlerExtensions→FryProxy.Pipeline.RequestHandlerChain`1FryProxy.Pipeline.RequestHandlerExtensions.RequestHandlerExtensions→FryProxy.Pipeline.RequestHandler`1
- Direction
- Pipeline.RequestHandlerExtensions uses Pipeline, so a change to Pipeline can break Pipeline.RequestHandlerExtensions, while a change to Pipeline.RequestHandlerExtensions can't break Pipeline.
- Position
- Below the diagonal: Pipeline.RequestHandlerExtensions uses a module listed above it, which is the healthy direction.
38→1 OpaqueTunnel uses IO✕
- Connections
- 2 pairs of types, where a type in OpaqueTunnel uses a type in IO.
- The types involved
FryProxy.OpaqueTunnel.OpaqueTunnel→FryProxy.IO.IConnectionFryProxy.OpaqueTunnel.OpaqueTunnel→FryProxy.IO.ReadBuffer
- Direction
- OpaqueTunnel uses IO, so a change to IO can break OpaqueTunnel, while a change to OpaqueTunnel can't break IO.
- Position
- Below the diagonal: OpaqueTunnel uses a module listed above it, which is the healthy direction.
38→2 OpaqueTunnel uses Http✕
- Connections
- 1 pair of types, where a type in OpaqueTunnel uses a type in Http.
- The types involved
FryProxy.OpaqueTunnel.OpaqueTunnel→FryProxy.Http.Target
- Direction
- OpaqueTunnel uses Http, so a change to Http can break OpaqueTunnel, while a change to OpaqueTunnel can't break Http.
- Position
- Below the diagonal: OpaqueTunnel uses a module listed above it, which is the healthy direction.
38→24 OpaqueTunnel uses FryProxy✕
- Connections
- 3 pairs of types, where a type in OpaqueTunnel uses a type in FryProxy.
- The types involved
FryProxy.OpaqueTunnel.OpaqueTunnel→FryProxy.TunnelConnectionFactoryFryProxy.OpaqueTunnel.OpaqueTunnel→FryProxy.TunnelFactory`1FryProxy.OpaqueTunnel.OpaqueTunnel→FryProxy.Tunnel`1
- Direction
- OpaqueTunnel uses FryProxy, so a change to FryProxy can break OpaqueTunnel, while a change to OpaqueTunnel can't break FryProxy.
- Position
- Below the diagonal: OpaqueTunnel uses a module listed above it, which is the healthy direction.
39→24 SocketExtensions uses FryProxy✕
- Connections
- 1 pair of types, where a type in SocketExtensions uses a type in FryProxy.
- The types involved
FryProxy.SocketExtensions.SocketExtensions→FryProxy.SocketTimeouts
- Direction
- SocketExtensions uses FryProxy, so a change to FryProxy can break SocketExtensions, while a change to SocketExtensions can't break FryProxy.
- Position
- Below the diagonal: SocketExtensions uses a module listed above it, which is the healthy direction.
40→1 TransparentTunnel uses IO✕
- Connections
- 1 pair of types, where a type in TransparentTunnel uses a type in IO.
- The types involved
FryProxy.TransparentTunnel.TransparentTunnel→FryProxy.IO.ReadBuffer
- Direction
- TransparentTunnel uses IO, so a change to IO can break TransparentTunnel, while a change to TransparentTunnel can't break IO.
- Position
- Below the diagonal: TransparentTunnel uses a module listed above it, which is the healthy direction.
40→2 TransparentTunnel uses Http✕
- Connections
- 1 pair of types, where a type in TransparentTunnel uses a type in Http.
- The types involved
FryProxy.TransparentTunnel.TransparentTunnel→FryProxy.Http.Target
- Direction
- TransparentTunnel uses Http, so a change to Http can break TransparentTunnel, while a change to TransparentTunnel can't break Http.
- Position
- Below the diagonal: TransparentTunnel uses a module listed above it, which is the healthy direction.
40→21 TransparentTunnel uses Pipeline✕
- Connections
- 1 pair of types, where a type in TransparentTunnel uses a type in Pipeline.
- The types involved
FryProxy.TransparentTunnel.TransparentTunnel→FryProxy.Pipeline.RequestHandlerChain`1
- Direction
- TransparentTunnel uses Pipeline, so a change to Pipeline can break TransparentTunnel, while a change to TransparentTunnel can't break Pipeline.
- Position
- Below the diagonal: TransparentTunnel uses a module listed above it, which is the healthy direction.
40→24 TransparentTunnel uses FryProxy✕
- Connections
- 3 pairs of types, where a type in TransparentTunnel uses a type in FryProxy.
- The types involved
FryProxy.TransparentTunnel.TransparentTunnel→FryProxy.TunnelConnectionFactoryFryProxy.TransparentTunnel.TransparentTunnel→FryProxy.TunnelFactory`1FryProxy.TransparentTunnel.TransparentTunnel→FryProxy.Tunnel`1
- Direction
- TransparentTunnel uses FryProxy, so a change to FryProxy can break TransparentTunnel, while a change to TransparentTunnel can't break FryProxy.
- Position
- Below the diagonal: TransparentTunnel uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A05:2025 — Injection | 7 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 7 | Medium |
Roadmap
Top priorities: Resolve the 16 Orphaned file finding(s) in Knowledge Freshness — start with Table.fs, Handlers.fs, HttpProxy.fs; Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them; Resolve the 1 Orphaned knowledge finding(s) in Knowledge Freshness — start with Huffman.fs.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 16 Orphaned file finding(s) in Knowledge Freshness — start with Table.fs, Handlers.fs, HttpProxy.fs. | +12.3 pts | Medium | Knowledge Freshness |
| Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them. | +10.2 pts | Medium | Architecture documentation |
| Resolve the 1 Orphaned knowledge finding(s) in Knowledge Freshness — start with Huffman.fs. | +4.6 pts | Low | Knowledge Freshness |
| Add a build/run (quick start) section to the root README — the first thing a newcomer needs. | +3.8 pts | Medium | Documentation (README) |
| Resolve the 2 Prerelease dependency finding(s) in Dependency Hygiene. | +1.4 pts | Low | Dependency Hygiene |
| Resolve the 1 Further orphaned files (smaller) finding(s) in Knowledge Freshness. | +1.3 pts | Low | Knowledge Freshness |
| Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release. | +2.3 pts | Medium | Release Hygiene |
| Resolve the 2 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED. | +0.8 pts | Low | Supply-chain Provenance & Signing |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 2.7 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 3.0 | Slop | Static Analysis (SAST): High: REDACTED |
| FryProxy/Pipeline/Handlers.fs | 8.5 | Near-clean | Code Duplication: Duplicated block (7 lines × 2) |
| FryProxy/IO/IByteBuffer.fs | 8.5 | Near-clean | Code Coverage: Low coverage: FryProxy/IO/IByteBuffer.fs |
| FryProxy/Http/Fields/Comment.fs | 8.5 | Near-clean | Code Coverage: Low coverage: FryProxy/Http/Fields/Comment.fs |
| FryProxy/Extension/Error.fs | 8.5 | Near-clean | Code Coverage: Low coverage: FryProxy/Extension/Error.fs |
| FryProxy.Demo/FryProxy.Demo.csproj | 8.5 | Near-clean | Code Coverage: No test project references FryProxy.Demo |
| FryProxy.Tests/FryProxy.Tests.fsproj | 9.5 | Near-clean | Dependency Hygiene: Outdated: FsUnit |
How the grades work
A definite problem that already costs you something and drags the score down: a missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here tends to cause failures elsewhere.
Likely wrong, but not failing yet. It degrades the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to carry for two years either.
Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.
Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.
Methodology & how to trust this report
This survey is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. All 37 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 1.0, the weighted average across measured dimensions.
What we checked — 37 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, 34 of 53 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Canine Code Analyzer duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 | ✓ deterministic |
Run transparency — what happened this run
- D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Single-maintainer repository — bus factor is not applicable (4 contributor(s) across 253 commit(s) sampled, automation and bot accounts excluded). One of them holds 94% of the history; the other 3 hold 2% each on average, below the 5% at which there is somebody to hand the work to. That is a single maintainer with drive-by contributors, not a team whose knowledge has concentrated — so the bus factor is not applicable and there is nothing here for the owner to act on.
- D17 Explicit Debt — measured, with a gap in what it reached — We measured this, but not all of it. What we 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. The C# workspace loaded this repository's projects but reported a load failure, and the dead-code reference search is unreliable over a graph that did not load cleanly, so it was skipped. The other debt markers on this row were read; dead symbols were not, and their absence from the score is not a finding that the code has none. First load diagnostic: Failure: Cannot open project 'FryProxy/FryProxy.fsproj' because the file extension '.fsproj' is not associated with a language.
- D17 Explicit Debt — measured, with a gap in what it reached — We measured this, but not all of it. What we 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. The 0 deducted marker(s) and the 0.0/KLoC density on this row were taken over this repository's .NET projects ALONE: .fs (3,429 lines, 99% of production source) went unread, because every marker collector on this path is reached through a C# workspace. D17's marker collectors need a compiler we do not have for that language, so none of its nine marker kinds were read there. The debt in that source is UNMEASURED — its absence from the score above is a gap in this analyzer's language coverage, not a finding that the code carries none.
- D22 Internal API Consistency — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. The loaded project set declares no packable project and no `.Contracts` project, so there is no intentionally-exposed surface for API consistency to be judged over.
- D24 Comment Value — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Each source language's comment syntax, and the code a comment annotates in it, needs its own proof before D24 judges it. Until then those comments are left unread, not counted as clean.
- 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.
- X2 Cancellation propagation — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
- D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- D8 Code Coverage: Coverage is measured by building and running the test suite inside our 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 — we run the suite once (for coverage), not the repeated runs under varied conditions that reveal nondeterminism, so a flaky test never recorded as failing is invisible here.
- D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
- D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- 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").
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
- P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
Dimensions
D1 · Cyclomatic Complexity
0 method(s) exceeded the cyclomatic complexity threshold of 15. A further 1 method(s) were over the threshold but excluded as flat dispatchers (a long switch/match over independent cases: many branches, almost no nesting), the largest being ReasonPhrase.forStatusCode at 42 — they are counted neither in the figure above nor in this dimension's score. 1 file carries no cyclomatic complexity row at all for this reason — every one of its over-threshold methods was excluded, so the exclusion is disclosed nowhere in the file itself: FryProxy/Http/ReasonPhrase.fs (ReasonPhrase.forStatusCode at 42). 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.
D2 · Cognitive Complexity
0 method(s) exceeded the cognitive complexity threshold of 15.
D3 · God Classes
0 god class(es) detected.
D4 · Code Duplication
1 duplicated block group(s) detected. 0.4 % of the production lines (14 of 3,448) are in a reported copy.
What to do
- Resolve the 1 Duplicated block (7 lines × 2) finding(s) in Code Duplication — start with Handlers.fs. — One of this dimension's main actionable groups (1 warning-level).
D5 · Coupling
1 projects, 0 dependency cycle(s), 0 unstable depended-on project(s).
D6 · Cohesion (LCOM4)
0 of 6 classes have LCOM4 above 3.
D8 · Code Coverage
Line coverage 89.4% — 3 file(s) below 50%.
What to do
- Resolve the 3 Low coverage finding(s) in Code Coverage — start with IByteBuffer.fs, Comment.fs, Error.fs. — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 1 No test project references FryProxy.Demo finding(s) in Code Coverage — start with FryProxy.Demo.csproj. — One of this dimension's main actionable groups (1 warning-level).
D11 · Test Reliability
0 flaky across 1 measured tier(s). integration: measured (0 flaky).
D12 · Dependency Hygiene
8 outdated, 0 vulnerable, 0 deprecated, 2 prerelease packages.
What to do
- Resolve the 2 Prerelease dependency finding(s) in Dependency Hygiene. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 Outdated finding(s) in Dependency Hygiene — start with FryProxy.Tests.fsproj. — One of this dimension's main actionable groups (1 recommendation-level).
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D14 · License Compliance
0 of 114 packages use a banned license. ★ DEPTH: this repository's MSBuild projects declare 7 direct `PackageReference`(s), and 107 further package(s) were reached beyond them by closing the graph over nuget.org's own nuspec dependency graph — so a banned licence pulled in only by a dependency's OWN dependencies is inside this verdict. A package whose licence nuget.org could not be asked for is not graded, and version ranges are taken at their lower bound, so this is the closure as that graph states it rather than a restored consumer's exact resolution.
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window.
D17 · Explicit Debt
0 deducted debt markers + unmeasured dead symbols across 19 LoC in the .NET projects (0.0/KLoC) → score 10.0. Dead code not measured: the solution did not load cleanly, so the reference search was skipped. Measured on the .NET source only: .fs (99% of production source) was not read, and carries at least 0 uncounted task marker(s) in 0 file(s).
D19 · Documentation Quality
1 of 1 documentation facets pass in full. 1 document(s) read across 2 unit(s).
D27 · Navigability
92 % of calls cross a namespace and 2 % go through an interface, but 73 % 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)
7 finding(s): 0 critical, 7 high, 0 medium, 0 low. 6 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens.
What to do
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- No action in Static Analysis (SAST) — all 6 REDACTED finding(s) are reported here at file:line but scored by D36 (supply-chain provenance), so none is charged to this dimension. — One of this dimension's main actionable groups (6 issue-level, 0 of them charged here).
D34 · Knowledge Freshness
17 of 17 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is FryProxy/Http/Hpack/Huffman.fs. Counted over 17 of the 55 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
What to do
- Resolve the 16 Orphaned file finding(s) in Knowledge Freshness — start with Table.fs, Handlers.fs, HttpProxy.fs. — One of this dimension's main actionable groups (16 recommendation-level).
- Resolve the 1 Orphaned knowledge finding(s) in Knowledge Freshness — start with Huffman.fs. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 1 Further orphaned files (smaller) finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
D35 · Change Coupling
No strong hidden change-coupling between production files.
D36 · Supply-chain Provenance & Signing
0/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).
What to do
- Resolve the 2 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 3 platform declaration(s) and 0 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
Frontend & cross-cutting dimensions
AX10 · Code composition
AX3 · Project dependency cycles
AX4 · Dependency direction
AX5 · Architecture & structure
AX8 · Test isolation
GD1 · Unfinished & placeholder code
M1 · Documentation (README)
What to do
- Add a build/run (quick start) section to the root README — the first thing a newcomer needs.
- Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
- No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
- Add a C4 context/container diagram (Structurizr, PlantUML or Mermaid) or an architecture.md overview.
M3 · Folder & project structure
P1 · CI/CD gates
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 2 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner. — REDACTED:9
- `FryProxy.Tests/FryProxy.Tests.fsproj` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`. — FryProxy.Tests/FryProxy.Tests.fsproj:18
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.
- Enable Dependabot/Renovate or a dependency-review gate.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
P6 · Release Hygiene
- No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
What to do
- Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.
PF3 · Async & latency hygiene
X5 · Nullable reference types
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 100% | Exemplary | Solid. |
| Architecture | 99% | Exemplary | Solid. |
| Maturity | 41% | Weak — gated by D34, M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 54% | Adequate — gated by P3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 71% | Adequate — gated by D36 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Performance | 100% | Exemplary | Strongest area. |
Unscored — 1 check(s) recorded observations but carry no score
- SC1 Supply-chain hygiene — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Not evidenced — 1 control(s) we could not find positive evidence for
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 76 check(s) not relevant to this codebase
- AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
- AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
- AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
- AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
- AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
- AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
- AX1 Captive dependencies — no DI registrations detected
- AX2 Stateful singletons — no singleton implementations detected
- AX6 Interface segregation — no public interfaces
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
- AXB1 Runtime evidence locked — no reproducible boot — This repository has nothing the runtime tiers could boot or serve — no markup, no UI framework or web-server dependency, no UI component source, no native UI project and no API definition — nothing here is a surface to boot — so runtime a11y/egress/header evidence has no subject here. Not applicable: this is neither a gap in the scan nor a finding about your code.
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- C1 Data Protection — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
- C2 Access Controls — No access-control surface detected in the analyzed source — no web/app surface to authorize (no HTTP API or web-UI project) and no authorization code at all (no [Authorize]/policies, no imperative guard methods). Access control is therefore N/A here — this is a library/CLI, which is authorized by its CALLER, not by itself. If this codebase grows request handlers, the dimension reactivates and a default-deny posture is expected then.
- C3 Audit Trail — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
- C4 Data Retention — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
- C5 Data-Subject Rights — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
- D10 Test Quality — ~2074 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-maintainer repository — bus factor is not applicable
- D18 Solution Shape — D18 scores the shape of a C#/VB .NET solution, but this repository's production source is mostly .fs, which the C#/VB workspace does not load — the projects that loaded are an immaterial minority, so solution shape was not assessed for this repository. Not scored — this is a gap in the analyzer's reach, not a verdict about this repository.
- 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 — N/A — too few peers to establish a naming convention (1337 declarations, no unit with a dominant convention).
- D22 Internal API Consistency — No intentionally-exposed public API to evaluate for consistency.
- D23 Boundary Type-Coupling — small single-context codebase (3,448 production LoC in the .NET projects) — bounded contexts are not needed at this size No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D24 Comment Value — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only; comments in this repository's .fs source were not judged.
- D25 ADR Conformance — no ADRs to check
- D26 Project Cohesion — This repository is one project, `FryProxy.Demo` (19 LoC, 0 public types across 0 namespaces), within the size bounds. Not scored: a single unit of this size gives project cohesion nothing to grade.
- D30 Dependency Vulnerabilities — nuget: `dotnet list package --vulnerable` could not read this solution's dependency graph — it reported an error for at least one project and returned no package data at all (typically a packages.config / non-PackageReference project, which the command cannot read). An unreadable dependency graph is not a clean one; migrate the project(s) to PackageReference to enable this scan
- 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.
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D7 Architectural Integrity — no checkable ADRs and no dependency cycles — architectural integrity not assessed
- DM1 Domain Modelling — applicable but not scored (2 of 3 signals for this style — below the bar we score at): 29 value object(s); 3 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 — reported, not scored — this repository's C# declares no analysable method bodies (a constants, record or DTO assembly), and this score is a density of unfinished work per method, which has no denominator here. The file-level signals below were still collected and are shown in full
- M4 Documentation accuracy — Not applicable: the 1 current-state document(s) make no claim of a kind M4 checks.
- P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
- P2 Observability — This repository's F# source (1 module(s), 54 file(s) read) declares no entry point and bootstraps no server, and nothing here deploys a service — it is a library, run inside whatever hosts it, so production observability (structured logging, tracing/metrics, health checks) is N/A. If it grows a binary or a service, the dimension reactivates.
- P7 Outbound HTTP resilience — not applicable — this isn't a service/API/worker
- P8 Schema migrations — no EF Core usage detected
- P9 Domain vs controller coverage — coverage data present for 52 file(s), but no domain-layer files were identified: no covered file's path contains any of the markers this check keys on (/domain/, /aggregates/, /valueobjects/, /domainmodel/, .domain/, /entities/), which are matched case-insensitively anywhere in the path. With no domain partition there is nothing to compare the web/controller layer against — if this repository keeps its business rules under a folder named none of those, that naming is what the check cannot see, not the domain logic.
- PF1 Benchmark discipline — Performance is assessed only for perf-relevant repos — a packaged library, one that ships benchmarks, or one already using allocation-aware APIs. This repo isn't one, so the Performance lens is not applicable and is excluded from the score.
- PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
- S1 Web-Security Posture — No web surface detected in the analyzed source — no HTTP API or web-UI project (no controllers/minimal-API endpoints, no Razor/Blazor views) and no web middleware (HTTPS redirection, HSTS, security headers, cookies). Transport security, security headers, secure cookies, CSRF/input-validation and middleware-order controls are therefore N/A here — this is a library/CLI/worker, not a web app. Crypto hygiene was still checked and found nothing to flag. If this codebase becomes web-facing, the dimension reactivates automatically.
- X1 Async correctness — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X10 Duplicated predicate — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X12 Unreachable branch — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X13 Undrained process stream — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X14 Bypassable address classification — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X16 Unfloored truncation loop — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X17 Uncapped recursion over a caller-supplied document — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X18 Disposal-pattern correctness — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X19 Unrestored process-global state — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X2 Cancellation propagation — X2 reached only 1% of this repository's production lines — fsharp (3,429 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- X20 Mistyped argument guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X21 Side-effecting pattern guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X22 Contradicted release guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X23 Unguarded diagnostic materialisation — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X24 Document value interpolated into markup unescaped — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X25 Inert configuration knob — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X26 Unsynchronised callback handoff — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X27 Collection changed while being enumerated — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X28 Index access outside its own emptiness guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X29 Per-element action decided by a fixed element — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X3 Exception handling — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X30 Support guard that admits what it rejects — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X32 Type resolved by simple name across every loaded assembly — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X4 Structured logging — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- 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 — 8 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Orphaned knowledge FryProxy/Http/Hpack/Huffman.fs:1
Serious — 11 finding(s)
- Low coverage: FryProxy/IO/IByteBuffer.fs FryProxy/IO/IByteBuffer.fs:1
- Low coverage: FryProxy/Http/Fields/Comment.fs FryProxy/Http/Fields/Comment.fs:1
- Low coverage: FryProxy/Extension/Error.fs FryProxy/Extension/Error.fs:1
- Prerelease dependency: FsCheck
- Prerelease dependency: FsCheck.NUnit
- REDACTED
- REDACTED
- REDACTED
- Duplicated block (7 lines × 2) FryProxy/Pipeline/Handlers.fs:63
- No test project references FryProxy.Demo FryProxy.Demo/FryProxy.Demo.csproj
- NuGet dependencies are not locked
Minor — 27 finding(s)
- Orphaned file FryProxy/Http/Hpack/Table.fs:1
- Orphaned file FryProxy/Pipeline/Handlers.fs:1
- Orphaned file FryProxy/HttpProxy.fs:1
- Orphaned file FryProxy/IO/ConnectionPool.fs:1
- Orphaned file FryProxy/SslTunnel.fs:1
- Orphaned file FryProxy/Http/Message.fs:1
- Orphaned file FryProxy/Http/Hpack/Command.fs:1
- Orphaned file FryProxy/IO/BufferedParser/Parser.fs:1
- Orphaned file FryProxy/Pipeline/Middleware.fs:1
- Orphaned file FryProxy/IO/AsyncTimeout.fs:1
- Orphaned file FryProxy/Http/Parse.fs:1
- Orphaned file FryProxy/Pipeline/Types.fs:1
- Orphaned file FryProxy/IO/ReadBuffer.fs:1
- Orphaned file FryProxy/Settings.fs:1
- Orphaned file FryProxy/Http/Hpack/Numeric.fs:1
- Orphaned file FryProxy/Http/Hpack/Decoder.fs:1
- Outdated: FsUnit FryProxy.Tests/FryProxy.Tests.fsproj:20
- Further orphaned files (smaller)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- No ADRs
- No architecture diagram/doc
- No SAST REDACTED:9
- No dependency-update automation FryProxy.Tests/FryProxy.Tests.fsproj:18
- No changelog
Minor — 7 finding(s)
- Outdated: FSharp.Core
- Outdated: FsCheck
- Outdated: FsCheck.NUnit
- Outdated: Microsoft.NET.Test.Sdk
- Outdated: NUnit
- Outdated: NUnit3TestAdapter
- Outdated: Testcontainers
Appendix B — Reproduction & audit trail
| Dimension | Tool | Version | Command | Findings | Raw output |
|---|---|---|---|---|---|
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-a7066b4bcfe345c3b06650946fcbd4b0/history.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-a7066b4bcfe345c3b06650946fcbd4b0/tree.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-tree.json |
| D29 · Static Analysis (SAST) | semgrep | — | semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/canine-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt . | 7 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | nuget | — | nuget: not applicable — nuget: `dotnet list package --vulnerable` could not read this solution's dependency graph — it reported an error for at least one project and returned no package data at all (typically a packages.config / non-PackageReference project, which the command cannot read). An unreadable dependency graph is not a clean one; migrate the project(s) to PackageReference to enable this scan | 0 | — |
| D31 · IaC & Container Security | trivy | — | trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan. | 0 | — |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. | 0 | — |
| D37 · Vulnerability-disclosure Policy | disclosure | — | disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . /tmp/codehealth-osv-sbom-594280cbfb7347e283837f85664e9857 | 0 | artifacts/raw/osv-scanner.json |