Executive summary
ChrisNikkel/SharpVG meets our standard for production, though we found no automated security scanning of the code, its secrets or its dependencies. It scores 74 out of 100 and is rated Strong, and all three of its critical findings are security problems in the build pipeline.
Production Readiness, at 68, is the weakest lens and counts most in the score. The best first steps are replacing each deprecated dependency and recording design decisions, each worth about 3 points. Raising Production Readiness to 70 would lift the score to about 76.
Three pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Pinning each tool to an exact version would close this risk.
The product code is 5,062 lines, about €15,000 to rebuild.
If Production Readiness rose from 68 to 70, the lowest score rated Strong, the score would rise from 74 to about 76.
New since the last survey: 2 findings
- Churn × Complexity Hotspots · Hotspot: SharpVG/SvgParser.fs SharpVG/SvgParser.fs
- Supply-chain Provenance & Signing · REDACTED
Fixed since the last survey: 2 findings
- Supply-chain Provenance & Signing REDACTED
- Platform End-of-Life · End-of-life runtime: .NET net9.0
Rebuild cost: about €15,000 · Estimate
| Cost to rebuild | €5,000 to €25,000, for 84 to 266 hours of work, about 0.1 person-years for one engineer |
|---|---|
| Difficulty of the problem | Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×1.1 at a score of 74. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it. |
| Size | Small: 5,062 lines of product code |
| What it is not | Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one. |
Top priorities
Diagnosis: what the measurements show together
Architecture — module dependency graph
Architecture: which parts of the code depend on which
| uses → | 1 SharpVG | 2 SharpVG.AnchorModule | 3 SharpVG.AnimationModule | 4 SharpVG.AreaModule | 5 SharpVG.AttributeModule | 6 SharpVG.AttributeTypeModule | 7 SharpVG.BodyModule | 8 SharpVG.CircleModule | 9 SharpVG.ClipPathModule | 10 SharpVG.ColorModule | 11 SharpVG.ElementModule | 12 SharpVG.EllipseModule | 13 SharpVG.FilterEffectModule | 14 SharpVG.FilterModule | 15 SharpVG.GradientModule | 16 SharpVG.GradientStopModule | 17 SharpVG.GraphicModule | 18 SharpVG.GroupModule | 19 SharpVG.HRefModule | 20 SharpVG.ImageModule | 21 SharpVG.LengthModule | 22 SharpVG.LineModule | 23 SharpVG.LinearGradientModule | 24 SharpVG.MarkerModule | 25 SharpVG.MaskModule | 26 SharpVG.PathModule | 27 SharpVG.PatternModule | 28 SharpVG.PenModule | 29 SharpVG.PointModule | 30 SharpVG.Points | 31 SharpVG.PolygonModule | 32 SharpVG.PolylineModule | 33 SharpVG.PreserveAspectRatioModule | 34 SharpVG.RadialGradientModule | 35 SharpVG.RawElementModule | 36 SharpVG.RectModule | 37 SharpVG.StyleModule | 38 SharpVG.StylesModule | 39 SharpVG.SvgParserHelpers | 40 SharpVG.SvgElementParsers |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 SharpVG | ||||||||||||||||||||||||||||||||||||||||
| 2 SharpVG.AnchorModule | 3 | |||||||||||||||||||||||||||||||||||||||
| 3 SharpVG.AnimationModule | 8 | |||||||||||||||||||||||||||||||||||||||
| 4 SharpVG.AreaModule | 4 | |||||||||||||||||||||||||||||||||||||||
| 5 SharpVG.AttributeModule | 3 | |||||||||||||||||||||||||||||||||||||||
| 6 SharpVG.AttributeTypeModule | 1 | |||||||||||||||||||||||||||||||||||||||
| 7 SharpVG.BodyModule | 2 | |||||||||||||||||||||||||||||||||||||||
| 8 SharpVG.CircleModule | 4 | |||||||||||||||||||||||||||||||||||||||
| 9 SharpVG.ClipPathModule | 4 | |||||||||||||||||||||||||||||||||||||||
| 10 SharpVG.ColorModule | 2 | |||||||||||||||||||||||||||||||||||||||
| 11 SharpVG.ElementModule | 8 | |||||||||||||||||||||||||||||||||||||||
| 12 SharpVG.EllipseModule | 3 | |||||||||||||||||||||||||||||||||||||||
| 13 SharpVG.FilterEffectModule | 15 | |||||||||||||||||||||||||||||||||||||||
| 14 SharpVG.FilterModule | 5 | |||||||||||||||||||||||||||||||||||||||
| 15 SharpVG.GradientModule | 3 | |||||||||||||||||||||||||||||||||||||||
| 16 SharpVG.GradientStopModule | 3 | |||||||||||||||||||||||||||||||||||||||
| 17 SharpVG.GraphicModule | 12 | |||||||||||||||||||||||||||||||||||||||
| 18 SharpVG.GroupModule | 7 | |||||||||||||||||||||||||||||||||||||||
| 19 SharpVG.HRefModule | 1 | |||||||||||||||||||||||||||||||||||||||
| 20 SharpVG.ImageModule | 5 | |||||||||||||||||||||||||||||||||||||||
| 21 SharpVG.LengthModule | 1 | |||||||||||||||||||||||||||||||||||||||
| 22 SharpVG.LineModule | 3 | |||||||||||||||||||||||||||||||||||||||
| 23 SharpVG.LinearGradientModule | 8 | |||||||||||||||||||||||||||||||||||||||
| 24 SharpVG.MarkerModule | 9 | |||||||||||||||||||||||||||||||||||||||
| 25 SharpVG.MaskModule | 6 | |||||||||||||||||||||||||||||||||||||||
| 26 SharpVG.PathModule | 7 | |||||||||||||||||||||||||||||||||||||||
| 27 SharpVG.PatternModule | 9 | |||||||||||||||||||||||||||||||||||||||
| 28 SharpVG.PenModule | 3 | |||||||||||||||||||||||||||||||||||||||
| 29 SharpVG.PointModule | 3 | |||||||||||||||||||||||||||||||||||||||
| 30 SharpVG.Points | 1 | |||||||||||||||||||||||||||||||||||||||
| 31 SharpVG.PolygonModule | 3 | |||||||||||||||||||||||||||||||||||||||
| 32 SharpVG.PolylineModule | 3 | |||||||||||||||||||||||||||||||||||||||
| 33 SharpVG.PreserveAspectRatioModule | 4 | |||||||||||||||||||||||||||||||||||||||
| 34 SharpVG.RadialGradientModule | 9 | |||||||||||||||||||||||||||||||||||||||
| 35 SharpVG.RawElementModule | 3 | |||||||||||||||||||||||||||||||||||||||
| 36 SharpVG.RectModule | 4 | |||||||||||||||||||||||||||||||||||||||
| 37 SharpVG.StyleModule | 14 | |||||||||||||||||||||||||||||||||||||||
| 38 SharpVG.StylesModule | 2 | |||||||||||||||||||||||||||||||||||||||
| 39 SharpVG.SvgParserHelpers | 14 | |||||||||||||||||||||||||||||||||||||||
| 40 SharpVG.SvgElementParsers | 3 | 1 |
2→1 SharpVG.AnchorModule uses SharpVG✕
- Connections
- 3 pairs of types, where a type in SharpVG.AnchorModule uses a type in SharpVG.
- The types involved
SharpVG.AnchorModule.AnchorModule→SharpVG.AnchorSharpVG.AnchorModule.AnchorModule→SharpVG.ElementSharpVG.AnchorModule.AnchorModule→SharpVG.Tag
- Direction
- SharpVG.AnchorModule uses SharpVG, so a change to SharpVG can break SharpVG.AnchorModule, while a change to SharpVG.AnchorModule can't break SharpVG.
- Position
- Below the diagonal: SharpVG.AnchorModule uses a module listed above it, which is the healthy direction.
3→1 SharpVG.AnimationModule uses SharpVG✕
- Connections
- 8 pairs of types, where a type in SharpVG.AnimationModule uses a type in SharpVG.
- The types involved
SharpVG.AnimationModule.AnimationModule→SharpVG.AdditiveSharpVG.AnimationModule.AnimationModule→SharpVG.AnimationSharpVG.AnimationModule.AnimationModule→SharpVG.AttributeTypeSharpVG.AnimationModule.AnimationModule→SharpVG.CalculationModeSharpVG.AnimationModule.AnimationModule→SharpVG.PathSharpVG.AnimationModule.AnimationModule→SharpVG.TagSharpVG.AnimationModule.AnimationModule→SharpVG.TimingSharpVG.AnimationModule.AnimationModule→SharpVG.Transform
- Direction
- SharpVG.AnimationModule uses SharpVG, so a change to SharpVG can break SharpVG.AnimationModule, while a change to SharpVG.AnimationModule can't break SharpVG.
- Position
- Below the diagonal: SharpVG.AnimationModule uses a module listed above it, which is the healthy direction.
4→1 SharpVG.AreaModule uses SharpVG✕
- Connections
- 4 pairs of types, where a type in SharpVG.AreaModule uses a type in SharpVG.
- The types involved
SharpVG.AreaModule.AreaModule→SharpVG.AreaSharpVG.AreaModule.AreaModule→SharpVG.AttributeSharpVG.AreaModule.AreaModule→SharpVG.LengthSharpVG.AreaModule.AreaModule→SharpVG.Point
- Direction
- SharpVG.AreaModule uses SharpVG, so a change to SharpVG can break SharpVG.AreaModule, while a change to SharpVG.AreaModule can't break SharpVG.
- Position
- Below the diagonal: SharpVG.AreaModule uses a module listed above it, which is the healthy direction.
5→1 SharpVG.AttributeModule uses SharpVG✕
- Connections
- 3 pairs of types, where a type in SharpVG.AttributeModule uses a type in SharpVG.
- The types involved
SharpVG.AttributeModule.AttributeModule→SharpVG.AttributeSharpVG.AttributeModule.AttributeModule→SharpVG.AttributeTypeSharpVG.AttributeModule.AttributeModule→SharpVG.HRef
- Direction
- SharpVG.AttributeModule uses SharpVG, so a change to SharpVG can break SharpVG.AttributeModule, while a change to SharpVG.AttributeModule can't break SharpVG.
- Position
- Below the diagonal: SharpVG.AttributeModule uses a module listed above it, which is the healthy direction.
6→1 SharpVG.AttributeTypeModule uses SharpVG✕
- Connections
- 1 pair of types, where a type in SharpVG.AttributeTypeModule uses a type in SharpVG.
- The types involved
SharpVG.AttributeTypeModule.AttributeTypeModule→SharpVG.AttributeType
- Direction
- SharpVG.AttributeTypeModule uses SharpVG, so a change to SharpVG can break SharpVG.AttributeTypeModule, while a change to SharpVG.AttributeTypeModule can't break SharpVG.
- Position
- Below the diagonal: SharpVG.AttributeTypeModule uses a module listed above it, which is the healthy direction.
7→1 SharpVG.BodyModule uses SharpVG✕
- Connections
- 2 pairs of types, where a type in SharpVG.BodyModule uses a type in SharpVG.
- The types involved
SharpVG.BodyModule.BodyModule→SharpVG.GroupElementSharpVG.BodyModule.BodyModule→SharpVG.Style
- Direction
- SharpVG.BodyModule uses SharpVG, so a change to SharpVG can break SharpVG.BodyModule, while a change to SharpVG.BodyModule can't break SharpVG.
- Position
- Below the diagonal: SharpVG.BodyModule uses a module listed above it, which is the healthy direction.
8→1 SharpVG.CircleModule uses SharpVG✕
- Connections
- 4 pairs of types, where a type in SharpVG.CircleModule uses a type in SharpVG.
- The types involved
SharpVG.CircleModule.CircleModule→SharpVG.CircleSharpVG.CircleModule.CircleModule→SharpVG.LengthSharpVG.CircleModule.CircleModule→SharpVG.PointSharpVG.CircleModule.CircleModule→SharpVG.Tag
- Direction
- SharpVG.CircleModule uses SharpVG, so a change to SharpVG can break SharpVG.CircleModule, while a change to SharpVG.CircleModule can't break SharpVG.
- Position
- Below the diagonal: SharpVG.CircleModule uses a module listed above it, which is the healthy direction.
9→1 SharpVG.ClipPathModule uses SharpVG✕
- Connections
- 4 pairs of types, where a type in SharpVG.ClipPathModule uses a type in SharpVG.
- The types involved
SharpVG.ClipPathModule.ClipPathModule→SharpVG.ClipPathSharpVG.ClipPathModule.ClipPathModule→SharpVG.ElementSharpVG.ClipPathModule.ClipPathModule→SharpVG.FilterUnitsSharpVG.ClipPathModule.ClipPathModule→SharpVG.Tag
- Direction
- SharpVG.ClipPathModule uses SharpVG, so a change to SharpVG can break SharpVG.ClipPathModule, while a change to SharpVG.ClipPathModule can't break SharpVG.
- Position
- Below the diagonal: SharpVG.ClipPathModule uses a module listed above it, which is the healthy direction.
10→1 SharpVG.ColorModule uses SharpVG✕
- Connections
- 2 pairs of types, where a type in SharpVG.ColorModule uses a type in SharpVG.
- The types involved
SharpVG.ColorModule.ColorModule→SharpVG.ColorSharpVG.ColorModule.ColorModule→SharpVG.Colors
- Direction
- SharpVG.ColorModule uses SharpVG, so a change to SharpVG can break SharpVG.ColorModule, while a change to SharpVG.ColorModule can't break SharpVG.
- Position
- Below the diagonal: SharpVG.ColorModule uses a module listed above it, which is the healthy direction.
11→1 SharpVG.ElementModule uses SharpVG✕
- Connections
- 8 pairs of types, where a type in SharpVG.ElementModule uses a type in SharpVG.
- The types involved
SharpVG.ElementModule.ElementModule→SharpVG.AnimationSharpVG.ElementModule.ElementModule→SharpVG.ElementSharpVG.ElementModule.ElementModule→SharpVG.HRefSharpVG.ElementModule.ElementModule→SharpVG.RawElementSharpVG.ElementModule.ElementModule→SharpVG.StyleSharpVG.ElementModule.ElementModule→SharpVG.TagSharpVG.ElementModule.ElementModule→SharpVG.TimingSharpVG.ElementModule.ElementModule→SharpVG.Transform
- Direction
- SharpVG.ElementModule uses SharpVG, so a change to SharpVG can break SharpVG.ElementModule, while a change to SharpVG.ElementModule can't break SharpVG.
- Position
- Below the diagonal: SharpVG.ElementModule uses a module listed above it, which is the healthy direction.
12→1 SharpVG.EllipseModule uses SharpVG✕
- Connections
- 3 pairs of types, where a type in SharpVG.EllipseModule uses a type in SharpVG.
- The types involved
SharpVG.EllipseModule.EllipseModule→SharpVG.EllipseSharpVG.EllipseModule.EllipseModule→SharpVG.PointSharpVG.EllipseModule.EllipseModule→SharpVG.Tag
- Direction
- SharpVG.EllipseModule uses SharpVG, so a change to SharpVG can break SharpVG.EllipseModule, while a change to SharpVG.EllipseModule can't break SharpVG.
- Position
- Below the diagonal: SharpVG.EllipseModule uses a module listed above it, which is the healthy direction.
13→1 SharpVG.FilterEffectModule uses SharpVG✕
- Connections
- 15 pairs of types, where a type in SharpVG.FilterEffectModule uses a type in SharpVG.
- The types involved
SharpVG.FilterEffectModule.FilterEffectModule→SharpVG.AreaSharpVG.FilterEffectModule.FilterEffectModule→SharpVG.BlendModeSharpVG.FilterEffectModule.FilterEffectModule→SharpVG.ChannelSelectorSharpVG.FilterEffectModule.FilterEffectModule→SharpVG.ColorSharpVG.FilterEffectModule.FilterEffectModule→SharpVG.ColorMatrixSharpVG.FilterEffectModule.FilterEffectModule→SharpVG.CompositeSharpVG.FilterEffectModule.FilterEffectModule→SharpVG.EdgeModeSharpVG.FilterEffectModule.FilterEffectModule→SharpVG.FilterEffectSharpVG.FilterEffectModule.FilterEffectModule→SharpVG.FilterEffectSourceSharpVG.FilterEffectModule.FilterEffectModule→SharpVG.LightSourceSharpVG.FilterEffectModule.FilterEffectModule→SharpVG.MorphologyOperatorSharpVG.FilterEffectModule.FilterEffectModule→SharpVG.NamedFilterEffectSharpVG.FilterEffectModule.FilterEffectModule→SharpVG.PointSharpVG.FilterEffectModule.FilterEffectModule→SharpVG.TransferFuncTypeSharpVG.FilterEffectModule.FilterEffectModule→SharpVG.TurbulenceType
- Direction
- SharpVG.FilterEffectModule uses SharpVG, so a change to SharpVG can break SharpVG.FilterEffectModule, while a change to SharpVG.FilterEffectModule can't break SharpVG.
- Position
- Below the diagonal: SharpVG.FilterEffectModule uses a module listed above it, which is the healthy direction.
14→1 SharpVG.FilterModule uses SharpVG✕
- Connections
- 5 pairs of types, where a type in SharpVG.FilterModule uses a type in SharpVG.
- The types involved
SharpVG.FilterModule.FilterModule→SharpVG.FilterSharpVG.FilterModule.FilterModule→SharpVG.FilterEffectSharpVG.FilterModule.FilterModule→SharpVG.FilterUnitsSharpVG.FilterModule.FilterModule→SharpVG.PointSharpVG.FilterModule.FilterModule→SharpVG.Tag
- Direction
- SharpVG.FilterModule uses SharpVG, so a change to SharpVG can break SharpVG.FilterModule, while a change to SharpVG.FilterModule can't break SharpVG.
- Position
- Below the diagonal: SharpVG.FilterModule uses a module listed above it, which is the healthy direction.
15→1 SharpVG.GradientModule uses SharpVG✕
- Connections
- 3 pairs of types, where a type in SharpVG.GradientModule uses a type in SharpVG.
- The types involved
SharpVG.GradientModule.GradientModule→SharpVG.GradientSharpVG.GradientModule.GradientModule→SharpVG.LinearGradientSharpVG.GradientModule.GradientModule→SharpVG.RadialGradient
- Direction
- SharpVG.GradientModule uses SharpVG, so a change to SharpVG can break SharpVG.GradientModule, while a change to SharpVG.GradientModule can't break SharpVG.
- Position
- Below the diagonal: SharpVG.GradientModule uses a module listed above it, which is the healthy direction.
16→1 SharpVG.GradientStopModule uses SharpVG✕
- Connections
- 3 pairs of types, where a type in SharpVG.GradientStopModule uses a type in SharpVG.
- The types involved
SharpVG.GradientStopModule.GradientStopModule→SharpVG.ColorSharpVG.GradientStopModule.GradientStopModule→SharpVG.GradientStopSharpVG.GradientStopModule.GradientStopModule→SharpVG.Tag
- Direction
- SharpVG.GradientStopModule uses SharpVG, so a change to SharpVG can break SharpVG.GradientStopModule, while a change to SharpVG.GradientStopModule can't break SharpVG.
- Position
- Below the diagonal: SharpVG.GradientStopModule uses a module listed above it, which is the healthy direction.
17→1 SharpVG.GraphicModule uses SharpVG✕
- Connections
- 12 pairs of types, where a type in SharpVG.GraphicModule uses a type in SharpVG.
- The types involved
SharpVG.GraphicModule.GraphicModule→SharpVG.CircleSharpVG.GraphicModule.GraphicModule→SharpVG.ElementSharpVG.GraphicModule.GraphicModule→SharpVG.EllipseSharpVG.GraphicModule.GraphicModule→SharpVG.GraphicSharpVG.GraphicModule.GraphicModule→SharpVG.ImageSharpVG.GraphicModule.GraphicModule→SharpVG.LineSharpVG.GraphicModule.GraphicModule→SharpVG.PathSharpVG.GraphicModule.GraphicModule→SharpVG.PolygonSharpVG.GraphicModule.GraphicModule→SharpVG.PolylineSharpVG.GraphicModule.GraphicModule→SharpVG.RectSharpVG.GraphicModule.GraphicModule→SharpVG.TextSharpVG.GraphicModule.GraphicModule→SharpVG.Use
- Direction
- SharpVG.GraphicModule uses SharpVG, so a change to SharpVG can break SharpVG.GraphicModule, while a change to SharpVG.GraphicModule can't break SharpVG.
- Position
- Below the diagonal: SharpVG.GraphicModule uses a module listed above it, which is the healthy direction.
18→1 SharpVG.GroupModule uses SharpVG✕
- Connections
- 7 pairs of types, where a type in SharpVG.GroupModule uses a type in SharpVG.
- The types involved
SharpVG.GroupModule.GroupModule→SharpVG.ElementSharpVG.GroupModule.GroupModule→SharpVG.GroupSharpVG.GroupModule.GroupModule→SharpVG.GroupElementSharpVG.GroupModule.GroupModule→SharpVG.LengthSharpVG.GroupModule.GroupModule→SharpVG.StyleSharpVG.GroupModule.GroupModule→SharpVG.TagSharpVG.GroupModule.GroupModule→SharpVG.Transform
- Direction
- SharpVG.GroupModule uses SharpVG, so a change to SharpVG can break SharpVG.GroupModule, while a change to SharpVG.GroupModule can't break SharpVG.
- Position
- Below the diagonal: SharpVG.GroupModule uses a module listed above it, which is the healthy direction.
19→1 SharpVG.HRefModule uses SharpVG✕
- Connections
- 1 pair of types, where a type in SharpVG.HRefModule uses a type in SharpVG.
- The types involved
SharpVG.HRefModule.HRefModule→SharpVG.HRef
- Direction
- SharpVG.HRefModule uses SharpVG, so a change to SharpVG can break SharpVG.HRefModule, while a change to SharpVG.HRefModule can't break SharpVG.
- Position
- Below the diagonal: SharpVG.HRefModule uses a module listed above it, which is the healthy direction.
20→1 SharpVG.ImageModule uses SharpVG✕
- Connections
- 5 pairs of types, where a type in SharpVG.ImageModule uses a type in SharpVG.
- The types involved
SharpVG.ImageModule.ImageModule→SharpVG.AreaSharpVG.ImageModule.ImageModule→SharpVG.ImageSharpVG.ImageModule.ImageModule→SharpVG.PointSharpVG.ImageModule.ImageModule→SharpVG.PreserveAspectRatioSharpVG.ImageModule.ImageModule→SharpVG.Tag
- Direction
- SharpVG.ImageModule uses SharpVG, so a change to SharpVG can break SharpVG.ImageModule, while a change to SharpVG.ImageModule can't break SharpVG.
- Position
- Below the diagonal: SharpVG.ImageModule uses a module listed above it, which is the healthy direction.
21→1 SharpVG.LengthModule uses SharpVG✕
- Connections
- 1 pair of types, where a type in SharpVG.LengthModule uses a type in SharpVG.
- The types involved
SharpVG.LengthModule.LengthModule→SharpVG.Length
- Direction
- SharpVG.LengthModule uses SharpVG, so a change to SharpVG can break SharpVG.LengthModule, while a change to SharpVG.LengthModule can't break SharpVG.
- Position
- Below the diagonal: SharpVG.LengthModule uses a module listed above it, which is the healthy direction.
22→1 SharpVG.LineModule uses SharpVG✕
- Connections
- 3 pairs of types, where a type in SharpVG.LineModule uses a type in SharpVG.
- The types involved
SharpVG.LineModule.LineModule→SharpVG.LineSharpVG.LineModule.LineModule→SharpVG.PointSharpVG.LineModule.LineModule→SharpVG.Tag
- Direction
- SharpVG.LineModule uses SharpVG, so a change to SharpVG can break SharpVG.LineModule, while a change to SharpVG.LineModule can't break SharpVG.
- Position
- Below the diagonal: SharpVG.LineModule uses a module listed above it, which is the healthy direction.
23→1 SharpVG.LinearGradientModule uses SharpVG✕
- Connections
- 8 pairs of types, where a type in SharpVG.LinearGradientModule uses a type in SharpVG.
- The types involved
SharpVG.LinearGradientModule.LinearGradientModule→SharpVG.FilterUnitsSharpVG.LinearGradientModule.LinearGradientModule→SharpVG.GradientStopSharpVG.LinearGradientModule.LinearGradientModule→SharpVG.HRefSharpVG.LinearGradientModule.LinearGradientModule→SharpVG.LinearGradientSharpVG.LinearGradientModule.LinearGradientModule→SharpVG.PointSharpVG.LinearGradientModule.LinearGradientModule→SharpVG.SpreadMethodSharpVG.LinearGradientModule.LinearGradientModule→SharpVG.TagSharpVG.LinearGradientModule.LinearGradientModule→SharpVG.Transform
- Direction
- SharpVG.LinearGradientModule uses SharpVG, so a change to SharpVG can break SharpVG.LinearGradientModule, while a change to SharpVG.LinearGradientModule can't break SharpVG.
- Position
- Below the diagonal: SharpVG.LinearGradientModule uses a module listed above it, which is the healthy direction.
24→1 SharpVG.MarkerModule uses SharpVG✕
- Connections
- 9 pairs of types, where a type in SharpVG.MarkerModule uses a type in SharpVG.
- The types involved
SharpVG.MarkerModule.MarkerModule→SharpVG.AreaSharpVG.MarkerModule.MarkerModule→SharpVG.ElementSharpVG.MarkerModule.MarkerModule→SharpVG.MarkerSharpVG.MarkerModule.MarkerModule→SharpVG.MarkerOrientSharpVG.MarkerModule.MarkerModule→SharpVG.MarkerUnitsSharpVG.MarkerModule.MarkerModule→SharpVG.PointSharpVG.MarkerModule.MarkerModule→SharpVG.PreserveAspectRatioSharpVG.MarkerModule.MarkerModule→SharpVG.TagSharpVG.MarkerModule.MarkerModule→SharpVG.ViewBox
- Direction
- SharpVG.MarkerModule uses SharpVG, so a change to SharpVG can break SharpVG.MarkerModule, while a change to SharpVG.MarkerModule can't break SharpVG.
- Position
- Below the diagonal: SharpVG.MarkerModule uses a module listed above it, which is the healthy direction.
25→1 SharpVG.MaskModule uses SharpVG✕
- Connections
- 6 pairs of types, where a type in SharpVG.MaskModule uses a type in SharpVG.
- The types involved
SharpVG.MaskModule.MaskModule→SharpVG.AreaSharpVG.MaskModule.MaskModule→SharpVG.ElementSharpVG.MaskModule.MaskModule→SharpVG.FilterUnitsSharpVG.MaskModule.MaskModule→SharpVG.MaskSharpVG.MaskModule.MaskModule→SharpVG.PointSharpVG.MaskModule.MaskModule→SharpVG.Tag
- Direction
- SharpVG.MaskModule uses SharpVG, so a change to SharpVG can break SharpVG.MaskModule, while a change to SharpVG.MaskModule can't break SharpVG.
- Position
- Below the diagonal: SharpVG.MaskModule uses a module listed above it, which is the healthy direction.
26→1 SharpVG.PathModule uses SharpVG✕
- Connections
- 7 pairs of types, where a type in SharpVG.PathModule uses a type in SharpVG.
- The types involved
SharpVG.PathModule.PathModule→SharpVG.AttributeSharpVG.PathModule.PathModule→SharpVG.EllipticalArcPathParametersSharpVG.PathModule.PathModule→SharpVG.LengthSharpVG.PathModule.PathModule→SharpVG.PathSharpVG.PathModule.PathModule→SharpVG.PathPositioningSharpVG.PathModule.PathModule→SharpVG.PointSharpVG.PathModule.PathModule→SharpVG.Tag
- Direction
- SharpVG.PathModule uses SharpVG, so a change to SharpVG can break SharpVG.PathModule, while a change to SharpVG.PathModule can't break SharpVG.
- Position
- Below the diagonal: SharpVG.PathModule uses a module listed above it, which is the healthy direction.
27→1 SharpVG.PatternModule uses SharpVG✕
- Connections
- 9 pairs of types, where a type in SharpVG.PatternModule uses a type in SharpVG.
- The types involved
SharpVG.PatternModule.PatternModule→SharpVG.AreaSharpVG.PatternModule.PatternModule→SharpVG.ElementSharpVG.PatternModule.PatternModule→SharpVG.FilterUnitsSharpVG.PatternModule.PatternModule→SharpVG.PatternSharpVG.PatternModule.PatternModule→SharpVG.PointSharpVG.PatternModule.PatternModule→SharpVG.PreserveAspectRatioSharpVG.PatternModule.PatternModule→SharpVG.TagSharpVG.PatternModule.PatternModule→SharpVG.TransformSharpVG.PatternModule.PatternModule→SharpVG.ViewBox
- Direction
- SharpVG.PatternModule uses SharpVG, so a change to SharpVG can break SharpVG.PatternModule, while a change to SharpVG.PatternModule can't break SharpVG.
- Position
- Below the diagonal: SharpVG.PatternModule uses a module listed above it, which is the healthy direction.
28→1 SharpVG.PenModule uses SharpVG✕
- Connections
- 3 pairs of types, where a type in SharpVG.PenModule uses a type in SharpVG.
- The types involved
SharpVG.PenModule.PenModule→SharpVG.ColorSharpVG.PenModule.PenModule→SharpVG.LengthSharpVG.PenModule.PenModule→SharpVG.Pen
- Direction
- SharpVG.PenModule uses SharpVG, so a change to SharpVG can break SharpVG.PenModule, while a change to SharpVG.PenModule can't break SharpVG.
- Position
- Below the diagonal: SharpVG.PenModule uses a module listed above it, which is the healthy direction.
29→1 SharpVG.PointModule uses SharpVG✕
- Connections
- 3 pairs of types, where a type in SharpVG.PointModule uses a type in SharpVG.
- The types involved
SharpVG.PointModule.PointModule→SharpVG.AttributeSharpVG.PointModule.PointModule→SharpVG.LengthSharpVG.PointModule.PointModule→SharpVG.Point
- Direction
- SharpVG.PointModule uses SharpVG, so a change to SharpVG can break SharpVG.PointModule, while a change to SharpVG.PointModule can't break SharpVG.
- Position
- Below the diagonal: SharpVG.PointModule uses a module listed above it, which is the healthy direction.
30→1 SharpVG.Points uses SharpVG✕
- Connections
- 1 pair of types, where a type in SharpVG.Points uses a type in SharpVG.
- The types involved
SharpVG.Points.Points→SharpVG.Point
- Direction
- SharpVG.Points uses SharpVG, so a change to SharpVG can break SharpVG.Points, while a change to SharpVG.Points can't break SharpVG.
- Position
- Below the diagonal: SharpVG.Points uses a module listed above it, which is the healthy direction.
31→1 SharpVG.PolygonModule uses SharpVG✕
- Connections
- 3 pairs of types, where a type in SharpVG.PolygonModule uses a type in SharpVG.
- The types involved
SharpVG.PolygonModule.PolygonModule→SharpVG.PointSharpVG.PolygonModule.PolygonModule→SharpVG.PolygonSharpVG.PolygonModule.PolygonModule→SharpVG.Tag
- Direction
- SharpVG.PolygonModule uses SharpVG, so a change to SharpVG can break SharpVG.PolygonModule, while a change to SharpVG.PolygonModule can't break SharpVG.
- Position
- Below the diagonal: SharpVG.PolygonModule uses a module listed above it, which is the healthy direction.
32→1 SharpVG.PolylineModule uses SharpVG✕
- Connections
- 3 pairs of types, where a type in SharpVG.PolylineModule uses a type in SharpVG.
- The types involved
SharpVG.PolylineModule.PolylineModule→SharpVG.PointSharpVG.PolylineModule.PolylineModule→SharpVG.PolylineSharpVG.PolylineModule.PolylineModule→SharpVG.Tag
- Direction
- SharpVG.PolylineModule uses SharpVG, so a change to SharpVG can break SharpVG.PolylineModule, while a change to SharpVG.PolylineModule can't break SharpVG.
- Position
- Below the diagonal: SharpVG.PolylineModule uses a module listed above it, which is the healthy direction.
33→1 SharpVG.PreserveAspectRatioModule uses SharpVG✕
- Connections
- 4 pairs of types, where a type in SharpVG.PreserveAspectRatioModule uses a type in SharpVG.
- The types involved
SharpVG.PreserveAspectRatioModule.PreserveAspectRatioModule→SharpVG.AspectRatioAlignSharpVG.PreserveAspectRatioModule.PreserveAspectRatioModule→SharpVG.AspectRatioScaleSharpVG.PreserveAspectRatioModule.PreserveAspectRatioModule→SharpVG.AttributeSharpVG.PreserveAspectRatioModule.PreserveAspectRatioModule→SharpVG.PreserveAspectRatio
- Direction
- SharpVG.PreserveAspectRatioModule uses SharpVG, so a change to SharpVG can break SharpVG.PreserveAspectRatioModule, while a change to SharpVG.PreserveAspectRatioModule can't break SharpVG.
- Position
- Below the diagonal: SharpVG.PreserveAspectRatioModule uses a module listed above it, which is the healthy direction.
34→1 SharpVG.RadialGradientModule uses SharpVG✕
- Connections
- 9 pairs of types, where a type in SharpVG.RadialGradientModule uses a type in SharpVG.
- The types involved
SharpVG.RadialGradientModule.RadialGradientModule→SharpVG.FilterUnitsSharpVG.RadialGradientModule.RadialGradientModule→SharpVG.GradientStopSharpVG.RadialGradientModule.RadialGradientModule→SharpVG.HRefSharpVG.RadialGradientModule.RadialGradientModule→SharpVG.LengthSharpVG.RadialGradientModule.RadialGradientModule→SharpVG.PointSharpVG.RadialGradientModule.RadialGradientModule→SharpVG.RadialGradientSharpVG.RadialGradientModule.RadialGradientModule→SharpVG.SpreadMethodSharpVG.RadialGradientModule.RadialGradientModule→SharpVG.TagSharpVG.RadialGradientModule.RadialGradientModule→SharpVG.Transform
- Direction
- SharpVG.RadialGradientModule uses SharpVG, so a change to SharpVG can break SharpVG.RadialGradientModule, while a change to SharpVG.RadialGradientModule can't break SharpVG.
- Position
- Below the diagonal: SharpVG.RadialGradientModule uses a module listed above it, which is the healthy direction.
35→1 SharpVG.RawElementModule uses SharpVG✕
- Connections
- 3 pairs of types, where a type in SharpVG.RawElementModule uses a type in SharpVG.
- The types involved
SharpVG.RawElementModule.RawElementModule→SharpVG.AttributeSharpVG.RawElementModule.RawElementModule→SharpVG.RawContentSharpVG.RawElementModule.RawElementModule→SharpVG.RawElement
- Direction
- SharpVG.RawElementModule uses SharpVG, so a change to SharpVG can break SharpVG.RawElementModule, while a change to SharpVG.RawElementModule can't break SharpVG.
- Position
- Below the diagonal: SharpVG.RawElementModule uses a module listed above it, which is the healthy direction.
36→1 SharpVG.RectModule uses SharpVG✕
- Connections
- 4 pairs of types, where a type in SharpVG.RectModule uses a type in SharpVG.
- The types involved
SharpVG.RectModule.RectModule→SharpVG.AreaSharpVG.RectModule.RectModule→SharpVG.PointSharpVG.RectModule.RectModule→SharpVG.RectSharpVG.RectModule.RectModule→SharpVG.Tag
- Direction
- SharpVG.RectModule uses SharpVG, so a change to SharpVG can break SharpVG.RectModule, while a change to SharpVG.RectModule can't break SharpVG.
- Position
- Below the diagonal: SharpVG.RectModule uses a module listed above it, which is the healthy direction.
37→1 SharpVG.StyleModule uses SharpVG✕
- Connections
- 14 pairs of types, where a type in SharpVG.StyleModule uses a type in SharpVG.
- The types involved
SharpVG.StyleModule.StyleModule→SharpVG.AttributeSharpVG.StyleModule.StyleModule→SharpVG.ColorSharpVG.StyleModule.StyleModule→SharpVG.DisplaySharpVG.StyleModule.StyleModule→SharpVG.FillRuleSharpVG.StyleModule.StyleModule→SharpVG.LengthSharpVG.StyleModule.StyleModule→SharpVG.PaintLayerSharpVG.StyleModule.StyleModule→SharpVG.PenSharpVG.StyleModule.StyleModule→SharpVG.ShapeRenderingSharpVG.StyleModule.StyleModule→SharpVG.StrokeLinecapSharpVG.StyleModule.StyleModule→SharpVG.StrokeLinejoinSharpVG.StyleModule.StyleModule→SharpVG.StyleSharpVG.StyleModule.StyleModule→SharpVG.TagSharpVG.StyleModule.StyleModule→SharpVG.VectorEffectSharpVG.StyleModule.StyleModule→SharpVG.Visibility
- Direction
- SharpVG.StyleModule uses SharpVG, so a change to SharpVG can break SharpVG.StyleModule, while a change to SharpVG.StyleModule can't break SharpVG.
- Position
- Below the diagonal: SharpVG.StyleModule uses a module listed above it, which is the healthy direction.
38→1 SharpVG.StylesModule uses SharpVG✕
- Connections
- 2 pairs of types, where a type in SharpVG.StylesModule uses a type in SharpVG.
- The types involved
SharpVG.StylesModule.StylesModule→SharpVG.StyleSharpVG.StylesModule.StylesModule→SharpVG.Tag
- Direction
- SharpVG.StylesModule uses SharpVG, so a change to SharpVG can break SharpVG.StylesModule, while a change to SharpVG.StylesModule can't break SharpVG.
- Position
- Below the diagonal: SharpVG.StylesModule uses a module listed above it, which is the healthy direction.
39→1 SharpVG.SvgParserHelpers uses SharpVG✕
- Connections
- 14 pairs of types, where a type in SharpVG.SvgParserHelpers uses a type in SharpVG.
- The types involved
SharpVG.SvgParserHelpers.ParseState→SharpVG.ParseModeSharpVG.SvgParserHelpers.ParseState→SharpVG.ParseWarningSharpVG.SvgParserHelpers.SvgParserHelpers→SharpVG.ColorSharpVG.SvgParserHelpers.SvgParserHelpers→SharpVG.ColorsSharpVG.SvgParserHelpers.SvgParserHelpers→SharpVG.ElementSharpVG.SvgParserHelpers.SvgParserHelpers→SharpVG.FilterUnitsSharpVG.SvgParserHelpers.SvgParserHelpers→SharpVG.HRefSharpVG.SvgParserHelpers.SvgParserHelpers→SharpVG.LengthSharpVG.SvgParserHelpers.SvgParserHelpers→SharpVG.ParseModeSharpVG.SvgParserHelpers.SvgParserHelpers→SharpVG.PathSharpVG.SvgParserHelpers.SvgParserHelpers→SharpVG.SpreadMethodSharpVG.SvgParserHelpers.SvgParserHelpers→SharpVG.StyleSharpVG.SvgParserHelpers.SvgParserHelpers→SharpVG.TransformSharpVG.SvgParserHelpers.SvgParserHelpers→SharpVG.ViewBox
- Direction
- SharpVG.SvgParserHelpers uses SharpVG, so a change to SharpVG can break SharpVG.SvgParserHelpers, while a change to SharpVG.SvgParserHelpers can't break SharpVG.
- Position
- Below the diagonal: SharpVG.SvgParserHelpers uses a module listed above it, which is the healthy direction.
40→1 SharpVG.SvgElementParsers uses SharpVG✕
- Connections
- 3 pairs of types, where a type in SharpVG.SvgElementParsers uses a type in SharpVG.
- The types involved
SharpVG.SvgElementParsers.SvgElementParsers→SharpVG.FilterEffectSharpVG.SvgElementParsers.SvgElementParsers→SharpVG.FilterEffectSourceSharpVG.SvgElementParsers.SvgElementParsers→SharpVG.GradientStop
- Direction
- SharpVG.SvgElementParsers uses SharpVG, so a change to SharpVG can break SharpVG.SvgElementParsers, while a change to SharpVG.SvgElementParsers can't break SharpVG.
- Position
- Below the diagonal: SharpVG.SvgElementParsers uses a module listed above it, which is the healthy direction.
40→39 SharpVG.SvgElementParsers uses SharpVG.SvgParserHelpers✕
- Connections
- 1 pair of types, where a type in SharpVG.SvgElementParsers uses a type in SharpVG.SvgParserHelpers.
- The types involved
SharpVG.SvgElementParsers.SvgElementParsers→SharpVG.SvgParserHelpers.ParseState
- Direction
- SharpVG.SvgElementParsers uses SharpVG.SvgParserHelpers, so a change to SharpVG.SvgParserHelpers can break SharpVG.SvgElementParsers, while a change to SharpVG.SvgElementParsers can't break SharpVG.SvgParserHelpers.
- Position
- Below the diagonal: SharpVG.SvgElementParsers 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
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A05:2025 — Injection | 5 | High / Critical |
Roadmap
Top priorities: Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them; Resolve the 1 Deprecated finding(s) in Dependency Hygiene — start with Tests.fsproj; 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.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 1 Deprecated finding(s) in Dependency Hygiene — start with Tests.fsproj. | +2.9 pts | Low | Dependency Hygiene |
| 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. | +3.1 pts | Medium | Architecture documentation |
| Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite. | +1.8 pts | Medium | Documentation (README) |
| Resolve the 4 TooManyFunctions finding(s) in God Classes — start with FilterEffect.fs, Style.fs, Svg.fs. | +0.8 pts | Low | God Classes |
| Resolve the 1 Hotspot finding(s) in Churn × Complexity Hotspots — start with SvgParser.fs. | +0.7 pts | Medium | Churn × Complexity Hotspots |
| Group production code under src/ (or split deliberately, e.g. backend/ + frontend/) so production and tooling code aren't mixed at the root. | +0.9 pts | Medium | Folder & project structure |
| Bring the 5 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with SvgParserHelpers.tryParseCssProperty (cyclomatic 65), SvgElementParsers.parseFilterEffect (cyclomatic 56), Text.ToTag (cyclomatic 31). | +0.6 pts | High | Cyclomatic Complexity |
| Resolve the 1 Scattered collaborators finding(s) in Navigability. | +0.2 pts | Low | Navigability |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 1.4 | Slop | Static Analysis (SAST): High: REDACTED |
| SharpVG/SvgParser.fs | 6.5 | Mixed | Cyclomatic Complexity: SvgParserHelpers.tryParseCssProperty (cyclomatic 65) |
| SharpVG/Svg.fs | 7.4 | Mixed | God Classes: TooManyFunctions: SvgModule |
| SharpVG/Element.fs | 7.4 | Mixed | God Classes: TooManyFunctions: ElementModule |
| SharpVG/Text.fs | 7.8 | Mixed | Cyclomatic Complexity: Text.ToTag (cyclomatic 31) |
| SharpVG/Gradient.fs | 7.8 | Mixed | Code Duplication: Duplicated block (10 lines × 2) |
| SharpVG/FilterEffect.fs | 8.5 | Near-clean | God Classes: TooManyFunctions: FilterEffectModule |
| SharpVG/Style.fs | 8.5 | Near-clean | God Classes: TooManyFunctions: StyleModule |
| SharpVG/Color.fs | 8.5 | Near-clean | Code Coverage: Low coverage: SharpVG/Color.fs |
| Helpers/Helpers.fsproj | 8.5 | Near-clean | Code Coverage: No test project references Helpers |
| Tests/Tests.fsproj | 8.5 | Near-clean | Dependency Hygiene: Deprecated: Xunit |
How the grades work
A definite problem that already costs you something and drags the score down: a missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here tends to cause failures elsewhere.
Likely wrong, but not failing yet. It degrades the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to carry for two years either.
Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.
Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.
Methodology & how to trust this report
Watchdog is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. 38 of 38 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); none rely on LLM judgement. Overall confidence is 0.9 — the weighted average across measured dimensions; it falls as more of the score leans on LLM-assisted judgement and rises when it's fully tool-backed.
What we checked — 38 dimensions across the health lenses
- Can you open the finding? Real findings cite a repo-relative file and line you can open at the cited line — never an absolute scratch path. Here, 43 of 56 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it — Roslyn, git, a scanner, or (for a handful of documentation/naming dimensions) an LLM labelled sampled · advisory — not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Watchdog duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 | ✓ deterministic |
| LLM (sampled · advisory) | Documentation quality, ADR conformance, naming — sampled over a bounded sample; advisory, never a deterministic measurement | — | ◐ LLM · sampled · advisory |
Run transparency — what happened this run
- D15 Churn × Complexity Hotspots — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. A hotspot's complexity is meant to be the worst body its churn actually touched. For SharpVG/SvgParser.fs that could not be established — the complexity reader for the file reports no body extents, or the history carries no per-line attribution — so the row quotes the file's worst body, which the counted changes may never have touched. The churn count is unaffected.
- D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Single-maintainer repository — bus factor is not applicable (5 contributor(s) across 503 commit(s) sampled, automation and bot accounts excluded). One of them holds 99% of the history; the other 4 hold 0.2% each on average, below the 5% at which there is somebody to hand the work to. That is a single maintainer with drive-by contributors, not a team whose knowledge has concentrated — so the bus factor is not applicable and there is nothing here for the owner to act on.
- D21 Naming Consistency — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D21's deterministic naming rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. Until then its declarations carry no naming verdict this run — this says nothing about whether its names are consistent.
- D22 Internal API Consistency — not measured this run — 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 — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
- D30 Dependency Vulnerabilities — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. The scanner produced no output at all, so no dependency was actually scanned. 2 of 3 declared ecosystem(s) (npm,nuget) WERE scanned and every vulnerability they reported is included in this result; osv was not, so this dimension's score covers less than the dependency surface this repository declares, and nothing here is evidence that osv is free of known-vulnerable dependencies.
- D43 Malicious Dependencies — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. The scanner produced no output at all, so no dependency was actually scanned. 1 of 2 declared ecosystem(s) (npm) WERE scanned and every vulnerability they reported is included in this result; osv was not, so this dimension's score covers less than the dependency surface this repository declares, and nothing here is evidence that osv is free of known-vulnerable dependencies.
- AX6 Interface segregation — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is computed over the public interfaces this run's compilations declare, and none was loaded, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- C1 Data Protection — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These personal data controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks personal data controls.
- C2 Access Controls — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These authorization controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks authorization controls.
- C3 Audit Trail — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These audit controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks audit controls.
- C4 Data Retention — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These retention controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks retention controls.
- C5 Data-Subject Rights — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These data-subject rights controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks data-subject rights controls.
- IC1 Incompleteness & stubs — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- M4 Documentation accuracy — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
- P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
- P8 Schema migrations — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads 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 — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These web-security controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks web-security controls.
- X1 Async correctness — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X12 Unreachable branch — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X13 Undrained process stream — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X14 Bypassable address classification — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X15 Unvalidated length from an untrusted reader — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X16 Unfloored truncation loop — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X17 Uncapped recursion over a caller-supplied document — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X18 Disposal-pattern correctness — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X19 Unrestored process-global state — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X2 Cancellation propagation — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X21 Side-effecting pattern guard — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X22 Contradicted release guard — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X24 Document value interpolated into markup unescaped — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X25 Inert configuration knob — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X26 Unsynchronised callback handoff — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X29 Per-element action decided by a fixed element — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X3 Exception handling — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X30 Support guard that admits what it rejects — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X32 Type resolved by simple name across every loaded assembly — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X4 Structured logging — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X5 Nullable reference types — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X6 Hand-rolled structured-format parsing — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and Python, JavaScript/TypeScript, Go, Java/Kotlin/Scala, Ruby, PHP, Rust, Swift, Erlang, Elixir and Dart source only, and no C# was loaded and none of those languages was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X7 Silent fallback defaults — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C#, 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
Watchdog assesses the repository exactly as committed, and only the repository. By design it does not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
- D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
- D8 Code Coverage: Coverage is measured by building and running the test suite inside Watchdog's isolated image — the target repo is never modified, and nothing on your systems runs. So coverage exists only when the suite builds and runs within the inline time budget; one that needs external services, can't build, or exceeds the budget yields no coverage (D8 then degrades to not-measured, not a low score). Line coverage also says nothing about assertion quality.
- D11 Test Reliability: Flakiness is inferred from history/markers — Watchdog runs the suite once (for coverage), not the repeated runs under varied conditions that reveal nondeterminism, so a flaky test never recorded as failing is invisible here.
- D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
- D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
- D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- 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: Onboarding quality is an LLM read of the docs/setup present — it cannot run the onboarding or measure how long a real new joiner takes; the verdict is sampled and advisory.
- 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
5 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was SvgParserHelpers.tryParseCssProperty at 65. A further 6 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 Colors.ToString at 148 — they are counted neither in the figure above nor in this dimension's score. 4 files carry no cyclomatic complexity row at all for this reason — every one of their over-threshold methods was excluded, so the exclusion is disclosed nowhere in the file itself: SharpVG/Color.fs (Colors.ToString at 148), SharpVG/FilterEffect.fs (FilterEffect.ToTag at 22), SharpVG/Path.fs (Path.ToDataString at 21), SharpVG/Animation.fs (Animation.ToTag at 17). 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 5 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with SvgParserHelpers.tryParseCssProperty (cyclomatic 65), SvgElementParsers.parseFilterEffect (cyclomatic 56), Text.ToTag (cyclomatic 31). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 5 together lifts Cyclomatic Complexity from 8.1 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
- Enforce Cyclomatic Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D2 · Cognitive Complexity
7 method(s) exceeded the cognitive complexity threshold of 15; the worst was SvgParserHelpers.tryParseCssProperty at 51.
What to do
- Bring the 2 bodies over 30 down to 30 or less in Cognitive Complexity — start with SvgParserHelpers.tryParseCssProperty (cognitive 51), SvgElementParsers.parseFilterEffect (cognitive 43). — 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 2 together lifts Cognitive Complexity from 8.2 to about 8.7/10, projected with the scoring formula itself and assuming each lands exactly at 30; a cleaner split scores higher.
- Enforce Cognitive Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D3 · God Classes
5 over-large unit(s) detected — types, modules or files that carry too much.
What to do
- Resolve the 4 TooManyFunctions finding(s) in God Classes — start with FilterEffect.fs, Style.fs, Svg.fs. — One of this dimension's main actionable groups (4 warning-level).
- Resolve the 1 FileTooLong finding(s) in God Classes — start with SvgParser.fs. — One of this dimension's main actionable groups (1 warning-level).
- Enforce God Classes in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D4 · Code Duplication
14 duplicated block group(s) detected.
What to do
- Resolve the 2 Duplicated block (11 lines × 2) finding(s) in Code Duplication — start with SvgParser.fs (2). — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 2 Duplicated block (10 lines × 2) finding(s) in Code Duplication — start with Svg.fs, Gradient.fs. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 2 Duplicated block (6 lines × 2) finding(s) in Code Duplication — start with Element.fs, SvgParser.fs. — One of this dimension's main actionable groups (2 warning-level).
- Enforce Code Duplication in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D5 · Coupling
6 projects, 0 dependency cycle(s), 0 unstable depended-on project(s).
D8 · Code Coverage
Line coverage 80.7% — 1 file(s) below 50%.
What to do
- Resolve the 1 Low coverage finding(s) in Code Coverage — start with Color.fs. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 No test project references Helpers finding(s) in Code Coverage — start with Helpers.fsproj. — One of this dimension's main actionable groups (1 warning-level).
- Enforce Code Coverage in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D11 · Test Reliability
0 flaky across 1 measured tier(s). unit: measured (0 flaky).
D12 · Dependency Hygiene
6 outdated, 0 vulnerable, 1 deprecated packages.
What to do
- Resolve the 1 Deprecated finding(s) in Dependency Hygiene — start with Tests.fsproj. — One of this dimension's main actionable groups (1 warning-level).
- Enforce Dependency Hygiene in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D14 · License Compliance
0 of 98 packages use a banned license. ★ DEPTH: this repository's MSBuild projects declare 8 direct `PackageReference`(s), and 90 further package(s) were reached beyond them by closing the graph over nuget.org's own nuspec dependency graph — so a banned licence pulled in only by a dependency's OWN dependencies is inside this verdict. A package whose licence nuget.org could not be asked for is not graded, and version ranges are taken at their lower bound, so this is the closure as that graph states it rather than a restored consumer's exact resolution.
D15 · Churn × Complexity Hotspots
Top hotspots: SharpVG/SvgParser.fs (2×65=130)
What to do
- Resolve the 1 Hotspot finding(s) in Churn × Complexity Hotspots — start with SvgParser.fs. — One of this dimension's main actionable groups (1 warning-level).
D26 · Project Cohesion
0 of 2 build units (MSBuild) flagged as possibly oversized/incoherent.
D27 · Navigability
94 % of calls cross a namespace and 0 % go through an interface, but 9 % of collaborators are co-located — so following a call takes several hops. Baseline: small — navigation cost is tolerated.
What to do
- Resolve the 1 Scattered collaborators finding(s) in Navigability. — One of this dimension's main actionable groups (1 recommendation-level).
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
5 finding(s): 0 critical, 3 high, 2 medium, 0 low. 3 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens.
What to do
- Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2). — One of this dimension's main actionable groups (2 warning-level).
- No action in Static Analysis (SAST) — all 3 REDACTED finding(s) are reported here at file:line but scored by D36 (supply-chain provenance), so none is charged to this dimension. — One of this dimension's main actionable groups (3 issue-level, 0 of them charged here).
D30 · Dependency Vulnerabilities
No known-vulnerable dependencies in the 2 ecosystem(s) that were scanned (npm,nuget). Partial dependency scan: 2 of 3 declared ecosystem(s) were scanned (npm,nuget), and the findings above are real and complete for them. osv was not scanned (osv: the scanner produced no output at all, so no dependency was actually scanned), so this is not the whole dependency surface and the result is reported at reduced confidence.
D34 · Knowledge Freshness
Every significant source file has living knowledge — recently and meaningfully worked. Counted over 18 of the 43 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
D35 · Change Coupling
No strong hidden change-coupling between production files.
D37 · Vulnerability-disclosure Policy
A vulnerability-disclosure policy (SECURITY.md) is published with a reporting contact.
D39 · IL Efficiency
15 of 1191 first-party methods have an oversized IL body.
D43 · Malicious Dependencies
No known-vulnerable dependencies in the 1 ecosystem(s) that were scanned (npm). Partial dependency scan: 1 of 2 declared ecosystem(s) were scanned (npm), and the findings above are real and complete for them. osv was not scanned (osv: the scanner produced no output at all, so no dependency was actually scanned), so this is not the whole dependency surface and the result is reported at reduced confidence.
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 6 platform declaration(s) and 0 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
Frontend & cross-cutting dimensions
AX10 · Code composition
What to do
- The domain core is a small share of production code, but most of the rest matched no layer vocabulary at all — so this is not yet an anemic-domain finding. The namespace/path convention could not place that code, which makes the composition above a statement about the naming, not about the design. Name the layers (or check that the repository's conventions differ from the ones this check knows) before reading a thin domain into it.
AX3 · Project dependency cycles
AX4 · Dependency direction
AX8 · Test isolation
GD1 · Unfinished & placeholder code
M1 · Documentation (README)
What to do
- Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
- Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
M3 · Folder & project structure
- Production code isn't grouped under a src/ folder — it's spread across several top-level directories, so there's no one place that says 'this is the product'.
What to do
- Group production code under src/ (or split deliberately, e.g. backend/ + frontend/) so production and tooling code aren't mixed at the root.
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 612 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.
- `Examples/FableClock/src/App.fsproj` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`. — Examples/FableClock/src/App.fsproj:16
What to do
- Add a SAST step to CI running what this repository's stack ships: `semgrep --config=auto` plus gitleaks for committed secrets (F# is not a CodeQL language and has no language-specific SAST engine) — so a security regression fails the build instead of landing.
- Enable Dependabot/Renovate or a dependency-review gate.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P6 · Release Hygiene
X20 · Mistyped argument guard
X23 · Unguarded diagnostic materialisation
X27 · Collection changed while being enumerated
X28 · Index access outside its own emptiness guard
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 83% | Strong | Solid. |
| Architecture | 96% | Exemplary | Solid. |
| Maturity | 71% | Strong | Solid. |
| Readiness | 68% | Adequate — gated by P3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 98% | Exemplary | Strongest area. |
Unscored — 3 check(s) recorded observations but carry no score
- D36 Supply-chain Provenance & Signing — 1 observation(s) recorded · The CI pipeline builds and tests but publishes no released artifact — no package publish, container push, GitHub release or deployment step. Supply-chain provenance, signing and SBOM attest RELEASED artifacts, so there is nothing to attest here. Add them to the release pipeline when this repo starts shipping artifacts (a published package, a container image, a deployed service or a tagged release). Build integrity and workflow-token hygiene are reported below: they describe what the CI runs and the token it runs with, neither of which is affected by whether the pipeline ships an artifact.
- P12 CI test-gate honesty — 1 observation(s) recorded · Reported, not scored — this card publishes what the CI gate does with the test inventory rather than grading it. The findings above are its output.
- SC1 Supply-chain hygiene — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Not evidenced — 5 control(s) we could not find positive evidence for
- C3 Audit Trail — Not assessed: these audit controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks audit controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- C4 Data Retention — Not assessed: these retention controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks retention controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- C5 Data-Subject Rights — Not assessed: these data-subject rights controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks data-subject rights controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- P4 Deployment & Rollback — not evidenced — no deploy/rollback/approval signal in the repo; absence of evidence is not evidence of a manual release
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 74 check(s) not relevant to this codebase
- AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
- AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
- AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
- AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
- AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
- AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
- AC7 A11y enforcement — No web markup found — accessibility is not applicable to this repository.
- AX1 Captive dependencies — Not applicable: this repository's 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 — ~5229 lines of test source are present (.fs) but no test cases reached the test census for this repository — no test root we could resolve declared them, or the files we read declare no cases in a test framework we recognise — so skipped/assertion-free tests couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
- D16 Bus Factor — single-maintainer repository — bus factor is not applicable
- D17 Explicit Debt — the C# workspace loaded 0 projects, so explicit-debt density could not be measured
- D18 Solution Shape — D18 scores the shape of a C#/VB .NET solution; this repository's .NET projects are all F# (.fsproj), which the C#/VB workspace does not load, so the dimension does not apply.
- D19 Documentation Quality — No runnable or published unit to look for an example in, and no multi-project root README to look for a map in; the other documentation kinds are withheld (see the gaps), so documentation quality is not applicable here.
- D20 ADR Quality — N/A — ADRs are expected on deployable products with a user-facing host, not consumed libraries; no ADR log is required here.
- D21 Naming Consistency — Naming consistency is measured on C# and TypeScript only; F# not measured.
- D22 Internal API Consistency — No intentionally-exposed public API to evaluate for consistency.
- D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D24 Comment Value — D24 reads C# and Visual Basic 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.
- 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) — No production classes were analyzable, so cohesion (LCOM4) was not measured (the solution likely failed to load or has no production code).
- D7 Architectural Integrity — no checkable ADRs and no dependency cycles — architectural integrity not assessed
- D9 Test Distribution — Test source is present (.fs) but no test cases reached the test census for this repository — no test root we could resolve declared them, or the files we read declare no cases in a test framework we recognise — so its unit/integration/BDD/E2E split couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
- DM1 Domain Modelling — not scored — this repository shows only 1 of the 3 signals this lens looks for (53 value object(s))
- ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
- ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- P2 Observability — This repository's F# source (2 module(s), 43 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 — no coverage report found on disk — produce a coverage report in a standard format (Cobertura — `dotnet test --collect:"XPlat Code Coverage"` with a `coverlet.collector` PackageReference) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures, or wire coverage collection into CI, to enable this cross-layer check
- 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 applicable: allocation awareness is rated where code engineers for it — at least 400 production lines that ship benchmarks or already use allocation-aware idioms (8 or more). This repository's F# code has 5,790 production line(s), 0 such use(s) and no benchmarks, so there is no allocation work to rate. The card is reward-only: its absence costs nothing.
- PF3 Async & latency hygiene — Not applicable: this repository declares no async functions, so there is no asynchronous code for a blocking call to stall.
- 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
- X21 Side-effecting pattern guard — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X22 Contradicted release guard — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X24 Document value interpolated into markup unescaped — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X25 Inert configuration knob — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X26 Unsynchronised callback handoff — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X29 Per-element action decided by a fixed element — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X3 Exception handling — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X30 Support guard that admits what it rejects — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X32 Type resolved by simple name across every loaded assembly — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X4 Structured logging — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X5 Nullable reference types — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X6 Hand-rolled structured-format parsing — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X7 Silent fallback defaults — 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
- REDACTED
Serious — 40 finding(s)
- TooManyFunctions: FilterEffectModule SharpVG/FilterEffect.fs:329
- TooManyFunctions: StyleModule SharpVG/Style.fs:178
- TooManyFunctions: SvgModule SharpVG/Svg.fs:45
- TooManyFunctions: ElementModule SharpVG/Element.fs:58
- REDACTED
- REDACTED
- Duplicated block (11 lines × 2) SharpVG/SvgParser.fs:623
- Duplicated block (11 lines × 2) SharpVG/SvgParser.fs:855
- Duplicated block (10 lines × 2) SharpVG/Svg.fs:265
- Duplicated block (10 lines × 2) SharpVG/Gradient.fs:40
- Duplicated block (6 lines × 2) SharpVG/Element.fs:64
- Duplicated block (6 lines × 2) SharpVG/SvgParser.fs:331
- Duplicated block (5 lines × 2) SharpVG/SvgParser.fs:592
- Duplicated block (5 lines × 2) SharpVG/Gradient.fs:55
- SvgParserHelpers.tryParseCssProperty (cyclomatic 65) SharpVG/SvgParser.fs:205
- SvgElementParsers.parseFilterEffect (cyclomatic 56) SharpVG/SvgParser.fs:970
- Text.ToTag (cyclomatic 31) SharpVG/Text.fs:189
- SvgParserHelpers.parsePathData (cyclomatic 23) SharpVG/SvgParser.fs:488
- SvgParserHelpers.tryParseColor (cyclomatic 16) SharpVG/SvgParser.fs:165
- Deprecated: Xunit Tests/Tests.fsproj:68
- Hotspot: SharpVG/SvgParser.fs SharpVG/SvgParser.fs:205
- SvgParserHelpers.tryParseCssProperty (cognitive 51) SharpVG/SvgParser.fs:205
- SvgElementParsers.parseFilterEffect (cognitive 43) SharpVG/SvgParser.fs:970
- SvgParserHelpers.parsePathData (cognitive 28) SharpVG/SvgParser.fs:488
- SvgParserHelpers.tryParseColor (cognitive 24) SharpVG/SvgParser.fs:165
- SvgHtmlParser.extractSvgStrings (cognitive 21) SharpVG/SvgParser.fs:1282
- Text.ToTag (cognitive 18) SharpVG/Text.fs:189
- SvgRootParser.applySheetToElement (cognitive 17) SharpVG/SvgParser.fs:1170
- FileTooLong: SharpVG/SvgParser.fs SharpVG/SvgParser.fs
- REDACTED
- Duplicated block (10 lines × 3) SharpVG/SvgParser.fs:858
- Duplicated block (8–9 lines × 4) SharpVG/SvgParser.fs:862
- Duplicated block (9 lines × 2) SharpVG/Element.fs:78
- Duplicated block (7 lines × 4) SharpVG/SvgParser.fs:836
- Duplicated block (7 lines × 2) SharpVG/Svg.fs:257
- Duplicated block (5 lines × 5) SharpVG/SvgParser.fs:838
- Low coverage: SharpVG/Color.fs SharpVG/Color.fs:1
- No test project references Helpers Helpers/Helpers.fsproj
- Coverage collected but not gated
- NuGet dependencies are not locked
Minor — 7 finding(s)
- Scattered collaborators
- REDACTED
- IL efficiency: 15 authored method(s) exceed the IL budget SharpVG/SvgParser.fs:206
- No ADRs
- No src/ separation
- No SAST
- No dependency-update automation Examples/FableClock/src/App.fsproj:16
Minor — 6 finding(s)
- Outdated: FSharp.Core
- Outdated: coverlet.collector
- Outdated: FsCheck
- Outdated: FsCheck.Xunit
- Outdated: Microsoft.NET.Test.Sdk
- Outdated: Xunit.Runner.VisualStudio
Appendix B — Reproduction & audit trail
| Dimension | Tool | Version | Command | Findings | Raw output |
|---|---|---|---|---|---|
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-cdb8f389a64e4f14858e5cba82f3e346/history.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-cdb8f389a64e4f14858e5cba82f3e346/tree.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-tree.json |
| D29 · Static Analysis (SAST) | semgrep | — | semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/watchdog-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt . | 5 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | dotnet | — | dotnet list SharpVG.sln package --vulnerable --include-transitive --format json | 0 | artifacts/raw/dotnet-vulnerable.json |
| D30 · Dependency Vulnerabilities | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . | 0 | — |
| D31 · IaC & Container Security | trivy | — | trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan. | 0 | — |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. | 0 | — |
| 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 . | 0 | — |
| D43 · Malicious Dependencies | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . --skip-db-update | 0 | artifacts/raw/trivy-fs.json |