Executive summary
fsharpforyou/tour falls short of our standard for production because the project has no automated tests and we found no logging, tracing or health checks in the code. It scores 45 out of 100 and is rated Weak, and 11 of its 13 critical findings are security problems in the build pipeline and in the packages it uses.
Production Readiness, at 24, is the weakest lens and counts most in the score. The best first step for the work it takes is recording design decisions, worth about 10 points. Adding automated tests would lift Production Readiness itself, worth about 18 points. Raising Production Readiness to 70 would lift the score to about 60.
Nine pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Two known security holes in the packages the code depends on can be used by attackers, and the project has no automated tests, so a change can break it without warning. Adding automated tests, pinning each tool to an exact version and updating the vulnerable packages would close these risks. The page or frame without a title needs a descriptive title.
The product code is 7,899 lines, about €7,000 to rebuild.
If Production Readiness rose from 24 to 70, the lowest score rated Strong, the score would rise from 45 to about 60.
Fixed since the last survey: 1 finding
- A11y enforcement · Accessibility enforcement below the top rung package.json
Rebuild cost: about €7,000 · Estimate
| Cost to rebuild | €2,300 to €12,000, for 39 to 123 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 45. 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: 7,899 lines of product code |
| What it is not | Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one. |
Top priorities
Diagnosis: what the measurements show together
Architecture: which parts of the code depend on which
| uses → | 1 App.Helper | 2 App.TourView | 3 App.WebWorker | 4 Constants | 5 Documentation.Json | 6 Editor.Tooltip | 7 Iframe | 8 Documentation | 9 MonacoEditor | 10 MonacoEditor.Monaco.Languages.Css | 11 MonacoEditor.Monaco.Languages.Html | 12 MonacoEditor.Monaco.Languages.Json | 13 MonacoEditor.Monaco.Languages.Typescript | 14 Documentation.TableOfContentsModule | 15 MonacoEditor.Monaco.Editor | 16 Navigation | 17 MonacoEditor.Monaco.Languages | 18 Navigation.PageModule | 19 MonacoEditor.Monaco | 20 App | 21 Editor | 22 MonacoEditor.Monaco.Worker | 23 App.LogLevelModule | 24 App.ThemeModule |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 App.Helper | ||||||||||||||||||||||||
| 2 App.TourView | ||||||||||||||||||||||||
| 3 App.WebWorker | ||||||||||||||||||||||||
| 4 Constants | ||||||||||||||||||||||||
| 5 Documentation.Json | ||||||||||||||||||||||||
| 6 Editor.Tooltip | ||||||||||||||||||||||||
| 7 Iframe | ||||||||||||||||||||||||
| 8 Documentation | 3 | |||||||||||||||||||||||
| 9 MonacoEditor | 2 | |||||||||||||||||||||||
| 10 MonacoEditor.Monaco.Languages.Css | 1 | |||||||||||||||||||||||
| 11 MonacoEditor.Monaco.Languages.Html | 2 | |||||||||||||||||||||||
| 12 MonacoEditor.Monaco.Languages.Json | 1 | |||||||||||||||||||||||
| 13 MonacoEditor.Monaco.Languages.Typescript | 2 | |||||||||||||||||||||||
| 14 Documentation.TableOfContentsModule | 2 | |||||||||||||||||||||||
| 15 MonacoEditor.Monaco.Editor | 1 | 77 | ||||||||||||||||||||||
| 16 Navigation | 4 | |||||||||||||||||||||||
| 17 MonacoEditor.Monaco.Languages | 1 | 1 | 1 | 1 | 31 | 85 | ||||||||||||||||||
| 18 Navigation.PageModule | 1 | 1 | ||||||||||||||||||||||
| 19 MonacoEditor.Monaco | 1 | 1 | ||||||||||||||||||||||
| 20 App | 3 | 7 | 3 | 1 | ||||||||||||||||||||
| 21 Editor | 2 | 6 | 2 | |||||||||||||||||||||
| 22 MonacoEditor.Monaco.Worker | 1 | |||||||||||||||||||||||
| 23 App.LogLevelModule | 1 | |||||||||||||||||||||||
| 24 App.ThemeModule | 1 |
8→5 Documentation uses Documentation.Json✕
- Connections
- 3 pairs of types, where a type in Documentation uses a type in Documentation.Json.
- The types involved
Documentation.Documentation→Documentation.Json.CategoryJsonDocumentation.Documentation→Documentation.Json.PageJsonDocumentation.Documentation→Documentation.Json.TableOfContentsJson
- Direction
- Documentation uses Documentation.Json, so a change to Documentation.Json can break Documentation, while a change to Documentation can't break Documentation.Json.
- Position
- Below the diagonal: Documentation uses a module listed above it, which is the healthy direction.
9→19 MonacoEditor uses MonacoEditor.Monaco part of a loop✕
- Connections
- 2 pairs of types, where a type in MonacoEditor uses a type in MonacoEditor.Monaco.
- The types involved
MonacoEditor.MonacoEditor→MonacoEditor.Monaco.EnvironmentMonacoEditor.Window→MonacoEditor.Monaco.Environment
- Direction
- MonacoEditor uses MonacoEditor.Monaco, so a change to MonacoEditor.Monaco can break MonacoEditor, while a change to MonacoEditor can't break MonacoEditor.Monaco.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
10→19 MonacoEditor.Monaco.Languages.Css uses MonacoEditor.Monaco part of a loop✕
- Connections
- 1 pair of types, where a type in MonacoEditor.Monaco.Languages.Css uses a type in MonacoEditor.Monaco.
- The types involved
MonacoEditor.Monaco.Languages.Css.LanguageServiceDefaults→MonacoEditor.Monaco.IEvent`1
- Direction
- MonacoEditor.Monaco.Languages.Css uses MonacoEditor.Monaco, so a change to MonacoEditor.Monaco can break MonacoEditor.Monaco.Languages.Css, while a change to MonacoEditor.Monaco.Languages.Css can't break MonacoEditor.Monaco.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
11→19 MonacoEditor.Monaco.Languages.Html uses MonacoEditor.Monaco part of a loop✕
- Connections
- 2 pairs of types, where a type in MonacoEditor.Monaco.Languages.Html uses a type in MonacoEditor.Monaco.
- The types involved
MonacoEditor.Monaco.Languages.Html.LanguageServiceDefaults→MonacoEditor.Monaco.IEvent`1MonacoEditor.Monaco.Languages.Html.LanguageServiceRegistration→MonacoEditor.Monaco.IDisposable
- Direction
- MonacoEditor.Monaco.Languages.Html uses MonacoEditor.Monaco, so a change to MonacoEditor.Monaco can break MonacoEditor.Monaco.Languages.Html, while a change to MonacoEditor.Monaco.Languages.Html can't break MonacoEditor.Monaco.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
12→19 MonacoEditor.Monaco.Languages.Json uses MonacoEditor.Monaco part of a loop✕
- Connections
- 1 pair of types, where a type in MonacoEditor.Monaco.Languages.Json uses a type in MonacoEditor.Monaco.
- The types involved
MonacoEditor.Monaco.Languages.Json.LanguageServiceDefaults→MonacoEditor.Monaco.IEvent`1
- Direction
- MonacoEditor.Monaco.Languages.Json uses MonacoEditor.Monaco, so a change to MonacoEditor.Monaco can break MonacoEditor.Monaco.Languages.Json, while a change to MonacoEditor.Monaco.Languages.Json can't break MonacoEditor.Monaco.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
13→19 MonacoEditor.Monaco.Languages.Typescript uses MonacoEditor.Monaco part of a loop✕
- Connections
- 2 pairs of types, where a type in MonacoEditor.Monaco.Languages.Typescript uses a type in MonacoEditor.Monaco.
- The types involved
MonacoEditor.Monaco.Languages.Typescript.LanguageServiceDefaults→MonacoEditor.Monaco.IDisposableMonacoEditor.Monaco.Languages.Typescript.LanguageServiceDefaults→MonacoEditor.Monaco.IEvent`1
- Direction
- MonacoEditor.Monaco.Languages.Typescript uses MonacoEditor.Monaco, so a change to MonacoEditor.Monaco can break MonacoEditor.Monaco.Languages.Typescript, while a change to MonacoEditor.Monaco.Languages.Typescript can't break MonacoEditor.Monaco.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
14→8 Documentation.TableOfContentsModule uses Documentation✕
- Connections
- 2 pairs of types, where a type in Documentation.TableOfContentsModule uses a type in Documentation.
- The types involved
Documentation.TableOfContentsModule.TableOfContentsModule→Documentation.PageDocumentation.TableOfContentsModule.TableOfContentsModule→Documentation.TableOfContents
- Direction
- Documentation.TableOfContentsModule uses Documentation, so a change to Documentation can break Documentation.TableOfContentsModule, while a change to Documentation.TableOfContentsModule can't break Documentation.
- Position
- Below the diagonal: Documentation.TableOfContentsModule uses a module listed above it, which is the healthy direction.
15→9 MonacoEditor.Monaco.Editor uses MonacoEditor✕
- Connections
- 1 pair of types, where a type in MonacoEditor.Monaco.Editor uses a type in MonacoEditor.
- The types involved
MonacoEditor.Monaco.Editor.IUnicodeHighlightOptions→MonacoEditor.Record`2
- Direction
- MonacoEditor.Monaco.Editor uses MonacoEditor, so a change to MonacoEditor can break MonacoEditor.Monaco.Editor, while a change to MonacoEditor.Monaco.Editor can't break MonacoEditor.
- Position
- Below the diagonal: MonacoEditor.Monaco.Editor uses a module listed above it, which is the healthy direction.
15→19 MonacoEditor.Monaco.Editor uses MonacoEditor.Monaco part of a loop✕
- Connections
- 77 pairs of types, where a type in MonacoEditor.Monaco.Editor uses a type in MonacoEditor.Monaco. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
MonacoEditor.Monaco.Editor.FindMatch→MonacoEditor.Monaco.RangeMonacoEditor.Monaco.Editor.IBaseMouseTarget→MonacoEditor.Monaco.PositionMonacoEditor.Monaco.Editor.IBaseMouseTarget→MonacoEditor.Monaco.RangeMonacoEditor.Monaco.Editor.ICodeEditor→MonacoEditor.Monaco.IEvent`1MonacoEditor.Monaco.Editor.ICodeEditor→MonacoEditor.Monaco.IKeyboardEventMonacoEditor.Monaco.Editor.ICodeEditor→MonacoEditor.Monaco.IPositionMonacoEditor.Monaco.Editor.ICodeEditor→MonacoEditor.Monaco.IScrollEventMonacoEditor.Monaco.Editor.ICodeEditor→MonacoEditor.Monaco.RangeMonacoEditor.Monaco.Editor.ICodeEditor→MonacoEditor.Monaco.SelectionMonacoEditor.Monaco.Editor.ICodeEditorOpener→MonacoEditor.Monaco.IPositionMonacoEditor.Monaco.Editor.ICodeEditorOpener→MonacoEditor.Monaco.IRangeMonacoEditor.Monaco.Editor.ICodeEditorOpener→MonacoEditor.Monaco.UriMonacoEditor.Monaco.Editor.ICommand→MonacoEditor.Monaco.SelectionMonacoEditor.Monaco.Editor.IContentWidgetPosition→MonacoEditor.Monaco.IPositionMonacoEditor.Monaco.Editor.ICursorPositionChangedEvent→MonacoEditor.Monaco.PositionMonacoEditor.Monaco.Editor.ICursorSelectionChangedEvent→MonacoEditor.Monaco.SelectionMonacoEditor.Monaco.Editor.ICursorState→MonacoEditor.Monaco.IPositionMonacoEditor.Monaco.Editor.ICursorStateComputer→MonacoEditor.Monaco.SelectionMonacoEditor.Monaco.Editor.ICursorStateComputerData→MonacoEditor.Monaco.SelectionMonacoEditor.Monaco.Editor.IDiffEditor→MonacoEditor.Monaco.IEvent`1MonacoEditor.Monaco.Editor.IEditOperationBuilder→MonacoEditor.Monaco.IRangeMonacoEditor.Monaco.Editor.IEditOperationBuilder→MonacoEditor.Monaco.SelectionMonacoEditor.Monaco.Editor.IEditor→MonacoEditor.Monaco.IDisposableMonacoEditor.Monaco.Editor.IEditor→MonacoEditor.Monaco.IPositionMonacoEditor.Monaco.Editor.IEditor→MonacoEditor.Monaco.IRange
- Direction
- MonacoEditor.Monaco.Editor uses MonacoEditor.Monaco, so a change to MonacoEditor.Monaco can break MonacoEditor.Monaco.Editor, while a change to MonacoEditor.Monaco.Editor can't break MonacoEditor.Monaco.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
16→8 Navigation uses Documentation✕
- Connections
- 4 pairs of types, where a type in Navigation uses a type in Documentation.
- The types involved
Navigation.CurrentEntry→Documentation.PageNavigation.DocEntryNavigation→Documentation.PageNavigation.Navigation→Documentation.PageNavigation.Page→Documentation.Page
- Direction
- Navigation uses Documentation, so a change to Documentation can break Navigation, while a change to Navigation can't break Documentation.
- Position
- Below the diagonal: Navigation uses a module listed above it, which is the healthy direction.
17→10 MonacoEditor.Monaco.Languages uses MonacoEditor.Monaco.Languages.Css✕
- Connections
- 1 pair of types, where a type in MonacoEditor.Monaco.Languages uses a type in MonacoEditor.Monaco.Languages.Css.
- The types involved
MonacoEditor.Monaco.Languages.Languages→MonacoEditor.Monaco.Languages.Css.IExports
- Direction
- MonacoEditor.Monaco.Languages uses MonacoEditor.Monaco.Languages.Css, so a change to MonacoEditor.Monaco.Languages.Css can break MonacoEditor.Monaco.Languages, while a change to MonacoEditor.Monaco.Languages can't break MonacoEditor.Monaco.Languages.Css.
- Position
- Below the diagonal: MonacoEditor.Monaco.Languages uses a module listed above it, which is the healthy direction.
17→11 MonacoEditor.Monaco.Languages uses MonacoEditor.Monaco.Languages.Html✕
- Connections
- 1 pair of types, where a type in MonacoEditor.Monaco.Languages uses a type in MonacoEditor.Monaco.Languages.Html.
- The types involved
MonacoEditor.Monaco.Languages.Languages→MonacoEditor.Monaco.Languages.Html.IExports
- Direction
- MonacoEditor.Monaco.Languages uses MonacoEditor.Monaco.Languages.Html, so a change to MonacoEditor.Monaco.Languages.Html can break MonacoEditor.Monaco.Languages, while a change to MonacoEditor.Monaco.Languages can't break MonacoEditor.Monaco.Languages.Html.
- Position
- Below the diagonal: MonacoEditor.Monaco.Languages uses a module listed above it, which is the healthy direction.
17→12 MonacoEditor.Monaco.Languages uses MonacoEditor.Monaco.Languages.Json✕
- Connections
- 1 pair of types, where a type in MonacoEditor.Monaco.Languages uses a type in MonacoEditor.Monaco.Languages.Json.
- The types involved
MonacoEditor.Monaco.Languages.Languages→MonacoEditor.Monaco.Languages.Json.IExports
- Direction
- MonacoEditor.Monaco.Languages uses MonacoEditor.Monaco.Languages.Json, so a change to MonacoEditor.Monaco.Languages.Json can break MonacoEditor.Monaco.Languages, while a change to MonacoEditor.Monaco.Languages can't break MonacoEditor.Monaco.Languages.Json.
- Position
- Below the diagonal: MonacoEditor.Monaco.Languages uses a module listed above it, which is the healthy direction.
17→13 MonacoEditor.Monaco.Languages uses MonacoEditor.Monaco.Languages.Typescript✕
- Connections
- 1 pair of types, where a type in MonacoEditor.Monaco.Languages uses a type in MonacoEditor.Monaco.Languages.Typescript.
- The types involved
MonacoEditor.Monaco.Languages.Languages→MonacoEditor.Monaco.Languages.Typescript.IExports
- Direction
- MonacoEditor.Monaco.Languages uses MonacoEditor.Monaco.Languages.Typescript, so a change to MonacoEditor.Monaco.Languages.Typescript can break MonacoEditor.Monaco.Languages, while a change to MonacoEditor.Monaco.Languages can't break MonacoEditor.Monaco.Languages.Typescript.
- Position
- Below the diagonal: MonacoEditor.Monaco.Languages uses a module listed above it, which is the healthy direction.
17→15 MonacoEditor.Monaco.Languages uses MonacoEditor.Monaco.Editor✕
- Connections
- 31 pairs of types, where a type in MonacoEditor.Monaco.Languages uses a type in MonacoEditor.Monaco.Editor. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
MonacoEditor.Monaco.Languages.CodeAction→MonacoEditor.Monaco.Editor.IMarkerDataMonacoEditor.Monaco.Languages.CodeActionContext→MonacoEditor.Monaco.Editor.IMarkerDataMonacoEditor.Monaco.Languages.CodeActionProvider→MonacoEditor.Monaco.Editor.ITextModelMonacoEditor.Monaco.Languages.CodeLensProvider→MonacoEditor.Monaco.Editor.ITextModelMonacoEditor.Monaco.Languages.CompletionItem→MonacoEditor.Monaco.Editor.ISingleEditOperationMonacoEditor.Monaco.Languages.CompletionItemProvider→MonacoEditor.Monaco.Editor.ITextModelMonacoEditor.Monaco.Languages.DeclarationProvider→MonacoEditor.Monaco.Editor.ITextModelMonacoEditor.Monaco.Languages.DefinitionProvider→MonacoEditor.Monaco.Editor.ITextModelMonacoEditor.Monaco.Languages.DocumentColorProvider→MonacoEditor.Monaco.Editor.ITextModelMonacoEditor.Monaco.Languages.DocumentFormattingEditProvider→MonacoEditor.Monaco.Editor.ITextModelMonacoEditor.Monaco.Languages.DocumentHighlightProvider→MonacoEditor.Monaco.Editor.ITextModelMonacoEditor.Monaco.Languages.DocumentRangeFormattingEditProvider→MonacoEditor.Monaco.Editor.ITextModelMonacoEditor.Monaco.Languages.DocumentRangeSemanticTokensProvider→MonacoEditor.Monaco.Editor.ITextModelMonacoEditor.Monaco.Languages.DocumentSemanticTokensProvider→MonacoEditor.Monaco.Editor.ITextModelMonacoEditor.Monaco.Languages.DocumentSymbolProvider→MonacoEditor.Monaco.Editor.ITextModelMonacoEditor.Monaco.Languages.FoldingRangeProvider→MonacoEditor.Monaco.Editor.ITextModelMonacoEditor.Monaco.Languages.HoverProvider→MonacoEditor.Monaco.Editor.ITextModelMonacoEditor.Monaco.Languages.ImplementationProvider→MonacoEditor.Monaco.Editor.ITextModelMonacoEditor.Monaco.Languages.InlayHintsProvider→MonacoEditor.Monaco.Editor.ITextModelMonacoEditor.Monaco.Languages.InlineCompletion→MonacoEditor.Monaco.Editor.ISingleEditOperationMonacoEditor.Monaco.Languages.InlineCompletionsProvider`1→MonacoEditor.Monaco.Editor.ITextModelMonacoEditor.Monaco.Languages.LinkProvider→MonacoEditor.Monaco.Editor.ITextModelMonacoEditor.Monaco.Languages.LinkedEditingRangeProvider→MonacoEditor.Monaco.Editor.ITextModelMonacoEditor.Monaco.Languages.MappedEditsProvider→MonacoEditor.Monaco.Editor.ITextModelMonacoEditor.Monaco.Languages.OnTypeFormattingEditProvider→MonacoEditor.Monaco.Editor.ITextModel
- Direction
- MonacoEditor.Monaco.Languages uses MonacoEditor.Monaco.Editor, so a change to MonacoEditor.Monaco.Editor can break MonacoEditor.Monaco.Languages, while a change to MonacoEditor.Monaco.Languages can't break MonacoEditor.Monaco.Editor.
- Position
- Below the diagonal: MonacoEditor.Monaco.Languages uses a module listed above it, which is the healthy direction.
17→19 MonacoEditor.Monaco.Languages uses MonacoEditor.Monaco part of a loop✕
- Connections
- 85 pairs of types, where a type in MonacoEditor.Monaco.Languages uses a type in MonacoEditor.Monaco. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
MonacoEditor.Monaco.Languages.CodeActionList→MonacoEditor.Monaco.IDisposableMonacoEditor.Monaco.Languages.CodeActionProvider→MonacoEditor.Monaco.CancellationTokenMonacoEditor.Monaco.Languages.CodeActionProvider→MonacoEditor.Monaco.RangeMonacoEditor.Monaco.Languages.CodeLens→MonacoEditor.Monaco.IRangeMonacoEditor.Monaco.Languages.CodeLensProvider→MonacoEditor.Monaco.CancellationTokenMonacoEditor.Monaco.Languages.CodeLensProvider→MonacoEditor.Monaco.IEvent`1MonacoEditor.Monaco.Languages.CompletionItem→MonacoEditor.Monaco.IMarkdownStringMonacoEditor.Monaco.Languages.CompletionItem→MonacoEditor.Monaco.IRangeMonacoEditor.Monaco.Languages.CompletionItemProvider→MonacoEditor.Monaco.CancellationTokenMonacoEditor.Monaco.Languages.CompletionItemProvider→MonacoEditor.Monaco.PositionMonacoEditor.Monaco.Languages.CompletionItemRanges→MonacoEditor.Monaco.IRangeMonacoEditor.Monaco.Languages.DeclarationProvider→MonacoEditor.Monaco.CancellationTokenMonacoEditor.Monaco.Languages.DeclarationProvider→MonacoEditor.Monaco.PositionMonacoEditor.Monaco.Languages.DefinitionProvider→MonacoEditor.Monaco.CancellationTokenMonacoEditor.Monaco.Languages.DefinitionProvider→MonacoEditor.Monaco.PositionMonacoEditor.Monaco.Languages.DocumentColorProvider→MonacoEditor.Monaco.CancellationTokenMonacoEditor.Monaco.Languages.DocumentContextItem→MonacoEditor.Monaco.IRangeMonacoEditor.Monaco.Languages.DocumentContextItem→MonacoEditor.Monaco.UriMonacoEditor.Monaco.Languages.DocumentFormattingEditProvider→MonacoEditor.Monaco.CancellationTokenMonacoEditor.Monaco.Languages.DocumentHighlight→MonacoEditor.Monaco.IRangeMonacoEditor.Monaco.Languages.DocumentHighlightProvider→MonacoEditor.Monaco.CancellationTokenMonacoEditor.Monaco.Languages.DocumentHighlightProvider→MonacoEditor.Monaco.PositionMonacoEditor.Monaco.Languages.DocumentRangeFormattingEditProvider→MonacoEditor.Monaco.CancellationTokenMonacoEditor.Monaco.Languages.DocumentRangeFormattingEditProvider→MonacoEditor.Monaco.RangeMonacoEditor.Monaco.Languages.DocumentRangeSemanticTokensProvider→MonacoEditor.Monaco.CancellationToken
- Direction
- MonacoEditor.Monaco.Languages uses MonacoEditor.Monaco, so a change to MonacoEditor.Monaco can break MonacoEditor.Monaco.Languages, while a change to MonacoEditor.Monaco.Languages can't break MonacoEditor.Monaco.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
18→8 Navigation.PageModule uses Documentation✕
- Connections
- 1 pair of types, where a type in Navigation.PageModule uses a type in Documentation.
- The types involved
Navigation.PageModule.PageModule→Documentation.Page
- Direction
- Navigation.PageModule uses Documentation, so a change to Documentation can break Navigation.PageModule, while a change to Navigation.PageModule can't break Documentation.
- Position
- Below the diagonal: Navigation.PageModule uses a module listed above it, which is the healthy direction.
18→16 Navigation.PageModule uses Navigation✕
- Connections
- 1 pair of types, where a type in Navigation.PageModule uses a type in Navigation.
- The types involved
Navigation.PageModule.PageModule→Navigation.Page
- Direction
- Navigation.PageModule uses Navigation, so a change to Navigation can break Navigation.PageModule, while a change to Navigation.PageModule can't break Navigation.
- Position
- Below the diagonal: Navigation.PageModule uses a module listed above it, which is the healthy direction.
19→15 MonacoEditor.Monaco uses MonacoEditor.Monaco.Editor✕
- Connections
- 1 pair of types, where a type in MonacoEditor.Monaco uses a type in MonacoEditor.Monaco.Editor.
- The types involved
MonacoEditor.Monaco.Monaco→MonacoEditor.Monaco.Editor.IExports
- Direction
- MonacoEditor.Monaco uses MonacoEditor.Monaco.Editor, so a change to MonacoEditor.Monaco.Editor can break MonacoEditor.Monaco, while a change to MonacoEditor.Monaco can't break MonacoEditor.Monaco.Editor.
- Position
- Below the diagonal: MonacoEditor.Monaco uses a module listed above it, which is the healthy direction.
19→17 MonacoEditor.Monaco uses MonacoEditor.Monaco.Languages✕
- Connections
- 1 pair of types, where a type in MonacoEditor.Monaco uses a type in MonacoEditor.Monaco.Languages.
- The types involved
MonacoEditor.Monaco.Monaco→MonacoEditor.Monaco.Languages.IExports
- Direction
- MonacoEditor.Monaco uses MonacoEditor.Monaco.Languages, so a change to MonacoEditor.Monaco.Languages can break MonacoEditor.Monaco, while a change to MonacoEditor.Monaco can't break MonacoEditor.Monaco.Languages.
- Position
- Below the diagonal: MonacoEditor.Monaco uses a module listed above it, which is the healthy direction.
20→8 App uses Documentation✕
- Connections
- 3 pairs of types, where a type in App uses a type in Documentation.
- The types involved
App.App→Documentation.TableOfContentsApp.Model→Documentation.TableOfContentsApp.Msg→Documentation.TableOfContents
- Direction
- App uses Documentation, so a change to Documentation can break App, while a change to App can't break Documentation.
- Position
- Below the diagonal: App uses a module listed above it, which is the healthy direction.
20→15 App uses MonacoEditor.Monaco.Editor✕
- Connections
- 7 pairs of types, where a type in App uses a type in MonacoEditor.Monaco.Editor.
- The types involved
App.App→MonacoEditor.Monaco.Editor.IMarkerDataApp.App→MonacoEditor.Monaco.Editor.IStandaloneCodeEditorApp.Model→MonacoEditor.Monaco.Editor.IMarkerDataApp.Model→MonacoEditor.Monaco.Editor.IStandaloneCodeEditorApp.MonacoEditor→MonacoEditor.Monaco.Editor.IStandaloneCodeEditorApp.Msg→MonacoEditor.Monaco.Editor.IMarkerDataApp.Msg→MonacoEditor.Monaco.Editor.IStandaloneCodeEditor
- Direction
- App uses MonacoEditor.Monaco.Editor, so a change to MonacoEditor.Monaco.Editor can break App, while a change to App can't break MonacoEditor.Monaco.Editor.
- Position
- Below the diagonal: App uses a module listed above it, which is the healthy direction.
20→16 App uses Navigation✕
- Connections
- 3 pairs of types, where a type in App uses a type in Navigation.
- The types involved
App.App→Navigation.PageApp.Model→Navigation.DocEntryNavigationApp.Model→Navigation.Page
- Direction
- App uses Navigation, so a change to Navigation can break App, while a change to App can't break Navigation.
- Position
- Below the diagonal: App uses a module listed above it, which is the healthy direction.
20→19 App uses MonacoEditor.Monaco✕
- Connections
- 1 pair of types, where a type in App uses a type in MonacoEditor.Monaco.
- The types involved
App.MonacoEditor→MonacoEditor.Monaco.IExports
- Direction
- App uses MonacoEditor.Monaco, so a change to MonacoEditor.Monaco can break App, while a change to App can't break MonacoEditor.Monaco.
- Position
- Below the diagonal: App uses a module listed above it, which is the healthy direction.
21→15 Editor uses MonacoEditor.Monaco.Editor✕
- Connections
- 2 pairs of types, where a type in Editor uses a type in MonacoEditor.Monaco.Editor.
- The types involved
Editor.Editor→MonacoEditor.Monaco.Editor.IMarkerDataEditor.Editor→MonacoEditor.Monaco.Editor.IStandaloneCodeEditor
- Direction
- Editor uses MonacoEditor.Monaco.Editor, so a change to MonacoEditor.Monaco.Editor can break Editor, while a change to Editor can't break MonacoEditor.Monaco.Editor.
- Position
- Below the diagonal: Editor uses a module listed above it, which is the healthy direction.
21→17 Editor uses MonacoEditor.Monaco.Languages✕
- Connections
- 6 pairs of types, where a type in Editor uses a type in MonacoEditor.Monaco.Languages.
- The types involved
Editor.Editor→MonacoEditor.Monaco.Languages.CompletionItemEditor.Editor→MonacoEditor.Monaco.Languages.CompletionItemKindEditor.Editor→MonacoEditor.Monaco.Languages.CompletionItemProviderEditor.Editor→MonacoEditor.Monaco.Languages.CompletionListEditor.Editor→MonacoEditor.Monaco.Languages.DefinitionProviderEditor.Editor→MonacoEditor.Monaco.Languages.HoverProvider
- Direction
- Editor uses MonacoEditor.Monaco.Languages, so a change to MonacoEditor.Monaco.Languages can break Editor, while a change to Editor can't break MonacoEditor.Monaco.Languages.
- Position
- Below the diagonal: Editor uses a module listed above it, which is the healthy direction.
21→19 Editor uses MonacoEditor.Monaco✕
- Connections
- 2 pairs of types, where a type in Editor uses a type in MonacoEditor.Monaco.
- The types involved
Editor.Editor→MonacoEditor.Monaco.IExportsEditor.Editor→MonacoEditor.Monaco.IRange
- Direction
- Editor uses MonacoEditor.Monaco, so a change to MonacoEditor.Monaco can break Editor, while a change to Editor can't break MonacoEditor.Monaco.
- Position
- Below the diagonal: Editor uses a module listed above it, which is the healthy direction.
22→19 MonacoEditor.Monaco.Worker uses MonacoEditor.Monaco✕
- Connections
- 1 pair of types, where a type in MonacoEditor.Monaco.Worker uses a type in MonacoEditor.Monaco.
- The types involved
MonacoEditor.Monaco.Worker.IMirrorModel→MonacoEditor.Monaco.Uri
- Direction
- MonacoEditor.Monaco.Worker uses MonacoEditor.Monaco, so a change to MonacoEditor.Monaco can break MonacoEditor.Monaco.Worker, while a change to MonacoEditor.Monaco.Worker can't break MonacoEditor.Monaco.
- Position
- Below the diagonal: MonacoEditor.Monaco.Worker uses a module listed above it, which is the healthy direction.
23→20 App.LogLevelModule uses App✕
- Connections
- 1 pair of types, where a type in App.LogLevelModule uses a type in App.
- The types involved
App.LogLevelModule.LogLevelModule→App.LogLevel
- Direction
- App.LogLevelModule uses App, so a change to App can break App.LogLevelModule, while a change to App.LogLevelModule can't break App.
- Position
- Below the diagonal: App.LogLevelModule uses a module listed above it, which is the healthy direction.
24→20 App.ThemeModule uses App✕
- Connections
- 1 pair of types, where a type in App.ThemeModule uses a type in App.
- The types involved
App.ThemeModule.ThemeModule→App.Theme
- Direction
- App.ThemeModule uses App, so a change to App can break App.ThemeModule, while a change to App.ThemeModule can't break App.
- Position
- Below the diagonal: App.ThemeModule uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
At a glance — Accessibility
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A05:2025 — Injection | 13 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 8 | High / Critical |
Roadmap
Top priorities: Resolve the 1 No automated tests finding(s) in Code Coverage; Resolve the 1 No ADRs found finding(s) in ADR Quality — start with App.fsproj; Resolve the 2 Outdated (npm) finding(s) in Dependency Hygiene.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 1 No ADRs found finding(s) in ADR Quality — start with App.fsproj. | +10.0 pts | Low | ADR Quality |
| Resolve the 2 Outdated (npm) finding(s) in Dependency Hygiene. | +9.1 pts | Low | Dependency Hygiene |
| Resolve the 1 No automated tests finding(s) in Code Coverage. | +18.2 pts | High | Code Coverage |
| Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them. | +7.3 pts | Medium | Architecture documentation |
| Write a diagnostic trail the user can hand back with a bug report: a log file under the platform's per-user data directory, switchable with a `--verbose`/`--debug` flag. Start with the error paths that emit nothing — a discarded error is the failure the user cannot describe and you cannot reproduce. | +6.0 pts | Medium | Observability |
| Expand the README with getting-started, architecture overview and a project map. | +3.7 pts | Medium | Documentation (README) |
| Make sure a person approves each release. The release job names an environment, but its approval rules live in the code host's settings, where we can't see them. Check that a reviewer must approve each release, or publish releases as drafts first, so a bad build can be stopped before anyone downloads it. | +2.3 pts | Medium | Deployment & Rollback |
| Resolve the 1 Hotspot finding(s) in Churn × Complexity Hotspots — start with App.fs. | +1.1 pts | Medium | Churn × Complexity Hotspots |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 0.8 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.0 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.8 | Mixed | Dependency Vulnerabilities: High CVE: REDACTED |
| src/App/Libs/Monaco.fs | 7.2 | Mixed | God Classes: FileTooLong: Libs/Monaco.fs |
| src/App/App.fs | 7.4 | Mixed | Cyclomatic Complexity: TourView.AppView (cyclomatic 26) |
| src/App/App.fsproj | 9.5 | Near-clean | ADR Quality: No ADRs found |
How the grades work
A definite problem that already costs you something and drags the score down: a missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here tends to cause failures elsewhere.
Likely wrong, but not failing yet. It degrades the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to carry for two years either.
Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.
Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.
Methodology & how to trust this report
This survey is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. All 36 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.9, the weighted average across measured dimensions.
What we checked — 36 dimensions across the health lenses
- Can you open the finding? Real findings cite a repo-relative file and line you can open at the cited line — never an absolute scratch path. Here, 30 of 110 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Canine Code Analyzer duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 | ✓ deterministic |
Run transparency — what happened this run
- D14 License Compliance — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This repository declares package.json, but the licence verdict published here was taken over its NuGet package dependencies. Nothing was read about its npm dependencies' licensing in either direction, and a clean score on this card must not be read as covering them.
- D15 Churn × Complexity Hotspots — measured, with a gap in what it reached — We measured this, but not all of it. What we 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/App/App.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. Too few commits for a meaningful bus factor (41 commit(s) sampled, fewer than the 50 this dimension needs before a bus factor means anything).
- D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
- D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22 identifies the intentionally-exposed surface from `IsPackable` and `.Contracts` project names, MSBuild conventions read off the loaded project set. This target exposed no such projects, so the probe never ran; this says nothing about whether the repository has a public API. This repository commits no C#/VB source at all, so there was never an MSBuild project set to read these conventions off. That is OUR side and it is a COLLECTOR gap, not an environment fault: no published-package marker D22 reads admitted any project here, so this ecosystem's public API has no collector, and the remedy is to write one — no change to the scan image can close it.
- D24 Comment Value — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Each source language's comment syntax, and the code a comment annotates in it, needs its own proof before D24 judges it. Until then those comments are left unread, not counted as clean.
- D26 Project Cohesion — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `src/App` (7899 LoC, 515 module-visible types across 2 directories) is over its size bounds, and whether one unit is a coherent whole or a grab-bag is read from its type references: the parts of it that reach the rest only through its shared core. Those are read over the C#/VB code model, which this unit's source did not supply. Its size alone is no verdict on its cohesion, so none is published.
- D34 Knowledge Freshness — 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. Too few commits to judge knowledge freshness (41 commit(s) sampled).
- AX6 Interface segregation — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is computed over the public interfaces this run's compilations declare, and none was loaded, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- AXB2 Runtime readiness — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. The dev server kept running but no port it opened served a page in the time allowed. (rule: no-answer). The renderer reported: the dev server (`npm run start`) kept running but served no page within 2 minutes. Likely cause (not identified): the dev server kept running but no port it opened served a page in the time allowed. Last output: "at Microsoft.FSharp.Primitives.Basics.List.collect[T,TResult](FSharpFunc`2 f, FSharpList`1 list) in <path>:line 443 / at Fable.Transforms.FSharp2Fable.Compiler.transformFile(Compiler com) in <path>:line 2984 / at Fable.Cli.Pipeline.Js.compileFile@174.Invoke(Unit unitVar) in <path>:line 180 / at Microsoft.FSharp.Control.AsyncPrimitives.CallThenInvoke[T,TResult](AsyncActivation`1 ctxt, TResult result1, FSharpFunc`2 part2) in <path>:line 509 / at Microsoft.FSharp.Control.Trampoline.Execute(FSharpFunc`2 firstAction) in <path>:line 112 / Watching src" No runtime evidence was gathered.
- AXR1 Runtime accessibility — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via DevServer (start). the dev server (`npm run start`) kept running but served no page within 2 minutes. Likely cause (not identified): the dev server kept running but no port it opened served a page in the time allowed. Last output: "at Microsoft.FSharp.Primitives.Basics.List.collect[T,TResult](FSharpFunc`2 f, FSharpList`1 list) in <path>:line 443 / at Fable.Transforms.FSharp2Fable.Compiler.transformFile(Compiler com) in <path>:line 2984 / at Fable.Cli.Pipeline.Js.compileFile@174.Invoke(Unit unitVar) in <path>:line 180 / at Microsoft.FSharp.Control.AsyncPrimitives.CallThenInvoke[T,TResult](AsyncActivation`1 ctxt, TResult result1, FSharpFunc`2 part2) in <path>:line 509 / at Microsoft.FSharp.Control.Trampoline.Execute(FSharpFunc`2 firstAction) in <path>:line 112 / Watching src" No runtime evidence was gathered.
- C1 Data Protection — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These personal data controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks personal data controls.
- C2 Access Controls — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These authorization controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks authorization controls.
- C3 Audit Trail — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These audit controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks audit controls.
- C4 Data Retention — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These retention controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks retention controls.
- C5 Data-Subject Rights — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These data-subject rights controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks data-subject rights controls.
- IC1 Incompleteness & stubs — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- P1 CI/CD gates — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. A CI pipeline exists and the word "test" appears, but no explicit test-runner invocation (your stack's test command, or a test job) was matched — so either the gate runs tests through a step this pass could not recognise, or "test" is incidental here (a path, "latest", a reporter). Which of the two it is cannot be settled from this dimension's evidence; the coverage dimensions report whether a suite exists at all. You can widen what we reach: name the test runner explicitly in the pipeline step (your stack's test command, or a job named for the suite) so the gate is unambiguous to a reader and to this pass.
- P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
- S1 Web-Security Posture — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These web-security controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks web-security controls.
- X1 Async correctness — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X12 Unreachable branch — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X13 Undrained process stream — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X14 Bypassable address classification — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X15 Unvalidated length from an untrusted reader — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X16 Unfloored truncation loop — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X17 Uncapped recursion over a caller-supplied document — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X18 Disposal-pattern correctness — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X19 Unrestored process-global state — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X2 Cancellation propagation — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X21 Side-effecting pattern guard — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X22 Contradicted release guard — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X24 Document value interpolated into markup unescaped — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X25 Inert configuration knob — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X26 Unsynchronised callback handoff — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X29 Per-element action decided by a fixed element — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X3 Exception handling — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X30 Support guard that admits what it rejects — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X32 Type resolved by simple name across every loaded assembly — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X4 Structured logging — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X5 Nullable reference types — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X7 Silent fallback defaults — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C#, Python, TypeScript/JavaScript, Rust, Go, Java, Kotlin, Scala, PHP, Ruby, Swift and Dart syntax only, and no C#, Python, TypeScript/JavaScript, Rust, Go, Java, Kotlin, Scala, PHP, Ruby, Swift or Dart was loaded for this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
- D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
- D8 Code Coverage: Coverage is measured by building and running the test suite inside our isolated image — the target repo is never modified, and nothing on your systems runs. So coverage exists only when the suite builds and runs within the inline time budget; one that needs external services, can't build, or exceeds the budget yields no coverage (D8 then degrades to not-measured, not a low score). Line coverage also says nothing about assertion quality.
- D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
- D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
- 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.
- 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.
- AC1 Text alternatives: Alt-text is detected structurally — the scan sees that an alternative EXISTS, not whether it meaningfully describes the image, and decorative-vs-missing is judged by attribute shape; runtime-injected images and a non-role=img decorative svg are out of scope. This is accessibility readiness, never a WCAG conformance claim.
- AC2 Forms & labels: Label association is read from static markup — a label wired up at runtime (JS-set aria-labelledby, framework-injected ids) reads as missing, a present label says nothing about whether its text is correct. A known UI-library field component (e.g. a JSX <TextField>) is now checked conservatively — flagged only when it carries NO label/aria-label/aria-labelledby/id/name — but wrapper/context-labelled libraries (Chakra/Radix FormControl+FormLabel) aren't statically visible (possible false positive) and non-JSX lowercased components are still skipped. A click handler on a plain element is now asked for a name too (it is a control the author declared), but the subtree test that answers it is deliberately generous: any DYNAMIC text expression in the subtree counts as a name, so an icon chosen by a ternary ({cond ? <IconA/> : <IconB/>}) reads as named, and a glyph component from a library the icon-import list does not know still names its parent. A clean result is "no unlabelled control found", not a labelling proof.
- AC3 Page structure: Page structure is read from the static markup tree — landmarks, headings and lang injected at runtime aren't seen, heading ORDER is checked structurally (not against the rendered visual hierarchy), and lang/title/main fire only on full documents, never partials, and the data-table check sees header-cell presence (a <th> exists), not whether each header correctly associates with its cells. Static readiness, not conformance.
- 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.
- 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
2 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was TourView.AppView at 26.
What to do
- Bring the 2 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with TourView.AppView (cyclomatic 26), App.update (cyclomatic 25). — 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 Cyclomatic Complexity from 9.1 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
D2 · Cognitive Complexity
1 method(s) exceeded the cognitive complexity threshold of 15; the worst was TourView.AppView at 26.
What to do
- Bring the 1 body over 15 down to 15 or less in Cognitive Complexity — start with TourView.AppView (cognitive 26). — Refactoring it lifts Cognitive Complexity from 9.3 to about 10.0/10.
D3 · God Classes
1 over-large unit(s) detected — types, modules or files that carry too much.
What to do
- Resolve the 1 FileTooLong finding(s) in God Classes — start with Monaco.fs. — One of this dimension's main actionable groups (1 warning-level).
D4 · Code Duplication
3 duplicated block group(s) detected. 0.7 % of the production lines (52 of 7,899) are in a reported copy.
What to do
- Resolve the 1 Duplicated block (9–12 lines × 2) finding(s) in Code Duplication — start with Monaco.fs. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Duplicated block (7 lines × 4) finding(s) in Code Duplication — start with Monaco.fs. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Duplicated block (5 lines × 2) finding(s) in Code Duplication — start with Monaco.fs. — One of this dimension's main actionable groups (1 warning-level).
D5 · Coupling
1 projects, 0 dependency cycle(s), 0 unstable depended-on project(s).
D8 · Code Coverage
No automated tests — no test code was found in this repository.
What to do
- Resolve the 1 No automated tests finding(s) in Code Coverage. — One of this dimension's main actionable groups (1 issue-level).
D12 · Dependency Hygiene
3 outdated, 0 vulnerable, 0 deprecated packages. Those are the NuGet packages; this repository's npm dependencies were read too — 67 outdated of 102 package(s) across 1 lockfile(s).
What to do
- Resolve the 2 Outdated (npm) finding(s) in Dependency Hygiene. — One of this dimension's main actionable groups (2 recommendation-level).
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D14 · License Compliance
0 of 22 packages use a banned license. ★ DEPTH: this repository's MSBuild projects declare 9 direct `PackageReference`(s), and 13 further package(s) were reached beyond them by closing the graph over nuget.org's own nuspec dependency graph — so a banned licence pulled in only by a dependency's OWN dependencies is inside this verdict. A package whose licence nuget.org could not be asked for is not graded, and version ranges are taken at their lower bound, so this is the closure as that graph states it rather than a restored consumer's exact resolution. ★ COVERAGE OF THIS VERDICT: it grades this repository's NuGet package dependencies and nothing else. The repository also declares package.json, and the licences of those dependencies were NOT read by this pass — a gap in this engine's coverage, not a statement about them. So this result says the graded closure carries no banned licence; it does NOT say this repository's licensing is clear.
D15 · Churn × Complexity Hotspots
Top hotspots: src/App/App.fs (2×26=52)
What to do
- Resolve the 1 Hotspot finding(s) in Churn × Complexity Hotspots — start with App.fs. — One of this dimension's main actionable groups (1 warning-level).
D20 · ADR Quality
No architecture decision records were found.
What to do
- Resolve the 1 No ADRs found finding(s) in ADR Quality — start with App.fsproj. — One of this dimension's main actionable groups (1 recommendation-level).
D27 · Navigability
94 % of calls cross a namespace and 9 % go through an interface, but 98 % 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)
13 finding(s): 0 critical, 9 high, 4 medium, 0 low. 9 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 3 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (3). — One of this dimension's main actionable groups (3 warning-level).
- 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 9 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 (9 issue-level, 0 of them charged here).
D30 · Dependency Vulnerabilities
2 finding(s): 0 critical, 2 high, 0 medium, 0 low.
What to do
- Resolve the 2 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
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 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 — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 1 platform declaration(s) and 8 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
AC1 · Text alternatives
AC2 · Forms & labels
AC3 · Page structure
- An iframe with no title (or an empty one) is announced only as "frame". Add a non-empty title describing its content, or an aria-label. — src/App/App.fs:611
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.
AC5 · ARIA correctness
AC6 · Visual & motion safety
AX10 · Code composition
AX3 · Project dependency cycles
AX4 · Dependency direction
GD1 · Unfinished & placeholder code
- A shipped binding's whole body still raises a "not implemented" error — generated scaffolding that was never completed. Implement it or remove the dead surface. — src/App/Editor.fs:183
What to do
- Finish or delete the bindings that still raise "not implemented", and replace placeholder text before shipping.
M1 · Documentation (README)
- The root README is 34 words, against a bar of 120. Of the three newcomer-critical sections this check looks for by heading, in the README and in the repository documents it links, it found no a build/run or getting-started section, no a testing section, no an architecture or project-map section. Sections are matched on HEADING text only, so material written under a heading this check does not recognise — or with no heading at all — is not seen and this row may understate what the document covers. — README.md:1
What to do
- Expand the README with getting-started, architecture overview and a project map.
- Add a build/run (quick start) section to the root README — the first thing a newcomer needs.
- Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
- No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
- Add a C4 context/container diagram (Structurizr, PlantUML or Mermaid) or an architecture.md overview.
M3 · Folder & project structure
P1 · CI/CD gates
What to do
- Run the test suite in CI via an explicit runner step (`dotnet test` for the toolchain this pipeline already uses) and gate merges on it.
P2 · Observability
- No logging or diagnostics emission found. This repository ships a binary its users launch rather than a service you operate, so there is no operator to page — but when a run fails on a user's machine, neither they nor you have anything to read.
What to do
- Write a diagnostic trail the user can hand back with a bug report: a log file under the platform's per-user data directory, switchable with a `--verbose`/`--debug` flag. Start with the error paths that emit nothing — a discarded error is the failure the user cannot describe and you cannot reproduce.
P3 · Security & performance tooling
- No static application security testing detected. For this repository's stack, add `semgrep --config=auto` plus gitleaks for committed secrets (F# is not a CodeQL language and has no language-specific SAST engine) as a CI step. What was searched, so you can tell an absence from a miss: the 2 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner. — REDACTED:3
- `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:21
What to do
- Add a SAST step to CI running what this repository's stack ships: `semgrep --config=auto` plus gitleaks for committed secrets (F# is not a CodeQL language and has no language-specific SAST engine) — so a security regression fails the build instead of landing.
- Enable Dependabot/Renovate or a dependency-review gate.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
What to do
- Make sure a person approves each release. The release job names an environment, but its approval rules live in the code host's settings, where we can't see them. Check that a reviewer must approve each release, or publish releases as drafts first, so a bad build can be stopped before anyone downloads it.
PF3 · Async & latency hygiene
WCAG coverage — what static analysis assessed
| Dimension | WCAG 2.2 A/AA criteria | Coverage |
|---|---|---|
| AC1 · Text alternatives | 1.1.1, 1.2.2, 1.2.5 | Partial signal |
| AC2 · Forms & labels | 1.3.1, 3.3.2, 4.1.2 | Partial signal |
| AC3 · Page structure | 1.4.4, 2.2.1, 2.4.1, 2.4.2, 3.1.1, 4.1.2 | Partial signal |
| AC5 · ARIA correctness | 4.1.2 | Partial signal |
| AC6 · Visual & motion safety | 1.4.3, 2.4.7 | Partial — literal CSS only |
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 94% | Checked 4 of 11 | Solid. |
| Architecture | 99% | Exemplary | Solid. |
| Maturity | 42% | Weak — gated by M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 24% | Critical — gated by D8, P2, P3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 70% | Checked 4 of 10 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Accessibility | 84% | Strong | Solid. |
| Performance | 100% | Exemplary | Strongest area. |
Unscored — 1 check(s) recorded observations but carry no score
- SC1 Supply-chain hygiene — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Not evidenced — 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 — 75 check(s) not relevant to this codebase
- AC4 Keyboard semantics — No interactive element found in the parsed markup — AC4 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 — Not applicable: 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.
- AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX6 Interface segregation — not assessed — interface segregation is computed over a type surface that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AX8 Test isolation — no test/production split to check
- AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXR1 Runtime accessibility — the dev server (`npm run start`) kept running but served no page within 2 minutes. Likely cause (not identified): the dev server kept running but no port it opened served a page in the time allowed. Last output: "at Microsoft.FSharp.Primitives.Basics.List.collect[T,TResult](FSharpFunc`2 f, FSharpList`1 list) in <path>:line 443 / at Fable.Transforms.FSharp2Fable.Compiler.transformFile(Compiler com) in <path>:line 2984 / at Fable.Cli.Pipeline.Js.compileFile@174.Invoke(Unit unitVar) in <path>:line 180 / at Microsoft.FSharp.Control.AsyncPrimitives.CallThenInvoke[T,TResult](AsyncActivation`1 ctxt, TResult result1, FSharpFunc`2 part2) in <path>:line 509 / at Microsoft.FSharp.Control.Trampoline.Execute(FSharpFunc`2 firstAction) in <path>:line 112 / Watching src" No runtime evidence was gathered. This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
- C1 Data Protection — Not assessed: these personal data controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks personal data controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- C2 Access Controls — Not assessed: these authorization controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks authorization controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- 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 — too few commits for a meaningful bus factor
- 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.
- D21 Naming Consistency — D21 withholds its case and prefix conventions rows: 2 candidate(s) found and not reported.
- D22 Internal API Consistency — The exposed public-API surface could not be collected — no C#/VB projects loaded.
- D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D24 Comment Value — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only; comments in this repository's .fs source were not judged.
- D25 ADR Conformance — no ADRs to check
- D26 Project Cohesion — D26 could not read how the parts of this repository's one build unit reference each other, so its cohesion was not measured. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- 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.
- D34 Knowledge Freshness — too few commits to judge knowledge freshness
- 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.
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D6 Cohesion (LCOM4) — Cohesion (LCOM4) was not measured: of the 2 type(s) found, none both holds instance state and has two or more methods whose shared use of it could be read (2 stateless), so LCOM4 is undefined for every type in this repository. Not scored — the metric does not apply here, and this is not a finding about this repository.
- D7 Architectural Integrity — no checkable ADRs and no dependency cycles — architectural integrity not assessed
- DM1 Domain Modelling — applicable but not scored (2 of 3 signals for this style — below the bar we score at): 9 value object(s); 3 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 70 current-state document(s) make no claim of a kind M4 checks. 1 claim(s) of kinds M4 does not check were not checked (command argument 1); M4 checks only links and versions and artefact counts.
- P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
- P7 Outbound HTTP resilience — not measured — the application kind could not be determined for this repo
- P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
- P9 Domain vs controller coverage — coverage not measured: this check compares the coverage of the analyzer's own test run across the domain and web layers, and that run measured none here — Test coverage (D8) says why
- PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for a BenchmarkDotNet reference in an .fsproj or .vbproj, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
- PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
- S1 Web-Security Posture — Not assessed: these web-security controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks web-security controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- X1 Async correctness — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X10 Duplicated predicate — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X12 Unreachable branch — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X13 Undrained process stream — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X14 Bypassable address classification — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X15 Unvalidated length from an untrusted reader — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X16 Unfloored truncation loop — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X17 Uncapped recursion over a caller-supplied document — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X18 Disposal-pattern correctness — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X19 Unrestored process-global state — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X2 Cancellation propagation — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X20 Mistyped argument guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X21 Side-effecting pattern guard — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X22 Contradicted release guard — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X23 Unguarded diagnostic materialisation — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X24 Document value interpolated into markup unescaped — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X25 Inert configuration knob — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X26 Unsynchronised callback handoff — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X27 Collection changed while being enumerated — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X28 Index access outside its own emptiness guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- 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 — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
Critical — 13 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- <iframe> without a title src/App/App.fs:611
- No automated tests
Serious — 17 finding(s)
- REDACTED
- REDACTED
- REDACTED
- TourView.AppView (cyclomatic 26) src/App/App.fs:380
- App.update (cyclomatic 25) src/App/App.fs:243
- Hotspot: src/App/App.fs src/App/App.fs:380
- TourView.AppView (cognitive 26) src/App/App.fs:380
- REDACTED
- FileTooLong: Libs/Monaco.fs src/App/Libs/Monaco.fs
- REDACTED
- REDACTED
- Duplicated block (9–12 lines × 2) src/App/Libs/Monaco.fs:1260
- Duplicated block (7 lines × 4) src/App/Libs/Monaco.fs:6672
- Duplicated block (5 lines × 2) src/App/Libs/Monaco.fs:7095
- Unfinished stub — raises a "not implemented" error src/App/Editor.fs:183
- No structured logging
- NuGet dependencies are not locked
Minor — 12 finding(s)
- Outdated (npm): diff
- Outdated (npm): js-tokens
- No ADRs found src/App/App.fsproj:4
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Thin README README.md:1
- No ADRs
- No architecture diagram/doc
- No SAST REDACTED:3
- No dependency-update automation src/App/App.fsproj:21
Minor — 68 finding(s)
- Outdated (npm): @babel/runtime
- Outdated (npm): @fable-org/fable-metadata
- Outdated (npm): @fable-org/fable-standalone
- Outdated (npm): @types/debug
- Outdated (npm): @types/mdast
- Outdated (npm): @types/ms
- Outdated (npm): @types/prop-types
- Outdated (npm): @types/react
- Outdated (npm): @types/scheduler
- Outdated (npm): @types/unist
- Outdated (npm): csstype
- Outdated (npm): debug
- Outdated (npm): decode-named-character-reference
- Outdated (npm): fault
- Outdated (npm): format
- Outdated (npm): hast-util-whitespace
- Outdated (npm): hastscript
- Outdated (npm): highlight.js
- Outdated (npm): inline-style-parser
- Outdated (npm): lowlight
- Outdated (npm): mdast-util-definitions
- Outdated (npm): mdast-util-from-markdown
- Outdated (npm): mdast-util-to-hast
- Outdated (npm): mdast-util-to-string
- Outdated (npm): micromark
- Outdated: Fable.Core
- Outdated: FSharp.Core
- Outdated: Thoth.Json
Appendix B — Reproduction & audit trail
| Dimension | Tool | Version | Command | Findings | Raw output |
|---|---|---|---|---|---|
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-94f38561d85f48d99d5f2e924bfb5e54/history.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-94f38561d85f48d99d5f2e924bfb5e54/tree.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-tree.json |
| D29 · Static Analysis (SAST) | semgrep | — | semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/canine-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt . | 13 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | dotnet | — | dotnet list Tour.sln package --vulnerable --include-transitive --format json | 2 | 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/** . | 0 | artifacts/raw/trivy-fs.json |