Executive summary
Smaug123/WoofWare.Myriad falls short of our standard for production, held back most by its Code Health lens, the quality of the code itself. It scores 58 out of 100 and is rated Adequate, and two of its three critical findings are security problems in its automatic dependency updates and in the packages it uses.
Code Health, at 47, is the weakest lens and counts most in the score. The best first step for the work it takes is making the naming consistent, worth about 4 points. Simplifying the hardest methods would lift Code Health itself, worth about 5 points. Raising Code Health to 70 would lift the score to about 66.
One automatic update takes new releases before a bad one can be spotted. One known security hole in a package the code depends on can be used by attackers. Setting a waiting period for automatic updates and updating the vulnerable packages would close both risks. The set of files in separate parts that keep changing together needs that dependency made explicit.
The product code is 102,005 lines, about €120,000 to rebuild.
If Code Health rose from 47 to 70, the lowest score rated Strong, the score would rise from 58 to about 66.
Rebuild cost: about €120,000 · Estimate
| Cost to rebuild | €41,000 to €210,000, for 688 to 2,181 hours of work, about 0.9 person-years for 1 to 2 engineers |
|---|---|
| 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.8 at a score of 58. 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 | Large: 102,005 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 — bounded-context dependency graph
Architecture: which parts of the code depend on which
| uses → | 1 ConsumePlugin | 2 ConsumePlugin.ArgParserRuntime_BasicNoPositionals | 3 ConsumePlugin.ArgParserRuntime_BoolNegation | 4 ConsumePlugin.ArgParserRuntime_DuArgs | 5 ConsumePlugin.ArgParserRuntime_MapArgs | 6 ConsumePlugin.ArgParserRuntime_PrefixedParent | 7 ConsumePlugin.ArgParserRuntime_SameBaseNameArgs | 8 ConsumePlugin.OpensLeakVictim.ArgParserRuntime_LeakArgs | 9 Gitea | 10 PureGym | 11 SomeNamespace.CapturingMock | 12 WoofWare.Myriad.Plugins.ArgParserRuntime | 13 WoofWare.Myriad.Plugins.SwaggerV2 | 14 ConsumePlugin.AliasedPositionalsArgParse | 15 ConsumePlugin.ArgParserRuntime_BasicNoPositionals.ScanErrorModule | 16 ConsumePlugin.ArgParserRuntime_BasicNoPositionals.SchemaErrorModule | 17 ConsumePlugin.ArgParserRuntime_BasicNoPositionals.WellFormedSchemaModule | 18 ConsumePlugin.ArgParserRuntime_BoolNegation.ScanErrorModule | 19 ConsumePlugin.ArgParserRuntime_BoolNegation.SchemaErrorModule | 20 ConsumePlugin.ArgParserRuntime_BoolNegation.WellFormedSchemaModule | 21 ConsumePlugin.ArgParserRuntime_DuArgs.ScanErrorModule | 22 ConsumePlugin.ArgParserRuntime_DuArgs.SchemaErrorModule | 23 ConsumePlugin.ArgParserRuntime_DuArgs.WellFormedSchemaModule | 24 ConsumePlugin.ArgParserRuntime_MapArgs.ScanErrorModule | 25 ConsumePlugin.ArgParserRuntime_MapArgs.SchemaErrorModule | 26 ConsumePlugin.ArgParserRuntime_MapArgs.WellFormedSchemaModule | 27 ConsumePlugin.ArgParserRuntime_PrefixedParent.ScanErrorModule | 28 ConsumePlugin.ArgParserRuntime_PrefixedParent.SchemaErrorModule | 29 ConsumePlugin.ArgParserRuntime_PrefixedParent.WellFormedSchemaModule | 30 ConsumePlugin.ArgParserRuntime_SameBaseNameArgs.ScanErrorModule | 31 ConsumePlugin.ArgParserRuntime_SameBaseNameArgs.SchemaErrorModule | 32 ConsumePlugin.ArgParserRuntime_SameBaseNameArgs.WellFormedSchemaModule | 33 ConsumePlugin.AwkwardDefaultFunctionNameArgParse | 34 ConsumePlugin.AwkwardFieldNameArgParse | 35 ConsumePlugin.AwkwardLongFormsArgParse | 36 ConsumePlugin.BasicModule | 37 ConsumePlugin.BasicNoPositionalsModule | 38 ConsumePlugin.BasicWithIntPositionalsModule | 39 WoofWare.Myriad.Plugins | 40 WoofWare.Myriad.Plugins.SwaggerClientGeneratorModule |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 ConsumePlugin | ||||||||||||||||||||||||||||||||||||||||
| 2 ConsumePlugin.ArgParserRuntime_BasicNoPositionals | ||||||||||||||||||||||||||||||||||||||||
| 3 ConsumePlugin.ArgParserRuntime_BoolNegation | ||||||||||||||||||||||||||||||||||||||||
| 4 ConsumePlugin.ArgParserRuntime_DuArgs | ||||||||||||||||||||||||||||||||||||||||
| 5 ConsumePlugin.ArgParserRuntime_MapArgs | ||||||||||||||||||||||||||||||||||||||||
| 6 ConsumePlugin.ArgParserRuntime_PrefixedParent | ||||||||||||||||||||||||||||||||||||||||
| 7 ConsumePlugin.ArgParserRuntime_SameBaseNameArgs | ||||||||||||||||||||||||||||||||||||||||
| 8 ConsumePlugin.OpensLeakVictim.ArgParserRuntime_LeakArgs | ||||||||||||||||||||||||||||||||||||||||
| 9 Gitea | ||||||||||||||||||||||||||||||||||||||||
| 10 PureGym | ||||||||||||||||||||||||||||||||||||||||
| 11 SomeNamespace.CapturingMock | ||||||||||||||||||||||||||||||||||||||||
| 12 WoofWare.Myriad.Plugins.ArgParserRuntime | ||||||||||||||||||||||||||||||||||||||||
| 13 WoofWare.Myriad.Plugins.SwaggerV2 | ||||||||||||||||||||||||||||||||||||||||
| 14 ConsumePlugin.AliasedPositionalsArgParse | 1 | |||||||||||||||||||||||||||||||||||||||
| 15 ConsumePlugin.ArgParserRuntime_BasicNoPositionals.ScanErrorModule | 1 | |||||||||||||||||||||||||||||||||||||||
| 16 ConsumePlugin.ArgParserRuntime_BasicNoPositionals.SchemaErrorModule | 1 | |||||||||||||||||||||||||||||||||||||||
| 17 ConsumePlugin.ArgParserRuntime_BasicNoPositionals.WellFormedSchemaModule | 3 | |||||||||||||||||||||||||||||||||||||||
| 18 ConsumePlugin.ArgParserRuntime_BoolNegation.ScanErrorModule | 1 | |||||||||||||||||||||||||||||||||||||||
| 19 ConsumePlugin.ArgParserRuntime_BoolNegation.SchemaErrorModule | 1 | |||||||||||||||||||||||||||||||||||||||
| 20 ConsumePlugin.ArgParserRuntime_BoolNegation.WellFormedSchemaModule | 3 | |||||||||||||||||||||||||||||||||||||||
| 21 ConsumePlugin.ArgParserRuntime_DuArgs.ScanErrorModule | 1 | |||||||||||||||||||||||||||||||||||||||
| 22 ConsumePlugin.ArgParserRuntime_DuArgs.SchemaErrorModule | 1 | |||||||||||||||||||||||||||||||||||||||
| 23 ConsumePlugin.ArgParserRuntime_DuArgs.WellFormedSchemaModule | 3 | |||||||||||||||||||||||||||||||||||||||
| 24 ConsumePlugin.ArgParserRuntime_MapArgs.ScanErrorModule | 1 | |||||||||||||||||||||||||||||||||||||||
| 25 ConsumePlugin.ArgParserRuntime_MapArgs.SchemaErrorModule | 1 | |||||||||||||||||||||||||||||||||||||||
| 26 ConsumePlugin.ArgParserRuntime_MapArgs.WellFormedSchemaModule | 3 | |||||||||||||||||||||||||||||||||||||||
| 27 ConsumePlugin.ArgParserRuntime_PrefixedParent.ScanErrorModule | 1 | |||||||||||||||||||||||||||||||||||||||
| 28 ConsumePlugin.ArgParserRuntime_PrefixedParent.SchemaErrorModule | 1 | |||||||||||||||||||||||||||||||||||||||
| 29 ConsumePlugin.ArgParserRuntime_PrefixedParent.WellFormedSchemaModule | 3 | |||||||||||||||||||||||||||||||||||||||
| 30 ConsumePlugin.ArgParserRuntime_SameBaseNameArgs.ScanErrorModule | 1 | |||||||||||||||||||||||||||||||||||||||
| 31 ConsumePlugin.ArgParserRuntime_SameBaseNameArgs.SchemaErrorModule | 1 | |||||||||||||||||||||||||||||||||||||||
| 32 ConsumePlugin.ArgParserRuntime_SameBaseNameArgs.WellFormedSchemaModule | 3 | |||||||||||||||||||||||||||||||||||||||
| 33 ConsumePlugin.AwkwardDefaultFunctionNameArgParse | 1 | |||||||||||||||||||||||||||||||||||||||
| 34 ConsumePlugin.AwkwardFieldNameArgParse | 1 | |||||||||||||||||||||||||||||||||||||||
| 35 ConsumePlugin.AwkwardLongFormsArgParse | 1 | |||||||||||||||||||||||||||||||||||||||
| 36 ConsumePlugin.BasicModule | 1 | |||||||||||||||||||||||||||||||||||||||
| 37 ConsumePlugin.BasicNoPositionalsModule | 1 | |||||||||||||||||||||||||||||||||||||||
| 38 ConsumePlugin.BasicWithIntPositionalsModule | 1 | |||||||||||||||||||||||||||||||||||||||
| 39 WoofWare.Myriad.Plugins | 6 | |||||||||||||||||||||||||||||||||||||||
| 40 WoofWare.Myriad.Plugins.SwaggerClientGeneratorModule | 3 | 8 |
14→1 ConsumePlugin.AliasedPositionalsArgParse uses ConsumePlugin✕
- Connections
- 1 pair of types, where a type in ConsumePlugin.AliasedPositionalsArgParse uses a type in ConsumePlugin.
- The types involved
ConsumePlugin.AliasedPositionalsArgParse.AliasedPositionalsArgParse→ConsumePlugin.AliasedPositionals
- Direction
- ConsumePlugin.AliasedPositionalsArgParse uses ConsumePlugin, so a change to ConsumePlugin can break ConsumePlugin.AliasedPositionalsArgParse, while a change to ConsumePlugin.AliasedPositionalsArgParse can't break ConsumePlugin.
- Position
- Below the diagonal: ConsumePlugin.AliasedPositionalsArgParse uses a module listed above it, which is the healthy direction.
15→2 ConsumePlugin.ArgParserRuntime_BasicNoPositionals.ScanErrorModule uses ConsumePlugin.ArgParserRuntime_BasicNoPositionals✕
- Connections
- 1 pair of types, where a type in ConsumePlugin.ArgParserRuntime_BasicNoPositionals.ScanErrorModule uses a type in ConsumePlugin.ArgParserRuntime_BasicNoPositionals.
- The types involved
ConsumePlugin.ArgParserRuntime_BasicNoPositionals.ScanErrorModule.ScanErrorModule→ConsumePlugin.ArgParserRuntime_BasicNoPositionals.ScanError
- Direction
- ConsumePlugin.ArgParserRuntime_BasicNoPositionals.ScanErrorModule uses ConsumePlugin.ArgParserRuntime_BasicNoPositionals, so a change to ConsumePlugin.ArgParserRuntime_BasicNoPositionals can break ConsumePlugin.ArgParserRuntime_BasicNoPositionals.ScanErrorModule, while a change to ConsumePlugin.ArgParserRuntime_BasicNoPositionals.ScanErrorModule can't break ConsumePlugin.ArgParserRuntime_BasicNoPositionals.
- Position
- Below the diagonal: ConsumePlugin.ArgParserRuntime_BasicNoPositionals.ScanErrorModule uses a module listed above it, which is the healthy direction.
16→2 ConsumePlugin.ArgParserRuntime_BasicNoPositionals.SchemaErrorModule uses ConsumePlugin.ArgParserRuntime_BasicNoPositionals✕
- Connections
- 1 pair of types, where a type in ConsumePlugin.ArgParserRuntime_BasicNoPositionals.SchemaErrorModule uses a type in ConsumePlugin.ArgParserRuntime_BasicNoPositionals.
- The types involved
ConsumePlugin.ArgParserRuntime_BasicNoPositionals.SchemaErrorModule.SchemaErrorModule→ConsumePlugin.ArgParserRuntime_BasicNoPositionals.SchemaError
- Direction
- ConsumePlugin.ArgParserRuntime_BasicNoPositionals.SchemaErrorModule uses ConsumePlugin.ArgParserRuntime_BasicNoPositionals, so a change to ConsumePlugin.ArgParserRuntime_BasicNoPositionals can break ConsumePlugin.ArgParserRuntime_BasicNoPositionals.SchemaErrorModule, while a change to ConsumePlugin.ArgParserRuntime_BasicNoPositionals.SchemaErrorModule can't break ConsumePlugin.ArgParserRuntime_BasicNoPositionals.
- Position
- Below the diagonal: ConsumePlugin.ArgParserRuntime_BasicNoPositionals.SchemaErrorModule uses a module listed above it, which is the healthy direction.
17→2 ConsumePlugin.ArgParserRuntime_BasicNoPositionals.WellFormedSchemaModule uses ConsumePlugin.ArgParserRuntime_BasicNoPositionals✕
- Connections
- 3 pairs of types, where a type in ConsumePlugin.ArgParserRuntime_BasicNoPositionals.WellFormedSchemaModule uses a type in ConsumePlugin.ArgParserRuntime_BasicNoPositionals.
- The types involved
ConsumePlugin.ArgParserRuntime_BasicNoPositionals.WellFormedSchemaModule.WellFormedSchemaModule→ConsumePlugin.ArgParserRuntime_BasicNoPositionals.ErasedSchemaConsumePlugin.ArgParserRuntime_BasicNoPositionals.WellFormedSchemaModule.WellFormedSchemaModule→ConsumePlugin.ArgParserRuntime_BasicNoPositionals.SchemaErrorConsumePlugin.ArgParserRuntime_BasicNoPositionals.WellFormedSchemaModule.WellFormedSchemaModule→ConsumePlugin.ArgParserRuntime_BasicNoPositionals.WellFormedSchema
- Direction
- ConsumePlugin.ArgParserRuntime_BasicNoPositionals.WellFormedSchemaModule uses ConsumePlugin.ArgParserRuntime_BasicNoPositionals, so a change to ConsumePlugin.ArgParserRuntime_BasicNoPositionals can break ConsumePlugin.ArgParserRuntime_BasicNoPositionals.WellFormedSchemaModule, while a change to ConsumePlugin.ArgParserRuntime_BasicNoPositionals.WellFormedSchemaModule can't break ConsumePlugin.ArgParserRuntime_BasicNoPositionals.
- Position
- Below the diagonal: ConsumePlugin.ArgParserRuntime_BasicNoPositionals.WellFormedSchemaModule uses a module listed above it, which is the healthy direction.
18→3 ConsumePlugin.ArgParserRuntime_BoolNegation.ScanErrorModule uses ConsumePlugin.ArgParserRuntime_BoolNegation✕
- Connections
- 1 pair of types, where a type in ConsumePlugin.ArgParserRuntime_BoolNegation.ScanErrorModule uses a type in ConsumePlugin.ArgParserRuntime_BoolNegation.
- The types involved
ConsumePlugin.ArgParserRuntime_BoolNegation.ScanErrorModule.ScanErrorModule→ConsumePlugin.ArgParserRuntime_BoolNegation.ScanError
- Direction
- ConsumePlugin.ArgParserRuntime_BoolNegation.ScanErrorModule uses ConsumePlugin.ArgParserRuntime_BoolNegation, so a change to ConsumePlugin.ArgParserRuntime_BoolNegation can break ConsumePlugin.ArgParserRuntime_BoolNegation.ScanErrorModule, while a change to ConsumePlugin.ArgParserRuntime_BoolNegation.ScanErrorModule can't break ConsumePlugin.ArgParserRuntime_BoolNegation.
- Position
- Below the diagonal: ConsumePlugin.ArgParserRuntime_BoolNegation.ScanErrorModule uses a module listed above it, which is the healthy direction.
19→3 ConsumePlugin.ArgParserRuntime_BoolNegation.SchemaErrorModule uses ConsumePlugin.ArgParserRuntime_BoolNegation✕
- Connections
- 1 pair of types, where a type in ConsumePlugin.ArgParserRuntime_BoolNegation.SchemaErrorModule uses a type in ConsumePlugin.ArgParserRuntime_BoolNegation.
- The types involved
ConsumePlugin.ArgParserRuntime_BoolNegation.SchemaErrorModule.SchemaErrorModule→ConsumePlugin.ArgParserRuntime_BoolNegation.SchemaError
- Direction
- ConsumePlugin.ArgParserRuntime_BoolNegation.SchemaErrorModule uses ConsumePlugin.ArgParserRuntime_BoolNegation, so a change to ConsumePlugin.ArgParserRuntime_BoolNegation can break ConsumePlugin.ArgParserRuntime_BoolNegation.SchemaErrorModule, while a change to ConsumePlugin.ArgParserRuntime_BoolNegation.SchemaErrorModule can't break ConsumePlugin.ArgParserRuntime_BoolNegation.
- Position
- Below the diagonal: ConsumePlugin.ArgParserRuntime_BoolNegation.SchemaErrorModule uses a module listed above it, which is the healthy direction.
20→3 ConsumePlugin.ArgParserRuntime_BoolNegation.WellFormedSchemaModule uses ConsumePlugin.ArgParserRuntime_BoolNegation✕
- Connections
- 3 pairs of types, where a type in ConsumePlugin.ArgParserRuntime_BoolNegation.WellFormedSchemaModule uses a type in ConsumePlugin.ArgParserRuntime_BoolNegation.
- The types involved
ConsumePlugin.ArgParserRuntime_BoolNegation.WellFormedSchemaModule.WellFormedSchemaModule→ConsumePlugin.ArgParserRuntime_BoolNegation.ErasedSchemaConsumePlugin.ArgParserRuntime_BoolNegation.WellFormedSchemaModule.WellFormedSchemaModule→ConsumePlugin.ArgParserRuntime_BoolNegation.SchemaErrorConsumePlugin.ArgParserRuntime_BoolNegation.WellFormedSchemaModule.WellFormedSchemaModule→ConsumePlugin.ArgParserRuntime_BoolNegation.WellFormedSchema
- Direction
- ConsumePlugin.ArgParserRuntime_BoolNegation.WellFormedSchemaModule uses ConsumePlugin.ArgParserRuntime_BoolNegation, so a change to ConsumePlugin.ArgParserRuntime_BoolNegation can break ConsumePlugin.ArgParserRuntime_BoolNegation.WellFormedSchemaModule, while a change to ConsumePlugin.ArgParserRuntime_BoolNegation.WellFormedSchemaModule can't break ConsumePlugin.ArgParserRuntime_BoolNegation.
- Position
- Below the diagonal: ConsumePlugin.ArgParserRuntime_BoolNegation.WellFormedSchemaModule uses a module listed above it, which is the healthy direction.
21→4 ConsumePlugin.ArgParserRuntime_DuArgs.ScanErrorModule uses ConsumePlugin.ArgParserRuntime_DuArgs✕
- Connections
- 1 pair of types, where a type in ConsumePlugin.ArgParserRuntime_DuArgs.ScanErrorModule uses a type in ConsumePlugin.ArgParserRuntime_DuArgs.
- The types involved
ConsumePlugin.ArgParserRuntime_DuArgs.ScanErrorModule.ScanErrorModule→ConsumePlugin.ArgParserRuntime_DuArgs.ScanError
- Direction
- ConsumePlugin.ArgParserRuntime_DuArgs.ScanErrorModule uses ConsumePlugin.ArgParserRuntime_DuArgs, so a change to ConsumePlugin.ArgParserRuntime_DuArgs can break ConsumePlugin.ArgParserRuntime_DuArgs.ScanErrorModule, while a change to ConsumePlugin.ArgParserRuntime_DuArgs.ScanErrorModule can't break ConsumePlugin.ArgParserRuntime_DuArgs.
- Position
- Below the diagonal: ConsumePlugin.ArgParserRuntime_DuArgs.ScanErrorModule uses a module listed above it, which is the healthy direction.
22→4 ConsumePlugin.ArgParserRuntime_DuArgs.SchemaErrorModule uses ConsumePlugin.ArgParserRuntime_DuArgs✕
- Connections
- 1 pair of types, where a type in ConsumePlugin.ArgParserRuntime_DuArgs.SchemaErrorModule uses a type in ConsumePlugin.ArgParserRuntime_DuArgs.
- The types involved
ConsumePlugin.ArgParserRuntime_DuArgs.SchemaErrorModule.SchemaErrorModule→ConsumePlugin.ArgParserRuntime_DuArgs.SchemaError
- Direction
- ConsumePlugin.ArgParserRuntime_DuArgs.SchemaErrorModule uses ConsumePlugin.ArgParserRuntime_DuArgs, so a change to ConsumePlugin.ArgParserRuntime_DuArgs can break ConsumePlugin.ArgParserRuntime_DuArgs.SchemaErrorModule, while a change to ConsumePlugin.ArgParserRuntime_DuArgs.SchemaErrorModule can't break ConsumePlugin.ArgParserRuntime_DuArgs.
- Position
- Below the diagonal: ConsumePlugin.ArgParserRuntime_DuArgs.SchemaErrorModule uses a module listed above it, which is the healthy direction.
23→4 ConsumePlugin.ArgParserRuntime_DuArgs.WellFormedSchemaModule uses ConsumePlugin.ArgParserRuntime_DuArgs✕
- Connections
- 3 pairs of types, where a type in ConsumePlugin.ArgParserRuntime_DuArgs.WellFormedSchemaModule uses a type in ConsumePlugin.ArgParserRuntime_DuArgs.
- The types involved
ConsumePlugin.ArgParserRuntime_DuArgs.WellFormedSchemaModule.WellFormedSchemaModule→ConsumePlugin.ArgParserRuntime_DuArgs.ErasedSchemaConsumePlugin.ArgParserRuntime_DuArgs.WellFormedSchemaModule.WellFormedSchemaModule→ConsumePlugin.ArgParserRuntime_DuArgs.SchemaErrorConsumePlugin.ArgParserRuntime_DuArgs.WellFormedSchemaModule.WellFormedSchemaModule→ConsumePlugin.ArgParserRuntime_DuArgs.WellFormedSchema
- Direction
- ConsumePlugin.ArgParserRuntime_DuArgs.WellFormedSchemaModule uses ConsumePlugin.ArgParserRuntime_DuArgs, so a change to ConsumePlugin.ArgParserRuntime_DuArgs can break ConsumePlugin.ArgParserRuntime_DuArgs.WellFormedSchemaModule, while a change to ConsumePlugin.ArgParserRuntime_DuArgs.WellFormedSchemaModule can't break ConsumePlugin.ArgParserRuntime_DuArgs.
- Position
- Below the diagonal: ConsumePlugin.ArgParserRuntime_DuArgs.WellFormedSchemaModule uses a module listed above it, which is the healthy direction.
24→5 ConsumePlugin.ArgParserRuntime_MapArgs.ScanErrorModule uses ConsumePlugin.ArgParserRuntime_MapArgs✕
- Connections
- 1 pair of types, where a type in ConsumePlugin.ArgParserRuntime_MapArgs.ScanErrorModule uses a type in ConsumePlugin.ArgParserRuntime_MapArgs.
- The types involved
ConsumePlugin.ArgParserRuntime_MapArgs.ScanErrorModule.ScanErrorModule→ConsumePlugin.ArgParserRuntime_MapArgs.ScanError
- Direction
- ConsumePlugin.ArgParserRuntime_MapArgs.ScanErrorModule uses ConsumePlugin.ArgParserRuntime_MapArgs, so a change to ConsumePlugin.ArgParserRuntime_MapArgs can break ConsumePlugin.ArgParserRuntime_MapArgs.ScanErrorModule, while a change to ConsumePlugin.ArgParserRuntime_MapArgs.ScanErrorModule can't break ConsumePlugin.ArgParserRuntime_MapArgs.
- Position
- Below the diagonal: ConsumePlugin.ArgParserRuntime_MapArgs.ScanErrorModule uses a module listed above it, which is the healthy direction.
25→5 ConsumePlugin.ArgParserRuntime_MapArgs.SchemaErrorModule uses ConsumePlugin.ArgParserRuntime_MapArgs✕
- Connections
- 1 pair of types, where a type in ConsumePlugin.ArgParserRuntime_MapArgs.SchemaErrorModule uses a type in ConsumePlugin.ArgParserRuntime_MapArgs.
- The types involved
ConsumePlugin.ArgParserRuntime_MapArgs.SchemaErrorModule.SchemaErrorModule→ConsumePlugin.ArgParserRuntime_MapArgs.SchemaError
- Direction
- ConsumePlugin.ArgParserRuntime_MapArgs.SchemaErrorModule uses ConsumePlugin.ArgParserRuntime_MapArgs, so a change to ConsumePlugin.ArgParserRuntime_MapArgs can break ConsumePlugin.ArgParserRuntime_MapArgs.SchemaErrorModule, while a change to ConsumePlugin.ArgParserRuntime_MapArgs.SchemaErrorModule can't break ConsumePlugin.ArgParserRuntime_MapArgs.
- Position
- Below the diagonal: ConsumePlugin.ArgParserRuntime_MapArgs.SchemaErrorModule uses a module listed above it, which is the healthy direction.
26→5 ConsumePlugin.ArgParserRuntime_MapArgs.WellFormedSchemaModule uses ConsumePlugin.ArgParserRuntime_MapArgs✕
- Connections
- 3 pairs of types, where a type in ConsumePlugin.ArgParserRuntime_MapArgs.WellFormedSchemaModule uses a type in ConsumePlugin.ArgParserRuntime_MapArgs.
- The types involved
ConsumePlugin.ArgParserRuntime_MapArgs.WellFormedSchemaModule.WellFormedSchemaModule→ConsumePlugin.ArgParserRuntime_MapArgs.ErasedSchemaConsumePlugin.ArgParserRuntime_MapArgs.WellFormedSchemaModule.WellFormedSchemaModule→ConsumePlugin.ArgParserRuntime_MapArgs.SchemaErrorConsumePlugin.ArgParserRuntime_MapArgs.WellFormedSchemaModule.WellFormedSchemaModule→ConsumePlugin.ArgParserRuntime_MapArgs.WellFormedSchema
- Direction
- ConsumePlugin.ArgParserRuntime_MapArgs.WellFormedSchemaModule uses ConsumePlugin.ArgParserRuntime_MapArgs, so a change to ConsumePlugin.ArgParserRuntime_MapArgs can break ConsumePlugin.ArgParserRuntime_MapArgs.WellFormedSchemaModule, while a change to ConsumePlugin.ArgParserRuntime_MapArgs.WellFormedSchemaModule can't break ConsumePlugin.ArgParserRuntime_MapArgs.
- Position
- Below the diagonal: ConsumePlugin.ArgParserRuntime_MapArgs.WellFormedSchemaModule uses a module listed above it, which is the healthy direction.
27→6 ConsumePlugin.ArgParserRuntime_PrefixedParent.ScanErrorModule uses ConsumePlugin.ArgParserRuntime_PrefixedParent✕
- Connections
- 1 pair of types, where a type in ConsumePlugin.ArgParserRuntime_PrefixedParent.ScanErrorModule uses a type in ConsumePlugin.ArgParserRuntime_PrefixedParent.
- The types involved
ConsumePlugin.ArgParserRuntime_PrefixedParent.ScanErrorModule.ScanErrorModule→ConsumePlugin.ArgParserRuntime_PrefixedParent.ScanError
- Direction
- ConsumePlugin.ArgParserRuntime_PrefixedParent.ScanErrorModule uses ConsumePlugin.ArgParserRuntime_PrefixedParent, so a change to ConsumePlugin.ArgParserRuntime_PrefixedParent can break ConsumePlugin.ArgParserRuntime_PrefixedParent.ScanErrorModule, while a change to ConsumePlugin.ArgParserRuntime_PrefixedParent.ScanErrorModule can't break ConsumePlugin.ArgParserRuntime_PrefixedParent.
- Position
- Below the diagonal: ConsumePlugin.ArgParserRuntime_PrefixedParent.ScanErrorModule uses a module listed above it, which is the healthy direction.
28→6 ConsumePlugin.ArgParserRuntime_PrefixedParent.SchemaErrorModule uses ConsumePlugin.ArgParserRuntime_PrefixedParent✕
- Connections
- 1 pair of types, where a type in ConsumePlugin.ArgParserRuntime_PrefixedParent.SchemaErrorModule uses a type in ConsumePlugin.ArgParserRuntime_PrefixedParent.
- The types involved
ConsumePlugin.ArgParserRuntime_PrefixedParent.SchemaErrorModule.SchemaErrorModule→ConsumePlugin.ArgParserRuntime_PrefixedParent.SchemaError
- Direction
- ConsumePlugin.ArgParserRuntime_PrefixedParent.SchemaErrorModule uses ConsumePlugin.ArgParserRuntime_PrefixedParent, so a change to ConsumePlugin.ArgParserRuntime_PrefixedParent can break ConsumePlugin.ArgParserRuntime_PrefixedParent.SchemaErrorModule, while a change to ConsumePlugin.ArgParserRuntime_PrefixedParent.SchemaErrorModule can't break ConsumePlugin.ArgParserRuntime_PrefixedParent.
- Position
- Below the diagonal: ConsumePlugin.ArgParserRuntime_PrefixedParent.SchemaErrorModule uses a module listed above it, which is the healthy direction.
29→6 ConsumePlugin.ArgParserRuntime_PrefixedParent.WellFormedSchemaModule uses ConsumePlugin.ArgParserRuntime_PrefixedParent✕
- Connections
- 3 pairs of types, where a type in ConsumePlugin.ArgParserRuntime_PrefixedParent.WellFormedSchemaModule uses a type in ConsumePlugin.ArgParserRuntime_PrefixedParent.
- The types involved
ConsumePlugin.ArgParserRuntime_PrefixedParent.WellFormedSchemaModule.WellFormedSchemaModule→ConsumePlugin.ArgParserRuntime_PrefixedParent.ErasedSchemaConsumePlugin.ArgParserRuntime_PrefixedParent.WellFormedSchemaModule.WellFormedSchemaModule→ConsumePlugin.ArgParserRuntime_PrefixedParent.SchemaErrorConsumePlugin.ArgParserRuntime_PrefixedParent.WellFormedSchemaModule.WellFormedSchemaModule→ConsumePlugin.ArgParserRuntime_PrefixedParent.WellFormedSchema
- Direction
- ConsumePlugin.ArgParserRuntime_PrefixedParent.WellFormedSchemaModule uses ConsumePlugin.ArgParserRuntime_PrefixedParent, so a change to ConsumePlugin.ArgParserRuntime_PrefixedParent can break ConsumePlugin.ArgParserRuntime_PrefixedParent.WellFormedSchemaModule, while a change to ConsumePlugin.ArgParserRuntime_PrefixedParent.WellFormedSchemaModule can't break ConsumePlugin.ArgParserRuntime_PrefixedParent.
- Position
- Below the diagonal: ConsumePlugin.ArgParserRuntime_PrefixedParent.WellFormedSchemaModule uses a module listed above it, which is the healthy direction.
30→7 ConsumePlugin.ArgParserRuntime_SameBaseNameArgs.ScanErrorModule uses ConsumePlugin.ArgParserRuntime_SameBaseNameArgs✕
- Connections
- 1 pair of types, where a type in ConsumePlugin.ArgParserRuntime_SameBaseNameArgs.ScanErrorModule uses a type in ConsumePlugin.ArgParserRuntime_SameBaseNameArgs.
- The types involved
ConsumePlugin.ArgParserRuntime_SameBaseNameArgs.ScanErrorModule.ScanErrorModule→ConsumePlugin.ArgParserRuntime_SameBaseNameArgs.ScanError
- Direction
- ConsumePlugin.ArgParserRuntime_SameBaseNameArgs.ScanErrorModule uses ConsumePlugin.ArgParserRuntime_SameBaseNameArgs, so a change to ConsumePlugin.ArgParserRuntime_SameBaseNameArgs can break ConsumePlugin.ArgParserRuntime_SameBaseNameArgs.ScanErrorModule, while a change to ConsumePlugin.ArgParserRuntime_SameBaseNameArgs.ScanErrorModule can't break ConsumePlugin.ArgParserRuntime_SameBaseNameArgs.
- Position
- Below the diagonal: ConsumePlugin.ArgParserRuntime_SameBaseNameArgs.ScanErrorModule uses a module listed above it, which is the healthy direction.
31→7 ConsumePlugin.ArgParserRuntime_SameBaseNameArgs.SchemaErrorModule uses ConsumePlugin.ArgParserRuntime_SameBaseNameArgs✕
- Connections
- 1 pair of types, where a type in ConsumePlugin.ArgParserRuntime_SameBaseNameArgs.SchemaErrorModule uses a type in ConsumePlugin.ArgParserRuntime_SameBaseNameArgs.
- The types involved
ConsumePlugin.ArgParserRuntime_SameBaseNameArgs.SchemaErrorModule.SchemaErrorModule→ConsumePlugin.ArgParserRuntime_SameBaseNameArgs.SchemaError
- Direction
- ConsumePlugin.ArgParserRuntime_SameBaseNameArgs.SchemaErrorModule uses ConsumePlugin.ArgParserRuntime_SameBaseNameArgs, so a change to ConsumePlugin.ArgParserRuntime_SameBaseNameArgs can break ConsumePlugin.ArgParserRuntime_SameBaseNameArgs.SchemaErrorModule, while a change to ConsumePlugin.ArgParserRuntime_SameBaseNameArgs.SchemaErrorModule can't break ConsumePlugin.ArgParserRuntime_SameBaseNameArgs.
- Position
- Below the diagonal: ConsumePlugin.ArgParserRuntime_SameBaseNameArgs.SchemaErrorModule uses a module listed above it, which is the healthy direction.
32→7 ConsumePlugin.ArgParserRuntime_SameBaseNameArgs.WellFormedSchemaModule uses ConsumePlugin.ArgParserRuntime_SameBaseNameArgs✕
- Connections
- 3 pairs of types, where a type in ConsumePlugin.ArgParserRuntime_SameBaseNameArgs.WellFormedSchemaModule uses a type in ConsumePlugin.ArgParserRuntime_SameBaseNameArgs.
- The types involved
ConsumePlugin.ArgParserRuntime_SameBaseNameArgs.WellFormedSchemaModule.WellFormedSchemaModule→ConsumePlugin.ArgParserRuntime_SameBaseNameArgs.ErasedSchemaConsumePlugin.ArgParserRuntime_SameBaseNameArgs.WellFormedSchemaModule.WellFormedSchemaModule→ConsumePlugin.ArgParserRuntime_SameBaseNameArgs.SchemaErrorConsumePlugin.ArgParserRuntime_SameBaseNameArgs.WellFormedSchemaModule.WellFormedSchemaModule→ConsumePlugin.ArgParserRuntime_SameBaseNameArgs.WellFormedSchema
- Direction
- ConsumePlugin.ArgParserRuntime_SameBaseNameArgs.WellFormedSchemaModule uses ConsumePlugin.ArgParserRuntime_SameBaseNameArgs, so a change to ConsumePlugin.ArgParserRuntime_SameBaseNameArgs can break ConsumePlugin.ArgParserRuntime_SameBaseNameArgs.WellFormedSchemaModule, while a change to ConsumePlugin.ArgParserRuntime_SameBaseNameArgs.WellFormedSchemaModule can't break ConsumePlugin.ArgParserRuntime_SameBaseNameArgs.
- Position
- Below the diagonal: ConsumePlugin.ArgParserRuntime_SameBaseNameArgs.WellFormedSchemaModule uses a module listed above it, which is the healthy direction.
33→1 ConsumePlugin.AwkwardDefaultFunctionNameArgParse uses ConsumePlugin✕
- Connections
- 1 pair of types, where a type in ConsumePlugin.AwkwardDefaultFunctionNameArgParse uses a type in ConsumePlugin.
- The types involved
ConsumePlugin.AwkwardDefaultFunctionNameArgParse.AwkwardDefaultFunctionNameArgParse→ConsumePlugin.AwkwardDefaultFunctionName
- Direction
- ConsumePlugin.AwkwardDefaultFunctionNameArgParse uses ConsumePlugin, so a change to ConsumePlugin can break ConsumePlugin.AwkwardDefaultFunctionNameArgParse, while a change to ConsumePlugin.AwkwardDefaultFunctionNameArgParse can't break ConsumePlugin.
- Position
- Below the diagonal: ConsumePlugin.AwkwardDefaultFunctionNameArgParse uses a module listed above it, which is the healthy direction.
34→1 ConsumePlugin.AwkwardFieldNameArgParse uses ConsumePlugin✕
- Connections
- 1 pair of types, where a type in ConsumePlugin.AwkwardFieldNameArgParse uses a type in ConsumePlugin.
- The types involved
ConsumePlugin.AwkwardFieldNameArgParse.AwkwardFieldNameArgParse→ConsumePlugin.AwkwardFieldName
- Direction
- ConsumePlugin.AwkwardFieldNameArgParse uses ConsumePlugin, so a change to ConsumePlugin can break ConsumePlugin.AwkwardFieldNameArgParse, while a change to ConsumePlugin.AwkwardFieldNameArgParse can't break ConsumePlugin.
- Position
- Below the diagonal: ConsumePlugin.AwkwardFieldNameArgParse uses a module listed above it, which is the healthy direction.
35→1 ConsumePlugin.AwkwardLongFormsArgParse uses ConsumePlugin✕
- Connections
- 1 pair of types, where a type in ConsumePlugin.AwkwardLongFormsArgParse uses a type in ConsumePlugin.
- The types involved
ConsumePlugin.AwkwardLongFormsArgParse.AwkwardLongFormsArgParse→ConsumePlugin.AwkwardLongForms
- Direction
- ConsumePlugin.AwkwardLongFormsArgParse uses ConsumePlugin, so a change to ConsumePlugin can break ConsumePlugin.AwkwardLongFormsArgParse, while a change to ConsumePlugin.AwkwardLongFormsArgParse can't break ConsumePlugin.
- Position
- Below the diagonal: ConsumePlugin.AwkwardLongFormsArgParse uses a module listed above it, which is the healthy direction.
36→1 ConsumePlugin.BasicModule uses ConsumePlugin✕
- Connections
- 1 pair of types, where a type in ConsumePlugin.BasicModule uses a type in ConsumePlugin.
- The types involved
ConsumePlugin.BasicModule.BasicModule→ConsumePlugin.Basic
- Direction
- ConsumePlugin.BasicModule uses ConsumePlugin, so a change to ConsumePlugin can break ConsumePlugin.BasicModule, while a change to ConsumePlugin.BasicModule can't break ConsumePlugin.
- Position
- Below the diagonal: ConsumePlugin.BasicModule uses a module listed above it, which is the healthy direction.
37→1 ConsumePlugin.BasicNoPositionalsModule uses ConsumePlugin✕
- Connections
- 1 pair of types, where a type in ConsumePlugin.BasicNoPositionalsModule uses a type in ConsumePlugin.
- The types involved
ConsumePlugin.BasicNoPositionalsModule.BasicNoPositionalsModule→ConsumePlugin.BasicNoPositionals
- Direction
- ConsumePlugin.BasicNoPositionalsModule uses ConsumePlugin, so a change to ConsumePlugin can break ConsumePlugin.BasicNoPositionalsModule, while a change to ConsumePlugin.BasicNoPositionalsModule can't break ConsumePlugin.
- Position
- Below the diagonal: ConsumePlugin.BasicNoPositionalsModule uses a module listed above it, which is the healthy direction.
38→1 ConsumePlugin.BasicWithIntPositionalsModule uses ConsumePlugin✕
- Connections
- 1 pair of types, where a type in ConsumePlugin.BasicWithIntPositionalsModule uses a type in ConsumePlugin.
- The types involved
ConsumePlugin.BasicWithIntPositionalsModule.BasicWithIntPositionalsModule→ConsumePlugin.BasicWithIntPositionals
- Direction
- ConsumePlugin.BasicWithIntPositionalsModule uses ConsumePlugin, so a change to ConsumePlugin can break ConsumePlugin.BasicWithIntPositionalsModule, while a change to ConsumePlugin.BasicWithIntPositionalsModule can't break ConsumePlugin.
- Position
- Below the diagonal: ConsumePlugin.BasicWithIntPositionalsModule uses a module listed above it, which is the healthy direction.
39→13 WoofWare.Myriad.Plugins uses WoofWare.Myriad.Plugins.SwaggerV2✕
- Connections
- 6 pairs of types, where a type in WoofWare.Myriad.Plugins uses a type in WoofWare.Myriad.Plugins.SwaggerV2.
- The types involved
WoofWare.Myriad.Plugins.Endpoint→WoofWare.Myriad.Plugins.SwaggerV2.DefinitionWoofWare.Myriad.Plugins.Endpoint→WoofWare.Myriad.Plugins.SwaggerV2.MimeTypeWoofWare.Myriad.Plugins.Endpoint→WoofWare.Myriad.Plugins.SwaggerV2.OperationIdWoofWare.Myriad.Plugins.Endpoint→WoofWare.Myriad.Plugins.SwaggerV2.SwaggerParameterWoofWare.Myriad.Plugins.SuccessResponse→WoofWare.Myriad.Plugins.SwaggerV2.DefinitionWoofWare.Myriad.Plugins.Types→WoofWare.Myriad.Plugins.SwaggerV2.Definition
- Direction
- WoofWare.Myriad.Plugins uses WoofWare.Myriad.Plugins.SwaggerV2, so a change to WoofWare.Myriad.Plugins.SwaggerV2 can break WoofWare.Myriad.Plugins, while a change to WoofWare.Myriad.Plugins can't break WoofWare.Myriad.Plugins.SwaggerV2.
- Position
- Below the diagonal: WoofWare.Myriad.Plugins uses a module listed above it, which is the healthy direction.
40→13 WoofWare.Myriad.Plugins.SwaggerClientGeneratorModule uses WoofWare.Myriad.Plugins.SwaggerV2✕
- Connections
- 3 pairs of types, where a type in WoofWare.Myriad.Plugins.SwaggerClientGeneratorModule uses a type in WoofWare.Myriad.Plugins.SwaggerV2.
- The types involved
WoofWare.Myriad.Plugins.SwaggerClientGeneratorModule.SwaggerClientGeneratorModule→WoofWare.Myriad.Plugins.SwaggerV2.DefinitionWoofWare.Myriad.Plugins.SwaggerClientGeneratorModule.SwaggerClientGeneratorModule→WoofWare.Myriad.Plugins.SwaggerV2.MimeTypeWoofWare.Myriad.Plugins.SwaggerClientGeneratorModule.SwaggerClientGeneratorModule→WoofWare.Myriad.Plugins.SwaggerV2.ResponseKey
- Direction
- WoofWare.Myriad.Plugins.SwaggerClientGeneratorModule uses WoofWare.Myriad.Plugins.SwaggerV2, so a change to WoofWare.Myriad.Plugins.SwaggerV2 can break WoofWare.Myriad.Plugins.SwaggerClientGeneratorModule, while a change to WoofWare.Myriad.Plugins.SwaggerClientGeneratorModule can't break WoofWare.Myriad.Plugins.SwaggerV2.
- Position
- Below the diagonal: WoofWare.Myriad.Plugins.SwaggerClientGeneratorModule uses a module listed above it, which is the healthy direction.
40→39 WoofWare.Myriad.Plugins.SwaggerClientGeneratorModule uses WoofWare.Myriad.Plugins✕
- Connections
- 8 pairs of types, where a type in WoofWare.Myriad.Plugins.SwaggerClientGeneratorModule uses a type in WoofWare.Myriad.Plugins.
- The types involved
WoofWare.Myriad.Plugins.SwaggerClientGeneratorModule.SwaggerClientGeneratorModule→WoofWare.Myriad.Plugins.EndpointWoofWare.Myriad.Plugins.SwaggerClientGeneratorModule.SwaggerClientGeneratorModule→WoofWare.Myriad.Plugins.HttpMethodWoofWare.Myriad.Plugins.SwaggerClientGeneratorModule.SwaggerClientGeneratorModule→WoofWare.Myriad.Plugins.MimeUsageWoofWare.Myriad.Plugins.SwaggerClientGeneratorModule.SwaggerClientGeneratorModule→WoofWare.Myriad.Plugins.PayloadShapeWoofWare.Myriad.Plugins.SwaggerClientGeneratorModule.SwaggerClientGeneratorModule→WoofWare.Myriad.Plugins.SuccessResponseWoofWare.Myriad.Plugins.SwaggerClientGeneratorModule.SwaggerClientGeneratorModule→WoofWare.Myriad.Plugins.SwaggerClientConfigWoofWare.Myriad.Plugins.SwaggerClientGeneratorModule.SwaggerClientGeneratorModule→WoofWare.Myriad.Plugins.TypeEntryWoofWare.Myriad.Plugins.SwaggerClientGeneratorModule.SwaggerClientGeneratorModule→WoofWare.Myriad.Plugins.Types
- Direction
- WoofWare.Myriad.Plugins.SwaggerClientGeneratorModule uses WoofWare.Myriad.Plugins, so a change to WoofWare.Myriad.Plugins can break WoofWare.Myriad.Plugins.SwaggerClientGeneratorModule, while a change to WoofWare.Myriad.Plugins.SwaggerClientGeneratorModule can't break WoofWare.Myriad.Plugins.
- Position
- Below the diagonal: WoofWare.Myriad.Plugins.SwaggerClientGeneratorModule uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A03:2025 — Software Supply Chain Failures | 5 | High / Critical |
| A05:2025 — Injection | 1 | High / Critical |
Roadmap
Top priorities: Bring the 10 bodies over 30 down to 30 or less in Cognitive Complexity — start with ArgParserGeneratorModule.toParseSpec (cognitive 135), SwaggerClientGeneratorModule.defnToType (cognitive 114), ArgParserRuntime.runParse (cognitive 81); Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them; Resolve the 1 `GeneralAPISettings` spells `API` where 18 names in the project spell it… finding(s) in Naming Consistency — start with GeneratedSwaggerGitea.fs.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 1 `GeneralAPISettings` spells `API` where 18 names in the project spell it… finding(s) in Naming Consistency — start with GeneratedSwaggerGitea.fs. | +4.3 pts | Low | Naming Consistency |
| Resolve the 1 `GetGeneralAPISettings` spells `API` where 18 names in the project spell… finding(s) in Naming Consistency — start with GeneratedSwaggerGitea.fs. | +4.3 pts | Low | Naming Consistency |
| Resolve the 1 `RepoGetByID` spells `ID` where 47 names in the project spell it `Id` finding(s) in Naming Consistency — start with GeneratedSwaggerGitea.fs. | +4.3 pts | Low | Naming Consistency |
| 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 |
| Bring the 10 bodies over 30 down to 30 or less in Cognitive Complexity — start with ArgParserGeneratorModule.toParseSpec (cognitive 135), SwaggerClientGeneratorModule.defnToType (cognitive 114), ArgParserRuntime.runParse (cognitive 81). | +5.3 pts | High | Cognitive Complexity |
| Add a build/run (quick start) section to the root README — the first thing a newcomer needs. | +2.5 pts | Medium | Documentation (README) |
| Make sure a person approves each release. The release job names an environment, but its approval rules live in the code host's settings, where we can't see them. Check that a reviewer must approve each release, or publish releases as drafts first, so a bad build can be stopped before anyone downloads it. | +1.5 pts | Medium | Deployment & Rollback |
| Resolve the 2 End-of-life runtime finding(s) in Platform End-of-Life — start with WoofWare.Myriad.Plugins.fsproj, analyzers.fsproj. | +0.5 pts | Low | Platform End-of-Life |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| WoofWare.Myriad.Plugins/ArgParserRuntime.fs | 5.5 | Mixed | Cyclomatic Complexity: ArgParserRuntime.runParse (cyclomatic 52) |
| WoofWare.Myriad.Plugins/OpenApi3.fs | 5.5 | Mixed | Cyclomatic Complexity: Parameter.Parse (cyclomatic 17) |
| WoofWare.Myriad.Plugins/ArgParserGenerator.fs | 7.0 | Mixed | Cyclomatic Complexity: ArgParserGeneratorModule.createRecordParse (cyclomatic 67) |
| WoofWare.Myriad.Plugins/AstHelper.fs | 7.0 | Mixed | Cyclomatic Complexity: AstHelper.parseMember (cyclomatic 16) |
| WoofWare.Myriad.Plugins/SwaggerClientGenerator.fs | 7.0 | Mixed | Cyclomatic Complexity: SwaggerClientGeneratorModule.defnToType (cyclomatic 52) |
| WoofWare.Myriad.Plugins/HttpClientGenerator.fs | 7.2 | Mixed | Cyclomatic Complexity: HttpClientGeneratorModule.constructMember (cyclomatic 80) |
| WoofWare.Myriad.Plugins/CataGenerator.fs | 7.2 | Mixed | Cyclomatic Complexity: CataGenerator.analyse (cyclomatic 27) |
| REDACTED | 7.2 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 7.2 | Mixed | Dependency Vulnerabilities: High CVE: REDACTED |
| WoofWare.Myriad.Plugins/CapturingInterfaceMockGenerator.fs | 7.4 | Mixed | Cyclomatic Complexity: CapturingInterfaceMockGeneratorModule.createType (cyclomatic 60) |
| WoofWare.Myriad.Plugins/JsonParseGenerator.fs | 7.4 | Mixed | Cyclomatic Complexity: JsonParseGeneratorModule.parseNonNullableNode (cyclomatic 34) |
| WoofWare.Myriad.Plugins/JsonSerializeGenerator.fs | 7.4 | Mixed | Cyclomatic Complexity: JsonSerializeGeneratorModule.serializeNodeNonNullable (cyclomatic 18) |
| WoofWare.Myriad.Plugins/InterfaceMockGenerator.fs | 7.8 | Mixed | Cyclomatic Complexity: InterfaceMockGeneratorModule.createType (cyclomatic 35) |
| REDACTED | 7.9 | Mixed | Supply-chain Provenance & Signing: REDACTED |
| REDACTED | 7.9 | Mixed | Supply-chain Provenance & Signing: REDACTED |
| WoofWare.Myriad.Plugins/WoofWare.Myriad.Plugins.fsproj | 7.9 | Mixed | Platform End-of-Life: End-of-life runtime: .NET net6.0 |
| analyzers/analyzers.fsproj | 7.9 | Mixed | Platform End-of-Life: End-of-life runtime: .NET net6.0 |
| ConsumePlugin/RestApiExample.fs | 8.0 | Near-clean | Change Coupling: Boundary-crossing change coupling: RestApiExample.fs ↔ HttpClientGenerator.fs |
| WoofWare.Myriad.Plugins/Parameters.fs | 8.5 | Near-clean | Code Coverage: Low coverage: WoofWare.Myriad.Plugins/Parameters.fs |
| WoofWare.Myriad.Plugins/Measure.fs | 8.5 | Near-clean | Code Coverage: Low coverage: WoofWare.Myriad.Plugins/Measure.fs |
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 36 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.9, the weighted average across measured dimensions.
What we checked — 36 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, 81 of 97 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
- D4 Code Duplication — 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. Code Duplication couldn't be assessed within its 9-minute budget on a solution this large — not included in this run.
- 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. Single-contributor repository — bus factor is not applicable (1 contributor(s) across 491 commit(s) sampled, automation and bot accounts excluded). Concentration needs a team to concentrate: with one contributor there is nobody to spread the knowledge to, so there is nothing here for the owner to act on.
- 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. This check's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
- 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.
- P8 Schema migrations — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads EF Core usage in C# and the schema tooling its file scan recognises only, and no .NET project was loaded, and this repository's language is not one the scan models, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- S1 Web-Security Posture — 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 web-security controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks web-security controls.
- X1 Async correctness — not measured this run — 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.
- X6 Hand-rolled structured-format parsing — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and Python, JavaScript/TypeScript, Go, Java/Kotlin/Scala, Ruby, PHP, Rust, Swift, Erlang, Elixir and Dart source only, and no C# was loaded and none of those languages was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X7 Silent fallback defaults — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C#, Python, TypeScript/JavaScript, Rust, Go, Java, Kotlin, Scala, PHP, Ruby, Swift and Dart syntax only, and no C#, Python, TypeScript/JavaScript, Rust, Go, Java, Kotlin, Scala, PHP, Ruby, Swift or Dart was loaded for this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
Limitations & what we did not check
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.
- D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
- D8 Code Coverage: Coverage is measured by building and running the test suite inside our isolated image — the target repo is never modified, and nothing on your systems runs. So coverage exists only when the suite builds and runs within the inline time budget; one that needs external services, can't build, or exceeds the budget yields no coverage (D8 then degrades to not-measured, not a low score). Line coverage also says nothing about assertion quality.
- 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.
- D21 Naming Consistency: Naming consistency compares each name with the convention its structural peers follow in this repository: it cannot tell whether a consistently used name is a good one, and languages other than C# and TypeScript are not measured.
- D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
- D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
- P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
- P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
Dimensions
D1 · Cyclomatic Complexity
25 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was HttpClientGeneratorModule.constructMember at 80. A further 2 method(s) were over the threshold but excluded as flat dispatchers (a long switch/match over independent cases: many branches, almost no nesting), the largest being DesiredGenerator.Parse at 18 — they are counted neither in the figure above nor in this dimension's score. 1 file carries no cyclomatic complexity row at all for this reason — every one of its over-threshold methods was excluded, so the exclusion is disclosed nowhere in the file itself: WoofWare.Myriad.Plugins/Parameters.fs (DesiredGenerator.Parse at 18). They are named here because the per-file figures other dimensions report are taken BEFORE this exclusion, so such a file can show a high maximum complexity elsewhere in this report and nothing here, with nothing to reconcile the two.
What to do
- Bring the 3 bodies over 60 down to 60 or less in Cyclomatic Complexity — start with HttpClientGeneratorModule.constructMember (cyclomatic 80), ArgParserGeneratorModule.createRecordParse (cyclomatic 67), ArgParserGeneratorModule.toParseSpec (cyclomatic 64). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 3 together lifts Cyclomatic Complexity from 2.3 to about 3.3/10, projected with the scoring formula itself and assuming each lands exactly at 60; a cleaner split scores higher.
D2 · Cognitive Complexity
28 method(s) exceeded the cognitive complexity threshold of 15; the worst was ArgParserGeneratorModule.toParseSpec at 135.
What to do
- Bring the 10 bodies over 30 down to 30 or less in Cognitive Complexity — start with ArgParserGeneratorModule.toParseSpec (cognitive 135), SwaggerClientGeneratorModule.defnToType (cognitive 114), ArgParserRuntime.runParse (cognitive 81). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 10 together lifts Cognitive Complexity from 2.0 to about 5.6/10, projected with the scoring formula itself and assuming each lands exactly at 30; a cleaner split scores higher.
D3 · God Classes
8 over-large unit(s) detected — types, modules or files that carry too much.
What to do
- Resolve the 8 FileTooLong finding(s) in God Classes — start with ArgParserGenerator.fs, ArgParserRuntime.fs, CataGenerator.fs. — One of this dimension's main actionable groups (8 warning-level).
D5 · Coupling
7 projects, 0 dependency cycle(s), 0 unstable depended-on project(s).
D8 · Code Coverage
Line coverage 77.7% — 9 file(s) below 50%.
What to do
- Resolve the 9 Low coverage finding(s) in Code Coverage — start with Parameters.fs, OpenApi3.fs, ArgParserRuntime.fs. — One of this dimension's main actionable groups (9 warning-level).
D12 · Dependency Hygiene
10 outdated, 0 vulnerable, 0 deprecated packages.
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D14 · License Compliance
0 of 144 packages use a banned license. ★ DEPTH: this repository's MSBuild projects declare 12 direct `PackageReference`(s), and 124 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.
D21 · Naming Consistency
3 naming inconsistencies among 45 declarations measured against a convention their peers follow.
What to do
- Resolve the 1 `GeneralAPISettings` spells `API` where 18 names in the project spell it… finding(s) in Naming Consistency — start with GeneratedSwaggerGitea.fs. — One of this dimension's main actionable groups (1 recommendation-level).
- Resolve the 1 `RepoGetByID` spells `ID` where 47 names in the project spell it `Id` finding(s) in Naming Consistency — start with GeneratedSwaggerGitea.fs. — One of this dimension's main actionable groups (1 recommendation-level).
- Resolve the 1 `GetGeneralAPISettings` spells `API` where 18 names in the project spell… finding(s) in Naming Consistency — start with GeneratedSwaggerGitea.fs. — One of this dimension's main actionable groups (1 recommendation-level).
D26 · Project Cohesion
2 of 3 build units (MSBuild) flagged as possibly oversized/incoherent.
What to do
- Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion. — One of this dimension's main actionable groups (1 recommendation-level).
D27 · Navigability
100 % of calls cross a namespace and 3 % go through an interface, but 65 % of collaborators are co-located — so following a call takes several hops. Baseline: small — navigation cost is tolerated.
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
1 finding(s): 0 critical, 1 high, 0 medium, 0 low. Separately, one or more rules could not re-parse an embedded snippet in 1 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.
What to do
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
D30 · Dependency Vulnerabilities
1 finding(s): 0 critical, 1 high, 0 medium, 0 low.
What to do
- Resolve the 1 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
D34 · Knowledge Freshness
Every significant source file has living knowledge — recently and meaningfully worked. Counted over 25 of the 70 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
D35 · Change Coupling
Strongest change-coupling: RestApiExample.fs↔HttpClientGenerator.fs 96%
What to do
- Resolve the 1 Boundary-crossing change coupling finding(s) in Change Coupling — start with RestApiExample.fs. — One of this dimension's main actionable groups (1 issue-level).
D36 · Supply-chain Provenance & Signing
3/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).
What to do
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
D44 · Platform End-of-Life
1 end-of-life runtime(s) and 0 end-of-life framework(s), read from 7 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.
What to do
- Resolve the 2 End-of-life runtime finding(s) in Platform End-of-Life — start with WoofWare.Myriad.Plugins.fsproj, analyzers.fsproj. — One of this dimension's main actionable groups (2 warning-level).
Frontend & cross-cutting dimensions
AX10 · Code composition
AX3 · Project dependency cycles
AX4 · Dependency direction
AX8 · Test isolation
GD1 · Unfinished & placeholder code
M1 · Documentation (README)
What to do
- Add a build/run (quick start) section to the root README — the first thing a newcomer needs.
- Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
- No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
- Add a C4 context/container diagram (Structurizr, PlantUML or Mermaid) or an architecture.md overview.
M3 · Folder & project structure
M4 · Documentation accuracy
P1 · CI/CD gates
P3 · Security & performance tooling
- No static application security testing detected. For this repository's stack, add `semgrep --config=auto` plus gitleaks for committed secrets (F# is not a CodeQL language and has no language-specific SAST engine) as a CI step. What was searched, so you can tell an absence from a miss: the 3 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:7
What to do
- Add a SAST step to CI running what this repository's stack ships: `semgrep --config=auto` plus gitleaks for committed secrets (F# is not a CodeQL language and has no language-specific SAST engine) — so a security regression fails the build instead of landing.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
What to do
- Make sure a person approves each release. The release job names an environment, but its approval rules live in the code host's settings, where we can't see them. Check that a reviewer must approve each release, or publish releases as drafts first, so a bad build can be stopped before anyone downloads it.
P6 · Release Hygiene
PF3 · Async & latency hygiene
X27 · Collection changed while being enumerated
X28 · Index access outside its own emptiness guard
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 47% | Checked 3 of 11 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 89% | Adequate — gated by D26 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Maturity | 57% | Adequate — gated by M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 68% | Adequate — gated by P3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 80% | Checked 4 of 10 | Solid. |
| Performance | 100% | Exemplary | Strongest area. |
Unscored — 1 check(s) recorded observations but carry no score
- SC1 Supply-chain hygiene — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Not evidenced — 4 control(s) we could not find positive evidence for
- C3 Audit Trail — Not assessed: these audit controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks audit controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- C4 Data Retention — Not assessed: these retention controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks retention controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- C5 Data-Subject Rights — Not assessed: these data-subject rights controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks data-subject rights controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 76 check(s) not relevant to this codebase
- AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
- AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
- AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
- AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
- AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
- AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
- AX1 Captive dependencies — 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.
- 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.
- AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX6 Interface segregation — not assessed — interface segregation is computed over a type surface that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
- AXB1 Runtime evidence locked — no reproducible boot — This repository has nothing the runtime tiers could boot or serve — no markup, no UI framework or web-server dependency, no UI component source, no native UI project and no API definition — nothing here is a surface to boot — so runtime a11y/egress/header evidence has no subject here. Not applicable: this is neither a gap in the scan nor a finding about your code.
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- 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 — ~17451 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 — single-contributor repository — bus factor is not applicable
- D17 Explicit Debt — the C# workspace loaded 0 projects, so explicit-debt density could not be measured
- D18 Solution Shape — D18 scores the shape of a C#/VB .NET solution; this repository's .NET projects are all F# (.fsproj), which the C#/VB workspace does not load, so the dimension does not apply.
- D19 Documentation Quality — No runnable or published unit to look for an example in, and no multi-project root README to look for a map in; the other documentation kinds are withheld (see the gaps), so documentation quality is not applicable here.
- D20 ADR Quality — N/A — ADRs are expected on deployable products with a user-facing host, not consumed libraries; no ADR log is required here.
- 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 — this repository's production source is .fs, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D25 ADR Conformance — no ADRs to check
- D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
- D32 Data Compliance (PII/GDPR) — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
- 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.
- D4 Code Duplication — Code Duplication not included (time budget)
- 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.
- D6 Cohesion (LCOM4) — Cohesion (LCOM4) was not measured: of the 48 type(s) found, none both holds instance state and has two or more methods whose shared use of it could be read (39 with fewer than two methods, 9 stateless), so LCOM4 is undefined for every type in this repository. Not scored — the metric does not apply here, and this is not a finding about this repository.
- D7 Architectural Integrity — no checkable ADRs and no dependency cycles — architectural integrity not assessed
- DM1 Domain Modelling — applicable but not scored (2 of 3 signals for this style — below the bar we score at): 492 value object(s); 14 domain event(s); its domain events are published by services or handlers — no domain entity raises one
- ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
- ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
- P2 Observability — This repository's F# source (3 module(s), 69 file(s) read) declares no entry point and bootstraps no server, and nothing here deploys a service — it is a library, run inside whatever hosts it, so production observability (structured logging, tracing/metrics, health checks) is N/A. If it grows a binary or a service, the dimension reactivates.
- P7 Outbound HTTP resilience — not measured — the application kind could not be determined for this repo
- P8 Schema migrations — 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
- P9 Domain vs controller coverage — coverage data present for 24 file(s), but no domain-layer files were identified: no covered file's path contains any of the markers this check keys on (/domain/, /aggregates/, /valueobjects/, /domainmodel/, .domain/, /entities/), which are matched case-insensitively anywhere in the path. With no domain partition there is nothing to compare the web/controller layer against — if this repository keeps its business rules under a folder named none of those, that naming is what the check cannot see, not the domain logic.
- PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for a BenchmarkDotNet reference in an .fsproj or .vbproj, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
- PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
- S1 Web-Security Posture — Not assessed: these web-security controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks web-security controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- 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.
- X29 Per-element action decided by a fixed element — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X3 Exception handling — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X30 Support guard that admits what it rejects — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X32 Type resolved by simple name across every loaded assembly — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X4 Structured logging — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X5 Nullable reference types — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X6 Hand-rolled structured-format parsing — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X7 Silent fallback defaults — 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
- 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 — 3 finding(s)
- REDACTED
- REDACTED
- Boundary-crossing change coupling: RestApiExample.fs ↔ HttpClientGenerator.fs ConsumePlugin/RestApiExample.fs:1
Serious — 75 finding(s)
- Low coverage: WoofWare.Myriad.Plugins/Parameters.fs WoofWare.Myriad.Plugins/Parameters.fs:1
- Low coverage: WoofWare.Myriad.Plugins/OpenApi3.fs WoofWare.Myriad.Plugins/OpenApi3.fs:1
- Low coverage: WoofWare.Myriad.Plugins/ArgParserRuntime.fs WoofWare.Myriad.Plugins/ArgParserRuntime.fs:1
- Low coverage: WoofWare.Myriad.Plugins/AstHelper.fs WoofWare.Myriad.Plugins/AstHelper.fs:1
- Low coverage: WoofWare.Myriad.Plugins/Measure.fs WoofWare.Myriad.Plugins/Measure.fs:1
- Low coverage: WoofWare.Myriad.Plugins/List.fs WoofWare.Myriad.Plugins/List.fs:1
- Low coverage: WoofWare.Myriad.Plugins.Attributes/Attributes.fs WoofWare.Myriad.Plugins.Attributes/Attributes.fs:1
- Low coverage: WoofWare.Myriad.Plugins.Attributes/ArgParserAttributes.fs WoofWare.Myriad.Plugins.Attributes/ArgParserAttributes.fs:1
- Low coverage: WoofWare.Myriad.Plugins.Attributes/RestEase.fs WoofWare.Myriad.Plugins.Attributes/RestEase.fs:1
- FileTooLong: WoofWare.Myriad.Plugins/ArgParserGenerator.fs WoofWare.Myriad.Plugins/ArgParserGenerator.fs
- FileTooLong: WoofWare.Myriad.Plugins/ArgParserRuntime.fs WoofWare.Myriad.Plugins/ArgParserRuntime.fs
- FileTooLong: WoofWare.Myriad.Plugins/CataGenerator.fs WoofWare.Myriad.Plugins/CataGenerator.fs
- FileTooLong: WoofWare.Myriad.Plugins/OpenApi3.fs WoofWare.Myriad.Plugins/OpenApi3.fs
- FileTooLong: WoofWare.Myriad.Plugins/JsonParseGenerator.fs WoofWare.Myriad.Plugins/JsonParseGenerator.fs
- FileTooLong: WoofWare.Myriad.Plugins/SwaggerClientGenerator.fs WoofWare.Myriad.Plugins/SwaggerClientGenerator.fs
- FileTooLong: WoofWare.Myriad.Plugins/JsonSerializeGenerator.fs WoofWare.Myriad.Plugins/JsonSerializeGenerator.fs
- FileTooLong: WoofWare.Myriad.Plugins/CapturingInterfaceMockGenerator.fs WoofWare.Myriad.Plugins/CapturingInterfaceMockGenerator.fs
- End-of-life runtime: .NET net6.0 WoofWare.Myriad.Plugins/WoofWare.Myriad.Plugins.fsproj:4
- End-of-life runtime: .NET net6.0 analyzers/analyzers.fsproj:7
- HttpClientGeneratorModule.constructMember (cyclomatic 80) WoofWare.Myriad.Plugins/HttpClientGenerator.fs:222
- ArgParserGeneratorModule.createRecordParse (cyclomatic 67) WoofWare.Myriad.Plugins/ArgParserGenerator.fs:2271
- ArgParserGeneratorModule.toParseSpec (cyclomatic 64) WoofWare.Myriad.Plugins/ArgParserGenerator.fs:1532
- ArgParserGeneratorModule.createParseFunction (cyclomatic 60) WoofWare.Myriad.Plugins/ArgParserGenerator.fs:1040
- CapturingInterfaceMockGeneratorModule.createType (cyclomatic 60) WoofWare.Myriad.Plugins/CapturingInterfaceMockGenerator.fs:189
- SwaggerClientGeneratorModule.defnToType (cyclomatic 52) WoofWare.Myriad.Plugins/SwaggerClientGenerator.fs:308
- ArgParserRuntime.runParse (cyclomatic 52) WoofWare.Myriad.Plugins/ArgParserRuntime.fs:1301
- SwaggerV2Generator.generate (cyclomatic 38) WoofWare.Myriad.Plugins/SwaggerClientGenerator.fs:759
- InterfaceMockGeneratorModule.createType (cyclomatic 35) WoofWare.Myriad.Plugins/InterfaceMockGenerator.fs:27
- JsonParseGeneratorModule.parseNonNullableNode (cyclomatic 34) WoofWare.Myriad.Plugins/JsonParseGenerator.fs:270
- ArgParserRuntime.scan (cyclomatic 31) WoofWare.Myriad.Plugins/ArgParserRuntime.fs:252
- ArgParserGeneratorModule.helpText (cyclomatic 30) WoofWare.Myriad.Plugins/ArgParserGenerator.fs:2049
- CataGenerator.analyse (cyclomatic 27) WoofWare.Myriad.Plugins/CataGenerator.fs:220
- ArgParserRuntime.resolve (cyclomatic 24) WoofWare.Myriad.Plugins/ArgParserRuntime.fs:626
- SwaggerClientGeneratorModule.computeType (cyclomatic 22) WoofWare.Myriad.Plugins/SwaggerClientGenerator.fs:603
- ArgParserGeneratorModule.createModule (cyclomatic 22) WoofWare.Myriad.Plugins/ArgParserGenerator.fs:3153
- WellFormedSchemaModule.errors (cyclomatic 22) WoofWare.Myriad.Plugins/ArgParserRuntime.fs:990
- HttpClientGeneratorModule.createModule (cyclomatic 21) WoofWare.Myriad.Plugins/HttpClientGenerator.fs:987
- SwaggerClientGeneratorModule.selectMimeType (cyclomatic 20) WoofWare.Myriad.Plugins/SwaggerClientGenerator.fs:248
- ParseTreeModule.accumulators (cyclomatic 19) WoofWare.Myriad.Plugins/ArgParserGenerator.fs:303
- ArgParserRuntime.selectWith (cyclomatic 19) WoofWare.Myriad.Plugins/ArgParserRuntime.fs:516
- ArgParserRuntime.validate (cyclomatic 18) WoofWare.Myriad.Plugins/ArgParserRuntime.fs:788
- JsonSerializeGeneratorModule.serializeNodeNonNullable (cyclomatic 18) WoofWare.Myriad.Plugins/JsonSerializeGenerator.fs:101
- Parameter.Parse (cyclomatic 17) WoofWare.Myriad.Plugins/OpenApi3.fs:847
- AstHelper.parseMember (cyclomatic 16) WoofWare.Myriad.Plugins/AstHelper.fs:247
- ArgParserGeneratorModule.toParseSpec (cognitive 135) WoofWare.Myriad.Plugins/ArgParserGenerator.fs:1532
- SwaggerClientGeneratorModule.defnToType (cognitive 114) WoofWare.Myriad.Plugins/SwaggerClientGenerator.fs:308
- ArgParserRuntime.runParse (cognitive 81) WoofWare.Myriad.Plugins/ArgParserRuntime.fs:1301
- HttpClientGeneratorModule.constructMember (cognitive 81) WoofWare.Myriad.Plugins/HttpClientGenerator.fs:222
- ArgParserGeneratorModule.createParseFunction (cognitive 69) WoofWare.Myriad.Plugins/ArgParserGenerator.fs:1040
- CapturingInterfaceMockGeneratorModule.createType (cognitive 62) WoofWare.Myriad.Plugins/CapturingInterfaceMockGenerator.fs:189
- ArgParserGeneratorModule.createRecordParse (cognitive 59) WoofWare.Myriad.Plugins/ArgParserGenerator.fs:2271
- ArgParserRuntime.scan (cognitive 56) WoofWare.Myriad.Plugins/ArgParserRuntime.fs:252
- SwaggerV2Generator.generate (cognitive 52) WoofWare.Myriad.Plugins/SwaggerClientGenerator.fs:759
- ArgParserRuntime.resolve (cognitive 34) WoofWare.Myriad.Plugins/ArgParserRuntime.fs:626
- ArgParserGeneratorModule.createModule (cognitive 30) WoofWare.Myriad.Plugins/ArgParserGenerator.fs:3153
- InterfaceMockGeneratorModule.createType (cognitive 30) WoofWare.Myriad.Plugins/InterfaceMockGenerator.fs:27
- CataGenerator.analyse (cognitive 27) WoofWare.Myriad.Plugins/CataGenerator.fs:220
- ArgParserRuntime.selectWith (cognitive 26) WoofWare.Myriad.Plugins/ArgParserRuntime.fs:516
- SwaggerClientGeneratorModule.selectMimeType (cognitive 22) WoofWare.Myriad.Plugins/SwaggerClientGenerator.fs:248
- WellFormedSchemaModule.errors (cognitive 21) WoofWare.Myriad.Plugins/ArgParserRuntime.fs:990
- HttpClientGeneratorModule.createModule (cognitive 21) WoofWare.Myriad.Plugins/HttpClientGenerator.fs:987
- SwaggerClientGeneratorModule.computeType (cognitive 20) WoofWare.Myriad.Plugins/SwaggerClientGenerator.fs:603
- Parameter.Parse (cognitive 19) WoofWare.Myriad.Plugins/OpenApi3.fs:847
- ParseTreeModule.accumulators (cognitive 19) WoofWare.Myriad.Plugins/ArgParserGenerator.fs:303
- MediaType.Parse (cognitive 18) WoofWare.Myriad.Plugins/OpenApi3.fs:321
- Header.Parse (cognitive 18) WoofWare.Myriad.Plugins/OpenApi3.fs:410
- JsonSerializeGeneratorModule.serializeNodeNonNullable (cognitive 18) WoofWare.Myriad.Plugins/JsonSerializeGenerator.fs:101
- Response.Parse (cognitive 17) WoofWare.Myriad.Plugins/OpenApi3.fs:558
- Operation.Parse (cognitive 17) WoofWare.Myriad.Plugins/OpenApi3.fs:1019
- JsonParseGeneratorModule.parseNonNullableNode (cognitive 17) WoofWare.Myriad.Plugins/JsonParseGenerator.fs:270
- ArgParserRuntime.validate (cognitive 16) WoofWare.Myriad.Plugins/ArgParserRuntime.fs:788
- CataGenerator.createBaseMatchClause (cognitive 16) WoofWare.Myriad.Plugins/CataGenerator.fs:754
- REDACTED
- REDACTED
- NuGet dependencies are not locked
Minor — 9 finding(s)
- `GeneralAPISettings` spells `API` where 18 names in the project spell it `Api` ConsumePlugin/GeneratedSwaggerGitea.fs:1177
- `RepoGetByID` spells `ID` where 47 names in the project spell it `Id` ConsumePlugin/GeneratedSwaggerGitea.fs:5917
- `GetGeneralAPISettings` spells `API` where 18 names in the project spell it `Api` ConsumePlugin/GeneratedSwaggerGitea.fs:5924
- Projects may be oversized for their cohesion
- REDACTED
- REDACTED
- No ADRs
- No architecture diagram/doc
- No SAST REDACTED:7
Minor — 10 finding(s)
- Outdated: FSharp.Core
- Outdated: Myriad.Sdk
- Outdated: ApiSurface
- Outdated: Microsoft.NET.Test.Sdk
- Outdated: NUnit
- Outdated: NUnit3TestAdapter
- Outdated: FsCheck
- Outdated: FsUnit
- Outdated: WoofWare.Expect
- Outdated: Myriad.Core
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-34877d4130fa4cf9bf2bda984ee8f3bb/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-34877d4130fa4cf9bf2bda984ee8f3bb/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 . | 1 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | dotnet | — | dotnet list WoofWare.Myriad.slnx package --vulnerable --include-transitive --format json | 1 | artifacts/raw/dotnet-vulnerable.json |
| D31 · IaC & Container Security | trivy | — | trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan. | 0 | — |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. | 0 | — |
| 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-d772be9f4bee41c896d1cbe18ae38c3b | 0 | artifacts/raw/osv-scanner.json |