Executive summary
dev-cycles/contextive falls short of our standard for production, in part because it has packages with a known security hole. It scores 61 out of 100 and is rated Adequate, and 92 of its 95 critical findings are security problems in the packages it uses and in the build pipeline.
Security and Compliance, at 50, is the weakest lens and counts most in the score. The best first step is fixing the test command with no tests behind it, worth about 5 points. Adding a reporting contact to the security policy comes next, worth about 3 points. Raising Security and Compliance to 70 would lift the score to about 67.
Fifty-two known security holes in the packages the code depends on can be used by attackers. Thirty-two pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Updating the vulnerable packages and pinning each tool to an exact version would close both risks. Passing outside input through environment variables would fix the eight pipeline steps that put outside input straight into a shell command. The two sets of files in separate parts that keep changing together need that dependency made explicit.
The product code is 2,658 lines, about €6,200 to rebuild.
If Security and Compliance rose from 50 to 70, the lowest score rated Strong, the score would rise from 61 to about 67.
New since the last survey: 18 findings
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
Fixed since the last survey: 14 findings
- Dependency Vulnerabilities · High CVE: REDACTED REDACTED
- Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · High CVE: REDACTED REDACTED
- Dependency Vulnerabilities · High CVE: REDACTED REDACTED
- Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · High CVE: REDACTED REDACTED
- Dependency Vulnerabilities · High CVE: REDACTED REDACTED
- Dependency Vulnerabilities · High CVE: REDACTED REDACTED
- Dependency Vulnerabilities · High CVE: REDACTED REDACTED
- Dependency Vulnerabilities · High CVE: REDACTED REDACTED
- Dependency Vulnerabilities · High CVE: REDACTED REDACTED
- Dependency Vulnerabilities · Medium CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · Medium CVE: [GHSA redacted] REDACTED
- Change Coupling · Boundary-crossing change coupling: common.fsx ↔ build.fsx src/ci/common.fsx
Rebuild cost: about €6,200 · Estimate
| Cost to rebuild | €2,100 to €10,000, for 35 to 110 hours of work, under 0.1 person-years for one engineer |
|---|---|
| Difficulty of the problem | Low, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.8 at a score of 61. 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: 2,658 lines of product code |
| Comment lines | The estimate prices 2,655 lines. Comment lines count towards the size of 2,658 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 — bounded-context dependency graph
Architecture: which parts of the code depend on which
| uses → | 1 Contextive.Core.File | 2 Contextive.LanguageServer.GlossaryFileInitializer.Models | 3 Contextive.LanguageServer.Logger | 4 Contextive.Core.GlossaryFile | 5 Contextive.LanguageServer.DefaultGlossaryFileProvider | 6 Contextive.LanguageServer.FileReader | 7 Contextive.LanguageServer.FileScanner | 8 Contextive.LanguageServer.LocalFileReader | 9 Fable.Import.VSCode | 10 Fable.Import.VSCode.Vscode.Comments | 11 Fable.Import.VSCode.Vscode.Extensions | 12 Fable.Import.VSCode.Vscode.Notebooks | 13 Fable.Import.VSCode.Vscode.Scm | 14 Fable.Import.VSCode.Vscode.Tests | 15 Contextive.Core.GlossaryFile.ContextModule | 16 Contextive.Core.GlossaryFile.GlossaryFileModule | 17 Contextive.Core.GlossaryFile.TermModule | 18 Contextive.LanguageServer.Completion | 19 Contextive.LanguageServer.Globs | 20 Contextive.LanguageServer.Glossary | 21 Contextive.LanguageServer.GlossaryFileInitializer | 22 Contextive.LanguageServer.Hover | 23 Contextive.LanguageServer.Hover.Filtering | 24 Fable.Import.VSCode.Vscode.Authentication | 25 Fable.Import.VSCode.Vscode.Commands | 26 Fable.Import.VSCode.Vscode.Debug | 27 Fable.Import.VSCode.Vscode.Env | 28 Fable.Import.VSCode.Vscode.Languages | 29 Fable.Import.VSCode.Vscode.Tasks | 30 Fable.Import.VSCode.Vscode.Window | 31 Fable.Import.VSCode.Vscode.Workspace | 32 Contextive.LanguageServer.Glossary.Handlers | 33 Contextive.LanguageServer.GlossaryManager | 34 Fable.Import.VSCode.Vscode | 35 Contextive.LanguageServer.GlossaryManager.Handlers | 36 Fable.Import.LanguageServer.Client | 37 Contextive.VsCodeExtension.Middleware | 38 Fable.Import.LanguageServer | 39 Contextive.VsCodeExtension.Extension | 40 Contextive.VsCodeExtension.MultiRoot |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 Contextive.Core.File | ||||||||||||||||||||||||||||||||||||||||
| 2 Contextive.LanguageServer.GlossaryFileInitializer.Models | ||||||||||||||||||||||||||||||||||||||||
| 3 Contextive.LanguageServer.Logger | ||||||||||||||||||||||||||||||||||||||||
| 4 Contextive.Core.GlossaryFile | 1 | |||||||||||||||||||||||||||||||||||||||
| 5 Contextive.LanguageServer.DefaultGlossaryFileProvider | 1 | |||||||||||||||||||||||||||||||||||||||
| 6 Contextive.LanguageServer.FileReader | 2 | |||||||||||||||||||||||||||||||||||||||
| 7 Contextive.LanguageServer.FileScanner | 1 | |||||||||||||||||||||||||||||||||||||||
| 8 Contextive.LanguageServer.LocalFileReader | 2 | |||||||||||||||||||||||||||||||||||||||
| 9 Fable.Import.VSCode | 1 | |||||||||||||||||||||||||||||||||||||||
| 10 Fable.Import.VSCode.Vscode.Comments | 1 | |||||||||||||||||||||||||||||||||||||||
| 11 Fable.Import.VSCode.Vscode.Extensions | 2 | |||||||||||||||||||||||||||||||||||||||
| 12 Fable.Import.VSCode.Vscode.Notebooks | 4 | |||||||||||||||||||||||||||||||||||||||
| 13 Fable.Import.VSCode.Vscode.Scm | 3 | |||||||||||||||||||||||||||||||||||||||
| 14 Fable.Import.VSCode.Vscode.Tests | 1 | |||||||||||||||||||||||||||||||||||||||
| 15 Contextive.Core.GlossaryFile.ContextModule | 2 | |||||||||||||||||||||||||||||||||||||||
| 16 Contextive.Core.GlossaryFile.GlossaryFileModule | 1 | |||||||||||||||||||||||||||||||||||||||
| 17 Contextive.Core.GlossaryFile.TermModule | 1 | |||||||||||||||||||||||||||||||||||||||
| 18 Contextive.LanguageServer.Completion | 2 | |||||||||||||||||||||||||||||||||||||||
| 19 Contextive.LanguageServer.Globs | 1 | |||||||||||||||||||||||||||||||||||||||
| 20 Contextive.LanguageServer.Glossary | 3 | 2 | 3 | |||||||||||||||||||||||||||||||||||||
| 21 Contextive.LanguageServer.GlossaryFileInitializer | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 22 Contextive.LanguageServer.Hover | 1 | |||||||||||||||||||||||||||||||||||||||
| 23 Contextive.LanguageServer.Hover.Filtering | 2 | |||||||||||||||||||||||||||||||||||||||
| 24 Fable.Import.VSCode.Vscode.Authentication | 1 | 7 | ||||||||||||||||||||||||||||||||||||||
| 25 Fable.Import.VSCode.Vscode.Commands | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 26 Fable.Import.VSCode.Vscode.Debug | 1 | 16 | ||||||||||||||||||||||||||||||||||||||
| 27 Fable.Import.VSCode.Vscode.Env | 1 | 4 | ||||||||||||||||||||||||||||||||||||||
| 28 Fable.Import.VSCode.Vscode.Languages | 1 | 50 | ||||||||||||||||||||||||||||||||||||||
| 29 Fable.Import.VSCode.Vscode.Tasks | 1 | 10 | ||||||||||||||||||||||||||||||||||||||
| 30 Fable.Import.VSCode.Vscode.Window | 1 | 47 | ||||||||||||||||||||||||||||||||||||||
| 31 Fable.Import.VSCode.Vscode.Workspace | 1 | 29 | ||||||||||||||||||||||||||||||||||||||
| 32 Contextive.LanguageServer.Glossary.Handlers | 1 | 3 | ||||||||||||||||||||||||||||||||||||||
| 33 Contextive.LanguageServer.GlossaryManager | 2 | 2 | 1 | |||||||||||||||||||||||||||||||||||||
| 34 Fable.Import.VSCode.Vscode | 72 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||
| 35 Contextive.LanguageServer.GlossaryManager.Handlers | 5 | |||||||||||||||||||||||||||||||||||||||
| 36 Fable.Import.LanguageServer.Client | 13 | |||||||||||||||||||||||||||||||||||||||
| 37 Contextive.VsCodeExtension.Middleware | 1 | |||||||||||||||||||||||||||||||||||||||
| 38 Fable.Import.LanguageServer | 4 | 4 | ||||||||||||||||||||||||||||||||||||||
| 39 Contextive.VsCodeExtension.Extension | 2 | 1 | 5 | |||||||||||||||||||||||||||||||||||||
| 40 Contextive.VsCodeExtension.MultiRoot | 1 | 3 |
4→1 Contextive.Core.GlossaryFile uses Contextive.Core.File✕
- Connections
- 1 pair of types, where a type in Contextive.Core.GlossaryFile uses a type in Contextive.Core.File.
- The types involved
Contextive.Core.GlossaryFile.GlossaryFile→Contextive.Core.File.FileError
- Direction
- Contextive.Core.GlossaryFile uses Contextive.Core.File, so a change to Contextive.Core.File can break Contextive.Core.GlossaryFile, while a change to Contextive.Core.GlossaryFile can't break Contextive.Core.File.
- Position
- Below the diagonal: Contextive.Core.GlossaryFile uses a module listed above it, which is the healthy direction.
5→1 Contextive.LanguageServer.DefaultGlossaryFileProvider uses Contextive.Core.File✕
- Connections
- 1 pair of types, where a type in Contextive.LanguageServer.DefaultGlossaryFileProvider uses a type in Contextive.Core.File.
- The types involved
Contextive.LanguageServer.DefaultGlossaryFileProvider.DefaultGlossaryFileProvider→Contextive.Core.File.PathConfiguration
- Direction
- Contextive.LanguageServer.DefaultGlossaryFileProvider uses Contextive.Core.File, so a change to Contextive.Core.File can break Contextive.LanguageServer.DefaultGlossaryFileProvider, while a change to Contextive.LanguageServer.DefaultGlossaryFileProvider can't break Contextive.Core.File.
- Position
- Below the diagonal: Contextive.LanguageServer.DefaultGlossaryFileProvider uses a module listed above it, which is the healthy direction.
6→1 Contextive.LanguageServer.FileReader uses Contextive.Core.File✕
- Connections
- 2 pairs of types, where a type in Contextive.LanguageServer.FileReader uses a type in Contextive.Core.File.
- The types involved
Contextive.LanguageServer.FileReader.FileReader→Contextive.Core.File.FileErrorContextive.LanguageServer.FileReader.FileReader→Contextive.Core.File.PathConfiguration
- Direction
- Contextive.LanguageServer.FileReader uses Contextive.Core.File, so a change to Contextive.Core.File can break Contextive.LanguageServer.FileReader, while a change to Contextive.LanguageServer.FileReader can't break Contextive.Core.File.
- Position
- Below the diagonal: Contextive.LanguageServer.FileReader uses a module listed above it, which is the healthy direction.
7→3 Contextive.LanguageServer.FileScanner uses Contextive.LanguageServer.Logger✕
- Connections
- 1 pair of types, where a type in Contextive.LanguageServer.FileScanner uses a type in Contextive.LanguageServer.Logger.
- The types involved
Contextive.LanguageServer.FileScanner.FileScanner→Contextive.LanguageServer.Logger.Logger
- Direction
- Contextive.LanguageServer.FileScanner uses Contextive.LanguageServer.Logger, so a change to Contextive.LanguageServer.Logger can break Contextive.LanguageServer.FileScanner, while a change to Contextive.LanguageServer.FileScanner can't break Contextive.LanguageServer.Logger.
- Position
- Below the diagonal: Contextive.LanguageServer.FileScanner uses a module listed above it, which is the healthy direction.
8→1 Contextive.LanguageServer.LocalFileReader uses Contextive.Core.File✕
- Connections
- 2 pairs of types, where a type in Contextive.LanguageServer.LocalFileReader uses a type in Contextive.Core.File.
- The types involved
Contextive.LanguageServer.LocalFileReader.LocalFileReader→Contextive.Core.File.FileErrorContextive.LanguageServer.LocalFileReader.LocalFileReader→Contextive.Core.File.PathConfiguration
- Direction
- Contextive.LanguageServer.LocalFileReader uses Contextive.Core.File, so a change to Contextive.Core.File can break Contextive.LanguageServer.LocalFileReader, while a change to Contextive.LanguageServer.LocalFileReader can't break Contextive.Core.File.
- Position
- Below the diagonal: Contextive.LanguageServer.LocalFileReader uses a module listed above it, which is the healthy direction.
9→34 Fable.Import.VSCode uses Fable.Import.VSCode.Vscode part of a loop✕
- Connections
- 1 pair of types, where a type in Fable.Import.VSCode uses a type in Fable.Import.VSCode.Vscode.
- The types involved
Fable.Import.VSCode.VSCode→Fable.Import.VSCode.Vscode.IExports
- Direction
- Fable.Import.VSCode uses Fable.Import.VSCode.Vscode, so a change to Fable.Import.VSCode.Vscode can break Fable.Import.VSCode, while a change to Fable.Import.VSCode can't break Fable.Import.VSCode.Vscode.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
10→34 Fable.Import.VSCode.Vscode.Comments uses Fable.Import.VSCode.Vscode part of a loop✕
- Connections
- 1 pair of types, where a type in Fable.Import.VSCode.Vscode.Comments uses a type in Fable.Import.VSCode.Vscode.
- The types involved
Fable.Import.VSCode.Vscode.Comments.IExports→Fable.Import.VSCode.Vscode.CommentController
- Direction
- Fable.Import.VSCode.Vscode.Comments uses Fable.Import.VSCode.Vscode, so a change to Fable.Import.VSCode.Vscode can break Fable.Import.VSCode.Vscode.Comments, while a change to Fable.Import.VSCode.Vscode.Comments can't break Fable.Import.VSCode.Vscode.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
11→34 Fable.Import.VSCode.Vscode.Extensions uses Fable.Import.VSCode.Vscode part of a loop✕
- Connections
- 2 pairs of types, where a type in Fable.Import.VSCode.Vscode.Extensions uses a type in Fable.Import.VSCode.Vscode.
- The types involved
Fable.Import.VSCode.Vscode.Extensions.IExports→Fable.Import.VSCode.Vscode.Event`1Fable.Import.VSCode.Vscode.Extensions.IExports→Fable.Import.VSCode.Vscode.Extension`1
- Direction
- Fable.Import.VSCode.Vscode.Extensions uses Fable.Import.VSCode.Vscode, so a change to Fable.Import.VSCode.Vscode can break Fable.Import.VSCode.Vscode.Extensions, while a change to Fable.Import.VSCode.Vscode.Extensions can't break Fable.Import.VSCode.Vscode.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
12→34 Fable.Import.VSCode.Vscode.Notebooks uses Fable.Import.VSCode.Vscode part of a loop✕
- Connections
- 4 pairs of types, where a type in Fable.Import.VSCode.Vscode.Notebooks uses a type in Fable.Import.VSCode.Vscode.
- The types involved
Fable.Import.VSCode.Vscode.Notebooks.IExports→Fable.Import.VSCode.Vscode.DisposableFable.Import.VSCode.Vscode.Notebooks.IExports→Fable.Import.VSCode.Vscode.NotebookCellStatusBarItemProviderFable.Import.VSCode.Vscode.Notebooks.IExports→Fable.Import.VSCode.Vscode.NotebookControllerFable.Import.VSCode.Vscode.Notebooks.IExports→Fable.Import.VSCode.Vscode.NotebookRendererMessaging
- Direction
- Fable.Import.VSCode.Vscode.Notebooks uses Fable.Import.VSCode.Vscode, so a change to Fable.Import.VSCode.Vscode can break Fable.Import.VSCode.Vscode.Notebooks, while a change to Fable.Import.VSCode.Vscode.Notebooks can't break Fable.Import.VSCode.Vscode.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
13→34 Fable.Import.VSCode.Vscode.Scm uses Fable.Import.VSCode.Vscode part of a loop✕
- Connections
- 3 pairs of types, where a type in Fable.Import.VSCode.Vscode.Scm uses a type in Fable.Import.VSCode.Vscode.
- The types involved
Fable.Import.VSCode.Vscode.Scm.IExports→Fable.Import.VSCode.Vscode.SourceControlFable.Import.VSCode.Vscode.Scm.IExports→Fable.Import.VSCode.Vscode.SourceControlInputBoxFable.Import.VSCode.Vscode.Scm.IExports→Fable.Import.VSCode.Vscode.Uri
- Direction
- Fable.Import.VSCode.Vscode.Scm uses Fable.Import.VSCode.Vscode, so a change to Fable.Import.VSCode.Vscode can break Fable.Import.VSCode.Vscode.Scm, while a change to Fable.Import.VSCode.Vscode.Scm can't break Fable.Import.VSCode.Vscode.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
14→34 Fable.Import.VSCode.Vscode.Tests uses Fable.Import.VSCode.Vscode part of a loop✕
- Connections
- 1 pair of types, where a type in Fable.Import.VSCode.Vscode.Tests uses a type in Fable.Import.VSCode.Vscode.
- The types involved
Fable.Import.VSCode.Vscode.Tests.IExports→Fable.Import.VSCode.Vscode.TestController
- Direction
- Fable.Import.VSCode.Vscode.Tests uses Fable.Import.VSCode.Vscode, so a change to Fable.Import.VSCode.Vscode can break Fable.Import.VSCode.Vscode.Tests, while a change to Fable.Import.VSCode.Vscode.Tests can't break Fable.Import.VSCode.Vscode.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
15→4 Contextive.Core.GlossaryFile.ContextModule uses Contextive.Core.GlossaryFile✕
- Connections
- 2 pairs of types, where a type in Contextive.Core.GlossaryFile.ContextModule uses a type in Contextive.Core.GlossaryFile.
- The types involved
Contextive.Core.GlossaryFile.ContextModule.ContextModule→Contextive.Core.GlossaryFile.ContextContextive.Core.GlossaryFile.ContextModule.ContextModule→Contextive.Core.GlossaryFile.Term
- Direction
- Contextive.Core.GlossaryFile.ContextModule uses Contextive.Core.GlossaryFile, so a change to Contextive.Core.GlossaryFile can break Contextive.Core.GlossaryFile.ContextModule, while a change to Contextive.Core.GlossaryFile.ContextModule can't break Contextive.Core.GlossaryFile.
- Position
- Below the diagonal: Contextive.Core.GlossaryFile.ContextModule uses a module listed above it, which is the healthy direction.
16→4 Contextive.Core.GlossaryFile.GlossaryFileModule uses Contextive.Core.GlossaryFile✕
- Connections
- 1 pair of types, where a type in Contextive.Core.GlossaryFile.GlossaryFileModule uses a type in Contextive.Core.GlossaryFile.
- The types involved
Contextive.Core.GlossaryFile.GlossaryFileModule.GlossaryFileModule→Contextive.Core.GlossaryFile.GlossaryFile
- Direction
- Contextive.Core.GlossaryFile.GlossaryFileModule uses Contextive.Core.GlossaryFile, so a change to Contextive.Core.GlossaryFile can break Contextive.Core.GlossaryFile.GlossaryFileModule, while a change to Contextive.Core.GlossaryFile.GlossaryFileModule can't break Contextive.Core.GlossaryFile.
- Position
- Below the diagonal: Contextive.Core.GlossaryFile.GlossaryFileModule uses a module listed above it, which is the healthy direction.
17→4 Contextive.Core.GlossaryFile.TermModule uses Contextive.Core.GlossaryFile✕
- Connections
- 1 pair of types, where a type in Contextive.Core.GlossaryFile.TermModule uses a type in Contextive.Core.GlossaryFile.
- The types involved
Contextive.Core.GlossaryFile.TermModule.TermModule→Contextive.Core.GlossaryFile.Term
- Direction
- Contextive.Core.GlossaryFile.TermModule uses Contextive.Core.GlossaryFile, so a change to Contextive.Core.GlossaryFile can break Contextive.Core.GlossaryFile.TermModule, while a change to Contextive.Core.GlossaryFile.TermModule can't break Contextive.Core.GlossaryFile.
- Position
- Below the diagonal: Contextive.Core.GlossaryFile.TermModule uses a module listed above it, which is the healthy direction.
18→4 Contextive.LanguageServer.Completion uses Contextive.Core.GlossaryFile✕
- Connections
- 2 pairs of types, where a type in Contextive.LanguageServer.Completion uses a type in Contextive.Core.GlossaryFile.
- The types involved
Contextive.LanguageServer.Completion.Completion→Contextive.Core.GlossaryFile.ContextContextive.LanguageServer.Completion.Completion→Contextive.Core.GlossaryFile.Term
- Direction
- Contextive.LanguageServer.Completion uses Contextive.Core.GlossaryFile, so a change to Contextive.Core.GlossaryFile can break Contextive.LanguageServer.Completion, while a change to Contextive.LanguageServer.Completion can't break Contextive.Core.GlossaryFile.
- Position
- Below the diagonal: Contextive.LanguageServer.Completion uses a module listed above it, which is the healthy direction.
19→4 Contextive.LanguageServer.Globs uses Contextive.Core.GlossaryFile✕
- Connections
- 1 pair of types, where a type in Contextive.LanguageServer.Globs uses a type in Contextive.Core.GlossaryFile.
- The types involved
Contextive.LanguageServer.Globs.Globs→Contextive.Core.GlossaryFile.Context
- Direction
- Contextive.LanguageServer.Globs uses Contextive.Core.GlossaryFile, so a change to Contextive.Core.GlossaryFile can break Contextive.LanguageServer.Globs, while a change to Contextive.LanguageServer.Globs can't break Contextive.Core.GlossaryFile.
- Position
- Below the diagonal: Contextive.LanguageServer.Globs uses a module listed above it, which is the healthy direction.
20→1 Contextive.LanguageServer.Glossary uses Contextive.Core.File✕
- Connections
- 3 pairs of types, where a type in Contextive.LanguageServer.Glossary uses a type in Contextive.Core.File.
- The types involved
Contextive.LanguageServer.Glossary.Glossary→Contextive.Core.File.FileErrorContextive.LanguageServer.Glossary.StartGlossary→Contextive.Core.File.PathConfigurationContextive.LanguageServer.Glossary.State→Contextive.Core.File.PathConfiguration
- Direction
- Contextive.LanguageServer.Glossary uses Contextive.Core.File, so a change to Contextive.Core.File can break Contextive.LanguageServer.Glossary, while a change to Contextive.LanguageServer.Glossary can't break Contextive.Core.File.
- Position
- Below the diagonal: Contextive.LanguageServer.Glossary uses a module listed above it, which is the healthy direction.
20→3 Contextive.LanguageServer.Glossary uses Contextive.LanguageServer.Logger✕
- Connections
- 2 pairs of types, where a type in Contextive.LanguageServer.Glossary uses a type in Contextive.LanguageServer.Logger.
- The types involved
Contextive.LanguageServer.Glossary.StartGlossary→Contextive.LanguageServer.Logger.LoggerContextive.LanguageServer.Glossary.State→Contextive.LanguageServer.Logger.Logger
- Direction
- Contextive.LanguageServer.Glossary uses Contextive.LanguageServer.Logger, so a change to Contextive.LanguageServer.Logger can break Contextive.LanguageServer.Glossary, while a change to Contextive.LanguageServer.Glossary can't break Contextive.LanguageServer.Logger.
- Position
- Below the diagonal: Contextive.LanguageServer.Glossary uses a module listed above it, which is the healthy direction.
20→4 Contextive.LanguageServer.Glossary uses Contextive.Core.GlossaryFile✕
- Connections
- 3 pairs of types, where a type in Contextive.LanguageServer.Glossary uses a type in Contextive.Core.GlossaryFile.
- The types involved
Contextive.LanguageServer.Glossary.Glossary→Contextive.Core.GlossaryFile.ContextContextive.LanguageServer.Glossary.Lookup→Contextive.Core.GlossaryFile.ContextContextive.LanguageServer.Glossary.State→Contextive.Core.GlossaryFile.GlossaryFile
- Direction
- Contextive.LanguageServer.Glossary uses Contextive.Core.GlossaryFile, so a change to Contextive.Core.GlossaryFile can break Contextive.LanguageServer.Glossary, while a change to Contextive.LanguageServer.Glossary can't break Contextive.Core.GlossaryFile.
- Position
- Below the diagonal: Contextive.LanguageServer.Glossary uses a module listed above it, which is the healthy direction.
21→2 Contextive.LanguageServer.GlossaryFileInitializer uses Contextive.LanguageServer.GlossaryFileInitializer.Models✕
- Connections
- 1 pair of types, where a type in Contextive.LanguageServer.GlossaryFileInitializer uses a type in Contextive.LanguageServer.GlossaryFileInitializer.Models.
- The types involved
Contextive.LanguageServer.GlossaryFileInitializer.GlossaryFileInitializer→Contextive.LanguageServer.GlossaryFileInitializer.Models.InitializeGlossaryFileResponse
- Direction
- Contextive.LanguageServer.GlossaryFileInitializer uses Contextive.LanguageServer.GlossaryFileInitializer.Models, so a change to Contextive.LanguageServer.GlossaryFileInitializer.Models can break Contextive.LanguageServer.GlossaryFileInitializer, while a change to Contextive.LanguageServer.GlossaryFileInitializer can't break Contextive.LanguageServer.GlossaryFileInitializer.Models.
- Position
- Below the diagonal: Contextive.LanguageServer.GlossaryFileInitializer uses a module listed above it, which is the healthy direction.
21→4 Contextive.LanguageServer.GlossaryFileInitializer uses Contextive.Core.GlossaryFile✕
- Connections
- 1 pair of types, where a type in Contextive.LanguageServer.GlossaryFileInitializer uses a type in Contextive.Core.GlossaryFile.
- The types involved
Contextive.LanguageServer.GlossaryFileInitializer.GlossaryFileInitializer→Contextive.Core.GlossaryFile.GlossaryFile
- Direction
- Contextive.LanguageServer.GlossaryFileInitializer uses Contextive.Core.GlossaryFile, so a change to Contextive.Core.GlossaryFile can break Contextive.LanguageServer.GlossaryFileInitializer, while a change to Contextive.LanguageServer.GlossaryFileInitializer can't break Contextive.Core.GlossaryFile.
- Position
- Below the diagonal: Contextive.LanguageServer.GlossaryFileInitializer uses a module listed above it, which is the healthy direction.
22→4 Contextive.LanguageServer.Hover uses Contextive.Core.GlossaryFile✕
- Connections
- 1 pair of types, where a type in Contextive.LanguageServer.Hover uses a type in Contextive.Core.GlossaryFile.
- The types involved
Contextive.LanguageServer.Hover.Hover→Contextive.Core.GlossaryFile.Context
- Direction
- Contextive.LanguageServer.Hover uses Contextive.Core.GlossaryFile, so a change to Contextive.Core.GlossaryFile can break Contextive.LanguageServer.Hover, while a change to Contextive.LanguageServer.Hover can't break Contextive.Core.GlossaryFile.
- Position
- Below the diagonal: Contextive.LanguageServer.Hover uses a module listed above it, which is the healthy direction.
23→4 Contextive.LanguageServer.Hover.Filtering uses Contextive.Core.GlossaryFile✕
- Connections
- 2 pairs of types, where a type in Contextive.LanguageServer.Hover.Filtering uses a type in Contextive.Core.GlossaryFile.
- The types involved
Contextive.LanguageServer.Hover.Filtering.Filtering→Contextive.Core.GlossaryFile.ContextContextive.LanguageServer.Hover.Filtering.Filtering→Contextive.Core.GlossaryFile.Term
- Direction
- Contextive.LanguageServer.Hover.Filtering uses Contextive.Core.GlossaryFile, so a change to Contextive.Core.GlossaryFile can break Contextive.LanguageServer.Hover.Filtering, while a change to Contextive.LanguageServer.Hover.Filtering can't break Contextive.Core.GlossaryFile.
- Position
- Below the diagonal: Contextive.LanguageServer.Hover.Filtering uses a module listed above it, which is the healthy direction.
24→9 Fable.Import.VSCode.Vscode.Authentication uses Fable.Import.VSCode✕
- Connections
- 1 pair of types, where a type in Fable.Import.VSCode.Vscode.Authentication uses a type in Fable.Import.VSCode.
- The types involved
Fable.Import.VSCode.Vscode.Authentication.IExports→Fable.Import.VSCode.Thenable`1
- Direction
- Fable.Import.VSCode.Vscode.Authentication uses Fable.Import.VSCode, so a change to Fable.Import.VSCode can break Fable.Import.VSCode.Vscode.Authentication, while a change to Fable.Import.VSCode.Vscode.Authentication can't break Fable.Import.VSCode.
- Position
- Below the diagonal: Fable.Import.VSCode.Vscode.Authentication uses a module listed above it, which is the healthy direction.
24→34 Fable.Import.VSCode.Vscode.Authentication uses Fable.Import.VSCode.Vscode part of a loop✕
- Connections
- 7 pairs of types, where a type in Fable.Import.VSCode.Vscode.Authentication uses a type in Fable.Import.VSCode.Vscode.
- The types involved
Fable.Import.VSCode.Vscode.Authentication.IExports→Fable.Import.VSCode.Vscode.AuthenticationGetSessionOptionsFable.Import.VSCode.Vscode.Authentication.IExports→Fable.Import.VSCode.Vscode.AuthenticationProviderFable.Import.VSCode.Vscode.Authentication.IExports→Fable.Import.VSCode.Vscode.AuthenticationProviderOptionsFable.Import.VSCode.Vscode.Authentication.IExports→Fable.Import.VSCode.Vscode.AuthenticationSessionFable.Import.VSCode.Vscode.Authentication.IExports→Fable.Import.VSCode.Vscode.AuthenticationSessionsChangeEventFable.Import.VSCode.Vscode.Authentication.IExports→Fable.Import.VSCode.Vscode.DisposableFable.Import.VSCode.Vscode.Authentication.IExports→Fable.Import.VSCode.Vscode.Event`1
- Direction
- Fable.Import.VSCode.Vscode.Authentication uses Fable.Import.VSCode.Vscode, so a change to Fable.Import.VSCode.Vscode can break Fable.Import.VSCode.Vscode.Authentication, while a change to Fable.Import.VSCode.Vscode.Authentication can't break Fable.Import.VSCode.Vscode.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
25→9 Fable.Import.VSCode.Vscode.Commands uses Fable.Import.VSCode✕
- Connections
- 1 pair of types, where a type in Fable.Import.VSCode.Vscode.Commands uses a type in Fable.Import.VSCode.
- The types involved
Fable.Import.VSCode.Vscode.Commands.IExports→Fable.Import.VSCode.Thenable`1
- Direction
- Fable.Import.VSCode.Vscode.Commands uses Fable.Import.VSCode, so a change to Fable.Import.VSCode can break Fable.Import.VSCode.Vscode.Commands, while a change to Fable.Import.VSCode.Vscode.Commands can't break Fable.Import.VSCode.
- Position
- Below the diagonal: Fable.Import.VSCode.Vscode.Commands uses a module listed above it, which is the healthy direction.
25→34 Fable.Import.VSCode.Vscode.Commands uses Fable.Import.VSCode.Vscode part of a loop✕
- Connections
- 1 pair of types, where a type in Fable.Import.VSCode.Vscode.Commands uses a type in Fable.Import.VSCode.Vscode.
- The types involved
Fable.Import.VSCode.Vscode.Commands.IExports→Fable.Import.VSCode.Vscode.Disposable
- Direction
- Fable.Import.VSCode.Vscode.Commands uses Fable.Import.VSCode.Vscode, so a change to Fable.Import.VSCode.Vscode can break Fable.Import.VSCode.Vscode.Commands, while a change to Fable.Import.VSCode.Vscode.Commands can't break Fable.Import.VSCode.Vscode.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
26→9 Fable.Import.VSCode.Vscode.Debug uses Fable.Import.VSCode✕
- Connections
- 1 pair of types, where a type in Fable.Import.VSCode.Vscode.Debug uses a type in Fable.Import.VSCode.
- The types involved
Fable.Import.VSCode.Vscode.Debug.IExports→Fable.Import.VSCode.Thenable`1
- Direction
- Fable.Import.VSCode.Vscode.Debug uses Fable.Import.VSCode, so a change to Fable.Import.VSCode can break Fable.Import.VSCode.Vscode.Debug, while a change to Fable.Import.VSCode.Vscode.Debug can't break Fable.Import.VSCode.
- Position
- Below the diagonal: Fable.Import.VSCode.Vscode.Debug uses a module listed above it, which is the healthy direction.
26→34 Fable.Import.VSCode.Vscode.Debug uses Fable.Import.VSCode.Vscode part of a loop✕
- Connections
- 16 pairs of types, where a type in Fable.Import.VSCode.Vscode.Debug uses a type in Fable.Import.VSCode.Vscode.
- The types involved
Fable.Import.VSCode.Vscode.Debug.IExports→Fable.Import.VSCode.Vscode.BreakpointFable.Import.VSCode.Vscode.Debug.IExports→Fable.Import.VSCode.Vscode.BreakpointsChangeEventFable.Import.VSCode.Vscode.Debug.IExports→Fable.Import.VSCode.Vscode.DebugAdapterDescriptorFactoryFable.Import.VSCode.Vscode.Debug.IExports→Fable.Import.VSCode.Vscode.DebugAdapterTrackerFactoryFable.Import.VSCode.Vscode.Debug.IExports→Fable.Import.VSCode.Vscode.DebugConfigurationFable.Import.VSCode.Vscode.Debug.IExports→Fable.Import.VSCode.Vscode.DebugConfigurationProviderFable.Import.VSCode.Vscode.Debug.IExports→Fable.Import.VSCode.Vscode.DebugConfigurationProviderTriggerKindFable.Import.VSCode.Vscode.Debug.IExports→Fable.Import.VSCode.Vscode.DebugConsoleFable.Import.VSCode.Vscode.Debug.IExports→Fable.Import.VSCode.Vscode.DebugProtocolSourceFable.Import.VSCode.Vscode.Debug.IExports→Fable.Import.VSCode.Vscode.DebugSessionFable.Import.VSCode.Vscode.Debug.IExports→Fable.Import.VSCode.Vscode.DebugSessionCustomEventFable.Import.VSCode.Vscode.Debug.IExports→Fable.Import.VSCode.Vscode.DebugSessionOptionsFable.Import.VSCode.Vscode.Debug.IExports→Fable.Import.VSCode.Vscode.DisposableFable.Import.VSCode.Vscode.Debug.IExports→Fable.Import.VSCode.Vscode.Event`1Fable.Import.VSCode.Vscode.Debug.IExports→Fable.Import.VSCode.Vscode.UriFable.Import.VSCode.Vscode.Debug.IExports→Fable.Import.VSCode.Vscode.WorkspaceFolder
- Direction
- Fable.Import.VSCode.Vscode.Debug uses Fable.Import.VSCode.Vscode, so a change to Fable.Import.VSCode.Vscode can break Fable.Import.VSCode.Vscode.Debug, while a change to Fable.Import.VSCode.Vscode.Debug can't break Fable.Import.VSCode.Vscode.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
27→9 Fable.Import.VSCode.Vscode.Env uses Fable.Import.VSCode✕
- Connections
- 1 pair of types, where a type in Fable.Import.VSCode.Vscode.Env uses a type in Fable.Import.VSCode.
- The types involved
Fable.Import.VSCode.Vscode.Env.IExports→Fable.Import.VSCode.Thenable`1
- Direction
- Fable.Import.VSCode.Vscode.Env uses Fable.Import.VSCode, so a change to Fable.Import.VSCode can break Fable.Import.VSCode.Vscode.Env, while a change to Fable.Import.VSCode.Vscode.Env can't break Fable.Import.VSCode.
- Position
- Below the diagonal: Fable.Import.VSCode.Vscode.Env uses a module listed above it, which is the healthy direction.
27→34 Fable.Import.VSCode.Vscode.Env uses Fable.Import.VSCode.Vscode part of a loop✕
- Connections
- 4 pairs of types, where a type in Fable.Import.VSCode.Vscode.Env uses a type in Fable.Import.VSCode.Vscode.
- The types involved
Fable.Import.VSCode.Vscode.Env.IExports→Fable.Import.VSCode.Vscode.ClipboardFable.Import.VSCode.Vscode.Env.IExports→Fable.Import.VSCode.Vscode.Event`1Fable.Import.VSCode.Vscode.Env.IExports→Fable.Import.VSCode.Vscode.UIKindFable.Import.VSCode.Vscode.Env.IExports→Fable.Import.VSCode.Vscode.Uri
- Direction
- Fable.Import.VSCode.Vscode.Env uses Fable.Import.VSCode.Vscode, so a change to Fable.Import.VSCode.Vscode can break Fable.Import.VSCode.Vscode.Env, while a change to Fable.Import.VSCode.Vscode.Env can't break Fable.Import.VSCode.Vscode.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
28→9 Fable.Import.VSCode.Vscode.Languages uses Fable.Import.VSCode✕
- Connections
- 1 pair of types, where a type in Fable.Import.VSCode.Vscode.Languages uses a type in Fable.Import.VSCode.
- The types involved
Fable.Import.VSCode.Vscode.Languages.IExports→Fable.Import.VSCode.Thenable`1
- Direction
- Fable.Import.VSCode.Vscode.Languages uses Fable.Import.VSCode, so a change to Fable.Import.VSCode can break Fable.Import.VSCode.Vscode.Languages, while a change to Fable.Import.VSCode.Vscode.Languages can't break Fable.Import.VSCode.
- Position
- Below the diagonal: Fable.Import.VSCode.Vscode.Languages uses a module listed above it, which is the healthy direction.
28→34 Fable.Import.VSCode.Vscode.Languages uses Fable.Import.VSCode.Vscode part of a loop✕
- Connections
- 50 pairs of types, where a type in Fable.Import.VSCode.Vscode.Languages uses a type in Fable.Import.VSCode.Vscode. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
Fable.Import.VSCode.Vscode.Languages.IExports→Fable.Import.VSCode.Vscode.CallHierarchyProviderFable.Import.VSCode.Vscode.Languages.IExports→Fable.Import.VSCode.Vscode.CodeActionFable.Import.VSCode.Vscode.Languages.IExports→Fable.Import.VSCode.Vscode.CodeActionProviderMetadataFable.Import.VSCode.Vscode.Languages.IExports→Fable.Import.VSCode.Vscode.CodeActionProvider`1Fable.Import.VSCode.Vscode.Languages.IExports→Fable.Import.VSCode.Vscode.CodeLensFable.Import.VSCode.Vscode.Languages.IExports→Fable.Import.VSCode.Vscode.CodeLensProvider`1Fable.Import.VSCode.Vscode.Languages.IExports→Fable.Import.VSCode.Vscode.CompletionItemFable.Import.VSCode.Vscode.Languages.IExports→Fable.Import.VSCode.Vscode.CompletionItemProvider`1Fable.Import.VSCode.Vscode.Languages.IExports→Fable.Import.VSCode.Vscode.DeclarationProviderFable.Import.VSCode.Vscode.Languages.IExports→Fable.Import.VSCode.Vscode.DefinitionProviderFable.Import.VSCode.Vscode.Languages.IExports→Fable.Import.VSCode.Vscode.DiagnosticFable.Import.VSCode.Vscode.Languages.IExports→Fable.Import.VSCode.Vscode.DiagnosticChangeEventFable.Import.VSCode.Vscode.Languages.IExports→Fable.Import.VSCode.Vscode.DiagnosticCollectionFable.Import.VSCode.Vscode.Languages.IExports→Fable.Import.VSCode.Vscode.DisposableFable.Import.VSCode.Vscode.Languages.IExports→Fable.Import.VSCode.Vscode.DocumentColorProviderFable.Import.VSCode.Vscode.Languages.IExports→Fable.Import.VSCode.Vscode.DocumentFormattingEditProviderFable.Import.VSCode.Vscode.Languages.IExports→Fable.Import.VSCode.Vscode.DocumentHighlightProviderFable.Import.VSCode.Vscode.Languages.IExports→Fable.Import.VSCode.Vscode.DocumentLinkFable.Import.VSCode.Vscode.Languages.IExports→Fable.Import.VSCode.Vscode.DocumentLinkProvider`1Fable.Import.VSCode.Vscode.Languages.IExports→Fable.Import.VSCode.Vscode.DocumentRangeFormattingEditProviderFable.Import.VSCode.Vscode.Languages.IExports→Fable.Import.VSCode.Vscode.DocumentRangeSemanticTokensProviderFable.Import.VSCode.Vscode.Languages.IExports→Fable.Import.VSCode.Vscode.DocumentSemanticTokensProviderFable.Import.VSCode.Vscode.Languages.IExports→Fable.Import.VSCode.Vscode.DocumentSymbolProviderFable.Import.VSCode.Vscode.Languages.IExports→Fable.Import.VSCode.Vscode.DocumentSymbolProviderMetadataFable.Import.VSCode.Vscode.Languages.IExports→Fable.Import.VSCode.Vscode.EvaluatableExpressionProvider
- Direction
- Fable.Import.VSCode.Vscode.Languages uses Fable.Import.VSCode.Vscode, so a change to Fable.Import.VSCode.Vscode can break Fable.Import.VSCode.Vscode.Languages, while a change to Fable.Import.VSCode.Vscode.Languages can't break Fable.Import.VSCode.Vscode.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
29→9 Fable.Import.VSCode.Vscode.Tasks uses Fable.Import.VSCode✕
- Connections
- 1 pair of types, where a type in Fable.Import.VSCode.Vscode.Tasks uses a type in Fable.Import.VSCode.
- The types involved
Fable.Import.VSCode.Vscode.Tasks.IExports→Fable.Import.VSCode.Thenable`1
- Direction
- Fable.Import.VSCode.Vscode.Tasks uses Fable.Import.VSCode, so a change to Fable.Import.VSCode can break Fable.Import.VSCode.Vscode.Tasks, while a change to Fable.Import.VSCode.Vscode.Tasks can't break Fable.Import.VSCode.
- Position
- Below the diagonal: Fable.Import.VSCode.Vscode.Tasks uses a module listed above it, which is the healthy direction.
29→34 Fable.Import.VSCode.Vscode.Tasks uses Fable.Import.VSCode.Vscode part of a loop✕
- Connections
- 10 pairs of types, where a type in Fable.Import.VSCode.Vscode.Tasks uses a type in Fable.Import.VSCode.Vscode.
- The types involved
Fable.Import.VSCode.Vscode.Tasks.IExports→Fable.Import.VSCode.Vscode.DisposableFable.Import.VSCode.Vscode.Tasks.IExports→Fable.Import.VSCode.Vscode.Event`1Fable.Import.VSCode.Vscode.Tasks.IExports→Fable.Import.VSCode.Vscode.TaskFable.Import.VSCode.Vscode.Tasks.IExports→Fable.Import.VSCode.Vscode.TaskEndEventFable.Import.VSCode.Vscode.Tasks.IExports→Fable.Import.VSCode.Vscode.TaskExecutionFable.Import.VSCode.Vscode.Tasks.IExports→Fable.Import.VSCode.Vscode.TaskFilterFable.Import.VSCode.Vscode.Tasks.IExports→Fable.Import.VSCode.Vscode.TaskProcessEndEventFable.Import.VSCode.Vscode.Tasks.IExports→Fable.Import.VSCode.Vscode.TaskProcessStartEventFable.Import.VSCode.Vscode.Tasks.IExports→Fable.Import.VSCode.Vscode.TaskProvider`1Fable.Import.VSCode.Vscode.Tasks.IExports→Fable.Import.VSCode.Vscode.TaskStartEvent
- Direction
- Fable.Import.VSCode.Vscode.Tasks uses Fable.Import.VSCode.Vscode, so a change to Fable.Import.VSCode.Vscode can break Fable.Import.VSCode.Vscode.Tasks, while a change to Fable.Import.VSCode.Vscode.Tasks can't break Fable.Import.VSCode.Vscode.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
30→9 Fable.Import.VSCode.Vscode.Window uses Fable.Import.VSCode✕
- Connections
- 1 pair of types, where a type in Fable.Import.VSCode.Vscode.Window uses a type in Fable.Import.VSCode.
- The types involved
Fable.Import.VSCode.Vscode.Window.IExports→Fable.Import.VSCode.Thenable`1
- Direction
- Fable.Import.VSCode.Vscode.Window uses Fable.Import.VSCode, so a change to Fable.Import.VSCode can break Fable.Import.VSCode.Vscode.Window, while a change to Fable.Import.VSCode.Vscode.Window can't break Fable.Import.VSCode.
- Position
- Below the diagonal: Fable.Import.VSCode.Vscode.Window uses a module listed above it, which is the healthy direction.
30→34 Fable.Import.VSCode.Vscode.Window uses Fable.Import.VSCode.Vscode part of a loop✕
- Connections
- 47 pairs of types, where a type in Fable.Import.VSCode.Vscode.Window uses a type in Fable.Import.VSCode.Vscode. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
Fable.Import.VSCode.Vscode.Window.IExports→Fable.Import.VSCode.Vscode.CancellationTokenFable.Import.VSCode.Vscode.Window.IExports→Fable.Import.VSCode.Vscode.ColorThemeFable.Import.VSCode.Vscode.Window.IExports→Fable.Import.VSCode.Vscode.CustomDocumentFable.Import.VSCode.Vscode.Window.IExports→Fable.Import.VSCode.Vscode.CustomEditorProvider`1Fable.Import.VSCode.Vscode.Window.IExports→Fable.Import.VSCode.Vscode.CustomReadonlyEditorProvider`1Fable.Import.VSCode.Vscode.Window.IExports→Fable.Import.VSCode.Vscode.CustomTextEditorProviderFable.Import.VSCode.Vscode.Window.IExports→Fable.Import.VSCode.Vscode.DecorationRenderOptionsFable.Import.VSCode.Vscode.Window.IExports→Fable.Import.VSCode.Vscode.DisposableFable.Import.VSCode.Vscode.Window.IExports→Fable.Import.VSCode.Vscode.Event`1Fable.Import.VSCode.Vscode.Window.IExports→Fable.Import.VSCode.Vscode.ExtensionTerminalOptionsFable.Import.VSCode.Vscode.Window.IExports→Fable.Import.VSCode.Vscode.FileDecorationProviderFable.Import.VSCode.Vscode.Window.IExports→Fable.Import.VSCode.Vscode.InputBoxFable.Import.VSCode.Vscode.Window.IExports→Fable.Import.VSCode.Vscode.InputBoxOptionsFable.Import.VSCode.Vscode.Window.IExports→Fable.Import.VSCode.Vscode.MessageOptionsFable.Import.VSCode.Vscode.Window.IExports→Fable.Import.VSCode.Vscode.OpenDialogOptionsFable.Import.VSCode.Vscode.Window.IExports→Fable.Import.VSCode.Vscode.OutputChannelFable.Import.VSCode.Vscode.Window.IExports→Fable.Import.VSCode.Vscode.ProgressOptionsFable.Import.VSCode.Vscode.Window.IExports→Fable.Import.VSCode.Vscode.QuickPickOptionsFable.Import.VSCode.Vscode.Window.IExports→Fable.Import.VSCode.Vscode.QuickPick`1Fable.Import.VSCode.Vscode.Window.IExports→Fable.Import.VSCode.Vscode.SaveDialogOptionsFable.Import.VSCode.Vscode.Window.IExports→Fable.Import.VSCode.Vscode.StatusBarAlignmentFable.Import.VSCode.Vscode.Window.IExports→Fable.Import.VSCode.Vscode.StatusBarItemFable.Import.VSCode.Vscode.Window.IExports→Fable.Import.VSCode.Vscode.TerminalFable.Import.VSCode.Vscode.Window.IExports→Fable.Import.VSCode.Vscode.TerminalLinkFable.Import.VSCode.Vscode.Window.IExports→Fable.Import.VSCode.Vscode.TerminalLinkProvider`1
- Direction
- Fable.Import.VSCode.Vscode.Window uses Fable.Import.VSCode.Vscode, so a change to Fable.Import.VSCode.Vscode can break Fable.Import.VSCode.Vscode.Window, while a change to Fable.Import.VSCode.Vscode.Window can't break Fable.Import.VSCode.Vscode.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
31→9 Fable.Import.VSCode.Vscode.Workspace uses Fable.Import.VSCode✕
- Connections
- 1 pair of types, where a type in Fable.Import.VSCode.Vscode.Workspace uses a type in Fable.Import.VSCode.
- The types involved
Fable.Import.VSCode.Vscode.Workspace.IExports→Fable.Import.VSCode.Thenable`1
- Direction
- Fable.Import.VSCode.Vscode.Workspace uses Fable.Import.VSCode, so a change to Fable.Import.VSCode can break Fable.Import.VSCode.Vscode.Workspace, while a change to Fable.Import.VSCode.Vscode.Workspace can't break Fable.Import.VSCode.
- Position
- Below the diagonal: Fable.Import.VSCode.Vscode.Workspace uses a module listed above it, which is the healthy direction.
31→34 Fable.Import.VSCode.Vscode.Workspace uses Fable.Import.VSCode.Vscode part of a loop✕
- Connections
- 29 pairs of types, where a type in Fable.Import.VSCode.Vscode.Workspace uses a type in Fable.Import.VSCode.Vscode. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
Fable.Import.VSCode.Vscode.Workspace.IExports→Fable.Import.VSCode.Vscode.CancellationTokenFable.Import.VSCode.Vscode.Workspace.IExports→Fable.Import.VSCode.Vscode.ConfigurationChangeEventFable.Import.VSCode.Vscode.Workspace.IExports→Fable.Import.VSCode.Vscode.DisposableFable.Import.VSCode.Vscode.Workspace.IExports→Fable.Import.VSCode.Vscode.Event`1Fable.Import.VSCode.Vscode.Workspace.IExports→Fable.Import.VSCode.Vscode.FileCreateEventFable.Import.VSCode.Vscode.Workspace.IExports→Fable.Import.VSCode.Vscode.FileDeleteEventFable.Import.VSCode.Vscode.Workspace.IExports→Fable.Import.VSCode.Vscode.FileRenameEventFable.Import.VSCode.Vscode.Workspace.IExports→Fable.Import.VSCode.Vscode.FileSystemFable.Import.VSCode.Vscode.Workspace.IExports→Fable.Import.VSCode.Vscode.FileSystemProviderFable.Import.VSCode.Vscode.Workspace.IExports→Fable.Import.VSCode.Vscode.FileSystemWatcherFable.Import.VSCode.Vscode.Workspace.IExports→Fable.Import.VSCode.Vscode.FileWillCreateEventFable.Import.VSCode.Vscode.Workspace.IExports→Fable.Import.VSCode.Vscode.FileWillDeleteEventFable.Import.VSCode.Vscode.Workspace.IExports→Fable.Import.VSCode.Vscode.FileWillRenameEventFable.Import.VSCode.Vscode.Workspace.IExports→Fable.Import.VSCode.Vscode.NotebookDataFable.Import.VSCode.Vscode.Workspace.IExports→Fable.Import.VSCode.Vscode.NotebookDocumentFable.Import.VSCode.Vscode.Workspace.IExports→Fable.Import.VSCode.Vscode.NotebookDocumentContentOptionsFable.Import.VSCode.Vscode.Workspace.IExports→Fable.Import.VSCode.Vscode.NotebookSerializerFable.Import.VSCode.Vscode.Workspace.IExports→Fable.Import.VSCode.Vscode.RelativePatternFable.Import.VSCode.Vscode.Workspace.IExports→Fable.Import.VSCode.Vscode.TaskFable.Import.VSCode.Vscode.Workspace.IExports→Fable.Import.VSCode.Vscode.TaskProvider`1Fable.Import.VSCode.Vscode.Workspace.IExports→Fable.Import.VSCode.Vscode.TextDocumentFable.Import.VSCode.Vscode.Workspace.IExports→Fable.Import.VSCode.Vscode.TextDocumentChangeEventFable.Import.VSCode.Vscode.Workspace.IExports→Fable.Import.VSCode.Vscode.TextDocumentContentProviderFable.Import.VSCode.Vscode.Workspace.IExports→Fable.Import.VSCode.Vscode.TextDocumentWillSaveEventFable.Import.VSCode.Vscode.Workspace.IExports→Fable.Import.VSCode.Vscode.Uri
- Direction
- Fable.Import.VSCode.Vscode.Workspace uses Fable.Import.VSCode.Vscode, so a change to Fable.Import.VSCode.Vscode can break Fable.Import.VSCode.Vscode.Workspace, while a change to Fable.Import.VSCode.Vscode.Workspace can't break Fable.Import.VSCode.Vscode.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
32→1 Contextive.LanguageServer.Glossary.Handlers uses Contextive.Core.File✕
- Connections
- 1 pair of types, where a type in Contextive.LanguageServer.Glossary.Handlers uses a type in Contextive.Core.File.
- The types involved
Contextive.LanguageServer.Glossary.Handlers.Handlers→Contextive.Core.File.PathConfiguration
- Direction
- Contextive.LanguageServer.Glossary.Handlers uses Contextive.Core.File, so a change to Contextive.Core.File can break Contextive.LanguageServer.Glossary.Handlers, while a change to Contextive.LanguageServer.Glossary.Handlers can't break Contextive.Core.File.
- Position
- Below the diagonal: Contextive.LanguageServer.Glossary.Handlers uses a module listed above it, which is the healthy direction.
32→20 Contextive.LanguageServer.Glossary.Handlers uses Contextive.LanguageServer.Glossary✕
- Connections
- 3 pairs of types, where a type in Contextive.LanguageServer.Glossary.Handlers uses a type in Contextive.LanguageServer.Glossary.
- The types involved
Contextive.LanguageServer.Glossary.Handlers.Handlers→Contextive.LanguageServer.Glossary.LookupContextive.LanguageServer.Glossary.Handlers.Handlers→Contextive.LanguageServer.Glossary.StartGlossaryContextive.LanguageServer.Glossary.Handlers.Handlers→Contextive.LanguageServer.Glossary.State
- Direction
- Contextive.LanguageServer.Glossary.Handlers uses Contextive.LanguageServer.Glossary, so a change to Contextive.LanguageServer.Glossary can break Contextive.LanguageServer.Glossary.Handlers, while a change to Contextive.LanguageServer.Glossary.Handlers can't break Contextive.LanguageServer.Glossary.
- Position
- Below the diagonal: Contextive.LanguageServer.Glossary.Handlers uses a module listed above it, which is the healthy direction.
33→3 Contextive.LanguageServer.GlossaryManager uses Contextive.LanguageServer.Logger✕
- Connections
- 2 pairs of types, where a type in Contextive.LanguageServer.GlossaryManager uses a type in Contextive.LanguageServer.Logger.
- The types involved
Contextive.LanguageServer.GlossaryManager.InitGlossaryManager→Contextive.LanguageServer.Logger.LoggerContextive.LanguageServer.GlossaryManager.State→Contextive.LanguageServer.Logger.Logger
- Direction
- Contextive.LanguageServer.GlossaryManager uses Contextive.LanguageServer.Logger, so a change to Contextive.LanguageServer.Logger can break Contextive.LanguageServer.GlossaryManager, while a change to Contextive.LanguageServer.GlossaryManager can't break Contextive.LanguageServer.Logger.
- Position
- Below the diagonal: Contextive.LanguageServer.GlossaryManager uses a module listed above it, which is the healthy direction.
33→4 Contextive.LanguageServer.GlossaryManager uses Contextive.Core.GlossaryFile✕
- Connections
- 2 pairs of types, where a type in Contextive.LanguageServer.GlossaryManager uses a type in Contextive.Core.GlossaryFile.
- The types involved
Contextive.LanguageServer.GlossaryManager.GlossaryManager→Contextive.Core.GlossaryFile.ContextContextive.LanguageServer.GlossaryManager.Lookup→Contextive.Core.GlossaryFile.Context
- Direction
- Contextive.LanguageServer.GlossaryManager uses Contextive.Core.GlossaryFile, so a change to Contextive.Core.GlossaryFile can break Contextive.LanguageServer.GlossaryManager, while a change to Contextive.LanguageServer.GlossaryManager can't break Contextive.Core.GlossaryFile.
- Position
- Below the diagonal: Contextive.LanguageServer.GlossaryManager uses a module listed above it, which is the healthy direction.
33→20 Contextive.LanguageServer.GlossaryManager uses Contextive.LanguageServer.Glossary✕
- Connections
- 1 pair of types, where a type in Contextive.LanguageServer.GlossaryManager uses a type in Contextive.LanguageServer.Glossary.
- The types involved
Contextive.LanguageServer.GlossaryManager.State→Contextive.LanguageServer.Glossary.Message
- Direction
- Contextive.LanguageServer.GlossaryManager uses Contextive.LanguageServer.Glossary, so a change to Contextive.LanguageServer.Glossary can break Contextive.LanguageServer.GlossaryManager, while a change to Contextive.LanguageServer.GlossaryManager can't break Contextive.LanguageServer.Glossary.
- Position
- Below the diagonal: Contextive.LanguageServer.GlossaryManager uses a module listed above it, which is the healthy direction.
34→9 Fable.Import.VSCode.Vscode uses Fable.Import.VSCode✕
- Connections
- 72 pairs of types, where a type in Fable.Import.VSCode.Vscode uses a type in Fable.Import.VSCode. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
Fable.Import.VSCode.Vscode.AuthenticationProvider→Fable.Import.VSCode.Thenable`1Fable.Import.VSCode.Vscode.CallHierarchyProvider→Fable.Import.VSCode.Thenable`1Fable.Import.VSCode.Vscode.Clipboard→Fable.Import.VSCode.Thenable`1Fable.Import.VSCode.Vscode.CodeActionProvider`1→Fable.Import.VSCode.Thenable`1Fable.Import.VSCode.Vscode.CodeLensProvider`1→Fable.Import.VSCode.Thenable`1Fable.Import.VSCode.Vscode.CommentingRangeProvider→Fable.Import.VSCode.Thenable`1Fable.Import.VSCode.Vscode.CompletionItemProvider`1→Fable.Import.VSCode.Thenable`1Fable.Import.VSCode.Vscode.CustomDocumentEditEvent`1→Fable.Import.VSCode.Thenable`1Fable.Import.VSCode.Vscode.CustomEditorProvider`1→Fable.Import.VSCode.Thenable`1Fable.Import.VSCode.Vscode.CustomReadonlyEditorProvider`1→Fable.Import.VSCode.Thenable`1Fable.Import.VSCode.Vscode.CustomTextEditorProvider→Fable.Import.VSCode.Thenable`1Fable.Import.VSCode.Vscode.DataTransferItem→Fable.Import.VSCode.Thenable`1Fable.Import.VSCode.Vscode.DebugAdapterDescriptorFactory→Fable.Import.VSCode.Thenable`1Fable.Import.VSCode.Vscode.DebugAdapterTrackerFactory→Fable.Import.VSCode.Thenable`1Fable.Import.VSCode.Vscode.DebugConfigurationProvider→Fable.Import.VSCode.Thenable`1Fable.Import.VSCode.Vscode.DebugSession→Fable.Import.VSCode.Thenable`1Fable.Import.VSCode.Vscode.DeclarationProvider→Fable.Import.VSCode.Thenable`1Fable.Import.VSCode.Vscode.DefinitionProvider→Fable.Import.VSCode.Thenable`1Fable.Import.VSCode.Vscode.DocumentColorProvider→Fable.Import.VSCode.Thenable`1Fable.Import.VSCode.Vscode.DocumentFormattingEditProvider→Fable.Import.VSCode.Thenable`1Fable.Import.VSCode.Vscode.DocumentHighlightProvider→Fable.Import.VSCode.Thenable`1Fable.Import.VSCode.Vscode.DocumentLinkProvider`1→Fable.Import.VSCode.Thenable`1Fable.Import.VSCode.Vscode.DocumentRangeFormattingEditProvider→Fable.Import.VSCode.Thenable`1Fable.Import.VSCode.Vscode.DocumentRangeSemanticTokensProvider→Fable.Import.VSCode.Thenable`1Fable.Import.VSCode.Vscode.DocumentSemanticTokensProvider→Fable.Import.VSCode.Thenable`1
- Direction
- Fable.Import.VSCode.Vscode uses Fable.Import.VSCode, so a change to Fable.Import.VSCode can break Fable.Import.VSCode.Vscode, while a change to Fable.Import.VSCode.Vscode can't break Fable.Import.VSCode.
- Position
- Below the diagonal: Fable.Import.VSCode.Vscode uses a module listed above it, which is the healthy direction.
34→10 Fable.Import.VSCode.Vscode uses Fable.Import.VSCode.Vscode.Comments✕
- Connections
- 1 pair of types, where a type in Fable.Import.VSCode.Vscode uses a type in Fable.Import.VSCode.Vscode.Comments.
- The types involved
Fable.Import.VSCode.Vscode.Vscode→Fable.Import.VSCode.Vscode.Comments.IExports
- Direction
- Fable.Import.VSCode.Vscode uses Fable.Import.VSCode.Vscode.Comments, so a change to Fable.Import.VSCode.Vscode.Comments can break Fable.Import.VSCode.Vscode, while a change to Fable.Import.VSCode.Vscode can't break Fable.Import.VSCode.Vscode.Comments.
- Position
- Below the diagonal: Fable.Import.VSCode.Vscode uses a module listed above it, which is the healthy direction.
34→11 Fable.Import.VSCode.Vscode uses Fable.Import.VSCode.Vscode.Extensions✕
- Connections
- 1 pair of types, where a type in Fable.Import.VSCode.Vscode uses a type in Fable.Import.VSCode.Vscode.Extensions.
- The types involved
Fable.Import.VSCode.Vscode.Vscode→Fable.Import.VSCode.Vscode.Extensions.IExports
- Direction
- Fable.Import.VSCode.Vscode uses Fable.Import.VSCode.Vscode.Extensions, so a change to Fable.Import.VSCode.Vscode.Extensions can break Fable.Import.VSCode.Vscode, while a change to Fable.Import.VSCode.Vscode can't break Fable.Import.VSCode.Vscode.Extensions.
- Position
- Below the diagonal: Fable.Import.VSCode.Vscode uses a module listed above it, which is the healthy direction.
34→12 Fable.Import.VSCode.Vscode uses Fable.Import.VSCode.Vscode.Notebooks✕
- Connections
- 1 pair of types, where a type in Fable.Import.VSCode.Vscode uses a type in Fable.Import.VSCode.Vscode.Notebooks.
- The types involved
Fable.Import.VSCode.Vscode.Vscode→Fable.Import.VSCode.Vscode.Notebooks.IExports
- Direction
- Fable.Import.VSCode.Vscode uses Fable.Import.VSCode.Vscode.Notebooks, so a change to Fable.Import.VSCode.Vscode.Notebooks can break Fable.Import.VSCode.Vscode, while a change to Fable.Import.VSCode.Vscode can't break Fable.Import.VSCode.Vscode.Notebooks.
- Position
- Below the diagonal: Fable.Import.VSCode.Vscode uses a module listed above it, which is the healthy direction.
34→13 Fable.Import.VSCode.Vscode uses Fable.Import.VSCode.Vscode.Scm✕
- Connections
- 1 pair of types, where a type in Fable.Import.VSCode.Vscode uses a type in Fable.Import.VSCode.Vscode.Scm.
- The types involved
Fable.Import.VSCode.Vscode.Vscode→Fable.Import.VSCode.Vscode.Scm.IExports
- Direction
- Fable.Import.VSCode.Vscode uses Fable.Import.VSCode.Vscode.Scm, so a change to Fable.Import.VSCode.Vscode.Scm can break Fable.Import.VSCode.Vscode, while a change to Fable.Import.VSCode.Vscode can't break Fable.Import.VSCode.Vscode.Scm.
- Position
- Below the diagonal: Fable.Import.VSCode.Vscode uses a module listed above it, which is the healthy direction.
34→14 Fable.Import.VSCode.Vscode uses Fable.Import.VSCode.Vscode.Tests✕
- Connections
- 1 pair of types, where a type in Fable.Import.VSCode.Vscode uses a type in Fable.Import.VSCode.Vscode.Tests.
- The types involved
Fable.Import.VSCode.Vscode.Vscode→Fable.Import.VSCode.Vscode.Tests.IExports
- Direction
- Fable.Import.VSCode.Vscode uses Fable.Import.VSCode.Vscode.Tests, so a change to Fable.Import.VSCode.Vscode.Tests can break Fable.Import.VSCode.Vscode, while a change to Fable.Import.VSCode.Vscode can't break Fable.Import.VSCode.Vscode.Tests.
- Position
- Below the diagonal: Fable.Import.VSCode.Vscode uses a module listed above it, which is the healthy direction.
34→24 Fable.Import.VSCode.Vscode uses Fable.Import.VSCode.Vscode.Authentication✕
- Connections
- 1 pair of types, where a type in Fable.Import.VSCode.Vscode uses a type in Fable.Import.VSCode.Vscode.Authentication.
- The types involved
Fable.Import.VSCode.Vscode.Vscode→Fable.Import.VSCode.Vscode.Authentication.IExports
- Direction
- Fable.Import.VSCode.Vscode uses Fable.Import.VSCode.Vscode.Authentication, so a change to Fable.Import.VSCode.Vscode.Authentication can break Fable.Import.VSCode.Vscode, while a change to Fable.Import.VSCode.Vscode can't break Fable.Import.VSCode.Vscode.Authentication.
- Position
- Below the diagonal: Fable.Import.VSCode.Vscode uses a module listed above it, which is the healthy direction.
34→25 Fable.Import.VSCode.Vscode uses Fable.Import.VSCode.Vscode.Commands✕
- Connections
- 1 pair of types, where a type in Fable.Import.VSCode.Vscode uses a type in Fable.Import.VSCode.Vscode.Commands.
- The types involved
Fable.Import.VSCode.Vscode.Vscode→Fable.Import.VSCode.Vscode.Commands.IExports
- Direction
- Fable.Import.VSCode.Vscode uses Fable.Import.VSCode.Vscode.Commands, so a change to Fable.Import.VSCode.Vscode.Commands can break Fable.Import.VSCode.Vscode, while a change to Fable.Import.VSCode.Vscode can't break Fable.Import.VSCode.Vscode.Commands.
- Position
- Below the diagonal: Fable.Import.VSCode.Vscode uses a module listed above it, which is the healthy direction.
34→26 Fable.Import.VSCode.Vscode uses Fable.Import.VSCode.Vscode.Debug✕
- Connections
- 1 pair of types, where a type in Fable.Import.VSCode.Vscode uses a type in Fable.Import.VSCode.Vscode.Debug.
- The types involved
Fable.Import.VSCode.Vscode.Vscode→Fable.Import.VSCode.Vscode.Debug.IExports
- Direction
- Fable.Import.VSCode.Vscode uses Fable.Import.VSCode.Vscode.Debug, so a change to Fable.Import.VSCode.Vscode.Debug can break Fable.Import.VSCode.Vscode, while a change to Fable.Import.VSCode.Vscode can't break Fable.Import.VSCode.Vscode.Debug.
- Position
- Below the diagonal: Fable.Import.VSCode.Vscode uses a module listed above it, which is the healthy direction.
34→27 Fable.Import.VSCode.Vscode uses Fable.Import.VSCode.Vscode.Env✕
- Connections
- 1 pair of types, where a type in Fable.Import.VSCode.Vscode uses a type in Fable.Import.VSCode.Vscode.Env.
- The types involved
Fable.Import.VSCode.Vscode.Vscode→Fable.Import.VSCode.Vscode.Env.IExports
- Direction
- Fable.Import.VSCode.Vscode uses Fable.Import.VSCode.Vscode.Env, so a change to Fable.Import.VSCode.Vscode.Env can break Fable.Import.VSCode.Vscode, while a change to Fable.Import.VSCode.Vscode can't break Fable.Import.VSCode.Vscode.Env.
- Position
- Below the diagonal: Fable.Import.VSCode.Vscode uses a module listed above it, which is the healthy direction.
34→28 Fable.Import.VSCode.Vscode uses Fable.Import.VSCode.Vscode.Languages✕
- Connections
- 1 pair of types, where a type in Fable.Import.VSCode.Vscode uses a type in Fable.Import.VSCode.Vscode.Languages.
- The types involved
Fable.Import.VSCode.Vscode.Vscode→Fable.Import.VSCode.Vscode.Languages.IExports
- Direction
- Fable.Import.VSCode.Vscode uses Fable.Import.VSCode.Vscode.Languages, so a change to Fable.Import.VSCode.Vscode.Languages can break Fable.Import.VSCode.Vscode, while a change to Fable.Import.VSCode.Vscode can't break Fable.Import.VSCode.Vscode.Languages.
- Position
- Below the diagonal: Fable.Import.VSCode.Vscode uses a module listed above it, which is the healthy direction.
34→29 Fable.Import.VSCode.Vscode uses Fable.Import.VSCode.Vscode.Tasks✕
- Connections
- 1 pair of types, where a type in Fable.Import.VSCode.Vscode uses a type in Fable.Import.VSCode.Vscode.Tasks.
- The types involved
Fable.Import.VSCode.Vscode.Vscode→Fable.Import.VSCode.Vscode.Tasks.IExports
- Direction
- Fable.Import.VSCode.Vscode uses Fable.Import.VSCode.Vscode.Tasks, so a change to Fable.Import.VSCode.Vscode.Tasks can break Fable.Import.VSCode.Vscode, while a change to Fable.Import.VSCode.Vscode can't break Fable.Import.VSCode.Vscode.Tasks.
- Position
- Below the diagonal: Fable.Import.VSCode.Vscode uses a module listed above it, which is the healthy direction.
34→30 Fable.Import.VSCode.Vscode uses Fable.Import.VSCode.Vscode.Window✕
- Connections
- 1 pair of types, where a type in Fable.Import.VSCode.Vscode uses a type in Fable.Import.VSCode.Vscode.Window.
- The types involved
Fable.Import.VSCode.Vscode.Vscode→Fable.Import.VSCode.Vscode.Window.IExports
- Direction
- Fable.Import.VSCode.Vscode uses Fable.Import.VSCode.Vscode.Window, so a change to Fable.Import.VSCode.Vscode.Window can break Fable.Import.VSCode.Vscode, while a change to Fable.Import.VSCode.Vscode can't break Fable.Import.VSCode.Vscode.Window.
- Position
- Below the diagonal: Fable.Import.VSCode.Vscode uses a module listed above it, which is the healthy direction.
34→31 Fable.Import.VSCode.Vscode uses Fable.Import.VSCode.Vscode.Workspace✕
- Connections
- 1 pair of types, where a type in Fable.Import.VSCode.Vscode uses a type in Fable.Import.VSCode.Vscode.Workspace.
- The types involved
Fable.Import.VSCode.Vscode.Vscode→Fable.Import.VSCode.Vscode.Workspace.IExports
- Direction
- Fable.Import.VSCode.Vscode uses Fable.Import.VSCode.Vscode.Workspace, so a change to Fable.Import.VSCode.Vscode.Workspace can break Fable.Import.VSCode.Vscode, while a change to Fable.Import.VSCode.Vscode can't break Fable.Import.VSCode.Vscode.Workspace.
- Position
- Below the diagonal: Fable.Import.VSCode.Vscode uses a module listed above it, which is the healthy direction.
35→33 Contextive.LanguageServer.GlossaryManager.Handlers uses Contextive.LanguageServer.GlossaryManager✕
- Connections
- 5 pairs of types, where a type in Contextive.LanguageServer.GlossaryManager.Handlers uses a type in Contextive.LanguageServer.GlossaryManager.
- The types involved
Contextive.LanguageServer.GlossaryManager.Handlers.Handlers→Contextive.LanguageServer.GlossaryManager.CreateGlossaryManagerContextive.LanguageServer.GlossaryManager.Handlers.Handlers→Contextive.LanguageServer.GlossaryManager.InitGlossaryManagerContextive.LanguageServer.GlossaryManager.Handlers.Handlers→Contextive.LanguageServer.GlossaryManager.LookupContextive.LanguageServer.GlossaryManager.Handlers.Handlers→Contextive.LanguageServer.GlossaryManager.OnWatchedFilesEventHandlersContextive.LanguageServer.GlossaryManager.Handlers.Handlers→Contextive.LanguageServer.GlossaryManager.State
- Direction
- Contextive.LanguageServer.GlossaryManager.Handlers uses Contextive.LanguageServer.GlossaryManager, so a change to Contextive.LanguageServer.GlossaryManager can break Contextive.LanguageServer.GlossaryManager.Handlers, while a change to Contextive.LanguageServer.GlossaryManager.Handlers can't break Contextive.LanguageServer.GlossaryManager.
- Position
- Below the diagonal: Contextive.LanguageServer.GlossaryManager.Handlers uses a module listed above it, which is the healthy direction.
36→34 Fable.Import.LanguageServer.Client uses Fable.Import.VSCode.Vscode✕
- Connections
- 13 pairs of types, where a type in Fable.Import.LanguageServer.Client uses a type in Fable.Import.VSCode.Vscode.
- The types involved
Fable.Import.LanguageServer.Client.BaseLanguageClient→Fable.Import.VSCode.Vscode.CancellationTokenFable.Import.LanguageServer.Client.BaseLanguageClient→Fable.Import.VSCode.Vscode.DiagnosticCollectionFable.Import.LanguageServer.Client.BaseLanguageClient→Fable.Import.VSCode.Vscode.DisposableFable.Import.LanguageServer.Client.BaseLanguageClient→Fable.Import.VSCode.Vscode.Event`1Fable.Import.LanguageServer.Client.BaseLanguageClient→Fable.Import.VSCode.Vscode.OutputChannelFable.Import.LanguageServer.Client.DynamicFeature`1→Fable.Import.VSCode.Vscode.NotebookCellTextDocumentFilterFable.Import.LanguageServer.Client.DynamicFeature`1→Fable.Import.VSCode.Vscode.TextDocumentFilterFable.Import.LanguageServer.Client.LanguageClientOptions→Fable.Import.VSCode.Vscode.NotebookCellTextDocumentFilterFable.Import.LanguageServer.Client.LanguageClientOptions→Fable.Import.VSCode.Vscode.OutputChannelFable.Import.LanguageServer.Client.LanguageClientOptions→Fable.Import.VSCode.Vscode.TextDocumentFilterFable.Import.LanguageServer.Client.StaticFeature→Fable.Import.VSCode.Vscode.NotebookCellTextDocumentFilterFable.Import.LanguageServer.Client.StaticFeature→Fable.Import.VSCode.Vscode.TextDocumentFilterFable.Import.LanguageServer.Client.SynchronizeOptions→Fable.Import.VSCode.Vscode.FileSystemWatcher
- Direction
- Fable.Import.LanguageServer.Client uses Fable.Import.VSCode.Vscode, so a change to Fable.Import.VSCode.Vscode can break Fable.Import.LanguageServer.Client, while a change to Fable.Import.LanguageServer.Client can't break Fable.Import.VSCode.Vscode.
- Position
- Below the diagonal: Fable.Import.LanguageServer.Client uses a module listed above it, which is the healthy direction.
37→36 Contextive.VsCodeExtension.Middleware uses Fable.Import.LanguageServer.Client✕
- Connections
- 1 pair of types, where a type in Contextive.VsCodeExtension.Middleware uses a type in Fable.Import.LanguageServer.Client.
- The types involved
Contextive.VsCodeExtension.Middleware.WorkspaceConfigurationMiddleware→Fable.Import.LanguageServer.Client.Middleware
- Direction
- Contextive.VsCodeExtension.Middleware uses Fable.Import.LanguageServer.Client, so a change to Fable.Import.LanguageServer.Client can break Contextive.VsCodeExtension.Middleware, while a change to Contextive.VsCodeExtension.Middleware can't break Fable.Import.LanguageServer.Client.
- Position
- Below the diagonal: Contextive.VsCodeExtension.Middleware uses a module listed above it, which is the healthy direction.
38→34 Fable.Import.LanguageServer uses Fable.Import.VSCode.Vscode✕
- Connections
- 4 pairs of types, where a type in Fable.Import.LanguageServer uses a type in Fable.Import.VSCode.Vscode.
- The types involved
Fable.Import.LanguageServer.LanguageClient→Fable.Import.VSCode.Vscode.CancellationTokenFable.Import.LanguageServer.LanguageClient→Fable.Import.VSCode.Vscode.DiagnosticCollectionFable.Import.LanguageServer.LanguageClient→Fable.Import.VSCode.Vscode.Event`1Fable.Import.LanguageServer.LanguageClient→Fable.Import.VSCode.Vscode.OutputChannel
- Direction
- Fable.Import.LanguageServer uses Fable.Import.VSCode.Vscode, so a change to Fable.Import.VSCode.Vscode can break Fable.Import.LanguageServer, while a change to Fable.Import.LanguageServer can't break Fable.Import.VSCode.Vscode.
- Position
- Below the diagonal: Fable.Import.LanguageServer uses a module listed above it, which is the healthy direction.
38→36 Fable.Import.LanguageServer uses Fable.Import.LanguageServer.Client✕
- Connections
- 4 pairs of types, where a type in Fable.Import.LanguageServer uses a type in Fable.Import.LanguageServer.Client.
- The types involved
Fable.Import.LanguageServer.LanguageClient→Fable.Import.LanguageServer.Client.ErrorHandlerFable.Import.LanguageServer.LanguageClient→Fable.Import.LanguageServer.Client.LanguageClientOptionsFable.Import.LanguageServer.LanguageClient→Fable.Import.LanguageServer.Client.MessageTransportsFable.Import.LanguageServer.LanguageClient→Fable.Import.LanguageServer.Client.StateChangeEvent
- Direction
- Fable.Import.LanguageServer uses Fable.Import.LanguageServer.Client, so a change to Fable.Import.LanguageServer.Client can break Fable.Import.LanguageServer, while a change to Fable.Import.LanguageServer can't break Fable.Import.LanguageServer.Client.
- Position
- Below the diagonal: Fable.Import.LanguageServer uses a module listed above it, which is the healthy direction.
39→34 Contextive.VsCodeExtension.Extension uses Fable.Import.VSCode.Vscode✕
- Connections
- 2 pairs of types, where a type in Contextive.VsCodeExtension.Extension uses a type in Fable.Import.VSCode.Vscode.
- The types involved
Contextive.VsCodeExtension.Extension.Extension→Fable.Import.VSCode.Vscode.DisposableContextive.VsCodeExtension.Extension.Extension→Fable.Import.VSCode.Vscode.ExtensionContext
- Direction
- Contextive.VsCodeExtension.Extension uses Fable.Import.VSCode.Vscode, so a change to Fable.Import.VSCode.Vscode can break Contextive.VsCodeExtension.Extension, while a change to Contextive.VsCodeExtension.Extension can't break Fable.Import.VSCode.Vscode.
- Position
- Below the diagonal: Contextive.VsCodeExtension.Extension uses a module listed above it, which is the healthy direction.
39→36 Contextive.VsCodeExtension.Extension uses Fable.Import.LanguageServer.Client✕
- Connections
- 1 pair of types, where a type in Contextive.VsCodeExtension.Extension uses a type in Fable.Import.LanguageServer.Client.
- The types involved
Contextive.VsCodeExtension.Extension.Extension→Fable.Import.LanguageServer.Client.LanguageClientOptions
- Direction
- Contextive.VsCodeExtension.Extension uses Fable.Import.LanguageServer.Client, so a change to Fable.Import.LanguageServer.Client can break Contextive.VsCodeExtension.Extension, while a change to Contextive.VsCodeExtension.Extension can't break Fable.Import.LanguageServer.Client.
- Position
- Below the diagonal: Contextive.VsCodeExtension.Extension uses a module listed above it, which is the healthy direction.
39→38 Contextive.VsCodeExtension.Extension uses Fable.Import.LanguageServer✕
- Connections
- 5 pairs of types, where a type in Contextive.VsCodeExtension.Extension uses a type in Fable.Import.LanguageServer.
- The types involved
Contextive.VsCodeExtension.Extension.Api→Fable.Import.LanguageServer.LanguageClientContextive.VsCodeExtension.Extension.Extension→Fable.Import.LanguageServer.ExecutableContextive.VsCodeExtension.Extension.Extension→Fable.Import.LanguageServer.ExecutableOptionsContextive.VsCodeExtension.Extension.Extension→Fable.Import.LanguageServer.LanguageClientContextive.VsCodeExtension.Extension.Extension→Fable.Import.LanguageServer.NodeModule
- Direction
- Contextive.VsCodeExtension.Extension uses Fable.Import.LanguageServer, so a change to Fable.Import.LanguageServer can break Contextive.VsCodeExtension.Extension, while a change to Contextive.VsCodeExtension.Extension can't break Fable.Import.LanguageServer.
- Position
- Below the diagonal: Contextive.VsCodeExtension.Extension uses a module listed above it, which is the healthy direction.
40→34 Contextive.VsCodeExtension.MultiRoot uses Fable.Import.VSCode.Vscode✕
- Connections
- 1 pair of types, where a type in Contextive.VsCodeExtension.MultiRoot uses a type in Fable.Import.VSCode.Vscode.
- The types involved
Contextive.VsCodeExtension.MultiRoot.MultiRoot→Fable.Import.VSCode.Vscode.CancellationToken
- Direction
- Contextive.VsCodeExtension.MultiRoot uses Fable.Import.VSCode.Vscode, so a change to Fable.Import.VSCode.Vscode can break Contextive.VsCodeExtension.MultiRoot, while a change to Contextive.VsCodeExtension.MultiRoot can't break Fable.Import.VSCode.Vscode.
- Position
- Below the diagonal: Contextive.VsCodeExtension.MultiRoot uses a module listed above it, which is the healthy direction.
40→37 Contextive.VsCodeExtension.MultiRoot uses Contextive.VsCodeExtension.Middleware✕
- Connections
- 3 pairs of types, where a type in Contextive.VsCodeExtension.MultiRoot uses a type in Contextive.VsCodeExtension.Middleware.
- The types involved
Contextive.VsCodeExtension.MultiRoot.MultiRoot→Contextive.VsCodeExtension.Middleware.ConfigurationMiddlewareContextive.VsCodeExtension.MultiRoot.MultiRoot→Contextive.VsCodeExtension.Middleware.ConfigurationParamsContextive.VsCodeExtension.MultiRoot.MultiRoot→Contextive.VsCodeExtension.Middleware.WorkspaceConfigurationMiddleware
- Direction
- Contextive.VsCodeExtension.MultiRoot uses Contextive.VsCodeExtension.Middleware, so a change to Contextive.VsCodeExtension.Middleware can break Contextive.VsCodeExtension.MultiRoot, while a change to Contextive.VsCodeExtension.MultiRoot can't break Contextive.VsCodeExtension.Middleware.
- Position
- Below the diagonal: Contextive.VsCodeExtension.MultiRoot uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A03:2025 — Software Supply Chain Failures | 79 | High / Critical |
| A05:2025 — Injection | 43 | High / Critical |
| A02:2025 — Security Misconfiguration | 1 | Medium |
Roadmap
Top priorities: Resolve the 17 Outdated (npm) finding(s) in Dependency Hygiene; Resolve the 1 Test suite declares a test script but contains no test files finding(s) in Test Reliability; Resolve the 14 Orphaned file finding(s) in Knowledge Freshness — start with Fable.Import.VSCode.LanguageServer.fs, GlossaryManager.fs, Completion.fs.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 1 Test suite declares a test script but contains no test files finding(s) in Test Reliability. | +4.6 pts | Low | Test Reliability |
| Resolve the 1 REDACTED finding(s) in Vulnerability-disclosure Policy — start with REDACTED. | +3.4 pts | Low | Vulnerability-disclosure Policy |
| Resolve the 17 Outdated (npm) finding(s) in Dependency Hygiene. | +6.6 pts | Medium | Dependency Hygiene |
| Resolve the 8 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (4), REDACTED (3), REDACTED. | +2.8 pts | Low | Static Analysis (SAST) |
| Resolve the 5 Outdated finding(s) in Dependency Hygiene — start with Contextive.Cli.Tests.fsproj, Contextive.LanguageServer.fsproj. | +2.5 pts | Low | Dependency Hygiene |
| Resolve the 6 REDACTED finding(s) charged to Static Analysis (SAST) — the other 26 are reported here at file:line but scored by D36 (supply-chain provenance), which charges them once. | +2.2 pts | Low | Static Analysis (SAST) |
| Resolve the 3 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED, REDACTED. | +2.0 pts | Low | Supply-chain Provenance & Signing |
| Resolve the 14 Orphaned file finding(s) in Knowledge Freshness — start with Fable.Import.VSCode.LanguageServer.fs, GlossaryManager.fs, Completion.fs. | +3.8 pts | Medium | Knowledge Freshness |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 0.0 | Slop | Dependency Vulnerabilities: Critical CVE: REDACTED |
| REDACTED | 0.0 | Slop | Dependency Vulnerabilities: Critical CVE: REDACTED |
| REDACTED | 1.3 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.3 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.7 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 3.0 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 3.7 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.6 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.1 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.8 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.8 | Mixed | Dependency Vulnerabilities: High CVE: REDACTED |
| REDACTED | 7.2 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 7.9 | Mixed | Supply-chain Provenance & Signing: REDACTED |
| src/intellij/build.fsx | 8.0 | Near-clean | Change Coupling: Boundary-crossing change coupling: build.fsx ↔ build.fsx |
| src/language-server/build.fsx | 8.0 | Near-clean | Change Coupling: Boundary-crossing change coupling: build.fsx ↔ build.fsx |
| src/core/Contextive.Core/CandidateTerms.fs | 8.5 | Near-clean | Code Duplication: Duplicated block (8 lines × 2) |
| src/vscode/contextive/package.json | 8.5 | Near-clean | Dependency Hygiene: Deprecated: glob |
| REDACTED | 9.3 | Near-clean | Vulnerability-disclosure Policy: REDACTED |
| src/cli/Contextive.Cli.Tests/Contextive.Cli.Tests.fsproj | 9.5 | Near-clean | Dependency Hygiene: Outdated: coverlet.collector |
| src/language-server/Contextive.LanguageServer/Contextive.LanguageServer.fsproj | 9.5 | Near-clean | Dependency Hygiene: Outdated: MediatR |
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 65 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.9, the weighted average across measured dimensions.
What we checked — 65 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, 142 of 601 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
- 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 (5 contributor(s) across 587 commit(s) sampled, automation and bot accounts excluded). One of them holds 99% of the history; the other 4 hold 0.2% each on average, below the 5% at which there is somebody to hand the work to. That is a single maintainer with drive-by contributors, not a team whose knowledge has concentrated — so the bus factor is not applicable and there is nothing here for the owner to act on.
- 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 'src/core/Contextive.Core/Contextive.Core.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 0 deducted marker(s) and the 0.0/KLoC density on this row were taken over this repository's .NET projects ALONE: .fs (2,178 lines, 86% 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. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
- D21 Naming Consistency — not measured this run — 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 — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22's deterministic call-shape 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. This says nothing about whether that surface is consistent.
- 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.
- D39 IL Efficiency — 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. IL NOT MEASURED: the analyzer's own build of this repository failed for an ENVIRONMENT reason (exit 1) — MSBuild's engine or the CLR gave up, or our image does not carry the SDK band/targeting pack this repository needs. This is OUR limitation, not a defect in the repo, and it is not a statement that this repository fails to build. D18 owns the question of whether this repository builds; it was not answered here.
- AXB2 Runtime readiness — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `npm run` found no package.json in the folder where our sandbox ran it. This is a limit of our sandbox, not of your repository. (rule: no-root-manifest). The renderer reported: the dev server (`npm run dev`) exited before it served a page. Likely cause (our sandbox): `npm run` found no package.json in the folder where our sandbox ran it. This is a limit of our sandbox, not of your repository. Last output: "npm error code ENOENT / npm error syscall open / npm error path <repo>/package.json / npm error errno -2 / npm error enoent Could not read package.json: Error: ENOENT: no such file or directory, open '<repo>/package.json' / npm error enoent This is related to npm not being able to find a file. / npm error enoent / npm error A complete log of this run can be found in: <path>" No runtime evidence was gathered.
- AXR1 Runtime accessibility — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via DevServer (dev). the dev server (`npm run dev`) exited before it served a page. Likely cause (our sandbox): `npm run` found no package.json in the folder where our sandbox ran it. This is a limit of our sandbox, not of your repository. Last output: "npm error code ENOENT / npm error syscall open / npm error path <repo>/package.json / npm error errno -2 / npm error enoent Could not read package.json: Error: ENOENT: no such file or directory, open '<repo>/package.json' / npm error enoent This is related to npm not being able to find a file. / npm error enoent / npm error A complete log of this run can be found in: <path>" No runtime evidence was gathered.
- M3 Folder & project structure — 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. Whether the tests sit apart from production code is not visible here, because the suite is not in a form this pass reads. The test-separation credit is granted rather than withheld: this is a gap in the analyzer's language coverage, not a finding about the repository's tests. You can widen what we reach: keep the test surface somewhere a reader can find it without opening a binary — an exported/checked-in test source tree beside the production code makes the suite reviewable, diffable and discoverable by tooling.
- 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.
- P1 CI/CD gates — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. A CI pipeline exists and the word "test" appears, but no explicit test-runner invocation (your stack's test command, or a test job) was matched — so either the gate runs tests through a step this pass could not recognise, or "test" is incidental here (a path, "latest", a reporter). Which of the two it is cannot be settled from this dimension's evidence; the coverage dimensions report whether a suite exists at all. You can widen what we reach: name the test runner explicitly in the pipeline step (your stack's test command, or a job named for the suite) so the gate is unambiguous to a reader and to this pass.
- P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
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.
- D7 Architectural Integrity: Layering is checked against detected/declared rules — an architecture whose boundaries live in convention or in code review, not in a rule a scanner can read, is not enforced here.
- 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.
- D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
- D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- 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
0 method(s) exceeded the cyclomatic complexity threshold of 15.
D2 · Cognitive Complexity
0 method(s) exceeded the cognitive complexity threshold of 15.
D3 · God Classes
0 god class(es) detected.
D4 · Code Duplication
1 duplicated block group(s) detected.
What to do
- Resolve the 1 Duplicated block (8 lines × 2) finding(s) in Code Duplication — start with CandidateTerms.fs. — One of this dimension's main actionable groups (1 warning-level).
- Enforce Code Duplication in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D5 · Coupling
1 projects, 0 dependency cycle(s), 0 unstable depended-on project(s).
D7 · Architectural Integrity
No mechanizable ADR was identified, so enforcement is not measured. Cycles found: 0.
What to do
- Enforce Architectural Integrity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D11 · Test Reliability
0 flaky across 3 measured tier(s). unit: measured (0 flaky); e2e: measured (0 flaky); JavaScript/TypeScript (jest via `npm ci --ignore-scripts` in src/vscode/contextive/ (0 tests)): measured (0 flaky).
What to do
- Resolve the 1 Test suite declares a test script but contains no test files finding(s) in Test Reliability. — One of this dimension's main actionable groups (1 issue-level).
D12 · Dependency Hygiene
120 outdated, 0 vulnerable, 1 deprecated packages. Those are the NuGet packages; this repository's npm dependencies were read too — 330 outdated of 492 package(s) across 3 lockfile(s).
What to do
- Resolve the 17 Outdated (npm) finding(s) in Dependency Hygiene. — One of this dimension's main actionable groups (17 recommendation-level).
- Resolve the 5 Outdated finding(s) in Dependency Hygiene — start with Contextive.Cli.Tests.fsproj, Contextive.LanguageServer.fsproj. — One of this dimension's main actionable groups (5 recommendation-level).
- Resolve the 2 Deprecated finding(s) in Dependency Hygiene — start with package.json. — One of this dimension's main actionable groups (2 warning-level).
- Enforce Dependency Hygiene in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D14 · License Compliance
0 of 157 packages use a banned license. ★ DEPTH: this repository's MSBuild projects declare 3 direct `PackageReference`(s), and 152 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
No churn × complexity hotspots in the window.
D17 · Explicit Debt
0 deducted debt markers + unmeasured dead symbols across 33 LoC in the .NET projects (0.0/KLoC) → score 10.0. Dead code not measured: the solution did not load cleanly, so the reference search was skipped. Measured on the .NET source only: .fs (86% of production source) was not read, and carries at least 0 uncounted task marker(s) in 0 file(s).
D19 · Documentation Quality
1 of 2 documentation facets pass in full; short on: F2 example. 18 document(s) read across 5 unit(s).
What to do
- Resolve the 1 Documentation finding(s) in Documentation Quality — start with README.md. — One of this dimension's main actionable groups (1 recommendation-level).
D20 · ADR Quality
1 of 9 evaluated ADRs have a defect readable from the log itself (a missing or empty section, no title, a single option, consequences with no cost, no status, a missing enforcement field, a status the log contradicts, a dangling link, an unlinked second decision on one question, a date that is no calendar day). How well each record argues its case is not measured.
D26 · Project Cohesion
0 of 1 projects flagged as possibly oversized/incoherent.
D27 · Navigability
87 % of calls cross a namespace and 4 % 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)
43 finding(s): 0 critical, 40 high, 3 medium, 0 low. 26 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. semgrep hit a parse error in 2 file(s) — `src/intellij/contextive/gradlew` (line 74, line 180), `src/language-server/Contextive.LanguageServer.Tests/fixtures/completion_tests/invalid_schema2.yml` — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them. Separately, one or more rules could not re-parse an embedded snippet in 3 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 8 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (4), REDACTED (3), REDACTED. — One of this dimension's main actionable groups (8 issue-level).
- Resolve the 6 REDACTED finding(s) charged to Static Analysis (SAST) — the other 26 are reported here at file:line but scored by D36 (supply-chain provenance), which charges them once. — One of this dimension's main actionable groups (32 issue-level, 6 of them charged here).
- Resolve the 3 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (3 warning-level).
D30 · Dependency Vulnerabilities
69 finding(s): 6 critical, 46 high, 12 medium, 5 low.
What to do
- Resolve the 45 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (43), REDACTED (2). — One of this dimension's main actionable groups (45 issue-level).
- Resolve the 6 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (6). — One of this dimension's main actionable groups (6 issue-level).
- Resolve the 1 High vulnerability finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
D34 · Knowledge Freshness
14 of 14 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is src/vscode/contextive/src/fable_vscode/Fable.Import.VSCode.LanguageServer.fs. Counted over 14 of the 40 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
What to do
- Resolve the 14 Orphaned file finding(s) in Knowledge Freshness — start with Fable.Import.VSCode.LanguageServer.fs, GlossaryManager.fs, Completion.fs. — One of this dimension's main actionable groups (14 recommendation-level).
- Resolve the 1 Orphaned files with no living knowledge finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
D35 · Change Coupling
Strongest change-coupling: build.fsx↔build.fsx 64%; build.fsx↔build.fsx 60%
What to do
- Resolve the 2 Boundary-crossing change coupling finding(s) in Change Coupling — start with build.fsx (2). — One of this dimension's main actionable groups (2 issue-level).
D36 · Supply-chain Provenance & Signing
0/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).
What to do
- Resolve the 3 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (3 warning-level).
- 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).
D37 · Vulnerability-disclosure Policy
A vulnerability-disclosure policy (REDACTED) is present but lists no reporting contact.
What to do
- Resolve the 1 REDACTED finding(s) in Vulnerability-disclosure Policy — start with REDACTED. — One of this dimension's main actionable groups (1 recommendation-level).
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 10 platform declaration(s) and 9 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
GD1 · Unfinished & placeholder code
IC1 · Incompleteness & stubs
M1 · Documentation (README)
What to do
- Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
M2 · Architecture documentation
What to do
- Grow the ADR log (currently 9) — reach 20 to raise the maturity tier; document significant decisions as they're made.
M3 · Folder & project structure
M4 · Documentation accuracy
P1 · CI/CD gates
What to do
- Run the test suite in CI via an explicit runner step (`dotnet test` for the toolchain this pipeline already uses) and gate merges on it.
P10 · Library API & versioning
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 8 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.
- `src/cli/Contextive.Cli.Tests/Contextive.Cli.Tests.fsproj` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`. — src/cli/Contextive.Cli.Tests/Contextive.Cli.Tests.fsproj:13
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
PF3 · Async & latency hygiene
X1 · Async correctness
X12 · Unreachable branch
X13 · Undrained process stream
X14 · Bypassable address classification
X15 · Unvalidated length from an untrusted reader
X16 · Unfloored truncation loop
X17 · Uncapped recursion over a caller-supplied document
X18 · Disposal-pattern correctness
X19 · Unrestored process-global state
X20 · Mistyped argument guard
X21 · Side-effecting pattern guard
X22 · Contradicted release guard
X23 · Unguarded diagnostic materialisation
X24 · Document value interpolated into markup unescaped
X25 · Inert configuration knob
X26 · Unsynchronised callback handoff
X27 · Collection changed while being enumerated
X28 · Index access outside its own emptiness guard
X29 · Per-element action decided by a fixed element
X3 · Exception handling
X30 · Support guard that admits what it rejects
X32 · Type resolved by simple name across every loaded assembly
X4 · Structured logging
X5 · Nullable reference types
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 100% | Exemplary | Solid. |
| Architecture | 97% | Exemplary | Solid. |
| Maturity | 71% | Adequate — gated by D34 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 55% | Adequate — gated by P3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 50% | Weak — gated by D29, 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 — 54 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
- AX8 Test isolation — no test/production split to check
- AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXR1 Runtime accessibility — the dev server (`npm run dev`) exited before it served a page. Likely cause (our sandbox): `npm run` found no package.json in the folder where our sandbox ran it. This is a limit of our sandbox, not of your repository. Last output: "npm error code ENOENT / npm error syscall open / npm error path <repo>/package.json / npm error errno -2 / npm error enoent Could not read package.json: Error: ENOENT: no such file or directory, open '<repo>/package.json' / npm error enoent This is related to npm not being able to find a file. / npm error enoent / npm error A complete log of this run can be found in: <path>" No runtime evidence was gathered. This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
- C1 Data Protection — 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 — ~4073 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, .kt, .ts, 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#, JavaScript, Kotlin not measured.
- D22 Internal API Consistency — API consistency is measured on C# only; the exposed JavaScript surface was not measured.
- D23 Boundary Type-Coupling — small single-context codebase (2,643 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, .kt source were not judged.
- D25 ADR Conformance — None of 8 binding record(s) states a rule in checkable form (a backticked element with a prohibition, or an `adr-rules` block), so conformance cannot be read from the code. Write the rule as an `adr-rules` block (`forbid:` a symbol, a package or a dependency) to make it checkable.
- 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.
- D39 IL Efficiency — IL not measured — the analyzer's build of the target did not succeed
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D6 Cohesion (LCOM4) — Cohesion (LCOM4) was not measured: of the 6 type(s) found, none both holds instance state and has two or more methods whose shared use of it could be read (4 with fewer than two methods, 1 stateless, 1 stub-like), so LCOM4 is undefined for every type in this repository. Not scored — the metric does not apply here, and this is not a finding about this repository.
- D8 Code Coverage — Coverage NOT MEASURED: the .NET half measured 82.1%; the JavaScript/TypeScript half could not be measured — the jest suite in src/vscode/contextive/ ran and not one test passed (No tests found, exiting with code 1), so the coverage would describe the failed run, not the code. This repository's production source spans both ecosystems, and no partial figure is published as if it were the whole: coverage is excluded from the score rather than counted as a near-zero. The named suite step is one the repository's maintainers can perform; once it passes, the real number is measured on the next scan. Alternatively, commit the lcov/Cobertura report your CI produces and it is read without a re-run.
- 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): 17 value object(s); 2 domain event(s); its domain events are published by services or handlers — no domain entity raises one
- ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
- ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- 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 — no coverage report found on disk — produce a coverage report in a standard format (Cobertura — `dotnet test --collect:"XPlat Code Coverage"` with a `coverlet.collector` PackageReference) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures, or wire coverage collection into CI, to enable this cross-layer check
- PF1 Benchmark discipline — 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.
- X10 Duplicated predicate — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X2 Cancellation propagation — no async method does work a token could cancel
- 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 — 95 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Boundary-crossing change coupling: build.fsx ↔ build.fsx src/intellij/build.fsx:1
- Boundary-crossing change coupling: build.fsx ↔ build.fsx src/language-server/build.fsx:1
- Test suite declares a test script but contains no test files: src/vscode/contextive/
- REDACTED
Serious — 26 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Deprecated: Microsoft.Testing.Platform.MSBuild
- Deprecated: glob src/vscode/contextive/package.json:79
- REDACTED
- REDACTED
- REDACTED
- Duplicated block (8 lines × 2) src/core/Contextive.Core/CandidateTerms.fs:17
- Coverage not measured — JavaScript/TypeScript suite
- NuGet dependencies are not locked
Minor — 52 finding(s)
- Outdated (npm): @astrojs/mdx
- Outdated (npm): @shikijs/core
- Outdated (npm): @shikijs/engine-javascript
- Outdated (npm): @shikijs/engine-oniguruma
- Outdated (npm): @shikijs/langs
- Outdated (npm): @shikijs/themes
- Outdated (npm): @shikijs/types
- Outdated (npm): @types/node
- Outdated (npm): balanced-match
- Outdated (npm): brace-expansion
- Outdated (npm): diff
- Outdated (npm): entities
- Outdated (npm): i18next
- Outdated (npm): minimatch
- Outdated (npm): nanoid
- Outdated (npm): postcss-nested
- Outdated (npm): shiki
- Orphaned file src/vscode/contextive/src/fable_vscode/Fable.Import.VSCode.LanguageServer.fs:1
- Orphaned file src/language-server/Contextive.LanguageServer/GlossaryManager.fs:1
- Orphaned file src/language-server/Contextive.LanguageServer/Completion.fs:1
- Orphaned file src/core/Contextive.Core/GlossaryFile.fs:1
- Orphaned file src/language-server/Contextive.LanguageServer/Hover.fs:1
- Orphaned file src/language-server/Contextive.LanguageServer/GlossaryFileInitializer.fs:1
- Orphaned file src/language-server/Contextive.LanguageServer/Glossary.fs:1
- Orphaned file src/core/Contextive.Core/GlossaryFileSchema.fs:1
- Orphaned file src/language-server/Contextive.LanguageServer/Rendering.fs:1
- Orphaned file src/language-server/Contextive.LanguageServer/Server.fs:1
- Orphaned file src/language-server/Contextive.LanguageServer/TextDocument.fs:1
- Orphaned file src/vscode/contextive/src/Extension.fs:1
- Orphaned file src/language-server/Contextive.LanguageServer/DefaultGlossaryFileProvider.fs:1
- Orphaned file src/language-server/Contextive.LanguageServer/Tokeniser.fs:1
- Outdated: coverlet.collector src/cli/Contextive.Cli.Tests/Contextive.Cli.Tests.fsproj:13
- Outdated: MediatR src/language-server/Contextive.LanguageServer/Contextive.LanguageServer.fsproj:31
- Outdated: DiffEngine
- Outdated: Verify
- Outdated: Verify.Expecto
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Deprecated: read-pkg-up REDACTED:5843
- Documentation: no build, run or usage example src/vscode/contextive/README.md:1
- ADR has no Consequences section docs/adr/0004-testing-framework-selection.md:1
- Orphaned files with no living knowledge
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- No SAST
- No dependency-update automation src/cli/Contextive.Cli.Tests/Contextive.Cli.Tests.fsproj:13
Minor — 428 finding(s)
- Outdated (npm): @astrojs/check
- Outdated (npm): @astrojs/compiler
- Outdated (npm): @astrojs/internal-helpers
- Outdated (npm): @astrojs/language-server
- Outdated (npm): @astrojs/markdown-remark
- Outdated (npm): @astrojs/prism
- Outdated (npm): @astrojs/sitemap
- Outdated (npm): @astrojs/starlight
- Outdated (npm): @astrojs/telemetry
- Outdated (npm): @astrojs/yaml2ts
- Outdated (npm): @babel/helper-string-parser
- Outdated (npm): @babel/helper-validator-identifier
- Outdated (npm): @babel/parser
- Outdated (npm): @babel/runtime
- Outdated (npm): @babel/types
- Outdated (npm): @ctrl/tinycolor
- Outdated (npm): @emmetio/css-parser
- Outdated (npm): @emnapi/runtime
- Outdated (npm): @esbuild/aix-ppc64
- Outdated (npm): @esbuild/android-arm
- Outdated (npm): @esbuild/android-arm64
- Outdated (npm): @esbuild/android-x64
- Outdated (npm): @esbuild/darwin-arm64
- Outdated (npm): @esbuild/darwin-x64
- Outdated (npm): @esbuild/freebsd-arm64
- Outdated: FSharp.Core
- Outdated: Humanizer
- Outdated: Humanizer.Core
- Outdated: Humanizer.Core.af
- Outdated: Humanizer.Core.ar
- Outdated: Humanizer.Core.az
- Outdated: Humanizer.Core.bg
- Outdated: Humanizer.Core.cs
- Outdated: Humanizer.Core.da
- Outdated: Humanizer.Core.de
- Outdated: Humanizer.Core.el
- Outdated: Humanizer.Core.es
- Outdated: Humanizer.Core.fa
- Outdated: Humanizer.Core.fr
- Outdated: Humanizer.Core.he
- Outdated: Humanizer.Core.hr
- Outdated: Humanizer.Core.hu
- Outdated: Humanizer.Core.hy
- Outdated: Humanizer.Core.id
- Outdated: Humanizer.Core.is
- Outdated: Humanizer.Core.it
- Outdated: Humanizer.Core.ja
- Outdated: Humanizer.Core.ku
- Outdated: Humanizer.Core.lv
- Outdated: Humanizer.Core.mt
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-b94e6bcaf4394b6f9da1276c487063e4/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-b94e6bcaf4394b6f9da1276c487063e4/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 . | 43 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | dotnet | — | dotnet list src/Contextive.sln package --vulnerable --include-transitive --format json | 69 | 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 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . --skip-db-update | 0 | artifacts/raw/trivy-fs.json |