Executive summary
artempyanykh/marksman falls short of our standard for production, held back most by its Production Readiness lens, the way the code is tested, built, released and run. It scores 64 out of 100 and is rated Adequate, and all ten of its critical findings are security problems in the build pipeline and in the packages it uses.
Production Readiness, at 57, is the weakest lens and counts most in the score. The best first step is recording design decisions, worth about 6 points. Keeping a changelog would lift Production Readiness itself, worth about 3 points. Raising Production Readiness to 70 would lift the score to about 67.
Seven pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. One known security hole in a package the code depends on can be used by attackers. Pinning each tool to an exact version and updating the vulnerable packages would close both risks. Passing outside input through environment variables would fix the pipeline step that puts outside input straight into a shell command, and limiting each secret to its own step would deal with the secret exposed to more of the pipeline than needed.
The product code is 13,346 lines, about €23,000 to rebuild.
If Production Readiness rose from 57 to 70, the lowest score rated Strong, the score would rise from 64 to about 67.
Fixed since the last survey: 3 findings
- Static Analysis (SAST) · Medium: watchdog-eol-dotnet-runtime-in-workflow REDACTED
- Static Analysis (SAST) · Medium: watchdog-eol-dotnet-runtime-in-workflow REDACTED
- Platform End-of-Life · End-of-life runtime: .NET net9.0 MarkdigPatches/MarkdigPatches.csproj
Rebuild cost: about €23,000 · Estimate
| Cost to rebuild | €7,500 to €38,000, for 125 to 398 hours of work, about 0.2 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.9 at a score of 64. 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: 13,346 lines of product code |
| Comment lines | The estimate prices 13,279 lines. Comment lines count towards the size of 13,346 lines but aren't priced as work. |
| What it is not | Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one. |
Top priorities
Diagnosis: what the measurements show together
Architecture — module dependency graph
Architecture: which parts of the code depend on which
| uses → | 1 Ionide.LanguageServerProtocol.JsonRpc | 2 Ionide.LanguageServerProtocol.Logging.Types | 3 Ionide.LanguageServerProtocol.Types | 4 Marksman.Config | 5 Marksman.Doc | 6 Marksman.Index | 7 Marksman.MMap | 8 Marksman.Paths | 9 Marksman.Workspace | 10 Marksman.Misc | 11 Marksman.State | 12 Marksman.Text | 13 Marksman.Graph | 14 Marksman.Names | 15 Marksman.Toc.TableOfContentsModule | 16 Marksman.Ast | 17 Marksman.Cst | 18 Marksman.Folder | 19 Marksman.Server | 20 Marksman.Syms | 21 Marksman.CodeActions | 22 Marksman.Compl | 23 Marksman.Compl.Candidates | 24 Marksman.Conn | 25 Marksman.Cst.HeadingModule | 26 Marksman.Cst.MdLinkDefModule | 27 Marksman.Diag.WorkspaceDiagModule | 28 Marksman.Doc.DocModule | 29 Marksman.Lenses | 30 Marksman.Refactor | 31 Marksman.Refs | 32 Marksman.Server.ServerUtil | 33 Marksman.State.StateModule | 34 Marksman.Structure.StructureModule | 35 Marksman.Symbols | 36 Marksman.Compl.Completions | 37 Marksman.Conn.ConnModule | 38 Marksman.Diag | 39 Marksman.Folder.FolderModule | 40 Marksman.Refs.DestModule |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 Ionide.LanguageServerProtocol.JsonRpc | ||||||||||||||||||||||||||||||||||||||||
| 2 Ionide.LanguageServerProtocol.Logging.Types | ||||||||||||||||||||||||||||||||||||||||
| 3 Ionide.LanguageServerProtocol.Types | ||||||||||||||||||||||||||||||||||||||||
| 4 Marksman.Config | ||||||||||||||||||||||||||||||||||||||||
| 5 Marksman.Doc | ||||||||||||||||||||||||||||||||||||||||
| 6 Marksman.Index | ||||||||||||||||||||||||||||||||||||||||
| 7 Marksman.MMap | ||||||||||||||||||||||||||||||||||||||||
| 8 Marksman.Paths | ||||||||||||||||||||||||||||||||||||||||
| 9 Marksman.Workspace | ||||||||||||||||||||||||||||||||||||||||
| 10 Marksman.Misc | 2 | |||||||||||||||||||||||||||||||||||||||
| 11 Marksman.State | 2 | 2 | ||||||||||||||||||||||||||||||||||||||
| 12 Marksman.Text | 5 | |||||||||||||||||||||||||||||||||||||||
| 13 Marksman.Graph | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 14 Marksman.Names | 6 | 1 | ||||||||||||||||||||||||||||||||||||||
| 15 Marksman.Toc.TableOfContentsModule | 1 | 2 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 16 Marksman.Ast | 3 | 1 | ||||||||||||||||||||||||||||||||||||||
| 17 Marksman.Cst | 3 | 4 | ||||||||||||||||||||||||||||||||||||||
| 18 Marksman.Folder | 1 | |||||||||||||||||||||||||||||||||||||||
| 19 Marksman.Server | 1 | 38 | 5 | 1 | ||||||||||||||||||||||||||||||||||||
| 20 Marksman.Syms | 4 | 1 | ||||||||||||||||||||||||||||||||||||||
| 21 Marksman.CodeActions | 1 | 4 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 22 Marksman.Compl | 1 | 4 | 1 | 2 | 2 | 1 | ||||||||||||||||||||||||||||||||||
| 23 Marksman.Compl.Candidates | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 24 Marksman.Conn | 2 | 1 | 3 | 2 | 7 | 14 | ||||||||||||||||||||||||||||||||||
| 25 Marksman.Cst.HeadingModule | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 26 Marksman.Cst.MdLinkDefModule | 1 | 1 | 1 | 2 | ||||||||||||||||||||||||||||||||||||
| 27 Marksman.Diag.WorkspaceDiagModule | 2 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 28 Marksman.Doc.DocModule | 2 | 1 | 1 | 1 | 5 | 1 | 1 | 1 | 1 | 3 | 1 | |||||||||||||||||||||||||||||
| 29 Marksman.Lenses | 3 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 30 Marksman.Refactor | 6 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 31 Marksman.Refs | 3 | 4 | ||||||||||||||||||||||||||||||||||||||
| 32 Marksman.Server.ServerUtil | 1 | 2 | 2 | 2 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||
| 33 Marksman.State.StateModule | 1 | 2 | 1 | 1 | 3 | 1 | 2 | 1 | ||||||||||||||||||||||||||||||||
| 34 Marksman.Structure.StructureModule | 1 | 1 | 2 | 1 | ||||||||||||||||||||||||||||||||||||
| 35 Marksman.Symbols | 3 | 1 | 1 | 1 | 4 | |||||||||||||||||||||||||||||||||||
| 36 Marksman.Compl.Completions | 2 | 2 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 37 Marksman.Conn.ConnModule | 1 | 1 | 2 | 3 | 9 | |||||||||||||||||||||||||||||||||||
| 38 Marksman.Diag | 2 | 1 | 2 | 1 | 2 | 2 | ||||||||||||||||||||||||||||||||||
| 39 Marksman.Folder.FolderModule | 2 | 1 | 1 | 4 | 1 | 3 | 2 | 1 | 2 | |||||||||||||||||||||||||||||||
| 40 Marksman.Refs.DestModule | 2 | 1 | 1 | 1 | 1 | 1 |
10→3 Marksman.Misc uses Ionide.LanguageServerProtocol.Types✕
- Connections
- 2 pairs of types, where a type in Marksman.Misc uses a type in Ionide.LanguageServerProtocol.Types.
- The types involved
Marksman.Misc.Misc→Ionide.LanguageServerProtocol.Types.PositionMarksman.Misc.Misc→Ionide.LanguageServerProtocol.Types.Range
- Direction
- Marksman.Misc uses Ionide.LanguageServerProtocol.Types, so a change to Ionide.LanguageServerProtocol.Types can break Marksman.Misc, while a change to Marksman.Misc can't break Ionide.LanguageServerProtocol.Types.
- Position
- Below the diagonal: Marksman.Misc uses a module listed above it, which is the healthy direction.
11→3 Marksman.State uses Ionide.LanguageServerProtocol.Types✕
- Connections
- 2 pairs of types, where a type in Marksman.State uses a type in Ionide.LanguageServerProtocol.Types.
- The types involved
Marksman.State.ClientDescription→Ionide.LanguageServerProtocol.Types.ClientCapabilitiesMarksman.State.ClientDescription→Ionide.LanguageServerProtocol.Types.ClientInfo
- Direction
- Marksman.State uses Ionide.LanguageServerProtocol.Types, so a change to Ionide.LanguageServerProtocol.Types can break Marksman.State, while a change to Marksman.State can't break Ionide.LanguageServerProtocol.Types.
- Position
- Below the diagonal: Marksman.State uses a module listed above it, which is the healthy direction.
11→4 Marksman.State uses Marksman.Config✕
- Connections
- 2 pairs of types, where a type in Marksman.State uses a type in Marksman.Config.
- The types involved
Marksman.State.ClientDescription→Marksman.Config.TextSyncMarksman.State.InitOptions→Marksman.Config.TextSync
- Direction
- Marksman.State uses Marksman.Config, so a change to Marksman.Config can break Marksman.State, while a change to Marksman.State can't break Marksman.Config.
- Position
- Below the diagonal: Marksman.State uses a module listed above it, which is the healthy direction.
12→3 Marksman.Text uses Ionide.LanguageServerProtocol.Types✕
- Connections
- 5 pairs of types, where a type in Marksman.Text uses a type in Ionide.LanguageServerProtocol.Types.
- The types involved
Marksman.Text.LineMap→Ionide.LanguageServerProtocol.Types.PositionMarksman.Text.LineMap→Ionide.LanguageServerProtocol.Types.RangeMarksman.Text.Text→Ionide.LanguageServerProtocol.Types.PositionMarksman.Text.Text→Ionide.LanguageServerProtocol.Types.RangeMarksman.Text.Text→Ionide.LanguageServerProtocol.Types.TextDocumentContentChangeEvent
- Direction
- Marksman.Text uses Ionide.LanguageServerProtocol.Types, so a change to Ionide.LanguageServerProtocol.Types can break Marksman.Text, while a change to Marksman.Text can't break Ionide.LanguageServerProtocol.Types.
- Position
- Below the diagonal: Marksman.Text uses a module listed above it, which is the healthy direction.
13→7 Marksman.Graph uses Marksman.MMap✕
- Connections
- 1 pair of types, where a type in Marksman.Graph uses a type in Marksman.MMap.
- The types involved
Marksman.Graph.Graph`1→Marksman.MMap.MMap`2
- Direction
- Marksman.Graph uses Marksman.MMap, so a change to Marksman.MMap can break Marksman.Graph, while a change to Marksman.Graph can't break Marksman.MMap.
- Position
- Below the diagonal: Marksman.Graph uses a module listed above it, which is the healthy direction.
13→10 Marksman.Graph uses Marksman.Misc✕
- Connections
- 1 pair of types, where a type in Marksman.Graph uses a type in Marksman.Misc.
- The types involved
Marksman.Graph.GraphDifference`1→Marksman.Misc.Difference`1
- Direction
- Marksman.Graph uses Marksman.Misc, so a change to Marksman.Misc can break Marksman.Graph, while a change to Marksman.Graph can't break Marksman.Misc.
- Position
- Below the diagonal: Marksman.Graph uses a module listed above it, which is the healthy direction.
14→8 Marksman.Names uses Marksman.Paths✕
- Connections
- 6 pairs of types, where a type in Marksman.Names uses a type in Marksman.Paths.
- The types involved
Marksman.Names.DocId→Marksman.Paths.RelPathMarksman.Names.DocId→Marksman.Paths.RootedRelPathMarksman.Names.DocId→Marksman.Paths.UriWith`1Marksman.Names.DocumentAlias→Marksman.Paths.CanonDocPathMarksman.Names.InternPath→Marksman.Paths.RelPathMarksman.Names.InternPath→Marksman.Paths.RootedRelPath
- Direction
- Marksman.Names uses Marksman.Paths, so a change to Marksman.Paths can break Marksman.Names, while a change to Marksman.Names can't break Marksman.Paths.
- Position
- Below the diagonal: Marksman.Names uses a module listed above it, which is the healthy direction.
14→10 Marksman.Names uses Marksman.Misc✕
- Connections
- 1 pair of types, where a type in Marksman.Names uses a type in Marksman.Misc.
- The types involved
Marksman.Names.DocumentAlias→Marksman.Misc.Slug
- Direction
- Marksman.Names uses Marksman.Misc, so a change to Marksman.Misc can break Marksman.Names, while a change to Marksman.Names can't break Marksman.Misc.
- Position
- Below the diagonal: Marksman.Names uses a module listed above it, which is the healthy direction.
15→2 Marksman.Toc.TableOfContentsModule uses Ionide.LanguageServerProtocol.Logging.Types✕
- Connections
- 1 pair of types, where a type in Marksman.Toc.TableOfContentsModule uses a type in Ionide.LanguageServerProtocol.Logging.Types.
- The types involved
Marksman.Toc.TableOfContentsModule.TableOfContentsModule→Ionide.LanguageServerProtocol.Logging.Types.ILog
- Direction
- Marksman.Toc.TableOfContentsModule uses Ionide.LanguageServerProtocol.Logging.Types, so a change to Ionide.LanguageServerProtocol.Logging.Types can break Marksman.Toc.TableOfContentsModule, while a change to Marksman.Toc.TableOfContentsModule can't break Ionide.LanguageServerProtocol.Logging.Types.
- Position
- Below the diagonal: Marksman.Toc.TableOfContentsModule uses a module listed above it, which is the healthy direction.
15→3 Marksman.Toc.TableOfContentsModule uses Ionide.LanguageServerProtocol.Types✕
- Connections
- 2 pairs of types, where a type in Marksman.Toc.TableOfContentsModule uses a type in Ionide.LanguageServerProtocol.Types.
- The types involved
Marksman.Toc.TableOfContentsModule.State→Ionide.LanguageServerProtocol.Types.RangeMarksman.Toc.TableOfContentsModule.TableOfContentsModule→Ionide.LanguageServerProtocol.Types.Range
- Direction
- Marksman.Toc.TableOfContentsModule uses Ionide.LanguageServerProtocol.Types, so a change to Ionide.LanguageServerProtocol.Types can break Marksman.Toc.TableOfContentsModule, while a change to Marksman.Toc.TableOfContentsModule can't break Ionide.LanguageServerProtocol.Types.
- Position
- Below the diagonal: Marksman.Toc.TableOfContentsModule uses a module listed above it, which is the healthy direction.
15→5 Marksman.Toc.TableOfContentsModule uses Marksman.Doc✕
- Connections
- 1 pair of types, where a type in Marksman.Toc.TableOfContentsModule uses a type in Marksman.Doc.
- The types involved
Marksman.Toc.TableOfContentsModule.TableOfContentsModule→Marksman.Doc.Doc
- Direction
- Marksman.Toc.TableOfContentsModule uses Marksman.Doc, so a change to Marksman.Doc can break Marksman.Toc.TableOfContentsModule, while a change to Marksman.Toc.TableOfContentsModule can't break Marksman.Doc.
- Position
- Below the diagonal: Marksman.Toc.TableOfContentsModule uses a module listed above it, which is the healthy direction.
15→6 Marksman.Toc.TableOfContentsModule uses Marksman.Index✕
- Connections
- 1 pair of types, where a type in Marksman.Toc.TableOfContentsModule uses a type in Marksman.Index.
- The types involved
Marksman.Toc.TableOfContentsModule.TableOfContentsModule→Marksman.Index.Index
- Direction
- Marksman.Toc.TableOfContentsModule uses Marksman.Index, so a change to Marksman.Index can break Marksman.Toc.TableOfContentsModule, while a change to Marksman.Toc.TableOfContentsModule can't break Marksman.Index.
- Position
- Below the diagonal: Marksman.Toc.TableOfContentsModule uses a module listed above it, which is the healthy direction.
15→12 Marksman.Toc.TableOfContentsModule uses Marksman.Text✕
- Connections
- 1 pair of types, where a type in Marksman.Toc.TableOfContentsModule uses a type in Marksman.Text.
- The types involved
Marksman.Toc.TableOfContentsModule.TableOfContentsModule→Marksman.Text.Text
- Direction
- Marksman.Toc.TableOfContentsModule uses Marksman.Text, so a change to Marksman.Text can break Marksman.Toc.TableOfContentsModule, while a change to Marksman.Toc.TableOfContentsModule can't break Marksman.Text.
- Position
- Below the diagonal: Marksman.Toc.TableOfContentsModule uses a module listed above it, which is the healthy direction.
16→10 Marksman.Ast uses Marksman.Misc✕
- Connections
- 3 pairs of types, where a type in Marksman.Ast uses a type in Marksman.Misc.
- The types involved
Marksman.Ast.Heading→Marksman.Misc.SlugMarksman.Ast.MdLinkDef→Marksman.Misc.LinkLabelMarksman.Ast.MdRef→Marksman.Misc.LinkLabel
- Direction
- Marksman.Ast uses Marksman.Misc, so a change to Marksman.Misc can break Marksman.Ast, while a change to Marksman.Ast can't break Marksman.Misc.
- Position
- Below the diagonal: Marksman.Ast uses a module listed above it, which is the healthy direction.
16→14 Marksman.Ast uses Marksman.Names✕
- Connections
- 1 pair of types, where a type in Marksman.Ast uses a type in Marksman.Names.
- The types involved
Marksman.Ast.MdLinkDef→Marksman.Names.UrlEncoded
- Direction
- Marksman.Ast uses Marksman.Names, so a change to Marksman.Names can break Marksman.Ast, while a change to Marksman.Ast can't break Marksman.Names.
- Position
- Below the diagonal: Marksman.Ast uses a module listed above it, which is the healthy direction.
17→3 Marksman.Cst uses Ionide.LanguageServerProtocol.Types✕
- Connections
- 3 pairs of types, where a type in Marksman.Cst uses a type in Ionide.LanguageServerProtocol.Types.
- The types involved
Marksman.Cst.Element→Ionide.LanguageServerProtocol.Types.RangeMarksman.Cst.Heading→Ionide.LanguageServerProtocol.Types.RangeMarksman.Cst.Node`1→Ionide.LanguageServerProtocol.Types.Range
- Direction
- Marksman.Cst uses Ionide.LanguageServerProtocol.Types, so a change to Ionide.LanguageServerProtocol.Types can break Marksman.Cst, while a change to Marksman.Cst can't break Ionide.LanguageServerProtocol.Types.
- Position
- Below the diagonal: Marksman.Cst uses a module listed above it, which is the healthy direction.
17→14 Marksman.Cst uses Marksman.Names✕
- Connections
- 4 pairs of types, where a type in Marksman.Cst uses a type in Marksman.Names.
- The types involved
Marksman.Cst.MdLink→Marksman.Names.UrlEncodedMarksman.Cst.MdLinkDef→Marksman.Names.UrlEncodedMarksman.Cst.WikiDest→Marksman.Names.InternPathMarksman.Cst.WikiLink→Marksman.Names.WikiEncoded
- Direction
- Marksman.Cst uses Marksman.Names, so a change to Marksman.Names can break Marksman.Cst, while a change to Marksman.Cst can't break Marksman.Names.
- Position
- Below the diagonal: Marksman.Cst uses a module listed above it, which is the healthy direction.
18→14 Marksman.Folder uses Marksman.Names✕
- Connections
- 1 pair of types, where a type in Marksman.Folder uses a type in Marksman.Names.
- The types involved
Marksman.Folder.DocumentDifference→Marksman.Names.DocId
- Direction
- Marksman.Folder uses Marksman.Names, so a change to Marksman.Names can break Marksman.Folder, while a change to Marksman.Folder can't break Marksman.Names.
- Position
- Below the diagonal: Marksman.Folder uses a module listed above it, which is the healthy direction.
19→1 Marksman.Server uses Ionide.LanguageServerProtocol.JsonRpc✕
- Connections
- 1 pair of types, where a type in Marksman.Server uses a type in Ionide.LanguageServerProtocol.JsonRpc.
- The types involved
Marksman.Server.MarksmanServer→Ionide.LanguageServerProtocol.JsonRpc.Error
- Direction
- Marksman.Server uses Ionide.LanguageServerProtocol.JsonRpc, so a change to Ionide.LanguageServerProtocol.JsonRpc can break Marksman.Server, while a change to Marksman.Server can't break Ionide.LanguageServerProtocol.JsonRpc.
- Position
- Below the diagonal: Marksman.Server uses a module listed above it, which is the healthy direction.
19→3 Marksman.Server uses Ionide.LanguageServerProtocol.Types✕
- Connections
- 38 pairs of types, where a type in Marksman.Server uses a type in Ionide.LanguageServerProtocol.Types. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
Marksman.Server.MarksmanClient→Ionide.LanguageServerProtocol.Types.PublishDiagnosticsParamsMarksman.Server.MarksmanServer→Ionide.LanguageServerProtocol.Types.CodeActionMarksman.Server.MarksmanServer→Ionide.LanguageServerProtocol.Types.CodeActionParamsMarksman.Server.MarksmanServer→Ionide.LanguageServerProtocol.Types.CodeLensMarksman.Server.MarksmanServer→Ionide.LanguageServerProtocol.Types.CodeLensParamsMarksman.Server.MarksmanServer→Ionide.LanguageServerProtocol.Types.CommandMarksman.Server.MarksmanServer→Ionide.LanguageServerProtocol.Types.CompletionListMarksman.Server.MarksmanServer→Ionide.LanguageServerProtocol.Types.CompletionParamsMarksman.Server.MarksmanServer→Ionide.LanguageServerProtocol.Types.CreateFilesParamsMarksman.Server.MarksmanServer→Ionide.LanguageServerProtocol.Types.DeleteFilesParamsMarksman.Server.MarksmanServer→Ionide.LanguageServerProtocol.Types.DidChangeTextDocumentParamsMarksman.Server.MarksmanServer→Ionide.LanguageServerProtocol.Types.DidChangeWorkspaceFoldersParamsMarksman.Server.MarksmanServer→Ionide.LanguageServerProtocol.Types.DidCloseTextDocumentParamsMarksman.Server.MarksmanServer→Ionide.LanguageServerProtocol.Types.DidOpenTextDocumentParamsMarksman.Server.MarksmanServer→Ionide.LanguageServerProtocol.Types.DocumentSymbolMarksman.Server.MarksmanServer→Ionide.LanguageServerProtocol.Types.DocumentSymbolParamsMarksman.Server.MarksmanServer→Ionide.LanguageServerProtocol.Types.ExecuteCommandParamsMarksman.Server.MarksmanServer→Ionide.LanguageServerProtocol.Types.GotoResultMarksman.Server.MarksmanServer→Ionide.LanguageServerProtocol.Types.HoverMarksman.Server.MarksmanServer→Ionide.LanguageServerProtocol.Types.InitializeParamsMarksman.Server.MarksmanServer→Ionide.LanguageServerProtocol.Types.InitializeResultMarksman.Server.MarksmanServer→Ionide.LanguageServerProtocol.Types.InitializedParamsMarksman.Server.MarksmanServer→Ionide.LanguageServerProtocol.Types.LocationMarksman.Server.MarksmanServer→Ionide.LanguageServerProtocol.Types.PrepareRenameParamsMarksman.Server.MarksmanServer→Ionide.LanguageServerProtocol.Types.PrepareRenameResult
- Direction
- Marksman.Server uses Ionide.LanguageServerProtocol.Types, so a change to Ionide.LanguageServerProtocol.Types can break Marksman.Server, while a change to Marksman.Server can't break Ionide.LanguageServerProtocol.Types.
- Position
- Below the diagonal: Marksman.Server uses a module listed above it, which is the healthy direction.
19→11 Marksman.Server uses Marksman.State✕
- Connections
- 5 pairs of types, where a type in Marksman.Server uses a type in Marksman.State.
- The types involved
Marksman.Server.DiagnosticsManager→Marksman.State.StateMarksman.Server.Mutation`1→Marksman.State.StateMarksman.Server.Server→Marksman.State.StateMarksman.Server.StateManager→Marksman.State.StateMarksman.Server.StateMessage→Marksman.State.State
- Direction
- Marksman.Server uses Marksman.State, so a change to Marksman.State can break Marksman.Server, while a change to Marksman.Server can't break Marksman.State.
- Position
- Below the diagonal: Marksman.Server uses a module listed above it, which is the healthy direction.
19→14 Marksman.Server uses Marksman.Names✕
- Connections
- 1 pair of types, where a type in Marksman.Server uses a type in Marksman.Names.
- The types involved
Marksman.Server.Server→Marksman.Names.DocId
- Direction
- Marksman.Server uses Marksman.Names, so a change to Marksman.Names can break Marksman.Server, while a change to Marksman.Server can't break Marksman.Names.
- Position
- Below the diagonal: Marksman.Server uses a module listed above it, which is the healthy direction.
20→10 Marksman.Syms uses Marksman.Misc✕
- Connections
- 4 pairs of types, where a type in Marksman.Syms uses a type in Marksman.Misc.
- The types involved
Marksman.Syms.CrossRef→Marksman.Misc.SlugMarksman.Syms.Def→Marksman.Misc.LinkLabelMarksman.Syms.IntraRef→Marksman.Misc.LinkLabelMarksman.Syms.IntraRef→Marksman.Misc.Slug
- Direction
- Marksman.Syms uses Marksman.Misc, so a change to Marksman.Misc can break Marksman.Syms, while a change to Marksman.Syms can't break Marksman.Misc.
- Position
- Below the diagonal: Marksman.Syms uses a module listed above it, which is the healthy direction.
20→14 Marksman.Syms uses Marksman.Names✕
- Connections
- 1 pair of types, where a type in Marksman.Syms uses a type in Marksman.Names.
- The types involved
Marksman.Syms.Scope→Marksman.Names.DocId
- Direction
- Marksman.Syms uses Marksman.Names, so a change to Marksman.Names can break Marksman.Syms, while a change to Marksman.Syms can't break Marksman.Names.
- Position
- Below the diagonal: Marksman.Syms uses a module listed above it, which is the healthy direction.
21→2 Marksman.CodeActions uses Ionide.LanguageServerProtocol.Logging.Types✕
- Connections
- 1 pair of types, where a type in Marksman.CodeActions uses a type in Ionide.LanguageServerProtocol.Logging.Types.
- The types involved
Marksman.CodeActions.CodeActions→Ionide.LanguageServerProtocol.Logging.Types.ILog
- Direction
- Marksman.CodeActions uses Ionide.LanguageServerProtocol.Logging.Types, so a change to Ionide.LanguageServerProtocol.Logging.Types can break Marksman.CodeActions, while a change to Marksman.CodeActions can't break Ionide.LanguageServerProtocol.Logging.Types.
- Position
- Below the diagonal: Marksman.CodeActions uses a module listed above it, which is the healthy direction.
21→3 Marksman.CodeActions uses Ionide.LanguageServerProtocol.Types✕
- Connections
- 4 pairs of types, where a type in Marksman.CodeActions uses a type in Ionide.LanguageServerProtocol.Types.
- The types involved
Marksman.CodeActions.CodeActions→Ionide.LanguageServerProtocol.Types.CodeActionContextMarksman.CodeActions.CodeActions→Ionide.LanguageServerProtocol.Types.RangeMarksman.CodeActions.CodeActions→Ionide.LanguageServerProtocol.Types.WorkspaceEditMarksman.CodeActions.DocumentAction→Ionide.LanguageServerProtocol.Types.Range
- Direction
- Marksman.CodeActions uses Ionide.LanguageServerProtocol.Types, so a change to Ionide.LanguageServerProtocol.Types can break Marksman.CodeActions, while a change to Marksman.CodeActions can't break Ionide.LanguageServerProtocol.Types.
- Position
- Below the diagonal: Marksman.CodeActions uses a module listed above it, which is the healthy direction.
21→4 Marksman.CodeActions uses Marksman.Config✕
- Connections
- 1 pair of types, where a type in Marksman.CodeActions uses a type in Marksman.Config.
- The types involved
Marksman.CodeActions.CodeActions→Marksman.Config.Config
- Direction
- Marksman.CodeActions uses Marksman.Config, so a change to Marksman.Config can break Marksman.CodeActions, while a change to Marksman.CodeActions can't break Marksman.Config.
- Position
- Below the diagonal: Marksman.CodeActions uses a module listed above it, which is the healthy direction.
21→5 Marksman.CodeActions uses Marksman.Doc✕
- Connections
- 1 pair of types, where a type in Marksman.CodeActions uses a type in Marksman.Doc.
- The types involved
Marksman.CodeActions.CodeActions→Marksman.Doc.Doc
- Direction
- Marksman.CodeActions uses Marksman.Doc, so a change to Marksman.Doc can break Marksman.CodeActions, while a change to Marksman.CodeActions can't break Marksman.Doc.
- Position
- Below the diagonal: Marksman.CodeActions uses a module listed above it, which is the healthy direction.
21→18 Marksman.CodeActions uses Marksman.Folder✕
- Connections
- 1 pair of types, where a type in Marksman.CodeActions uses a type in Marksman.Folder.
- The types involved
Marksman.CodeActions.CodeActions→Marksman.Folder.Folder
- Direction
- Marksman.CodeActions uses Marksman.Folder, so a change to Marksman.Folder can break Marksman.CodeActions, while a change to Marksman.CodeActions can't break Marksman.Folder.
- Position
- Below the diagonal: Marksman.CodeActions uses a module listed above it, which is the healthy direction.
22→2 Marksman.Compl uses Ionide.LanguageServerProtocol.Logging.Types✕
- Connections
- 1 pair of types, where a type in Marksman.Compl uses a type in Ionide.LanguageServerProtocol.Logging.Types.
- The types involved
Marksman.Compl.Compl→Ionide.LanguageServerProtocol.Logging.Types.ILog
- Direction
- Marksman.Compl uses Ionide.LanguageServerProtocol.Logging.Types, so a change to Ionide.LanguageServerProtocol.Logging.Types can break Marksman.Compl, while a change to Marksman.Compl can't break Ionide.LanguageServerProtocol.Logging.Types.
- Position
- Below the diagonal: Marksman.Compl uses a module listed above it, which is the healthy direction.
22→3 Marksman.Compl uses Ionide.LanguageServerProtocol.Types✕
- Connections
- 4 pairs of types, where a type in Marksman.Compl uses a type in Ionide.LanguageServerProtocol.Types.
- The types involved
Marksman.Compl.Compl→Ionide.LanguageServerProtocol.Types.CompletionItemMarksman.Compl.Compl→Ionide.LanguageServerProtocol.Types.PositionMarksman.Compl.PartialElement→Ionide.LanguageServerProtocol.Types.PositionMarksman.Compl.PartialElement→Ionide.LanguageServerProtocol.Types.Range
- Direction
- Marksman.Compl uses Ionide.LanguageServerProtocol.Types, so a change to Ionide.LanguageServerProtocol.Types can break Marksman.Compl, while a change to Marksman.Compl can't break Ionide.LanguageServerProtocol.Types.
- Position
- Below the diagonal: Marksman.Compl uses a module listed above it, which is the healthy direction.
22→5 Marksman.Compl uses Marksman.Doc✕
- Connections
- 1 pair of types, where a type in Marksman.Compl uses a type in Marksman.Doc.
- The types involved
Marksman.Compl.Compl→Marksman.Doc.Doc
- Direction
- Marksman.Compl uses Marksman.Doc, so a change to Marksman.Doc can break Marksman.Compl, while a change to Marksman.Compl can't break Marksman.Doc.
- Position
- Below the diagonal: Marksman.Compl uses a module listed above it, which is the healthy direction.
22→14 Marksman.Compl uses Marksman.Names✕
- Connections
- 2 pairs of types, where a type in Marksman.Compl uses a type in Marksman.Names.
- The types involved
Marksman.Compl.PartialElement→Marksman.Names.UrlEncodedMarksman.Compl.PartialElement→Marksman.Names.WikiEncoded
- Direction
- Marksman.Compl uses Marksman.Names, so a change to Marksman.Names can break Marksman.Compl, while a change to Marksman.Compl can't break Marksman.Names.
- Position
- Below the diagonal: Marksman.Compl uses a module listed above it, which is the healthy direction.
22→17 Marksman.Compl uses Marksman.Cst✕
- Connections
- 2 pairs of types, where a type in Marksman.Compl uses a type in Marksman.Cst.
- The types involved
Marksman.Compl.Completable→Marksman.Cst.ElementMarksman.Compl.PartialElement→Marksman.Cst.Node`1
- Direction
- Marksman.Compl uses Marksman.Cst, so a change to Marksman.Cst can break Marksman.Compl, while a change to Marksman.Compl can't break Marksman.Cst.
- Position
- Below the diagonal: Marksman.Compl uses a module listed above it, which is the healthy direction.
22→18 Marksman.Compl uses Marksman.Folder✕
- Connections
- 1 pair of types, where a type in Marksman.Compl uses a type in Marksman.Folder.
- The types involved
Marksman.Compl.Compl→Marksman.Folder.Folder
- Direction
- Marksman.Compl uses Marksman.Folder, so a change to Marksman.Folder can break Marksman.Compl, while a change to Marksman.Compl can't break Marksman.Folder.
- Position
- Below the diagonal: Marksman.Compl uses a module listed above it, which is the healthy direction.
23→5 Marksman.Compl.Candidates uses Marksman.Doc✕
- Connections
- 1 pair of types, where a type in Marksman.Compl.Candidates uses a type in Marksman.Doc.
- The types involved
Marksman.Compl.Candidates.Candidates→Marksman.Doc.Doc
- Direction
- Marksman.Compl.Candidates uses Marksman.Doc, so a change to Marksman.Doc can break Marksman.Compl.Candidates, while a change to Marksman.Compl.Candidates can't break Marksman.Doc.
- Position
- Below the diagonal: Marksman.Compl.Candidates uses a module listed above it, which is the healthy direction.
23→14 Marksman.Compl.Candidates uses Marksman.Names✕
- Connections
- 1 pair of types, where a type in Marksman.Compl.Candidates uses a type in Marksman.Names.
- The types involved
Marksman.Compl.Candidates.Candidates→Marksman.Names.InternName
- Direction
- Marksman.Compl.Candidates uses Marksman.Names, so a change to Marksman.Names can break Marksman.Compl.Candidates, while a change to Marksman.Compl.Candidates can't break Marksman.Names.
- Position
- Below the diagonal: Marksman.Compl.Candidates uses a module listed above it, which is the healthy direction.
23→17 Marksman.Compl.Candidates uses Marksman.Cst✕
- Connections
- 1 pair of types, where a type in Marksman.Compl.Candidates uses a type in Marksman.Cst.
- The types involved
Marksman.Compl.Candidates.Candidates→Marksman.Cst.MdLinkDef
- Direction
- Marksman.Compl.Candidates uses Marksman.Cst, so a change to Marksman.Cst can break Marksman.Compl.Candidates, while a change to Marksman.Compl.Candidates can't break Marksman.Cst.
- Position
- Below the diagonal: Marksman.Compl.Candidates uses a module listed above it, which is the healthy direction.
23→18 Marksman.Compl.Candidates uses Marksman.Folder✕
- Connections
- 1 pair of types, where a type in Marksman.Compl.Candidates uses a type in Marksman.Folder.
- The types involved
Marksman.Compl.Candidates.Candidates→Marksman.Folder.Folder
- Direction
- Marksman.Compl.Candidates uses Marksman.Folder, so a change to Marksman.Folder can break Marksman.Compl.Candidates, while a change to Marksman.Compl.Candidates can't break Marksman.Folder.
- Position
- Below the diagonal: Marksman.Compl.Candidates uses a module listed above it, which is the healthy direction.
24→7 Marksman.Conn uses Marksman.MMap✕
- Connections
- 2 pairs of types, where a type in Marksman.Conn uses a type in Marksman.MMap.
- The types involved
Marksman.Conn.Conn→Marksman.MMap.MMap`2Marksman.Conn.ConnDifference→Marksman.MMap.MMapDifference`2
- Direction
- Marksman.Conn uses Marksman.MMap, so a change to Marksman.MMap can break Marksman.Conn, while a change to Marksman.Conn can't break Marksman.MMap.
- Position
- Below the diagonal: Marksman.Conn uses a module listed above it, which is the healthy direction.
24→8 Marksman.Conn uses Marksman.Paths✕
- Connections
- 1 pair of types, where a type in Marksman.Conn uses a type in Marksman.Paths.
- The types involved
Marksman.Conn.DocumentInput→Marksman.Paths.RelPath
- Direction
- Marksman.Conn uses Marksman.Paths, so a change to Marksman.Paths can break Marksman.Conn, while a change to Marksman.Conn can't break Marksman.Paths.
- Position
- Below the diagonal: Marksman.Conn uses a module listed above it, which is the healthy direction.
24→10 Marksman.Conn uses Marksman.Misc✕
- Connections
- 3 pairs of types, where a type in Marksman.Conn uses a type in Marksman.Misc.
- The types involved
Marksman.Conn.ConnectionChange→Marksman.Misc.Difference`1Marksman.Conn.DefinitionSelector→Marksman.Misc.LinkLabelMarksman.Conn.DocumentInput→Marksman.Misc.Slug
- Direction
- Marksman.Conn uses Marksman.Misc, so a change to Marksman.Misc can break Marksman.Conn, while a change to Marksman.Conn can't break Marksman.Misc.
- Position
- Below the diagonal: Marksman.Conn uses a module listed above it, which is the healthy direction.
24→13 Marksman.Conn uses Marksman.Graph✕
- Connections
- 2 pairs of types, where a type in Marksman.Conn uses a type in Marksman.Graph.
- The types involved
Marksman.Conn.Conn→Marksman.Graph.Graph`1Marksman.Conn.ConnDifference→Marksman.Graph.GraphDifference`1
- Direction
- Marksman.Conn uses Marksman.Graph, so a change to Marksman.Graph can break Marksman.Conn, while a change to Marksman.Conn can't break Marksman.Graph.
- Position
- Below the diagonal: Marksman.Conn uses a module listed above it, which is the healthy direction.
24→14 Marksman.Conn uses Marksman.Names✕
- Connections
- 7 pairs of types, where a type in Marksman.Conn uses a type in Marksman.Names.
- The types involved
Marksman.Conn.CandidateDocumentResolution→Marksman.Names.DocIdMarksman.Conn.CandidateDocumentResolution→Marksman.Names.DocumentAliasMarksman.Conn.ConnectionChange→Marksman.Names.DocumentAliasMarksman.Conn.ConnectionComputation→Marksman.Names.InternNameMarksman.Conn.ConnectionDependency→Marksman.Names.DocumentAliasMarksman.Conn.ConnectionValue→Marksman.Names.DocIdMarksman.Conn.DocumentInput→Marksman.Names.DocId
- Direction
- Marksman.Conn uses Marksman.Names, so a change to Marksman.Names can break Marksman.Conn, while a change to Marksman.Conn can't break Marksman.Names.
- Position
- Below the diagonal: Marksman.Conn uses a module listed above it, which is the healthy direction.
24→20 Marksman.Conn uses Marksman.Syms✕
- Connections
- 14 pairs of types, where a type in Marksman.Conn uses a type in Marksman.Syms.
- The types involved
Marksman.Conn.Conn→Marksman.Syms.ScopeMarksman.Conn.Conn→Marksman.Syms.SymMarksman.Conn.ConnDifference→Marksman.Syms.DefMarksman.Conn.ConnDifference→Marksman.Syms.RefMarksman.Conn.ConnDifference→Marksman.Syms.ScopeMarksman.Conn.ConnDifference→Marksman.Syms.TagMarksman.Conn.ConnectionComputation→Marksman.Syms.RefMarksman.Conn.ConnectionComputation→Marksman.Syms.ScopeMarksman.Conn.ConnectionValue→Marksman.Syms.DefMarksman.Conn.DefinitionSelector→Marksman.Syms.ScopeMarksman.Conn.DocumentInput→Marksman.Syms.SymMarksman.Conn.Unresolved→Marksman.Syms.RefMarksman.Conn.Unresolved→Marksman.Syms.ScopeMarksman.Conn.UnresolvedScope→Marksman.Syms.Scope
- Direction
- Marksman.Conn uses Marksman.Syms, so a change to Marksman.Syms can break Marksman.Conn, while a change to Marksman.Conn can't break Marksman.Syms.
- Position
- Below the diagonal: Marksman.Conn uses a module listed above it, which is the healthy direction.
25→3 Marksman.Cst.HeadingModule uses Ionide.LanguageServerProtocol.Types✕
- Connections
- 1 pair of types, where a type in Marksman.Cst.HeadingModule uses a type in Ionide.LanguageServerProtocol.Types.
- The types involved
Marksman.Cst.HeadingModule.HeadingModule→Ionide.LanguageServerProtocol.Types.Range
- Direction
- Marksman.Cst.HeadingModule uses Ionide.LanguageServerProtocol.Types, so a change to Ionide.LanguageServerProtocol.Types can break Marksman.Cst.HeadingModule, while a change to Marksman.Cst.HeadingModule can't break Ionide.LanguageServerProtocol.Types.
- Position
- Below the diagonal: Marksman.Cst.HeadingModule uses a module listed above it, which is the healthy direction.
25→10 Marksman.Cst.HeadingModule uses Marksman.Misc✕
- Connections
- 1 pair of types, where a type in Marksman.Cst.HeadingModule uses a type in Marksman.Misc.
- The types involved
Marksman.Cst.HeadingModule.HeadingModule→Marksman.Misc.Slug
- Direction
- Marksman.Cst.HeadingModule uses Marksman.Misc, so a change to Marksman.Misc can break Marksman.Cst.HeadingModule, while a change to Marksman.Cst.HeadingModule can't break Marksman.Misc.
- Position
- Below the diagonal: Marksman.Cst.HeadingModule uses a module listed above it, which is the healthy direction.
25→16 Marksman.Cst.HeadingModule uses Marksman.Ast✕
- Connections
- 1 pair of types, where a type in Marksman.Cst.HeadingModule uses a type in Marksman.Ast.
- The types involved
Marksman.Cst.HeadingModule.HeadingModule→Marksman.Ast.Heading
- Direction
- Marksman.Cst.HeadingModule uses Marksman.Ast, so a change to Marksman.Ast can break Marksman.Cst.HeadingModule, while a change to Marksman.Cst.HeadingModule can't break Marksman.Ast.
- Position
- Below the diagonal: Marksman.Cst.HeadingModule uses a module listed above it, which is the healthy direction.
25→17 Marksman.Cst.HeadingModule uses Marksman.Cst✕
- Connections
- 1 pair of types, where a type in Marksman.Cst.HeadingModule uses a type in Marksman.Cst.
- The types involved
Marksman.Cst.HeadingModule.HeadingModule→Marksman.Cst.Heading
- Direction
- Marksman.Cst.HeadingModule uses Marksman.Cst, so a change to Marksman.Cst can break Marksman.Cst.HeadingModule, while a change to Marksman.Cst.HeadingModule can't break Marksman.Cst.
- Position
- Below the diagonal: Marksman.Cst.HeadingModule uses a module listed above it, which is the healthy direction.
26→10 Marksman.Cst.MdLinkDefModule uses Marksman.Misc✕
- Connections
- 1 pair of types, where a type in Marksman.Cst.MdLinkDefModule uses a type in Marksman.Misc.
- The types involved
Marksman.Cst.MdLinkDefModule.MdLinkDefModule→Marksman.Misc.LinkLabel
- Direction
- Marksman.Cst.MdLinkDefModule uses Marksman.Misc, so a change to Marksman.Misc can break Marksman.Cst.MdLinkDefModule, while a change to Marksman.Cst.MdLinkDefModule can't break Marksman.Misc.
- Position
- Below the diagonal: Marksman.Cst.MdLinkDefModule uses a module listed above it, which is the healthy direction.
26→14 Marksman.Cst.MdLinkDefModule uses Marksman.Names✕
- Connections
- 1 pair of types, where a type in Marksman.Cst.MdLinkDefModule uses a type in Marksman.Names.
- The types involved
Marksman.Cst.MdLinkDefModule.MdLinkDefModule→Marksman.Names.UrlEncoded
- Direction
- Marksman.Cst.MdLinkDefModule uses Marksman.Names, so a change to Marksman.Names can break Marksman.Cst.MdLinkDefModule, while a change to Marksman.Cst.MdLinkDefModule can't break Marksman.Names.
- Position
- Below the diagonal: Marksman.Cst.MdLinkDefModule uses a module listed above it, which is the healthy direction.
26→16 Marksman.Cst.MdLinkDefModule uses Marksman.Ast✕
- Connections
- 1 pair of types, where a type in Marksman.Cst.MdLinkDefModule uses a type in Marksman.Ast.
- The types involved
Marksman.Cst.MdLinkDefModule.MdLinkDefModule→Marksman.Ast.MdLinkDef
- Direction
- Marksman.Cst.MdLinkDefModule uses Marksman.Ast, so a change to Marksman.Ast can break Marksman.Cst.MdLinkDefModule, while a change to Marksman.Cst.MdLinkDefModule can't break Marksman.Ast.
- Position
- Below the diagonal: Marksman.Cst.MdLinkDefModule uses a module listed above it, which is the healthy direction.
26→17 Marksman.Cst.MdLinkDefModule uses Marksman.Cst✕
- Connections
- 2 pairs of types, where a type in Marksman.Cst.MdLinkDefModule uses a type in Marksman.Cst.
- The types involved
Marksman.Cst.MdLinkDefModule.MdLinkDefModule→Marksman.Cst.MdLinkDefMarksman.Cst.MdLinkDefModule.MdLinkDefModule→Marksman.Cst.Node`1
- Direction
- Marksman.Cst.MdLinkDefModule uses Marksman.Cst, so a change to Marksman.Cst can break Marksman.Cst.MdLinkDefModule, while a change to Marksman.Cst.MdLinkDefModule can't break Marksman.Cst.
- Position
- Below the diagonal: Marksman.Cst.MdLinkDefModule uses a module listed above it, which is the healthy direction.
27→8 Marksman.Diag.WorkspaceDiagModule uses Marksman.Paths✕
- Connections
- 2 pairs of types, where a type in Marksman.Diag.WorkspaceDiagModule uses a type in Marksman.Paths.
- The types involved
Marksman.Diag.WorkspaceDiagModule.WorkspaceDiagModule→Marksman.Paths.RootPathMarksman.Diag.WorkspaceDiagModule.WorkspaceDiagModule→Marksman.Paths.UriWith`1
- Direction
- Marksman.Diag.WorkspaceDiagModule uses Marksman.Paths, so a change to Marksman.Paths can break Marksman.Diag.WorkspaceDiagModule, while a change to Marksman.Diag.WorkspaceDiagModule can't break Marksman.Paths.
- Position
- Below the diagonal: Marksman.Diag.WorkspaceDiagModule uses a module listed above it, which is the healthy direction.
27→9 Marksman.Diag.WorkspaceDiagModule uses Marksman.Workspace✕
- Connections
- 1 pair of types, where a type in Marksman.Diag.WorkspaceDiagModule uses a type in Marksman.Workspace.
- The types involved
Marksman.Diag.WorkspaceDiagModule.WorkspaceDiagModule→Marksman.Workspace.Workspace
- Direction
- Marksman.Diag.WorkspaceDiagModule uses Marksman.Workspace, so a change to Marksman.Workspace can break Marksman.Diag.WorkspaceDiagModule, while a change to Marksman.Diag.WorkspaceDiagModule can't break Marksman.Workspace.
- Position
- Below the diagonal: Marksman.Diag.WorkspaceDiagModule uses a module listed above it, which is the healthy direction.
27→14 Marksman.Diag.WorkspaceDiagModule uses Marksman.Names✕
- Connections
- 1 pair of types, where a type in Marksman.Diag.WorkspaceDiagModule uses a type in Marksman.Names.
- The types involved
Marksman.Diag.WorkspaceDiagModule.WorkspaceDiagModule→Marksman.Names.DocId
- Direction
- Marksman.Diag.WorkspaceDiagModule uses Marksman.Names, so a change to Marksman.Names can break Marksman.Diag.WorkspaceDiagModule, while a change to Marksman.Diag.WorkspaceDiagModule can't break Marksman.Names.
- Position
- Below the diagonal: Marksman.Diag.WorkspaceDiagModule uses a module listed above it, which is the healthy direction.
27→18 Marksman.Diag.WorkspaceDiagModule uses Marksman.Folder✕
- Connections
- 1 pair of types, where a type in Marksman.Diag.WorkspaceDiagModule uses a type in Marksman.Folder.
- The types involved
Marksman.Diag.WorkspaceDiagModule.WorkspaceDiagModule→Marksman.Folder.Folder
- Direction
- Marksman.Diag.WorkspaceDiagModule uses Marksman.Folder, so a change to Marksman.Folder can break Marksman.Diag.WorkspaceDiagModule, while a change to Marksman.Diag.WorkspaceDiagModule can't break Marksman.Folder.
- Position
- Below the diagonal: Marksman.Diag.WorkspaceDiagModule uses a module listed above it, which is the healthy direction.
28→3 Marksman.Doc.DocModule uses Ionide.LanguageServerProtocol.Types✕
- Connections
- 2 pairs of types, where a type in Marksman.Doc.DocModule uses a type in Ionide.LanguageServerProtocol.Types.
- The types involved
Marksman.Doc.DocModule.DocModule→Ionide.LanguageServerProtocol.Types.DidChangeTextDocumentParamsMarksman.Doc.DocModule.DocModule→Ionide.LanguageServerProtocol.Types.TextDocumentItem
- Direction
- Marksman.Doc.DocModule uses Ionide.LanguageServerProtocol.Types, so a change to Ionide.LanguageServerProtocol.Types can break Marksman.Doc.DocModule, while a change to Marksman.Doc.DocModule can't break Ionide.LanguageServerProtocol.Types.
- Position
- Below the diagonal: Marksman.Doc.DocModule uses a module listed above it, which is the healthy direction.
28→4 Marksman.Doc.DocModule uses Marksman.Config✕
- Connections
- 1 pair of types, where a type in Marksman.Doc.DocModule uses a type in Marksman.Config.
- The types involved
Marksman.Doc.DocModule.DocModule→Marksman.Config.ParserSettings
- Direction
- Marksman.Doc.DocModule uses Marksman.Config, so a change to Marksman.Config can break Marksman.Doc.DocModule, while a change to Marksman.Doc.DocModule can't break Marksman.Config.
- Position
- Below the diagonal: Marksman.Doc.DocModule uses a module listed above it, which is the healthy direction.
28→5 Marksman.Doc.DocModule uses Marksman.Doc✕
- Connections
- 1 pair of types, where a type in Marksman.Doc.DocModule uses a type in Marksman.Doc.
- The types involved
Marksman.Doc.DocModule.DocModule→Marksman.Doc.Doc
- Direction
- Marksman.Doc.DocModule uses Marksman.Doc, so a change to Marksman.Doc can break Marksman.Doc.DocModule, while a change to Marksman.Doc.DocModule can't break Marksman.Doc.
- Position
- Below the diagonal: Marksman.Doc.DocModule uses a module listed above it, which is the healthy direction.
28→6 Marksman.Doc.DocModule uses Marksman.Index✕
- Connections
- 1 pair of types, where a type in Marksman.Doc.DocModule uses a type in Marksman.Index.
- The types involved
Marksman.Doc.DocModule.DocModule→Marksman.Index.Index
- Direction
- Marksman.Doc.DocModule uses Marksman.Index, so a change to Marksman.Index can break Marksman.Doc.DocModule, while a change to Marksman.Doc.DocModule can't break Marksman.Index.
- Position
- Below the diagonal: Marksman.Doc.DocModule uses a module listed above it, which is the healthy direction.
28→8 Marksman.Doc.DocModule uses Marksman.Paths✕
- Connections
- 5 pairs of types, where a type in Marksman.Doc.DocModule uses a type in Marksman.Paths.
- The types involved
Marksman.Doc.DocModule.DocModule→Marksman.Paths.AbsPathMarksman.Doc.DocModule.DocModule→Marksman.Paths.LocalPathMarksman.Doc.DocModule.DocModule→Marksman.Paths.RelPathMarksman.Doc.DocModule.DocModule→Marksman.Paths.RootPathMarksman.Doc.DocModule.DocModule→Marksman.Paths.UriWith`1
- Direction
- Marksman.Doc.DocModule uses Marksman.Paths, so a change to Marksman.Paths can break Marksman.Doc.DocModule, while a change to Marksman.Doc.DocModule can't break Marksman.Paths.
- Position
- Below the diagonal: Marksman.Doc.DocModule uses a module listed above it, which is the healthy direction.
28→10 Marksman.Doc.DocModule uses Marksman.Misc✕
- Connections
- 1 pair of types, where a type in Marksman.Doc.DocModule uses a type in Marksman.Misc.
- The types involved
Marksman.Doc.DocModule.DocModule→Marksman.Misc.Slug
- Direction
- Marksman.Doc.DocModule uses Marksman.Misc, so a change to Marksman.Misc can break Marksman.Doc.DocModule, while a change to Marksman.Doc.DocModule can't break Marksman.Misc.
- Position
- Below the diagonal: Marksman.Doc.DocModule uses a module listed above it, which is the healthy direction.
28→12 Marksman.Doc.DocModule uses Marksman.Text✕
- Connections
- 1 pair of types, where a type in Marksman.Doc.DocModule uses a type in Marksman.Text.
- The types involved
Marksman.Doc.DocModule.DocModule→Marksman.Text.Text
- Direction
- Marksman.Doc.DocModule uses Marksman.Text, so a change to Marksman.Text can break Marksman.Doc.DocModule, while a change to Marksman.Doc.DocModule can't break Marksman.Text.
- Position
- Below the diagonal: Marksman.Doc.DocModule uses a module listed above it, which is the healthy direction.
28→14 Marksman.Doc.DocModule uses Marksman.Names✕
- Connections
- 1 pair of types, where a type in Marksman.Doc.DocModule uses a type in Marksman.Names.
- The types involved
Marksman.Doc.DocModule.DocModule→Marksman.Names.DocId
- Direction
- Marksman.Doc.DocModule uses Marksman.Names, so a change to Marksman.Names can break Marksman.Doc.DocModule, while a change to Marksman.Doc.DocModule can't break Marksman.Names.
- Position
- Below the diagonal: Marksman.Doc.DocModule uses a module listed above it, which is the healthy direction.
28→16 Marksman.Doc.DocModule uses Marksman.Ast✕
- Connections
- 1 pair of types, where a type in Marksman.Doc.DocModule uses a type in Marksman.Ast.
- The types involved
Marksman.Doc.DocModule.DocModule→Marksman.Ast.Ast
- Direction
- Marksman.Doc.DocModule uses Marksman.Ast, so a change to Marksman.Ast can break Marksman.Doc.DocModule, while a change to Marksman.Doc.DocModule can't break Marksman.Ast.
- Position
- Below the diagonal: Marksman.Doc.DocModule uses a module listed above it, which is the healthy direction.
28→17 Marksman.Doc.DocModule uses Marksman.Cst✕
- Connections
- 3 pairs of types, where a type in Marksman.Doc.DocModule uses a type in Marksman.Cst.
- The types involved
Marksman.Doc.DocModule.DocModule→Marksman.Cst.CstMarksman.Doc.DocModule.DocModule→Marksman.Cst.HeadingMarksman.Doc.DocModule.DocModule→Marksman.Cst.Node`1
- Direction
- Marksman.Doc.DocModule uses Marksman.Cst, so a change to Marksman.Cst can break Marksman.Doc.DocModule, while a change to Marksman.Doc.DocModule can't break Marksman.Cst.
- Position
- Below the diagonal: Marksman.Doc.DocModule uses a module listed above it, which is the healthy direction.
28→20 Marksman.Doc.DocModule uses Marksman.Syms✕
- Connections
- 1 pair of types, where a type in Marksman.Doc.DocModule uses a type in Marksman.Syms.
- The types involved
Marksman.Doc.DocModule.DocModule→Marksman.Syms.Sym
- Direction
- Marksman.Doc.DocModule uses Marksman.Syms, so a change to Marksman.Syms can break Marksman.Doc.DocModule, while a change to Marksman.Doc.DocModule can't break Marksman.Syms.
- Position
- Below the diagonal: Marksman.Doc.DocModule uses a module listed above it, which is the healthy direction.
29→3 Marksman.Lenses uses Ionide.LanguageServerProtocol.Types✕
- Connections
- 3 pairs of types, where a type in Marksman.Lenses uses a type in Ionide.LanguageServerProtocol.Types.
- The types involved
Marksman.Lenses.FindReferencesData→Ionide.LanguageServerProtocol.Types.LocationMarksman.Lenses.FindReferencesData→Ionide.LanguageServerProtocol.Types.PositionMarksman.Lenses.Lenses→Ionide.LanguageServerProtocol.Types.CodeLens
- Direction
- Marksman.Lenses uses Ionide.LanguageServerProtocol.Types, so a change to Ionide.LanguageServerProtocol.Types can break Marksman.Lenses, while a change to Marksman.Lenses can't break Ionide.LanguageServerProtocol.Types.
- Position
- Below the diagonal: Marksman.Lenses uses a module listed above it, which is the healthy direction.
29→5 Marksman.Lenses uses Marksman.Doc✕
- Connections
- 1 pair of types, where a type in Marksman.Lenses uses a type in Marksman.Doc.
- The types involved
Marksman.Lenses.Lenses→Marksman.Doc.Doc
- Direction
- Marksman.Lenses uses Marksman.Doc, so a change to Marksman.Doc can break Marksman.Lenses, while a change to Marksman.Lenses can't break Marksman.Doc.
- Position
- Below the diagonal: Marksman.Lenses uses a module listed above it, which is the healthy direction.
29→11 Marksman.Lenses uses Marksman.State✕
- Connections
- 1 pair of types, where a type in Marksman.Lenses uses a type in Marksman.State.
- The types involved
Marksman.Lenses.Lenses→Marksman.State.ClientDescription
- Direction
- Marksman.Lenses uses Marksman.State, so a change to Marksman.State can break Marksman.Lenses, while a change to Marksman.Lenses can't break Marksman.State.
- Position
- Below the diagonal: Marksman.Lenses uses a module listed above it, which is the healthy direction.
29→17 Marksman.Lenses uses Marksman.Cst✕
- Connections
- 1 pair of types, where a type in Marksman.Lenses uses a type in Marksman.Cst.
- The types involved
Marksman.Lenses.Lenses→Marksman.Cst.Element
- Direction
- Marksman.Lenses uses Marksman.Cst, so a change to Marksman.Cst can break Marksman.Lenses, while a change to Marksman.Lenses can't break Marksman.Cst.
- Position
- Below the diagonal: Marksman.Lenses uses a module listed above it, which is the healthy direction.
29→18 Marksman.Lenses uses Marksman.Folder✕
- Connections
- 1 pair of types, where a type in Marksman.Lenses uses a type in Marksman.Folder.
- The types involved
Marksman.Lenses.Lenses→Marksman.Folder.Folder
- Direction
- Marksman.Lenses uses Marksman.Folder, so a change to Marksman.Folder can break Marksman.Lenses, while a change to Marksman.Lenses can't break Marksman.Folder.
- Position
- Below the diagonal: Marksman.Lenses uses a module listed above it, which is the healthy direction.
30→3 Marksman.Refactor uses Ionide.LanguageServerProtocol.Types✕
- Connections
- 6 pairs of types, where a type in Marksman.Refactor uses a type in Ionide.LanguageServerProtocol.Types.
- The types involved
Marksman.Refactor.Refactor→Ionide.LanguageServerProtocol.Types.PositionMarksman.Refactor.Refactor→Ionide.LanguageServerProtocol.Types.RangeMarksman.Refactor.Refactor→Ionide.LanguageServerProtocol.Types.TextDocumentEditMarksman.Refactor.Refactor→Ionide.LanguageServerProtocol.Types.TextEditMarksman.Refactor.Refactor→Ionide.LanguageServerProtocol.Types.WorkspaceEditMarksman.Refactor.RenameResult→Ionide.LanguageServerProtocol.Types.WorkspaceEdit
- Direction
- Marksman.Refactor uses Ionide.LanguageServerProtocol.Types, so a change to Ionide.LanguageServerProtocol.Types can break Marksman.Refactor, while a change to Marksman.Refactor can't break Ionide.LanguageServerProtocol.Types.
- Position
- Below the diagonal: Marksman.Refactor uses a module listed above it, which is the healthy direction.
30→4 Marksman.Refactor uses Marksman.Config✕
- Connections
- 1 pair of types, where a type in Marksman.Refactor uses a type in Marksman.Config.
- The types involved
Marksman.Refactor.Refactor→Marksman.Config.ComplWikiStyle
- Direction
- Marksman.Refactor uses Marksman.Config, so a change to Marksman.Config can break Marksman.Refactor, while a change to Marksman.Refactor can't break Marksman.Config.
- Position
- Below the diagonal: Marksman.Refactor uses a module listed above it, which is the healthy direction.
30→5 Marksman.Refactor uses Marksman.Doc✕
- Connections
- 1 pair of types, where a type in Marksman.Refactor uses a type in Marksman.Doc.
- The types involved
Marksman.Refactor.Refactor→Marksman.Doc.Doc
- Direction
- Marksman.Refactor uses Marksman.Doc, so a change to Marksman.Doc can break Marksman.Refactor, while a change to Marksman.Refactor can't break Marksman.Doc.
- Position
- Below the diagonal: Marksman.Refactor uses a module listed above it, which is the healthy direction.
30→17 Marksman.Refactor uses Marksman.Cst✕
- Connections
- 1 pair of types, where a type in Marksman.Refactor uses a type in Marksman.Cst.
- The types involved
Marksman.Refactor.Refactor→Marksman.Cst.Element
- Direction
- Marksman.Refactor uses Marksman.Cst, so a change to Marksman.Cst can break Marksman.Refactor, while a change to Marksman.Refactor can't break Marksman.Cst.
- Position
- Below the diagonal: Marksman.Refactor uses a module listed above it, which is the healthy direction.
30→18 Marksman.Refactor uses Marksman.Folder✕
- Connections
- 1 pair of types, where a type in Marksman.Refactor uses a type in Marksman.Folder.
- The types involved
Marksman.Refactor.Refactor→Marksman.Folder.Folder
- Direction
- Marksman.Refactor uses Marksman.Folder, so a change to Marksman.Folder can break Marksman.Refactor, while a change to Marksman.Refactor can't break Marksman.Folder.
- Position
- Below the diagonal: Marksman.Refactor uses a module listed above it, which is the healthy direction.
31→5 Marksman.Refs uses Marksman.Doc✕
- Connections
- 3 pairs of types, where a type in Marksman.Refs uses a type in Marksman.Doc.
- The types involved
Marksman.Refs.Dest→Marksman.Doc.DocMarksman.Refs.DocLink→Marksman.Doc.DocMarksman.Refs.FileLink→Marksman.Doc.Doc
- Direction
- Marksman.Refs uses Marksman.Doc, so a change to Marksman.Doc can break Marksman.Refs, while a change to Marksman.Refs can't break Marksman.Doc.
- Position
- Below the diagonal: Marksman.Refs uses a module listed above it, which is the healthy direction.
31→17 Marksman.Refs uses Marksman.Cst✕
- Connections
- 4 pairs of types, where a type in Marksman.Refs uses a type in Marksman.Cst.
- The types involved
Marksman.Refs.Dest→Marksman.Cst.HeadingMarksman.Refs.Dest→Marksman.Cst.MdLinkDefMarksman.Refs.Dest→Marksman.Cst.Node`1Marksman.Refs.Dest→Marksman.Cst.Tag
- Direction
- Marksman.Refs uses Marksman.Cst, so a change to Marksman.Cst can break Marksman.Refs, while a change to Marksman.Refs can't break Marksman.Cst.
- Position
- Below the diagonal: Marksman.Refs uses a module listed above it, which is the healthy direction.
32→2 Marksman.Server.ServerUtil uses Ionide.LanguageServerProtocol.Logging.Types✕
- Connections
- 1 pair of types, where a type in Marksman.Server.ServerUtil uses a type in Ionide.LanguageServerProtocol.Logging.Types.
- The types involved
Marksman.Server.ServerUtil.ServerUtil→Ionide.LanguageServerProtocol.Logging.Types.ILog
- Direction
- Marksman.Server.ServerUtil uses Ionide.LanguageServerProtocol.Logging.Types, so a change to Ionide.LanguageServerProtocol.Logging.Types can break Marksman.Server.ServerUtil, while a change to Marksman.Server.ServerUtil can't break Ionide.LanguageServerProtocol.Logging.Types.
- Position
- Below the diagonal: Marksman.Server.ServerUtil uses a module listed above it, which is the healthy direction.
32→3 Marksman.Server.ServerUtil uses Ionide.LanguageServerProtocol.Types✕
- Connections
- 2 pairs of types, where a type in Marksman.Server.ServerUtil uses a type in Ionide.LanguageServerProtocol.Types.
- The types involved
Marksman.Server.ServerUtil.ServerUtil→Ionide.LanguageServerProtocol.Types.InitializeParamsMarksman.Server.ServerUtil.ServerUtil→Ionide.LanguageServerProtocol.Types.ServerCapabilities
- Direction
- Marksman.Server.ServerUtil uses Ionide.LanguageServerProtocol.Types, so a change to Ionide.LanguageServerProtocol.Types can break Marksman.Server.ServerUtil, while a change to Marksman.Server.ServerUtil can't break Ionide.LanguageServerProtocol.Types.
- Position
- Below the diagonal: Marksman.Server.ServerUtil uses a module listed above it, which is the healthy direction.
32→4 Marksman.Server.ServerUtil uses Marksman.Config✕
- Connections
- 2 pairs of types, where a type in Marksman.Server.ServerUtil uses a type in Marksman.Config.
- The types involved
Marksman.Server.ServerUtil.ServerUtil→Marksman.Config.ConfigMarksman.Server.ServerUtil.ServerUtil→Marksman.Config.TextSync
- Direction
- Marksman.Server.ServerUtil uses Marksman.Config, so a change to Marksman.Config can break Marksman.Server.ServerUtil, while a change to Marksman.Server.ServerUtil can't break Marksman.Config.
- Position
- Below the diagonal: Marksman.Server.ServerUtil uses a module listed above it, which is the healthy direction.
32→8 Marksman.Server.ServerUtil uses Marksman.Paths✕
- Connections
- 2 pairs of types, where a type in Marksman.Server.ServerUtil uses a type in Marksman.Paths.
- The types involved
Marksman.Server.ServerUtil.ServerUtil→Marksman.Paths.RootPathMarksman.Server.ServerUtil.ServerUtil→Marksman.Paths.UriWith`1
- Direction
- Marksman.Server.ServerUtil uses Marksman.Paths, so a change to Marksman.Paths can break Marksman.Server.ServerUtil, while a change to Marksman.Server.ServerUtil can't break Marksman.Paths.
- Position
- Below the diagonal: Marksman.Server.ServerUtil uses a module listed above it, which is the healthy direction.
32→9 Marksman.Server.ServerUtil uses Marksman.Workspace✕
- Connections
- 1 pair of types, where a type in Marksman.Server.ServerUtil uses a type in Marksman.Workspace.
- The types involved
Marksman.Server.ServerUtil.ServerUtil→Marksman.Workspace.Workspace
- Direction
- Marksman.Server.ServerUtil uses Marksman.Workspace, so a change to Marksman.Workspace can break Marksman.Server.ServerUtil, while a change to Marksman.Server.ServerUtil can't break Marksman.Workspace.
- Position
- Below the diagonal: Marksman.Server.ServerUtil uses a module listed above it, which is the healthy direction.
32→11 Marksman.Server.ServerUtil uses Marksman.State✕
- Connections
- 1 pair of types, where a type in Marksman.Server.ServerUtil uses a type in Marksman.State.
- The types involved
Marksman.Server.ServerUtil.ServerUtil→Marksman.State.ClientDescription
- Direction
- Marksman.Server.ServerUtil uses Marksman.State, so a change to Marksman.State can break Marksman.Server.ServerUtil, while a change to Marksman.Server.ServerUtil can't break Marksman.State.
- Position
- Below the diagonal: Marksman.Server.ServerUtil uses a module listed above it, which is the healthy direction.
32→18 Marksman.Server.ServerUtil uses Marksman.Folder✕
- Connections
- 1 pair of types, where a type in Marksman.Server.ServerUtil uses a type in Marksman.Folder.
- The types involved
Marksman.Server.ServerUtil.ServerUtil→Marksman.Folder.Folder
- Direction
- Marksman.Server.ServerUtil uses Marksman.Folder, so a change to Marksman.Folder can break Marksman.Server.ServerUtil, while a change to Marksman.Server.ServerUtil can't break Marksman.Folder.
- Position
- Below the diagonal: Marksman.Server.ServerUtil uses a module listed above it, which is the healthy direction.
33→2 Marksman.State.StateModule uses Ionide.LanguageServerProtocol.Logging.Types✕
- Connections
- 1 pair of types, where a type in Marksman.State.StateModule uses a type in Ionide.LanguageServerProtocol.Logging.Types.
- The types involved
Marksman.State.StateModule.StateModule→Ionide.LanguageServerProtocol.Logging.Types.ILog
- Direction
- Marksman.State.StateModule uses Ionide.LanguageServerProtocol.Logging.Types, so a change to Ionide.LanguageServerProtocol.Logging.Types can break Marksman.State.StateModule, while a change to Marksman.State.StateModule can't break Ionide.LanguageServerProtocol.Logging.Types.
- Position
- Below the diagonal: Marksman.State.StateModule uses a module listed above it, which is the healthy direction.
33→3 Marksman.State.StateModule uses Ionide.LanguageServerProtocol.Types✕
- Connections
- 2 pairs of types, where a type in Marksman.State.StateModule uses a type in Ionide.LanguageServerProtocol.Types.
- The types involved
Marksman.State.StateModule.StateModule→Ionide.LanguageServerProtocol.Types.ClientCapabilitiesMarksman.State.StateModule.StateModule→Ionide.LanguageServerProtocol.Types.WorkspaceFolder
- Direction
- Marksman.State.StateModule uses Ionide.LanguageServerProtocol.Types, so a change to Ionide.LanguageServerProtocol.Types can break Marksman.State.StateModule, while a change to Marksman.State.StateModule can't break Ionide.LanguageServerProtocol.Types.
- Position
- Below the diagonal: Marksman.State.StateModule uses a module listed above it, which is the healthy direction.
33→4 Marksman.State.StateModule uses Marksman.Config✕
- Connections
- 1 pair of types, where a type in Marksman.State.StateModule uses a type in Marksman.Config.
- The types involved
Marksman.State.StateModule.StateModule→Marksman.Config.Config
- Direction
- Marksman.State.StateModule uses Marksman.Config, so a change to Marksman.Config can break Marksman.State.StateModule, while a change to Marksman.State.StateModule can't break Marksman.Config.
- Position
- Below the diagonal: Marksman.State.StateModule uses a module listed above it, which is the healthy direction.
33→5 Marksman.State.StateModule uses Marksman.Doc✕
- Connections
- 1 pair of types, where a type in Marksman.State.StateModule uses a type in Marksman.Doc.
- The types involved
Marksman.State.StateModule.StateModule→Marksman.Doc.Doc
- Direction
- Marksman.State.StateModule uses Marksman.Doc, so a change to Marksman.Doc can break Marksman.State.StateModule, while a change to Marksman.State.StateModule can't break Marksman.Doc.
- Position
- Below the diagonal: Marksman.State.StateModule uses a module listed above it, which is the healthy direction.
33→8 Marksman.State.StateModule uses Marksman.Paths✕
- Connections
- 3 pairs of types, where a type in Marksman.State.StateModule uses a type in Marksman.Paths.
- The types involved
Marksman.State.StateModule.StateModule→Marksman.Paths.AbsPathMarksman.State.StateModule.StateModule→Marksman.Paths.RootPathMarksman.State.StateModule.StateModule→Marksman.Paths.UriWith`1
- Direction
- Marksman.State.StateModule uses Marksman.Paths, so a change to Marksman.Paths can break Marksman.State.StateModule, while a change to Marksman.State.StateModule can't break Marksman.Paths.
- Position
- Below the diagonal: Marksman.State.StateModule uses a module listed above it, which is the healthy direction.
33→9 Marksman.State.StateModule uses Marksman.Workspace✕
- Connections
- 1 pair of types, where a type in Marksman.State.StateModule uses a type in Marksman.Workspace.
- The types involved
Marksman.State.StateModule.StateModule→Marksman.Workspace.Workspace
- Direction
- Marksman.State.StateModule uses Marksman.Workspace, so a change to Marksman.Workspace can break Marksman.State.StateModule, while a change to Marksman.State.StateModule can't break Marksman.Workspace.
- Position
- Below the diagonal: Marksman.State.StateModule uses a module listed above it, which is the healthy direction.
33→11 Marksman.State.StateModule uses Marksman.State✕
- Connections
- 2 pairs of types, where a type in Marksman.State.StateModule uses a type in Marksman.State.
- The types involved
Marksman.State.StateModule.StateModule→Marksman.State.ClientDescriptionMarksman.State.StateModule.StateModule→Marksman.State.State
- Direction
- Marksman.State.StateModule uses Marksman.State, so a change to Marksman.State can break Marksman.State.StateModule, while a change to Marksman.State.StateModule can't break Marksman.State.
- Position
- Below the diagonal: Marksman.State.StateModule uses a module listed above it, which is the healthy direction.
33→18 Marksman.State.StateModule uses Marksman.Folder✕
- Connections
- 1 pair of types, where a type in Marksman.State.StateModule uses a type in Marksman.Folder.
- The types involved
Marksman.State.StateModule.StateModule→Marksman.Folder.Folder
- Direction
- Marksman.State.StateModule uses Marksman.Folder, so a change to Marksman.Folder can break Marksman.State.StateModule, while a change to Marksman.State.StateModule can't break Marksman.Folder.
- Position
- Below the diagonal: Marksman.State.StateModule uses a module listed above it, which is the healthy direction.
34→4 Marksman.Structure.StructureModule uses Marksman.Config✕
- Connections
- 1 pair of types, where a type in Marksman.Structure.StructureModule uses a type in Marksman.Config.
- The types involved
Marksman.Structure.StructureModule.StructureModule→Marksman.Config.ParserSettings
- Direction
- Marksman.Structure.StructureModule uses Marksman.Config, so a change to Marksman.Config can break Marksman.Structure.StructureModule, while a change to Marksman.Structure.StructureModule can't break Marksman.Config.
- Position
- Below the diagonal: Marksman.Structure.StructureModule uses a module listed above it, which is the healthy direction.
34→16 Marksman.Structure.StructureModule uses Marksman.Ast✕
- Connections
- 1 pair of types, where a type in Marksman.Structure.StructureModule uses a type in Marksman.Ast.
- The types involved
Marksman.Structure.StructureModule.StructureModule→Marksman.Ast.Element
- Direction
- Marksman.Structure.StructureModule uses Marksman.Ast, so a change to Marksman.Ast can break Marksman.Structure.StructureModule, while a change to Marksman.Structure.StructureModule can't break Marksman.Ast.
- Position
- Below the diagonal: Marksman.Structure.StructureModule uses a module listed above it, which is the healthy direction.
34→17 Marksman.Structure.StructureModule uses Marksman.Cst✕
- Connections
- 2 pairs of types, where a type in Marksman.Structure.StructureModule uses a type in Marksman.Cst.
- The types involved
Marksman.Structure.StructureModule.StructureModule→Marksman.Cst.CstMarksman.Structure.StructureModule.StructureModule→Marksman.Cst.Element
- Direction
- Marksman.Structure.StructureModule uses Marksman.Cst, so a change to Marksman.Cst can break Marksman.Structure.StructureModule, while a change to Marksman.Structure.StructureModule can't break Marksman.Cst.
- Position
- Below the diagonal: Marksman.Structure.StructureModule uses a module listed above it, which is the healthy direction.
34→20 Marksman.Structure.StructureModule uses Marksman.Syms✕
- Connections
- 1 pair of types, where a type in Marksman.Structure.StructureModule uses a type in Marksman.Syms.
- The types involved
Marksman.Structure.StructureModule.StructureModule→Marksman.Syms.Sym
- Direction
- Marksman.Structure.StructureModule uses Marksman.Syms, so a change to Marksman.Syms can break Marksman.Structure.StructureModule, while a change to Marksman.Structure.StructureModule can't break Marksman.Syms.
- Position
- Below the diagonal: Marksman.Structure.StructureModule uses a module listed above it, which is the healthy direction.
35→3 Marksman.Symbols uses Ionide.LanguageServerProtocol.Types✕
- Connections
- 3 pairs of types, where a type in Marksman.Symbols uses a type in Ionide.LanguageServerProtocol.Types.
- The types involved
Marksman.Symbols.Symbols→Ionide.LanguageServerProtocol.Types.DocumentSymbolMarksman.Symbols.Symbols→Ionide.LanguageServerProtocol.Types.SymbolInformationMarksman.Symbols.Symbols→Ionide.LanguageServerProtocol.Types.U2`2
- Direction
- Marksman.Symbols uses Ionide.LanguageServerProtocol.Types, so a change to Ionide.LanguageServerProtocol.Types can break Marksman.Symbols, while a change to Marksman.Symbols can't break Ionide.LanguageServerProtocol.Types.
- Position
- Below the diagonal: Marksman.Symbols uses a module listed above it, which is the healthy direction.
35→5 Marksman.Symbols uses Marksman.Doc✕
- Connections
- 1 pair of types, where a type in Marksman.Symbols uses a type in Marksman.Doc.
- The types involved
Marksman.Symbols.Symbols→Marksman.Doc.Doc
- Direction
- Marksman.Symbols uses Marksman.Doc, so a change to Marksman.Doc can break Marksman.Symbols, while a change to Marksman.Symbols can't break Marksman.Doc.
- Position
- Below the diagonal: Marksman.Symbols uses a module listed above it, which is the healthy direction.
35→9 Marksman.Symbols uses Marksman.Workspace✕
- Connections
- 1 pair of types, where a type in Marksman.Symbols uses a type in Marksman.Workspace.
- The types involved
Marksman.Symbols.Symbols→Marksman.Workspace.Workspace
- Direction
- Marksman.Symbols uses Marksman.Workspace, so a change to Marksman.Workspace can break Marksman.Symbols, while a change to Marksman.Symbols can't break Marksman.Workspace.
- Position
- Below the diagonal: Marksman.Symbols uses a module listed above it, which is the healthy direction.
35→14 Marksman.Symbols uses Marksman.Names✕
- Connections
- 1 pair of types, where a type in Marksman.Symbols uses a type in Marksman.Names.
- The types involved
Marksman.Symbols.Symbols→Marksman.Names.DocId
- Direction
- Marksman.Symbols uses Marksman.Names, so a change to Marksman.Names can break Marksman.Symbols, while a change to Marksman.Symbols can't break Marksman.Names.
- Position
- Below the diagonal: Marksman.Symbols uses a module listed above it, which is the healthy direction.
35→17 Marksman.Symbols uses Marksman.Cst✕
- Connections
- 4 pairs of types, where a type in Marksman.Symbols uses a type in Marksman.Cst.
- The types involved
Marksman.Symbols.Symbols→Marksman.Cst.CstMarksman.Symbols.Symbols→Marksman.Cst.HeadingMarksman.Symbols.Symbols→Marksman.Cst.Node`1Marksman.Symbols.Symbols→Marksman.Cst.Tag
- Direction
- Marksman.Symbols uses Marksman.Cst, so a change to Marksman.Cst can break Marksman.Symbols, while a change to Marksman.Symbols can't break Marksman.Cst.
- Position
- Below the diagonal: Marksman.Symbols uses a module listed above it, which is the healthy direction.
36→3 Marksman.Compl.Completions uses Ionide.LanguageServerProtocol.Types✕
- Connections
- 2 pairs of types, where a type in Marksman.Compl.Completions uses a type in Ionide.LanguageServerProtocol.Types.
- The types involved
Marksman.Compl.Completions.Completions→Ionide.LanguageServerProtocol.Types.CompletionItemMarksman.Compl.Completions.Completions→Ionide.LanguageServerProtocol.Types.Position
- Direction
- Marksman.Compl.Completions uses Ionide.LanguageServerProtocol.Types, so a change to Ionide.LanguageServerProtocol.Types can break Marksman.Compl.Completions, while a change to Marksman.Compl.Completions can't break Ionide.LanguageServerProtocol.Types.
- Position
- Below the diagonal: Marksman.Compl.Completions uses a module listed above it, which is the healthy direction.
36→4 Marksman.Compl.Completions uses Marksman.Config✕
- Connections
- 2 pairs of types, where a type in Marksman.Compl.Completions uses a type in Marksman.Config.
- The types involved
Marksman.Compl.Completions.Completions→Marksman.Config.ComplWikiStyleMarksman.Compl.Completions.Completions→Marksman.Config.Config
- Direction
- Marksman.Compl.Completions uses Marksman.Config, so a change to Marksman.Config can break Marksman.Compl.Completions, while a change to Marksman.Compl.Completions can't break Marksman.Config.
- Position
- Below the diagonal: Marksman.Compl.Completions uses a module listed above it, which is the healthy direction.
36→5 Marksman.Compl.Completions uses Marksman.Doc✕
- Connections
- 1 pair of types, where a type in Marksman.Compl.Completions uses a type in Marksman.Doc.
- The types involved
Marksman.Compl.Completions.Completions→Marksman.Doc.Doc
- Direction
- Marksman.Compl.Completions uses Marksman.Doc, so a change to Marksman.Doc can break Marksman.Compl.Completions, while a change to Marksman.Compl.Completions can't break Marksman.Doc.
- Position
- Below the diagonal: Marksman.Compl.Completions uses a module listed above it, which is the healthy direction.
36→17 Marksman.Compl.Completions uses Marksman.Cst✕
- Connections
- 1 pair of types, where a type in Marksman.Compl.Completions uses a type in Marksman.Cst.
- The types involved
Marksman.Compl.Completions.Completions→Marksman.Cst.MdLinkDef
- Direction
- Marksman.Compl.Completions uses Marksman.Cst, so a change to Marksman.Cst can break Marksman.Compl.Completions, while a change to Marksman.Compl.Completions can't break Marksman.Cst.
- Position
- Below the diagonal: Marksman.Compl.Completions uses a module listed above it, which is the healthy direction.
36→22 Marksman.Compl.Completions uses Marksman.Compl✕
- Connections
- 1 pair of types, where a type in Marksman.Compl.Completions uses a type in Marksman.Compl.
- The types involved
Marksman.Compl.Completions.Completions→Marksman.Compl.Completable
- Direction
- Marksman.Compl.Completions uses Marksman.Compl, so a change to Marksman.Compl can break Marksman.Compl.Completions, while a change to Marksman.Compl.Completions can't break Marksman.Compl.
- Position
- Below the diagonal: Marksman.Compl.Completions uses a module listed above it, which is the healthy direction.
37→2 Marksman.Conn.ConnModule uses Ionide.LanguageServerProtocol.Logging.Types✕
- Connections
- 1 pair of types, where a type in Marksman.Conn.ConnModule uses a type in Ionide.LanguageServerProtocol.Logging.Types.
- The types involved
Marksman.Conn.ConnModule.ConnModule→Ionide.LanguageServerProtocol.Logging.Types.ILog
- Direction
- Marksman.Conn.ConnModule uses Ionide.LanguageServerProtocol.Logging.Types, so a change to Ionide.LanguageServerProtocol.Logging.Types can break Marksman.Conn.ConnModule, while a change to Marksman.Conn.ConnModule can't break Ionide.LanguageServerProtocol.Logging.Types.
- Position
- Below the diagonal: Marksman.Conn.ConnModule uses a module listed above it, which is the healthy direction.
37→7 Marksman.Conn.ConnModule uses Marksman.MMap✕
- Connections
- 1 pair of types, where a type in Marksman.Conn.ConnModule uses a type in Marksman.MMap.
- The types involved
Marksman.Conn.ConnModule.ConnModule→Marksman.MMap.MMap`2
- Direction
- Marksman.Conn.ConnModule uses Marksman.MMap, so a change to Marksman.MMap can break Marksman.Conn.ConnModule, while a change to Marksman.Conn.ConnModule can't break Marksman.MMap.
- Position
- Below the diagonal: Marksman.Conn.ConnModule uses a module listed above it, which is the healthy direction.
37→14 Marksman.Conn.ConnModule uses Marksman.Names✕
- Connections
- 2 pairs of types, where a type in Marksman.Conn.ConnModule uses a type in Marksman.Names.
- The types involved
Marksman.Conn.ConnModule.ConnModule→Marksman.Names.DocIdMarksman.Conn.ConnModule.ConnModule→Marksman.Names.InternName
- Direction
- Marksman.Conn.ConnModule uses Marksman.Names, so a change to Marksman.Names can break Marksman.Conn.ConnModule, while a change to Marksman.Conn.ConnModule can't break Marksman.Names.
- Position
- Below the diagonal: Marksman.Conn.ConnModule uses a module listed above it, which is the healthy direction.
37→20 Marksman.Conn.ConnModule uses Marksman.Syms✕
- Connections
- 3 pairs of types, where a type in Marksman.Conn.ConnModule uses a type in Marksman.Syms.
- The types involved
Marksman.Conn.ConnModule.ConnModule→Marksman.Syms.RefMarksman.Conn.ConnModule.ConnModule→Marksman.Syms.ScopeMarksman.Conn.ConnModule.ConnModule→Marksman.Syms.Sym
- Direction
- Marksman.Conn.ConnModule uses Marksman.Syms, so a change to Marksman.Syms can break Marksman.Conn.ConnModule, while a change to Marksman.Conn.ConnModule can't break Marksman.Syms.
- Position
- Below the diagonal: Marksman.Conn.ConnModule uses a module listed above it, which is the healthy direction.
37→24 Marksman.Conn.ConnModule uses Marksman.Conn✕
- Connections
- 9 pairs of types, where a type in Marksman.Conn.ConnModule uses a type in Marksman.Conn.
- The types involved
Marksman.Conn.ConnModule.ConnModule→Marksman.Conn.ConnMarksman.Conn.ConnModule.ConnModule→Marksman.Conn.ConnDifferenceMarksman.Conn.ConnModule.ConnModule→Marksman.Conn.ConnectionChangeMarksman.Conn.ConnModule.ConnModule→Marksman.Conn.ConnectionComputationMarksman.Conn.ConnModule.ConnModule→Marksman.Conn.ConnectionDependencyMarksman.Conn.ConnModule.ConnModule→Marksman.Conn.ConnectionValueMarksman.Conn.ConnModule.ConnModule→Marksman.Conn.DefinitionSelectorMarksman.Conn.ConnModule.ConnModule→Marksman.Conn.OracleMarksman.Conn.ConnModule.ConnModule→Marksman.Conn.ReferenceResolution
- Direction
- Marksman.Conn.ConnModule uses Marksman.Conn, so a change to Marksman.Conn can break Marksman.Conn.ConnModule, while a change to Marksman.Conn.ConnModule can't break Marksman.Conn.
- Position
- Below the diagonal: Marksman.Conn.ConnModule uses a module listed above it, which is the healthy direction.
38→3 Marksman.Diag uses Ionide.LanguageServerProtocol.Types✕
- Connections
- 2 pairs of types, where a type in Marksman.Diag uses a type in Ionide.LanguageServerProtocol.Types.
- The types involved
Marksman.Diag.Diag→Ionide.LanguageServerProtocol.Types.DiagnosticMarksman.Diag.Entry→Ionide.LanguageServerProtocol.Types.Range
- Direction
- Marksman.Diag uses Ionide.LanguageServerProtocol.Types, so a change to Ionide.LanguageServerProtocol.Types can break Marksman.Diag, while a change to Marksman.Diag can't break Ionide.LanguageServerProtocol.Types.
- Position
- Below the diagonal: Marksman.Diag uses a module listed above it, which is the healthy direction.
38→5 Marksman.Diag uses Marksman.Doc✕
- Connections
- 1 pair of types, where a type in Marksman.Diag uses a type in Marksman.Doc.
- The types involved
Marksman.Diag.Diag→Marksman.Doc.Doc
- Direction
- Marksman.Diag uses Marksman.Doc, so a change to Marksman.Doc can break Marksman.Diag, while a change to Marksman.Diag can't break Marksman.Doc.
- Position
- Below the diagonal: Marksman.Diag uses a module listed above it, which is the healthy direction.
38→17 Marksman.Diag uses Marksman.Cst✕
- Connections
- 2 pairs of types, where a type in Marksman.Diag uses a type in Marksman.Cst.
- The types involved
Marksman.Diag.Diag→Marksman.Cst.ElementMarksman.Diag.Entry→Marksman.Cst.Element
- Direction
- Marksman.Diag uses Marksman.Cst, so a change to Marksman.Cst can break Marksman.Diag, while a change to Marksman.Diag can't break Marksman.Cst.
- Position
- Below the diagonal: Marksman.Diag uses a module listed above it, which is the healthy direction.
38→18 Marksman.Diag uses Marksman.Folder✕
- Connections
- 1 pair of types, where a type in Marksman.Diag uses a type in Marksman.Folder.
- The types involved
Marksman.Diag.Diag→Marksman.Folder.Folder
- Direction
- Marksman.Diag uses Marksman.Folder, so a change to Marksman.Folder can break Marksman.Diag, while a change to Marksman.Diag can't break Marksman.Folder.
- Position
- Below the diagonal: Marksman.Diag uses a module listed above it, which is the healthy direction.
38→20 Marksman.Diag uses Marksman.Syms✕
- Connections
- 2 pairs of types, where a type in Marksman.Diag uses a type in Marksman.Syms.
- The types involved
Marksman.Diag.Diag→Marksman.Syms.RefMarksman.Diag.Entry→Marksman.Syms.Ref
- Direction
- Marksman.Diag uses Marksman.Syms, so a change to Marksman.Syms can break Marksman.Diag, while a change to Marksman.Diag can't break Marksman.Syms.
- Position
- Below the diagonal: Marksman.Diag uses a module listed above it, which is the healthy direction.
38→31 Marksman.Diag uses Marksman.Refs✕
- Connections
- 2 pairs of types, where a type in Marksman.Diag uses a type in Marksman.Refs.
- The types involved
Marksman.Diag.Diag→Marksman.Refs.DestMarksman.Diag.Entry→Marksman.Refs.Dest
- Direction
- Marksman.Diag uses Marksman.Refs, so a change to Marksman.Refs can break Marksman.Diag, while a change to Marksman.Diag can't break Marksman.Refs.
- Position
- Below the diagonal: Marksman.Diag uses a module listed above it, which is the healthy direction.
39→4 Marksman.Folder.FolderModule uses Marksman.Config✕
- Connections
- 2 pairs of types, where a type in Marksman.Folder.FolderModule uses a type in Marksman.Config.
- The types involved
Marksman.Folder.FolderModule.FolderModule→Marksman.Config.ConfigMarksman.Folder.FolderModule.FolderModule→Marksman.Config.ParserSettings
- Direction
- Marksman.Folder.FolderModule uses Marksman.Config, so a change to Marksman.Config can break Marksman.Folder.FolderModule, while a change to Marksman.Folder.FolderModule can't break Marksman.Config.
- Position
- Below the diagonal: Marksman.Folder.FolderModule uses a module listed above it, which is the healthy direction.
39→5 Marksman.Folder.FolderModule uses Marksman.Doc✕
- Connections
- 1 pair of types, where a type in Marksman.Folder.FolderModule uses a type in Marksman.Doc.
- The types involved
Marksman.Folder.FolderModule.FolderModule→Marksman.Doc.Doc
- Direction
- Marksman.Folder.FolderModule uses Marksman.Doc, so a change to Marksman.Doc can break Marksman.Folder.FolderModule, while a change to Marksman.Folder.FolderModule can't break Marksman.Doc.
- Position
- Below the diagonal: Marksman.Folder.FolderModule uses a module listed above it, which is the healthy direction.
39→7 Marksman.Folder.FolderModule uses Marksman.MMap✕
- Connections
- 1 pair of types, where a type in Marksman.Folder.FolderModule uses a type in Marksman.MMap.
- The types involved
Marksman.Folder.FolderModule.FolderModule→Marksman.MMap.MMap`2
- Direction
- Marksman.Folder.FolderModule uses Marksman.MMap, so a change to Marksman.MMap can break Marksman.Folder.FolderModule, while a change to Marksman.Folder.FolderModule can't break Marksman.MMap.
- Position
- Below the diagonal: Marksman.Folder.FolderModule uses a module listed above it, which is the healthy direction.
39→8 Marksman.Folder.FolderModule uses Marksman.Paths✕
- Connections
- 4 pairs of types, where a type in Marksman.Folder.FolderModule uses a type in Marksman.Paths.
- The types involved
Marksman.Folder.FolderModule.FolderModule→Marksman.Paths.AbsPathMarksman.Folder.FolderModule.FolderModule→Marksman.Paths.RelPathMarksman.Folder.FolderModule.FolderModule→Marksman.Paths.RootPathMarksman.Folder.FolderModule.FolderModule→Marksman.Paths.UriWith`1
- Direction
- Marksman.Folder.FolderModule uses Marksman.Paths, so a change to Marksman.Paths can break Marksman.Folder.FolderModule, while a change to Marksman.Folder.FolderModule can't break Marksman.Paths.
- Position
- Below the diagonal: Marksman.Folder.FolderModule uses a module listed above it, which is the healthy direction.
39→10 Marksman.Folder.FolderModule uses Marksman.Misc✕
- Connections
- 1 pair of types, where a type in Marksman.Folder.FolderModule uses a type in Marksman.Misc.
- The types involved
Marksman.Folder.FolderModule.FolderModule→Marksman.Misc.Slug
- Direction
- Marksman.Folder.FolderModule uses Marksman.Misc, so a change to Marksman.Misc can break Marksman.Folder.FolderModule, while a change to Marksman.Folder.FolderModule can't break Marksman.Misc.
- Position
- Below the diagonal: Marksman.Folder.FolderModule uses a module listed above it, which is the healthy direction.
39→14 Marksman.Folder.FolderModule uses Marksman.Names✕
- Connections
- 3 pairs of types, where a type in Marksman.Folder.FolderModule uses a type in Marksman.Names.
- The types involved
Marksman.Folder.FolderModule.FolderModule→Marksman.Names.DocIdMarksman.Folder.FolderModule.FolderModule→Marksman.Names.InternNameMarksman.Folder.FolderModule.FolderModule→Marksman.Names.InternPath
- Direction
- Marksman.Folder.FolderModule uses Marksman.Names, so a change to Marksman.Names can break Marksman.Folder.FolderModule, while a change to Marksman.Folder.FolderModule can't break Marksman.Names.
- Position
- Below the diagonal: Marksman.Folder.FolderModule uses a module listed above it, which is the healthy direction.
39→18 Marksman.Folder.FolderModule uses Marksman.Folder✕
- Connections
- 2 pairs of types, where a type in Marksman.Folder.FolderModule uses a type in Marksman.Folder.
- The types involved
Marksman.Folder.FolderModule.FolderModule→Marksman.Folder.DocumentDifferenceMarksman.Folder.FolderModule.FolderModule→Marksman.Folder.Folder
- Direction
- Marksman.Folder.FolderModule uses Marksman.Folder, so a change to Marksman.Folder can break Marksman.Folder.FolderModule, while a change to Marksman.Folder.FolderModule can't break Marksman.Folder.
- Position
- Below the diagonal: Marksman.Folder.FolderModule uses a module listed above it, which is the healthy direction.
39→20 Marksman.Folder.FolderModule uses Marksman.Syms✕
- Connections
- 1 pair of types, where a type in Marksman.Folder.FolderModule uses a type in Marksman.Syms.
- The types involved
Marksman.Folder.FolderModule.FolderModule→Marksman.Syms.Sym
- Direction
- Marksman.Folder.FolderModule uses Marksman.Syms, so a change to Marksman.Syms can break Marksman.Folder.FolderModule, while a change to Marksman.Folder.FolderModule can't break Marksman.Syms.
- Position
- Below the diagonal: Marksman.Folder.FolderModule uses a module listed above it, which is the healthy direction.
39→24 Marksman.Folder.FolderModule uses Marksman.Conn✕
- Connections
- 2 pairs of types, where a type in Marksman.Folder.FolderModule uses a type in Marksman.Conn.
- The types involved
Marksman.Folder.FolderModule.FolderModule→Marksman.Conn.ConnMarksman.Folder.FolderModule.FolderModule→Marksman.Conn.Oracle
- Direction
- Marksman.Folder.FolderModule uses Marksman.Conn, so a change to Marksman.Conn can break Marksman.Folder.FolderModule, while a change to Marksman.Folder.FolderModule can't break Marksman.Conn.
- Position
- Below the diagonal: Marksman.Folder.FolderModule uses a module listed above it, which is the healthy direction.
40→3 Marksman.Refs.DestModule uses Ionide.LanguageServerProtocol.Types✕
- Connections
- 2 pairs of types, where a type in Marksman.Refs.DestModule uses a type in Ionide.LanguageServerProtocol.Types.
- The types involved
Marksman.Refs.DestModule.DestModule→Ionide.LanguageServerProtocol.Types.LocationMarksman.Refs.DestModule.DestModule→Ionide.LanguageServerProtocol.Types.Range
- Direction
- Marksman.Refs.DestModule uses Ionide.LanguageServerProtocol.Types, so a change to Ionide.LanguageServerProtocol.Types can break Marksman.Refs.DestModule, while a change to Marksman.Refs.DestModule can't break Ionide.LanguageServerProtocol.Types.
- Position
- Below the diagonal: Marksman.Refs.DestModule uses a module listed above it, which is the healthy direction.
40→5 Marksman.Refs.DestModule uses Marksman.Doc✕
- Connections
- 1 pair of types, where a type in Marksman.Refs.DestModule uses a type in Marksman.Doc.
- The types involved
Marksman.Refs.DestModule.DestModule→Marksman.Doc.Doc
- Direction
- Marksman.Refs.DestModule uses Marksman.Doc, so a change to Marksman.Doc can break Marksman.Refs.DestModule, while a change to Marksman.Refs.DestModule can't break Marksman.Doc.
- Position
- Below the diagonal: Marksman.Refs.DestModule uses a module listed above it, which is the healthy direction.
40→17 Marksman.Refs.DestModule uses Marksman.Cst✕
- Connections
- 1 pair of types, where a type in Marksman.Refs.DestModule uses a type in Marksman.Cst.
- The types involved
Marksman.Refs.DestModule.DestModule→Marksman.Cst.Element
- Direction
- Marksman.Refs.DestModule uses Marksman.Cst, so a change to Marksman.Cst can break Marksman.Refs.DestModule, while a change to Marksman.Refs.DestModule can't break Marksman.Cst.
- Position
- Below the diagonal: Marksman.Refs.DestModule uses a module listed above it, which is the healthy direction.
40→18 Marksman.Refs.DestModule uses Marksman.Folder✕
- Connections
- 1 pair of types, where a type in Marksman.Refs.DestModule uses a type in Marksman.Folder.
- The types involved
Marksman.Refs.DestModule.DestModule→Marksman.Folder.Folder
- Direction
- Marksman.Refs.DestModule uses Marksman.Folder, so a change to Marksman.Folder can break Marksman.Refs.DestModule, while a change to Marksman.Refs.DestModule can't break Marksman.Folder.
- Position
- Below the diagonal: Marksman.Refs.DestModule uses a module listed above it, which is the healthy direction.
40→20 Marksman.Refs.DestModule uses Marksman.Syms✕
- Connections
- 1 pair of types, where a type in Marksman.Refs.DestModule uses a type in Marksman.Syms.
- The types involved
Marksman.Refs.DestModule.DestModule→Marksman.Syms.Sym
- Direction
- Marksman.Refs.DestModule uses Marksman.Syms, so a change to Marksman.Syms can break Marksman.Refs.DestModule, while a change to Marksman.Refs.DestModule can't break Marksman.Syms.
- Position
- Below the diagonal: Marksman.Refs.DestModule uses a module listed above it, which is the healthy direction.
40→31 Marksman.Refs.DestModule uses Marksman.Refs✕
- Connections
- 1 pair of types, where a type in Marksman.Refs.DestModule uses a type in Marksman.Refs.
- The types involved
Marksman.Refs.DestModule.DestModule→Marksman.Refs.Dest
- Direction
- Marksman.Refs.DestModule uses Marksman.Refs, so a change to Marksman.Refs can break Marksman.Refs.DestModule, while a change to Marksman.Refs.DestModule can't break Marksman.Refs.
- Position
- Below the diagonal: Marksman.Refs.DestModule uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A05:2025 — Injection | 11 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 9 | High / Critical |
Roadmap
Top priorities: Resolve the 1 No ADRs found finding(s) in ADR Quality; 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; Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 1 No ADRs found finding(s) in ADR Quality. | +5.9 pts | Low | ADR Quality |
| Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them. | +5.0 pts | Medium | Architecture documentation |
| Resolve the 1 Deprecated finding(s) in Dependency Hygiene — start with Tests.fsproj. | +1.9 pts | Low | Dependency Hygiene |
| Resolve the 1 Outdated finding(s) in Dependency Hygiene — start with Tests.fsproj. | +1.9 pts | Low | Dependency Hygiene |
| Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release. | +2.7 pts | Medium | Release Hygiene |
| Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite. | +1.9 pts | Medium | Documentation (README) |
| Resolve the 4 CommentedOutCode finding(s) in Explicit Debt — start with PatchedLinkInlineParser.cs (4). | +0.6 pts | Low | Explicit Debt |
| Resolve the 2 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED. | +0.6 pts | Low | Supply-chain Provenance & Signing |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 2.1 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.3 | Slop | Static Analysis (SAST): High: REDACTED |
| MarkdigPatches/PatchedLinkInlineParser.cs | 6.0 | Mixed | Explicit Debt: CommentedOutCode |
| Marksman/Parser.fs | 6.9 | Mixed | Cyclomatic Complexity: Markdown.scrapeText (cyclomatic 25) |
| Marksman/Compl.fs | 7.0 | Mixed | Cyclomatic Complexity: PartialElementModule.linkInLine (cyclomatic 31) |
| Marksman/Conn.fs | 7.2 | Mixed | Cognitive Complexity: Conn.CompactFormat (cognitive 24) |
| REDACTED | 7.2 | Mixed | Dependency Vulnerabilities: High CVE: REDACTED |
| Marksman/Ast.fs | 7.8 | Mixed | Cyclomatic Complexity: ElementModule.toSym (cyclomatic 24) |
| Marksman/Refactor.fs | 7.8 | Mixed | Cognitive Complexity: Refactor.renameHeadingLink (cognitive 26) |
| Marksman/Text.fs | 7.8 | Mixed | Cognitive Complexity: LineMap.TryFindPosition (cognitive 23) |
| Marksman/Misc.fs | 7.8 | Mixed | Cognitive Complexity: Misc.String.Slug (cognitive 16) |
| Tests/Tests.fsproj | 8.0 | Near-clean | Dependency Hygiene: Deprecated: xunit |
| Marksman/Paths.fs | 8.5 | Near-clean | Cyclomatic Complexity: Paths.systemPathToUriString (cyclomatic 19) |
| Marksman/CodeActions.fs | 8.5 | Near-clean | Cognitive Complexity: CodeActions.tableOfContentsInner (cognitive 39) |
| Marksman/Diag.fs | 8.5 | Near-clean | Cognitive Complexity: Diag.checkLink (cognitive 33) |
| LanguageServerProtocol/JsonUtils.fs | 8.5 | Near-clean | Cognitive Complexity: ErasedUnionConverter.ReadJson (cognitive 18) |
| Marksman/Names.fs | 8.5 | Near-clean | Cognitive Complexity: InternNameModule.tryAsPath (cognitive 16) |
| LanguageServerProtocol/Server.fs | 8.5 | Near-clean | God Classes: TooManyMethods: LspServer |
| LanguageServerProtocol/Types.fs | 8.5 | Near-clean | God Classes: FileTooLong: LanguageServerProtocol/Types.fs |
| Marksman/Server.fs | 8.5 | Near-clean | God Classes: FileTooLong: Marksman/Server.fs |
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 46 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 1.0, the weighted average across measured dimensions.
What we checked — 46 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, 67 of 90 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
- 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 Benchmarks/ConnectionUpdates.fs that could not be established — the complexity reader for the file reports no body extents, or the history carries no per-line attribution — so the row quotes the file's worst body, which the counted changes may never have touched. The churn count is unaffected.
- D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Single-maintainer repository — bus factor is not applicable (33 contributor(s) across 533 commit(s) sampled, automation and bot accounts excluded). One of them holds 91% of the history; the other 32 hold 0.3% each on average, below the 5% at which there is somebody to hand the work to. That is a single maintainer with drive-by contributors, not a team whose knowledge has concentrated — so the bus factor is not applicable and there is nothing here for the owner to act on.
- D17 Explicit Debt — 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. The C# workspace loaded this repository's projects but reported a load failure, and the dead-code reference search is unreliable over a graph that did not load cleanly, so it was skipped. The other debt markers on this row were read; dead symbols were not, and their absence from the score is not a finding that the code has none. First load diagnostic: Failure: Cannot open project 'Marksman/Marksman.fsproj' because the file extension '.fsproj' is not associated with a language.
- D17 Explicit Debt — 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. The 4 deducted marker(s) and the 0.4/KLoC density on this row were taken over this repository's .NET projects ALONE: .fs (12,953 lines, 97% of production source) went unread, because every marker collector on this path is reached through a C# workspace. D17's marker collectors need a compiler we do not have for that language, so none of its nine marker kinds were read there. The debt in that source is UNMEASURED — its absence from the score above is a gap in this analyzer's language coverage, not a finding that the code carries none.
- D19 Documentation Quality — 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 kind did not reach the 95 % precision gate in three adjudicated runs (docs/plans/deterministic-engine/adjudication/D19-sample3-v3.md), so by the pre-registered fallback it publishes no row until a re-measurement shows it does. The candidates are counted here, not reported as findings, and the score does not include them.
- 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. D21's deterministic naming rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. Until then its declarations carry no naming verdict this run — this says nothing about whether its names are consistent.
- D22 Internal API Consistency — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. The loaded project set declares no packable project and no `.Contracts` project, so there is no intentionally-exposed surface for API consistency to be judged over.
- 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. `MarkdigPatches` (393 LoC, 640 public types across 220 namespaces) 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.
- M4 Documentation accuracy — 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. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
- P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
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.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- D8 Code Coverage: Coverage is measured by building and running the test suite inside 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.
- D11 Test Reliability: Flakiness is inferred from history/markers — we run the suite once (for coverage), not the repeated runs under varied conditions that reveal nondeterminism, so a flaky test never recorded as failing is invisible here.
- D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
- D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- D20 ADR Quality: ADR quality 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.
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
- P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
- P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
Dimensions
D1 · Cyclomatic Complexity
7 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was PartialElementModule.linkInLine at 31.
What to do
- Bring the 7 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with PartialElementModule.linkInLine (cyclomatic 31), PromptModule.ofCompletable (cyclomatic 25), Markdown.scrapeText (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 7 together lifts Cyclomatic Complexity from 8.7 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
D2 · Cognitive Complexity
16 method(s) exceeded the cognitive complexity threshold of 15; the worst was Markdown.scrapeText at 61.
What to do
- Bring the 16 bodies over 15 down to 15 or less in Cognitive Complexity — start with Markdown.scrapeText (cognitive 61), CodeActions.tableOfContentsInner (cognitive 39), Diag.checkLink (cognitive 33). — 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 16 together lifts Cognitive Complexity from 7.3 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
D3 · God Classes
9 god class(es) detected.
What to do
- Resolve the 5 FileTooLong finding(s) in God Classes — start with Types.fs, Server.fs, Compl.fs. — One of this dimension's main actionable groups (5 warning-level).
- Resolve the 2 TooManyMethods finding(s) in God Classes — start with Server.fs, Client.fs. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 TooManyFunctions finding(s) in God Classes — start with Misc.fs. — One of this dimension's main actionable groups (1 warning-level).
D4 · Code Duplication
6 duplicated block group(s) detected.
What to do
- Resolve the 1 Duplicated block (11–13 lines × 2) finding(s) in Code Duplication — start with LanguageServerProtocol.fs. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Duplicated block (13 lines × 2) finding(s) in Code Duplication — start with Compl.fs. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Duplicated block (7–10 lines × 2) finding(s) in Code Duplication — start with Compl.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).
D6 · Cohesion (LCOM4)
0 of 11 classes have LCOM4 above 3.
D8 · Code Coverage
Line coverage 70.4%.
D11 · Test Reliability
0 flaky across 1 measured tier(s). unit: measured (0 flaky).
D12 · Dependency Hygiene
12 outdated, 0 vulnerable, 1 deprecated packages.
What to do
- Resolve the 1 Deprecated finding(s) in Dependency Hygiene — start with Tests.fsproj. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Outdated finding(s) in Dependency Hygiene — start with Tests.fsproj. — One of this dimension's main actionable groups (1 recommendation-level).
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D14 · License Compliance
0 of 159 packages use a banned license. ★ DEPTH: this repository's MSBuild projects declare 16 direct `PackageReference`(s), and 143 further package(s) were reached beyond them by closing the graph over nuget.org's own nuspec dependency graph — so a banned licence pulled in only by a dependency's OWN dependencies is inside this verdict. A package whose licence nuget.org could not be asked for is not graded, and version ranges are taken at their lower bound, so this is the closure as that graph states it rather than a restored consumer's exact resolution.
D15 · Churn × Complexity Hotspots
Top hotspots: Benchmarks/ConnectionUpdates.fs (2×17=34)
What to do
- Resolve the 1 Hotspot finding(s) in Churn × Complexity Hotspots — start with ConnectionUpdates.fs. — One of this dimension's main actionable groups (1 warning-level).
D17 · Explicit Debt
4 deducted debt markers + unmeasured dead symbols across 393 LoC in the .NET projects (0.4/KLoC) → score 9.2. Dead code not measured: the solution did not load cleanly, so the reference search was skipped. Measured on the .NET source only: .fs (97% of production source) was not read, and carries at least 0 uncounted task marker(s) in 0 file(s).
What to do
- Resolve the 4 CommentedOutCode finding(s) in Explicit Debt — start with PatchedLinkInlineParser.cs (4). — One of this dimension's main actionable groups (4 warning-level).
D19 · Documentation Quality
1 of 1 documentation facets pass in full. 6 document(s) read across 2 unit(s).
D20 · ADR Quality
No architecture decision records were found.
What to do
- Resolve the 1 No ADRs found finding(s) in ADR Quality. — One of this dimension's main actionable groups (1 recommendation-level).
D27 · Navigability
93 % of calls cross a namespace and 1 % go through an interface, but 100 % 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)
11 finding(s): 0 critical, 9 high, 2 medium, 0 low. 7 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. Separately, one or more rules could not re-parse an embedded snippet in 1 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.
What to do
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- No action in Static Analysis (SAST) — all 7 REDACTED finding(s) are reported here at file:line but scored by D36 (supply-chain provenance), so none is charged to this dimension. — One of this dimension's main actionable groups (7 issue-level, 0 of them charged here).
D30 · Dependency Vulnerabilities
1 finding(s): 0 critical, 1 high, 0 medium, 0 low.
What to do
- Resolve the 1 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
D34 · Knowledge Freshness
Every significant source file has living knowledge — recently and meaningfully worked. Counted over 37 of the 42 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
D35 · Change Coupling
No strong hidden change-coupling between production files.
D36 · Supply-chain Provenance & Signing
0/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).
What to do
- Resolve the 2 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).
D39 · IL Efficiency
10 of 2425 first-party methods have an oversized IL body.
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 5 platform declaration(s) and 0 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
Frontend & cross-cutting dimensions
AX10 · Code composition
What to do
- The domain core is a small share of production code, but most of the rest matched no layer vocabulary at all — so this is not yet an anemic-domain finding. The namespace/path convention could not place that code, which makes the composition above a statement about the naming, not about the design. Name the layers (or check that the repository's conventions differ from the ones this check knows) before reading a thin domain into it.
AX3 · Project dependency cycles
AX4 · Dependency direction
AX5 · Architecture & structure
AX8 · Test isolation
GD1 · Unfinished & placeholder code
IC1 · Incompleteness & stubs
- A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers). (×5) — MarkdigPatches/PatchedLinkInlineParser.cs:69, MarkdigPatches/PatchedLinkInlineParser.cs:80, MarkdigPatches/PatchedLinkInlineParser.cs:145, …
What to do
- Clear the softer debt: remove commented-out code and dead branches, re-enable or delete skipped tests, and replace blanket warning suppressions with targeted ones.
M1 · Documentation (README)
What to do
- Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
- Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
- Describe the projects a newcomer cannot place from the root README: 1 of 1 have no README of their own, in their folder or in their family's project (`MarkdigPatches`).
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
M4 · Documentation accuracy
P1 · CI/CD gates
P3 · Security & performance tooling
- No static application security testing detected. For this repository's stack, add `semgrep --config=auto` plus gitleaks for committed secrets (F# is not a CodeQL language and has no language-specific SAST engine) as a CI step. What was searched, so you can tell an absence from a miss: the 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:4
- `Benchmarks/Benchmarks.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`. — Benchmarks/Benchmarks.fsproj:15
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
P6 · Release Hygiene
- No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
What to do
- Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.
PF3 · Async & latency hygiene
X12 · Unreachable branch
X16 · Unfloored truncation loop
X23 · Unguarded diagnostic materialisation
X28 · Index access outside its own emptiness guard
X5 · Nullable reference types
- ~1.3 `!` suppressions per 1k syntax nodes — 2 suppression(s) across the 1497 syntax node(s) in code where nullable warnings are ENABLED, which is the only code a `!` can suppress anything in (a `!` under `#nullable disable` is inert and is not counted, and its file's nodes are not in the denominator). Each one tells the compiler to trust you about null, suppressing the very safety NRTs provide. Many are correct: each is a claim the checker could not verify, and it is wrong only where the value can in fact be missing, so review the densest places first.
What to do
- Enable <Nullable>enable</Nullable> across all projects and resolve warnings rather than suppressing with `!`.
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 90% | Exemplary | Solid. |
| Architecture | 100% | Exemplary | Solid. |
| Maturity | 59% | Adequate — gated by M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 57% | Adequate — gated by P3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 66% | Adequate — gated by D36 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Performance | 100% | Exemplary | Strongest area. |
Unscored — 1 check(s) recorded observations but carry no score
- SC1 Supply-chain hygiene — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Not evidenced — 1 control(s) we could not find positive evidence for
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 72 check(s) not relevant to this codebase
- AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
- AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
- AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
- AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
- AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
- AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
- AC7 A11y enforcement — No web markup found — accessibility is not applicable to this repository.
- AX1 Captive dependencies — no DI registrations detected
- AX2 Stateful singletons — no singleton implementations detected
- AX6 Interface segregation — no public interfaces
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
- AXB1 Runtime evidence locked — no reproducible boot — This repository has nothing the runtime tiers could boot or serve — no markup, no UI framework or web-server dependency, no UI component source, no native UI project and no API definition — nothing here is a surface to boot — so runtime a11y/egress/header evidence has no subject here. Not applicable: this is neither a gap in the scan nor a finding about your code.
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- C1 Data Protection — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
- C2 Access Controls — No access-control surface detected in the analyzed source — no web/app surface to authorize (no HTTP API or web-UI project) and no authorization code at all (no [Authorize]/policies, no imperative guard methods). Access control is therefore N/A here — this is a library/CLI, which is authorized by its CALLER, not by itself. If this codebase grows request handlers, the dimension reactivates and a default-deny posture is expected then.
- C3 Audit Trail — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
- C4 Data Retention — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
- C5 Data-Subject Rights — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
- D10 Test Quality — ~4845 lines of test source are present (.fs) but no test cases reached the test census for this repository — no test root we could resolve declared them, or the files we read declare no cases in a test framework we recognise — so skipped/assertion-free tests couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
- D16 Bus Factor — single-maintainer repository — bus factor is not applicable
- D18 Solution Shape — D18 scores the shape of a C#/VB .NET solution, but this repository's production source is mostly .fs, which the C#/VB workspace does not load — the projects that loaded are an immaterial minority, so solution shape was not assessed for this repository. Not scored — this is a gap in the analyzer's reach, not a verdict about this repository.
- D21 Naming Consistency — Naming consistency is measured on C# and TypeScript only; F# not measured.
- D22 Internal API Consistency — No intentionally-exposed public API to evaluate for consistency.
- D23 Boundary Type-Coupling — small single-context codebase (13,346 production LoC in the .NET projects) — bounded contexts are not needed at this size 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 project 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.
- 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.
- D7 Architectural Integrity — no checkable ADRs and no dependency cycles — architectural integrity not assessed
- D9 Test Distribution — Test source is present (.fs) but no test cases reached the test census for this repository — no test root we could resolve declared them, or the files we read declare no cases in a test framework we recognise — so its unit/integration/BDD/E2E split couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
- DM1 Domain Modelling — applicable but not scored (2 of 3 signals for this style — below the bar we score at): 307 value object(s); 1 domain event(s); its domain events are published by services or handlers — no domain entity raises one
- ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
- ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
- P2 Observability — This repo is a library, not a deployed service — it has no process to operate, so production observability (structured logging, tracing/metrics, health checks) is N/A. A library may log via an injected ILogger, but the absence of operational telemetry is not a defect here. If it grows a host (web API, worker), the dimension reactivates.
- P7 Outbound HTTP resilience — not applicable — this isn't a service/API/worker
- P8 Schema migrations — no EF Core usage detected
- P9 Domain vs controller coverage — coverage data present for 42 file(s), but no domain-layer files were identified: no covered file's path contains any of the markers this check keys on (/domain/, /aggregates/, /valueobjects/, /domainmodel/, .domain/, /entities/), which are matched case-insensitively anywhere in the path. With no domain partition there is nothing to compare the web/controller layer against — if this repository keeps its business rules under a folder named none of those, that naming is what the check cannot see, not the domain logic.
- PF1 Benchmark discipline — Performance is assessed only for perf-relevant repos — a packaged library, one that ships benchmarks, or one already using allocation-aware APIs. This repo isn't one, so the Performance lens is not applicable and is excluded from the score.
- 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 — No web surface detected in the analyzed source — no HTTP API or web-UI project (no controllers/minimal-API endpoints, no Razor/Blazor views) and no web middleware (HTTPS redirection, HSTS, security headers, cookies). Transport security, security headers, secure cookies, CSRF/input-validation and middleware-order controls are therefore N/A here — this is a library/CLI/worker, not a web app. Crypto hygiene was still checked and found nothing to flag. If this codebase becomes web-facing, the dimension reactivates automatically.
- X1 Async correctness — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X10 Duplicated predicate — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X13 Undrained process stream — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X14 Bypassable address classification — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X17 Uncapped recursion over a caller-supplied document — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X18 Disposal-pattern correctness — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X19 Unrestored process-global state — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X2 Cancellation propagation — no async method does work a token could cancel
- 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 — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X22 Contradicted release guard — 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 — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X25 Inert configuration knob — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X26 Unsynchronised callback handoff — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- 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
- X29 Per-element action decided by a fixed element — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X3 Exception handling — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X30 Support guard that admits what it rejects — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X32 Type resolved by simple name across every loaded assembly — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X4 Structured logging — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X7 Silent fallback defaults — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
Critical — 10 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
Serious — 50 finding(s)
- FileTooLong: LanguageServerProtocol/Types.fs LanguageServerProtocol/Types.fs
- FileTooLong: Marksman/Server.fs Marksman/Server.fs
- FileTooLong: Marksman/Compl.fs Marksman/Compl.fs
- FileTooLong: Marksman/Conn.fs Marksman/Conn.fs
- FileTooLong: Marksman/Folder.fs Marksman/Folder.fs
- CommentedOutCode MarkdigPatches/PatchedLinkInlineParser.cs:67
- CommentedOutCode MarkdigPatches/PatchedLinkInlineParser.cs:78
- CommentedOutCode MarkdigPatches/PatchedLinkInlineParser.cs:143
- CommentedOutCode MarkdigPatches/PatchedLinkInlineParser.cs:150
- REDACTED
- REDACTED
- TooManyMethods: LspServer LanguageServerProtocol/Server.fs:390
- TooManyMethods: LspClient LanguageServerProtocol/Client.fs:140
- REDACTED
- REDACTED
- PartialElementModule.linkInLine (cyclomatic 31) Marksman/Compl.fs:53
- PromptModule.ofCompletable (cyclomatic 25) Marksman/Compl.fs:278
- Markdown.scrapeText (cyclomatic 25) Marksman/Parser.fs:223
- ElementModule.toSym (cyclomatic 24) Marksman/Ast.fs:113
- WikiLinkParser.Match (cyclomatic 21) Marksman/Parser.fs:83
- PatchedLinkInlineParser.TryProcessLinkOrImage (cyclomatic 19) MarkdigPatches/PatchedLinkInlineParser.cs:227
- Paths.systemPathToUriString (cyclomatic 19) Marksman/Paths.fs:13
- Deprecated: xunit Tests/Tests.fsproj:46
- Hotspot: Benchmarks/ConnectionUpdates.fs Benchmarks/ConnectionUpdates.fs:37
- Markdown.scrapeText (cognitive 61) Marksman/Parser.fs:223
- CodeActions.tableOfContentsInner (cognitive 39) Marksman/CodeActions.fs:39
- Diag.checkLink (cognitive 33) Marksman/Diag.fs:53
- ElementModule.toSym (cognitive 32) Marksman/Ast.fs:113
- PatchedLinkInlineParser.TryProcessLinkOrImage (cognitive 31) MarkdigPatches/PatchedLinkInlineParser.cs:227
- Refactor.renameHeadingLink (cognitive 26) Marksman/Refactor.fs:82
- Refactor.rename (cognitive 26) Marksman/Refactor.fs:184
- PartialElementModule.linkInLine (cognitive 25) Marksman/Compl.fs:53
- Conn.CompactFormat (cognitive 24) Marksman/Conn.fs:255
- LineMap.TryFindPosition (cognitive 23) Marksman/Text.fs:22
- PatchedLinkInlineParser.Match (cognitive 20) MarkdigPatches/PatchedLinkInlineParser.cs:29
- Text.LineContentOffsets (cognitive 19) Marksman/Text.fs:118
- ErasedUnionConverter.ReadJson (cognitive 18) LanguageServerProtocol/JsonUtils.fs:216
- PromptModule.ofCompletable (cognitive 17) Marksman/Compl.fs:278
- InternNameModule.tryAsPath (cognitive 16) Marksman/Names.fs:109
- Misc.String.Slug (cognitive 16) Marksman/Misc.fs:50
- TooManyFunctions: Misc Marksman/Misc.fs:1
- MethodTooLong: PatchedLinkInlineParser.TryProcessLinkOrImage MarkdigPatches/PatchedLinkInlineParser.cs:227
- REDACTED
- Duplicated block (11–13 lines × 2) LanguageServerProtocol/LanguageServerProtocol.fs:526
- Duplicated block (13 lines × 2) Marksman/Compl.fs:569
- Duplicated block (7–10 lines × 2) Marksman/Compl.fs:79
- Duplicated block (10 lines × 2) Marksman/Conn.fs:268
- Duplicated block (8 lines × 2) MarkdigPatches/PatchedLinkInlineParser.cs:278
- Duplicated block (10 lines × 3) Marksman/Conn.fs:263
- NuGet dependencies are not locked
Minor — 19 finding(s)
- Commented-out code MarkdigPatches/PatchedLinkInlineParser.cs:69
- Commented-out code MarkdigPatches/PatchedLinkInlineParser.cs:80
- Commented-out code MarkdigPatches/PatchedLinkInlineParser.cs:145
- Commented-out code MarkdigPatches/PatchedLinkInlineParser.cs:152
- Commented-out code MarkdigPatches/PatchedLinkInlineParser.cs:368
- Outdated: coverlet.collector Tests/Tests.fsproj:51
- No ADRs found
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- IL efficiency: 10 authored method(s) exceed the IL budget Marksman/Parser.fs:224
- No ADRs
- No architecture diagram/doc
- No SAST REDACTED:4
- No dependency-update automation Benchmarks/Benchmarks.fsproj:15
- No changelog
- Null-forgiving operator (`!`) suppressions override nullable warnings
Minor — 11 finding(s)
- Outdated: FSharp.Core
- Outdated: FSharp.SystemCommandLine
- Outdated: FSharpPlus
- Outdated: Markdig
- Outdated: Serilog
- Outdated: Serilog.Sinks.Console
- Outdated: Tomlyn
- Outdated: Microsoft.NET.Test.Sdk
- Outdated: xunit.runner.visualstudio
- Outdated: StreamJsonRpc
- Outdated: BenchmarkDotNet
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-97f8dd0f2eaf4c64a9c2993af776917b/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-97f8dd0f2eaf4c64a9c2993af776917b/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 . | 11 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | dotnet | — | dotnet list Marksman.sln package --vulnerable --include-transitive --format json | 1 | 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 | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . /tmp/codehealth-osv-sbom-e832cae7d460402a858f6577222b7fbd | 0 | artifacts/raw/osv-scanner.json |