Executive summary
goswinr/Fesh falls short of our standard for a preview release because its Testing dimensions are rated Critical, and the project has no automated tests. It scores 59 out of 100, which alone would earn Adequate, but it is rated Weak: a rating can't sit more than one step above its weakest group.
Production Readiness, at 40, is the weakest lens and counts most in the score. The best first step is adding automated tests, worth about 17 points. Recording design decisions comes next, worth about 6 points. Raising Production Readiness to 62 would lift the score to about 70.
The project has no automated tests, so a change can break it without warning. Adding automated tests would close this risk.
The product code is 15,336 lines, about €16,000 to rebuild.
If Production Readiness rose from 40 to 62, the lowest score rated Strong, the score would rise from 59 to about 70.
Rebuild cost: about €16,000 · Estimate
| Cost to rebuild | €5,400 to €27,000, for 91 to 287 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 | ×0.8 at a score of 59. 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: 15,336 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: which parts of the code depend on which
| uses → | 1 CompileScript | 2 DocString | 3 DotnetSdk | 4 Editor.AutoFixErrors | 5 Editor.CodeLineTools | 6 Editor.Commenting | 7 Editor.CursorBehavior | 8 Editor.Doc | 9 Editor.DocChangeCompletion | 10 Editor.Keys | 11 Model | 12 Model.AvalonEditTypeExtensions | 13 Util.AutoOpenDateTime | 14 Util.Pen | 15 XmlParser | 16 Config | 17 Editor.AlignText | 18 Editor.ErrorUtil | 19 Editor.FsCheckerUtil | 20 Editor.KeyboardShortcuts | 21 Editor.Selection | 22 Editor.SelectionForEval | 23 Editor.UtilCompletion | 24 Views.MenuUtil | 25 Config.Folders | 26 Editor | 27 Editor.SwapLines | 28 Editor.DocChangeUtil | 29 Editor.GitClone | 30 Editor.MagicScrollbar | 31 Editor.MaybeShow | 32 Editor.ParseBrackets | 33 Editor.Redrawing | 34 Editor.SourceLink | 35 Views | 36 Fesh | 37 App | 38 Initialize | 39 Theme | 40 ThemeChrome |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 CompileScript | ||||||||||||||||||||||||||||||||||||||||
| 2 DocString | ||||||||||||||||||||||||||||||||||||||||
| 3 DotnetSdk | ||||||||||||||||||||||||||||||||||||||||
| 4 Editor.AutoFixErrors | ||||||||||||||||||||||||||||||||||||||||
| 5 Editor.CodeLineTools | ||||||||||||||||||||||||||||||||||||||||
| 6 Editor.Commenting | ||||||||||||||||||||||||||||||||||||||||
| 7 Editor.CursorBehavior | ||||||||||||||||||||||||||||||||||||||||
| 8 Editor.Doc | ||||||||||||||||||||||||||||||||||||||||
| 9 Editor.DocChangeCompletion | ||||||||||||||||||||||||||||||||||||||||
| 10 Editor.Keys | ||||||||||||||||||||||||||||||||||||||||
| 11 Model | ||||||||||||||||||||||||||||||||||||||||
| 12 Model.AvalonEditTypeExtensions | ||||||||||||||||||||||||||||||||||||||||
| 13 Util.AutoOpenDateTime | ||||||||||||||||||||||||||||||||||||||||
| 14 Util.Pen | ||||||||||||||||||||||||||||||||||||||||
| 15 XmlParser | ||||||||||||||||||||||||||||||||||||||||
| 16 Config | 2 | 1 | ||||||||||||||||||||||||||||||||||||||
| 17 Editor.AlignText | 1 | |||||||||||||||||||||||||||||||||||||||
| 18 Editor.ErrorUtil | 2 | |||||||||||||||||||||||||||||||||||||||
| 19 Editor.FsCheckerUtil | 1 | |||||||||||||||||||||||||||||||||||||||
| 20 Editor.KeyboardShortcuts | 1 | |||||||||||||||||||||||||||||||||||||||
| 21 Editor.Selection | 1 | |||||||||||||||||||||||||||||||||||||||
| 22 Editor.SelectionForEval | 1 | |||||||||||||||||||||||||||||||||||||||
| 23 Editor.UtilCompletion | 1 | |||||||||||||||||||||||||||||||||||||||
| 24 Views.MenuUtil | 1 | |||||||||||||||||||||||||||||||||||||||
| 25 Config.Folders | 1 | |||||||||||||||||||||||||||||||||||||||
| 26 Editor | 1 | 4 | 2 | 2 | 3 | |||||||||||||||||||||||||||||||||||
| 27 Editor.SwapLines | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 28 Editor.DocChangeUtil | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 29 Editor.GitClone | 1 | |||||||||||||||||||||||||||||||||||||||
| 30 Editor.MagicScrollbar | 2 | |||||||||||||||||||||||||||||||||||||||
| 31 Editor.MaybeShow | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 32 Editor.ParseBrackets | 2 | |||||||||||||||||||||||||||||||||||||||
| 33 Editor.Redrawing | 8 | |||||||||||||||||||||||||||||||||||||||
| 34 Editor.SourceLink | 2 | |||||||||||||||||||||||||||||||||||||||
| 35 Views | 6 | 5 | 5 | |||||||||||||||||||||||||||||||||||||
| 36 Fesh | 2 | 2 | 2 | 1 | ||||||||||||||||||||||||||||||||||||
| 37 App | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 38 Initialize | 1 | |||||||||||||||||||||||||||||||||||||||
| 39 Theme | 2 | |||||||||||||||||||||||||||||||||||||||
| 40 ThemeChrome | 2 |
16→11 Config uses Model✕
- Connections
- 2 pairs of types, where a type in Config uses a type in Model.
- The types involved
Fesh.Config.Config→Fesh.Model.IFeshLogFesh.Config.FoldingStatus→Fesh.Model.FilePath
- Direction
- Config uses Model, so a change to Model can break Config, while a change to Config can't break Model.
- Position
- Below the diagonal: Config uses a module listed above it, which is the healthy direction.
16→13 Config uses Util.AutoOpenDateTime✕
- Connections
- 1 pair of types, where a type in Config uses a type in Util.AutoOpenDateTime.
- The types involved
Fesh.Config.UsedFile→Fesh.Util.AutoOpenDateTime.DateTime
- Direction
- Config uses Util.AutoOpenDateTime, so a change to Util.AutoOpenDateTime can break Config, while a change to Config can't break Util.AutoOpenDateTime.
- Position
- Below the diagonal: Config uses a module listed above it, which is the healthy direction.
17→11 Editor.AlignText uses Model✕
- Connections
- 1 pair of types, where a type in Editor.AlignText uses a type in Model.
- The types involved
Fesh.Editor.AlignText.AlignText→Fesh.Model.IEditor
- Direction
- Editor.AlignText uses Model, so a change to Model can break Editor.AlignText, while a change to Editor.AlignText can't break Model.
- Position
- Below the diagonal: Editor.AlignText uses a module listed above it, which is the healthy direction.
18→11 Editor.ErrorUtil uses Model✕
- Connections
- 2 pairs of types, where a type in Editor.ErrorUtil uses a type in Model.
- The types involved
Fesh.Editor.ErrorUtil.ErrorUtil→Fesh.Model.ErrorsBySeverityFesh.Editor.ErrorUtil.ErrorUtil→Fesh.Model.IEditor
- Direction
- Editor.ErrorUtil uses Model, so a change to Model can break Editor.ErrorUtil, while a change to Editor.ErrorUtil can't break Model.
- Position
- Below the diagonal: Editor.ErrorUtil uses a module listed above it, which is the healthy direction.
19→11 Editor.FsCheckerUtil uses Model✕
- Connections
- 1 pair of types, where a type in Editor.FsCheckerUtil uses a type in Model.
- The types involved
Fesh.Editor.FsCheckerUtil.FsCheckerUtil→Fesh.Model.FilePath
- Direction
- Editor.FsCheckerUtil uses Model, so a change to Model can break Editor.FsCheckerUtil, while a change to Editor.FsCheckerUtil can't break Model.
- Position
- Below the diagonal: Editor.FsCheckerUtil uses a module listed above it, which is the healthy direction.
20→10 Editor.KeyboardShortcuts uses Editor.Keys✕
- Connections
- 1 pair of types, where a type in Editor.KeyboardShortcuts uses a type in Editor.Keys.
- The types involved
Fesh.Editor.KeyboardShortcuts.KeyboardShortcuts→Fesh.Editor.Keys.AltKeyCombo
- Direction
- Editor.KeyboardShortcuts uses Editor.Keys, so a change to Editor.Keys can break Editor.KeyboardShortcuts, while a change to Editor.KeyboardShortcuts can't break Editor.Keys.
- Position
- Below the diagonal: Editor.KeyboardShortcuts uses a module listed above it, which is the healthy direction.
21→11 Editor.Selection uses Model✕
- Connections
- 1 pair of types, where a type in Editor.Selection uses a type in Model.
- The types involved
Fesh.Editor.Selection.Selection→Fesh.Model.CodeSegment
- Direction
- Editor.Selection uses Model, so a change to Model can break Editor.Selection, while a change to Editor.Selection can't break Model.
- Position
- Below the diagonal: Editor.Selection uses a module listed above it, which is the healthy direction.
22→11 Editor.SelectionForEval uses Model✕
- Connections
- 1 pair of types, where a type in Editor.SelectionForEval uses a type in Model.
- The types involved
Fesh.Editor.SelectionForEval.SelectionForEval→Fesh.Model.CodeSegment
- Direction
- Editor.SelectionForEval uses Model, so a change to Model can break Editor.SelectionForEval, while a change to Editor.SelectionForEval can't break Model.
- Position
- Below the diagonal: Editor.SelectionForEval uses a module listed above it, which is the healthy direction.
23→12 Editor.UtilCompletion uses Model.AvalonEditTypeExtensions✕
- Connections
- 1 pair of types, where a type in Editor.UtilCompletion uses a type in Model.AvalonEditTypeExtensions.
- The types involved
Fesh.Editor.UtilCompletion.UtilCompletion→Fesh.Model.AvalonEditTypeExtensions.ISegment
- Direction
- Editor.UtilCompletion uses Model.AvalonEditTypeExtensions, so a change to Model.AvalonEditTypeExtensions can break Editor.UtilCompletion, while a change to Editor.UtilCompletion can't break Model.AvalonEditTypeExtensions.
- Position
- Below the diagonal: Editor.UtilCompletion uses a module listed above it, which is the healthy direction.
24→11 Views.MenuUtil uses Model✕
- Connections
- 1 pair of types, where a type in Views.MenuUtil uses a type in Model.
- The types involved
Fesh.Views.MenuUtil.MenuUtil→Fesh.Model.CommandInfo
- Direction
- Views.MenuUtil uses Model, so a change to Model can break Views.MenuUtil, while a change to Views.MenuUtil can't break Model.
- Position
- Below the diagonal: Views.MenuUtil uses a module listed above it, which is the healthy direction.
25→16 Config.Folders uses Config✕
- Connections
- 1 pair of types, where a type in Config.Folders uses a type in Config.
- The types involved
Fesh.Config.Folders.Folders→Fesh.Config.HostedStartUpData
- Direction
- Config.Folders uses Config, so a change to Config can break Config.Folders, while a change to Config.Folders can't break Config.
- Position
- Below the diagonal: Config.Folders uses a module listed above it, which is the healthy direction.
26→5 Editor uses Editor.CodeLineTools✕
- Connections
- 1 pair of types, where a type in Editor uses a type in Editor.CodeLineTools.
- The types involved
Fesh.Editor.FoldFrom→Fesh.Editor.CodeLineTools.LineInfo
- Direction
- Editor uses Editor.CodeLineTools, so a change to Editor.CodeLineTools can break Editor, while a change to Editor can't break Editor.CodeLineTools.
- Position
- Below the diagonal: Editor uses a module listed above it, which is the healthy direction.
26→11 Editor uses Model✕
- Connections
- 4 pairs of types, where a type in Editor uses a type in Model.
- The types involved
Fesh.Editor.Editor→Fesh.Model.FilePathFesh.Editor.Editor→Fesh.Model.IEditorFesh.Editor.EvaluationTracker→Fesh.Model.EvalRequestFesh.Editor.PositionInCodeEx→Fesh.Model.PositionInCode
- Direction
- Editor uses Model, so a change to Model can break Editor, while a change to Editor can't break Model.
- Position
- Below the diagonal: Editor uses a module listed above it, which is the healthy direction.
26→12 Editor uses Model.AvalonEditTypeExtensions✕
- Connections
- 2 pairs of types, where a type in Editor uses a type in Model.AvalonEditTypeExtensions.
- The types involved
Fesh.Editor.RedrawSegment→Fesh.Model.AvalonEditTypeExtensions.ISegmentFesh.Editor.SegmentToMark→Fesh.Model.AvalonEditTypeExtensions.ISegment
- Direction
- Editor uses Model.AvalonEditTypeExtensions, so a change to Model.AvalonEditTypeExtensions can break Editor, while a change to Editor can't break Model.AvalonEditTypeExtensions.
- Position
- Below the diagonal: Editor uses a module listed above it, which is the healthy direction.
26→15 Editor uses XmlParser✕
- Connections
- 2 pairs of types, where a type in Editor uses a type in XmlParser.
- The types involved
Fesh.Editor.TypeInfo→Fesh.XmlParser.ChildFesh.Editor.TypeInfo→Fesh.XmlParser.Node
- Direction
- Editor uses XmlParser, so a change to XmlParser can break Editor, while a change to Editor can't break XmlParser.
- Position
- Below the diagonal: Editor uses a module listed above it, which is the healthy direction.
26→16 Editor uses Config✕
- Connections
- 3 pairs of types, where a type in Editor uses a type in Config.
- The types involved
Fesh.Editor.Editor→Fesh.Config.ConfigFesh.Editor.EvaluationTracker→Fesh.Config.ConfigFesh.Editor.InteractionState→Fesh.Config.Config
- Direction
- Editor uses Config, so a change to Config can break Editor, while a change to Editor can't break Config.
- Position
- Below the diagonal: Editor uses a module listed above it, which is the healthy direction.
27→11 Editor.SwapLines uses Model✕
- Connections
- 1 pair of types, where a type in Editor.SwapLines uses a type in Model.
- The types involved
Fesh.Editor.SwapLines.SwapLines→Fesh.Model.IEditor
- Direction
- Editor.SwapLines uses Model, so a change to Model can break Editor.SwapLines, while a change to Editor.SwapLines can't break Model.
- Position
- Below the diagonal: Editor.SwapLines uses a module listed above it, which is the healthy direction.
27→21 Editor.SwapLines uses Editor.Selection✕
- Connections
- 1 pair of types, where a type in Editor.SwapLines uses a type in Editor.Selection.
- The types involved
Fesh.Editor.SwapLines.SwapPair→Fesh.Editor.Selection.Seg
- Direction
- Editor.SwapLines uses Editor.Selection, so a change to Editor.Selection can break Editor.SwapLines, while a change to Editor.SwapLines can't break Editor.Selection.
- Position
- Below the diagonal: Editor.SwapLines uses a module listed above it, which is the healthy direction.
28→11 Editor.DocChangeUtil uses Model✕
- Connections
- 1 pair of types, where a type in Editor.DocChangeUtil uses a type in Model.
- The types involved
Fesh.Editor.DocChangeUtil.DocChangeUtil→Fesh.Model.PositionInCode
- Direction
- Editor.DocChangeUtil uses Model, so a change to Model can break Editor.DocChangeUtil, while a change to Editor.DocChangeUtil can't break Model.
- Position
- Below the diagonal: Editor.DocChangeUtil uses a module listed above it, which is the healthy direction.
28→26 Editor.DocChangeUtil uses Editor✕
- Connections
- 1 pair of types, where a type in Editor.DocChangeUtil uses a type in Editor.
- The types involved
Fesh.Editor.DocChangeUtil.DocChangeUtil→Fesh.Editor.Shift
- Direction
- Editor.DocChangeUtil uses Editor, so a change to Editor can break Editor.DocChangeUtil, while a change to Editor.DocChangeUtil can't break Editor.
- Position
- Below the diagonal: Editor.DocChangeUtil uses a module listed above it, which is the healthy direction.
29→26 Editor.GitClone uses Editor✕
- Connections
- 1 pair of types, where a type in Editor.GitClone uses a type in Editor.
- The types involved
Fesh.Editor.GitClone.GitClone→Fesh.Editor.GitHubFile
- Direction
- Editor.GitClone uses Editor, so a change to Editor can break Editor.GitClone, while a change to Editor.GitClone can't break Editor.
- Position
- Below the diagonal: Editor.GitClone uses a module listed above it, which is the healthy direction.
30→26 Editor.MagicScrollbar uses Editor✕
- Connections
- 2 pairs of types, where a type in Editor.MagicScrollbar uses a type in Editor.
- The types involved
Fesh.Editor.MagicScrollbar.ScrollBarEnhancer→Fesh.Editor.ErrorHighlighterFesh.Editor.MagicScrollbar.ScrollbarAdorner→Fesh.Editor.ErrorHighlighter
- Direction
- Editor.MagicScrollbar uses Editor, so a change to Editor can break Editor.MagicScrollbar, while a change to Editor.MagicScrollbar can't break Editor.
- Position
- Below the diagonal: Editor.MagicScrollbar uses a module listed above it, which is the healthy direction.
31→11 Editor.MaybeShow uses Model✕
- Connections
- 1 pair of types, where a type in Editor.MaybeShow uses a type in Model.
- The types involved
Fesh.Editor.MaybeShow.MaybeShow→Fesh.Model.PositionInCode
- Direction
- Editor.MaybeShow uses Model, so a change to Model can break Editor.MaybeShow, while a change to Editor.MaybeShow can't break Model.
- Position
- Below the diagonal: Editor.MaybeShow uses a module listed above it, which is the healthy direction.
31→26 Editor.MaybeShow uses Editor✕
- Connections
- 1 pair of types, where a type in Editor.MaybeShow uses a type in Editor.
- The types involved
Fesh.Editor.MaybeShow.MaybeShow→Fesh.Editor.ShowAutocomplete
- Direction
- Editor.MaybeShow uses Editor, so a change to Editor can break Editor.MaybeShow, while a change to Editor.MaybeShow can't break Editor.
- Position
- Below the diagonal: Editor.MaybeShow uses a module listed above it, which is the healthy direction.
32→26 Editor.ParseBrackets uses Editor✕
- Connections
- 2 pairs of types, where a type in Editor.ParseBrackets uses a type in Editor.
- The types involved
Fesh.Editor.ParseBrackets.Bracket→Fesh.Editor.BracketKindFesh.Editor.ParseBrackets.BracketPair→Fesh.Editor.BracketKind
- Direction
- Editor.ParseBrackets uses Editor, so a change to Editor can break Editor.ParseBrackets, while a change to Editor.ParseBrackets can't break Editor.
- Position
- Below the diagonal: Editor.ParseBrackets uses a module listed above it, which is the healthy direction.
33→26 Editor.Redrawing uses Editor✕
- Connections
- 8 pairs of types, where a type in Editor.Redrawing uses a type in Editor.
- The types involved
Fesh.Editor.Redrawing.DrawingServices→Fesh.Editor.BracketHighlighterFesh.Editor.Redrawing.DrawingServices→Fesh.Editor.CompletionsFesh.Editor.Redrawing.DrawingServices→Fesh.Editor.ErrorHighlighterFesh.Editor.Redrawing.DrawingServices→Fesh.Editor.EvaluationTrackerFesh.Editor.Redrawing.DrawingServices→Fesh.Editor.FoldingsFesh.Editor.Redrawing.DrawingServices→Fesh.Editor.SelectionHighlighterFesh.Editor.Redrawing.DrawingServices→Fesh.Editor.SemanticHighlighterFesh.Editor.Redrawing.EventCombiner→Fesh.Editor.InteractionState
- Direction
- Editor.Redrawing uses Editor, so a change to Editor can break Editor.Redrawing, while a change to Editor.Redrawing can't break Editor.
- Position
- Below the diagonal: Editor.Redrawing uses a module listed above it, which is the healthy direction.
34→26 Editor.SourceLink uses Editor✕
- Connections
- 2 pairs of types, where a type in Editor.SourceLink uses a type in Editor.
- The types involved
Fesh.Editor.SourceLink.SourceLink→Fesh.Editor.SourceLinkFileFesh.Editor.SourceLink.SourceLink→Fesh.Editor.SourceLinkLookup
- Direction
- Editor.SourceLink uses Editor, so a change to Editor can break Editor.SourceLink, while a change to Editor.SourceLink can't break Editor.
- Position
- Below the diagonal: Editor.SourceLink uses a module listed above it, which is the healthy direction.
35→11 Views uses Model✕
- Connections
- 6 pairs of types, where a type in Views uses a type in Model.
- The types involved
Fesh.Views.CheckerStatus→Fesh.Model.FileCheckStateFesh.Views.CheckerStatus→Fesh.Model.IEditorFesh.Views.FeshWindow→Fesh.Model.FilePathFesh.Views.Log→Fesh.Model.FilePathFesh.Views.Log→Fesh.Model.IFeshLogFesh.Views.Tabs→Fesh.Model.FilePath
- Direction
- Views uses Model, so a change to Model can break Views, while a change to Views can't break Model.
- Position
- Below the diagonal: Views uses a module listed above it, which is the healthy direction.
35→16 Views uses Config✕
- Connections
- 5 pairs of types, where a type in Views uses a type in Config.
- The types involved
Fesh.Views.FeshWindow→Fesh.Config.ConfigFesh.Views.Log→Fesh.Config.ConfigFesh.Views.Menu→Fesh.Config.ConfigFesh.Views.Tabs→Fesh.Config.ConfigFesh.Views.TabsAndLog→Fesh.Config.Config
- Direction
- Views uses Config, so a change to Config can break Views, while a change to Views can't break Config.
- Position
- Below the diagonal: Views uses a module listed above it, which is the healthy direction.
35→26 Views uses Editor✕
- Connections
- 5 pairs of types, where a type in Views uses a type in Editor.
- The types involved
Fesh.Views.CheckerStatus→Fesh.Editor.EditorFesh.Views.Commands→Fesh.Editor.DefinitionFesh.Views.Commands→Fesh.Editor.SourceLinkFileFesh.Views.FileChangeTracker→Fesh.Editor.EditorFesh.Views.Tab→Fesh.Editor.Editor
- Direction
- Views uses Editor, so a change to Editor can break Views, while a change to Views can't break Editor.
- Position
- Below the diagonal: Views uses a module listed above it, which is the healthy direction.
36→11 Fesh uses Model✕
- Connections
- 2 pairs of types, where a type in Fesh uses a type in Model.
- The types involved
Fesh.Fsi→Fesh.Model.EvalDataFesh.Fsi→Fesh.Model.EvalRequest
- Direction
- Fesh uses Model, so a change to Model can break Fesh, while a change to Fesh can't break Model.
- Position
- Below the diagonal: Fesh uses a module listed above it, which is the healthy direction.
36→14 Fesh uses Util.Pen✕
- Connections
- 2 pairs of types, where a type in Fesh uses a type in Util.Pen.
- The types involved
Fesh.EditorColors→Fesh.Util.Pen.PenFesh.ErrorColors→Fesh.Util.Pen.Pen
- Direction
- Fesh uses Util.Pen, so a change to Util.Pen can break Fesh, while a change to Fesh can't break Util.Pen.
- Position
- Below the diagonal: Fesh uses a module listed above it, which is the healthy direction.
36→16 Fesh uses Config✕
- Connections
- 2 pairs of types, where a type in Fesh uses a type in Config.
- The types involved
Fesh.Fesh→Fesh.Config.ConfigFesh.Fsi→Fesh.Config.Config
- Direction
- Fesh uses Config, so a change to Config can break Fesh, while a change to Fesh can't break Config.
- Position
- Below the diagonal: Fesh uses a module listed above it, which is the healthy direction.
36→35 Fesh uses Views✕
- Connections
- 1 pair of types, where a type in Fesh uses a type in Views.
- The types involved
Fesh.Fesh→Fesh.Views.Log
- Direction
- Fesh uses Views, so a change to Views can break Fesh, while a change to Fesh can't break Views.
- Position
- Below the diagonal: Fesh uses a module listed above it, which is the healthy direction.
37→16 App uses Config✕
- Connections
- 1 pair of types, where a type in App uses a type in Config.
- The types involved
Fesh.App.App→Fesh.Config.HostedStartUpData
- Direction
- App uses Config, so a change to Config can break App, while a change to App can't break Config.
- Position
- Below the diagonal: App uses a module listed above it, which is the healthy direction.
37→36 App uses Fesh✕
- Connections
- 1 pair of types, where a type in App uses a type in Fesh.
- The types involved
Fesh.App.App→Fesh.Fesh
- Direction
- App uses Fesh, so a change to Fesh can break App, while a change to App can't break Fesh.
- Position
- Below the diagonal: App uses a module listed above it, which is the healthy direction.
38→36 Initialize uses Fesh✕
- Connections
- 1 pair of types, where a type in Initialize uses a type in Fesh.
- The types involved
Fesh.Initialize.Initialize→Fesh.Fesh
- Direction
- Initialize uses Fesh, so a change to Fesh can break Initialize, while a change to Initialize can't break Fesh.
- Position
- Below the diagonal: Initialize uses a module listed above it, which is the healthy direction.
39→36 Theme uses Fesh✕
- Connections
- 2 pairs of types, where a type in Theme uses a type in Fesh.
- The types involved
Fesh.Theme.XshdColors→Fesh.EditorColorsFesh.Theme.XshdColors→Fesh.LogWindowColors
- Direction
- Theme uses Fesh, so a change to Fesh can break Theme, while a change to Theme can't break Fesh.
- Position
- Below the diagonal: Theme uses a module listed above it, which is the healthy direction.
40→36 ThemeChrome uses Fesh✕
- Connections
- 2 pairs of types, where a type in ThemeChrome uses a type in Fesh.
- The types involved
Fesh.ThemeChrome.ThemeChrome→Fesh.ChromeColorsFesh.ThemeChrome.ThemeChrome→Fesh.EditorColors
- Direction
- ThemeChrome uses Fesh, so a change to Fesh can break ThemeChrome, while a change to ThemeChrome can't break Fesh.
- Position
- Below the diagonal: ThemeChrome uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A03:2025 — Software Supply Chain Failures | 2 | Medium |
Roadmap
Top priorities: Resolve the 1 No automated tests finding(s) in Code Coverage; Resolve the 1 No tests found finding(s) in Test Distribution; Resolve the 1 No ADRs found finding(s) in ADR Quality.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 1 No tests found finding(s) in Test Distribution. | +17.3 pts | Low | Test Distribution |
| Resolve the 1 No ADRs found finding(s) in ADR Quality. | +5.6 pts | Low | ADR Quality |
| Resolve the 1 No automated tests finding(s) in Code Coverage. | +17.3 pts | High | Code Coverage |
| Write a diagnostic trail the user can hand back with a bug report: a log file under the platform's per-user data directory, switchable with a `--verbose`/`--debug` flag. Start with the error paths that emit nothing — a discarded error is the failure the user cannot describe and you cannot reproduce. | +5.3 pts | Medium | Observability |
| Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them. | +5.3 pts | Medium | Architecture documentation |
| Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite. | +2.1 pts | Medium | Documentation (README) |
| Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion. | +0.9 pts | Low | Project Cohesion |
| Run the test suite in CI via an explicit runner step (`dotnet test` for the toolchain this pipeline already uses) and gate merges on it. | +0.6 pts | Medium | CI/CD gates |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| Src/Editor/RectangleSelection.fs | 7.1 | Near-clean | Code Duplication: Duplicated block (15 lines × 2) |
| Src/Editor/SwapLines.fs | 7.4 | Near-clean | Code Duplication: Duplicated block (10–24 lines × 2) |
| Src/Util.fs | 7.4 | Near-clean | Code Duplication: Duplicated block (15 lines × 2) |
| Src/Editor/Foldings.fs | 7.4 | Near-clean | Code Duplication: Duplicated block (12 lines × 2) |
| Src/Editor/SelectionHighlighter.fs | 7.8 | Near-clean | Code Duplication: Duplicated block (13 lines × 2) |
| Src/Editor/TypeInfo.fs | 8.5 | Near-clean | God Classes: FileTooLong: Editor/TypeInfo.fs |
| Src/Fsi.fs | 8.5 | Near-clean | God Classes: FileTooLong: Src/Fsi.fs |
| Src/Views/Tabs.fs | 8.5 | Near-clean | God Classes: TooManyMethods: Tabs |
| Src/Editor/Commenting.fs | 8.5 | Near-clean | Code Duplication: Duplicated block (22–23 lines × 2) |
| Src/Editor/AlignText.fs | 8.5 | Near-clean | Code Duplication: Duplicated block (9 lines × 2) |
| Src/Views/Log.fs | 8.5 | Near-clean | Code Duplication: Duplicated block (7 lines × 2) |
| Src/Editor/NugetVersions.fs | 8.5 | Near-clean | Code Duplication: Duplicated block (6 lines × 2) |
| Src/Views/StatusBar.fs | 8.5 | Near-clean | Code Duplication: Duplicated block (2–5 lines × 4) |
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. 35 of 35 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); none rely on LLM judgement. Overall confidence is 0.8 — 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 — 35 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, 27 of 38 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
- D1 Cyclomatic Complexity — 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. Most of this repository's production source (.fs) had no cyclomatic complexity computed for it: no method bodies were exposed for those file kinds by any language model this pass could load.
- D2 Cognitive Complexity — 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. Most of this repository's production source (.fs) had no cognitive complexity computed for it: no method bodies were exposed for those file kinds by any language model this pass could load.
- D6 Cohesion (LCOM4) — 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. 56 of 56 class(es) with two or more methods were found, but the language model this pass loaded exposed none of their method bodies, so which method touches which field could not be seen.
- D15 Churn × Complexity Hotspots — 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. A hotspot is churn × complexity. Churn was measured (9911 line(s) across the 90-day window), but no complexity could be computed for .fs, which is most of this repository's production code — so every churned file would score as complexity 0 and the hotspot list would be empty no matter how tangled the code is. Not scored — this is a gap in the analysis run, not a finding about this repository.
- 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 (2 contributor(s) across 1301 commit(s) sampled, automation and bot accounts excluded). One of them holds 100% of the history; the other 1 hold 0% 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.
- D39 IL Efficiency — 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. `dotnet build` exited 1 with a compiler/MSBuild diagnostic, so there were no assemblies to read IL from. The build itself is D18's row, with the ask; nothing further is charged here.
- AX2 Stateful singletons — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads Microsoft.Extensions.DependencyInjection singletons in C#, Spring/JSR-330/CDI singletons in Java and Kotlin, module state in Python request handlers, handler state in Go and Swift, Play controllers, Cask routes, Scalatra servlets, Finatra controllers, Akka/Pekko HTTP routes and JSR-330 singletons in Scala, Rails, Sinatra, Grape, Roda and Hanami handlers and Rack apps in Ruby, and module state in F# request handlers (Giraffe, Saturn, Falco, Oxpecker and Suave handlers and ASP.NET Core controllers) only, and this repository's product is written in F#, which was left unread, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- AX6 Interface segregation — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is computed over the public interfaces this run's compilations declare, and none was loaded, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- AXB1 Runtime evidence locked — no reproducible boot — 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. Subject: a native UI project (Src/ThemeChrome.xaml). The Runtime Evidence tier boots an app only via docker-compose, an Aspire AppHost, a Dockerfile, an npm dev script, a web service's own toolchain entry point (cargo, go, dotnet, Python, Spring Boot), or an Android app's own Gradle wrapper (run on an emulator); an Apple or Flutter app needs a host it lacks. None applied, so no live runtime a11y/egress/header evidence was collected. You can widen what we reach: add a docker-compose.yml (or an Aspire AppHost) that brings the app up with its dependencies. Watchdog then boots it in an isolated sandbox and gathers real runtime evidence — you change nothing in your pipeline (no CI step, no SDK).
- 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.
- P1 CI/CD gates — 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 CI pipeline exists and the word "test" appears, but no explicit test-runner invocation (your stack's test command, or a test job) was matched — so either the gate runs tests through a step this pass could not recognise, or "test" is incidental here (a path, "latest", a reporter). Which of the two it is cannot be settled from this dimension's evidence; the coverage dimensions report whether a suite exists at all. You can widen what we reach: name the test runner explicitly in the pipeline step (your stack's test command, or a job named for the suite) so the gate is unambiguous to a reader and to this pass.
- 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
- 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.
- D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
- 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.
- D20 ADR Quality: ADR quality is an LLM read of the decision records present — it cannot know about decisions made and never recorded, and its verdict is sampled and advisory.
- 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.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- M4 Documentation accuracy: Onboarding quality is an LLM read of the docs/setup present — it cannot run the onboarding or measure how long a real new joiner takes; the verdict is sampled and advisory.
- P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
- P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
Dimensions
D3 · God Classes
3 god class(es) detected.
What to do
- Resolve the 2 FileTooLong finding(s) in God Classes — start with TypeInfo.fs, Fsi.fs. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 TooManyMethods finding(s) in God Classes — start with Tabs.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
22 duplicated block group(s) detected.
What to do
- Resolve the 3 Duplicated block (15 lines × 2) finding(s) in Code Duplication — start with RectangleSelection.fs (2), Util.fs. — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 3 Duplicated block (5 lines × 2) finding(s) in Code Duplication — start with Foldings.fs (2), Util.fs. — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 2 Duplicated block (14 lines × 2) finding(s) in Code Duplication — start with RectangleSelection.fs, Util.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
2 projects, 0 dependency cycle(s), 0 unstable depended-on project(s).
D8 · Code Coverage
No automated tests — no test code was found in this repository.
What to do
- Resolve the 1 No automated tests finding(s) in Code Coverage. — One of this dimension's main actionable groups (1 issue-level).
- Enforce Code Coverage in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D9 · Test Distribution
No test suite found.
What to do
- Resolve the 1 No tests found finding(s) in Test Distribution. — One of this dimension's main actionable groups (1 recommendation-level).
D12 · Dependency Hygiene
2 outdated, 0 vulnerable, 0 deprecated packages.
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D14 · License Compliance
0 of 131 packages use a banned license. ★ DEPTH: this repository's MSBuild projects declare 11 direct `PackageReference`(s), and 108 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.
D20 · ADR Quality
No architecture decision records were found.
What to do
- Resolve the 1 No ADRs found finding(s) in ADR Quality. — One of this dimension's main actionable groups (1 recommendation-level).
D26 · Project Cohesion
1 of 1 build units (MSBuild) flagged as possibly oversized/incoherent.
What to do
- Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion. — One of this dimension's main actionable groups (1 recommendation-level).
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
semgrep found no security issues. Separately, one or more rules could not re-parse an embedded snippet in 2 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.
D34 · Knowledge Freshness
Every significant source file has living knowledge — recently and meaningfully worked. Counted over 58 of the 64 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.
D36 · Supply-chain Provenance & Signing
2/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).
What to do
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 2 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
GD1 · Unfinished & placeholder code
M1 · Documentation (README)
What to do
- Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
- Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
M3 · Folder & project structure
M4 · Documentation accuracy
P1 · CI/CD gates
What to do
- Run the test suite in CI via an explicit runner step (`dotnet test` for the toolchain this pipeline already uses) and gate merges on it.
P2 · Observability
- No logging or diagnostics emission found. This repository ships a binary its users launch rather than a service you operate, so there is no operator to page — but when a run fails on a user's machine, neither they nor you have anything to read.
What to do
- Write a diagnostic trail the user can hand back with a bug report: a log file under the platform's per-user data directory, switchable with a `--verbose`/`--debug` flag. Start with the error paths that emit nothing — a discarded error is the failure the user cannot describe and you cannot reproduce.
P3 · Security & performance tooling
- No static application security testing detected. For this repository's stack, add `semgrep --config=auto` plus gitleaks for committed secrets (F# is not a CodeQL language and has no language-specific SAST engine) as a CI step. What was searched, so you can tell an absence from a miss: the 24015 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner. — .github/workflows/build.yml:7
- `.github/dependabot.yml` schedules updates, but no `package-ecosystem` entry covers `nuget`, which this tree depends on — so those dependencies get no update pull requests and no advisory pressure, however complete the dep-scan credit looks. Add the missing entry to the `updates:` list. — .github/dependabot.yml:2
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.
- Dependabot is configured but does not watch `nuget` — add that `package-ecosystem` entry to .github/dependabot.yml so those dependencies get the same automatic update and advisory pressure as the ones it already covers.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
P6 · Release Hygiene
PF2 · Allocation hygiene
What to do
- Raise allocation-aware density on the hot paths — currently 73 use(s) across 18,199 production line(s) (~4.0/1k). More of the idioms below on the allocation-heavy paths climbs this toward 10.
- F#: on hot paths, work through Span/Memory (AsSpan/AsMemory) instead of copies, rent buffers from ArrayPool, make small records, unions and tuples [<Struct>]/struct (…) and options voption, mark lambda parameters of inline functions [<InlineIfLambda>], use valueTask for completions that are usually synchronous, and presize ResizeArray/StringBuilder.
PF3 · Async & latency 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 | 93% | Exemplary | Strongest area. |
| Architecture | 84% | Adequate — gated by D26 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Maturity | 66% | Adequate — gated by M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 40% | Weak — gated by D8, D9, P2, P3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 88% | Strong | Solid. |
| Performance | 89% | Exemplary | Solid. |
Unscored — 1 check(s) recorded observations but carry no score
- SC1 Supply-chain hygiene — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Not evidenced — 4 control(s) we could not find positive evidence for
- C3 Audit Trail — Not assessed: these audit controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks audit controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- C4 Data Retention — Not assessed: these retention controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks retention controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- C5 Data-Subject Rights — Not assessed: these data-subject rights controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks data-subject rights controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 79 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 — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX6 Interface segregation — not assessed — interface segregation is computed over a type surface that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AX8 Test isolation — no test/production split to check
- AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
- AXB1 Runtime evidence locked — no reproducible boot — 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.
- D1 Cyclomatic Complexity — cyclomatic complexity not measured — .fs exposed no member bodies
- D10 Test Quality — No tests were found in the analyzed repository to assess for quality.
- D11 Test Reliability — No test suite was found to re-run, so reliability couldn't be assessed. Two searches produced that zero and both came back empty: the classifier that reads the loaded workspace recognised no suite it could run, and a walk of the source on disk — which covers the JS/TS `*.test.*` and `*.spec.*` conventions and probes for a Pester suite — found no test source in any other ecosystem either. Neither search reaches a suite that is missing from the loaded workspace and carries no name either walk recognises, so this is 'no suite found by those two searches', not a verdict that the repository has none.
- D15 Churn × Complexity Hotspots — complexity unreadable for .fs — churn × complexity hotspots could not be measured
- 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.
- D2 Cognitive Complexity — cognitive complexity not measured — .fs exposed no member bodies
- 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
- D27 Navigability — No calls could be sampled, so navigability was not assessed — tracing effort is measured over resolved call sites and this target exposed none. Not scored — this is a gap in the analyzer's reach, not a verdict about this repository.
- D30 Dependency Vulnerabilities — nuget: the solution did not restore on the analyzer's .NET SDK (an SDK/target-framework/restore mismatch, common for an older codebase), so there was no restored dependency graph to scan
- D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
- D32 Data Compliance (PII/GDPR) — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- D39 IL Efficiency — IL not measured — the target did not build
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D43 Malicious Dependencies — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Python pyproject.toml/requirements.txt (pip/uv/Poetry), a Swift Package.swift/Package.resolved, a Cargo manifest, a Go module (go.mod/go.sum), a Gradle version catalogue, a Maven POM, an sbt build (build.sbt), composer.json, package.json, a Dart pubspec.yaml, an Elixir mix.exs/mix.lock (Hex), a rebar.config / erlang.mk DEPS (Hex), a Ruby Gemfile/Gemfile.lock or .gemspec (Bundler/RubyGems) — not scanned yet).
- D6 Cohesion (LCOM4) — cohesion (LCOM4) not measured — the code model exposed no member bodies
- D7 Architectural Integrity — no checkable ADRs and no dependency cycles — architectural integrity not assessed
- DM1 Domain Modelling — applicable but not scored (2 of 3 signals for this style — below the bar we score at): 45 value object(s); 1 domain event(s); its domain events are published by services or handlers — no domain entity raises one
- ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
- ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
- P7 Outbound HTTP resilience — not measured — the application kind could not be determined for this repo
- P8 Schema migrations — 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.
- 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 — 1 finding(s)
- No automated tests
Serious — 27 finding(s)
- Duplicated block (15 lines × 2) Src/Editor/RectangleSelection.fs:41
- Duplicated block (15 lines × 2) Src/Editor/RectangleSelection.fs:183
- Duplicated block (15 lines × 2) Src/Util.fs:418
- Duplicated block (5 lines × 2) Src/Editor/Foldings.fs:205
- Duplicated block (5 lines × 2) Src/Editor/Foldings.fs:367
- Duplicated block (5 lines × 2) Src/Util.fs:507
- FileTooLong: Editor/TypeInfo.fs Src/Editor/TypeInfo.fs
- FileTooLong: Src/Fsi.fs Src/Fsi.fs
- Duplicated block (14 lines × 2) Src/Editor/RectangleSelection.fs:56
- Duplicated block (14 lines × 2) Src/Util.fs:490
- Duplicated block (7 lines × 2) Src/Editor/RectangleSelection.fs:83
- Duplicated block (7 lines × 2) Src/Views/Log.fs:279
- TooManyMethods: Tabs Src/Views/Tabs.fs:22
- Duplicated block (10–24 lines × 2) Src/Editor/SwapLines.fs:28
- Duplicated block (22–23 lines × 2) Src/Editor/Commenting.fs:35
- Duplicated block (17–18 lines × 2) Src/Editor/SwapLines.fs:53
- Duplicated block (14 lines × 3) Src/Editor/RectangleSelection.fs:141
- Duplicated block (13 lines × 2) Src/Editor/SelectionHighlighter.fs:289
- Duplicated block (12 lines × 2) Src/Editor/Foldings.fs:73
- Duplicated block (11 lines × 2) Src/Editor/SwapLines.fs:16
- Duplicated block (6–10 lines × 2) Src/Editor/SelectionHighlighter.fs:75
- Duplicated block (9 lines × 2) Src/Editor/AlignText.fs:21
- Duplicated block (6–7 lines × 2) Src/Editor/RectangleSelection.fs:34
- Duplicated block (6 lines × 2) Src/Editor/NugetVersions.fs:83
- Duplicated block (2–5 lines × 4) Src/Views/StatusBar.fs:72
- No structured logging
- NuGet dependencies are not locked
Minor — 8 finding(s)
- No ADRs found
- Projects may be oversized for their cohesion
- REDACTED
- REDACTED
- No tests found
- No ADRs
- No SAST .github/workflows/build.yml:7
- Dependabot does not watch nuget .github/dependabot.yml:2
Minor — 2 finding(s)
- Outdated: FSharp.Compiler.Service
- Outdated: FSharp.Core
Appendix B — Reproduction & audit trail
| Dimension | Tool | Version | Command | Findings | Raw output |
|---|---|---|---|---|---|
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-b57d3949c27a415dba8304e3bbf3564f/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-b57d3949c27a415dba8304e3bbf3564f/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 . | 0 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | nuget | — | nuget: not applicable — nuget: the solution did not restore on the analyzer's .NET SDK (an SDK/target-framework/restore mismatch, common for an older codebase), so there was no restored dependency graph to scan | 0 | — |
| D31 · IaC & Container Security | trivy | — | trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan. | 0 | — |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. | 0 | — |
| D37 · Vulnerability-disclosure Policy | disclosure | — | disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | none (no readable dependency manifest) | — | none (no readable dependency manifest): not applicable — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Python pyproject.toml/requirements.txt (pip/uv/Poetry), a Swift Package.swift/Package.resolved, a Cargo manifest, a Go module (go.mod/go.sum), a Gradle version catalogue, a Maven POM, an sbt build (build.sbt), composer.json, package.json, a Dart pubspec.yaml, an Elixir mix.exs/mix.lock (Hex), a rebar.config / erlang.mk DEPS (Hex), a Ruby Gemfile/Gemfile.lock or .gemspec (Bundler/RubyGems) — not scanned yet). | 0 | — |