Executive summary
fable-compiler/repl falls short of our standard for production, in part because the project has no automated tests. It scores 38 out of 100 and is rated Weak, and 11 of its 27 critical findings are security problems.
Production Readiness, at 26, is the weakest lens and counts most in the score. The best first step is adding automated tests, worth about 9 points. Recording design decisions comes next, worth about 6 points. Raising Production Readiness to 70 would lift the score to about 47.
Seven pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Two known security holes in the packages the code depends on can be used by attackers, and seven controls can't be used without a mouse. Pinning each tool to an exact version, updating the vulnerable packages and making the controls work with a keyboard would close these risks. Limiting each secret to its own step would fix the secret exposed to more of the pipeline than needed, and the password or key in the code's history needs replacing, with the old one switched off. The three images with no text description need a text description.
The product code is 25,255 lines, about €22,000 to rebuild.
If Production Readiness rose from 26 to 70, the lowest score rated Strong, the score would rise from 38 to about 47.
New since the last survey: 5 findings
- Secrets (history) · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Supply-chain Provenance & Signing · REDACTED
- Supply-chain Provenance & Signing · REDACTED
Fixed since the last survey: 3 findings
- Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
- Supply-chain Provenance & Signing · Unpinned build actions
- Supply-chain Provenance & Signing REDACTED
Rebuild cost: about €22,000 · Estimate
| Cost to rebuild | €7,100 to €36,000, for 119 to 378 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.7 at a score of 38. 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 | Medium: 25,255 lines of product code |
| What it is not | Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one. |
Top priorities
Diagnosis: what the measurements show together
Architecture — module dependency graph
Architecture: which parts of the code depend on which
| uses → | 1 Fable.Repl.Mouse | 2 Fable.Repl.Mouse.Cmd | 3 Fable.Repl.Sidebar | 4 Feliz.Styles | 5 Snabbdom | 6 Sutil | 7 Sutil.Cmd | 8 Elmish.Snabbdom.Program.Util | 9 Feliz | 10 Feliz.Snabbdom | 11 Monaco.Languages | 12 Sutil.DevToolsControl | 13 Monaco | 14 Sutil.DOM | 15 Sutil.ObservableStore.Registry | 16 Elmish.Snabbdom.HMR.Bindings | 17 Elmish.Snabbdom.Program | 18 Monaco.Editor | 19 Monaco.Languages.Css | 20 Monaco.Languages.Html | 21 Sutil.Html | 22 Sutil.ObservablePromise | 23 Sutil.ObservableStore | 24 Sutil.ObservableStore.Helpers | 25 Sutil.Store | 26 Sutil.Transition | 27 Sutil.Transition.LoopTasks | 28 Elmish.Snabbdom.HMR.Program.Internal | 29 Fable.Repl.Main | 30 Feliz.ReactEditor | 31 Feliz.ReactEditor.Dispatch | 32 Sutil.Bindings | 33 Sutil.Cmd.OfTask | 34 Elmish.Cmd | 35 Fable.Repl.Loader | 36 Elmish.Cmd.OfAsync | 37 Elmish.Cmd.OfAsyncImmediate | 38 Elmish.Cmd.OfAsyncWith | 39 Elmish.Cmd.OfFunc | 40 Elmish.Cmd.OfTask |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 Fable.Repl.Mouse | ||||||||||||||||||||||||||||||||||||||||
| 2 Fable.Repl.Mouse.Cmd | ||||||||||||||||||||||||||||||||||||||||
| 3 Fable.Repl.Sidebar | ||||||||||||||||||||||||||||||||||||||||
| 4 Feliz.Styles | ||||||||||||||||||||||||||||||||||||||||
| 5 Snabbdom | ||||||||||||||||||||||||||||||||||||||||
| 6 Sutil | ||||||||||||||||||||||||||||||||||||||||
| 7 Sutil.Cmd | ||||||||||||||||||||||||||||||||||||||||
| 8 Elmish.Snabbdom.Program.Util | 1 | |||||||||||||||||||||||||||||||||||||||
| 9 Feliz | 23 | |||||||||||||||||||||||||||||||||||||||
| 10 Feliz.Snabbdom | 1 | |||||||||||||||||||||||||||||||||||||||
| 11 Monaco.Languages | 14 | |||||||||||||||||||||||||||||||||||||||
| 12 Sutil.DevToolsControl | 1 | |||||||||||||||||||||||||||||||||||||||
| 13 Monaco | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 14 Sutil.DOM | 6 | |||||||||||||||||||||||||||||||||||||||
| 15 Sutil.ObservableStore.Registry | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 16 Elmish.Snabbdom.HMR.Bindings | 1 | |||||||||||||||||||||||||||||||||||||||
| 17 Elmish.Snabbdom.Program | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 18 Monaco.Editor | 36 | |||||||||||||||||||||||||||||||||||||||
| 19 Monaco.Languages.Css | 1 | |||||||||||||||||||||||||||||||||||||||
| 20 Monaco.Languages.Html | 1 | |||||||||||||||||||||||||||||||||||||||
| 21 Sutil.Html | 2 | 2 | ||||||||||||||||||||||||||||||||||||||
| 22 Sutil.ObservablePromise | 1 | |||||||||||||||||||||||||||||||||||||||
| 23 Sutil.ObservableStore | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 24 Sutil.ObservableStore.Helpers | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 25 Sutil.Store | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 26 Sutil.Transition | 1 | 3 | ||||||||||||||||||||||||||||||||||||||
| 27 Sutil.Transition.LoopTasks | 1 | |||||||||||||||||||||||||||||||||||||||
| 28 Elmish.Snabbdom.HMR.Program.Internal | 1 | |||||||||||||||||||||||||||||||||||||||
| 29 Fable.Repl.Main | 1 | 2 | 5 | |||||||||||||||||||||||||||||||||||||
| 30 Feliz.ReactEditor | 2 | |||||||||||||||||||||||||||||||||||||||
| 31 Feliz.ReactEditor.Dispatch | 1 | |||||||||||||||||||||||||||||||||||||||
| 32 Sutil.Bindings | 2 | 1 | 1 | 2 | 1 | 1 | ||||||||||||||||||||||||||||||||||
| 33 Sutil.Cmd.OfTask | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 34 Elmish.Cmd | 1 | |||||||||||||||||||||||||||||||||||||||
| 35 Fable.Repl.Loader | 2 | |||||||||||||||||||||||||||||||||||||||
| 36 Elmish.Cmd.OfAsync | 1 | |||||||||||||||||||||||||||||||||||||||
| 37 Elmish.Cmd.OfAsyncImmediate | 1 | |||||||||||||||||||||||||||||||||||||||
| 38 Elmish.Cmd.OfAsyncWith | 1 | |||||||||||||||||||||||||||||||||||||||
| 39 Elmish.Cmd.OfFunc | 1 | |||||||||||||||||||||||||||||||||||||||
| 40 Elmish.Cmd.OfTask | 1 | 1 |
8→5 Elmish.Snabbdom.Program.Util uses Snabbdom✕
- Connections
- 1 pair of types, where a type in Elmish.Snabbdom.Program.Util uses a type in Snabbdom.
- The types involved
Elmish.Snabbdom.Program.Util.Util→Snabbdom.VNode
- Direction
- Elmish.Snabbdom.Program.Util uses Snabbdom, so a change to Snabbdom can break Elmish.Snabbdom.Program.Util, while a change to Elmish.Snabbdom.Program.Util can't break Snabbdom.
- Position
- Below the diagonal: Elmish.Snabbdom.Program.Util uses a module listed above it, which is the healthy direction.
9→4 Feliz uses Feliz.Styles✕
- Connections
- 23 pairs of types, where a type in Feliz uses a type in Feliz.Styles.
- The types involved
Feliz.AttrEngine→Feliz.Styles.ICssUnitFeliz.AttrEngine→Feliz.Styles.ITransformPropertyFeliz.CssEngine→Feliz.Styles.IBackgroundRepeatFeliz.CssEngine→Feliz.Styles.IBorderStyleFeliz.CssEngine→Feliz.Styles.ICssUnitFeliz.CssEngine→Feliz.Styles.IGridSpanFeliz.CssEngine→Feliz.Styles.ITextDecorationLineFeliz.CssEngine→Feliz.Styles.ITransformPropertyFeliz.CssEngine→Feliz.Styles.ITransitionPropertyFeliz.Util→Feliz.Styles.IBorderStyleFeliz.Util→Feliz.Styles.ICssUnitFeliz.Util→Feliz.Styles.IGridSpanFeliz.Util→Feliz.Styles.IGridTemplateItemFeliz.Util→Feliz.Styles.ITextDecorationFeliz.Util→Feliz.Styles.ITextDecorationLineFeliz.Util→Feliz.Styles.ITransformPropertyFeliz.Util→Feliz.Styles.ITransitionPropertyFeliz.grid→Feliz.Styles.ICssUnitFeliz.grid→Feliz.Styles.IGridTemplateItemFeliz.gridColumn→Feliz.Styles.IGridSpanFeliz.gridRow→Feliz.Styles.IGridSpanFeliz.length→Feliz.Styles.ICssUnitFeliz.transform→Feliz.Styles.ICssUnit
- Direction
- Feliz uses Feliz.Styles, so a change to Feliz.Styles can break Feliz, while a change to Feliz can't break Feliz.Styles.
- Position
- Below the diagonal: Feliz uses a module listed above it, which is the healthy direction.
10→5 Feliz.Snabbdom uses Snabbdom✕
- Connections
- 1 pair of types, where a type in Feliz.Snabbdom uses a type in Snabbdom.
- The types involved
Feliz.Snabbdom.Node→Snabbdom.VNode
- Direction
- Feliz.Snabbdom uses Snabbdom, so a change to Snabbdom can break Feliz.Snabbdom, while a change to Feliz.Snabbdom can't break Snabbdom.
- Position
- Below the diagonal: Feliz.Snabbdom uses a module listed above it, which is the healthy direction.
11→13 Monaco.Languages uses Monaco part of a loop✕
- Connections
- 14 pairs of types, where a type in Monaco.Languages uses a type in Monaco.
- The types involved
Monaco.Languages.DefinitionLink→Monaco.IRangeMonaco.Languages.DefinitionLink→Monaco.UriMonaco.Languages.DocumentHighlight→Monaco.IRangeMonaco.Languages.DocumentSymbol→Monaco.IRangeMonaco.Languages.ICodeLensSymbol→Monaco.IRangeMonaco.Languages.IColorInformation→Monaco.IRangeMonaco.Languages.IExports→Monaco.IDisposableMonaco.Languages.ILink→Monaco.IRangeMonaco.Languages.Location→Monaco.IRangeMonaco.Languages.Location→Monaco.UriMonaco.Languages.RenameLocation→Monaco.IRangeMonaco.Languages.ResourceFileEdit→Monaco.UriMonaco.Languages.ResourceTextEdit→Monaco.UriMonaco.Languages.TextEdit→Monaco.IRange
- Direction
- Monaco.Languages uses Monaco, so a change to Monaco can break Monaco.Languages, while a change to Monaco.Languages can't break Monaco.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
12→6 Sutil.DevToolsControl uses Sutil✕
- Connections
- 1 pair of types, where a type in Sutil.DevToolsControl uses a type in Sutil.
- The types involved
Sutil.DevToolsControl.IControlBlock→Sutil.IStoreDebugger
- Direction
- Sutil.DevToolsControl uses Sutil, so a change to Sutil can break Sutil.DevToolsControl, while a change to Sutil.DevToolsControl can't break Sutil.
- Position
- Below the diagonal: Sutil.DevToolsControl uses a module listed above it, which is the healthy direction.
13→11 Monaco uses Monaco.Languages✕
- Connections
- 1 pair of types, where a type in Monaco uses a type in Monaco.Languages.
- The types involved
Monaco.IExports→Monaco.Languages.IExports
- Direction
- Monaco uses Monaco.Languages, so a change to Monaco.Languages can break Monaco, while a change to Monaco can't break Monaco.Languages.
- Position
- Below the diagonal: Monaco uses a module listed above it, which is the healthy direction.
13→18 Monaco uses Monaco.Editor part of a loop✕
- Connections
- 1 pair of types, where a type in Monaco uses a type in Monaco.Editor.
- The types involved
Monaco.IExports→Monaco.Editor.IExports
- Direction
- Monaco uses Monaco.Editor, so a change to Monaco.Editor can break Monaco, while a change to Monaco can't break Monaco.Editor.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
14→10 Sutil.DOM uses Feliz.Snabbdom✕
- Connections
- 6 pairs of types, where a type in Sutil.DOM uses a type in Feliz.Snabbdom.
- The types involved
Sutil.DOM.BuildContext→Feliz.Snabbdom.NodeSutil.DOM.DOM→Feliz.Snabbdom.EventTargetSutil.DOM.DOM→Feliz.Snabbdom.NodeSutil.DOM.DomAction→Feliz.Snabbdom.NodeSutil.DOM.NodeGroup→Feliz.Snabbdom.NodeSutil.DOM.SutilNode→Feliz.Snabbdom.Node
- Direction
- Sutil.DOM uses Feliz.Snabbdom, so a change to Feliz.Snabbdom can break Sutil.DOM, while a change to Sutil.DOM can't break Feliz.Snabbdom.
- Position
- Below the diagonal: Sutil.DOM uses a module listed above it, which is the healthy direction.
15→6 Sutil.ObservableStore.Registry uses Sutil✕
- Connections
- 1 pair of types, where a type in Sutil.ObservableStore.Registry uses a type in Sutil.
- The types involved
Sutil.ObservableStore.Registry.Registry→Sutil.IStoreDebugger
- Direction
- Sutil.ObservableStore.Registry uses Sutil, so a change to Sutil can break Sutil.ObservableStore.Registry, while a change to Sutil.ObservableStore.Registry can't break Sutil.
- Position
- Below the diagonal: Sutil.ObservableStore.Registry uses a module listed above it, which is the healthy direction.
15→12 Sutil.ObservableStore.Registry uses Sutil.DevToolsControl✕
- Connections
- 1 pair of types, where a type in Sutil.ObservableStore.Registry uses a type in Sutil.DevToolsControl.
- The types involved
Sutil.ObservableStore.Registry.Registry→Sutil.DevToolsControl.IControlBlock
- Direction
- Sutil.ObservableStore.Registry uses Sutil.DevToolsControl, so a change to Sutil.DevToolsControl can break Sutil.ObservableStore.Registry, while a change to Sutil.ObservableStore.Registry can't break Sutil.DevToolsControl.
- Position
- Below the diagonal: Sutil.ObservableStore.Registry uses a module listed above it, which is the healthy direction.
16→13 Elmish.Snabbdom.HMR.Bindings uses Monaco✕
- Connections
- 1 pair of types, where a type in Elmish.Snabbdom.HMR.Bindings uses a type in Monaco.
- The types involved
Elmish.Snabbdom.HMR.Bindings.IHot→Monaco.Promise
- Direction
- Elmish.Snabbdom.HMR.Bindings uses Monaco, so a change to Monaco can break Elmish.Snabbdom.HMR.Bindings, while a change to Elmish.Snabbdom.HMR.Bindings can't break Monaco.
- Position
- Below the diagonal: Elmish.Snabbdom.HMR.Bindings uses a module listed above it, which is the healthy direction.
17→10 Elmish.Snabbdom.Program uses Feliz.Snabbdom✕
- Connections
- 1 pair of types, where a type in Elmish.Snabbdom.Program uses a type in Feliz.Snabbdom.
- The types involved
Elmish.Snabbdom.Program.Program→Feliz.Snabbdom.Node
- Direction
- Elmish.Snabbdom.Program uses Feliz.Snabbdom, so a change to Feliz.Snabbdom can break Elmish.Snabbdom.Program, while a change to Elmish.Snabbdom.Program can't break Feliz.Snabbdom.
- Position
- Below the diagonal: Elmish.Snabbdom.Program uses a module listed above it, which is the healthy direction.
17→13 Elmish.Snabbdom.Program uses Monaco✕
- Connections
- 1 pair of types, where a type in Elmish.Snabbdom.Program uses a type in Monaco.
- The types involved
Elmish.Snabbdom.Program.Program→Monaco.Promise
- Direction
- Elmish.Snabbdom.Program uses Monaco, so a change to Monaco can break Elmish.Snabbdom.Program, while a change to Elmish.Snabbdom.Program can't break Monaco.
- Position
- Below the diagonal: Elmish.Snabbdom.Program uses a module listed above it, which is the healthy direction.
18→13 Monaco.Editor uses Monaco✕
- Connections
- 36 pairs of types, where a type in Monaco.Editor uses a type in Monaco. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
Monaco.Editor.FindMatch→Monaco.RangeMonaco.Editor.ICodeEditor→Monaco.IDisposableMonaco.Editor.ICommand→Monaco.SelectionMonaco.Editor.IContentWidgetPosition→Monaco.IPositionMonaco.Editor.ICursorPositionChangedEvent→Monaco.PositionMonaco.Editor.ICursorSelectionChangedEvent→Monaco.SelectionMonaco.Editor.ICursorState→Monaco.IPositionMonaco.Editor.ICursorStateComputerData→Monaco.SelectionMonaco.Editor.IDiffEditor→Monaco.IDisposableMonaco.Editor.IEditor→Monaco.IDisposableMonaco.Editor.IEditor→Monaco.PositionMonaco.Editor.IEditor→Monaco.SelectionMonaco.Editor.IEditorAction→Monaco.PromiseMonaco.Editor.IEditorMouseEvent→Monaco.IMouseEventMonaco.Editor.IExports→Monaco.IDisposableMonaco.Editor.IExports→Monaco.PromiseMonaco.Editor.IIdentifiedSingleEditOperation→Monaco.RangeMonaco.Editor.IMarker→Monaco.MarkerSeverityMonaco.Editor.IMarker→Monaco.UriMonaco.Editor.IMarkerData→Monaco.MarkerSeverityMonaco.Editor.IModelChangedEvent→Monaco.UriMonaco.Editor.IModelContentChange→Monaco.IRangeMonaco.Editor.IModelDecoration→Monaco.RangeMonaco.Editor.IModelDeltaDecoration→Monaco.IRangeMonaco.Editor.IMouseTarget→Monaco.Position
- Direction
- Monaco.Editor uses Monaco, so a change to Monaco can break Monaco.Editor, while a change to Monaco.Editor can't break Monaco.
- Position
- Below the diagonal: Monaco.Editor uses a module listed above it, which is the healthy direction.
19→13 Monaco.Languages.Css uses Monaco✕
- Connections
- 1 pair of types, where a type in Monaco.Languages.Css uses a type in Monaco.
- The types involved
Monaco.Languages.Css.LanguageServiceDefaults→Monaco.IEvent
- Direction
- Monaco.Languages.Css uses Monaco, so a change to Monaco can break Monaco.Languages.Css, while a change to Monaco.Languages.Css can't break Monaco.
- Position
- Below the diagonal: Monaco.Languages.Css uses a module listed above it, which is the healthy direction.
20→13 Monaco.Languages.Html uses Monaco✕
- Connections
- 1 pair of types, where a type in Monaco.Languages.Html uses a type in Monaco.
- The types involved
Monaco.Languages.Html.LanguageServiceDefaults→Monaco.IEvent
- Direction
- Monaco.Languages.Html uses Monaco, so a change to Monaco can break Monaco.Languages.Html, while a change to Monaco.Languages.Html can't break Monaco.
- Position
- Below the diagonal: Monaco.Languages.Html uses a module listed above it, which is the healthy direction.
21→9 Sutil.Html uses Feliz✕
- Connections
- 2 pairs of types, where a type in Sutil.Html uses a type in Feliz.
- The types involved
Sutil.Html.SutilAttrEngine→Feliz.AttrEngineSutil.Html.SutilHtmlEngine→Feliz.HtmlEngine
- Direction
- Sutil.Html uses Feliz, so a change to Feliz can break Sutil.Html, while a change to Sutil.Html can't break Feliz.
- Position
- Below the diagonal: Sutil.Html uses a module listed above it, which is the healthy direction.
21→14 Sutil.Html uses Sutil.DOM✕
- Connections
- 2 pairs of types, where a type in Sutil.Html uses a type in Sutil.DOM.
- The types involved
Sutil.Html.NodeAttr→Sutil.DOM.SutilElementSutil.Html.SutilHtmlEngine→Sutil.DOM.SutilElement
- Direction
- Sutil.Html uses Sutil.DOM, so a change to Sutil.DOM can break Sutil.Html, while a change to Sutil.Html can't break Sutil.DOM.
- Position
- Below the diagonal: Sutil.Html uses a module listed above it, which is the healthy direction.
22→13 Sutil.ObservablePromise uses Monaco✕
- Connections
- 1 pair of types, where a type in Sutil.ObservablePromise uses a type in Monaco.
- The types involved
Sutil.ObservablePromise.ObservablePromise→Monaco.Promise
- Direction
- Sutil.ObservablePromise uses Monaco, so a change to Monaco can break Sutil.ObservablePromise, while a change to Sutil.ObservablePromise can't break Monaco.
- Position
- Below the diagonal: Sutil.ObservablePromise uses a module listed above it, which is the healthy direction.
23→6 Sutil.ObservableStore uses Sutil✕
- Connections
- 1 pair of types, where a type in Sutil.ObservableStore uses a type in Sutil.
- The types involved
Sutil.ObservableStore.Store→Sutil.IStore
- Direction
- Sutil.ObservableStore uses Sutil, so a change to Sutil can break Sutil.ObservableStore, while a change to Sutil.ObservableStore can't break Sutil.
- Position
- Below the diagonal: Sutil.ObservableStore uses a module listed above it, which is the healthy direction.
23→13 Sutil.ObservableStore uses Monaco✕
- Connections
- 1 pair of types, where a type in Sutil.ObservableStore uses a type in Monaco.
- The types involved
Sutil.ObservableStore.Store→Monaco.IDisposable
- Direction
- Sutil.ObservableStore uses Monaco, so a change to Monaco can break Sutil.ObservableStore, while a change to Sutil.ObservableStore can't break Monaco.
- Position
- Below the diagonal: Sutil.ObservableStore uses a module listed above it, which is the healthy direction.
24→2 Sutil.ObservableStore.Helpers uses Fable.Repl.Mouse.Cmd✕
- Connections
- 1 pair of types, where a type in Sutil.ObservableStore.Helpers uses a type in Fable.Repl.Mouse.Cmd.
- The types involved
Sutil.ObservableStore.Helpers.CmdHandler→Fable.Repl.Mouse.Cmd.Cmd
- Direction
- Sutil.ObservableStore.Helpers uses Fable.Repl.Mouse.Cmd, so a change to Fable.Repl.Mouse.Cmd can break Sutil.ObservableStore.Helpers, while a change to Sutil.ObservableStore.Helpers can't break Fable.Repl.Mouse.Cmd.
- Position
- Below the diagonal: Sutil.ObservableStore.Helpers uses a module listed above it, which is the healthy direction.
24→13 Sutil.ObservableStore.Helpers uses Monaco✕
- Connections
- 1 pair of types, where a type in Sutil.ObservableStore.Helpers uses a type in Monaco.
- The types involved
Sutil.ObservableStore.Helpers.CmdHandler→Monaco.IDisposable
- Direction
- Sutil.ObservableStore.Helpers uses Monaco, so a change to Monaco can break Sutil.ObservableStore.Helpers, while a change to Sutil.ObservableStore.Helpers can't break Monaco.
- Position
- Below the diagonal: Sutil.ObservableStore.Helpers uses a module listed above it, which is the healthy direction.
25→6 Sutil.Store uses Sutil✕
- Connections
- 1 pair of types, where a type in Sutil.Store uses a type in Sutil.
- The types involved
Sutil.Store.Store→Sutil.IStore
- Direction
- Sutil.Store uses Sutil, so a change to Sutil can break Sutil.Store, while a change to Sutil.Store can't break Sutil.
- Position
- Below the diagonal: Sutil.Store uses a module listed above it, which is the healthy direction.
25→13 Sutil.Store uses Monaco✕
- Connections
- 1 pair of types, where a type in Sutil.Store uses a type in Monaco.
- The types involved
Sutil.Store.Store→Monaco.IDisposable
- Direction
- Sutil.Store uses Monaco, so a change to Monaco can break Sutil.Store, while a change to Sutil.Store can't break Monaco.
- Position
- Below the diagonal: Sutil.Store uses a module listed above it, which is the healthy direction.
26→13 Sutil.Transition uses Monaco✕
- Connections
- 1 pair of types, where a type in Sutil.Transition uses a type in Monaco.
- The types involved
Sutil.Transition.HideableRuntime→Monaco.IDisposable
- Direction
- Sutil.Transition uses Monaco, so a change to Monaco can break Sutil.Transition, while a change to Sutil.Transition can't break Monaco.
- Position
- Below the diagonal: Sutil.Transition uses a module listed above it, which is the healthy direction.
26→14 Sutil.Transition uses Sutil.DOM✕
- Connections
- 3 pairs of types, where a type in Sutil.Transition uses a type in Sutil.DOM.
- The types involved
Sutil.Transition.Hideable→Sutil.DOM.SutilElementSutil.Transition.HideableRuntime→Sutil.DOM.SutilNodeSutil.Transition.Transition→Sutil.DOM.SutilElement
- Direction
- Sutil.Transition uses Sutil.DOM, so a change to Sutil.DOM can break Sutil.Transition, while a change to Sutil.Transition can't break Sutil.DOM.
- Position
- Below the diagonal: Sutil.Transition uses a module listed above it, which is the healthy direction.
27→13 Sutil.Transition.LoopTasks uses Monaco✕
- Connections
- 1 pair of types, where a type in Sutil.Transition.LoopTasks uses a type in Monaco.
- The types involved
Sutil.Transition.LoopTasks.LoopTask→Monaco.Promise
- Direction
- Sutil.Transition.LoopTasks uses Monaco, so a change to Monaco can break Sutil.Transition.LoopTasks, while a change to Sutil.Transition.LoopTasks can't break Monaco.
- Position
- Below the diagonal: Sutil.Transition.LoopTasks uses a module listed above it, which is the healthy direction.
28→16 Elmish.Snabbdom.HMR.Program.Internal uses Elmish.Snabbdom.HMR.Bindings✕
- Connections
- 1 pair of types, where a type in Elmish.Snabbdom.HMR.Program.Internal uses a type in Elmish.Snabbdom.HMR.Bindings.
- The types involved
Elmish.Snabbdom.HMR.Program.Internal.Internal→Elmish.Snabbdom.HMR.Bindings.IHot
- Direction
- Elmish.Snabbdom.HMR.Program.Internal uses Elmish.Snabbdom.HMR.Bindings, so a change to Elmish.Snabbdom.HMR.Bindings can break Elmish.Snabbdom.HMR.Program.Internal, while a change to Elmish.Snabbdom.HMR.Program.Internal can't break Elmish.Snabbdom.HMR.Bindings.
- Position
- Below the diagonal: Elmish.Snabbdom.HMR.Program.Internal uses a module listed above it, which is the healthy direction.
29→1 Fable.Repl.Main uses Fable.Repl.Mouse✕
- Connections
- 1 pair of types, where a type in Fable.Repl.Main uses a type in Fable.Repl.Mouse.
- The types involved
Fable.Repl.Main.Msg→Fable.Repl.Mouse.Position
- Direction
- Fable.Repl.Main uses Fable.Repl.Mouse, so a change to Fable.Repl.Mouse can break Fable.Repl.Main, while a change to Fable.Repl.Main can't break Fable.Repl.Mouse.
- Position
- Below the diagonal: Fable.Repl.Main uses a module listed above it, which is the healthy direction.
29→3 Fable.Repl.Main uses Fable.Repl.Sidebar✕
- Connections
- 2 pairs of types, where a type in Fable.Repl.Main uses a type in Fable.Repl.Sidebar.
- The types involved
Fable.Repl.Main.Model→Fable.Repl.Sidebar.ModelFable.Repl.Main.Msg→Fable.Repl.Sidebar.Msg
- Direction
- Fable.Repl.Main uses Fable.Repl.Sidebar, so a change to Fable.Repl.Sidebar can break Fable.Repl.Main, while a change to Fable.Repl.Main can't break Fable.Repl.Sidebar.
- Position
- Below the diagonal: Fable.Repl.Main uses a module listed above it, which is the healthy direction.
29→18 Fable.Repl.Main uses Monaco.Editor✕
- Connections
- 5 pairs of types, where a type in Fable.Repl.Main uses a type in Monaco.Editor.
- The types involved
Fable.Repl.Main.Main→Monaco.Editor.IEditorConstructionOptionsFable.Repl.Main.Main→Monaco.Editor.IMarkerDataFable.Repl.Main.Model→Monaco.Editor.IEditorFable.Repl.Main.Model→Monaco.Editor.IMarkerDataFable.Repl.Main.Msg→Monaco.Editor.IEditor
- Direction
- Fable.Repl.Main uses Monaco.Editor, so a change to Monaco.Editor can break Fable.Repl.Main, while a change to Fable.Repl.Main can't break Monaco.Editor.
- Position
- Below the diagonal: Fable.Repl.Main uses a module listed above it, which is the healthy direction.
30→18 Feliz.ReactEditor uses Monaco.Editor✕
- Connections
- 2 pairs of types, where a type in Feliz.ReactEditor uses a type in Monaco.Editor.
- The types involved
Feliz.ReactEditor.editor→Monaco.Editor.IEditorConstructionOptionsFeliz.ReactEditor.editor→Monaco.Editor.IMarkerData
- Direction
- Feliz.ReactEditor uses Monaco.Editor, so a change to Monaco.Editor can break Feliz.ReactEditor, while a change to Feliz.ReactEditor can't break Monaco.Editor.
- Position
- Below the diagonal: Feliz.ReactEditor uses a module listed above it, which is the healthy direction.
31→18 Feliz.ReactEditor.Dispatch uses Monaco.Editor✕
- Connections
- 1 pair of types, where a type in Feliz.ReactEditor.Dispatch uses a type in Monaco.Editor.
- The types involved
Feliz.ReactEditor.Dispatch.Dispatch→Monaco.Editor.IMarkerData
- Direction
- Feliz.ReactEditor.Dispatch uses Monaco.Editor, so a change to Monaco.Editor can break Feliz.ReactEditor.Dispatch, while a change to Feliz.ReactEditor.Dispatch can't break Monaco.Editor.
- Position
- Below the diagonal: Feliz.ReactEditor.Dispatch uses a module listed above it, which is the healthy direction.
32→6 Sutil.Bindings uses Sutil✕
- Connections
- 2 pairs of types, where a type in Sutil.Bindings uses a type in Sutil.
- The types involved
Sutil.Bindings.Bindings→Sutil.IStoreSutil.Bindings.KeyedStoreItem→Sutil.IStore
- Direction
- Sutil.Bindings uses Sutil, so a change to Sutil can break Sutil.Bindings, while a change to Sutil.Bindings can't break Sutil.
- Position
- Below the diagonal: Sutil.Bindings uses a module listed above it, which is the healthy direction.
32→10 Sutil.Bindings uses Feliz.Snabbdom✕
- Connections
- 1 pair of types, where a type in Sutil.Bindings uses a type in Feliz.Snabbdom.
- The types involved
Sutil.Bindings.Bindings→Feliz.Snabbdom.Node
- Direction
- Sutil.Bindings uses Feliz.Snabbdom, so a change to Feliz.Snabbdom can break Sutil.Bindings, while a change to Sutil.Bindings can't break Feliz.Snabbdom.
- Position
- Below the diagonal: Sutil.Bindings uses a module listed above it, which is the healthy direction.
32→13 Sutil.Bindings uses Monaco✕
- Connections
- 1 pair of types, where a type in Sutil.Bindings uses a type in Monaco.
- The types involved
Sutil.Bindings.Bindings→Monaco.Promise
- Direction
- Sutil.Bindings uses Monaco, so a change to Monaco can break Sutil.Bindings, while a change to Sutil.Bindings can't break Monaco.
- Position
- Below the diagonal: Sutil.Bindings uses a module listed above it, which is the healthy direction.
32→14 Sutil.Bindings uses Sutil.DOM✕
- Connections
- 2 pairs of types, where a type in Sutil.Bindings uses a type in Sutil.DOM.
- The types involved
Sutil.Bindings.Bindings→Sutil.DOM.SutilElementSutil.Bindings.KeyedStoreItem→Sutil.DOM.SutilNode
- Direction
- Sutil.Bindings uses Sutil.DOM, so a change to Sutil.DOM can break Sutil.Bindings, while a change to Sutil.Bindings can't break Sutil.DOM.
- Position
- Below the diagonal: Sutil.Bindings uses a module listed above it, which is the healthy direction.
32→22 Sutil.Bindings uses Sutil.ObservablePromise✕
- Connections
- 1 pair of types, where a type in Sutil.Bindings uses a type in Sutil.ObservablePromise.
- The types involved
Sutil.Bindings.Bindings→Sutil.ObservablePromise.ObservablePromise
- Direction
- Sutil.Bindings uses Sutil.ObservablePromise, so a change to Sutil.ObservablePromise can break Sutil.Bindings, while a change to Sutil.Bindings can't break Sutil.ObservablePromise.
- Position
- Below the diagonal: Sutil.Bindings uses a module listed above it, which is the healthy direction.
32→25 Sutil.Bindings uses Sutil.Store✕
- Connections
- 1 pair of types, where a type in Sutil.Bindings uses a type in Sutil.Store.
- The types involved
Sutil.Bindings.Bindings→Sutil.Store.Store
- Direction
- Sutil.Bindings uses Sutil.Store, so a change to Sutil.Store can break Sutil.Bindings, while a change to Sutil.Bindings can't break Sutil.Store.
- Position
- Below the diagonal: Sutil.Bindings uses a module listed above it, which is the healthy direction.
33→7 Sutil.Cmd.OfTask uses Sutil.Cmd✕
- Connections
- 1 pair of types, where a type in Sutil.Cmd.OfTask uses a type in Sutil.Cmd.
- The types involved
Sutil.Cmd.OfTask.OfTask→Sutil.Cmd.Cmd
- Direction
- Sutil.Cmd.OfTask uses Sutil.Cmd, so a change to Sutil.Cmd can break Sutil.Cmd.OfTask, while a change to Sutil.Cmd.OfTask can't break Sutil.Cmd.
- Position
- Below the diagonal: Sutil.Cmd.OfTask uses a module listed above it, which is the healthy direction.
33→27 Sutil.Cmd.OfTask uses Sutil.Transition.LoopTasks✕
- Connections
- 1 pair of types, where a type in Sutil.Cmd.OfTask uses a type in Sutil.Transition.LoopTasks.
- The types involved
Sutil.Cmd.OfTask.OfTask→Sutil.Transition.LoopTasks.Task
- Direction
- Sutil.Cmd.OfTask uses Sutil.Transition.LoopTasks, so a change to Sutil.Transition.LoopTasks can break Sutil.Cmd.OfTask, while a change to Sutil.Cmd.OfTask can't break Sutil.Transition.LoopTasks.
- Position
- Below the diagonal: Sutil.Cmd.OfTask uses a module listed above it, which is the healthy direction.
34→31 Elmish.Cmd uses Feliz.ReactEditor.Dispatch✕
- Connections
- 1 pair of types, where a type in Elmish.Cmd uses a type in Feliz.ReactEditor.Dispatch.
- The types involved
Elmish.Cmd.Cmd→Feliz.ReactEditor.Dispatch.Dispatch
- Direction
- Elmish.Cmd uses Feliz.ReactEditor.Dispatch, so a change to Feliz.ReactEditor.Dispatch can break Elmish.Cmd, while a change to Elmish.Cmd can't break Feliz.ReactEditor.Dispatch.
- Position
- Below the diagonal: Elmish.Cmd uses a module listed above it, which is the healthy direction.
35→29 Fable.Repl.Loader uses Fable.Repl.Main✕
- Connections
- 2 pairs of types, where a type in Fable.Repl.Loader uses a type in Fable.Repl.Main.
- The types involved
Fable.Repl.Loader.Model→Fable.Repl.Main.ModelFable.Repl.Loader.Msg→Fable.Repl.Main.Msg
- Direction
- Fable.Repl.Loader uses Fable.Repl.Main, so a change to Fable.Repl.Main can break Fable.Repl.Loader, while a change to Fable.Repl.Loader can't break Fable.Repl.Main.
- Position
- Below the diagonal: Fable.Repl.Loader uses a module listed above it, which is the healthy direction.
36→34 Elmish.Cmd.OfAsync uses Elmish.Cmd✕
- Connections
- 1 pair of types, where a type in Elmish.Cmd.OfAsync uses a type in Elmish.Cmd.
- The types involved
Elmish.Cmd.OfAsync.OfAsync→Elmish.Cmd.Cmd
- Direction
- Elmish.Cmd.OfAsync uses Elmish.Cmd, so a change to Elmish.Cmd can break Elmish.Cmd.OfAsync, while a change to Elmish.Cmd.OfAsync can't break Elmish.Cmd.
- Position
- Below the diagonal: Elmish.Cmd.OfAsync uses a module listed above it, which is the healthy direction.
37→34 Elmish.Cmd.OfAsyncImmediate uses Elmish.Cmd✕
- Connections
- 1 pair of types, where a type in Elmish.Cmd.OfAsyncImmediate uses a type in Elmish.Cmd.
- The types involved
Elmish.Cmd.OfAsyncImmediate.OfAsyncImmediate→Elmish.Cmd.Cmd
- Direction
- Elmish.Cmd.OfAsyncImmediate uses Elmish.Cmd, so a change to Elmish.Cmd can break Elmish.Cmd.OfAsyncImmediate, while a change to Elmish.Cmd.OfAsyncImmediate can't break Elmish.Cmd.
- Position
- Below the diagonal: Elmish.Cmd.OfAsyncImmediate uses a module listed above it, which is the healthy direction.
38→34 Elmish.Cmd.OfAsyncWith uses Elmish.Cmd✕
- Connections
- 1 pair of types, where a type in Elmish.Cmd.OfAsyncWith uses a type in Elmish.Cmd.
- The types involved
Elmish.Cmd.OfAsyncWith.OfAsyncWith→Elmish.Cmd.Cmd
- Direction
- Elmish.Cmd.OfAsyncWith uses Elmish.Cmd, so a change to Elmish.Cmd can break Elmish.Cmd.OfAsyncWith, while a change to Elmish.Cmd.OfAsyncWith can't break Elmish.Cmd.
- Position
- Below the diagonal: Elmish.Cmd.OfAsyncWith uses a module listed above it, which is the healthy direction.
39→34 Elmish.Cmd.OfFunc uses Elmish.Cmd✕
- Connections
- 1 pair of types, where a type in Elmish.Cmd.OfFunc uses a type in Elmish.Cmd.
- The types involved
Elmish.Cmd.OfFunc.OfFunc→Elmish.Cmd.Cmd
- Direction
- Elmish.Cmd.OfFunc uses Elmish.Cmd, so a change to Elmish.Cmd can break Elmish.Cmd.OfFunc, while a change to Elmish.Cmd.OfFunc can't break Elmish.Cmd.
- Position
- Below the diagonal: Elmish.Cmd.OfFunc uses a module listed above it, which is the healthy direction.
40→27 Elmish.Cmd.OfTask uses Sutil.Transition.LoopTasks✕
- Connections
- 1 pair of types, where a type in Elmish.Cmd.OfTask uses a type in Sutil.Transition.LoopTasks.
- The types involved
Elmish.Cmd.OfTask.OfTask→Sutil.Transition.LoopTasks.Task
- Direction
- Elmish.Cmd.OfTask uses Sutil.Transition.LoopTasks, so a change to Sutil.Transition.LoopTasks can break Elmish.Cmd.OfTask, while a change to Elmish.Cmd.OfTask can't break Sutil.Transition.LoopTasks.
- Position
- Below the diagonal: Elmish.Cmd.OfTask uses a module listed above it, which is the healthy direction.
40→34 Elmish.Cmd.OfTask uses Elmish.Cmd✕
- Connections
- 1 pair of types, where a type in Elmish.Cmd.OfTask uses a type in Elmish.Cmd.
- The types involved
Elmish.Cmd.OfTask.OfTask→Elmish.Cmd.Cmd
- Direction
- Elmish.Cmd.OfTask uses Elmish.Cmd, so a change to Elmish.Cmd can break Elmish.Cmd.OfTask, while a change to Elmish.Cmd.OfTask can't break Elmish.Cmd.
- Position
- Below the diagonal: Elmish.Cmd.OfTask uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
At a glance — Accessibility
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A05:2025 — Injection | 15 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 4 | High / Critical |
| A07:2025 — Authentication Failures | 2 | High / Critical |
| A02:2025 — Security Misconfiguration | 1 | 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. | +9.5 pts | Low | Test Distribution |
| Resolve the 1 No ADRs found finding(s) in ADR Quality. | +6.0 pts | Low | ADR Quality |
| Resolve the 1 No automated tests finding(s) in Code Coverage. | +9.5 pts | High | Code Coverage |
| Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them. | +4.2 pts | Medium | Architecture documentation |
| 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. | +4.0 pts | Medium | Observability |
| Resolve the 23 Orphaned file finding(s) in Knowledge Freshness — start with DOM.fs, Bindings.fs, HtmlEngine.fs. | +3.8 pts | Medium | Knowledge Freshness |
| Add a text alternative — alt on images (alt="" for purely decorative ones), a title or aria-label on meaningful svg, an aria-label or inner fallback content on canvas, and a captions <track> on video. | +3.2 pts | Medium | Text alternatives |
| Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href. | +3.2 pts | Medium | Keyboard semantics |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 0.4 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 1.4 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.0 | Slop | Secrets (history): High secret: REDACTED |
| src/Fable.Repl.Lib/Feliz.Engine/CssEngine.fs | 7.2 | Mixed | God Classes: TooManyMethods: CssEngine |
| src/App/Libs/Monaco.fs | 7.2 | Mixed | God Classes: FileTooLong: Libs/Monaco.fs |
| src/App/public/samples/fulma/breadcrumb.fs | 7.4 | Mixed | Code Duplication: Duplicated block (8 lines × 2) |
| src/Fable.Repl.Lib/Feliz.Engine/HtmlEngine.fs | 7.8 | Mixed | God Classes: TooManyMethods: HtmlEngine |
| src/Fable.Repl.Lib/Feliz.Engine/AttrEngine.fs | 7.8 | Mixed | God Classes: TooManyMethods: AttrEngine |
| src/App/Main.fs | 7.8 | Mixed | God Classes: FileTooLong: App/Main.fs |
| src/Fable.Repl.Lib/Elmish/cmd.fs | 7.8 | Mixed | Code Duplication: Duplicated block (99–109 lines × 2) |
| src/App/public/samples/ui/spreadsheet.fs | 7.8 | Mixed | Code Duplication: Duplicated block (82 lines × 2) |
| src/App/public/samples/fulma/content.fs | 7.8 | Mixed | Code Duplication: Duplicated block (23 lines × 2) |
| REDACTED | 7.9 | Mixed | IaC & Container Security: Medium IaC: REDACTED |
| src/Export/fcs-export.fsproj | 7.9 | Mixed | Platform End-of-Life: End-of-life runtime: .NET net5.0 |
| src/Fable.Repl.Lib/Feliz.Engine.Event/EventEngine.fs | 8.5 | Near-clean | God Classes: TooManyMethods: EventEngine |
| src/Fable.Repl.Lib/Sutil/DOM.fs | 8.5 | Near-clean | God Classes: FileTooLong: Sutil/DOM.fs |
| src/Fable.Repl.Lib/Feliz.Engine/SvgEngine.fs | 8.5 | Near-clean | God Classes: TooManyMethods: SvgEngine |
| src/Fable.Repl.Lib/Sutil/Bindings.fs | 8.5 | Near-clean | God Classes: TooManyFunctions: Bindings |
| src/Fable.Repl.Lib/Sutil/Transition.fs | 8.5 | Near-clean | God Classes: TooManyFunctions: Transition |
| src/App/Widgets/General.fs | 8.5 | Near-clean | Code Duplication: Duplicated block (31–33 lines × 2) |
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. 42 of 42 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); none rely on LLM judgement. Overall confidence is 0.7 — 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 — 42 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, 116 of 130 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 · checkov | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 · 3.2.533 | ✓ 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. 42 of 42 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.
- D12 Dependency Hygiene — 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. `dotnet list package` did not return usable output (restore or query failed); no outdated/vulnerable/deprecated data to assess. The tool said: .paket/Paket.Restore.targets(171,5): error MSB3073: The command "dotnet paket restore" exited with code 1. [src/App/App.fsproj].
- D14 License Compliance — 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. This repository declares package.json, but the licence verdict published here was taken over its NuGet package dependencies. Nothing was read about its npm dependencies' licensing in either direction, and a clean score on this card must not be read as covering them.
- 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 (6 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.
- D19 Documentation Quality — 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. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
- 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 — 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. D22 identifies the intentionally-exposed surface from `IsPackable` and `.Contracts` project names, MSBuild conventions read off the loaded project set. This target exposed no such projects, so the probe never ran; this says nothing about whether the repository has a public API. This repository commits no C#/VB source at all, so there was never an MSBuild project set to read these conventions off. That is OUR side and it is a COLLECTOR gap, not an environment fault: no published-package marker D22 reads admitted any project here, so this ecosystem's public API has no collector, and the remedy is to write one — no change to the scan image can close it.
- D24 Comment Value — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
- D30 Dependency Vulnerabilities — measured, with a gap in what it reached — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. The 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. 2 of 3 declared ecosystem(s) (npm,osv) WERE scanned and every vulnerability they reported is included in this result; nuget was not, so this dimension's score covers less than the dependency surface this repository declares, and nothing here is evidence that nuget is free of known-vulnerable dependencies.
- D39 IL Efficiency — 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. IL NOT MEASURED: the analyzer's own build of this repository failed for an ENVIRONMENT reason (exit 1) — MSBuild's engine or the CLR gave up, or our image does not carry the SDK band/targeting pack this repository needs. This is OUR limitation, not a defect in the repo, and it is not a statement that this repository fails to build. D18 owns the question of whether this repository builds; it was not answered here.
- AC1 Text alternatives — 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. This repository renders user interface from a TEMPLATE LANGUAGE or a host-language HTML BUILDER — 6 Sutil (F#)/Feliz (F#) template file(s) carrying 27 markup element(s) (e.g. src/Fable.Repl.Lib/Sutil/Styling.fs, src/Fable.Repl.Lib/Sutil/Transition.fs, src/Fable.Repl.Lib/Feliz.Engine/AttrEngine.fs) — and the accessibility cards on this run were measured over the 14 parsed markup document(s) ONLY. The markup model reads .html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx, html`…` templates and DOM-assigned HTML strings in .ts/.js, the .erb/.ejs/.eex/.heex/.leex/.twig/.jinja/.j2/.liquid/.njk/.hbs/.mustache/.blade.php/.gohtml template languages, .astro/.templ/.pug/.jade/.haml/.slim, and the kotlinx.html/Compose HTML/kotlin-react, Giraffe/Falco/Fable.React/Feliz/Bolero and Jaspr builder DSLs; 6 of the file(s) above import an HTML builder DSL whose element calls it did not project — a builder it has no reader for, or calls in a shape its reader does not know — so those views were not merely unparsed but unenumerated: not one of their elements entered the population any card scored. Their absence from the counts above is a gap in this analyzer's frontend coverage — not a finding that they carry text alternatives, labels, keyboard semantics or correct ARIA.
- AC2 Forms & labels — 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. This repository renders user interface from a TEMPLATE LANGUAGE or a host-language HTML BUILDER — 6 Sutil (F#)/Feliz (F#) template file(s) carrying 27 markup element(s) (e.g. src/Fable.Repl.Lib/Sutil/Styling.fs, src/Fable.Repl.Lib/Sutil/Transition.fs, src/Fable.Repl.Lib/Feliz.Engine/AttrEngine.fs) — and the accessibility cards on this run were measured over the 14 parsed markup document(s) ONLY. The markup model reads .html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx, html`…` templates and DOM-assigned HTML strings in .ts/.js, the .erb/.ejs/.eex/.heex/.leex/.twig/.jinja/.j2/.liquid/.njk/.hbs/.mustache/.blade.php/.gohtml template languages, .astro/.templ/.pug/.jade/.haml/.slim, and the kotlinx.html/Compose HTML/kotlin-react, Giraffe/Falco/Fable.React/Feliz/Bolero and Jaspr builder DSLs; 6 of the file(s) above import an HTML builder DSL whose element calls it did not project — a builder it has no reader for, or calls in a shape its reader does not know — so those views were not merely unparsed but unenumerated: not one of their elements entered the population any card scored. Their absence from the counts above is a gap in this analyzer's frontend coverage — not a finding that they carry text alternatives, labels, keyboard semantics or correct ARIA.
- AC3 Page structure — 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. This repository renders user interface from a TEMPLATE LANGUAGE or a host-language HTML BUILDER — 6 Sutil (F#)/Feliz (F#) template file(s) carrying 27 markup element(s) (e.g. src/Fable.Repl.Lib/Sutil/Styling.fs, src/Fable.Repl.Lib/Sutil/Transition.fs, src/Fable.Repl.Lib/Feliz.Engine/AttrEngine.fs) — and the accessibility cards on this run were measured over the 14 parsed markup document(s) ONLY. The markup model reads .html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx, html`…` templates and DOM-assigned HTML strings in .ts/.js, the .erb/.ejs/.eex/.heex/.leex/.twig/.jinja/.j2/.liquid/.njk/.hbs/.mustache/.blade.php/.gohtml template languages, .astro/.templ/.pug/.jade/.haml/.slim, and the kotlinx.html/Compose HTML/kotlin-react, Giraffe/Falco/Fable.React/Feliz/Bolero and Jaspr builder DSLs; 6 of the file(s) above import an HTML builder DSL whose element calls it did not project — a builder it has no reader for, or calls in a shape its reader does not know — so those views were not merely unparsed but unenumerated: not one of their elements entered the population any card scored. Their absence from the counts above is a gap in this analyzer's frontend coverage — not a finding that they carry text alternatives, labels, keyboard semantics or correct ARIA.
- AC4 Keyboard semantics — 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. This repository renders user interface from a TEMPLATE LANGUAGE or a host-language HTML BUILDER — 6 Sutil (F#)/Feliz (F#) template file(s) carrying 27 markup element(s) (e.g. src/Fable.Repl.Lib/Sutil/Styling.fs, src/Fable.Repl.Lib/Sutil/Transition.fs, src/Fable.Repl.Lib/Feliz.Engine/AttrEngine.fs) — and the accessibility cards on this run were measured over the 14 parsed markup document(s) ONLY. The markup model reads .html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx, html`…` templates and DOM-assigned HTML strings in .ts/.js, the .erb/.ejs/.eex/.heex/.leex/.twig/.jinja/.j2/.liquid/.njk/.hbs/.mustache/.blade.php/.gohtml template languages, .astro/.templ/.pug/.jade/.haml/.slim, and the kotlinx.html/Compose HTML/kotlin-react, Giraffe/Falco/Fable.React/Feliz/Bolero and Jaspr builder DSLs; 6 of the file(s) above import an HTML builder DSL whose element calls it did not project — a builder it has no reader for, or calls in a shape its reader does not know — so those views were not merely unparsed but unenumerated: not one of their elements entered the population any card scored. Their absence from the counts above is a gap in this analyzer's frontend coverage — not a finding that they carry text alternatives, labels, keyboard semantics or correct ARIA.
- AC5 ARIA 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 repository renders user interface from a TEMPLATE LANGUAGE or a host-language HTML BUILDER — 6 Sutil (F#)/Feliz (F#) template file(s) carrying 27 markup element(s) (e.g. src/Fable.Repl.Lib/Sutil/Styling.fs, src/Fable.Repl.Lib/Sutil/Transition.fs, src/Fable.Repl.Lib/Feliz.Engine/AttrEngine.fs) — and the accessibility cards on this run were measured over the 14 parsed markup document(s) ONLY. The markup model reads .html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx, html`…` templates and DOM-assigned HTML strings in .ts/.js, the .erb/.ejs/.eex/.heex/.leex/.twig/.jinja/.j2/.liquid/.njk/.hbs/.mustache/.blade.php/.gohtml template languages, .astro/.templ/.pug/.jade/.haml/.slim, and the kotlinx.html/Compose HTML/kotlin-react, Giraffe/Falco/Fable.React/Feliz/Bolero and Jaspr builder DSLs; 6 of the file(s) above import an HTML builder DSL whose element calls it did not project — a builder it has no reader for, or calls in a shape its reader does not know — so those views were not merely unparsed but unenumerated: not one of their elements entered the population any card scored. Their absence from the counts above is a gap in this analyzer's frontend coverage — not a finding that they carry text alternatives, labels, keyboard semantics or correct ARIA.
- AC6 Visual & motion safety — 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. This repository renders user interface from a TEMPLATE LANGUAGE or a host-language HTML BUILDER — 6 Sutil (F#)/Feliz (F#) template file(s) carrying 27 markup element(s) (e.g. src/Fable.Repl.Lib/Sutil/Styling.fs, src/Fable.Repl.Lib/Sutil/Transition.fs, src/Fable.Repl.Lib/Feliz.Engine/AttrEngine.fs) — and the accessibility cards on this run were measured over the 14 parsed markup document(s) ONLY. The markup model reads .html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx, html`…` templates and DOM-assigned HTML strings in .ts/.js, the .erb/.ejs/.eex/.heex/.leex/.twig/.jinja/.j2/.liquid/.njk/.hbs/.mustache/.blade.php/.gohtml template languages, .astro/.templ/.pug/.jade/.haml/.slim, and the kotlinx.html/Compose HTML/kotlin-react, Giraffe/Falco/Fable.React/Feliz/Bolero and Jaspr builder DSLs; 6 of the file(s) above import an HTML builder DSL whose element calls it did not project — a builder it has no reader for, or calls in a shape its reader does not know — so those views were not merely unparsed but unenumerated: not one of their elements entered the population any card scored. Their absence from the counts above is a gap in this analyzer's frontend coverage — not a finding that they carry text alternatives, labels, keyboard semantics or correct ARIA.
- 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.
- AXR1 Runtime accessibility — 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. Render strategy: boot via REDACTED (REDACTED). docker build failed (exit 1) — ------ REDACTED:1 -------------------- 1 | >>> FROM gitpod/workspace-full:latest 2 | 3 | USER root -------------------- ERROR: failed to solve: failed to register layer: write /home/gitpod/.sdkman/candidates/java/11.0.28.fx-zulu/lib/libjfxwebkit.so: no space left on device; runtime evidence skipped.
- 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.
- 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.
- 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.
- Package restore incomplete — third-party types were unresolved in part of the solution — NuGet restore did not complete for src/App/App.fsproj, so those projects were analysed with framework references only: every check keyed on a third-party type saw an error type there and reported nothing. Findings on those projects are a lower bound; run `dotnet restore` on them and rescan.
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.
- 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.
- D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- 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").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a REDACTED (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- AC1 Text alternatives: Alt-text is detected structurally — the scan sees that an alternative EXISTS, not whether it meaningfully describes the image, and decorative-vs-missing is judged by attribute shape; runtime-injected images and a non-role=img decorative svg are out of scope. This is accessibility readiness, never a WCAG conformance claim.
- AC2 Forms & labels: Label association is read from static markup — a label wired up at runtime (JS-set aria-labelledby, framework-injected ids) reads as missing, a present label says nothing about whether its text is correct. A known UI-library field component (e.g. a JSX <TextField>) is now checked conservatively — flagged only when it carries NO label/aria-label/aria-labelledby/id/name — but wrapper/context-labelled libraries (Chakra/Radix FormControl+FormLabel) aren't statically visible (possible false positive) and non-JSX lowercased components are still skipped. A click handler on a plain element is now asked for a name too (it is a control the author declared), but the subtree test that answers it is deliberately generous: any DYNAMIC text expression in the subtree counts as a name, so an icon chosen by a ternary ({cond ? <IconA/> : <IconB/>}) reads as named, and a glyph component from a library the icon-import list does not know still names its parent. A clean result is "no unlabelled control found", not a labelling proof.
- AC3 Page structure: Page structure is read from the static markup tree — landmarks, headings and lang injected at runtime aren't seen, heading ORDER is checked structurally (not against the rendered visual hierarchy), and lang/title/main fire only on full documents, never partials, and the data-table check sees header-cell presence (a <th> exists), not whether each header correctly associates with its cells. Static readiness, not conformance.
- AC4 Keyboard semantics: Keyboard semantics are inferred from markup attributes — interactivity wired purely in script, focus managed at runtime, and component-level handlers are invisible. A clean result means "no static keyboard-trap shape", not a keyboard-operability proof.
- AC6 Visual & motion safety: Contrast and motion safety are PARTIAL by construction — literal colours (hex/rgb/hsl/named) in inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS top-level declarations are read (same-rule/same-element colour+background pairs only); computed/runtime/theme colour, external-CDN stylesheets, CSS-in-JS dynamic (${…}) and nested-selector colours, cross-element pairs and image contrast stay out of reach, so a clean result is bounded by what the static CSS itself shows.
- AC7 A11y enforcement: Enforcement is scored from in-repo config/CI evidence only — an a11y gate enforced in external tooling with no in-repo trace can't be credited, and a configured linter is presence, not proof the rules actually run or block a merge.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
- P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
Dimensions
D3 · God Classes
14 god class(es) detected.
What to do
- Resolve the 7 TooManyMethods finding(s) in God Classes — start with CssEngine.fs (3), HtmlEngine.fs, AttrEngine.fs. — One of this dimension's main actionable groups (7 warning-level).
- Resolve the 5 FileTooLong finding(s) in God Classes — start with Monaco.fs, CssEngine.fs, DOM.fs. — One of this dimension's main actionable groups (5 warning-level).
- Resolve the 2 TooManyFunctions finding(s) in God Classes — start with Bindings.fs, Transition.fs. — One of this dimension's main actionable groups (2 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
26 duplicated block group(s) detected. 17 of the 26 are in trees this repository does not ship — vendored, example/demo, project-template, fixture and benchmark code — and are ranked below the shipped groups rather than excluded from them: the duplication there is real and is still counted in this dimension's score. The dimensions that publish a production-file census leave those trees out of theirs, so this count is deliberately drawn over the wider population.
What to do
- Resolve the 2 Duplicated block (8 lines × 2) finding(s) in Code Duplication — start with Main.fs, breadcrumb.fs. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 2 Duplicated block (6 lines × 2) finding(s) in Code Duplication — start with HtmlEngine.fs, recharts.fs. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 2 Duplicated block (13 lines × 2) finding(s) in Code Duplication — start with card.fs, modal.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
11 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).
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D14 · License Compliance
0 of 114 packages use a banned license. ★ DEPTH: this repository's MSBuild projects declare 13 direct `PackageReference`(s), and 93 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. ★ COVERAGE OF THIS VERDICT: it grades this repository's NuGet package dependencies and nothing else. The repository also declares package.json, and the licences of those dependencies were NOT read by this pass — a gap in this engine's coverage, not a statement about them. So this result says the graded closure carries no banned licence; it does NOT say this repository's licensing is clear.
D16 · Bus Factor
2 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is src/App/Main.fs. Counted over 39 of the 58 production source files in this repository: 18 are under the ~2,400-byte size floor this dimension measures over, and the remaining 1 have no attributable history left to measure.
D19 · Documentation Quality
1 of 1 documentation facets pass in full. 1 document(s) read across 1 unit(s).
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 9 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)
1 finding(s): 0 critical, 1 high, 0 medium, 0 low. Remediation for historically-committed secrets is credential rotation — they remain in history regardless of later deletion.
What to do
- Resolve the 1 High secret finding(s) in Secrets (history) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 1 Rotate the exposed credentials finding(s) in Secrets (history). — One of this dimension's main actionable groups (1 recommendation-level).
D29 · Static Analysis (SAST)
15 finding(s): 0 critical, 8 high, 7 medium, 0 low. 7 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. semgrep hit a parse error in 1 file(s) — `src/App/fonts/firacode/specimen.html` (lines 2–65) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them.
What to do
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 3 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (3). — One of this dimension's main actionable groups (3 warning-level).
- No action in Static Analysis (SAST) — all 7 REDACTED finding(s) are reported here at file:line but scored by D36 (supply-chain provenance), so none is charged to this dimension. — One of this dimension's main actionable groups (7 issue-level, 0 of them charged here).
D30 · Dependency Vulnerabilities
4 finding(s): 0 critical, 2 high, 2 medium, 0 low. Partial dependency scan: 2 of 3 declared ecosystem(s) were scanned (npm,osv), and the findings above are real and complete for them. nuget was not scanned (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), so this is not the whole dependency surface and the result is reported at reduced confidence.
What to do
- Resolve the 2 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
- Resolve the 2 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (2). — One of this dimension's main actionable groups (2 warning-level).
D31 · IaC & Container Security
1 finding(s): 0 critical, 0 high, 1 medium, 0 low.
What to do
- Resolve the 1 Medium IaC finding(s) in IaC & Container Security — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
D34 · Knowledge Freshness
26 of 40 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is src/App/Libs/Monaco.fs. Counted over 40 of the 58 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
What to do
- Resolve the 23 Orphaned file finding(s) in Knowledge Freshness — start with DOM.fs, Bindings.fs, HtmlEngine.fs. — One of this dimension's main actionable groups (23 recommendation-level).
- Resolve the 3 Most significant orphaned file finding(s) in Knowledge Freshness — start with Monaco.fs, CssEngine.fs, AttrEngine.fs. — One of this dimension's main actionable groups (3 recommendation-level).
- Resolve the 1 Concentrated knowledge decay finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
D35 · Change Coupling
No strong hidden change-coupling between production files.
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
D44 · Platform End-of-Life
1 end-of-life runtime(s) and 0 end-of-life framework(s), read from 11 platform declaration(s) and 19 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
What to do
- Resolve the 1 End-of-life runtime finding(s) in Platform End-of-Life — start with fcs-export.fsproj. — One of this dimension's main actionable groups (1 warning-level).
Frontend & cross-cutting dimensions
AC1 · Text alternatives
- An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative. (×3) — src/App/Loader.fs:81, src/App/Sidebar.fs:242, src/App/Sidebar.fs:299
What to do
- Add a text alternative — alt on images (alt="" for purely decorative ones), a title or aria-label on meaningful svg, an aria-label or inner fallback content on canvas, and a captions <track> on video.
AC2 · Forms & labels
- This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it. (×2) — src/Fable.Repl.Lib/Sutil/Bulma.fs:21, src/Fable.Repl.Lib/Sutil/Bulma.fs:31
What to do
- Give every control a programmatic label (a <label for> / wrapping <label> / aria-label) and every button text — a placeholder is not a label.
AC3 · Page structure
- An iframe with no title (or an empty one) is announced only as "frame". Add a non-empty title describing its content, or an aria-label. — src/App/Main.fs:1012
- The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en"). (×2) — src/App/fonts/firacode/specimen.html:2, src/App/index.html:2
- No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>. — src/App/fonts/firacode/specimen.html:2
- No <main> (or role="main") means no "skip to content" target and a weaker landmark map. This document's body is only the mount point <div id="app-container">, so there is no content here to wrap — render the <main> from the component mounted into it. — src/App/index.html:2
What to do
- Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh.
AC4 · Keyboard semantics
- A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler. (×7) — src/App/Main.fs:708, src/App/Main.fs:719, src/App/Main.fs:730, …
- An <a> with no href, role or tabindex isn't focusable or keyboard-activatable. Give it a real href, or use a <button> for an action. (×7) — src/App/Main.fs:713, src/App/Main.fs:724, src/App/Main.fs:735, …
What to do
- Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href.
AC6 · Visual & motion safety
AC7 · A11y enforcement
- No accessibility enforcement found — no a11y linter (eslint-plugin-jsx-a11y) and no axe/pa11y/Lighthouse in tests or CI. Start with the linter to catch issues at author time. What was searched, so you can tell an absence from a miss: the 14 markup file(s) this pass actually assessed, the linter configuration checked in beside them, and this repository's test and CI files — matched by name against the accessibility checkers this dimension carries. An audit run outside the repository, a hosted scanner, or a check whose name is not one of those, is not seen here. — package.json:25
What to do
- Enforce accessibility in the toolchain: add eslint-plugin-jsx-a11y, then assert with your test runner's axe binding (jest-axe, vitest-axe, cypress-axe or @axe-core/playwright) in tests, then gate axe/pa11y/Lighthouse in CI.
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.
- No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
- Add a C4 context/container diagram (Structurizr, PlantUML or Mermaid) or an architecture.md overview.
M3 · Folder & project structure
What to do
- Start a test surface where your build system looks for one (tests/, test/, spec/, or your ecosystem's test source set) — the separation follows from putting the first tests in the right place.
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 1798 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.
- `src/App/public/samples/Samples.fsproj` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`. — src/App/public/samples/Samples.fsproj:72
What to do
- Add a SAST step to CI running what this repository's stack ships: `semgrep --config=auto` plus gitleaks for committed secrets (F# is not a CodeQL language and has no language-specific SAST engine) — so a security regression fails the build instead of landing.
- Enable Dependabot/Renovate or a dependency-review gate.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
What to do
- Nothing pauses a release for a human: publish as a draft release (or gate the release job on a protected tag/manual dispatch) so a bad build can be stopped before users can download it.
P6 · Release Hygiene
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
WCAG coverage — what static analysis assessed
| Dimension | WCAG 2.2 A/AA criteria | Coverage |
|---|---|---|
| AC1 · Text alternatives | 1.1.1, 1.2.2, 1.2.5 | Partial signal |
| AC2 · Forms & labels | 1.3.1, 3.3.2, 4.1.2 | Partial signal |
| AC3 · Page structure | 1.4.4, 2.2.1, 2.4.1, 2.4.2, 3.1.1, 4.1.2 | Partial signal |
| AC4 · Keyboard semantics | 2.1.1, 2.4.3 | Partial signal |
| AC6 · Visual & motion safety | 1.4.3, 2.4.7 | Partial — literal CSS only |
| AC7 · A11y enforcement | enforcement — no page criterion | Enforcement posture (process) |
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 88% | Strong | Solid. |
| Architecture | 97% | Exemplary | Solid. |
| Maturity | 44% | Weak — gated by D34, M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 26% | Weak — gated by D8, D9, P2, P3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 82% | Strong | Solid. |
| Accessibility | 28% | Weak — gated by AC1, AC3, AC4 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Performance | 100% | Exemplary | Strongest area. |
Unscored — 2 check(s) recorded observations but carry no score
- D36 Supply-chain Provenance & Signing — 2 observation(s) recorded · The CI pipeline builds and tests but publishes no released artifact — no package publish, container push, GitHub release or deployment step. Supply-chain provenance, signing and SBOM attest RELEASED artifacts, so there is nothing to attest here. Add them to the release pipeline when this repo starts shipping artifacts (a published package, a container image, a deployed service or a tagged release). Build integrity and workflow-token hygiene are reported below: they describe what the CI runs and the token it runs with, neither of which is affected by whether the pipeline ships an artifact.
- 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 — 72 check(s) not relevant to this codebase
- AC5 ARIA correctness — AC5 could not be measured here. This repository renders user interface from a template language — 6 Sutil (F#)/Feliz (F#) template file(s) carrying 27 markup element(s) (e.g. src/Fable.Repl.Lib/Sutil/Styling.fs, src/Fable.Repl.Lib/Sutil/Transition.fs, src/Fable.Repl.Lib/Feliz.Engine/AttrEngine.fs) — which this analyzer's markup model does not read (it reads .html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx, html`…` templates and DOM-assigned HTML strings in .ts/.js, the .erb/.ejs/.eex/.heex/.leex/.twig/.jinja/.j2/.liquid/.njk/.hbs/.mustache/.blade.php/.gohtml template languages, .astro/.templ/.pug/.jade/.haml/.slim, and the kotlinx.html/Compose HTML/kotlin-react, Giraffe/Falco/Fable.React/Feliz/Bolero and Jaspr builder DSLs), so no ARIA usage from it could enter the population. The parsed markup carried none either, but that is a gap in our frontend coverage, NOT a statement that this repository has no ARIA usage.
- AX1 Captive dependencies — Not applicable: this repository's F# imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's; this repository's JavaScript imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's.
- AX2 Stateful singletons — 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
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXR1 Runtime accessibility — docker build failed (exit 1) — ------ REDACTED:1 -------------------- 1 | >>> FROM gitpod/workspace-full:latest 2 | 3 | USER root -------------------- ERROR: failed to solve: failed to register layer: write /home/gitpod/.sdkman/candidates/java/11.0.28.fx-zulu/lib/libjfxwebkit.so: no space left on device; runtime evidence skipped This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
- 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.
- D12 Dependency Hygiene — Dependency hygiene not measured
- D15 Churn × Complexity Hotspots — complexity unreadable for .fs — churn × complexity hotspots could not be measured
- 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.
- 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#, JavaScript not measured.
- D22 Internal API Consistency — The exposed public-API surface could not be collected — no C#/VB projects loaded.
- 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.
- 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 analyzer's build of the target did not succeed
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D6 Cohesion (LCOM4) — cohesion (LCOM4) 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): 60 value object(s); 4 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
- M4 Documentation accuracy — Not applicable: the 1 current-state document(s) make no claim of a kind M4 checks. 1 claim(s) of kinds M4 does not check were not checked (environment variable 1); M4 checks only links and versions and artefact counts.
- P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
- P7 Outbound HTTP resilience — not measured — the application kind could not be determined for this repo
- P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
- P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (Cobertura — `dotnet test --collect:"XPlat Code Coverage"` with a `coverlet.collector` PackageReference) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures, or wire coverage collection into CI, to enable this cross-layer check
- PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for a BenchmarkDotNet reference in an .fsproj or .vbproj, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
- PF2 Allocation hygiene — Not applicable: allocation awareness is rated where code engineers for it — at least 400 production lines that ship benchmarks or already use allocation-aware idioms (8 or more). This repository's F# code has 21,310 production line(s), 2 such use(s) and no benchmarks, so there is no allocation work to rate. The card is reward-only: its absence costs nothing.
- 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 — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X7 Silent fallback defaults — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
Critical — 27 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Click handler on a non-interactive <li> src/App/Main.fs:708
- Click handler on a non-interactive <li> src/App/Main.fs:719
- Click handler on a non-interactive <li> src/App/Main.fs:730
- Click handler on a non-interactive <li> src/App/Main.fs:979
- Click handler on a non-interactive <li> src/App/Main.fs:992
- <img> without a text alternative src/App/Loader.fs:81
- <img> without a text alternative src/App/Sidebar.fs:242
- <img> without a text alternative src/App/Sidebar.fs:299
- <select> without a programmatic label src/Fable.Repl.Lib/Sutil/Bulma.fs:21
- <select> without a programmatic label src/Fable.Repl.Lib/Sutil/Bulma.fs:31
- <html> without a lang src/App/fonts/firacode/specimen.html:2
- <html> without a lang src/App/index.html:2
- Click handler on a non-interactive <div> src/App/Main.fs:778
- Click handler on a non-interactive <div> src/App/Main.fs:820
- REDACTED
- REDACTED
- <iframe> without a title src/App/Main.fs:1012
- REDACTED
- REDACTED
- No automated tests
Serious — 65 finding(s)
- Anchor without href src/App/Main.fs:713
- Anchor without href src/App/Main.fs:724
- Anchor without href src/App/Main.fs:735
- Anchor without href src/App/Main.fs:986
- Anchor without href src/App/Main.fs:999
- Anchor without href src/App/Widgets/Samples.fs:202
- Anchor without href src/App/Widgets/Samples.fs:212
- TooManyMethods: HtmlEngine src/Fable.Repl.Lib/Feliz.Engine/HtmlEngine.fs:5
- TooManyMethods: AttrEngine src/Fable.Repl.Lib/Feliz.Engine/AttrEngine.fs:6
- TooManyMethods: CssEngine src/Fable.Repl.Lib/Feliz.Engine/CssEngine.fs:107
- TooManyMethods: EventEngine src/Fable.Repl.Lib/Feliz.Engine.Event/EventEngine.fs:13
- TooManyMethods: SvgEngine src/Fable.Repl.Lib/Feliz.Engine/SvgEngine.fs:5
- TooManyMethods: length src/Fable.Repl.Lib/Feliz.Engine/CssEngine.fs:2828
- TooManyMethods: transform src/Fable.Repl.Lib/Feliz.Engine/CssEngine.fs:3020
- FileTooLong: Libs/Monaco.fs src/App/Libs/Monaco.fs
- FileTooLong: Feliz.Engine/CssEngine.fs src/Fable.Repl.Lib/Feliz.Engine/CssEngine.fs
- FileTooLong: Sutil/DOM.fs src/Fable.Repl.Lib/Sutil/DOM.fs
- FileTooLong: App/Main.fs src/App/Main.fs
- FileTooLong: Feliz.Engine/AttrEngine.fs src/Fable.Repl.Lib/Feliz.Engine/AttrEngine.fs
- REDACTED
- REDACTED
- REDACTED
- Page without a main landmark src/App/fonts/firacode/specimen.html:2
- Page without a main landmark src/App/index.html:2
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- TooManyFunctions: Bindings src/Fable.Repl.Lib/Sutil/Bindings.fs:2
- TooManyFunctions: Transition src/Fable.Repl.Lib/Sutil/Transition.fs:1
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Duplicated block (8 lines × 2) src/App/Main.fs:864
- Duplicated block (8 lines × 2) src/App/public/samples/fulma/breadcrumb.fs:19
- Duplicated block (6 lines × 2) src/Fable.Repl.Lib/Feliz.Engine/HtmlEngine.fs:11
- Duplicated block (6 lines × 2) src/App/public/samples/visual/recharts.fs:9
- Duplicated block (13 lines × 2) src/App/public/samples/fulma/card.fs:14
- Duplicated block (13 lines × 2) src/App/public/samples/fulma/modal.fs:57
- Accessibility enforcement below the top rung package.json:25
- REDACTED
- Duplicated block (99–109 lines × 2) src/Fable.Repl.Lib/Elmish/cmd.fs:80
- Duplicated block (31–33 lines × 2) src/App/Widgets/General.fs:171
- Duplicated block (18–27 lines × 2) src/Fable.Repl.Lib/Elmish/cmd.fs:239
- Duplicated block (14 lines × 2) src/App/Libs/Monaco.fs:2068
- Duplicated block (8–11 lines × 2) src/App/Libs/Monaco.fs:738
- Duplicated block (5 lines × 2) src/App/Libs/Monaco.fs:3295
- Duplicated block (7 lines × 2) src/Fable.Repl.Lib/Sutil/Styling.fs:75
- Duplicated block (82 lines × 2) src/App/public/samples/ui/spreadsheet.fs:48
- Duplicated block (40–42 lines × 2) src/App/public/samples/ui/spreadsheet.fs:8
- Duplicated block (23 lines × 2) src/App/public/samples/fulma/content.fs:8
- Duplicated block (22 lines × 3) src/App/public/samples/fulma/content.fs:9
- Duplicated block (20 lines × 2) src/App/public/samples/fulma/navbar.fs:10
- Duplicated block (18 lines × 3) src/App/public/samples/fulma/table.fs:10
- Duplicated block (17 lines × 3) src/App/public/samples/fulma/pagination.fs:9
- Duplicated block (12 lines × 2) src/App/public/samples/games/ants.fs:268
- Duplicated block (9 lines × 3) src/App/public/samples/fulma/tabs.fs:10
- Duplicated block (7–8 lines × 5) src/App/public/samples/fulma/hero.fs:22
- Duplicated block (5 lines × 3) src/App/public/samples/fulma/notification.fs:23
- Duplicated block (8 lines × 3) src/App/public/samples/fulma/breadcrumb.fs:10
- Duplicated block (4–5 lines × 6) src/App/public/samples/fulma/breadcrumb.fs:60
- End-of-life runtime: .NET net5.0 src/Export/fcs-export.fsproj:5
- No structured logging
- NuGet dependencies are not locked
Minor — 38 finding(s)
- Orphaned file src/Fable.Repl.Lib/Sutil/DOM.fs:1
- Orphaned file src/Fable.Repl.Lib/Sutil/Bindings.fs:1
- Orphaned file src/Fable.Repl.Lib/Feliz.Engine/HtmlEngine.fs:1
- Orphaned file src/Fable.Repl.Lib/Sutil/Transition.fs:1
- Orphaned file src/Fable.Repl.Lib/Feliz.Engine.Event/EventEngine.fs:1
- Orphaned file src/Fable.Repl.Lib/Sutil/Store.fs:1
- Orphaned file src/Fable.Repl.Lib/Elmish.Snabbdom/Elmish.Snabbdom.HMR.fs:1
- Orphaned file src/Fable.Repl.Lib/Elmish/cmd.fs:1
- Orphaned file src/Fable.Repl.Lib/Sutil/ObservableStore.fs:1
- Orphaned file src/Fable.Repl.Lib/Sutil/Types.fs:1
- Orphaned file src/Fable.Repl.Lib/Sutil/TransitionFunctions.fs:1
- Orphaned file src/Fable.Repl.Lib/Promise/Promise.fs:1
- Orphaned file src/Fable.Repl.Lib/Feliz.Snabbdom/Feliz.Snabbdom.fs:1
- Orphaned file src/Fable.Repl.Lib/Elmish/program.fs:1
- Orphaned file src/Fable.Repl.Lib/Sutil/Easing.fs:1
- Orphaned file src/Fable.Repl.Lib/Feliz.Engine/SvgEngine.fs:1
- Orphaned file src/Fable.Repl.Lib/Elmish.Snabbdom/Elmish.Snabbdom.fs:1
- Orphaned file src/Fable.Repl.Lib/Sutil/Styling.fs:1
- Orphaned file src/Fable.Repl.Lib/Sutil/Observable.fs:1
- Orphaned file src/Export/Program.fs:1
- Orphaned file src/Fable.Repl.Lib/Sutil/Attr.fs:1
- Orphaned file src/Fable.Repl.Lib/Sutil/Html.fs:1
- Orphaned file src/Fable.Repl.Lib/Sutil/ResizeObserver.fs:1
- Most significant orphaned file src/App/Libs/Monaco.fs:1
- Most significant orphaned file src/Fable.Repl.Lib/Feliz.Engine/CssEngine.fs:1
- Most significant orphaned file src/Fable.Repl.Lib/Feliz.Engine/AttrEngine.fs:1
- Off-boarding risk: anonymized user #1
- Further sole-owners (lower concentration)
- No ADRs found
- Projects may be oversized for their cohesion
- REDACTED
- Concentrated knowledge decay
- REDACTED
- No tests found
- No ADRs
- No architecture diagram/doc
- No SAST
- No dependency-update automation src/App/public/samples/Samples.fsproj:72
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-1611e44266d84af7bbe3de2d403fe361/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-1611e44266d84af7bbe3de2d403fe361/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 . | 15 | 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 | — |
| D30 · Dependency Vulnerabilities | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . --skip-db-update | 4 | artifacts/raw/trivy-fs.json |
| D31 · IaC & Container Security | trivy | — | trivy config --format json --quiet . | 1 | artifacts/raw/trivy-config.json |
| 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 | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . --skip-db-update | 0 | artifacts/raw/trivy-fs.json |