Executive summary
fsprojects/Fleece falls short of our standard for a preview release because six files are no longer known to anyone active in the project and the project keeps no record of its design decisions. It scores 49 out of 100 and is rated Adequate, and five of its 12 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 recording design decisions, worth about 7 points. Having someone learn and document the six files no active contributor knows comes next, worth about 5 points. Raising Maturity to 62 would lift the score to about 52.
Six parts of the code are no longer understood by anyone working on it. Five pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with, and one control can't be used without a mouse. Having someone learn the forgotten files, pinning each tool to an exact version and making the controls work with a keyboard would close these risks.
The product code is 3,693 lines, about €4,900 to rebuild.
If Maturity rose from 41 to 62, the lowest score rated Strong, the score would rise from 49 to about 52.
New since the last survey: 2 findings
- Visual & motion safety · Low contrast colour pair in CSS (2.2:1) docsrc/files/style.css
- Visual & motion safety · Low contrast colour pair in CSS (2.2:1) docsrc/content/content/style.css
Fixed since the last survey: 10 findings
- Code Duplication · Duplicated block (19–21 lines × 3) src/Fleece.FSharpData/Fleece.FSharpData.fs
- Code Duplication · Duplicated block (7 lines × 3) src/Fleece.FSharpData/Fleece.FSharpData.fs
- Code Duplication · Duplicated block (6 lines × 4) src/Fleece.FSharpData/Fleece.FSharpData.fs
- Code Duplication · Duplicated block (6 lines × 3) src/Fleece.FSharpData/Fleece.FSharpData.fs
- Code Duplication · Duplicated block (6 lines × 2) src/Fleece.FSharpData/Fleece.FSharpData.fs
- Code Duplication · Duplicated block (5 lines × 3) src/Fleece.FSharpData/Fleece.FSharpData.fs
- Code Duplication · Duplicated block (5 lines × 4) src/Fleece.FSharpData/Fleece.FSharpData.fs
- Code Coverage · Coverage not measured — no coverage collector is wired up
- Dependency Hygiene · Vulnerable: Newtonsoft.Json
- A11y enforcement · Accessibility enforcement below the top rung
Rebuild cost: about €4,900 · Estimate
| Cost to rebuild | €1,600 to €8,100, for 27 to 85 hours of work, under 0.1 person-years for one engineer |
|---|---|
| Difficulty of the problem | Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.7 at a score of 49. 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,693 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 Combinators | 2 DocLib | 3 DocLib.SemVer | 4 Fleece | 5 Fleece.SystemTextJson.InternalsModule | 6 DocLib.GlobbingPatternModule | 7 DocLib.SemVer.SemVer | 8 Fleece.Codec | 9 Fleece.Codecs | 10 Fleece.Codecs.Internals | 11 Fleece.ComputationExpressions | 12 Fleece.Decode | 13 Fleece.Decode.Fail | 14 Fleece.FSharpData | 15 Fleece.FSharpData.Internals | 16 Fleece.FSharpData.OperatorsModule.Codec | 17 Fleece.FSharpData.OperatorsModule.Decode | 18 Fleece.FSharpData.OperatorsModule.Decode.Fail | 19 Fleece.Internals | 20 Fleece.Newtonsoft | 21 Fleece.Newtonsoft.OperatorsModule.Codec | 22 Fleece.Newtonsoft.OperatorsModule.Decode | 23 Fleece.Newtonsoft.OperatorsModule.Decode.Fail | 24 Fleece.Operators | 25 Fleece.SystemJson | 26 Fleece.SystemJson.OperatorsModule.Codec | 27 Fleece.SystemJson.OperatorsModule.Decode | 28 Fleece.SystemJson.OperatorsModule.Decode.Fail | 29 Fleece.SystemTextJson | 30 Fleece.SystemTextJson.OperatorsModule.Codec | 31 Fleece.SystemTextJson.OperatorsModule.Decode | 32 Fleece.SystemTextJson.OperatorsModule.Decode.Fail | 33 Fleece.FSharpData.OperatorsModule | 34 Fleece.FSharpData.OperatorsModule.JsonCodec | 35 Fleece.Newtonsoft.OperatorsModule | 36 Fleece.Newtonsoft.OperatorsModule.JsonCodec | 37 Fleece.SystemJson.OperatorsModule | 38 Fleece.SystemJson.OperatorsModule.JsonCodec | 39 Fleece.SystemTextJson.OperatorsModule | 40 Fleece.SystemTextJson.OperatorsModule.JsonCodec |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 Combinators | ||||||||||||||||||||||||||||||||||||||||
| 2 DocLib | ||||||||||||||||||||||||||||||||||||||||
| 3 DocLib.SemVer | ||||||||||||||||||||||||||||||||||||||||
| 4 Fleece | ||||||||||||||||||||||||||||||||||||||||
| 5 Fleece.SystemTextJson.InternalsModule | ||||||||||||||||||||||||||||||||||||||||
| 6 DocLib.GlobbingPatternModule | 1 | |||||||||||||||||||||||||||||||||||||||
| 7 DocLib.SemVer.SemVer | 1 | |||||||||||||||||||||||||||||||||||||||
| 8 Fleece.Codec | 3 | |||||||||||||||||||||||||||||||||||||||
| 9 Fleece.Codecs | 2 | |||||||||||||||||||||||||||||||||||||||
| 10 Fleece.Codecs.Internals | 2 | |||||||||||||||||||||||||||||||||||||||
| 11 Fleece.ComputationExpressions | 4 | |||||||||||||||||||||||||||||||||||||||
| 12 Fleece.Decode | 1 | |||||||||||||||||||||||||||||||||||||||
| 13 Fleece.Decode.Fail | 2 | |||||||||||||||||||||||||||||||||||||||
| 14 Fleece.FSharpData | 6 | |||||||||||||||||||||||||||||||||||||||
| 15 Fleece.FSharpData.Internals | 1 | |||||||||||||||||||||||||||||||||||||||
| 16 Fleece.FSharpData.OperatorsModule.Codec | 2 | |||||||||||||||||||||||||||||||||||||||
| 17 Fleece.FSharpData.OperatorsModule.Decode | 1 | |||||||||||||||||||||||||||||||||||||||
| 18 Fleece.FSharpData.OperatorsModule.Decode.Fail | 2 | |||||||||||||||||||||||||||||||||||||||
| 19 Fleece.Internals | 6 | |||||||||||||||||||||||||||||||||||||||
| 20 Fleece.Newtonsoft | 6 | |||||||||||||||||||||||||||||||||||||||
| 21 Fleece.Newtonsoft.OperatorsModule.Codec | 2 | |||||||||||||||||||||||||||||||||||||||
| 22 Fleece.Newtonsoft.OperatorsModule.Decode | 1 | |||||||||||||||||||||||||||||||||||||||
| 23 Fleece.Newtonsoft.OperatorsModule.Decode.Fail | 2 | |||||||||||||||||||||||||||||||||||||||
| 24 Fleece.Operators | 3 | |||||||||||||||||||||||||||||||||||||||
| 25 Fleece.SystemJson | 6 | |||||||||||||||||||||||||||||||||||||||
| 26 Fleece.SystemJson.OperatorsModule.Codec | 2 | |||||||||||||||||||||||||||||||||||||||
| 27 Fleece.SystemJson.OperatorsModule.Decode | 1 | |||||||||||||||||||||||||||||||||||||||
| 28 Fleece.SystemJson.OperatorsModule.Decode.Fail | 2 | |||||||||||||||||||||||||||||||||||||||
| 29 Fleece.SystemTextJson | 6 | 1 | ||||||||||||||||||||||||||||||||||||||
| 30 Fleece.SystemTextJson.OperatorsModule.Codec | 2 | |||||||||||||||||||||||||||||||||||||||
| 31 Fleece.SystemTextJson.OperatorsModule.Decode | 1 | |||||||||||||||||||||||||||||||||||||||
| 32 Fleece.SystemTextJson.OperatorsModule.Decode.Fail | 2 | |||||||||||||||||||||||||||||||||||||||
| 33 Fleece.FSharpData.OperatorsModule | 3 | 1 | ||||||||||||||||||||||||||||||||||||||
| 34 Fleece.FSharpData.OperatorsModule.JsonCodec | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 35 Fleece.Newtonsoft.OperatorsModule | 3 | 1 | ||||||||||||||||||||||||||||||||||||||
| 36 Fleece.Newtonsoft.OperatorsModule.JsonCodec | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 37 Fleece.SystemJson.OperatorsModule | 3 | 1 | ||||||||||||||||||||||||||||||||||||||
| 38 Fleece.SystemJson.OperatorsModule.JsonCodec | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 39 Fleece.SystemTextJson.OperatorsModule | 3 | 1 | ||||||||||||||||||||||||||||||||||||||
| 40 Fleece.SystemTextJson.OperatorsModule.JsonCodec | 1 | 1 |
6→2 DocLib.GlobbingPatternModule uses DocLib✕
- Connections
- 1 pair of types, where a type in DocLib.GlobbingPatternModule uses a type in DocLib.
- The types involved
DocLib.GlobbingPatternModule.GlobbingPatternModule→DocLib.IGlobbingPattern
- Direction
- DocLib.GlobbingPatternModule uses DocLib, so a change to DocLib can break DocLib.GlobbingPatternModule, while a change to DocLib.GlobbingPatternModule can't break DocLib.
- Position
- Below the diagonal: DocLib.GlobbingPatternModule uses a module listed above it, which is the healthy direction.
7→3 DocLib.SemVer.SemVer uses DocLib.SemVer✕
- Connections
- 1 pair of types, where a type in DocLib.SemVer.SemVer uses a type in DocLib.SemVer.
- The types involved
DocLib.SemVer.SemVer.SemVer→DocLib.SemVer.SemVerInfo
- Direction
- DocLib.SemVer.SemVer uses DocLib.SemVer, so a change to DocLib.SemVer can break DocLib.SemVer.SemVer, while a change to DocLib.SemVer.SemVer can't break DocLib.SemVer.
- Position
- Below the diagonal: DocLib.SemVer.SemVer uses a module listed above it, which is the healthy direction.
8→4 Fleece.Codec uses Fleece✕
- Connections
- 3 pairs of types, where a type in Fleece.Codec uses a type in Fleece.
- The types involved
Fleece.Codec.Codec→Fleece.Codec`4Fleece.Codec.Codec→Fleece.IEncodingFleece.Codec.Codec→Fleece.PropertyList`1
- Direction
- Fleece.Codec uses Fleece, so a change to Fleece can break Fleece.Codec, while a change to Fleece.Codec can't break Fleece.
- Position
- Below the diagonal: Fleece.Codec uses a module listed above it, which is the healthy direction.
9→4 Fleece.Codecs uses Fleece✕
- Connections
- 2 pairs of types, where a type in Fleece.Codecs uses a type in Fleece.
- The types involved
Fleece.Codecs.Codecs→Fleece.Codec`4Fleece.Codecs.Codecs→Fleece.PropertyList`1
- Direction
- Fleece.Codecs uses Fleece, so a change to Fleece can break Fleece.Codecs, while a change to Fleece.Codecs can't break Fleece.
- Position
- Below the diagonal: Fleece.Codecs uses a module listed above it, which is the healthy direction.
10→4 Fleece.Codecs.Internals uses Fleece✕
- Connections
- 2 pairs of types, where a type in Fleece.Codecs.Internals uses a type in Fleece.
- The types involved
Fleece.Codecs.Internals.Internals→Fleece.Codec`4Fleece.Codecs.Internals.Internals→Fleece.DecodeError
- Direction
- Fleece.Codecs.Internals uses Fleece, so a change to Fleece can break Fleece.Codecs.Internals, while a change to Fleece.Codecs.Internals can't break Fleece.
- Position
- Below the diagonal: Fleece.Codecs.Internals uses a module listed above it, which is the healthy direction.
11→4 Fleece.ComputationExpressions uses Fleece✕
- Connections
- 4 pairs of types, where a type in Fleece.ComputationExpressions uses a type in Fleece.
- The types involved
Fleece.ComputationExpressions.CodecApplicativeBuilder→Fleece.Codec`4Fleece.ComputationExpressions.CodecApplicativeBuilder→Fleece.PropertyList`1Fleece.ComputationExpressions.ComputationExpressions→Fleece.Codec`4Fleece.ComputationExpressions.ComputationExpressions→Fleece.PropertyList`1
- Direction
- Fleece.ComputationExpressions uses Fleece, so a change to Fleece can break Fleece.ComputationExpressions, while a change to Fleece.ComputationExpressions can't break Fleece.
- Position
- Below the diagonal: Fleece.ComputationExpressions uses a module listed above it, which is the healthy direction.
12→4 Fleece.Decode uses Fleece✕
- Connections
- 1 pair of types, where a type in Fleece.Decode uses a type in Fleece.
- The types involved
Fleece.Decode.Decode→Fleece.DecodeError
- Direction
- Fleece.Decode uses Fleece, so a change to Fleece can break Fleece.Decode, while a change to Fleece.Decode can't break Fleece.
- Position
- Below the diagonal: Fleece.Decode uses a module listed above it, which is the healthy direction.
13→4 Fleece.Decode.Fail uses Fleece✕
- Connections
- 2 pairs of types, where a type in Fleece.Decode.Fail uses a type in Fleece.
- The types involved
Fleece.Decode.Fail.Fail→Fleece.DecodeErrorFleece.Decode.Fail.Fail→Fleece.PropertyList`1
- Direction
- Fleece.Decode.Fail uses Fleece, so a change to Fleece can break Fleece.Decode.Fail, while a change to Fleece.Decode.Fail can't break Fleece.
- Position
- Below the diagonal: Fleece.Decode.Fail uses a module listed above it, which is the healthy direction.
14→4 Fleece.FSharpData uses Fleece✕
- Connections
- 6 pairs of types, where a type in Fleece.FSharpData uses a type in Fleece.
- The types involved
Fleece.FSharpData.Encoding→Fleece.Codec`4Fleece.FSharpData.Encoding→Fleece.DateTimeContentsFleece.FSharpData.Encoding→Fleece.DecodeErrorFleece.FSharpData.Encoding→Fleece.IEncodingFleece.FSharpData.Encoding→Fleece.PropertyList`1Fleece.FSharpData.Operators→Fleece.DecodeError
- Direction
- Fleece.FSharpData uses Fleece, so a change to Fleece can break Fleece.FSharpData, while a change to Fleece.FSharpData can't break Fleece.
- Position
- Below the diagonal: Fleece.FSharpData uses a module listed above it, which is the healthy direction.
15→4 Fleece.FSharpData.Internals uses Fleece✕
- Connections
- 1 pair of types, where a type in Fleece.FSharpData.Internals uses a type in Fleece.
- The types involved
Fleece.FSharpData.Internals.Internals→Fleece.PropertyList`1
- Direction
- Fleece.FSharpData.Internals uses Fleece, so a change to Fleece can break Fleece.FSharpData.Internals, while a change to Fleece.FSharpData.Internals can't break Fleece.
- Position
- Below the diagonal: Fleece.FSharpData.Internals uses a module listed above it, which is the healthy direction.
16→4 Fleece.FSharpData.OperatorsModule.Codec uses Fleece✕
- Connections
- 2 pairs of types, where a type in Fleece.FSharpData.OperatorsModule.Codec uses a type in Fleece.
- The types involved
Fleece.FSharpData.OperatorsModule.Codec.Codec→Fleece.Codec`4Fleece.FSharpData.OperatorsModule.Codec.Codec→Fleece.PropertyList`1
- Direction
- Fleece.FSharpData.OperatorsModule.Codec uses Fleece, so a change to Fleece can break Fleece.FSharpData.OperatorsModule.Codec, while a change to Fleece.FSharpData.OperatorsModule.Codec can't break Fleece.
- Position
- Below the diagonal: Fleece.FSharpData.OperatorsModule.Codec uses a module listed above it, which is the healthy direction.
17→4 Fleece.FSharpData.OperatorsModule.Decode uses Fleece✕
- Connections
- 1 pair of types, where a type in Fleece.FSharpData.OperatorsModule.Decode uses a type in Fleece.
- The types involved
Fleece.FSharpData.OperatorsModule.Decode.Decode→Fleece.DecodeError
- Direction
- Fleece.FSharpData.OperatorsModule.Decode uses Fleece, so a change to Fleece can break Fleece.FSharpData.OperatorsModule.Decode, while a change to Fleece.FSharpData.OperatorsModule.Decode can't break Fleece.
- Position
- Below the diagonal: Fleece.FSharpData.OperatorsModule.Decode uses a module listed above it, which is the healthy direction.
18→4 Fleece.FSharpData.OperatorsModule.Decode.Fail uses Fleece✕
- Connections
- 2 pairs of types, where a type in Fleece.FSharpData.OperatorsModule.Decode.Fail uses a type in Fleece.
- The types involved
Fleece.FSharpData.OperatorsModule.Decode.Fail.Fail→Fleece.DecodeErrorFleece.FSharpData.OperatorsModule.Decode.Fail.Fail→Fleece.PropertyList`1
- Direction
- Fleece.FSharpData.OperatorsModule.Decode.Fail uses Fleece, so a change to Fleece can break Fleece.FSharpData.OperatorsModule.Decode.Fail, while a change to Fleece.FSharpData.OperatorsModule.Decode.Fail can't break Fleece.
- Position
- Below the diagonal: Fleece.FSharpData.OperatorsModule.Decode.Fail uses a module listed above it, which is the healthy direction.
19→4 Fleece.Internals uses Fleece✕
- Connections
- 6 pairs of types, where a type in Fleece.Internals uses a type in Fleece.
- The types involved
Fleece.Internals.CodecCache`3→Fleece.Codec`4Fleece.Internals.GetArrCodec→Fleece.Codec`4Fleece.Internals.GetCodec→Fleece.Codec`4Fleece.Internals.GetCodec→Fleece.PropertyList`1Fleece.Internals.GetDec→Fleece.Codec`4Fleece.Internals.GetEnc→Fleece.Codec`4
- Direction
- Fleece.Internals uses Fleece, so a change to Fleece can break Fleece.Internals, while a change to Fleece.Internals can't break Fleece.
- Position
- Below the diagonal: Fleece.Internals uses a module listed above it, which is the healthy direction.
20→4 Fleece.Newtonsoft uses Fleece✕
- Connections
- 6 pairs of types, where a type in Fleece.Newtonsoft uses a type in Fleece.
- The types involved
Fleece.Newtonsoft.Encoding→Fleece.Codec`4Fleece.Newtonsoft.Encoding→Fleece.DateTimeContentsFleece.Newtonsoft.Encoding→Fleece.DecodeErrorFleece.Newtonsoft.Encoding→Fleece.IEncodingFleece.Newtonsoft.Encoding→Fleece.PropertyList`1Fleece.Newtonsoft.Operators→Fleece.DecodeError
- Direction
- Fleece.Newtonsoft uses Fleece, so a change to Fleece can break Fleece.Newtonsoft, while a change to Fleece.Newtonsoft can't break Fleece.
- Position
- Below the diagonal: Fleece.Newtonsoft uses a module listed above it, which is the healthy direction.
21→4 Fleece.Newtonsoft.OperatorsModule.Codec uses Fleece✕
- Connections
- 2 pairs of types, where a type in Fleece.Newtonsoft.OperatorsModule.Codec uses a type in Fleece.
- The types involved
Fleece.Newtonsoft.OperatorsModule.Codec.Codec→Fleece.Codec`4Fleece.Newtonsoft.OperatorsModule.Codec.Codec→Fleece.PropertyList`1
- Direction
- Fleece.Newtonsoft.OperatorsModule.Codec uses Fleece, so a change to Fleece can break Fleece.Newtonsoft.OperatorsModule.Codec, while a change to Fleece.Newtonsoft.OperatorsModule.Codec can't break Fleece.
- Position
- Below the diagonal: Fleece.Newtonsoft.OperatorsModule.Codec uses a module listed above it, which is the healthy direction.
22→4 Fleece.Newtonsoft.OperatorsModule.Decode uses Fleece✕
- Connections
- 1 pair of types, where a type in Fleece.Newtonsoft.OperatorsModule.Decode uses a type in Fleece.
- The types involved
Fleece.Newtonsoft.OperatorsModule.Decode.Decode→Fleece.DecodeError
- Direction
- Fleece.Newtonsoft.OperatorsModule.Decode uses Fleece, so a change to Fleece can break Fleece.Newtonsoft.OperatorsModule.Decode, while a change to Fleece.Newtonsoft.OperatorsModule.Decode can't break Fleece.
- Position
- Below the diagonal: Fleece.Newtonsoft.OperatorsModule.Decode uses a module listed above it, which is the healthy direction.
23→4 Fleece.Newtonsoft.OperatorsModule.Decode.Fail uses Fleece✕
- Connections
- 2 pairs of types, where a type in Fleece.Newtonsoft.OperatorsModule.Decode.Fail uses a type in Fleece.
- The types involved
Fleece.Newtonsoft.OperatorsModule.Decode.Fail.Fail→Fleece.DecodeErrorFleece.Newtonsoft.OperatorsModule.Decode.Fail.Fail→Fleece.PropertyList`1
- Direction
- Fleece.Newtonsoft.OperatorsModule.Decode.Fail uses Fleece, so a change to Fleece can break Fleece.Newtonsoft.OperatorsModule.Decode.Fail, while a change to Fleece.Newtonsoft.OperatorsModule.Decode.Fail can't break Fleece.
- Position
- Below the diagonal: Fleece.Newtonsoft.OperatorsModule.Decode.Fail uses a module listed above it, which is the healthy direction.
24→4 Fleece.Operators uses Fleece✕
- Connections
- 3 pairs of types, where a type in Fleece.Operators uses a type in Fleece.
- The types involved
Fleece.Operators.Operators→Fleece.Codec`4Fleece.Operators.Operators→Fleece.DecodeErrorFleece.Operators.Operators→Fleece.PropertyList`1
- Direction
- Fleece.Operators uses Fleece, so a change to Fleece can break Fleece.Operators, while a change to Fleece.Operators can't break Fleece.
- Position
- Below the diagonal: Fleece.Operators uses a module listed above it, which is the healthy direction.
25→4 Fleece.SystemJson uses Fleece✕
- Connections
- 6 pairs of types, where a type in Fleece.SystemJson uses a type in Fleece.
- The types involved
Fleece.SystemJson.Encoding→Fleece.Codec`4Fleece.SystemJson.Encoding→Fleece.DateTimeContentsFleece.SystemJson.Encoding→Fleece.DecodeErrorFleece.SystemJson.Encoding→Fleece.IEncodingFleece.SystemJson.Encoding→Fleece.PropertyList`1Fleece.SystemJson.Operators→Fleece.DecodeError
- Direction
- Fleece.SystemJson uses Fleece, so a change to Fleece can break Fleece.SystemJson, while a change to Fleece.SystemJson can't break Fleece.
- Position
- Below the diagonal: Fleece.SystemJson uses a module listed above it, which is the healthy direction.
26→4 Fleece.SystemJson.OperatorsModule.Codec uses Fleece✕
- Connections
- 2 pairs of types, where a type in Fleece.SystemJson.OperatorsModule.Codec uses a type in Fleece.
- The types involved
Fleece.SystemJson.OperatorsModule.Codec.Codec→Fleece.Codec`4Fleece.SystemJson.OperatorsModule.Codec.Codec→Fleece.PropertyList`1
- Direction
- Fleece.SystemJson.OperatorsModule.Codec uses Fleece, so a change to Fleece can break Fleece.SystemJson.OperatorsModule.Codec, while a change to Fleece.SystemJson.OperatorsModule.Codec can't break Fleece.
- Position
- Below the diagonal: Fleece.SystemJson.OperatorsModule.Codec uses a module listed above it, which is the healthy direction.
27→4 Fleece.SystemJson.OperatorsModule.Decode uses Fleece✕
- Connections
- 1 pair of types, where a type in Fleece.SystemJson.OperatorsModule.Decode uses a type in Fleece.
- The types involved
Fleece.SystemJson.OperatorsModule.Decode.Decode→Fleece.DecodeError
- Direction
- Fleece.SystemJson.OperatorsModule.Decode uses Fleece, so a change to Fleece can break Fleece.SystemJson.OperatorsModule.Decode, while a change to Fleece.SystemJson.OperatorsModule.Decode can't break Fleece.
- Position
- Below the diagonal: Fleece.SystemJson.OperatorsModule.Decode uses a module listed above it, which is the healthy direction.
28→4 Fleece.SystemJson.OperatorsModule.Decode.Fail uses Fleece✕
- Connections
- 2 pairs of types, where a type in Fleece.SystemJson.OperatorsModule.Decode.Fail uses a type in Fleece.
- The types involved
Fleece.SystemJson.OperatorsModule.Decode.Fail.Fail→Fleece.DecodeErrorFleece.SystemJson.OperatorsModule.Decode.Fail.Fail→Fleece.PropertyList`1
- Direction
- Fleece.SystemJson.OperatorsModule.Decode.Fail uses Fleece, so a change to Fleece can break Fleece.SystemJson.OperatorsModule.Decode.Fail, while a change to Fleece.SystemJson.OperatorsModule.Decode.Fail can't break Fleece.
- Position
- Below the diagonal: Fleece.SystemJson.OperatorsModule.Decode.Fail uses a module listed above it, which is the healthy direction.
29→4 Fleece.SystemTextJson uses Fleece✕
- Connections
- 6 pairs of types, where a type in Fleece.SystemTextJson uses a type in Fleece.
- The types involved
Fleece.SystemTextJson.Encoding→Fleece.Codec`4Fleece.SystemTextJson.Encoding→Fleece.DateTimeContentsFleece.SystemTextJson.Encoding→Fleece.DecodeErrorFleece.SystemTextJson.Encoding→Fleece.IEncodingFleece.SystemTextJson.Encoding→Fleece.PropertyList`1Fleece.SystemTextJson.Operators→Fleece.DecodeError
- Direction
- Fleece.SystemTextJson uses Fleece, so a change to Fleece can break Fleece.SystemTextJson, while a change to Fleece.SystemTextJson can't break Fleece.
- Position
- Below the diagonal: Fleece.SystemTextJson uses a module listed above it, which is the healthy direction.
29→5 Fleece.SystemTextJson uses Fleece.SystemTextJson.InternalsModule✕
- Connections
- 1 pair of types, where a type in Fleece.SystemTextJson uses a type in Fleece.SystemTextJson.InternalsModule.
- The types involved
Fleece.SystemTextJson.Encoding→Fleece.SystemTextJson.InternalsModule.JsonElementOrWriter
- Direction
- Fleece.SystemTextJson uses Fleece.SystemTextJson.InternalsModule, so a change to Fleece.SystemTextJson.InternalsModule can break Fleece.SystemTextJson, while a change to Fleece.SystemTextJson can't break Fleece.SystemTextJson.InternalsModule.
- Position
- Below the diagonal: Fleece.SystemTextJson uses a module listed above it, which is the healthy direction.
30→4 Fleece.SystemTextJson.OperatorsModule.Codec uses Fleece✕
- Connections
- 2 pairs of types, where a type in Fleece.SystemTextJson.OperatorsModule.Codec uses a type in Fleece.
- The types involved
Fleece.SystemTextJson.OperatorsModule.Codec.Codec→Fleece.Codec`4Fleece.SystemTextJson.OperatorsModule.Codec.Codec→Fleece.PropertyList`1
- Direction
- Fleece.SystemTextJson.OperatorsModule.Codec uses Fleece, so a change to Fleece can break Fleece.SystemTextJson.OperatorsModule.Codec, while a change to Fleece.SystemTextJson.OperatorsModule.Codec can't break Fleece.
- Position
- Below the diagonal: Fleece.SystemTextJson.OperatorsModule.Codec uses a module listed above it, which is the healthy direction.
31→4 Fleece.SystemTextJson.OperatorsModule.Decode uses Fleece✕
- Connections
- 1 pair of types, where a type in Fleece.SystemTextJson.OperatorsModule.Decode uses a type in Fleece.
- The types involved
Fleece.SystemTextJson.OperatorsModule.Decode.Decode→Fleece.DecodeError
- Direction
- Fleece.SystemTextJson.OperatorsModule.Decode uses Fleece, so a change to Fleece can break Fleece.SystemTextJson.OperatorsModule.Decode, while a change to Fleece.SystemTextJson.OperatorsModule.Decode can't break Fleece.
- Position
- Below the diagonal: Fleece.SystemTextJson.OperatorsModule.Decode uses a module listed above it, which is the healthy direction.
32→4 Fleece.SystemTextJson.OperatorsModule.Decode.Fail uses Fleece✕
- Connections
- 2 pairs of types, where a type in Fleece.SystemTextJson.OperatorsModule.Decode.Fail uses a type in Fleece.
- The types involved
Fleece.SystemTextJson.OperatorsModule.Decode.Fail.Fail→Fleece.DecodeErrorFleece.SystemTextJson.OperatorsModule.Decode.Fail.Fail→Fleece.PropertyList`1
- Direction
- Fleece.SystemTextJson.OperatorsModule.Decode.Fail uses Fleece, so a change to Fleece can break Fleece.SystemTextJson.OperatorsModule.Decode.Fail, while a change to Fleece.SystemTextJson.OperatorsModule.Decode.Fail can't break Fleece.
- Position
- Below the diagonal: Fleece.SystemTextJson.OperatorsModule.Decode.Fail uses a module listed above it, which is the healthy direction.
33→4 Fleece.FSharpData.OperatorsModule uses Fleece✕
- Connections
- 3 pairs of types, where a type in Fleece.FSharpData.OperatorsModule uses a type in Fleece.
- The types involved
Fleece.FSharpData.OperatorsModule.OperatorsModule→Fleece.Codec`4Fleece.FSharpData.OperatorsModule.OperatorsModule→Fleece.DecodeErrorFleece.FSharpData.OperatorsModule.OperatorsModule→Fleece.PropertyList`1
- Direction
- Fleece.FSharpData.OperatorsModule uses Fleece, so a change to Fleece can break Fleece.FSharpData.OperatorsModule, while a change to Fleece.FSharpData.OperatorsModule can't break Fleece.
- Position
- Below the diagonal: Fleece.FSharpData.OperatorsModule uses a module listed above it, which is the healthy direction.
33→14 Fleece.FSharpData.OperatorsModule uses Fleece.FSharpData✕
- Connections
- 1 pair of types, where a type in Fleece.FSharpData.OperatorsModule uses a type in Fleece.FSharpData.
- The types involved
Fleece.FSharpData.OperatorsModule.OperatorsModule→Fleece.FSharpData.Encoding
- Direction
- Fleece.FSharpData.OperatorsModule uses Fleece.FSharpData, so a change to Fleece.FSharpData can break Fleece.FSharpData.OperatorsModule, while a change to Fleece.FSharpData.OperatorsModule can't break Fleece.FSharpData.
- Position
- Below the diagonal: Fleece.FSharpData.OperatorsModule uses a module listed above it, which is the healthy direction.
34→4 Fleece.FSharpData.OperatorsModule.JsonCodec uses Fleece✕
- Connections
- 1 pair of types, where a type in Fleece.FSharpData.OperatorsModule.JsonCodec uses a type in Fleece.
- The types involved
Fleece.FSharpData.OperatorsModule.JsonCodec.JsonCodec→Fleece.Codec`4
- Direction
- Fleece.FSharpData.OperatorsModule.JsonCodec uses Fleece, so a change to Fleece can break Fleece.FSharpData.OperatorsModule.JsonCodec, while a change to Fleece.FSharpData.OperatorsModule.JsonCodec can't break Fleece.
- Position
- Below the diagonal: Fleece.FSharpData.OperatorsModule.JsonCodec uses a module listed above it, which is the healthy direction.
34→14 Fleece.FSharpData.OperatorsModule.JsonCodec uses Fleece.FSharpData✕
- Connections
- 1 pair of types, where a type in Fleece.FSharpData.OperatorsModule.JsonCodec uses a type in Fleece.FSharpData.
- The types involved
Fleece.FSharpData.OperatorsModule.JsonCodec.JsonCodec→Fleece.FSharpData.Encoding
- Direction
- Fleece.FSharpData.OperatorsModule.JsonCodec uses Fleece.FSharpData, so a change to Fleece.FSharpData can break Fleece.FSharpData.OperatorsModule.JsonCodec, while a change to Fleece.FSharpData.OperatorsModule.JsonCodec can't break Fleece.FSharpData.
- Position
- Below the diagonal: Fleece.FSharpData.OperatorsModule.JsonCodec uses a module listed above it, which is the healthy direction.
35→4 Fleece.Newtonsoft.OperatorsModule uses Fleece✕
- Connections
- 3 pairs of types, where a type in Fleece.Newtonsoft.OperatorsModule uses a type in Fleece.
- The types involved
Fleece.Newtonsoft.OperatorsModule.OperatorsModule→Fleece.Codec`4Fleece.Newtonsoft.OperatorsModule.OperatorsModule→Fleece.DecodeErrorFleece.Newtonsoft.OperatorsModule.OperatorsModule→Fleece.PropertyList`1
- Direction
- Fleece.Newtonsoft.OperatorsModule uses Fleece, so a change to Fleece can break Fleece.Newtonsoft.OperatorsModule, while a change to Fleece.Newtonsoft.OperatorsModule can't break Fleece.
- Position
- Below the diagonal: Fleece.Newtonsoft.OperatorsModule uses a module listed above it, which is the healthy direction.
35→20 Fleece.Newtonsoft.OperatorsModule uses Fleece.Newtonsoft✕
- Connections
- 1 pair of types, where a type in Fleece.Newtonsoft.OperatorsModule uses a type in Fleece.Newtonsoft.
- The types involved
Fleece.Newtonsoft.OperatorsModule.OperatorsModule→Fleece.Newtonsoft.Encoding
- Direction
- Fleece.Newtonsoft.OperatorsModule uses Fleece.Newtonsoft, so a change to Fleece.Newtonsoft can break Fleece.Newtonsoft.OperatorsModule, while a change to Fleece.Newtonsoft.OperatorsModule can't break Fleece.Newtonsoft.
- Position
- Below the diagonal: Fleece.Newtonsoft.OperatorsModule uses a module listed above it, which is the healthy direction.
36→4 Fleece.Newtonsoft.OperatorsModule.JsonCodec uses Fleece✕
- Connections
- 1 pair of types, where a type in Fleece.Newtonsoft.OperatorsModule.JsonCodec uses a type in Fleece.
- The types involved
Fleece.Newtonsoft.OperatorsModule.JsonCodec.JsonCodec→Fleece.Codec`4
- Direction
- Fleece.Newtonsoft.OperatorsModule.JsonCodec uses Fleece, so a change to Fleece can break Fleece.Newtonsoft.OperatorsModule.JsonCodec, while a change to Fleece.Newtonsoft.OperatorsModule.JsonCodec can't break Fleece.
- Position
- Below the diagonal: Fleece.Newtonsoft.OperatorsModule.JsonCodec uses a module listed above it, which is the healthy direction.
36→20 Fleece.Newtonsoft.OperatorsModule.JsonCodec uses Fleece.Newtonsoft✕
- Connections
- 1 pair of types, where a type in Fleece.Newtonsoft.OperatorsModule.JsonCodec uses a type in Fleece.Newtonsoft.
- The types involved
Fleece.Newtonsoft.OperatorsModule.JsonCodec.JsonCodec→Fleece.Newtonsoft.Encoding
- Direction
- Fleece.Newtonsoft.OperatorsModule.JsonCodec uses Fleece.Newtonsoft, so a change to Fleece.Newtonsoft can break Fleece.Newtonsoft.OperatorsModule.JsonCodec, while a change to Fleece.Newtonsoft.OperatorsModule.JsonCodec can't break Fleece.Newtonsoft.
- Position
- Below the diagonal: Fleece.Newtonsoft.OperatorsModule.JsonCodec uses a module listed above it, which is the healthy direction.
37→4 Fleece.SystemJson.OperatorsModule uses Fleece✕
- Connections
- 3 pairs of types, where a type in Fleece.SystemJson.OperatorsModule uses a type in Fleece.
- The types involved
Fleece.SystemJson.OperatorsModule.OperatorsModule→Fleece.Codec`4Fleece.SystemJson.OperatorsModule.OperatorsModule→Fleece.DecodeErrorFleece.SystemJson.OperatorsModule.OperatorsModule→Fleece.PropertyList`1
- Direction
- Fleece.SystemJson.OperatorsModule uses Fleece, so a change to Fleece can break Fleece.SystemJson.OperatorsModule, while a change to Fleece.SystemJson.OperatorsModule can't break Fleece.
- Position
- Below the diagonal: Fleece.SystemJson.OperatorsModule uses a module listed above it, which is the healthy direction.
37→25 Fleece.SystemJson.OperatorsModule uses Fleece.SystemJson✕
- Connections
- 1 pair of types, where a type in Fleece.SystemJson.OperatorsModule uses a type in Fleece.SystemJson.
- The types involved
Fleece.SystemJson.OperatorsModule.OperatorsModule→Fleece.SystemJson.Encoding
- Direction
- Fleece.SystemJson.OperatorsModule uses Fleece.SystemJson, so a change to Fleece.SystemJson can break Fleece.SystemJson.OperatorsModule, while a change to Fleece.SystemJson.OperatorsModule can't break Fleece.SystemJson.
- Position
- Below the diagonal: Fleece.SystemJson.OperatorsModule uses a module listed above it, which is the healthy direction.
38→4 Fleece.SystemJson.OperatorsModule.JsonCodec uses Fleece✕
- Connections
- 1 pair of types, where a type in Fleece.SystemJson.OperatorsModule.JsonCodec uses a type in Fleece.
- The types involved
Fleece.SystemJson.OperatorsModule.JsonCodec.JsonCodec→Fleece.Codec`4
- Direction
- Fleece.SystemJson.OperatorsModule.JsonCodec uses Fleece, so a change to Fleece can break Fleece.SystemJson.OperatorsModule.JsonCodec, while a change to Fleece.SystemJson.OperatorsModule.JsonCodec can't break Fleece.
- Position
- Below the diagonal: Fleece.SystemJson.OperatorsModule.JsonCodec uses a module listed above it, which is the healthy direction.
38→25 Fleece.SystemJson.OperatorsModule.JsonCodec uses Fleece.SystemJson✕
- Connections
- 1 pair of types, where a type in Fleece.SystemJson.OperatorsModule.JsonCodec uses a type in Fleece.SystemJson.
- The types involved
Fleece.SystemJson.OperatorsModule.JsonCodec.JsonCodec→Fleece.SystemJson.Encoding
- Direction
- Fleece.SystemJson.OperatorsModule.JsonCodec uses Fleece.SystemJson, so a change to Fleece.SystemJson can break Fleece.SystemJson.OperatorsModule.JsonCodec, while a change to Fleece.SystemJson.OperatorsModule.JsonCodec can't break Fleece.SystemJson.
- Position
- Below the diagonal: Fleece.SystemJson.OperatorsModule.JsonCodec uses a module listed above it, which is the healthy direction.
39→4 Fleece.SystemTextJson.OperatorsModule uses Fleece✕
- Connections
- 3 pairs of types, where a type in Fleece.SystemTextJson.OperatorsModule uses a type in Fleece.
- The types involved
Fleece.SystemTextJson.OperatorsModule.OperatorsModule→Fleece.Codec`4Fleece.SystemTextJson.OperatorsModule.OperatorsModule→Fleece.DecodeErrorFleece.SystemTextJson.OperatorsModule.OperatorsModule→Fleece.PropertyList`1
- Direction
- Fleece.SystemTextJson.OperatorsModule uses Fleece, so a change to Fleece can break Fleece.SystemTextJson.OperatorsModule, while a change to Fleece.SystemTextJson.OperatorsModule can't break Fleece.
- Position
- Below the diagonal: Fleece.SystemTextJson.OperatorsModule uses a module listed above it, which is the healthy direction.
39→29 Fleece.SystemTextJson.OperatorsModule uses Fleece.SystemTextJson✕
- Connections
- 1 pair of types, where a type in Fleece.SystemTextJson.OperatorsModule uses a type in Fleece.SystemTextJson.
- The types involved
Fleece.SystemTextJson.OperatorsModule.OperatorsModule→Fleece.SystemTextJson.Encoding
- Direction
- Fleece.SystemTextJson.OperatorsModule uses Fleece.SystemTextJson, so a change to Fleece.SystemTextJson can break Fleece.SystemTextJson.OperatorsModule, while a change to Fleece.SystemTextJson.OperatorsModule can't break Fleece.SystemTextJson.
- Position
- Below the diagonal: Fleece.SystemTextJson.OperatorsModule uses a module listed above it, which is the healthy direction.
40→4 Fleece.SystemTextJson.OperatorsModule.JsonCodec uses Fleece✕
- Connections
- 1 pair of types, where a type in Fleece.SystemTextJson.OperatorsModule.JsonCodec uses a type in Fleece.
- The types involved
Fleece.SystemTextJson.OperatorsModule.JsonCodec.JsonCodec→Fleece.Codec`4
- Direction
- Fleece.SystemTextJson.OperatorsModule.JsonCodec uses Fleece, so a change to Fleece can break Fleece.SystemTextJson.OperatorsModule.JsonCodec, while a change to Fleece.SystemTextJson.OperatorsModule.JsonCodec can't break Fleece.
- Position
- Below the diagonal: Fleece.SystemTextJson.OperatorsModule.JsonCodec uses a module listed above it, which is the healthy direction.
40→29 Fleece.SystemTextJson.OperatorsModule.JsonCodec uses Fleece.SystemTextJson✕
- Connections
- 1 pair of types, where a type in Fleece.SystemTextJson.OperatorsModule.JsonCodec uses a type in Fleece.SystemTextJson.
- The types involved
Fleece.SystemTextJson.OperatorsModule.JsonCodec.JsonCodec→Fleece.SystemTextJson.Encoding
- Direction
- Fleece.SystemTextJson.OperatorsModule.JsonCodec uses Fleece.SystemTextJson, so a change to Fleece.SystemTextJson can break Fleece.SystemTextJson.OperatorsModule.JsonCodec, while a change to Fleece.SystemTextJson.OperatorsModule.JsonCodec can't break Fleece.SystemTextJson.
- Position
- Below the diagonal: Fleece.SystemTextJson.OperatorsModule.JsonCodec 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 — Accessibility
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A05:2025 — Injection | 10 | High / Critical |
Roadmap
Top priorities: Resolve the 1 No ADRs found finding(s) in ADR Quality — start with docs.fsproj; Resolve the 6 Orphaned knowledge finding(s) in Knowledge Freshness — start with Fleece.fs, doclib.fs, Fleece.SystemTextJson.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.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 1 No ADRs found finding(s) in ADR Quality — start with docs.fsproj. | +6.7 pts | Low | ADR Quality |
| Resolve the 6 Orphaned knowledge finding(s) in Knowledge Freshness — start with Fleece.fs, doclib.fs, Fleece.SystemTextJson.fs. | +5.4 pts | Low | 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. | +4.9 pts | Medium | Architecture documentation |
| Resolve the 2 Orphaned file finding(s) in Knowledge Freshness — start with Compatibility.fs, Program.fs. | +2.3 pts | Low | Knowledge Freshness |
| Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href. | +3.4 pts | Medium | Keyboard semantics |
| Write a diagnostic trail the user can hand back with a bug report: a log file under the platform's per-user data directory, switchable with a `--verbose`/`--debug` flag. Start with the error paths that emit nothing — a discarded error is the failure the user cannot describe and you cannot reproduce. | +3.2 pts | Medium | Observability |
| Resolve the 1 Further orphaned files (smaller) finding(s) in Knowledge Freshness. | +1.5 pts | Low | Knowledge Freshness |
| Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1. | +2.9 pts | Medium | Visual & motion safety |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 0.5 | Slop | Static Analysis (SAST): High: REDACTED |
| src/Fleece.FSharpData/Fleece.FSharpData.fs | 7.0 | Near-clean | God Classes: TooManyMethods: Encoding |
| src/Fleece/Fleece.fs | 7.1 | Near-clean | God Classes: FileTooLong: Fleece/Fleece.fs |
| docsrc/tool/doclib.fs | 7.4 | Near-clean | Cyclomatic Complexity: SemVer.parse (cyclomatic 16) |
| src/Fleece.SystemTextJson/Fleece.SystemTextJson.fs | 7.8 | Near-clean | God Classes: TooManyMethods: Encoding |
| src/Fleece.NewtonsoftJson/Fleece.NewtonsoftJson.fs | 7.8 | Near-clean | God Classes: TooManyMethods: Encoding |
| src/Fleece/Compatibility.fs | 7.8 | Near-clean | God Classes: TooManyFunctions: OperatorsModule |
| REDACTED | 7.9 | Near-clean | Static Analysis (SAST): Medium: REDACTED |
| src/Fleece.SystemTextJson/Fleece.SystemTextJson.fsproj | 8.0 | Near-clean | Dependency Hygiene: Deprecated: System.Text.Json |
| src/Fleece.SystemJson/Fleece.SystemJson.fs | 8.5 | Near-clean | God Classes: TooManyMethods: Encoding |
| docsrc/tool/docsTool.fsproj | 9.3 | Near-clean | Dependency Hygiene: Outdated: FSharp.Formatting |
| Benchmarks/Benchmarks.fsproj | 9.5 | Near-clean | Dependency Hygiene: Outdated: FSharp.Core |
| src/Fleece.FSharpData/Fleece.FSharpData.fsproj | 9.5 | Near-clean | Dependency Hygiene: Outdated: FSharp.Data |
| src/Fleece.NewtonsoftJson/Fleece.NewtonsoftJson.fsproj | 9.5 | Near-clean | Dependency Hygiene: Outdated: Newtonsoft.Json |
| docsrc/docs/docs.fsproj | 9.5 | Near-clean | ADR Quality: No ADRs found |
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 38 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.8, the weighted average across measured dimensions.
What we checked — 38 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, 71 of 82 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Canine Code Analyzer duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 | ✓ deterministic |
Run transparency — what happened this run
- D8 Code Coverage — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Coverage NOT MEASURED: `--collect:"XPlat Code Coverage"` names a data collector that ships in the `coverlet.collector` package, and this repository wires up none — no test project references it and no runsettings declares one. The absence of coverage here is therefore not evidence about the suite or about our analyzer environment: without a collector, `--collect` produces nothing even from a suite that builds and passes. Add a `coverlet.collector` PackageReference to the test project(s) (or commit the Cobertura/OpenCover/lcov report your CI produces) and real coverage will be measured. It is excluded from the score rather than counted as a near-zero defect. You can widen what we reach: add the `coverlet.collector` package to the test projects to enable coverage (or commit the Cobertura/OpenCover/lcov report your CI produces).
- D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test reliability NOT MEASURED: the test run produced no results for any test tier, so no test ever ran and flakiness could not be exercised. The cause could not be attributed, so it is excluded from the score rather than read as an absence of tests.
- D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. All 8 significant source file(s) were last meaningfully changed so long ago that no living knowledge remains — nothing since has been substantial enough to re-establish ownership (a broad, mechanical sweep that touches many files shallowly does not count, and neither does no activity at all). There is no concentration to measure, so the bus factor is not scored. This is not a clean bill: nobody currently holds working knowledge of this code (see D34 Knowledge Freshness). Counted over 7 of the 9 production source files in this repository: 1 are under the ~2,400-byte size floor this dimension measures over, and the remaining 1 have no attributable history left to measure.
- D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D21's deterministic naming rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. Until then its declarations carry no naming verdict this run — this says nothing about whether its names are consistent.
- D22 Internal API Consistency — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. This repository's source is written only in languages whose packages are published through a manifest, and no manifest in the tree makes a publication act: either there is no package manifest of any ecosystem (no package.json, pyproject.toml, setup.py, gemspec, Cargo.toml, pom.xml, build.gradle, composer.json, pubspec.yaml or mix.exs), or every one present declares in its package manager's own terms that it is not published (an npm package marked "private": true, a Cargo package with publish = false, a pubspec with publish_to: none, a Composer "project", a Poetry project with package-mode = false, or the "Private :: Do Not Upload" classifier). With no publication act there is no intentionally-exposed surface for API consistency to be judged over.
- D24 Comment Value — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 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.
- AX6 Interface segregation — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is computed over the public interfaces this run's compilations declare, and none was loaded, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- C1 Data Protection — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These personal data controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks personal data controls.
- C2 Access Controls — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These authorization controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks authorization controls.
- C3 Audit Trail — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These audit controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks audit controls.
- C4 Data Retention — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These retention controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks retention controls.
- C5 Data-Subject Rights — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These data-subject rights controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks data-subject rights controls.
- IC1 Incompleteness & stubs — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
- X1 Async correctness — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X12 Unreachable branch — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X13 Undrained process stream — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X14 Bypassable address classification — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X15 Unvalidated length from an untrusted reader — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X16 Unfloored truncation loop — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X17 Uncapped recursion over a caller-supplied document — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X18 Disposal-pattern correctness — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X19 Unrestored process-global state — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X2 Cancellation propagation — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X21 Side-effecting pattern guard — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X22 Contradicted release guard — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X24 Document value interpolated into markup unescaped — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X25 Inert configuration knob — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X26 Unsynchronised callback handoff — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X29 Per-element action decided by a fixed element — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X3 Exception handling — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X30 Support guard that admits what it rejects — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X32 Type resolved by simple name across every loaded assembly — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X4 Structured logging — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X5 Nullable reference types — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
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.
- 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.
- D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
- D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
- 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.
- AC1 Text alternatives: Alt-text is detected structurally — the scan sees that an alternative EXISTS, not whether it meaningfully describes the image, and decorative-vs-missing is judged by attribute shape; runtime-injected images and a non-role=img decorative svg are out of scope. This is accessibility readiness, never a WCAG conformance claim.
- AC2 Forms & labels: Label association is read from static markup — a label wired up at runtime (JS-set aria-labelledby, framework-injected ids) reads as missing, a present label says nothing about whether its text is correct. A known UI-library field component (e.g. a JSX <TextField>) is now checked conservatively — flagged only when it carries NO label/aria-label/aria-labelledby/id/name — but wrapper/context-labelled libraries (Chakra/Radix FormControl+FormLabel) aren't statically visible (possible false positive) and non-JSX lowercased components are still skipped. A click handler on a plain element is now asked for a name too (it is a control the author declared), but the subtree test that answers it is deliberately generous: any DYNAMIC text expression in the subtree counts as a name, so an icon chosen by a ternary ({cond ? <IconA/> : <IconB/>}) reads as named, and a glyph component from a library the icon-import list does not know still names its parent. A clean result is "no unlabelled control found", not a labelling proof.
- AC3 Page structure: Page structure is read from the static markup tree — landmarks, headings and lang injected at runtime aren't seen, heading ORDER is checked structurally (not against the rendered visual hierarchy), and lang/title/main fire only on full documents, never partials, and the data-table check sees header-cell presence (a <th> exists), not whether each header correctly associates with its cells. Static readiness, not conformance.
- AC4 Keyboard semantics: Keyboard semantics are inferred from markup attributes — interactivity wired purely in script, focus managed at runtime, and component-level handlers are invisible. A clean result means "no static keyboard-trap shape", not a keyboard-operability proof.
- AC6 Visual & motion safety: Contrast and motion safety are PARTIAL by construction — literal colours (hex/rgb/hsl/named) in inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS top-level declarations are read (same-rule/same-element colour+background pairs only); computed/runtime/theme colour, external-CDN stylesheets, CSS-in-JS dynamic (${…}) and nested-selector colours, cross-element pairs and image contrast stay out of reach, so a clean result is bounded by what the static CSS itself shows.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
Dimensions
D1 · Cyclomatic Complexity
1 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was SemVer.parse at 16.
What to do
- Bring the 1 body over 15 down to 15 or less in Cyclomatic Complexity — start with SemVer.parse (cyclomatic 16). — Refactoring it lifts Cyclomatic Complexity from 9.9 to about 10.0/10.
D2 · Cognitive Complexity
1 method(s) exceeded the cognitive complexity threshold of 15; the worst was SemVerInfo.CompareTo at 16.
What to do
- Bring the 1 body over 15 down to 15 or less in Cognitive Complexity — start with SemVerInfo.CompareTo (cognitive 16). — Refactoring it lifts Cognitive Complexity from 9.9 to about 10.0/10.
D3 · God Classes
10 god class(es) detected.
What to do
- Resolve the 5 TooManyMethods finding(s) in God Classes — start with Fleece.SystemTextJson.fs, Fleece.FSharpData.fs, Fleece.NewtonsoftJson.fs. — One of this dimension's main actionable groups (5 warning-level).
- Resolve the 3 TooManyFunctions finding(s) in God Classes — start with Fleece.fs (2), Compatibility.fs. — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 2 FileTooLong finding(s) in God Classes — start with Fleece.fs, doclib.fs. — One of this dimension's main actionable groups (2 warning-level).
D4 · Code Duplication
18 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.
What to do
- Resolve the 2 Duplicated block (5 lines × 2) finding(s) in Code Duplication — start with Fleece.NewtonsoftJson.fs, Fleece.fs. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 Members sharing a duplicated core (4 members, 50+ identical tokens) finding(s) in Code Duplication — start with Fleece.FSharpData.fs. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Duplicated block (44 lines × 2) finding(s) in Code Duplication — start with Fleece.FSharpData.fs. — One of this dimension's main actionable groups (1 warning-level).
D5 · Coupling
13 projects, 0 dependency cycle(s), 0 unstable depended-on project(s).
D6 · Cohesion (LCOM4)
0 of 2 classes have LCOM4 above 3.
D12 · Dependency Hygiene
11 outdated, 1 vulnerable, 1 deprecated packages.
What to do
- Resolve the 6 Outdated finding(s) in Dependency Hygiene — start with docsTool.fsproj (2), Benchmarks.fsproj, Fleece.FSharpData.fsproj. — One of this dimension's main actionable groups (6 recommendation-level).
- Resolve the 1 Deprecated finding(s) in Dependency Hygiene — start with Fleece.SystemTextJson.fsproj. — One of this dimension's main actionable groups (1 warning-level).
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D14 · License Compliance
0 of 163 packages use a banned license. ★ DEPTH: this repository's MSBuild projects declare 12 direct `PackageReference`(s), and 138 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.
D20 · ADR Quality
No architecture decision records were found.
What to do
- Resolve the 1 No ADRs found finding(s) in ADR Quality — start with docs.fsproj. — One of this dimension's main actionable groups (1 recommendation-level).
D26 · Project Cohesion
0 of 7 build units (MSBuild) flagged as possibly oversized/incoherent.
D27 · Navigability
81 % of calls cross a namespace and 3 % go through an interface, but 100 % of collaborators are co-located — so a call's collaborators sit together and tracing stays easy. Baseline: small — navigation cost is tolerated.
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
10 finding(s): 0 critical, 5 high, 5 medium, 0 low. 5 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 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2). — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2). — One of this dimension's main actionable groups (2 warning-level).
- No action in Static Analysis (SAST) — all 5 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 (5 issue-level, 0 of them charged here).
D34 · Knowledge Freshness
8 of 8 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is src/Fleece/Fleece.fs. Counted over 8 of the 9 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 6 Orphaned knowledge finding(s) in Knowledge Freshness — start with Fleece.fs, doclib.fs, Fleece.SystemTextJson.fs. — One of this dimension's main actionable groups (6 issue-level).
- Resolve the 2 Orphaned file finding(s) in Knowledge Freshness — start with Compatibility.fs, Program.fs. — One of this dimension's main actionable groups (2 recommendation-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.
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 13 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
AC1 · Text alternatives
AC2 · Forms & labels
AC3 · Page structure
- A <table> with data cells but no <th> gives assistive technology no way to associate cells with their headers. Mark the header row/column cells as <th> (with a scope). (×3) — REDACTED:3, docsrc/tool/templates/reference/part-nested.cshtml:2, docsrc/tool/templates/reference/part-nested.cshtml:29
- No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>. — docsrc/tool/templates/template.cshtml:2
What to do
- Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh.
AC4 · Keyboard semantics
- This <code> binds mouse-enter and mouse-leave and nothing else — no click, no key handler, no focus handler, and no tabindex="0", so it cannot even take focus. A keyboard user cannot hover, so whatever the pair reveals or highlights is reachable with a mouse only. Bind the same state to focus/blur as well, and add tabindex="0"="0" so the element can receive that focus. — REDACTED:13
What to do
- Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href.
AC6 · Visual & motion safety
- `span.omitted` sets color: #808080 on background-color: #3c4e52 — 2.2:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. (×2) — docsrc/files/style.css:60, docsrc/content/content/style.css:60
- `h1 a` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. (×2) — docsrc/files/style.css:222, docsrc/content/content/style.css:222
What to do
- Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1.
AX10 · Code composition
AX3 · Project dependency cycles
AX4 · Dependency direction
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
P2 · Observability
- No logging or diagnostics emission found. This repository ships a binary its users launch rather than a service you operate, so there is no operator to page — but when a run fails on a user's machine, neither they nor you have anything to read.
What to do
- Write a diagnostic trail the user can hand back with a bug report: a log file under the platform's per-user data directory, switchable with a `--verbose`/`--debug` flag. Start with the error paths that emit nothing — a discarded error is the failure the user cannot describe and you cannot reproduce.
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:6
- `Benchmarks/Benchmarks.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`. — Benchmarks/Benchmarks.fsproj:16
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.
P6 · Release Hygiene
PF1 · Benchmark discipline
- A F#/VB BenchmarkDotNet suite exists but nothing turns on its allocation measurement — allocations (the main way hot code pressures a garbage collector or allocator) aren't being measured. — Benchmarks/Parsing.fs
What to do
- Add [<MemoryDiagnoser>] to the benchmarks so allocation regressions are visible, not just time.
S1 · Web-Security Posture
- `https://code.jquery.com/jquery-1.8.0.js` is executed by this page with no Subresource Integrity. Whoever can answer that request — the CDN, anyone who compromises it, anyone on the network path — runs arbitrary script in this page's origin, with its session. The URL also names no version, so it resolves to whatever that origin serves at fetch time — the executed bytes can change with nobody touching this repository. 3 such include(s) across the repository's markup. — docsrc/tool/templates/template.cshtml:10
What to do
- Pin third-party scripts and verify them: name an exact version in the URL and add an `integrity="sha384-…"` hash alongside `crossorigin="anonymous"` (both are required — an integrity hash on a cross-origin script without `crossorigin` is not evaluated, it blocks the script). Where the vendor ships a continuously-updated loader and publishes no stable hash (tag managers, analytics, chat widgets), Subresource Integrity is not available: constrain it instead with a `Content-Security-Policy` that names the exact origins allowed to execute, and drop the script from the pages that do not need it. Where the page is shipped inside a package that others host, prefer vendoring the asset and serving it from the app’s own origin, so no consumer inherits a third-party dependency they did not choose.
X28 · Index access outside its own emptiness guard
WCAG coverage — what static analysis assessed
| Dimension | WCAG 2.2 A/AA criteria | Coverage |
|---|---|---|
| AC1 · Text alternatives | 1.1.1, 1.2.2, 1.2.5 | Partial signal |
| AC2 · Forms & labels | 1.3.1, 3.3.2, 4.1.2 | Partial signal |
| AC3 · Page structure | 1.4.4, 2.2.1, 2.4.1, 2.4.2, 3.1.1, 4.1.2 | Partial signal |
| AC4 · Keyboard semantics | 2.1.1, 2.4.3 | Partial signal |
| AC6 · Visual & motion safety | 1.4.3, 2.4.7 | Partial — literal CSS only |
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 80% | Checked 4 of 11 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 100% | Exemplary | Strongest area. |
| Maturity | 41% | Weak — gated by D34, M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 47% | Adequate — gated by P2, P3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 85% | Strong | Solid. |
| Accessibility | 42% | Weak — gated by AC4, AC6 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Performance | 80% | Strong | Solid. |
Unscored — 2 check(s) recorded observations but carry no score
- D36 Supply-chain Provenance & Signing — 1 observation(s) recorded · The CI pipeline publishes no artifact — no package publish, container push or release with files to download. Supply-chain provenance, signing and an SBOM describe a PUBLISHED artifact for the people who obtain it, so there is nothing to attest here; a deployment of the service itself publishes nothing for anyone else to verify. Add them to the release pipeline when this repo starts publishing artifacts (a package, a container image, or a release with downloadable files). Build integrity and workflow-token hygiene are reported below: they describe what the CI runs and the token it runs with, neither of which is affected by whether the pipeline ships an artifact.
- SC1 Supply-chain hygiene — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Not evidenced — 5 control(s) we could not find positive evidence for
- C3 Audit Trail — Not assessed: these audit controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks audit controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- C4 Data Retention — Not assessed: these retention controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks retention controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- C5 Data-Subject Rights — Not assessed: these data-subject rights controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks data-subject rights controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- P4 Deployment & Rollback — not evidenced — no deploy/rollback/approval signal in the repo; absence of evidence is not evidence of a manual release
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 71 check(s) not relevant to this codebase
- AC5 ARIA correctness — No ARIA usage found in the parsed markup — AC5 not applicable here.
- AX1 Captive dependencies — Not applicable: this repository's F# imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's; this repository's JavaScript imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's.
- AX2 Stateful singletons — No container singleton was found, so there is no shared instance for concurrent requests to race on. No F# function in this code takes an ASP.NET Core or Suave HttpContext (a Giraffe, Saturn, Falco, Oxpecker or Suave handler) and no F# class is an ASP.NET Core controller, so no request handler shares module state between request threads. TypeScript/JavaScript runs each process's requests on one event loop, so no two requests write a shared object at the same instant (interleaving across an await is a different defect).
- 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
- AX8 Test isolation — no test/production split to check
- AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
- AXB1 Runtime evidence locked — no reproducible boot — This repository has nothing the runtime tiers could boot or serve — 6 markup documents under demonstration, documentation or developer-tool trees (or modules the build marks non-production) but none in the product; no UI framework or web-server dependency, no UI component source, no native UI project and no API definition — those pages are demos or docs for the code, not something this tier can 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 — ~1587 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.
- D11 Test Reliability — Test reliability not measured — no test run produced results
- D16 Bus Factor — dormant codebase — no living knowledge left to concentrate
- D17 Explicit Debt — the C# workspace loaded 0 projects, so explicit-debt density could not be measured
- D18 Solution Shape — D18 scores the shape of a C#/VB .NET solution; this repository's .NET projects are all F# (.fsproj), which the C#/VB workspace does not load, so the dimension does not apply.
- D19 Documentation Quality — No runnable or published unit to look for an example in, and no multi-project root README to look for a map in; the other documentation kinds are withheld (see the gaps), so documentation quality is not applicable here.
- D21 Naming Consistency — Naming consistency is measured on C# and TypeScript only; F#, JavaScript not measured.
- D22 Internal API Consistency — No intentionally-exposed public API to evaluate for consistency.
- D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D24 Comment Value — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only; comments in this repository's .fs source were not judged.
- D25 ADR Conformance — no ADRs to check
- D30 Dependency Vulnerabilities — nuget: the solution did not restore on the analyzer's .NET SDK (an SDK/target-framework/restore mismatch, common for an older codebase), so there was no restored dependency graph to 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
- D8 Code Coverage — Coverage not measured — no coverage collector is wired up
- DM1 Domain Modelling — not scored — this repository shows only 1 of the 3 signals this lens looks for (39 value object(s))
- 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
- 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'.
- 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 — coverage not measured: this check compares the coverage of the analyzer's own test run across the domain and web layers, and that run measured none here — Test coverage (D8) says why
- 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.
- PF3 Async & latency hygiene — Not applicable: this repository declares no async functions, so there is no asynchronous code for a blocking call to stall.
- X1 Async correctness — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X10 Duplicated predicate — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X12 Unreachable branch — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X13 Undrained process stream — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X14 Bypassable address classification — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X15 Unvalidated length from an untrusted reader — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X16 Unfloored truncation loop — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X17 Uncapped recursion over a caller-supplied document — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X18 Disposal-pattern correctness — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X19 Unrestored process-global state — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X2 Cancellation propagation — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X20 Mistyped argument guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X21 Side-effecting pattern guard — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X22 Contradicted release guard — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- 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 — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X25 Inert configuration knob — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X26 Unsynchronised callback handoff — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X27 Collection changed while being enumerated — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- 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 — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X7 Silent fallback defaults — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
Critical — 12 finding(s)
- Orphaned knowledge src/Fleece/Fleece.fs:1
- Orphaned knowledge docsrc/tool/doclib.fs:1
- Orphaned knowledge src/Fleece.SystemTextJson/Fleece.SystemTextJson.fs:1
- Orphaned knowledge src/Fleece.NewtonsoftJson/Fleece.NewtonsoftJson.fs:1
- Orphaned knowledge src/Fleece.FSharpData/Fleece.FSharpData.fs:1
- Orphaned knowledge src/Fleece.SystemJson/Fleece.SystemJson.fs:1
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Hover-only interaction on <code> REDACTED:13
Serious — 49 finding(s)
- TooManyMethods: Encoding src/Fleece.SystemTextJson/Fleece.SystemTextJson.fs:39
- TooManyMethods: Encoding src/Fleece.FSharpData/Fleece.FSharpData.fs:74
- TooManyMethods: Encoding src/Fleece.NewtonsoftJson/Fleece.NewtonsoftJson.fs:80
- TooManyMethods: Encoding src/Fleece.SystemJson/Fleece.SystemJson.fs:69
- TooManyMethods: GetCodec src/Fleece/Fleece.fs:623
- Data table has no header cells REDACTED:3
- Data table has no header cells docsrc/tool/templates/reference/part-nested.cshtml:2
- Data table has no header cells docsrc/tool/templates/reference/part-nested.cshtml:29
- TooManyFunctions: OperatorsModule src/Fleece/Compatibility.fs:70
- TooManyFunctions: Codecs src/Fleece/Fleece.fs:400
- TooManyFunctions: Operators src/Fleece/Fleece.fs:900
- Low contrast colour pair in CSS (2.2:1) docsrc/files/style.css:60
- Low contrast colour pair in CSS (2.2:1) docsrc/content/content/style.css:60
- Focus outline removed in CSS without a :focus replacement docsrc/files/style.css:222
- Focus outline removed in CSS without a :focus replacement docsrc/content/content/style.css:222
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- FileTooLong: Fleece/Fleece.fs src/Fleece/Fleece.fs
- FileTooLong: tool/doclib.fs docsrc/tool/doclib.fs
- Duplicated block (5 lines × 2) src/Fleece.NewtonsoftJson/Fleece.NewtonsoftJson.fs:196
- Duplicated block (5 lines × 2) src/Fleece/Fleece.fs:954
- Page without a main landmark docsrc/tool/templates/template.cshtml:2
- SemVer.parse (cyclomatic 16) docsrc/tool/doclib.fs:314
- Deprecated: System.Text.Json src/Fleece.SystemTextJson/Fleece.SystemTextJson.fsproj:17
- SemVerInfo.CompareTo (cognitive 16) docsrc/tool/doclib.fs:238
- REDACTED
- REDACTED
- Members sharing a duplicated core (4 members, 50+ identical tokens) src/Fleece.FSharpData/Fleece.FSharpData.fs:1
- Duplicated block (44 lines × 2) src/Fleece.FSharpData/Fleece.FSharpData.fs:180
- Duplicated block (38–40 lines × 3) src/Fleece.FSharpData/Fleece.FSharpData.fs:219
- Duplicated block (55–57 lines × 3) src/Fleece.FSharpData/Fleece.FSharpData.fs:124
- Duplicated block (53 lines × 4) src/Fleece.FSharpData/Fleece.FSharpData.fs:308
- Duplicated block (4–13 lines × 4) src/Fleece.FSharpData/Fleece.FSharpData.fs:97
- Duplicated block (32 lines × 3) src/Fleece.FSharpData/Fleece.FSharpData.fs:268
- Duplicated block (9 lines × 3) src/Fleece.FSharpData/Fleece.FSharpData.fs:82
- Duplicated block (9 lines × 2) src/Fleece.FSharpData/Fleece.FSharpData.fs:71
- Duplicated block (8 lines × 4) src/Fleece.FSharpData/Fleece.FSharpData.fs:292
- Duplicated block (2–8 lines × 4) src/Fleece.FSharpData/Fleece.FSharpData.fs:365
- Duplicated block (15–17 lines × 4) src/Fleece.FSharpData/Fleece.FSharpData.fs:143
- Duplicated block (7–8 lines × 3) src/Fleece.FSharpData/Fleece.FSharpData.fs:187
- Duplicated block (6 lines × 2) src/Fleece/Compatibility.fs:114
- Duplicated block (5 lines × 4) src/Fleece/Fleece.fs:470
- Duplicated block (4–5 lines × 4) src/Fleece.FSharpData/Fleece.FSharpData.fs:113
- Duplicated block (6 lines × 3) src/Fleece.SystemTextJson/Fleece.SystemTextJson.fs:265
- No structured logging
- Third-party script without Subresource Integrity docsrc/tool/templates/template.cshtml:10
- NuGet dependencies are not locked
Minor — 16 finding(s)
- Outdated: FSharp.Core Benchmarks/Benchmarks.fsproj:17
- Outdated: FSharp.Data src/Fleece.FSharpData/Fleece.FSharpData.fsproj:17
- Outdated: Newtonsoft.Json src/Fleece.NewtonsoftJson/Fleece.NewtonsoftJson.fsproj:17
- Outdated: FSharp.Formatting docsrc/tool/docsTool.fsproj:18
- Outdated: FSharp.Formatting.Literate docsrc/tool/docsTool.fsproj:17
- Outdated: System.Text.Json src/Fleece.SystemTextJson/Fleece.SystemTextJson.fsproj:17
- Orphaned file src/Fleece/Compatibility.fs:1
- Orphaned file docsrc/tool/Program.fs:1
- No ADRs found docsrc/docs/docs.fsproj:4
- Further orphaned files (smaller)
- REDACTED
- No ADRs
- No architecture diagram/doc
- No SAST REDACTED:6
- No dependency-update automation Benchmarks/Benchmarks.fsproj:16
- Benchmarks don't track allocations Benchmarks/Parsing.fs
Minor — 5 finding(s)
- Outdated: Microsoft.NETFramework.ReferenceAssemblies
- Outdated: FsCheck
- Outdated: System.Json
- Outdated: FSharpPlus
- Outdated: BenchmarkDotNet
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-7891aa566e1244649511fd366d592fe6/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-7891aa566e1244649511fd366d592fe6/tree.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-tree.json |
| D29 · Static Analysis (SAST) | semgrep | — | semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/canine-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt . | 10 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | nuget | — | nuget: not applicable — nuget: the solution did not restore on the analyzer's .NET SDK (an SDK/target-framework/restore mismatch, common for an older codebase), so there was no restored dependency graph to 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-2c48bb7c5e73455f8c1b2db30ad420e1 | 0 | artifacts/raw/osv-scanner.json |