Executive summary
davedawkins/sutil-oxide falls short of our standard for production, in part because it has controls that only work with a mouse. It scores 38 out of 100 and is rated Weak, and 55 of its 75 critical findings are security problems.
Accessibility, at 28, is the weakest lens, level with Production Readiness, and counts most in the score. The best first step is adding automated tests, worth about 8 points. Replacing the two exposed passwords or keys and switching the old ones off comes next, worth about 5 points. Raising Accessibility to 70 would lift the score to about 46.
Fifty known security holes in the packages the code depends on can be used by attackers. Five controls can't be used without a mouse, and eight form fields can't be read by a screen reader. Making the controls work with a keyboard, updating the vulnerable packages and labelling the form fields would close these risks. Pinning each tool to an exact version would fix the three pipeline tools referenced by a changeable name, and the two passwords or keys in the code need replacing, with the old ones switched off. The two labels or groups of fields with no name need connecting to their fields or naming.
The product code is 10,170 lines, about €8,700 to rebuild.
If Accessibility rose from 28 to 70, the lowest score rated Strong, the score would rise from 38 to about 46.
New since the last survey: 21 findings
- Secret Scanning · REDACTED
- Secret Scanning · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Supply-chain Provenance & Signing · REDACTED
- Supply-chain Provenance & Signing · REDACTED
- Keyboard semantics · Click handler on a non-interactive <div> src/SutilOxide/UI.fs
Fixed since the last survey: 19 findings
- Dependency Vulnerabilities · High CVE: REDACTED REDACTED
- Dependency Vulnerabilities · High CVE: REDACTED REDACTED
- Dependency Vulnerabilities · High CVE: REDACTED REDACTED
- Dependency Vulnerabilities · High CVE: REDACTED REDACTED
- Dependency Vulnerabilities · High CVE: REDACTED REDACTED
- Dependency Vulnerabilities · High CVE: REDACTED REDACTED
- Dependency Vulnerabilities · High CVE: REDACTED REDACTED
- Dependency Vulnerabilities · High CVE: REDACTED REDACTED
- Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · High vulnerability: REDACTED REDACTED
- Dependency Vulnerabilities · High vulnerability: REDACTED REDACTED
- Dependency Vulnerabilities · Medium CVE: REDACTED REDACTED
- Dependency Vulnerabilities · Medium CVE: REDACTED REDACTED
- Dependency Vulnerabilities · Medium CVE: REDACTED REDACTED
- Dependency Vulnerabilities · Medium CVE: REDACTED REDACTED
- Dependency Vulnerabilities · Medium CVE: [GHSA redacted] REDACTED
- Supply-chain Provenance & Signing REDACTED
- Keyboard semantics · Focusable <div> isn't keyboard-operable src/SutilOxide/UI.fs
Rebuild cost: about €8,700 · Estimate
| Cost to rebuild | €2,900 to €14,000, for 48 to 152 hours of work, under 0.1 person-years for one engineer |
|---|---|
| Difficulty of the problem | Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.7 at a score of 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 | Small: 10,170 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 Browser.Types | 2 SutilOxide.CellEditor | 3 SutilOxide.FileSystem.Types | 4 SutilOxide.PropertyTypes | 5 SutilOxide.Reactive | 6 SutilOxide.Types | 7 SutilOxide.UI.Tool | 8 Browser.IntersectionObserver | 9 Browser.MutationObserver | 10 SutilOxide.AceEditor.Ace | 11 SutilOxide.FileSystem | 12 SutilOxide.FileSystem.FileSystemExt | 13 SutilOxide.FileSystem.Internal | 14 SutilOxide.FileSystemExt.Extensions | 15 SutilOxide.Log | 16 SutilOxide.PropertyEditor | 17 SutilOxide.Reactive.AsyncEventSource | 18 SutilOxide.Reactive.Cell | 19 SutilOxide.Reactive.Event | 20 SutilOxide.Reactive.EventSource | 21 SutilOxide.Reactive.Internal | 22 SutilOxide.UI.Common | 23 SutilOxide.AceEditor | 24 SutilOxide.EntryCache | 25 SutilOxide.EntryCacheDiagnostics | 26 SutilOxide.FileSystem.KeyedStorageIndexedDB | 27 SutilOxide.Reactive.CellInternal | 28 SutilOxide.SubFolderFileSystem | 29 SutilOxide.UI.Control | 30 SutilOxide.UI.Forms | 31 SutilOxide.UI | 32 SutilOxide.UI.Ribbon | 33 SutilOxide.UI.Toolbar | 34 TextEditor | 35 App | 36 SutilOxide.Dock | 37 SutilOxide.Dock.EventHandlers | 38 SutilOxide.DomHelpers.DomHelpers | 39 SutilOxide.Dock.DockHelpers | 40 SutilOxide.Dock.ModelHelpers |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 Browser.Types | ||||||||||||||||||||||||||||||||||||||||
| 2 SutilOxide.CellEditor | ||||||||||||||||||||||||||||||||||||||||
| 3 SutilOxide.FileSystem.Types | ||||||||||||||||||||||||||||||||||||||||
| 4 SutilOxide.PropertyTypes | ||||||||||||||||||||||||||||||||||||||||
| 5 SutilOxide.Reactive | ||||||||||||||||||||||||||||||||||||||||
| 6 SutilOxide.Types | ||||||||||||||||||||||||||||||||||||||||
| 7 SutilOxide.UI.Tool | ||||||||||||||||||||||||||||||||||||||||
| 8 Browser.IntersectionObserver | 1 | |||||||||||||||||||||||||||||||||||||||
| 9 Browser.MutationObserver | 1 | |||||||||||||||||||||||||||||||||||||||
| 10 SutilOxide.AceEditor.Ace | 3 | |||||||||||||||||||||||||||||||||||||||
| 11 SutilOxide.FileSystem | 3 | |||||||||||||||||||||||||||||||||||||||
| 12 SutilOxide.FileSystem.FileSystemExt | 1 | |||||||||||||||||||||||||||||||||||||||
| 13 SutilOxide.FileSystem.Internal | 4 | |||||||||||||||||||||||||||||||||||||||
| 14 SutilOxide.FileSystemExt.Extensions | 1 | |||||||||||||||||||||||||||||||||||||||
| 15 SutilOxide.Log | 3 | |||||||||||||||||||||||||||||||||||||||
| 16 SutilOxide.PropertyEditor | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 17 SutilOxide.Reactive.AsyncEventSource | 1 | |||||||||||||||||||||||||||||||||||||||
| 18 SutilOxide.Reactive.Cell | 1 | |||||||||||||||||||||||||||||||||||||||
| 19 SutilOxide.Reactive.Event | 1 | |||||||||||||||||||||||||||||||||||||||
| 20 SutilOxide.Reactive.EventSource | 1 | |||||||||||||||||||||||||||||||||||||||
| 21 SutilOxide.Reactive.Internal | 3 | |||||||||||||||||||||||||||||||||||||||
| 22 SutilOxide.UI.Common | 1 | |||||||||||||||||||||||||||||||||||||||
| 23 SutilOxide.AceEditor | 6 | |||||||||||||||||||||||||||||||||||||||
| 24 SutilOxide.EntryCache | 1 | |||||||||||||||||||||||||||||||||||||||
| 25 SutilOxide.EntryCacheDiagnostics | 4 | |||||||||||||||||||||||||||||||||||||||
| 26 SutilOxide.FileSystem.KeyedStorageIndexedDB | 1 | |||||||||||||||||||||||||||||||||||||||
| 27 SutilOxide.Reactive.CellInternal | 1 | |||||||||||||||||||||||||||||||||||||||
| 28 SutilOxide.SubFolderFileSystem | 4 | 2 | ||||||||||||||||||||||||||||||||||||||
| 29 SutilOxide.UI.Control | 7 | |||||||||||||||||||||||||||||||||||||||
| 30 SutilOxide.UI.Forms | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 31 SutilOxide.UI | 1 | 2 | 1 | |||||||||||||||||||||||||||||||||||||
| 32 SutilOxide.UI.Ribbon | 2 | |||||||||||||||||||||||||||||||||||||||
| 33 SutilOxide.UI.Toolbar | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 34 TextEditor | 2 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 35 App | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 36 SutilOxide.Dock | 11 | |||||||||||||||||||||||||||||||||||||||
| 37 SutilOxide.Dock.EventHandlers | 2 | |||||||||||||||||||||||||||||||||||||||
| 38 SutilOxide.DomHelpers.DomHelpers | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 39 SutilOxide.Dock.DockHelpers | 3 | 1 | ||||||||||||||||||||||||||||||||||||||
| 40 SutilOxide.Dock.ModelHelpers | 1 | 1 |
8→1 Browser.IntersectionObserver uses Browser.Types✕
- Connections
- 1 pair of types, where a type in Browser.IntersectionObserver uses a type in Browser.Types.
- The types involved
Browser.IntersectionObserver.IntersectionObserver→Browser.Types.IntersectionObserverCtor
- Direction
- Browser.IntersectionObserver uses Browser.Types, so a change to Browser.Types can break Browser.IntersectionObserver, while a change to Browser.IntersectionObserver can't break Browser.Types.
- Position
- Below the diagonal: Browser.IntersectionObserver uses a module listed above it, which is the healthy direction.
9→1 Browser.MutationObserver uses Browser.Types✕
- Connections
- 1 pair of types, where a type in Browser.MutationObserver uses a type in Browser.Types.
- The types involved
Browser.MutationObserver.MutationObserver→Browser.Types.MutationObserverCtor
- Direction
- Browser.MutationObserver uses Browser.Types, so a change to Browser.Types can break Browser.MutationObserver, while a change to Browser.MutationObserver can't break Browser.Types.
- Position
- Below the diagonal: Browser.MutationObserver uses a module listed above it, which is the healthy direction.
10→23 SutilOxide.AceEditor.Ace uses SutilOxide.AceEditor part of a loop✕
- Connections
- 3 pairs of types, where a type in SutilOxide.AceEditor.Ace uses a type in SutilOxide.AceEditor.
- The types involved
SutilOxide.AceEditor.Ace.EditSession→SutilOxide.AceEditor.KeyOf`1SutilOxide.AceEditor.Ace.Editor→SutilOxide.AceEditor.KeyOf`1SutilOxide.AceEditor.Ace.VirtualRenderer→SutilOxide.AceEditor.KeyOf`1
- Direction
- SutilOxide.AceEditor.Ace uses SutilOxide.AceEditor, so a change to SutilOxide.AceEditor can break SutilOxide.AceEditor.Ace, while a change to SutilOxide.AceEditor.Ace can't break SutilOxide.AceEditor.
- 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.
11→3 SutilOxide.FileSystem uses SutilOxide.FileSystem.Types✕
- Connections
- 3 pairs of types, where a type in SutilOxide.FileSystem uses a type in SutilOxide.FileSystem.Types.
- The types involved
SutilOxide.FileSystem.FileSystem→SutilOxide.FileSystem.Types.ContentSutilOxide.FileSystem.FileSystem→SutilOxide.FileSystem.Types.EntrySutilOxide.FileSystem.IWriteOnlyFileSystemOf`1→SutilOxide.FileSystem.Types.Content
- Direction
- SutilOxide.FileSystem uses SutilOxide.FileSystem.Types, so a change to SutilOxide.FileSystem.Types can break SutilOxide.FileSystem, while a change to SutilOxide.FileSystem can't break SutilOxide.FileSystem.Types.
- Position
- Below the diagonal: SutilOxide.FileSystem uses a module listed above it, which is the healthy direction.
12→3 SutilOxide.FileSystem.FileSystemExt uses SutilOxide.FileSystem.Types✕
- Connections
- 1 pair of types, where a type in SutilOxide.FileSystem.FileSystemExt uses a type in SutilOxide.FileSystem.Types.
- The types involved
SutilOxide.FileSystem.FileSystemExt.FileSystemExt→SutilOxide.FileSystem.Types.Entry
- Direction
- SutilOxide.FileSystem.FileSystemExt uses SutilOxide.FileSystem.Types, so a change to SutilOxide.FileSystem.Types can break SutilOxide.FileSystem.FileSystemExt, while a change to SutilOxide.FileSystem.FileSystemExt can't break SutilOxide.FileSystem.Types.
- Position
- Below the diagonal: SutilOxide.FileSystem.FileSystemExt uses a module listed above it, which is the healthy direction.
13→3 SutilOxide.FileSystem.Internal uses SutilOxide.FileSystem.Types✕
- Connections
- 4 pairs of types, where a type in SutilOxide.FileSystem.Internal uses a type in SutilOxide.FileSystem.Types.
- The types involved
SutilOxide.FileSystem.Internal.EntryContent→SutilOxide.FileSystem.Types.EntryTypeSutilOxide.FileSystem.Internal.EntryStorage→SutilOxide.FileSystem.Types.EntryMetaDataSutilOxide.FileSystem.Internal.EntryStorage→SutilOxide.FileSystem.Types.EntryTypeSutilOxide.FileSystem.Internal.EntryStorageDto→SutilOxide.FileSystem.Types.EntryType
- Direction
- SutilOxide.FileSystem.Internal uses SutilOxide.FileSystem.Types, so a change to SutilOxide.FileSystem.Types can break SutilOxide.FileSystem.Internal, while a change to SutilOxide.FileSystem.Internal can't break SutilOxide.FileSystem.Types.
- Position
- Below the diagonal: SutilOxide.FileSystem.Internal uses a module listed above it, which is the healthy direction.
14→3 SutilOxide.FileSystemExt.Extensions uses SutilOxide.FileSystem.Types✕
- Connections
- 1 pair of types, where a type in SutilOxide.FileSystemExt.Extensions uses a type in SutilOxide.FileSystem.Types.
- The types involved
SutilOxide.FileSystemExt.Extensions.Extensions→SutilOxide.FileSystem.Types.Entry
- Direction
- SutilOxide.FileSystemExt.Extensions uses SutilOxide.FileSystem.Types, so a change to SutilOxide.FileSystem.Types can break SutilOxide.FileSystemExt.Extensions, while a change to SutilOxide.FileSystemExt.Extensions can't break SutilOxide.FileSystem.Types.
- Position
- Below the diagonal: SutilOxide.FileSystemExt.Extensions uses a module listed above it, which is the healthy direction.
15→5 SutilOxide.Log uses SutilOxide.Reactive✕
- Connections
- 3 pairs of types, where a type in SutilOxide.Log uses a type in SutilOxide.Reactive.
- The types involved
SutilOxide.Log.Log→SutilOxide.Reactive.ICell`1SutilOxide.Log.Log→SutilOxide.Reactive.IEventSource`1SutilOxide.Log.Log→SutilOxide.Reactive.ISignal`1
- Direction
- SutilOxide.Log uses SutilOxide.Reactive, so a change to SutilOxide.Reactive can break SutilOxide.Log, while a change to SutilOxide.Log can't break SutilOxide.Reactive.
- Position
- Below the diagonal: SutilOxide.Log uses a module listed above it, which is the healthy direction.
16→2 SutilOxide.PropertyEditor uses SutilOxide.CellEditor✕
- Connections
- 1 pair of types, where a type in SutilOxide.PropertyEditor uses a type in SutilOxide.CellEditor.
- The types involved
SutilOxide.PropertyEditor.PropertyEditor→SutilOxide.CellEditor.Cell`1
- Direction
- SutilOxide.PropertyEditor uses SutilOxide.CellEditor, so a change to SutilOxide.CellEditor can break SutilOxide.PropertyEditor, while a change to SutilOxide.PropertyEditor can't break SutilOxide.CellEditor.
- Position
- Below the diagonal: SutilOxide.PropertyEditor uses a module listed above it, which is the healthy direction.
16→4 SutilOxide.PropertyEditor uses SutilOxide.PropertyTypes✕
- Connections
- 2 pairs of types, where a type in SutilOxide.PropertyEditor uses a type in SutilOxide.PropertyTypes.
- The types involved
SutilOxide.PropertyEditor.PropertyEditor→SutilOxide.PropertyTypes.DataTypeSutilOxide.PropertyEditor.PropertyEditor→SutilOxide.PropertyTypes.MutableMap`2
- Direction
- SutilOxide.PropertyEditor uses SutilOxide.PropertyTypes, so a change to SutilOxide.PropertyTypes can break SutilOxide.PropertyEditor, while a change to SutilOxide.PropertyEditor can't break SutilOxide.PropertyTypes.
- Position
- Below the diagonal: SutilOxide.PropertyEditor uses a module listed above it, which is the healthy direction.
17→5 SutilOxide.Reactive.AsyncEventSource uses SutilOxide.Reactive✕
- Connections
- 1 pair of types, where a type in SutilOxide.Reactive.AsyncEventSource uses a type in SutilOxide.Reactive.
- The types involved
SutilOxide.Reactive.AsyncEventSource.AsyncEventSource→SutilOxide.Reactive.IAsyncEventSource`1
- Direction
- SutilOxide.Reactive.AsyncEventSource uses SutilOxide.Reactive, so a change to SutilOxide.Reactive can break SutilOxide.Reactive.AsyncEventSource, while a change to SutilOxide.Reactive.AsyncEventSource can't break SutilOxide.Reactive.
- Position
- Below the diagonal: SutilOxide.Reactive.AsyncEventSource uses a module listed above it, which is the healthy direction.
18→5 SutilOxide.Reactive.Cell uses SutilOxide.Reactive✕
- Connections
- 1 pair of types, where a type in SutilOxide.Reactive.Cell uses a type in SutilOxide.Reactive.
- The types involved
SutilOxide.Reactive.Cell.Cell→SutilOxide.Reactive.ICell`1
- Direction
- SutilOxide.Reactive.Cell uses SutilOxide.Reactive, so a change to SutilOxide.Reactive can break SutilOxide.Reactive.Cell, while a change to SutilOxide.Reactive.Cell can't break SutilOxide.Reactive.
- Position
- Below the diagonal: SutilOxide.Reactive.Cell uses a module listed above it, which is the healthy direction.
19→5 SutilOxide.Reactive.Event uses SutilOxide.Reactive✕
- Connections
- 1 pair of types, where a type in SutilOxide.Reactive.Event uses a type in SutilOxide.Reactive.
- The types involved
SutilOxide.Reactive.Event.Event→SutilOxide.Reactive.IEvent`1
- Direction
- SutilOxide.Reactive.Event uses SutilOxide.Reactive, so a change to SutilOxide.Reactive can break SutilOxide.Reactive.Event, while a change to SutilOxide.Reactive.Event can't break SutilOxide.Reactive.
- Position
- Below the diagonal: SutilOxide.Reactive.Event uses a module listed above it, which is the healthy direction.
20→5 SutilOxide.Reactive.EventSource uses SutilOxide.Reactive✕
- Connections
- 1 pair of types, where a type in SutilOxide.Reactive.EventSource uses a type in SutilOxide.Reactive.
- The types involved
SutilOxide.Reactive.EventSource.EventSource→SutilOxide.Reactive.IEventSource`1
- Direction
- SutilOxide.Reactive.EventSource uses SutilOxide.Reactive, so a change to SutilOxide.Reactive can break SutilOxide.Reactive.EventSource, while a change to SutilOxide.Reactive.EventSource can't break SutilOxide.Reactive.
- Position
- Below the diagonal: SutilOxide.Reactive.EventSource uses a module listed above it, which is the healthy direction.
21→5 SutilOxide.Reactive.Internal uses SutilOxide.Reactive✕
- Connections
- 3 pairs of types, where a type in SutilOxide.Reactive.Internal uses a type in SutilOxide.Reactive.
- The types involved
SutilOxide.Reactive.Internal.Cell`1→SutilOxide.Reactive.ICell`1SutilOxide.Reactive.Internal.EventSource`1→SutilOxide.Reactive.IEventSource`1SutilOxide.Reactive.Internal.PromiseEventSource`1→SutilOxide.Reactive.IAsyncEventSource`1
- Direction
- SutilOxide.Reactive.Internal uses SutilOxide.Reactive, so a change to SutilOxide.Reactive can break SutilOxide.Reactive.Internal, while a change to SutilOxide.Reactive.Internal can't break SutilOxide.Reactive.
- Position
- Below the diagonal: SutilOxide.Reactive.Internal uses a module listed above it, which is the healthy direction.
22→5 SutilOxide.UI.Common uses SutilOxide.Reactive✕
- Connections
- 1 pair of types, where a type in SutilOxide.UI.Common uses a type in SutilOxide.Reactive.
- The types involved
SutilOxide.UI.Common.Value`1→SutilOxide.Reactive.ISignal`1
- Direction
- SutilOxide.UI.Common uses SutilOxide.Reactive, so a change to SutilOxide.Reactive can break SutilOxide.UI.Common, while a change to SutilOxide.UI.Common can't break SutilOxide.Reactive.
- Position
- Below the diagonal: SutilOxide.UI.Common uses a module listed above it, which is the healthy direction.
23→10 SutilOxide.AceEditor uses SutilOxide.AceEditor.Ace✕
- Connections
- 6 pairs of types, where a type in SutilOxide.AceEditor uses a type in SutilOxide.AceEditor.Ace.
- The types involved
SutilOxide.AceEditor.AceEditor→SutilOxide.AceEditor.Ace.IExportsSutilOxide.AceEditor.IExports→SutilOxide.AceEditor.Ace.ConfigSutilOxide.AceEditor.IExports→SutilOxide.AceEditor.Ace.DocumentSutilOxide.AceEditor.IExports→SutilOxide.AceEditor.Ace.EditSessionSutilOxide.AceEditor.IExports→SutilOxide.AceEditor.Ace.EditorSutilOxide.AceEditor.IExports→SutilOxide.AceEditor.Ace.SyntaxMode
- Direction
- SutilOxide.AceEditor uses SutilOxide.AceEditor.Ace, so a change to SutilOxide.AceEditor.Ace can break SutilOxide.AceEditor, while a change to SutilOxide.AceEditor can't break SutilOxide.AceEditor.Ace.
- Position
- Below the diagonal: SutilOxide.AceEditor uses a module listed above it, which is the healthy direction.
24→11 SutilOxide.EntryCache uses SutilOxide.FileSystem✕
- Connections
- 1 pair of types, where a type in SutilOxide.EntryCache uses a type in SutilOxide.FileSystem.
- The types involved
SutilOxide.EntryCache.LruByteCache`1→SutilOxide.FileSystem.LayerStats
- Direction
- SutilOxide.EntryCache uses SutilOxide.FileSystem, so a change to SutilOxide.FileSystem can break SutilOxide.EntryCache, while a change to SutilOxide.EntryCache can't break SutilOxide.FileSystem.
- Position
- Below the diagonal: SutilOxide.EntryCache uses a module listed above it, which is the healthy direction.
25→11 SutilOxide.EntryCacheDiagnostics uses SutilOxide.FileSystem✕
- Connections
- 4 pairs of types, where a type in SutilOxide.EntryCacheDiagnostics uses a type in SutilOxide.FileSystem.
- The types involved
SutilOxide.EntryCacheDiagnostics.EntryCacheDiagnostics→SutilOxide.FileSystem.IEntryCacheDiagnosticsSutilOxide.EntryCacheDiagnostics.EntryCacheDiagnostics→SutilOxide.FileSystem.IKeyedStorageAsyncSutilOxide.EntryCacheDiagnostics.EntryCacheDiagnostics→SutilOxide.FileSystem.ITopReadsEntrySutilOxide.EntryCacheDiagnostics.EntryCacheDiagnostics→SutilOxide.FileSystem.LayerStats
- Direction
- SutilOxide.EntryCacheDiagnostics uses SutilOxide.FileSystem, so a change to SutilOxide.FileSystem can break SutilOxide.EntryCacheDiagnostics, while a change to SutilOxide.EntryCacheDiagnostics can't break SutilOxide.FileSystem.
- Position
- Below the diagonal: SutilOxide.EntryCacheDiagnostics uses a module listed above it, which is the healthy direction.
26→11 SutilOxide.FileSystem.KeyedStorageIndexedDB uses SutilOxide.FileSystem✕
- Connections
- 1 pair of types, where a type in SutilOxide.FileSystem.KeyedStorageIndexedDB uses a type in SutilOxide.FileSystem.
- The types involved
SutilOxide.FileSystem.KeyedStorageIndexedDB.KeyedStorageIndexedDB→SutilOxide.FileSystem.IKeyedStorageAsync
- Direction
- SutilOxide.FileSystem.KeyedStorageIndexedDB uses SutilOxide.FileSystem, so a change to SutilOxide.FileSystem can break SutilOxide.FileSystem.KeyedStorageIndexedDB, while a change to SutilOxide.FileSystem.KeyedStorageIndexedDB can't break SutilOxide.FileSystem.
- Position
- Below the diagonal: SutilOxide.FileSystem.KeyedStorageIndexedDB uses a module listed above it, which is the healthy direction.
27→21 SutilOxide.Reactive.CellInternal uses SutilOxide.Reactive.Internal✕
- Connections
- 1 pair of types, where a type in SutilOxide.Reactive.CellInternal uses a type in SutilOxide.Reactive.Internal.
- The types involved
SutilOxide.Reactive.CellInternal.CellInternal→SutilOxide.Reactive.Internal.Cell`1
- Direction
- SutilOxide.Reactive.CellInternal uses SutilOxide.Reactive.Internal, so a change to SutilOxide.Reactive.Internal can break SutilOxide.Reactive.CellInternal, while a change to SutilOxide.Reactive.CellInternal can't break SutilOxide.Reactive.Internal.
- Position
- Below the diagonal: SutilOxide.Reactive.CellInternal uses a module listed above it, which is the healthy direction.
28→3 SutilOxide.SubFolderFileSystem uses SutilOxide.FileSystem.Types✕
- Connections
- 4 pairs of types, where a type in SutilOxide.SubFolderFileSystem uses a type in SutilOxide.FileSystem.Types.
- The types involved
SutilOxide.SubFolderFileSystem.SubFolderFileSystemAsync→SutilOxide.FileSystem.Types.ContentSutilOxide.SubFolderFileSystem.SubFolderFileSystemAsync→SutilOxide.FileSystem.Types.EntrySutilOxide.SubFolderFileSystem.VirtualFileSystem→SutilOxide.FileSystem.Types.ContentSutilOxide.SubFolderFileSystem.VirtualFileSystem→SutilOxide.FileSystem.Types.Entry
- Direction
- SutilOxide.SubFolderFileSystem uses SutilOxide.FileSystem.Types, so a change to SutilOxide.FileSystem.Types can break SutilOxide.SubFolderFileSystem, while a change to SutilOxide.SubFolderFileSystem can't break SutilOxide.FileSystem.Types.
- Position
- Below the diagonal: SutilOxide.SubFolderFileSystem uses a module listed above it, which is the healthy direction.
28→11 SutilOxide.SubFolderFileSystem uses SutilOxide.FileSystem✕
- Connections
- 2 pairs of types, where a type in SutilOxide.SubFolderFileSystem uses a type in SutilOxide.FileSystem.
- The types involved
SutilOxide.SubFolderFileSystem.SubFolderFileSystemAsync→SutilOxide.FileSystem.IFsAsyncSutilOxide.SubFolderFileSystem.VirtualFileSystem→SutilOxide.FileSystem.IFsAsync
- Direction
- SutilOxide.SubFolderFileSystem uses SutilOxide.FileSystem, so a change to SutilOxide.FileSystem can break SutilOxide.SubFolderFileSystem, while a change to SutilOxide.SubFolderFileSystem can't break SutilOxide.FileSystem.
- Position
- Below the diagonal: SutilOxide.SubFolderFileSystem uses a module listed above it, which is the healthy direction.
29→22 SutilOxide.UI.Control uses SutilOxide.UI.Common✕
- Connections
- 7 pairs of types, where a type in SutilOxide.UI.Control uses a type in SutilOxide.UI.Common.
- The types involved
SutilOxide.UI.Control.Control→SutilOxide.UI.Common.IconSutilOxide.UI.Control.Control→SutilOxide.UI.Common.TextSutilOxide.UI.Control.Control→SutilOxide.UI.Common.Value`1SutilOxide.UI.Control.ControlOption→SutilOxide.UI.Common.IconSutilOxide.UI.Control.ControlOption→SutilOxide.UI.Common.ShortcutSutilOxide.UI.Control.ControlOption→SutilOxide.UI.Common.TextSutilOxide.UI.Control.ControlType→SutilOxide.UI.Common.Value`1
- Direction
- SutilOxide.UI.Control uses SutilOxide.UI.Common, so a change to SutilOxide.UI.Common can break SutilOxide.UI.Control, while a change to SutilOxide.UI.Control can't break SutilOxide.UI.Common.
- Position
- Below the diagonal: SutilOxide.UI.Control uses a module listed above it, which is the healthy direction.
30→6 SutilOxide.UI.Forms uses SutilOxide.Types✕
- Connections
- 1 pair of types, where a type in SutilOxide.UI.Forms uses a type in SutilOxide.Types.
- The types involved
SutilOxide.UI.Forms.Forms→SutilOxide.Types.MultiLineText
- Direction
- SutilOxide.UI.Forms uses SutilOxide.Types, so a change to SutilOxide.Types can break SutilOxide.UI.Forms, while a change to SutilOxide.UI.Forms can't break SutilOxide.Types.
- Position
- Below the diagonal: SutilOxide.UI.Forms uses a module listed above it, which is the healthy direction.
30→22 SutilOxide.UI.Forms uses SutilOxide.UI.Common✕
- Connections
- 1 pair of types, where a type in SutilOxide.UI.Forms uses a type in SutilOxide.UI.Common.
- The types involved
SutilOxide.UI.Forms.Field`1→SutilOxide.UI.Common.Value`1
- Direction
- SutilOxide.UI.Forms uses SutilOxide.UI.Common, so a change to SutilOxide.UI.Common can break SutilOxide.UI.Forms, while a change to SutilOxide.UI.Forms can't break SutilOxide.UI.Common.
- Position
- Below the diagonal: SutilOxide.UI.Forms uses a module listed above it, which is the healthy direction.
31→5 SutilOxide.UI uses SutilOxide.Reactive✕
- Connections
- 1 pair of types, where a type in SutilOxide.UI uses a type in SutilOxide.Reactive.
- The types involved
SutilOxide.UI.IPaneController→SutilOxide.Reactive.ISignal`1
- Direction
- SutilOxide.UI uses SutilOxide.Reactive, so a change to SutilOxide.Reactive can break SutilOxide.UI, while a change to SutilOxide.UI can't break SutilOxide.Reactive.
- Position
- Below the diagonal: SutilOxide.UI uses a module listed above it, which is the healthy direction.
31→6 SutilOxide.UI uses SutilOxide.Types✕
- Connections
- 2 pairs of types, where a type in SutilOxide.UI uses a type in SutilOxide.Types.
- The types involved
SutilOxide.UI.DockLocation→SutilOxide.Types.BasicLocationSutilOxide.UI.DockPane→SutilOxide.Types.LabelElement
- Direction
- SutilOxide.UI uses SutilOxide.Types, so a change to SutilOxide.Types can break SutilOxide.UI, while a change to SutilOxide.UI can't break SutilOxide.Types.
- Position
- Below the diagonal: SutilOxide.UI uses a module listed above it, which is the healthy direction.
31→29 SutilOxide.UI uses SutilOxide.UI.Control✕
- Connections
- 1 pair of types, where a type in SutilOxide.UI uses a type in SutilOxide.UI.Control.
- The types involved
SutilOxide.UI.IRibbonController→SutilOxide.UI.Control.Control
- Direction
- SutilOxide.UI uses SutilOxide.UI.Control, so a change to SutilOxide.UI.Control can break SutilOxide.UI, while a change to SutilOxide.UI can't break SutilOxide.UI.Control.
- Position
- Below the diagonal: SutilOxide.UI uses a module listed above it, which is the healthy direction.
32→29 SutilOxide.UI.Ribbon uses SutilOxide.UI.Control✕
- Connections
- 2 pairs of types, where a type in SutilOxide.UI.Ribbon uses a type in SutilOxide.UI.Control.
- The types involved
SutilOxide.UI.Ribbon.Group→SutilOxide.UI.Control.ControlSutilOxide.UI.Ribbon.Ribbon→SutilOxide.UI.Control.Control
- Direction
- SutilOxide.UI.Ribbon uses SutilOxide.UI.Control, so a change to SutilOxide.UI.Control can break SutilOxide.UI.Ribbon, while a change to SutilOxide.UI.Ribbon can't break SutilOxide.UI.Control.
- Position
- Below the diagonal: SutilOxide.UI.Ribbon uses a module listed above it, which is the healthy direction.
33→22 SutilOxide.UI.Toolbar uses SutilOxide.UI.Common✕
- Connections
- 1 pair of types, where a type in SutilOxide.UI.Toolbar uses a type in SutilOxide.UI.Common.
- The types involved
SutilOxide.UI.Toolbar.ToolbarOption→SutilOxide.UI.Common.Orientation
- Direction
- SutilOxide.UI.Toolbar uses SutilOxide.UI.Common, so a change to SutilOxide.UI.Common can break SutilOxide.UI.Toolbar, while a change to SutilOxide.UI.Toolbar can't break SutilOxide.UI.Common.
- Position
- Below the diagonal: SutilOxide.UI.Toolbar uses a module listed above it, which is the healthy direction.
33→29 SutilOxide.UI.Toolbar uses SutilOxide.UI.Control✕
- Connections
- 1 pair of types, where a type in SutilOxide.UI.Toolbar uses a type in SutilOxide.UI.Control.
- The types involved
SutilOxide.UI.Toolbar.Toolbar→SutilOxide.UI.Control.Control
- Direction
- SutilOxide.UI.Toolbar uses SutilOxide.UI.Control, so a change to SutilOxide.UI.Control can break SutilOxide.UI.Toolbar, while a change to SutilOxide.UI.Toolbar can't break SutilOxide.UI.Control.
- Position
- Below the diagonal: SutilOxide.UI.Toolbar uses a module listed above it, which is the healthy direction.
34→10 TextEditor uses SutilOxide.AceEditor.Ace✕
- Connections
- 2 pairs of types, where a type in TextEditor uses a type in SutilOxide.AceEditor.Ace.
- The types involved
TextEditor.TextEditor→SutilOxide.AceEditor.Ace.ConfigTextEditor.TextEditor→SutilOxide.AceEditor.Ace.Editor
- Direction
- TextEditor uses SutilOxide.AceEditor.Ace, so a change to SutilOxide.AceEditor.Ace can break TextEditor, while a change to TextEditor can't break SutilOxide.AceEditor.Ace.
- Position
- Below the diagonal: TextEditor uses a module listed above it, which is the healthy direction.
34→11 TextEditor uses SutilOxide.FileSystem✕
- Connections
- 1 pair of types, where a type in TextEditor uses a type in SutilOxide.FileSystem.
- The types involved
TextEditor.Editor→SutilOxide.FileSystem.IFileSystemAsync
- Direction
- TextEditor uses SutilOxide.FileSystem, so a change to SutilOxide.FileSystem can break TextEditor, while a change to TextEditor can't break SutilOxide.FileSystem.
- Position
- Below the diagonal: TextEditor uses a module listed above it, which is the healthy direction.
34→23 TextEditor uses SutilOxide.AceEditor✕
- Connections
- 1 pair of types, where a type in TextEditor uses a type in SutilOxide.AceEditor.
- The types involved
TextEditor.TextEditor→SutilOxide.AceEditor.IExports
- Direction
- TextEditor uses SutilOxide.AceEditor, so a change to SutilOxide.AceEditor can break TextEditor, while a change to TextEditor can't break SutilOxide.AceEditor.
- Position
- Below the diagonal: TextEditor uses a module listed above it, which is the healthy direction.
35→11 App uses SutilOxide.FileSystem✕
- Connections
- 1 pair of types, where a type in App uses a type in SutilOxide.FileSystem.
- The types involved
App.App→SutilOxide.FileSystem.IFileSystemAsync
- Direction
- App uses SutilOxide.FileSystem, so a change to SutilOxide.FileSystem can break App, while a change to App can't break SutilOxide.FileSystem.
- Position
- Below the diagonal: App uses a module listed above it, which is the healthy direction.
35→34 App uses TextEditor✕
- Connections
- 1 pair of types, where a type in App uses a type in TextEditor.
- The types involved
App.App→TextEditor.Editor
- Direction
- App uses TextEditor, so a change to TextEditor can break App, while a change to App can't break TextEditor.
- Position
- Below the diagonal: App uses a module listed above it, which is the healthy direction.
36→31 SutilOxide.Dock uses SutilOxide.UI✕
- Connections
- 11 pairs of types, where a type in SutilOxide.Dock uses a type in SutilOxide.UI.
- The types involved
SutilOxide.Dock.Dock→SutilOxide.UI.DockCollectionSutilOxide.Dock.Dock→SutilOxide.UI.DockLocationSutilOxide.Dock.Dock→SutilOxide.UI.DockPaneSutilOxide.Dock.DockContainer→SutilOxide.UI.DockLocationSutilOxide.Dock.DockContainer→SutilOxide.UI.DockPaneSutilOxide.Dock.DockContainer→SutilOxide.UI.PaneOptionSutilOxide.Dock.DockProperty→SutilOxide.UI.DockLocationSutilOxide.Dock.Message→SutilOxide.UI.DockLocationSutilOxide.Dock.Message→SutilOxide.UI.DockPaneSutilOxide.Dock.Model→SutilOxide.UI.DockCollectionSutilOxide.Dock.Model→SutilOxide.UI.DockLocation
- Direction
- SutilOxide.Dock uses SutilOxide.UI, so a change to SutilOxide.UI can break SutilOxide.Dock, while a change to SutilOxide.Dock can't break SutilOxide.UI.
- Position
- Below the diagonal: SutilOxide.Dock uses a module listed above it, which is the healthy direction.
37→31 SutilOxide.Dock.EventHandlers uses SutilOxide.UI✕
- Connections
- 2 pairs of types, where a type in SutilOxide.Dock.EventHandlers uses a type in SutilOxide.UI.
- The types involved
SutilOxide.Dock.EventHandlers.EventHandlers→SutilOxide.UI.DockLocationSutilOxide.Dock.EventHandlers.EventHandlers→SutilOxide.UI.DockPane
- Direction
- SutilOxide.Dock.EventHandlers uses SutilOxide.UI, so a change to SutilOxide.UI can break SutilOxide.Dock.EventHandlers, while a change to SutilOxide.Dock.EventHandlers can't break SutilOxide.UI.
- Position
- Below the diagonal: SutilOxide.Dock.EventHandlers uses a module listed above it, which is the healthy direction.
38→6 SutilOxide.DomHelpers.DomHelpers uses SutilOxide.Types✕
- Connections
- 1 pair of types, where a type in SutilOxide.DomHelpers.DomHelpers uses a type in SutilOxide.Types.
- The types involved
SutilOxide.DomHelpers.DomHelpers.DomHelpers→SutilOxide.Types.TabHalf
- Direction
- SutilOxide.DomHelpers.DomHelpers uses SutilOxide.Types, so a change to SutilOxide.Types can break SutilOxide.DomHelpers.DomHelpers, while a change to SutilOxide.DomHelpers.DomHelpers can't break SutilOxide.Types.
- Position
- Below the diagonal: SutilOxide.DomHelpers.DomHelpers uses a module listed above it, which is the healthy direction.
38→31 SutilOxide.DomHelpers.DomHelpers uses SutilOxide.UI✕
- Connections
- 1 pair of types, where a type in SutilOxide.DomHelpers.DomHelpers uses a type in SutilOxide.UI.
- The types involved
SutilOxide.DomHelpers.DomHelpers.DomHelpers→SutilOxide.UI.DockLocation
- Direction
- SutilOxide.DomHelpers.DomHelpers uses SutilOxide.UI, so a change to SutilOxide.UI can break SutilOxide.DomHelpers.DomHelpers, while a change to SutilOxide.DomHelpers.DomHelpers can't break SutilOxide.UI.
- Position
- Below the diagonal: SutilOxide.DomHelpers.DomHelpers uses a module listed above it, which is the healthy direction.
39→31 SutilOxide.Dock.DockHelpers uses SutilOxide.UI✕
- Connections
- 3 pairs of types, where a type in SutilOxide.Dock.DockHelpers uses a type in SutilOxide.UI.
- The types involved
SutilOxide.Dock.DockHelpers.DockHelpers→SutilOxide.UI.DockCollectionSutilOxide.Dock.DockHelpers.DockHelpers→SutilOxide.UI.DockLocationSutilOxide.Dock.DockHelpers.DockHelpers→SutilOxide.UI.DockPane
- Direction
- SutilOxide.Dock.DockHelpers uses SutilOxide.UI, so a change to SutilOxide.UI can break SutilOxide.Dock.DockHelpers, while a change to SutilOxide.Dock.DockHelpers can't break SutilOxide.UI.
- Position
- Below the diagonal: SutilOxide.Dock.DockHelpers uses a module listed above it, which is the healthy direction.
39→36 SutilOxide.Dock.DockHelpers uses SutilOxide.Dock✕
- Connections
- 1 pair of types, where a type in SutilOxide.Dock.DockHelpers uses a type in SutilOxide.Dock.
- The types involved
SutilOxide.Dock.DockHelpers.DockHelpers→SutilOxide.Dock.Model
- Direction
- SutilOxide.Dock.DockHelpers uses SutilOxide.Dock, so a change to SutilOxide.Dock can break SutilOxide.Dock.DockHelpers, while a change to SutilOxide.Dock.DockHelpers can't break SutilOxide.Dock.
- Position
- Below the diagonal: SutilOxide.Dock.DockHelpers uses a module listed above it, which is the healthy direction.
40→31 SutilOxide.Dock.ModelHelpers uses SutilOxide.UI✕
- Connections
- 1 pair of types, where a type in SutilOxide.Dock.ModelHelpers uses a type in SutilOxide.UI.
- The types involved
SutilOxide.Dock.ModelHelpers.ModelHelpers→SutilOxide.UI.DockLocation
- Direction
- SutilOxide.Dock.ModelHelpers uses SutilOxide.UI, so a change to SutilOxide.UI can break SutilOxide.Dock.ModelHelpers, while a change to SutilOxide.Dock.ModelHelpers can't break SutilOxide.UI.
- Position
- Below the diagonal: SutilOxide.Dock.ModelHelpers uses a module listed above it, which is the healthy direction.
40→36 SutilOxide.Dock.ModelHelpers uses SutilOxide.Dock✕
- Connections
- 1 pair of types, where a type in SutilOxide.Dock.ModelHelpers uses a type in SutilOxide.Dock.
- The types involved
SutilOxide.Dock.ModelHelpers.ModelHelpers→SutilOxide.Dock.Model
- Direction
- SutilOxide.Dock.ModelHelpers uses SutilOxide.Dock, so a change to SutilOxide.Dock can break SutilOxide.Dock.ModelHelpers, while a change to SutilOxide.Dock.ModelHelpers can't break SutilOxide.Dock.
- Position
- Below the diagonal: SutilOxide.Dock.ModelHelpers 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 |
|---|---|---|
| A03:2025 — Software Supply Chain Failures | 72 | High / Critical |
| A05:2025 — Injection | 4 | High / Critical |
| A07:2025 — Authentication Failures | 2 | High / Critical |
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 2 Leaked secret finding(s) in Secret Scanning — start with REDACTED (2).
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 1 No tests found finding(s) in Test Distribution. | +8.5 pts | Low | Test Distribution |
| Resolve the 2 Leaked secret finding(s) in Secret Scanning — start with REDACTED (2). | +5.4 pts | Low | Secret Scanning |
| Resolve the 1 No automated tests finding(s) in Code Coverage. | +8.5 pts | High | Code Coverage |
| 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. | +4.2 pts | Medium | Security & performance tooling |
| 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.0 pts | Medium | Architecture documentation |
| Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href. | +3.3 pts | Medium | Keyboard semantics |
| Use valid, non-abstract roles, supply the ARIA state each role requires, and never put aria-hidden on a focusable element. | +3.3 pts | Medium | ARIA correctness |
| Automate the release in CI — a deploy stage for a service (Helm/Kubernetes manifests or an equivalent rollout), or a tag-triggered publish job for an artifact — so releases are repeatable and reversible. | +3.0 pts | Medium | Deployment & Rollback |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 0.0 | Slop | Secret Scanning: Leaked secret: REDACTED |
| REDACTED | 2.7 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.1 | Mixed | Static Analysis (SAST): High: REDACTED |
| src/SutilOxide/FileSystem/KeyedStorageIndexedDB.js | 7.0 | Mixed | Cyclomatic Complexity: KeyedStorageIndexedDB.checkConsistency (cyclomatic 66) |
| src/SutilOxide/Ace.fs | 7.2 | Mixed | God Classes: FileTooLong: SutilOxide/Ace.fs |
| src/SutilOxide/Dock.fs | 7.4 | Mixed | Cyclomatic Complexity: Dock._update (cyclomatic 30) |
| src/SutilOxide/UI.fs | 7.8 | Mixed | Cyclomatic Complexity: Control.renderControlWithParent (cyclomatic 17) |
| src/SutilOxide/Toolbar.fs | 8.5 | Near-clean | Cognitive Complexity: Toolbar.mkButton (cognitive 17) |
| src/SutilOxide/FileSystem/KeyedStorageFileSystemAsync.fs | 8.5 | Near-clean | God Classes: FileTooLong: FileSystem/KeyedStorageFileSystemAsync.fs |
| src/SutilOxide/Reactive.fs | 8.5 | Near-clean | Code Duplication: Duplicated block (10 lines × 2) |
| src/SutilOxide/FileExplorer.fs | 8.5 | Near-clean | Code Duplication: Duplicated block (9 lines × 2) |
| src/SutilOxide/DomHelpers.fs | 8.5 | Near-clean | Code Duplication: Duplicated block (5 lines × 2) |
| src/SutilOxide/FileSystem/SubFolderFileSystem.fs | 8.5 | Near-clean | Cohesion (LCOM4): Low cohesion: VirtualFileSystem (LCOM4 4) |
How the grades work
A definite problem that already costs you something and drags the score down: a missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here tends to cause failures elsewhere.
Likely wrong, but not failing yet. It degrades the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to carry for two years either.
Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.
Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.
Methodology & how to trust this report
Watchdog is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. 44 of 44 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); none rely on LLM judgement. Overall confidence is 0.9 — the weighted average across measured dimensions; it falls as more of the score leans on LLM-assisted judgement and rises when it's fully tool-backed.
What we checked — 44 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, 123 of 141 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it — Roslyn, git, a scanner, or (for a handful of documentation/naming dimensions) an LLM labelled sampled · advisory — not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Watchdog duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 | ✓ deterministic |
| LLM (sampled · advisory) | Documentation quality, ADR conformance, naming — sampled over a bounded sample; advisory, never a deterministic measurement | — | ◐ LLM · sampled · advisory |
Run transparency — what happened this run
- D15 Churn × Complexity Hotspots — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. A hotspot's complexity is meant to be the worst body its churn actually touched. For src/SutilOxide/UI.fs that could not be established — the complexity reader for the file reports no body extents, or the history carries no per-line attribution — so the row quotes the file's worst body, which the counted changes may never have touched. The churn count is unaffected.
- D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Single-maintainer repository — bus factor is not applicable (3 contributor(s) across 183 commit(s) sampled, automation and bot accounts excluded). One of them holds 96% of the history; the other 2 hold 2% each on average, below the 5% at which there is somebody to hand the work to. That is a single maintainer with drive-by contributors, not a team whose knowledge has concentrated — so the bus factor is not applicable and there is nothing here for the owner to act on.
- D21 Naming Consistency — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D21's deterministic naming rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. Until then its declarations carry no naming verdict this run — this says nothing about whether its names are consistent.
- D22 Internal API Consistency — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. This repository's source is written only in languages whose packages are published through a manifest, and no manifest in the tree makes a publication act: either there is no package manifest of any ecosystem (no package.json, pyproject.toml, setup.py, gemspec, Cargo.toml, pom.xml, build.gradle, composer.json, pubspec.yaml or mix.exs), or every one present declares in its package manager's own terms that it is not published (an npm package marked "private": true, a Cargo package with publish = false, a pubspec with publish_to: none, a Composer "project", a Poetry project with package-mode = false, or the "Private :: Do Not Upload" classifier). With no publication act there is no intentionally-exposed surface for API consistency to be judged over.
- D24 Comment Value — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
- 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 build of this repository exited 1 and the cause could not be attributed, so no assemblies were produced and there was no IL to read. We do not read it as a defect in the repository: an unattributed failure leans OURS. D18 owns the question of whether this repository builds; it was not answered here.
- AX6 Interface segregation — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is computed over the public interfaces this run's compilations declare, and none was loaded, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- AXB1 Runtime evidence locked — no reproducible boot — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Subject: 10 markup document(s) — HTML, Razor, JSX, Vue, Svelte or server templates. The Runtime Evidence tier boots an app only via docker-compose, an Aspire AppHost, a Dockerfile, an npm dev script, a web service's own toolchain entry point (cargo, go, dotnet, Python, Spring Boot), or an Android app's own Gradle wrapper (run on an emulator); an Apple or Flutter app needs a host it lacks. None applied, so no live runtime a11y/egress/header evidence was collected. You can widen what we reach: add a docker-compose.yml (or an Aspire AppHost) that brings the app up with its dependencies. Watchdog then boots it in an isolated sandbox and gathers real runtime evidence — you change nothing in your pipeline (no CI step, no SDK).
- C1 Data Protection — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These personal data controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks personal data controls.
- C2 Access Controls — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These authorization controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks authorization controls.
- C3 Audit Trail — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These audit controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks audit controls.
- C4 Data Retention — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These retention controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks retention controls.
- C5 Data-Subject Rights — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These data-subject rights controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks data-subject rights controls.
- IC1 Incompleteness & stubs — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- 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.
- 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.
Limitations & what we did not check
Watchdog assesses the repository exactly as committed, and only the repository. By design it does not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
- D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- D8 Code Coverage: Coverage is measured by building and running the test suite inside Watchdog's isolated image — the target repo is never modified, and nothing on your systems runs. So coverage exists only when the suite builds and runs within the inline time budget; one that needs external services, can't build, or exceeds the budget yields no coverage (D8 then degrades to not-measured, not a low score). Line coverage also says nothing about assertion quality.
- D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
- D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
- D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
- D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- 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.
- AC5 ARIA correctness: ARIA correctness is checked against the static role/attribute shape — roles/attributes set dynamically aren't seen, a valid role says nothing about whether it matches the element's real behaviour, and required-state checks are suppressed when a JSX spread could supply them. The two-branch toggle check (a control whose state is conveyed only by which of two mutually exclusive branches renders) reads CONDITIONALS THAT ARE ATTRIBUTES — Vue v-if/v-else/v-show and Alpine x-if/x-show — so the same toggle written as a Svelte {#if} block or a JSX ternary is control flow the markup model never projects as a branch and is not seen at all.
- 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".
Dimensions
D1 · Cyclomatic Complexity
8 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was KeyedStorageIndexedDB.checkConsistency at 66. A further 1 method(s) were over the threshold but excluded as flat dispatchers (a long switch/match over independent cases: many branches, almost no nesting), the largest being DockPane.Create at 22 — they are counted neither in the figure above nor in this dimension's score.
What to do
- Bring the 8 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with KeyedStorageIndexedDB.checkConsistency (cyclomatic 66), checkConsistency (cyclomatic 66), KeyedStorageIndexedDB.fixOrphanedEntries (cyclomatic 41). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 8 together lifts Cyclomatic Complexity from 7.8 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
- Enforce Cyclomatic Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D2 · Cognitive Complexity
11 method(s) exceeded the cognitive complexity threshold of 15; the worst was KeyedStorageIndexedDB.checkConsistency at 103.
What to do
- Bring the 2 bodies over 60 down to 60 or less in Cognitive Complexity — start with KeyedStorageIndexedDB.checkConsistency (cognitive 103), checkConsistency (cognitive 103). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 2 together lifts Cognitive Complexity from 7.1 to about 7.7/10, projected with the scoring formula itself and assuming each lands exactly at 60; a cleaner split scores higher.
- Enforce Cognitive Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D3 · God Classes
8 god class(es) detected.
What to do
- Resolve the 5 FileTooLong finding(s) in God Classes — start with UI.fs, KeyedStorageIndexedDB.js, Ace.fs. — One of this dimension's main actionable groups (5 warning-level).
- Resolve the 2 MethodTooLong finding(s) in God Classes — start with KeyedStorageIndexedDB.js (2). — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 TooManyMethods finding(s) in God Classes — start with KeyedStorageIndexedDB.js. — One of this dimension's main actionable groups (1 warning-level).
- Enforce God Classes in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D4 · Code Duplication
6 duplicated block group(s) detected.
What to do
- Resolve the 2 Duplicated block (10 lines × 2) finding(s) in Code Duplication — start with Ace.fs, Reactive.fs. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 Duplicated block (9 lines × 2) finding(s) in Code Duplication — start with FileExplorer.fs. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Duplicated block (8 lines × 2) finding(s) in Code Duplication — start with Ace.fs. — One of this dimension's main actionable groups (1 warning-level).
- Enforce Code Duplication in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D5 · Coupling
2 projects, 0 dependency cycle(s), 0 unstable depended-on project(s).
D6 · Cohesion (LCOM4)
1 of 5 classes have LCOM4 above 3.
What to do
- Resolve the 1 Low cohesion finding(s) in Cohesion (LCOM4) — start with SubFolderFileSystem.fs. — One of this dimension's main actionable groups (1 warning-level).
- Enforce Cohesion (LCOM4) in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D8 · Code Coverage
No automated tests — no test code was found in this repository.
What to do
- Resolve the 1 No automated tests finding(s) in Code Coverage. — One of this dimension's main actionable groups (1 issue-level).
- Enforce Code Coverage in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D9 · Test Distribution
No test suite found.
What to do
- Resolve the 1 No tests found finding(s) in Test Distribution. — One of this dimension's main actionable groups (1 recommendation-level).
D12 · Dependency Hygiene
2 outdated, 0 vulnerable, 0 deprecated packages. Those are the NuGet packages; this repository's npm dependencies were read too — 1 outdated of 1 package(s) across 1 lockfile(s).
D13 · Secret Scanning
1 secret(s) detected.
What to do
- Resolve the 2 Leaked secret finding(s) in Secret Scanning — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
- Enforce Secret Scanning in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D14 · License Compliance
0 of 12 packages use a banned license. ★ DEPTH: this repository's MSBuild projects declare 5 direct `PackageReference`(s), and 8 further package(s) were reached beyond them by closing the graph over nuget.org's own nuspec dependency graph — so a banned licence pulled in only by a dependency's OWN dependencies is inside this verdict. A package whose licence nuget.org could not be asked for is not graded, and version ranges are taken at their lower bound, so this is the closure as that graph states it rather than a restored consumer's exact resolution.
D15 · Churn × Complexity Hotspots
Top hotspots: src/SutilOxide/UI.fs (11×22=242)
What to do
- Resolve the 1 Hotspot finding(s) in Churn × Complexity Hotspots — start with UI.fs. — One of this dimension's main actionable groups (1 warning-level).
D26 · Project Cohesion
1 of 2 build units (MSBuild) flagged as possibly oversized/incoherent.
What to do
- Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion. — One of this dimension's main actionable groups (1 recommendation-level).
D27 · Navigability
89 % of calls cross a namespace and 10 % go through an interface, but 89 % of collaborators are co-located — so a call's collaborators sit together and tracing stays easy. Baseline: small — navigation cost is tolerated.
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
4 finding(s): 0 critical, 3 high, 1 medium, 0 low. 3 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens.
What to do
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
- No action in Static Analysis (SAST) — all 3 REDACTED finding(s) are reported here at file:line but scored by D36 (supply-chain provenance), so none is charged to this dimension. — One of this dimension's main actionable groups (3 issue-level, 0 of them charged here).
D30 · Dependency Vulnerabilities
65 finding(s): 12 critical, 38 high, 11 medium, 4 low.
What to do
- Resolve the 36 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (36). — One of this dimension's main actionable groups (36 issue-level).
- Resolve the 11 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (11). — One of this dimension's main actionable groups (11 issue-level).
- Resolve the 2 High vulnerability finding(s) in Dependency Vulnerabilities — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
D34 · Knowledge Freshness
Every significant source file has living knowledge — recently and meaningfully worked. Counted over 29 of the 34 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
D35 · Change Coupling
No strong hidden change-coupling between production files.
D36 · Supply-chain Provenance & Signing
0/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).
What to do
- Resolve the 2 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 2 platform declaration(s) and 0 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
Frontend & cross-cutting dimensions
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. (×7) — src/SutilOxide/CellEditor.fs:403, src/SutilOxide/FileExplorer.fs:466, src/SutilOxide/UI.fs:737, …
- This <div> carries a click handler, which makes it a control, but it has no text, aria-label or labelled child (the icon-only case), so assistive tech has no name to announce for it. Note that switching it to <button type="button"> — the right fix for its keyboard operability — does not give it a name either: an icon-only button still needs one. Add visible text or an aria-label. — src/SutilOxide/CellEditor.fs:506
- This <label> has no for and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label for="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id. (×2) — src/SutilOxide/UI.fs:468, src/SutilOxide/UI.fs:1294
- This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label for>, a wrapping <label>, or aria-label. — src/SutilOxide/UI.fs:674
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
- The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en"). — index.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="sutil-app">, so there is no content here to wrap — render the <main> from the component mounted into it. — 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. (×3) — src/SutilOxide/CellEditor.fs:506, src/SutilOxide/Dock.fs:486, src/SutilOxide/Modal.fs:59
- A click handler on a plain element with no role and no tabindex: even where another element's key handler can reach it, assistive tech can neither focus it nor announce what it is. Use a <button>, or add role + tabindex="0". (×2) — src/SutilOxide/UI.fs:379, src/SutilOxide/UI.fs:472
What to do
- Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href.
AC5 · ARIA correctness
- A plain <div> has the implicit role "generic", which supports no ARIA states, so this aria-checked is dropped and assistive tech is never told the state at all. Put aria-checked on the element that owns the behaviour (the button or control the user operates), or give this <div> a role that supports aria-checked. — src/SutilOxide/UI.fs:379
- This role is not a valid WAI-ARIA role, so assistive tech ignores it. Use a valid role (or the native element). — src/SutilOxide/UI.fs:404
What to do
- Use valid, non-abstract roles, supply the ARIA state each role requires, and never put aria-hidden on a focusable element.
AC6 · Visual & motion safety
AC7 · A11y enforcement
- No accessibility enforcement found — no automated accessibility check runs over the HTML your app renders. Assert the accessibility invariants over that HTML in the test suite you already have (parse the output and assert, or drive a browser), and gate that test in CI so a regression blocks the merge. What was searched, so you can tell an absence from a miss: the 10 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.
What to do
- Enforce accessibility in the test suite you already have: assert the accessibility invariants over the HTML your app renders — parse the rendered output in an existing test, or drive a real browser from one — and gate that test in CI so a regression blocks the merge.
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)
- 22 code files changed in the last 6 months but the README was not touched — it may no longer reflect the system.
What to do
- Add a build/run (quick start) section to the root README — the first thing a newcomer needs.
- Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
- Review the README against recent changes; refresh the parts that drifted.
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.
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 1429 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/App.fsproj` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`. — src/App/App.fsproj:10
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
- No release automation was found in CI — neither a deploy stage (Helm/Kubernetes/compose manifests, an orchestrated rollout) nor a publish job that ships the built artifact. Releases appear to be run by hand, which is slower, less repeatable and harder to reverse.
What to do
- Automate the release in CI — a deploy stage for a service (Helm/Kubernetes manifests or an equivalent rollout), or a tag-triggered publish job for an artifact — so releases are repeatable and reversible.
PF3 · Async & latency hygiene
S1 · Web-Security Posture
- `https://kit.fontawesome.com/a1cdbc2d94.js` is executed by this page with no Subresource Integrity. Whoever can answer that request — the CDN, anyone who compromises it, anyone on the network path — runs arbitrary script in this page's origin, with its session. The URL also names no version, so it resolves to whatever that origin serves at fetch time — the executed bytes can change with nobody touching this repository. — index.html:10
What to do
- Pin third-party scripts and verify them: name an exact version in the URL and add an `integrity="sha384-…"` hash alongside `crossorigin="anonymous"` (both are required — an integrity hash on a cross-origin script without `crossorigin` is not evaluated, it blocks the script). Where the vendor ships a continuously-updated loader and publishes no stable hash (tag managers, analytics, chat widgets), Subresource Integrity is not available: constrain it instead with a `Content-Security-Policy` that names the exact origins allowed to execute, and drop the script from the pages that do not need it. Where the page is shipped inside a package that others host, prefer vendoring the asset and serving it from the app’s own origin, so no consumer inherits a third-party dependency they did not choose.
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 |
|---|---|---|
| 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 |
| AC5 · ARIA correctness | 4.1.2 | 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 | 81% | Strong | Solid. |
| Architecture | 88% | Adequate — gated by D26 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Maturity | 46% | Weak — gated by M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 28% | Weak — gated by D8, D9, P3, P4 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 72% | Adequate — gated by D30, D36 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Accessibility | 28% | Weak — gated by AC3, AC4, AC5 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Performance | 100% | Exemplary | Strongest area. |
Unscored — 1 check(s) recorded observations but carry no score
- SC1 Supply-chain hygiene — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Not evidenced — 5 control(s) we could not find positive evidence for
- C3 Audit Trail — Not assessed: these audit controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks audit controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- C4 Data Retention — Not assessed: these retention controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks retention controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- C5 Data-Subject Rights — Not assessed: these data-subject rights controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks data-subject rights controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
- P6 Release Hygiene — not evidenced — no changelog, version stamp or semver release tag in the repo
Not included — 69 check(s) not relevant to this codebase
- AC1 Text alternatives — No image/media element found in the parsed markup — AC1 not applicable here.
- AX1 Captive dependencies — Not applicable: this repository's F# imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's; this repository's JavaScript imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's.
- AX2 Stateful singletons — No container singleton was found, so there is no shared instance for concurrent requests to race on. No F# function in this code takes an ASP.NET Core or Suave HttpContext (a Giraffe, Saturn, Falco, Oxpecker or Suave handler) and no F# class is an ASP.NET Core controller, so no request handler shares module state between request threads. Its F# is compiled by Fable to JavaScript, which runs on one event loop, so no two requests write a shared object at the same instant. TypeScript/JavaScript runs each process's requests on one event loop, so no two requests write a shared object at the same instant (interleaving across an await is a different defect).
- AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX6 Interface segregation — not assessed — interface segregation is computed over a type surface that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AX8 Test isolation — no test/production split to check
- AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
- AXB1 Runtime evidence locked — no reproducible boot — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- C1 Data Protection — Not assessed: these personal data controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks personal data controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- C2 Access Controls — Not assessed: these authorization controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks authorization controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- D10 Test Quality — 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.
- D16 Bus Factor — single-maintainer repository — bus factor is not applicable
- D17 Explicit Debt — the C# workspace loaded 0 projects, so explicit-debt density could not be measured
- D18 Solution Shape — D18 scores the shape of a C#/VB .NET solution; this repository's .NET projects are all F# (.fsproj), which the C#/VB workspace does not load, so the dimension does not apply.
- D19 Documentation Quality — No runnable or published unit to look for an example in, and no multi-project root README to look for a map in; the other documentation kinds are withheld (see the gaps), so documentation quality is not applicable here.
- D20 ADR Quality — N/A — ADRs are expected on deployable products with a user-facing host, not consumed libraries; no ADR log is required here.
- D21 Naming Consistency — Naming consistency is measured on C# and TypeScript only; F#, JavaScript not measured.
- D22 Internal API Consistency — No intentionally-exposed public API to evaluate for consistency.
- D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D24 Comment Value — D24 reads C# and Visual Basic comments only — this repository's production source is .fs, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D25 ADR Conformance — no ADRs to check
- D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
- D32 Data Compliance (PII/GDPR) — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
- 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.
- 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): 28 value object(s); 2 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 2 current-state document(s) make no claim of a kind M4 checks.
- P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
- P2 Observability — This repository's JavaScript/TypeScript, F# source (3 module(s), 37 file(s) read) declares no entry point and bootstraps no server, and nothing here deploys a service — it is a library, run inside whatever hosts it, so production observability (structured logging, tracing/metrics, health checks) is N/A. If it grows a binary or a service, the dimension reactivates.
- P7 Outbound HTTP resilience — not measured — the application kind could not be determined for this repo
- P8 Schema migrations — 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 12,355 production line(s), 0 such use(s) and no benchmarks, so there is no allocation work to rate. The card is reward-only: its absence costs nothing.
- 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 — 75 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- <input> without a programmatic label src/SutilOxide/CellEditor.fs:403
- <input> without a programmatic label src/SutilOxide/FileExplorer.fs:466
- <input> without a programmatic label src/SutilOxide/UI.fs:674
- <input> without a programmatic label src/SutilOxide/UI.fs:1363
- <input> without a programmatic label src/SutilOxide/UI.fs:1489
- Click handler on a non-interactive <div> src/SutilOxide/CellEditor.fs:506
- Click handler on a non-interactive <div> src/SutilOxide/Dock.fs:486
- Click handler on a non-interactive <div> src/SutilOxide/Modal.fs:59
- Click handler on a non-interactive <div> src/SutilOxide/UI.fs:379
- Click handler on a non-interactive <div> src/SutilOxide/UI.fs:472
- REDACTED
- REDACTED
- REDACTED
- <label> that labels no control src/SutilOxide/UI.fs:468
- <label> that labels no control src/SutilOxide/UI.fs:1294
- <textarea> without a programmatic label src/SutilOxide/UI.fs:737
- <textarea> without a programmatic label src/SutilOxide/UI.fs:1533
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Custom control with no accessible name on <div> src/SutilOxide/CellEditor.fs:506
- <select> without a programmatic label src/SutilOxide/UI.fs:1334
- <html> without a lang index.html:2
- aria-checked on a <div> with no role to carry it src/SutilOxide/UI.fs:379
- Invalid ARIA role "label" src/SutilOxide/UI.fs:404
- REDACTED
- No automated tests
Serious — 49 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- FileTooLong: SutilOxide/UI.fs src/SutilOxide/UI.fs
- FileTooLong: FileSystem/KeyedStorageIndexedDB.js src/SutilOxide/FileSystem/KeyedStorageIndexedDB.js
- FileTooLong: SutilOxide/Ace.fs src/SutilOxide/Ace.fs
- FileTooLong: SutilOxide/Dock.fs src/SutilOxide/Dock.fs
- FileTooLong: FileSystem/KeyedStorageFileSystemAsync.fs src/SutilOxide/FileSystem/KeyedStorageFileSystemAsync.fs
- MethodTooLong: KeyedStorageIndexedDB.checkConsistency src/SutilOxide/FileSystem/KeyedStorageIndexedDB.js:871
- MethodTooLong: KeyedStorageIndexedDB.fixOrphanedEntries src/SutilOxide/FileSystem/KeyedStorageIndexedDB.js:1474
- REDACTED
- REDACTED
- Duplicated block (10 lines × 2) src/SutilOxide/Ace.fs:670
- Duplicated block (10 lines × 2) src/SutilOxide/Reactive.fs:396
- Page without a main landmark index.html:2
- Accessibility enforcement below the top rung
- KeyedStorageIndexedDB.checkConsistency (cyclomatic 66) src/SutilOxide/FileSystem/KeyedStorageIndexedDB.js:871
- KeyedStorageIndexedDB.fixOrphanedEntries (cyclomatic 41) src/SutilOxide/FileSystem/KeyedStorageIndexedDB.js:1474
- KeyedStorageIndexedDB.fixDanglingReferences (cyclomatic 32) src/SutilOxide/FileSystem/KeyedStorageIndexedDB.js:1335
- Dock._update (cyclomatic 30) src/SutilOxide/Dock.fs:187
- Control.renderControlWithParent (cyclomatic 17) src/SutilOxide/UI.fs:373
- Hotspot: src/SutilOxide/UI.fs src/SutilOxide/UI.fs:952
- KeyedStorageIndexedDB.checkConsistency (cognitive 103) src/SutilOxide/FileSystem/KeyedStorageIndexedDB.js:871
- KeyedStorageIndexedDB.fixOrphanedEntries (cognitive 55) src/SutilOxide/FileSystem/KeyedStorageIndexedDB.js:1474
- KeyedStorageIndexedDB.fixDanglingReferences (cognitive 53) src/SutilOxide/FileSystem/KeyedStorageIndexedDB.js:1335
- Dock._update (cognitive 30) src/SutilOxide/Dock.fs:187
- _flushGetBatch (cognitive 23) src/SutilOxide/FileSystem/KeyedStorageIndexedDB.js:634
- KeyedStorageIndexedDB.checkConsistency::buildPath (cognitive 21) src/SutilOxide/FileSystem/KeyedStorageIndexedDB.js:981
- Toolbar.mkButton (cognitive 17) src/SutilOxide/Toolbar.fs:147
- REDACTED
- TooManyMethods: KeyedStorageIndexedDB src/SutilOxide/FileSystem/KeyedStorageIndexedDB.js:36
- REDACTED
- REDACTED
- Duplicated block (9 lines × 2) src/SutilOxide/FileExplorer.fs:423
- Duplicated block (8 lines × 2) src/SutilOxide/Ace.fs:697
- Duplicated block (7 lines × 2) src/SutilOxide/Ace.fs:253
- Duplicated block (5 lines × 2) src/SutilOxide/DomHelpers.fs:146
- Low cohesion: VirtualFileSystem (LCOM4 4) src/SutilOxide/FileSystem/SubFolderFileSystem.fs:63
- README may be stale
- No deployment automation
- Third-party script without Subresource Integrity index.html:10
- NuGet dependencies are not locked
Minor — 14 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Projects may be oversized for their cohesion
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- No tests found
- No ADRs
- No architecture diagram/doc
- No SAST
- No dependency-update automation src/App/App.fsproj:10
Minor — 3 finding(s)
- Outdated: FSharp.Core
- Outdated: Thoth.Json
- Outdated (npm): ace-builds
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-f3ed2693a1a04d29a718ef13c91d3be0/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-f3ed2693a1a04d29a718ef13c91d3be0/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 . | 4 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | dotnet | — | dotnet list sutil-oxide.sln package --vulnerable --include-transitive --format json | 65 | artifacts/raw/dotnet-vulnerable.json |
| D31 · IaC & Container Security | trivy | — | trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan. | 0 | — |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. | 0 | — |
| D37 · Vulnerability-disclosure Policy | disclosure | — | disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | 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 |