Executive summary
ionide/ionide-vscode-fsharp falls short of our standard for production because its Testing dimensions are rated Critical, and the project has no automated tests. It scores 58 out of 100, which alone would earn Adequate, but it is rated Weak: a rating can't sit more than one step above its weakest group.
Production Readiness, at 52, is the weakest lens and counts most in the score. The best first step for the work it takes is updating the outdated dependencies, worth about 3 points. Adding automated tests would lift Production Readiness itself, worth about 6 points. Raising Production Readiness to 70 would lift the score to about 61.
Ten pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. One automatic update takes new releases before a bad one can be spotted, and one secret can leak from the build pipeline. Pinning each tool to an exact version, setting a waiting period for automatic updates and limiting the secret to its own step would close these risks. Correcting the flagged pipeline settings would fix the three weaknesses in the build pipeline's configuration, and fixing the weaknesses the scanner points to would deal with the security weakness in the code.
The product code is 9,218 lines, about €9,600 to rebuild.
If Production Readiness rose from 52 to 70, the lowest score rated Strong, the score would rise from 58 to about 61.
New since the last survey: 22 findings
- Cyclomatic Complexity · SolutionExplorer.activate (cyclomatic 76) src/Components/SolutionExplorer.fs
- Cyclomatic Complexity · SolutionExplorer.createProvider (cyclomatic 43) src/Components/SolutionExplorer.fs
- Cyclomatic Complexity · LanguageService.getOptions (cyclomatic 40) src/Core/LanguageService.fs
- Cyclomatic Complexity · SolutionExplorer.getSolutionModel (cyclomatic 20) src/Components/SolutionExplorer.fs
- Cyclomatic Complexity · SolutionExplorer.newProject (cyclomatic 16) src/Components/SolutionExplorer.fs
- Cognitive Complexity · SolutionExplorer.activate (cognitive 91) src/Components/SolutionExplorer.fs
- Cognitive Complexity · SolutionExplorer.newProject (cognitive 47) src/Components/SolutionExplorer.fs
- Cognitive Complexity · LanguageService.getOptions (cognitive 36) src/Core/LanguageService.fs
- Cognitive Complexity · Debugger.makeDebugConfigFor (cognitive 25) src/Components/Debugger.fs
- Cognitive Complexity · Panel.mapContent (cognitive 22) src/Components/InfoPanel.fs
- Cognitive Complexity · Document.|FSharp|CSharp|VB|FSharpScript|Markdown|Other| (cognitive 21) src/Core/Utils.fs
- Cognitive Complexity · SolutionExplorer.getSolutionModel (cognitive 20) src/Components/SolutionExplorer.fs
- Cognitive Complexity · Watcher.handler (cognitive 17) src/Components/Fsi.fs
- Churn × Complexity Hotspots · Hotspot: src/Core/LanguageService.fs src/Core/LanguageService.fs
- Churn × Complexity Hotspots · Hotspot: src/Components/SolutionExplorer.fs src/Components/SolutionExplorer.fs
- Churn × Complexity Hotspots · Hotspot: src/Components/TestExplorer.fs src/Components/TestExplorer.fs
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Dependency Vulnerabilities · REDACTED
Fixed since the last survey: 47 findings
- Code Duplication · Duplicated block (11 lines × 2) src/Components/Diagnostics.fs
- Code Duplication · Duplicated block (10 lines × 3) src/Components/Diagnostics.fs
- Code Duplication · Duplicated block (9–10 lines × 2) src/Components/QuickInfo.fs
- Dependency Hygiene · Vulnerable: NuGet.Common
- Dependency Hygiene · Vulnerable: NuGet.Packaging
- Dependency Hygiene · Vulnerable: NuGet.Protocol
- Dependency Hygiene · Vulnerable: System.Formats.Asn1
- Dependency Hygiene · Vulnerable: System.Security.Cryptography.Pkcs
- Dependency Hygiene · Deprecated: axios package.json
- Dependency Hygiene · Deprecated: vscode-debugadapter package.json
- Static Analysis (SAST) · High: REDACTED REDACTED
- Static Analysis (SAST) · High: REDACTED REDACTED
- Static Analysis (SAST) · Medium: watchdog-eol-action-major-in-workflow REDACTED
- Static Analysis (SAST) · Medium: watchdog-eol-action-major-in-workflow REDACTED
- Dependency Vulnerabilities · Critical CVE: NuGet.Packaging 6.4.0
- Dependency Vulnerabilities · Critical CVE: [GHSA redacted] yarn.lock
- Dependency Vulnerabilities · Critical CVE: [GHSA redacted] yarn.lock
- Dependency Vulnerabilities · High CVE: NuGet.Common 6.4.0
- Dependency Vulnerabilities · High CVE: NuGet.Protocol 6.4.0
- Dependency Vulnerabilities · High CVE: System.Formats.Asn1 7.0.0
- Dependency Vulnerabilities · High CVE: System.Security.Cryptography.Pkcs 7.0.1
- Dependency Vulnerabilities · High CVE: [GHSA redacted] yarn.lock
- Dependency Vulnerabilities · High CVE: [GHSA redacted] yarn.lock
- Dependency Vulnerabilities · High CVE: [GHSA redacted] yarn.lock
- Dependency Vulnerabilities · High CVE: [GHSA redacted] yarn.lock
- Dependency Vulnerabilities · High CVE: [GHSA redacted] yarn.lock
- Dependency Vulnerabilities · High CVE: [GHSA redacted] yarn.lock
- Dependency Vulnerabilities · High CVE: [GHSA redacted] yarn.lock
- Dependency Vulnerabilities · High CVE: [GHSA redacted] yarn.lock
- Dependency Vulnerabilities · High CVE: [GHSA redacted] yarn.lock
- Dependency Vulnerabilities · High CVE: [GHSA redacted] yarn.lock
- Dependency Vulnerabilities · High CVE: [GHSA redacted] yarn.lock
- Dependency Vulnerabilities · High CVE: [GHSA redacted] yarn.lock
- Dependency Vulnerabilities · High CVE: [GHSA redacted] yarn.lock
- Dependency Vulnerabilities · High vulnerability: [GHSA redacted] yarn.lock
- Dependency Vulnerabilities · High vulnerability: [GHSA redacted] yarn.lock
- Dependency Vulnerabilities · High CVE: [GHSA redacted] yarn.lock
- Dependency Vulnerabilities · High CVE: [GHSA redacted] yarn.lock
- Dependency Vulnerabilities · High CVE: [GHSA redacted] yarn.lock
- Dependency Vulnerabilities · Medium CVE: [GHSA redacted] yarn.lock
- Dependency Vulnerabilities · Medium CVE: [GHSA redacted] yarn.lock
- IaC & Container Security · Critical IaC: DS-0010 .gitpod/Dockerfile
- IaC & Container Security · High IaC: WD-DOCKER-0001 .gitpod/Dockerfile
- IaC & Container Security · Medium IaC: DS-0001 .gitpod/Dockerfile
- Supply-chain Provenance & Signing · Workflow holding a long-lived secret is unscoped REDACTED
- Supply-chain Provenance & Signing · PR-triggered workflow without a permissions block REDACTED
- Platform End-of-Life · End-of-life runtime: Node.js 12 .tool-versions
Rebuild cost: about €9,600 · Estimate
| Cost to rebuild | €3,200 to €16,000, for 53 to 168 hours of work, under 0.1 person-years for one engineer |
|---|---|
| Difficulty of the problem | Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.8 at a score of 58. 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: 9,218 lines of product code |
| What it is not | Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one. |
Top priorities
Diagnosis: what the measurements show together
Architecture: which parts of the code depend on which
| uses → | 1 Ionide.VSCode.FSharp.Import.XPath | 2 Ionide.VSCode.FSharp.TestExplorer.TestName | 3 Fable.Import.VSCode | 4 Fable.Import.VSCode.Vscode.Comments | 5 Fable.Import.VSCode.Vscode.Extensions | 6 Fable.Import.VSCode.Vscode.Notebooks | 7 Fable.Import.VSCode.Vscode.Scm | 8 Fable.Import.VSCode.Vscode.Tests | 9 Ionide.VSCode.FSharp.TestExplorer.TrxParser | 10 Fable.Import.VSCode.Vscode.Authentication | 11 Fable.Import.VSCode.Vscode.Commands | 12 Fable.Import.VSCode.Vscode.Debug | 13 Fable.Import.VSCode.Vscode.Env | 14 Fable.Import.VSCode.Vscode.Languages | 15 Fable.Import.VSCode.Vscode.Tasks | 16 Fable.Import.VSCode.Vscode.Window | 17 Fable.Import.VSCode.Vscode.Workspace | 18 Fable.Import.VSCode.Vscode | 19 Fable.Import.LanguageServer.Client | 20 Ionide.VSCode.FSharp.CodeLensHelpers | 21 Ionide.VSCode.FSharp.DTO | 22 Ionide.VSCode.FSharp.LineLensShared.Documents | 23 Ionide.VSCode.FSharp.Logging | 24 Fable.Import.LanguageServer | 25 Ionide.VSCode.FSharp.Debugger | 26 Ionide.VSCode.FSharp.Gitignore | 27 Ionide.VSCode.FSharp.LineLensShared | 28 Ionide.VSCode.FSharp.MSBuild | 29 Ionide.VSCode.FSharp.Notifications | 30 Ionide.VSCode.FSharp.Project | 31 Ionide.VSCode.FSharp.TestExplorer | 32 Ionide.VSCode.FSharp.TestExplorer.TestItem | 33 Ionide.VSCode.FSharpModule | 34 Ionide.VSCode.FSharp.LanguageService | 35 Ionide.VSCode.FSharp.LineLens.DecorationUpdate | 36 Ionide.VSCode.FSharp.LineLensShared.DecorationUpdateModule | 37 Ionide.VSCode.FSharp.PipelineHints.PipelineDecorationUpdate | 38 Ionide.VSCode.FSharp.Project.CurrentWorkspaceConfiguration | 39 Ionide.VSCode.FSharp.SolutionExplorer | 40 Ionide.VSCode.FSharp.TestExplorer.Interactions |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 Ionide.VSCode.FSharp.Import.XPath | ||||||||||||||||||||||||||||||||||||||||
| 2 Ionide.VSCode.FSharp.TestExplorer.TestName | ||||||||||||||||||||||||||||||||||||||||
| 3 Fable.Import.VSCode | 1 | |||||||||||||||||||||||||||||||||||||||
| 4 Fable.Import.VSCode.Vscode.Comments | 1 | |||||||||||||||||||||||||||||||||||||||
| 5 Fable.Import.VSCode.Vscode.Extensions | 2 | |||||||||||||||||||||||||||||||||||||||
| 6 Fable.Import.VSCode.Vscode.Notebooks | 4 | |||||||||||||||||||||||||||||||||||||||
| 7 Fable.Import.VSCode.Vscode.Scm | 3 | |||||||||||||||||||||||||||||||||||||||
| 8 Fable.Import.VSCode.Vscode.Tests | 1 | |||||||||||||||||||||||||||||||||||||||
| 9 Ionide.VSCode.FSharp.TestExplorer.TrxParser | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 10 Fable.Import.VSCode.Vscode.Authentication | 1 | 7 | ||||||||||||||||||||||||||||||||||||||
| 11 Fable.Import.VSCode.Vscode.Commands | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 12 Fable.Import.VSCode.Vscode.Debug | 1 | 16 | ||||||||||||||||||||||||||||||||||||||
| 13 Fable.Import.VSCode.Vscode.Env | 1 | 4 | ||||||||||||||||||||||||||||||||||||||
| 14 Fable.Import.VSCode.Vscode.Languages | 1 | 50 | ||||||||||||||||||||||||||||||||||||||
| 15 Fable.Import.VSCode.Vscode.Tasks | 1 | 10 | ||||||||||||||||||||||||||||||||||||||
| 16 Fable.Import.VSCode.Vscode.Window | 1 | 47 | ||||||||||||||||||||||||||||||||||||||
| 17 Fable.Import.VSCode.Vscode.Workspace | 1 | 29 | ||||||||||||||||||||||||||||||||||||||
| 18 Fable.Import.VSCode.Vscode | 72 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||
| 19 Fable.Import.LanguageServer.Client | 13 | |||||||||||||||||||||||||||||||||||||||
| 20 Ionide.VSCode.FSharp.CodeLensHelpers | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 21 Ionide.VSCode.FSharp.DTO | 2 | |||||||||||||||||||||||||||||||||||||||
| 22 Ionide.VSCode.FSharp.LineLensShared.Documents | 5 | |||||||||||||||||||||||||||||||||||||||
| 23 Ionide.VSCode.FSharp.Logging | 2 | |||||||||||||||||||||||||||||||||||||||
| 24 Fable.Import.LanguageServer | 4 | 4 | ||||||||||||||||||||||||||||||||||||||
| 25 Ionide.VSCode.FSharp.Debugger | 5 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 26 Ionide.VSCode.FSharp.Gitignore | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 27 Ionide.VSCode.FSharp.LineLensShared | 7 | 1 | ||||||||||||||||||||||||||||||||||||||
| 28 Ionide.VSCode.FSharp.MSBuild | 8 | 2 | 1 | |||||||||||||||||||||||||||||||||||||
| 29 Ionide.VSCode.FSharp.Notifications | 4 | 1 | ||||||||||||||||||||||||||||||||||||||
| 30 Ionide.VSCode.FSharp.Project | 5 | 7 | 1 | |||||||||||||||||||||||||||||||||||||
| 31 Ionide.VSCode.FSharp.TestExplorer | 6 | 1 | ||||||||||||||||||||||||||||||||||||||
| 32 Ionide.VSCode.FSharp.TestExplorer.TestItem | 1 | 8 | 3 | |||||||||||||||||||||||||||||||||||||
| 33 Ionide.VSCode.FSharpModule | 3 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 34 Ionide.VSCode.FSharp.LanguageService | 6 | 12 | 1 | 2 | ||||||||||||||||||||||||||||||||||||
| 35 Ionide.VSCode.FSharp.LineLens.DecorationUpdate | 4 | 4 | 2 | |||||||||||||||||||||||||||||||||||||
| 36 Ionide.VSCode.FSharp.LineLensShared.DecorationUpdateModule | 1 | 1 | 1 | 2 | ||||||||||||||||||||||||||||||||||||
| 37 Ionide.VSCode.FSharp.PipelineHints.PipelineDecorationUpdate | 3 | 2 | 1 | |||||||||||||||||||||||||||||||||||||
| 38 Ionide.VSCode.FSharp.Project.CurrentWorkspaceConfiguration | 1 | 2 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 39 Ionide.VSCode.FSharp.SolutionExplorer | 1 | 4 | 3 | 1 | ||||||||||||||||||||||||||||||||||||
| 40 Ionide.VSCode.FSharp.TestExplorer.Interactions | 1 | 1 | 7 | 2 | 3 |
3→18 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.
4→18 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.
5→18 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.
6→18 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.
7→18 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.
8→18 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.
9→1 Ionide.VSCode.FSharp.TestExplorer.TrxParser uses Ionide.VSCode.FSharp.Import.XPath✕
- Connections
- 1 pair of types, where a type in Ionide.VSCode.FSharp.TestExplorer.TrxParser uses a type in Ionide.VSCode.FSharp.Import.XPath.
- The types involved
Ionide.VSCode.FSharp.TestExplorer.TrxParser.TrxParser→Ionide.VSCode.FSharp.Import.XPath.XPathSelector
- Direction
- Ionide.VSCode.FSharp.TestExplorer.TrxParser uses Ionide.VSCode.FSharp.Import.XPath, so a change to Ionide.VSCode.FSharp.Import.XPath can break Ionide.VSCode.FSharp.TestExplorer.TrxParser, while a change to Ionide.VSCode.FSharp.TestExplorer.TrxParser can't break Ionide.VSCode.FSharp.Import.XPath.
- Position
- Below the diagonal: Ionide.VSCode.FSharp.TestExplorer.TrxParser uses a module listed above it, which is the healthy direction.
9→2 Ionide.VSCode.FSharp.TestExplorer.TrxParser uses Ionide.VSCode.FSharp.TestExplorer.TestName✕
- Connections
- 1 pair of types, where a type in Ionide.VSCode.FSharp.TestExplorer.TrxParser uses a type in Ionide.VSCode.FSharp.TestExplorer.TestName.
- The types involved
Ionide.VSCode.FSharp.TestExplorer.TrxParser.TrxParser→Ionide.VSCode.FSharp.TestExplorer.TestName.NameHierarchy`1
- Direction
- Ionide.VSCode.FSharp.TestExplorer.TrxParser uses Ionide.VSCode.FSharp.TestExplorer.TestName, so a change to Ionide.VSCode.FSharp.TestExplorer.TestName can break Ionide.VSCode.FSharp.TestExplorer.TrxParser, while a change to Ionide.VSCode.FSharp.TestExplorer.TrxParser can't break Ionide.VSCode.FSharp.TestExplorer.TestName.
- Position
- Below the diagonal: Ionide.VSCode.FSharp.TestExplorer.TrxParser uses a module listed above it, which is the healthy direction.
10→3 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.
10→18 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.
11→3 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.
11→18 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.
12→3 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.
12→18 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.
13→3 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.
13→18 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.
14→3 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.
14→18 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.
15→3 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.
15→18 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.
16→3 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.
16→18 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.
17→3 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.
17→18 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.
18→3 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.
18→4 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.
18→5 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.
18→6 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.
18→7 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.
18→8 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.
18→10 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.
18→11 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.
18→12 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.
18→13 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.
18→14 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.
18→15 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.
18→16 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.
18→17 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.
19→18 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.
20→3 Ionide.VSCode.FSharp.CodeLensHelpers uses Fable.Import.VSCode✕
- Connections
- 1 pair of types, where a type in Ionide.VSCode.FSharp.CodeLensHelpers uses a type in Fable.Import.VSCode.
- The types involved
Ionide.VSCode.FSharp.CodeLensHelpers.CodeLensHelpers→Fable.Import.VSCode.Thenable`1
- Direction
- Ionide.VSCode.FSharp.CodeLensHelpers uses Fable.Import.VSCode, so a change to Fable.Import.VSCode can break Ionide.VSCode.FSharp.CodeLensHelpers, while a change to Ionide.VSCode.FSharp.CodeLensHelpers can't break Fable.Import.VSCode.
- Position
- Below the diagonal: Ionide.VSCode.FSharp.CodeLensHelpers uses a module listed above it, which is the healthy direction.
20→18 Ionide.VSCode.FSharp.CodeLensHelpers uses Fable.Import.VSCode.Vscode✕
- Connections
- 2 pairs of types, where a type in Ionide.VSCode.FSharp.CodeLensHelpers uses a type in Fable.Import.VSCode.Vscode.
- The types involved
Ionide.VSCode.FSharp.CodeLensHelpers.CodeLensHelpers→Fable.Import.VSCode.Vscode.ExtensionContextIonide.VSCode.FSharp.CodeLensHelpers.CustomIExports→Fable.Import.VSCode.Vscode.Disposable
- Direction
- Ionide.VSCode.FSharp.CodeLensHelpers uses Fable.Import.VSCode.Vscode, so a change to Fable.Import.VSCode.Vscode can break Ionide.VSCode.FSharp.CodeLensHelpers, while a change to Ionide.VSCode.FSharp.CodeLensHelpers can't break Fable.Import.VSCode.Vscode.
- Position
- Below the diagonal: Ionide.VSCode.FSharp.CodeLensHelpers uses a module listed above it, which is the healthy direction.
21→18 Ionide.VSCode.FSharp.DTO uses Fable.Import.VSCode.Vscode✕
- Connections
- 2 pairs of types, where a type in Ionide.VSCode.FSharp.DTO uses a type in Fable.Import.VSCode.Vscode.
- The types involved
Ionide.VSCode.FSharp.DTO.HighlightingRange→Fable.Import.VSCode.Vscode.RangeIonide.VSCode.FSharp.DTO.TestAdapterEntry→Fable.Import.VSCode.Vscode.Range
- Direction
- Ionide.VSCode.FSharp.DTO uses Fable.Import.VSCode.Vscode, so a change to Fable.Import.VSCode.Vscode can break Ionide.VSCode.FSharp.DTO, while a change to Ionide.VSCode.FSharp.DTO can't break Fable.Import.VSCode.Vscode.
- Position
- Below the diagonal: Ionide.VSCode.FSharp.DTO uses a module listed above it, which is the healthy direction.
22→18 Ionide.VSCode.FSharp.LineLensShared.Documents uses Fable.Import.VSCode.Vscode✕
- Connections
- 5 pairs of types, where a type in Ionide.VSCode.FSharp.LineLensShared.Documents uses a type in Fable.Import.VSCode.Vscode.
- The types involved
Ionide.VSCode.FSharp.LineLensShared.Documents.Cached→Fable.Import.VSCode.Vscode.DecorationOptionsIonide.VSCode.FSharp.LineLensShared.Documents.Cached→Fable.Import.VSCode.Vscode.TextEditorIonide.VSCode.FSharp.LineLensShared.Documents.DocumentInfo→Fable.Import.VSCode.Vscode.UriIonide.VSCode.FSharp.LineLensShared.Documents.Documents→Fable.Import.VSCode.Vscode.DecorationOptionsIonide.VSCode.FSharp.LineLensShared.Documents.Documents→Fable.Import.VSCode.Vscode.Uri
- Direction
- Ionide.VSCode.FSharp.LineLensShared.Documents uses Fable.Import.VSCode.Vscode, so a change to Fable.Import.VSCode.Vscode can break Ionide.VSCode.FSharp.LineLensShared.Documents, while a change to Ionide.VSCode.FSharp.LineLensShared.Documents can't break Fable.Import.VSCode.Vscode.
- Position
- Below the diagonal: Ionide.VSCode.FSharp.LineLensShared.Documents uses a module listed above it, which is the healthy direction.
23→18 Ionide.VSCode.FSharp.Logging uses Fable.Import.VSCode.Vscode✕
- Connections
- 2 pairs of types, where a type in Ionide.VSCode.FSharp.Logging uses a type in Fable.Import.VSCode.Vscode.
- The types involved
Ionide.VSCode.FSharp.Logging.ConsoleAndOutputChannelLogger→Fable.Import.VSCode.Vscode.OutputChannelIonide.VSCode.FSharp.Logging.Logging→Fable.Import.VSCode.Vscode.OutputChannel
- Direction
- Ionide.VSCode.FSharp.Logging uses Fable.Import.VSCode.Vscode, so a change to Fable.Import.VSCode.Vscode can break Ionide.VSCode.FSharp.Logging, while a change to Ionide.VSCode.FSharp.Logging can't break Fable.Import.VSCode.Vscode.
- Position
- Below the diagonal: Ionide.VSCode.FSharp.Logging uses a module listed above it, which is the healthy direction.
24→18 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.
24→19 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.
25→18 Ionide.VSCode.FSharp.Debugger uses Fable.Import.VSCode.Vscode✕
- Connections
- 5 pairs of types, where a type in Ionide.VSCode.FSharp.Debugger uses a type in Fable.Import.VSCode.Vscode.
- The types involved
Ionide.VSCode.FSharp.Debugger.Debugger→Fable.Import.VSCode.Vscode.DebugConfigurationIonide.VSCode.FSharp.Debugger.Debugger→Fable.Import.VSCode.Vscode.DebugConfigurationProviderIonide.VSCode.FSharp.Debugger.Debugger→Fable.Import.VSCode.Vscode.ExtensionContextIonide.VSCode.FSharp.Debugger.Debugger→Fable.Import.VSCode.Vscode.OutputChannelIonide.VSCode.FSharp.Debugger.Debugger→Fable.Import.VSCode.Vscode.Task
- Direction
- Ionide.VSCode.FSharp.Debugger uses Fable.Import.VSCode.Vscode, so a change to Fable.Import.VSCode.Vscode can break Ionide.VSCode.FSharp.Debugger, while a change to Ionide.VSCode.FSharp.Debugger can't break Fable.Import.VSCode.Vscode.
- Position
- Below the diagonal: Ionide.VSCode.FSharp.Debugger uses a module listed above it, which is the healthy direction.
25→21 Ionide.VSCode.FSharp.Debugger uses Ionide.VSCode.FSharp.DTO✕
- Connections
- 1 pair of types, where a type in Ionide.VSCode.FSharp.Debugger uses a type in Ionide.VSCode.FSharp.DTO.
- The types involved
Ionide.VSCode.FSharp.Debugger.Debugger→Ionide.VSCode.FSharp.DTO.Project
- Direction
- Ionide.VSCode.FSharp.Debugger uses Ionide.VSCode.FSharp.DTO, so a change to Ionide.VSCode.FSharp.DTO can break Ionide.VSCode.FSharp.Debugger, while a change to Ionide.VSCode.FSharp.Debugger can't break Ionide.VSCode.FSharp.DTO.
- Position
- Below the diagonal: Ionide.VSCode.FSharp.Debugger uses a module listed above it, which is the healthy direction.
25→23 Ionide.VSCode.FSharp.Debugger uses Ionide.VSCode.FSharp.Logging✕
- Connections
- 1 pair of types, where a type in Ionide.VSCode.FSharp.Debugger uses a type in Ionide.VSCode.FSharp.Logging.
- The types involved
Ionide.VSCode.FSharp.Debugger.Debugger→Ionide.VSCode.FSharp.Logging.ConsoleAndOutputChannelLogger
- Direction
- Ionide.VSCode.FSharp.Debugger uses Ionide.VSCode.FSharp.Logging, so a change to Ionide.VSCode.FSharp.Logging can break Ionide.VSCode.FSharp.Debugger, while a change to Ionide.VSCode.FSharp.Debugger can't break Ionide.VSCode.FSharp.Logging.
- Position
- Below the diagonal: Ionide.VSCode.FSharp.Debugger uses a module listed above it, which is the healthy direction.
26→3 Ionide.VSCode.FSharp.Gitignore uses Fable.Import.VSCode✕
- Connections
- 1 pair of types, where a type in Ionide.VSCode.FSharp.Gitignore uses a type in Fable.Import.VSCode.
- The types involved
Ionide.VSCode.FSharp.Gitignore.Gitignore→Fable.Import.VSCode.Thenable`1
- Direction
- Ionide.VSCode.FSharp.Gitignore uses Fable.Import.VSCode, so a change to Fable.Import.VSCode can break Ionide.VSCode.FSharp.Gitignore, while a change to Ionide.VSCode.FSharp.Gitignore can't break Fable.Import.VSCode.
- Position
- Below the diagonal: Ionide.VSCode.FSharp.Gitignore uses a module listed above it, which is the healthy direction.
26→18 Ionide.VSCode.FSharp.Gitignore uses Fable.Import.VSCode.Vscode✕
- Connections
- 1 pair of types, where a type in Ionide.VSCode.FSharp.Gitignore uses a type in Fable.Import.VSCode.Vscode.
- The types involved
Ionide.VSCode.FSharp.Gitignore.Gitignore→Fable.Import.VSCode.Vscode.ExtensionContext
- Direction
- Ionide.VSCode.FSharp.Gitignore uses Fable.Import.VSCode.Vscode, so a change to Fable.Import.VSCode.Vscode can break Ionide.VSCode.FSharp.Gitignore, while a change to Ionide.VSCode.FSharp.Gitignore can't break Fable.Import.VSCode.Vscode.
- Position
- Below the diagonal: Ionide.VSCode.FSharp.Gitignore uses a module listed above it, which is the healthy direction.
26→23 Ionide.VSCode.FSharp.Gitignore uses Ionide.VSCode.FSharp.Logging✕
- Connections
- 1 pair of types, where a type in Ionide.VSCode.FSharp.Gitignore uses a type in Ionide.VSCode.FSharp.Logging.
- The types involved
Ionide.VSCode.FSharp.Gitignore.Gitignore→Ionide.VSCode.FSharp.Logging.ConsoleAndOutputChannelLogger
- Direction
- Ionide.VSCode.FSharp.Gitignore uses Ionide.VSCode.FSharp.Logging, so a change to Ionide.VSCode.FSharp.Logging can break Ionide.VSCode.FSharp.Gitignore, while a change to Ionide.VSCode.FSharp.Gitignore can't break Ionide.VSCode.FSharp.Logging.
- Position
- Below the diagonal: Ionide.VSCode.FSharp.Gitignore uses a module listed above it, which is the healthy direction.
27→18 Ionide.VSCode.FSharp.LineLensShared uses Fable.Import.VSCode.Vscode✕
- Connections
- 7 pairs of types, where a type in Ionide.VSCode.FSharp.LineLensShared uses a type in Fable.Import.VSCode.Vscode.
- The types involved
Ionide.VSCode.FSharp.LineLensShared.LineLens→Fable.Import.VSCode.Vscode.DecorationRenderOptionsIonide.VSCode.FSharp.LineLensShared.LineLens→Fable.Import.VSCode.Vscode.ExtensionContextIonide.VSCode.FSharp.LineLensShared.LineLens→Fable.Import.VSCode.Vscode.UriIonide.VSCode.FSharp.LineLensShared.LineLensShared→Fable.Import.VSCode.Vscode.TextDocumentIonide.VSCode.FSharp.LineLensShared.LineLensState→Fable.Import.VSCode.Vscode.DisposableIonide.VSCode.FSharp.LineLensShared.LineLensState→Fable.Import.VSCode.Vscode.TextEditorDecorationTypeIonide.VSCode.FSharp.LineLensShared.LineLensState→Fable.Import.VSCode.Vscode.Uri
- Direction
- Ionide.VSCode.FSharp.LineLensShared uses Fable.Import.VSCode.Vscode, so a change to Fable.Import.VSCode.Vscode can break Ionide.VSCode.FSharp.LineLensShared, while a change to Ionide.VSCode.FSharp.LineLensShared can't break Fable.Import.VSCode.Vscode.
- Position
- Below the diagonal: Ionide.VSCode.FSharp.LineLensShared uses a module listed above it, which is the healthy direction.
27→22 Ionide.VSCode.FSharp.LineLensShared uses Ionide.VSCode.FSharp.LineLensShared.Documents✕
- Connections
- 1 pair of types, where a type in Ionide.VSCode.FSharp.LineLensShared uses a type in Ionide.VSCode.FSharp.LineLensShared.Documents.
- The types involved
Ionide.VSCode.FSharp.LineLensShared.LineLensState→Ionide.VSCode.FSharp.LineLensShared.Documents.DocumentInfo
- Direction
- Ionide.VSCode.FSharp.LineLensShared uses Ionide.VSCode.FSharp.LineLensShared.Documents, so a change to Ionide.VSCode.FSharp.LineLensShared.Documents can break Ionide.VSCode.FSharp.LineLensShared, while a change to Ionide.VSCode.FSharp.LineLensShared can't break Ionide.VSCode.FSharp.LineLensShared.Documents.
- Position
- Below the diagonal: Ionide.VSCode.FSharp.LineLensShared uses a module listed above it, which is the healthy direction.
28→18 Ionide.VSCode.FSharp.MSBuild uses Fable.Import.VSCode.Vscode✕
- Connections
- 8 pairs of types, where a type in Ionide.VSCode.FSharp.MSBuild uses a type in Fable.Import.VSCode.Vscode.
- The types involved
Ionide.VSCode.FSharp.MSBuild.MSBuild→Fable.Import.VSCode.Vscode.CancellationTokenIonide.VSCode.FSharp.MSBuild.MSBuild→Fable.Import.VSCode.Vscode.ExtensionContextIonide.VSCode.FSharp.MSBuild.MSBuild→Fable.Import.VSCode.Vscode.OutputChannelIonide.VSCode.FSharp.MSBuild.MSBuild→Fable.Import.VSCode.Vscode.ShellExecutionIonide.VSCode.FSharp.MSBuild.MSBuild→Fable.Import.VSCode.Vscode.TaskIonide.VSCode.FSharp.MSBuild.MSBuild→Fable.Import.VSCode.Vscode.TaskDefinitionIonide.VSCode.FSharp.MSBuild.MSBuild→Fable.Import.VSCode.Vscode.TaskFilterIonide.VSCode.FSharp.MSBuild.MSBuild→Fable.Import.VSCode.Vscode.TaskProvider`1
- Direction
- Ionide.VSCode.FSharp.MSBuild uses Fable.Import.VSCode.Vscode, so a change to Fable.Import.VSCode.Vscode can break Ionide.VSCode.FSharp.MSBuild, while a change to Ionide.VSCode.FSharp.MSBuild can't break Fable.Import.VSCode.Vscode.
- Position
- Below the diagonal: Ionide.VSCode.FSharp.MSBuild uses a module listed above it, which is the healthy direction.
28→21 Ionide.VSCode.FSharp.MSBuild uses Ionide.VSCode.FSharp.DTO✕
- Connections
- 2 pairs of types, where a type in Ionide.VSCode.FSharp.MSBuild uses a type in Ionide.VSCode.FSharp.DTO.
- The types involved
Ionide.VSCode.FSharp.MSBuild.MSBuild→Ionide.VSCode.FSharp.DTO.ProjectIonide.VSCode.FSharp.MSBuild.MSBuild→Ionide.VSCode.FSharp.DTO.WorkspacePeekFound
- Direction
- Ionide.VSCode.FSharp.MSBuild uses Ionide.VSCode.FSharp.DTO, so a change to Ionide.VSCode.FSharp.DTO can break Ionide.VSCode.FSharp.MSBuild, while a change to Ionide.VSCode.FSharp.MSBuild can't break Ionide.VSCode.FSharp.DTO.
- Position
- Below the diagonal: Ionide.VSCode.FSharp.MSBuild uses a module listed above it, which is the healthy direction.
28→23 Ionide.VSCode.FSharp.MSBuild uses Ionide.VSCode.FSharp.Logging✕
- Connections
- 1 pair of types, where a type in Ionide.VSCode.FSharp.MSBuild uses a type in Ionide.VSCode.FSharp.Logging.
- The types involved
Ionide.VSCode.FSharp.MSBuild.MSBuild→Ionide.VSCode.FSharp.Logging.ConsoleAndOutputChannelLogger
- Direction
- Ionide.VSCode.FSharp.MSBuild uses Ionide.VSCode.FSharp.Logging, so a change to Ionide.VSCode.FSharp.Logging can break Ionide.VSCode.FSharp.MSBuild, while a change to Ionide.VSCode.FSharp.MSBuild can't break Ionide.VSCode.FSharp.Logging.
- Position
- Below the diagonal: Ionide.VSCode.FSharp.MSBuild uses a module listed above it, which is the healthy direction.
29→18 Ionide.VSCode.FSharp.Notifications uses Fable.Import.VSCode.Vscode✕
- Connections
- 4 pairs of types, where a type in Ionide.VSCode.FSharp.Notifications uses a type in Fable.Import.VSCode.Vscode.
- The types involved
Ionide.VSCode.FSharp.Notifications.DocumentParsedEvent→Fable.Import.VSCode.Vscode.TextDocumentIonide.VSCode.FSharp.Notifications.Notifications→Fable.Import.VSCode.Vscode.EventEmitter`1Ionide.VSCode.FSharp.Notifications.Notifications→Fable.Import.VSCode.Vscode.Event`1Ionide.VSCode.FSharp.Notifications.Notifications→Fable.Import.VSCode.Vscode.Position
- Direction
- Ionide.VSCode.FSharp.Notifications uses Fable.Import.VSCode.Vscode, so a change to Fable.Import.VSCode.Vscode can break Ionide.VSCode.FSharp.Notifications, while a change to Ionide.VSCode.FSharp.Notifications can't break Fable.Import.VSCode.Vscode.
- Position
- Below the diagonal: Ionide.VSCode.FSharp.Notifications uses a module listed above it, which is the healthy direction.
29→21 Ionide.VSCode.FSharp.Notifications uses Ionide.VSCode.FSharp.DTO✕
- Connections
- 1 pair of types, where a type in Ionide.VSCode.FSharp.Notifications uses a type in Ionide.VSCode.FSharp.DTO.
- The types involved
Ionide.VSCode.FSharp.Notifications.Notifications→Ionide.VSCode.FSharp.DTO.TestForFile
- Direction
- Ionide.VSCode.FSharp.Notifications uses Ionide.VSCode.FSharp.DTO, so a change to Ionide.VSCode.FSharp.DTO can break Ionide.VSCode.FSharp.Notifications, while a change to Ionide.VSCode.FSharp.Notifications can't break Ionide.VSCode.FSharp.DTO.
- Position
- Below the diagonal: Ionide.VSCode.FSharp.Notifications uses a module listed above it, which is the healthy direction.
30→18 Ionide.VSCode.FSharp.Project uses Fable.Import.VSCode.Vscode✕
- Connections
- 5 pairs of types, where a type in Ionide.VSCode.FSharp.Project uses a type in Fable.Import.VSCode.Vscode.
- The types involved
Ionide.VSCode.FSharp.Project.Project→Fable.Import.VSCode.Vscode.EventEmitter`1Ionide.VSCode.FSharp.Project.Project→Fable.Import.VSCode.Vscode.Event`1Ionide.VSCode.FSharp.Project.Project→Fable.Import.VSCode.Vscode.ExtensionContextIonide.VSCode.FSharp.Project.Project→Fable.Import.VSCode.Vscode.OutputChannelIonide.VSCode.FSharp.Project.Project→Fable.Import.VSCode.Vscode.Terminal
- Direction
- Ionide.VSCode.FSharp.Project uses Fable.Import.VSCode.Vscode, so a change to Fable.Import.VSCode.Vscode can break Ionide.VSCode.FSharp.Project, while a change to Ionide.VSCode.FSharp.Project can't break Fable.Import.VSCode.Vscode.
- Position
- Below the diagonal: Ionide.VSCode.FSharp.Project uses a module listed above it, which is the healthy direction.
30→21 Ionide.VSCode.FSharp.Project uses Ionide.VSCode.FSharp.DTO✕
- Connections
- 7 pairs of types, where a type in Ionide.VSCode.FSharp.Project uses a type in Ionide.VSCode.FSharp.DTO.
- The types involved
Ionide.VSCode.FSharp.Project.Project→Ionide.VSCode.FSharp.DTO.ProjectIonide.VSCode.FSharp.Project.Project→Ionide.VSCode.FSharp.DTO.ProjectLoadingIonide.VSCode.FSharp.Project.Project→Ionide.VSCode.FSharp.DTO.Result`1Ionide.VSCode.FSharp.Project.Project→Ionide.VSCode.FSharp.DTO.WorkspacePeekFoundIonide.VSCode.FSharp.Project.Project→Ionide.VSCode.FSharp.DTO.WorkspacePeekFoundSolutionIonide.VSCode.FSharp.Project.Project→Ionide.VSCode.FSharp.DTO.WorkspacePeekFoundSolutionItemIonide.VSCode.FSharp.Project.ProjectLoadingState→Ionide.VSCode.FSharp.DTO.Project
- Direction
- Ionide.VSCode.FSharp.Project uses Ionide.VSCode.FSharp.DTO, so a change to Ionide.VSCode.FSharp.DTO can break Ionide.VSCode.FSharp.Project, while a change to Ionide.VSCode.FSharp.Project can't break Ionide.VSCode.FSharp.DTO.
- Position
- Below the diagonal: Ionide.VSCode.FSharp.Project uses a module listed above it, which is the healthy direction.
30→23 Ionide.VSCode.FSharp.Project uses Ionide.VSCode.FSharp.Logging✕
- Connections
- 1 pair of types, where a type in Ionide.VSCode.FSharp.Project uses a type in Ionide.VSCode.FSharp.Logging.
- The types involved
Ionide.VSCode.FSharp.Project.Project→Ionide.VSCode.FSharp.Logging.ConsoleAndOutputChannelLogger
- Direction
- Ionide.VSCode.FSharp.Project uses Ionide.VSCode.FSharp.Logging, so a change to Ionide.VSCode.FSharp.Logging can break Ionide.VSCode.FSharp.Project, while a change to Ionide.VSCode.FSharp.Project can't break Ionide.VSCode.FSharp.Logging.
- Position
- Below the diagonal: Ionide.VSCode.FSharp.Project uses a module listed above it, which is the healthy direction.
31→18 Ionide.VSCode.FSharp.TestExplorer uses Fable.Import.VSCode.Vscode✕
- Connections
- 6 pairs of types, where a type in Ionide.VSCode.FSharp.TestExplorer uses a type in Fable.Import.VSCode.Vscode.
- The types involved
Ionide.VSCode.FSharp.TestExplorer.CodeLocationCache→Fable.Import.VSCode.Vscode.UriIonide.VSCode.FSharp.TestExplorer.LocationRecord→Fable.Import.VSCode.Vscode.RangeIonide.VSCode.FSharp.TestExplorer.LocationRecord→Fable.Import.VSCode.Vscode.UriIonide.VSCode.FSharp.TestExplorer.TestExplorer→Fable.Import.VSCode.Vscode.ExtensionContextIonide.VSCode.FSharp.TestExplorer.TestExplorer→Fable.Import.VSCode.Vscode.OutputChannelIonide.VSCode.FSharp.TestExplorer.TestExplorer→Fable.Import.VSCode.Vscode.TestItem
- Direction
- Ionide.VSCode.FSharp.TestExplorer uses Fable.Import.VSCode.Vscode, so a change to Fable.Import.VSCode.Vscode can break Ionide.VSCode.FSharp.TestExplorer, while a change to Ionide.VSCode.FSharp.TestExplorer can't break Fable.Import.VSCode.Vscode.
- Position
- Below the diagonal: Ionide.VSCode.FSharp.TestExplorer uses a module listed above it, which is the healthy direction.
31→23 Ionide.VSCode.FSharp.TestExplorer uses Ionide.VSCode.FSharp.Logging✕
- Connections
- 1 pair of types, where a type in Ionide.VSCode.FSharp.TestExplorer uses a type in Ionide.VSCode.FSharp.Logging.
- The types involved
Ionide.VSCode.FSharp.TestExplorer.TestExplorer→Ionide.VSCode.FSharp.Logging.ConsoleAndOutputChannelLogger
- Direction
- Ionide.VSCode.FSharp.TestExplorer uses Ionide.VSCode.FSharp.Logging, so a change to Ionide.VSCode.FSharp.Logging can break Ionide.VSCode.FSharp.TestExplorer, while a change to Ionide.VSCode.FSharp.TestExplorer can't break Ionide.VSCode.FSharp.Logging.
- Position
- Below the diagonal: Ionide.VSCode.FSharp.TestExplorer uses a module listed above it, which is the healthy direction.
32→2 Ionide.VSCode.FSharp.TestExplorer.TestItem uses Ionide.VSCode.FSharp.TestExplorer.TestName✕
- Connections
- 1 pair of types, where a type in Ionide.VSCode.FSharp.TestExplorer.TestItem uses a type in Ionide.VSCode.FSharp.TestExplorer.TestName.
- The types involved
Ionide.VSCode.FSharp.TestExplorer.TestItem.TestItem→Ionide.VSCode.FSharp.TestExplorer.TestName.NameHierarchy`1
- Direction
- Ionide.VSCode.FSharp.TestExplorer.TestItem uses Ionide.VSCode.FSharp.TestExplorer.TestName, so a change to Ionide.VSCode.FSharp.TestExplorer.TestName can break Ionide.VSCode.FSharp.TestExplorer.TestItem, while a change to Ionide.VSCode.FSharp.TestExplorer.TestItem can't break Ionide.VSCode.FSharp.TestExplorer.TestName.
- Position
- Below the diagonal: Ionide.VSCode.FSharp.TestExplorer.TestItem uses a module listed above it, which is the healthy direction.
32→18 Ionide.VSCode.FSharp.TestExplorer.TestItem uses Fable.Import.VSCode.Vscode✕
- Connections
- 8 pairs of types, where a type in Ionide.VSCode.FSharp.TestExplorer.TestItem uses a type in Fable.Import.VSCode.Vscode.
- The types involved
Ionide.VSCode.FSharp.TestExplorer.TestItem.TestItem→Fable.Import.VSCode.Vscode.LocationIonide.VSCode.FSharp.TestExplorer.TestItem.TestItem→Fable.Import.VSCode.Vscode.TestControllerIonide.VSCode.FSharp.TestExplorer.TestItem.TestItem→Fable.Import.VSCode.Vscode.TestItemIonide.VSCode.FSharp.TestExplorer.TestItem.TestItem→Fable.Import.VSCode.Vscode.TestItemCollectionIonide.VSCode.FSharp.TestExplorer.TestItem.TestItem→Fable.Import.VSCode.Vscode.UriIonide.VSCode.FSharp.TestExplorer.TestItem.TestItemBuilder→Fable.Import.VSCode.Vscode.RangeIonide.VSCode.FSharp.TestExplorer.TestItem.TestItemBuilder→Fable.Import.VSCode.Vscode.TestItemIonide.VSCode.FSharp.TestExplorer.TestItem.TestItemBuilder→Fable.Import.VSCode.Vscode.Uri
- Direction
- Ionide.VSCode.FSharp.TestExplorer.TestItem uses Fable.Import.VSCode.Vscode, so a change to Fable.Import.VSCode.Vscode can break Ionide.VSCode.FSharp.TestExplorer.TestItem, while a change to Ionide.VSCode.FSharp.TestExplorer.TestItem can't break Fable.Import.VSCode.Vscode.
- Position
- Below the diagonal: Ionide.VSCode.FSharp.TestExplorer.TestItem uses a module listed above it, which is the healthy direction.
32→21 Ionide.VSCode.FSharp.TestExplorer.TestItem uses Ionide.VSCode.FSharp.DTO✕
- Connections
- 3 pairs of types, where a type in Ionide.VSCode.FSharp.TestExplorer.TestItem uses a type in Ionide.VSCode.FSharp.DTO.
- The types involved
Ionide.VSCode.FSharp.TestExplorer.TestItem.TestItem→Ionide.VSCode.FSharp.DTO.TestAdapterEntryIonide.VSCode.FSharp.TestExplorer.TestItem.TestItem→Ionide.VSCode.FSharp.DTO.TestForFileIonide.VSCode.FSharp.TestExplorer.TestItem.TestItem→Ionide.VSCode.FSharp.DTO.TestItemDTO
- Direction
- Ionide.VSCode.FSharp.TestExplorer.TestItem uses Ionide.VSCode.FSharp.DTO, so a change to Ionide.VSCode.FSharp.DTO can break Ionide.VSCode.FSharp.TestExplorer.TestItem, while a change to Ionide.VSCode.FSharp.TestExplorer.TestItem can't break Ionide.VSCode.FSharp.DTO.
- Position
- Below the diagonal: Ionide.VSCode.FSharp.TestExplorer.TestItem uses a module listed above it, which is the healthy direction.
33→18 Ionide.VSCode.FSharpModule uses Fable.Import.VSCode.Vscode✕
- Connections
- 3 pairs of types, where a type in Ionide.VSCode.FSharpModule uses a type in Fable.Import.VSCode.Vscode.
- The types involved
Ionide.VSCode.FSharpModule.Api→Fable.Import.VSCode.Vscode.Event`1Ionide.VSCode.FSharpModule.FSharpModule→Fable.Import.VSCode.Vscode.DisposableIonide.VSCode.FSharpModule.FSharpModule→Fable.Import.VSCode.Vscode.ExtensionContext
- Direction
- Ionide.VSCode.FSharpModule uses Fable.Import.VSCode.Vscode, so a change to Fable.Import.VSCode.Vscode can break Ionide.VSCode.FSharpModule, while a change to Ionide.VSCode.FSharpModule can't break Fable.Import.VSCode.Vscode.
- Position
- Below the diagonal: Ionide.VSCode.FSharpModule uses a module listed above it, which is the healthy direction.
33→21 Ionide.VSCode.FSharpModule uses Ionide.VSCode.FSharp.DTO✕
- Connections
- 1 pair of types, where a type in Ionide.VSCode.FSharpModule uses a type in Ionide.VSCode.FSharp.DTO.
- The types involved
Ionide.VSCode.FSharpModule.Api→Ionide.VSCode.FSharp.DTO.Project
- Direction
- Ionide.VSCode.FSharpModule uses Ionide.VSCode.FSharp.DTO, so a change to Ionide.VSCode.FSharp.DTO can break Ionide.VSCode.FSharpModule, while a change to Ionide.VSCode.FSharpModule can't break Ionide.VSCode.FSharp.DTO.
- Position
- Below the diagonal: Ionide.VSCode.FSharpModule uses a module listed above it, which is the healthy direction.
33→23 Ionide.VSCode.FSharpModule uses Ionide.VSCode.FSharp.Logging✕
- Connections
- 1 pair of types, where a type in Ionide.VSCode.FSharpModule uses a type in Ionide.VSCode.FSharp.Logging.
- The types involved
Ionide.VSCode.FSharpModule.FSharpModule→Ionide.VSCode.FSharp.Logging.ConsoleAndOutputChannelLogger
- Direction
- Ionide.VSCode.FSharpModule uses Ionide.VSCode.FSharp.Logging, so a change to Ionide.VSCode.FSharp.Logging can break Ionide.VSCode.FSharpModule, while a change to Ionide.VSCode.FSharpModule can't break Ionide.VSCode.FSharp.Logging.
- Position
- Below the diagonal: Ionide.VSCode.FSharpModule uses a module listed above it, which is the healthy direction.
34→18 Ionide.VSCode.FSharp.LanguageService uses Fable.Import.VSCode.Vscode✕
- Connections
- 6 pairs of types, where a type in Ionide.VSCode.FSharp.LanguageService uses a type in Fable.Import.VSCode.Vscode.
- The types involved
Ionide.VSCode.FSharp.LanguageService.LanguageService→Fable.Import.VSCode.Vscode.EventEmitter`1Ionide.VSCode.FSharp.LanguageService.LanguageService→Fable.Import.VSCode.Vscode.Event`1Ionide.VSCode.FSharp.LanguageService.LanguageService→Fable.Import.VSCode.Vscode.ExtensionContextIonide.VSCode.FSharp.LanguageService.LanguageService→Fable.Import.VSCode.Vscode.NotebookCellTextDocumentFilterIonide.VSCode.FSharp.LanguageService.LanguageService→Fable.Import.VSCode.Vscode.TextDocumentFilterIonide.VSCode.FSharp.LanguageService.LanguageService→Fable.Import.VSCode.Vscode.Uri
- Direction
- Ionide.VSCode.FSharp.LanguageService uses Fable.Import.VSCode.Vscode, so a change to Fable.Import.VSCode.Vscode can break Ionide.VSCode.FSharp.LanguageService, while a change to Ionide.VSCode.FSharp.LanguageService can't break Fable.Import.VSCode.Vscode.
- Position
- Below the diagonal: Ionide.VSCode.FSharp.LanguageService uses a module listed above it, which is the healthy direction.
34→21 Ionide.VSCode.FSharp.LanguageService uses Ionide.VSCode.FSharp.DTO✕
- Connections
- 12 pairs of types, where a type in Ionide.VSCode.FSharp.LanguageService uses a type in Ionide.VSCode.FSharp.DTO.
- The types involved
Ionide.VSCode.FSharp.LanguageService.LanguageService→Ionide.VSCode.FSharp.DTO.CompileDataIonide.VSCode.FSharp.LanguageService.LanguageService→Ionide.VSCode.FSharp.DTO.DocumentationDescriptionIonide.VSCode.FSharp.LanguageService.LanguageService→Ionide.VSCode.FSharp.DTO.FsdnResponseIonide.VSCode.FSharp.LanguageService.LanguageService→Ionide.VSCode.FSharp.DTO.HighlightingResponseIonide.VSCode.FSharp.LanguageService.LanguageService→Ionide.VSCode.FSharp.DTO.PipelineHintIonide.VSCode.FSharp.LanguageService.LanguageService→Ionide.VSCode.FSharp.DTO.ProjectIonide.VSCode.FSharp.LanguageService.LanguageService→Ionide.VSCode.FSharp.DTO.Result`1Ionide.VSCode.FSharp.LanguageService.LanguageService→Ionide.VSCode.FSharp.DTO.SignatureDataIonide.VSCode.FSharp.LanguageService.LanguageService→Ionide.VSCode.FSharp.DTO.SymbolsIonide.VSCode.FSharp.LanguageService.LanguageService→Ionide.VSCode.FSharp.DTO.TestItemDTOIonide.VSCode.FSharp.LanguageService.LanguageService→Ionide.VSCode.FSharp.DTO.TestResultDTOIonide.VSCode.FSharp.LanguageService.LanguageService→Ionide.VSCode.FSharp.DTO.WorkspacePeek
- Direction
- Ionide.VSCode.FSharp.LanguageService uses Ionide.VSCode.FSharp.DTO, so a change to Ionide.VSCode.FSharp.DTO can break Ionide.VSCode.FSharp.LanguageService, while a change to Ionide.VSCode.FSharp.LanguageService can't break Ionide.VSCode.FSharp.DTO.
- Position
- Below the diagonal: Ionide.VSCode.FSharp.LanguageService uses a module listed above it, which is the healthy direction.
34→23 Ionide.VSCode.FSharp.LanguageService uses Ionide.VSCode.FSharp.Logging✕
- Connections
- 1 pair of types, where a type in Ionide.VSCode.FSharp.LanguageService uses a type in Ionide.VSCode.FSharp.Logging.
- The types involved
Ionide.VSCode.FSharp.LanguageService.LanguageService→Ionide.VSCode.FSharp.Logging.ConsoleAndOutputChannelLogger
- Direction
- Ionide.VSCode.FSharp.LanguageService uses Ionide.VSCode.FSharp.Logging, so a change to Ionide.VSCode.FSharp.Logging can break Ionide.VSCode.FSharp.LanguageService, while a change to Ionide.VSCode.FSharp.LanguageService can't break Ionide.VSCode.FSharp.Logging.
- Position
- Below the diagonal: Ionide.VSCode.FSharp.LanguageService uses a module listed above it, which is the healthy direction.
34→24 Ionide.VSCode.FSharp.LanguageService uses Fable.Import.LanguageServer✕
- Connections
- 2 pairs of types, where a type in Ionide.VSCode.FSharp.LanguageService uses a type in Fable.Import.LanguageServer.
- The types involved
Ionide.VSCode.FSharp.LanguageService.LanguageService→Fable.Import.LanguageServer.ExecutableIonide.VSCode.FSharp.LanguageService.LanguageService→Fable.Import.LanguageServer.LanguageClient
- Direction
- Ionide.VSCode.FSharp.LanguageService uses Fable.Import.LanguageServer, so a change to Fable.Import.LanguageServer can break Ionide.VSCode.FSharp.LanguageService, while a change to Ionide.VSCode.FSharp.LanguageService can't break Fable.Import.LanguageServer.
- Position
- Below the diagonal: Ionide.VSCode.FSharp.LanguageService uses a module listed above it, which is the healthy direction.
35→18 Ionide.VSCode.FSharp.LineLens.DecorationUpdate uses Fable.Import.VSCode.Vscode✕
- Connections
- 4 pairs of types, where a type in Ionide.VSCode.FSharp.LineLens.DecorationUpdate uses a type in Fable.Import.VSCode.Vscode.
- The types involved
Ionide.VSCode.FSharp.LineLens.DecorationUpdate.DecorationUpdate→Fable.Import.VSCode.Vscode.DecorationOptionsIonide.VSCode.FSharp.LineLens.DecorationUpdate.DecorationUpdate→Fable.Import.VSCode.Vscode.RangeIonide.VSCode.FSharp.LineLens.DecorationUpdate.DecorationUpdate→Fable.Import.VSCode.Vscode.TextDocumentIonide.VSCode.FSharp.LineLens.DecorationUpdate.DecorationUpdate→Fable.Import.VSCode.Vscode.Uri
- Direction
- Ionide.VSCode.FSharp.LineLens.DecorationUpdate uses Fable.Import.VSCode.Vscode, so a change to Fable.Import.VSCode.Vscode can break Ionide.VSCode.FSharp.LineLens.DecorationUpdate, while a change to Ionide.VSCode.FSharp.LineLens.DecorationUpdate can't break Fable.Import.VSCode.Vscode.
- Position
- Below the diagonal: Ionide.VSCode.FSharp.LineLens.DecorationUpdate uses a module listed above it, which is the healthy direction.
35→21 Ionide.VSCode.FSharp.LineLens.DecorationUpdate uses Ionide.VSCode.FSharp.DTO✕
- Connections
- 4 pairs of types, where a type in Ionide.VSCode.FSharp.LineLens.DecorationUpdate uses a type in Ionide.VSCode.FSharp.DTO.
- The types involved
Ionide.VSCode.FSharp.LineLens.DecorationUpdate.DecorationUpdate→Ionide.VSCode.FSharp.DTO.RangeIonide.VSCode.FSharp.LineLens.DecorationUpdate.DecorationUpdate→Ionide.VSCode.FSharp.DTO.Result`1Ionide.VSCode.FSharp.LineLens.DecorationUpdate.DecorationUpdate→Ionide.VSCode.FSharp.DTO.SignatureDataIonide.VSCode.FSharp.LineLens.DecorationUpdate.DecorationUpdate→Ionide.VSCode.FSharp.DTO.Symbols
- Direction
- Ionide.VSCode.FSharp.LineLens.DecorationUpdate uses Ionide.VSCode.FSharp.DTO, so a change to Ionide.VSCode.FSharp.DTO can break Ionide.VSCode.FSharp.LineLens.DecorationUpdate, while a change to Ionide.VSCode.FSharp.LineLens.DecorationUpdate can't break Ionide.VSCode.FSharp.DTO.
- Position
- Below the diagonal: Ionide.VSCode.FSharp.LineLens.DecorationUpdate uses a module listed above it, which is the healthy direction.
35→27 Ionide.VSCode.FSharp.LineLens.DecorationUpdate uses Ionide.VSCode.FSharp.LineLensShared✕
- Connections
- 2 pairs of types, where a type in Ionide.VSCode.FSharp.LineLens.DecorationUpdate uses a type in Ionide.VSCode.FSharp.LineLensShared.
- The types involved
Ionide.VSCode.FSharp.LineLens.DecorationUpdate.DecorationUpdate→Ionide.VSCode.FSharp.LineLensShared.LineLensConfigIonide.VSCode.FSharp.LineLens.DecorationUpdate.DecorationUpdate→Ionide.VSCode.FSharp.LineLensShared.LineLensState
- Direction
- Ionide.VSCode.FSharp.LineLens.DecorationUpdate uses Ionide.VSCode.FSharp.LineLensShared, so a change to Ionide.VSCode.FSharp.LineLensShared can break Ionide.VSCode.FSharp.LineLens.DecorationUpdate, while a change to Ionide.VSCode.FSharp.LineLens.DecorationUpdate can't break Ionide.VSCode.FSharp.LineLensShared.
- Position
- Below the diagonal: Ionide.VSCode.FSharp.LineLens.DecorationUpdate uses a module listed above it, which is the healthy direction.
36→18 Ionide.VSCode.FSharp.LineLensShared.DecorationUpdateModule uses Fable.Import.VSCode.Vscode✕
- Connections
- 1 pair of types, where a type in Ionide.VSCode.FSharp.LineLensShared.DecorationUpdateModule uses a type in Fable.Import.VSCode.Vscode.
- The types involved
Ionide.VSCode.FSharp.LineLensShared.DecorationUpdateModule.DecorationUpdateModule→Fable.Import.VSCode.Vscode.TextDocument
- Direction
- Ionide.VSCode.FSharp.LineLensShared.DecorationUpdateModule uses Fable.Import.VSCode.Vscode, so a change to Fable.Import.VSCode.Vscode can break Ionide.VSCode.FSharp.LineLensShared.DecorationUpdateModule, while a change to Ionide.VSCode.FSharp.LineLensShared.DecorationUpdateModule can't break Fable.Import.VSCode.Vscode.
- Position
- Below the diagonal: Ionide.VSCode.FSharp.LineLensShared.DecorationUpdateModule uses a module listed above it, which is the healthy direction.
36→22 Ionide.VSCode.FSharp.LineLensShared.DecorationUpdateModule uses Ionide.VSCode.FSharp.LineLensShared.Documents✕
- Connections
- 1 pair of types, where a type in Ionide.VSCode.FSharp.LineLensShared.DecorationUpdateModule uses a type in Ionide.VSCode.FSharp.LineLensShared.Documents.
- The types involved
Ionide.VSCode.FSharp.LineLensShared.DecorationUpdateModule.DecorationUpdateModule→Ionide.VSCode.FSharp.LineLensShared.Documents.DocumentInfo
- Direction
- Ionide.VSCode.FSharp.LineLensShared.DecorationUpdateModule uses Ionide.VSCode.FSharp.LineLensShared.Documents, so a change to Ionide.VSCode.FSharp.LineLensShared.Documents can break Ionide.VSCode.FSharp.LineLensShared.DecorationUpdateModule, while a change to Ionide.VSCode.FSharp.LineLensShared.DecorationUpdateModule can't break Ionide.VSCode.FSharp.LineLensShared.Documents.
- Position
- Below the diagonal: Ionide.VSCode.FSharp.LineLensShared.DecorationUpdateModule uses a module listed above it, which is the healthy direction.
36→23 Ionide.VSCode.FSharp.LineLensShared.DecorationUpdateModule uses Ionide.VSCode.FSharp.Logging✕
- Connections
- 1 pair of types, where a type in Ionide.VSCode.FSharp.LineLensShared.DecorationUpdateModule uses a type in Ionide.VSCode.FSharp.Logging.
- The types involved
Ionide.VSCode.FSharp.LineLensShared.DecorationUpdateModule.DecorationUpdateModule→Ionide.VSCode.FSharp.Logging.ConsoleAndOutputChannelLogger
- Direction
- Ionide.VSCode.FSharp.LineLensShared.DecorationUpdateModule uses Ionide.VSCode.FSharp.Logging, so a change to Ionide.VSCode.FSharp.Logging can break Ionide.VSCode.FSharp.LineLensShared.DecorationUpdateModule, while a change to Ionide.VSCode.FSharp.LineLensShared.DecorationUpdateModule can't break Ionide.VSCode.FSharp.Logging.
- Position
- Below the diagonal: Ionide.VSCode.FSharp.LineLensShared.DecorationUpdateModule uses a module listed above it, which is the healthy direction.
36→27 Ionide.VSCode.FSharp.LineLensShared.DecorationUpdateModule uses Ionide.VSCode.FSharp.LineLensShared✕
- Connections
- 2 pairs of types, where a type in Ionide.VSCode.FSharp.LineLensShared.DecorationUpdateModule uses a type in Ionide.VSCode.FSharp.LineLensShared.
- The types involved
Ionide.VSCode.FSharp.LineLensShared.DecorationUpdateModule.DecorationUpdateModule→Ionide.VSCode.FSharp.LineLensShared.LineLensConfigIonide.VSCode.FSharp.LineLensShared.DecorationUpdateModule.DecorationUpdateModule→Ionide.VSCode.FSharp.LineLensShared.LineLensState
- Direction
- Ionide.VSCode.FSharp.LineLensShared.DecorationUpdateModule uses Ionide.VSCode.FSharp.LineLensShared, so a change to Ionide.VSCode.FSharp.LineLensShared can break Ionide.VSCode.FSharp.LineLensShared.DecorationUpdateModule, while a change to Ionide.VSCode.FSharp.LineLensShared.DecorationUpdateModule can't break Ionide.VSCode.FSharp.LineLensShared.
- Position
- Below the diagonal: Ionide.VSCode.FSharp.LineLensShared.DecorationUpdateModule uses a module listed above it, which is the healthy direction.
37→18 Ionide.VSCode.FSharp.PipelineHints.PipelineDecorationUpdate uses Fable.Import.VSCode.Vscode✕
- Connections
- 3 pairs of types, where a type in Ionide.VSCode.FSharp.PipelineHints.PipelineDecorationUpdate uses a type in Fable.Import.VSCode.Vscode.
- The types involved
Ionide.VSCode.FSharp.PipelineHints.PipelineDecorationUpdate.PipelineDecorationUpdate→Fable.Import.VSCode.Vscode.DecorationOptionsIonide.VSCode.FSharp.PipelineHints.PipelineDecorationUpdate.PipelineDecorationUpdate→Fable.Import.VSCode.Vscode.RangeIonide.VSCode.FSharp.PipelineHints.PipelineDecorationUpdate.PipelineDecorationUpdate→Fable.Import.VSCode.Vscode.TextDocument
- Direction
- Ionide.VSCode.FSharp.PipelineHints.PipelineDecorationUpdate uses Fable.Import.VSCode.Vscode, so a change to Fable.Import.VSCode.Vscode can break Ionide.VSCode.FSharp.PipelineHints.PipelineDecorationUpdate, while a change to Ionide.VSCode.FSharp.PipelineHints.PipelineDecorationUpdate can't break Fable.Import.VSCode.Vscode.
- Position
- Below the diagonal: Ionide.VSCode.FSharp.PipelineHints.PipelineDecorationUpdate uses a module listed above it, which is the healthy direction.
37→21 Ionide.VSCode.FSharp.PipelineHints.PipelineDecorationUpdate uses Ionide.VSCode.FSharp.DTO✕
- Connections
- 2 pairs of types, where a type in Ionide.VSCode.FSharp.PipelineHints.PipelineDecorationUpdate uses a type in Ionide.VSCode.FSharp.DTO.
- The types involved
Ionide.VSCode.FSharp.PipelineHints.PipelineDecorationUpdate.PipelineDecorationUpdate→Ionide.VSCode.FSharp.DTO.PipelineHintIonide.VSCode.FSharp.PipelineHints.PipelineDecorationUpdate.PipelineDecorationUpdate→Ionide.VSCode.FSharp.DTO.Result`1
- Direction
- Ionide.VSCode.FSharp.PipelineHints.PipelineDecorationUpdate uses Ionide.VSCode.FSharp.DTO, so a change to Ionide.VSCode.FSharp.DTO can break Ionide.VSCode.FSharp.PipelineHints.PipelineDecorationUpdate, while a change to Ionide.VSCode.FSharp.PipelineHints.PipelineDecorationUpdate can't break Ionide.VSCode.FSharp.DTO.
- Position
- Below the diagonal: Ionide.VSCode.FSharp.PipelineHints.PipelineDecorationUpdate uses a module listed above it, which is the healthy direction.
37→27 Ionide.VSCode.FSharp.PipelineHints.PipelineDecorationUpdate uses Ionide.VSCode.FSharp.LineLensShared✕
- Connections
- 1 pair of types, where a type in Ionide.VSCode.FSharp.PipelineHints.PipelineDecorationUpdate uses a type in Ionide.VSCode.FSharp.LineLensShared.
- The types involved
Ionide.VSCode.FSharp.PipelineHints.PipelineDecorationUpdate.PipelineDecorationUpdate→Ionide.VSCode.FSharp.LineLensShared.LineLensConfig
- Direction
- Ionide.VSCode.FSharp.PipelineHints.PipelineDecorationUpdate uses Ionide.VSCode.FSharp.LineLensShared, so a change to Ionide.VSCode.FSharp.LineLensShared can break Ionide.VSCode.FSharp.PipelineHints.PipelineDecorationUpdate, while a change to Ionide.VSCode.FSharp.PipelineHints.PipelineDecorationUpdate can't break Ionide.VSCode.FSharp.LineLensShared.
- Position
- Below the diagonal: Ionide.VSCode.FSharp.PipelineHints.PipelineDecorationUpdate uses a module listed above it, which is the healthy direction.
38→3 Ionide.VSCode.FSharp.Project.CurrentWorkspaceConfiguration uses Fable.Import.VSCode✕
- Connections
- 1 pair of types, where a type in Ionide.VSCode.FSharp.Project.CurrentWorkspaceConfiguration uses a type in Fable.Import.VSCode.
- The types involved
Ionide.VSCode.FSharp.Project.CurrentWorkspaceConfiguration.CurrentWorkspaceConfiguration→Fable.Import.VSCode.Thenable`1
- Direction
- Ionide.VSCode.FSharp.Project.CurrentWorkspaceConfiguration uses Fable.Import.VSCode, so a change to Fable.Import.VSCode can break Ionide.VSCode.FSharp.Project.CurrentWorkspaceConfiguration, while a change to Ionide.VSCode.FSharp.Project.CurrentWorkspaceConfiguration can't break Fable.Import.VSCode.
- Position
- Below the diagonal: Ionide.VSCode.FSharp.Project.CurrentWorkspaceConfiguration uses a module listed above it, which is the healthy direction.
38→18 Ionide.VSCode.FSharp.Project.CurrentWorkspaceConfiguration uses Fable.Import.VSCode.Vscode✕
- Connections
- 2 pairs of types, where a type in Ionide.VSCode.FSharp.Project.CurrentWorkspaceConfiguration uses a type in Fable.Import.VSCode.Vscode.
- The types involved
Ionide.VSCode.FSharp.Project.CurrentWorkspaceConfiguration.CurrentWorkspaceConfiguration→Fable.Import.VSCode.Vscode.ExtensionContextIonide.VSCode.FSharp.Project.CurrentWorkspaceConfiguration.CurrentWorkspaceConfiguration→Fable.Import.VSCode.Vscode.Memento
- Direction
- Ionide.VSCode.FSharp.Project.CurrentWorkspaceConfiguration uses Fable.Import.VSCode.Vscode, so a change to Fable.Import.VSCode.Vscode can break Ionide.VSCode.FSharp.Project.CurrentWorkspaceConfiguration, while a change to Ionide.VSCode.FSharp.Project.CurrentWorkspaceConfiguration can't break Fable.Import.VSCode.Vscode.
- Position
- Below the diagonal: Ionide.VSCode.FSharp.Project.CurrentWorkspaceConfiguration uses a module listed above it, which is the healthy direction.
38→21 Ionide.VSCode.FSharp.Project.CurrentWorkspaceConfiguration uses Ionide.VSCode.FSharp.DTO✕
- Connections
- 1 pair of types, where a type in Ionide.VSCode.FSharp.Project.CurrentWorkspaceConfiguration uses a type in Ionide.VSCode.FSharp.DTO.
- The types involved
Ionide.VSCode.FSharp.Project.CurrentWorkspaceConfiguration.CurrentWorkspaceConfiguration→Ionide.VSCode.FSharp.DTO.WorkspacePeekFound
- Direction
- Ionide.VSCode.FSharp.Project.CurrentWorkspaceConfiguration uses Ionide.VSCode.FSharp.DTO, so a change to Ionide.VSCode.FSharp.DTO can break Ionide.VSCode.FSharp.Project.CurrentWorkspaceConfiguration, while a change to Ionide.VSCode.FSharp.Project.CurrentWorkspaceConfiguration can't break Ionide.VSCode.FSharp.DTO.
- Position
- Below the diagonal: Ionide.VSCode.FSharp.Project.CurrentWorkspaceConfiguration uses a module listed above it, which is the healthy direction.
38→30 Ionide.VSCode.FSharp.Project.CurrentWorkspaceConfiguration uses Ionide.VSCode.FSharp.Project✕
- Connections
- 1 pair of types, where a type in Ionide.VSCode.FSharp.Project.CurrentWorkspaceConfiguration uses a type in Ionide.VSCode.FSharp.Project.
- The types involved
Ionide.VSCode.FSharp.Project.CurrentWorkspaceConfiguration.CurrentWorkspaceConfiguration→Ionide.VSCode.FSharp.Project.ConfiguredWorkspace
- Direction
- Ionide.VSCode.FSharp.Project.CurrentWorkspaceConfiguration uses Ionide.VSCode.FSharp.Project, so a change to Ionide.VSCode.FSharp.Project can break Ionide.VSCode.FSharp.Project.CurrentWorkspaceConfiguration, while a change to Ionide.VSCode.FSharp.Project.CurrentWorkspaceConfiguration can't break Ionide.VSCode.FSharp.Project.
- Position
- Below the diagonal: Ionide.VSCode.FSharp.Project.CurrentWorkspaceConfiguration uses a module listed above it, which is the healthy direction.
39→3 Ionide.VSCode.FSharp.SolutionExplorer uses Fable.Import.VSCode✕
- Connections
- 1 pair of types, where a type in Ionide.VSCode.FSharp.SolutionExplorer uses a type in Fable.Import.VSCode.
- The types involved
Ionide.VSCode.FSharp.SolutionExplorer.SolutionExplorer→Fable.Import.VSCode.Thenable`1
- Direction
- Ionide.VSCode.FSharp.SolutionExplorer uses Fable.Import.VSCode, so a change to Fable.Import.VSCode can break Ionide.VSCode.FSharp.SolutionExplorer, while a change to Ionide.VSCode.FSharp.SolutionExplorer can't break Fable.Import.VSCode.
- Position
- Below the diagonal: Ionide.VSCode.FSharp.SolutionExplorer uses a module listed above it, which is the healthy direction.
39→18 Ionide.VSCode.FSharp.SolutionExplorer uses Fable.Import.VSCode.Vscode✕
- Connections
- 4 pairs of types, where a type in Ionide.VSCode.FSharp.SolutionExplorer uses a type in Fable.Import.VSCode.Vscode.
- The types involved
Ionide.VSCode.FSharp.SolutionExplorer.SolutionExplorer→Fable.Import.VSCode.Vscode.EventEmitter`1Ionide.VSCode.FSharp.SolutionExplorer.SolutionExplorer→Fable.Import.VSCode.Vscode.Event`1Ionide.VSCode.FSharp.SolutionExplorer.SolutionExplorer→Fable.Import.VSCode.Vscode.ExtensionContextIonide.VSCode.FSharp.SolutionExplorer.SolutionExplorer→Fable.Import.VSCode.Vscode.TreeDataProvider`1
- Direction
- Ionide.VSCode.FSharp.SolutionExplorer uses Fable.Import.VSCode.Vscode, so a change to Fable.Import.VSCode.Vscode can break Ionide.VSCode.FSharp.SolutionExplorer, while a change to Ionide.VSCode.FSharp.SolutionExplorer can't break Fable.Import.VSCode.Vscode.
- Position
- Below the diagonal: Ionide.VSCode.FSharp.SolutionExplorer uses a module listed above it, which is the healthy direction.
39→21 Ionide.VSCode.FSharp.SolutionExplorer uses Ionide.VSCode.FSharp.DTO✕
- Connections
- 3 pairs of types, where a type in Ionide.VSCode.FSharp.SolutionExplorer uses a type in Ionide.VSCode.FSharp.DTO.
- The types involved
Ionide.VSCode.FSharp.SolutionExplorer.Model→Ionide.VSCode.FSharp.DTO.ProjectIonide.VSCode.FSharp.SolutionExplorer.SolutionExplorer→Ionide.VSCode.FSharp.DTO.ProjectIonide.VSCode.FSharp.SolutionExplorer.SolutionExplorer→Ionide.VSCode.FSharp.DTO.WorkspacePeekFound
- Direction
- Ionide.VSCode.FSharp.SolutionExplorer uses Ionide.VSCode.FSharp.DTO, so a change to Ionide.VSCode.FSharp.DTO can break Ionide.VSCode.FSharp.SolutionExplorer, while a change to Ionide.VSCode.FSharp.SolutionExplorer can't break Ionide.VSCode.FSharp.DTO.
- Position
- Below the diagonal: Ionide.VSCode.FSharp.SolutionExplorer uses a module listed above it, which is the healthy direction.
39→30 Ionide.VSCode.FSharp.SolutionExplorer uses Ionide.VSCode.FSharp.Project✕
- Connections
- 1 pair of types, where a type in Ionide.VSCode.FSharp.SolutionExplorer uses a type in Ionide.VSCode.FSharp.Project.
- The types involved
Ionide.VSCode.FSharp.SolutionExplorer.SolutionExplorer→Ionide.VSCode.FSharp.Project.ProjectLoadingState
- Direction
- Ionide.VSCode.FSharp.SolutionExplorer uses Ionide.VSCode.FSharp.Project, so a change to Ionide.VSCode.FSharp.Project can break Ionide.VSCode.FSharp.SolutionExplorer, while a change to Ionide.VSCode.FSharp.SolutionExplorer can't break Ionide.VSCode.FSharp.Project.
- Position
- Below the diagonal: Ionide.VSCode.FSharp.SolutionExplorer uses a module listed above it, which is the healthy direction.
40→3 Ionide.VSCode.FSharp.TestExplorer.Interactions uses Fable.Import.VSCode✕
- Connections
- 1 pair of types, where a type in Ionide.VSCode.FSharp.TestExplorer.Interactions uses a type in Fable.Import.VSCode.
- The types involved
Ionide.VSCode.FSharp.TestExplorer.Interactions.Interactions→Fable.Import.VSCode.Thenable`1
- Direction
- Ionide.VSCode.FSharp.TestExplorer.Interactions uses Fable.Import.VSCode, so a change to Fable.Import.VSCode can break Ionide.VSCode.FSharp.TestExplorer.Interactions, while a change to Ionide.VSCode.FSharp.TestExplorer.Interactions can't break Fable.Import.VSCode.
- Position
- Below the diagonal: Ionide.VSCode.FSharp.TestExplorer.Interactions uses a module listed above it, which is the healthy direction.
40→9 Ionide.VSCode.FSharp.TestExplorer.Interactions uses Ionide.VSCode.FSharp.TestExplorer.TrxParser✕
- Connections
- 1 pair of types, where a type in Ionide.VSCode.FSharp.TestExplorer.Interactions uses a type in Ionide.VSCode.FSharp.TestExplorer.TrxParser.
- The types involved
Ionide.VSCode.FSharp.TestExplorer.Interactions.Interactions→Ionide.VSCode.FSharp.TestExplorer.TrxParser.TestWithResult
- Direction
- Ionide.VSCode.FSharp.TestExplorer.Interactions uses Ionide.VSCode.FSharp.TestExplorer.TrxParser, so a change to Ionide.VSCode.FSharp.TestExplorer.TrxParser can break Ionide.VSCode.FSharp.TestExplorer.Interactions, while a change to Ionide.VSCode.FSharp.TestExplorer.Interactions can't break Ionide.VSCode.FSharp.TestExplorer.TrxParser.
- Position
- Below the diagonal: Ionide.VSCode.FSharp.TestExplorer.Interactions uses a module listed above it, which is the healthy direction.
40→18 Ionide.VSCode.FSharp.TestExplorer.Interactions uses Fable.Import.VSCode.Vscode✕
- Connections
- 7 pairs of types, where a type in Ionide.VSCode.FSharp.TestExplorer.Interactions uses a type in Fable.Import.VSCode.Vscode.
- The types involved
Ionide.VSCode.FSharp.TestExplorer.Interactions.Interactions→Fable.Import.VSCode.Vscode.CancellationTokenIonide.VSCode.FSharp.TestExplorer.Interactions.Interactions→Fable.Import.VSCode.Vscode.TestControllerIonide.VSCode.FSharp.TestExplorer.Interactions.Interactions→Fable.Import.VSCode.Vscode.TestItemIonide.VSCode.FSharp.TestExplorer.Interactions.Interactions→Fable.Import.VSCode.Vscode.TestItemCollectionIonide.VSCode.FSharp.TestExplorer.Interactions.Interactions→Fable.Import.VSCode.Vscode.TestRunIonide.VSCode.FSharp.TestExplorer.Interactions.Interactions→Fable.Import.VSCode.Vscode.TestRunRequestIonide.VSCode.FSharp.TestExplorer.Interactions.ProjectRunRequest→Fable.Import.VSCode.Vscode.TestItem
- Direction
- Ionide.VSCode.FSharp.TestExplorer.Interactions uses Fable.Import.VSCode.Vscode, so a change to Fable.Import.VSCode.Vscode can break Ionide.VSCode.FSharp.TestExplorer.Interactions, while a change to Ionide.VSCode.FSharp.TestExplorer.Interactions can't break Fable.Import.VSCode.Vscode.
- Position
- Below the diagonal: Ionide.VSCode.FSharp.TestExplorer.Interactions uses a module listed above it, which is the healthy direction.
40→21 Ionide.VSCode.FSharp.TestExplorer.Interactions uses Ionide.VSCode.FSharp.DTO✕
- Connections
- 2 pairs of types, where a type in Ionide.VSCode.FSharp.TestExplorer.Interactions uses a type in Ionide.VSCode.FSharp.DTO.
- The types involved
Ionide.VSCode.FSharp.TestExplorer.Interactions.Interactions→Ionide.VSCode.FSharp.DTO.ProjectIonide.VSCode.FSharp.TestExplorer.Interactions.Interactions→Ionide.VSCode.FSharp.DTO.TestForFile
- Direction
- Ionide.VSCode.FSharp.TestExplorer.Interactions uses Ionide.VSCode.FSharp.DTO, so a change to Ionide.VSCode.FSharp.DTO can break Ionide.VSCode.FSharp.TestExplorer.Interactions, while a change to Ionide.VSCode.FSharp.TestExplorer.Interactions can't break Ionide.VSCode.FSharp.DTO.
- Position
- Below the diagonal: Ionide.VSCode.FSharp.TestExplorer.Interactions uses a module listed above it, which is the healthy direction.
40→31 Ionide.VSCode.FSharp.TestExplorer.Interactions uses Ionide.VSCode.FSharp.TestExplorer✕
- Connections
- 3 pairs of types, where a type in Ionide.VSCode.FSharp.TestExplorer.Interactions uses a type in Ionide.VSCode.FSharp.TestExplorer.
- The types involved
Ionide.VSCode.FSharp.TestExplorer.Interactions.Interactions→Ionide.VSCode.FSharp.TestExplorer.CodeLocationCacheIonide.VSCode.FSharp.TestExplorer.Interactions.Interactions→Ionide.VSCode.FSharp.TestExplorer.LocationRecordIonide.VSCode.FSharp.TestExplorer.Interactions.Interactions→Ionide.VSCode.FSharp.TestExplorer.TestResult
- Direction
- Ionide.VSCode.FSharp.TestExplorer.Interactions uses Ionide.VSCode.FSharp.TestExplorer, so a change to Ionide.VSCode.FSharp.TestExplorer can break Ionide.VSCode.FSharp.TestExplorer.Interactions, while a change to Ionide.VSCode.FSharp.TestExplorer.Interactions can't break Ionide.VSCode.FSharp.TestExplorer.
- Position
- Below the diagonal: Ionide.VSCode.FSharp.TestExplorer.Interactions uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A05:2025 — Injection | 16 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 6 | Medium |
Roadmap
Top priorities: Resolve the 1 No automated tests finding(s) in Code Coverage; Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them; Resolve the 8 Outdated (npm) finding(s) in Dependency Hygiene — start with package.json (2).
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 8 Outdated (npm) finding(s) in Dependency Hygiene — start with package.json (2). | +2.6 pts | Low | Dependency Hygiene |
| Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them. | +4.4 pts | Medium | Architecture documentation |
| Resolve the 8 Orphaned file finding(s) in Knowledge Freshness — start with Logging.fs, QuickInfo.fs, LineLens.fs. | +1.9 pts | Low | Knowledge Freshness |
| Resolve the 1 No automated tests finding(s) in Code Coverage. | +6.3 pts | High | Code Coverage |
| Resolve the 1 Off-boarding risk finding(s) in Bus Factor. | +1.3 pts | Low | Bus Factor |
| Resolve the 3 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (3). | +0.8 pts | Low | Static Analysis (SAST) |
| Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite. | +1.4 pts | Medium | Documentation (README) |
| Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. | +0.5 pts | Low | Static Analysis (SAST) |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 4.4 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.8 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.1 | Mixed | Static Analysis (SAST): High: REDACTED |
| src/Components/SolutionExplorer.fs | 7.0 | Mixed | Cyclomatic Complexity: SolutionExplorer.activate (cyclomatic 76) |
| src/Core/LanguageService.fs | 7.0 | Mixed | Cyclomatic Complexity: LanguageService.getOptions (cyclomatic 40) |
| REDACTED | 7.2 | Mixed | Static Analysis (SAST): High: REDACTED |
| src/Components/Fsi.fs | 7.4 | Mixed | Cognitive Complexity: Watcher.handler (cognitive 17) |
| src/Core/Project.fs | 7.4 | Mixed | God Classes: FileTooLong: Core/Project.fs |
| src/Components/MSBuild.fs | 7.8 | Mixed | Code Duplication: Duplicated block (16 lines × 2) |
| REDACTED | 7.9 | Mixed | Dependency Vulnerabilities: Medium CVE: REDACTED |
| src/Components/Debugger.fs | 8.5 | Near-clean | Cognitive Complexity: Debugger.makeDebugConfigFor (cognitive 25) |
| src/Components/InfoPanel.fs | 8.5 | Near-clean | Cognitive Complexity: Panel.mapContent (cognitive 22) |
| src/Core/Utils.fs | 8.5 | Near-clean | Cognitive Complexity: Document.|FSharp|CSharp|VB|FSharpScript|Markdown|Other| (cognitive 21) |
| src/Components/QuickInfo.fs | 8.5 | Near-clean | Code Duplication: Duplicated block (15 lines × 2) |
| src/Components/LineLens/LineLens.fs | 8.5 | Near-clean | Code Duplication: Duplicated block (11 lines × 2) |
| src/Components/TestExplorer.fs | 8.5 | Near-clean | Code Duplication: Duplicated block (13 lines × 2) |
| package.json | 9.3 | Near-clean | Dependency Hygiene: Outdated (npm): htmlparser2 |
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 39 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 — 39 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, 70 of 103 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Canine Code Analyzer duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 | ✓ deterministic |
Run transparency — what happened this run
- D15 Churn × Complexity Hotspots — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. A hotspot's complexity is meant to be the worst body its churn actually touched. For src/Components/SolutionExplorer.fs, src/Components/TestExplorer.fs, src/Core/LanguageService.fs that could not be established — the complexity reader for the file reports no body extents, or the history carries no per-line attribution — so the row quotes the file's worst body, which the counted changes may never have touched. The churn count is unaffected.
- 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 identifies the intentionally-exposed surface from `IsPackable` and `.Contracts` project names, MSBuild conventions read off the loaded project set. This target exposed no such projects, so the probe never ran; this says nothing about whether the repository has a public API. This repository commits no C#/VB source at all, so there was never an MSBuild project set to read these conventions off. That is OUR side and it is a COLLECTOR gap, not an environment fault: it declares a published package (src/Ionide.FSharp.fsproj), but no published-package marker D22 reads admitted any project here, so this ecosystem's public API has no collector, and the remedy is to write one — no change to the scan image can close it.
- D24 Comment Value — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Each source language's comment syntax, and the code a comment annotates in it, needs its own proof before D24 judges it. Until then those comments are left unread, not counted as clean.
- AX6 Interface segregation — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is computed over the public interfaces this run's compilations declare, and none was loaded, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- C1 Data Protection — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These personal data controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks personal data controls.
- C2 Access Controls — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These authorization controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks authorization controls.
- C3 Audit Trail — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These audit controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks audit controls.
- C4 Data Retention — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These retention controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks retention controls.
- C5 Data-Subject Rights — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These data-subject rights controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks data-subject rights controls.
- IC1 Incompleteness & stubs — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- M4 Documentation accuracy — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
- P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
- S1 Web-Security Posture — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These web-security controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks web-security controls.
- X1 Async correctness — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X12 Unreachable branch — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X13 Undrained process stream — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X14 Bypassable address classification — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X15 Unvalidated length from an untrusted reader — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X16 Unfloored truncation loop — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X17 Uncapped recursion over a caller-supplied document — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X18 Disposal-pattern correctness — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X19 Unrestored process-global state — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X2 Cancellation propagation — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X21 Side-effecting pattern guard — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X22 Contradicted release guard — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X24 Document value interpolated into markup unescaped — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X25 Inert configuration knob — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X26 Unsynchronised callback handoff — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X29 Per-element action decided by a fixed element — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X3 Exception handling — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X30 Support guard that admits what it rejects — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X32 Type resolved by simple name across every loaded assembly — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X4 Structured logging — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X5 Nullable reference types — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X6 Hand-rolled structured-format parsing — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and Python, JavaScript/TypeScript, Go, Java/Kotlin/Scala, Ruby, PHP, Rust, Swift, Erlang, Elixir and Dart source only, and no C# was loaded and none of those languages was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
- D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- D8 Code Coverage: Coverage is measured by building and running the test suite inside our isolated image — the target repo is never modified, and nothing on your systems runs. So coverage exists only when the suite builds and runs within the inline time budget; one that needs external services, can't build, or exceeds the budget yields no coverage (D8 then degrades to not-measured, not a low score). Line coverage also says nothing about assertion quality.
- 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.
- D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- 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
5 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was SolutionExplorer.activate at 76. A further 3 method(s) were over the threshold but excluded as flat dispatchers (a long switch/match over independent cases: many branches, almost no nesting), the largest being SolutionExplorer.getLabel at 17 — they are counted neither in the figure above nor in this dimension's score.
What to do
- Bring the 5 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with SolutionExplorer.activate (cyclomatic 76), SolutionExplorer.createProvider (cyclomatic 43), LanguageService.getOptions (cyclomatic 40). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 5 together lifts Cyclomatic Complexity from 7.9 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
D2 · Cognitive Complexity
8 method(s) exceeded the cognitive complexity threshold of 15; the worst was SolutionExplorer.activate at 91.
What to do
- Bring the 1 body over 60 down to 60 or less in Cognitive Complexity — start with SolutionExplorer.activate (cognitive 91). — Refactoring it lifts Cognitive Complexity from 7.5 to about 7.9/10.
D3 · God Classes
4 over-large unit(s) detected — types, modules or files that carry too much.
What to do
- Resolve the 4 FileTooLong finding(s) in God Classes — start with SolutionExplorer.fs, LanguageService.fs, Project.fs. — One of this dimension's main actionable groups (4 warning-level).
D4 · Code Duplication
21 duplicated block group(s) detected. 1 of the 21 are in trees this repository does not ship — vendored, example/demo, project-template, fixture and benchmark code — and are ranked below the shipped groups rather than excluded from them: the duplication there is real and is still counted in this dimension's score. The dimensions that publish a production-file census leave those trees out of theirs, so this count is deliberately drawn over the wider population.
What to do
- Resolve the 4 Duplicated block (9 lines × 2) finding(s) in Code Duplication — start with SolutionExplorer.fs (3), LanguageService.fs. — One of this dimension's main actionable groups (4 warning-level).
- Resolve the 2 Duplicated block (12 lines × 3) finding(s) in Code Duplication — start with MSBuild.fs, LanguageService.fs. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 2 Duplicated block (7 lines × 2) finding(s) in Code Duplication — start with SolutionExplorer.fs, LanguageService.fs. — One of this dimension's main actionable groups (2 warning-level).
D5 · Coupling
1 projects, 0 dependency cycle(s), 0 unstable depended-on project(s).
D6 · Cohesion (LCOM4)
0 of 2 classes have LCOM4 above 3.
D8 · Code Coverage
No automated tests — no test code was found in this repository.
What to do
- Resolve the 1 No automated tests finding(s) in Code Coverage. — One of this dimension's main actionable groups (1 issue-level).
D12 · Dependency Hygiene
2 outdated, 0 vulnerable, 0 deprecated packages. Those are the NuGet packages; this repository's npm dependencies were read too — 22 outdated of 24 package(s) across 1 lockfile(s).
What to do
- Resolve the 8 Outdated (npm) finding(s) in Dependency Hygiene — start with package.json (2). — One of this dimension's main actionable groups (8 recommendation-level).
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D14 · License Compliance
0 of 24 shipped npm package(s) use a banned license. Licences were resolved from registry.npmjs.org over the 24 package(s) this repository's committed lockfile installs for a consumer — its 7 production, optional and peer dependency(ies), across 1 product package.json manifest(s), and everything those install in turn. Its 3 `devDependencies` declaration(s), and every package only they reach, are excluded: a consumer installs none of them. ★ Each licence is the one the registry publishes for the package's CURRENT release rather than for the pinned version, which is the same caveat the Hex and RubyGems arms carry. This repository publishes itself under MIT, which is its own choice and is not judged here.
D15 · Churn × Complexity Hotspots
Top hotspots: src/Core/LanguageService.fs (5×40=200); src/Components/SolutionExplorer.fs (2×76=152); src/Components/TestExplorer.fs (2×19=38)
What to do
- Resolve the 3 Hotspot finding(s) in Churn × Complexity Hotspots — start with LanguageService.fs, SolutionExplorer.fs, TestExplorer.fs. — One of this dimension's main actionable groups (3 warning-level).
D16 · Bus Factor
4 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is src/Core/Project.fs. Counted over 24 of the 33 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 1 Off-boarding risk finding(s) in Bus Factor. — One of this dimension's main actionable groups (1 recommendation-level).
D19 · Documentation Quality
1 of 1 documentation facets pass in full. 2 document(s) read across 2 unit(s).
D26 · Project Cohesion
1 of 2 build units (MSBuild, npm) flagged as possibly oversized/incoherent.
What to do
- Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion. — One of this dimension's main actionable groups (1 recommendation-level).
D27 · Navigability
92 % of calls cross a namespace and 17 % 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)
17 finding(s): 0 critical, 17 high, 0 medium, 0 low. 10 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. Separately, one or more rules could not re-parse an embedded snippet in 1 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.
What to do
- Resolve the 3 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (3). — One of this dimension's main actionable groups (3 issue-level).
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- No action in Static Analysis (SAST) — all 10 REDACTED finding(s) are reported here at file:line but scored by D36 (supply-chain provenance), so none is charged to this dimension. — One of this dimension's main actionable groups (10 issue-level, 0 of them charged here).
D30 · Dependency Vulnerabilities
1 finding(s): 0 critical, 0 high, 1 medium, 0 low.
What to do
- Resolve the 1 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
D34 · Knowledge Freshness
8 of 24 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is src/Core/Logging.fs. Counted over 24 of the 33 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 8 Orphaned file finding(s) in Knowledge Freshness — start with Logging.fs, QuickInfo.fs, LineLens.fs. — One of this dimension's main actionable groups (8 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
No strong hidden change-coupling between production files.
D36 · Supply-chain Provenance & Signing
0/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).
What to do
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 2 platform declaration(s) and 7 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
AX3 · Project dependency cycles
AX4 · Dependency direction
GD1 · Unfinished & placeholder code
M1 · Documentation (README)
What to do
- Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
- No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
- Add a C4 context/container diagram (Structurizr, PlantUML or Mermaid) or an architecture.md overview.
M3 · Folder & project structure
M4 · Documentation accuracy
- README.md names .NET 8, but the projects target .NET 10. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — README.md:25
What to do
- Reconcile the README with reality: README.md names .NET 8, but the projects target .NET 10.
P1 · CI/CD gates
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 3 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner. — REDACTED:7
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.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
P6 · Release Hygiene
PF3 · Async & latency hygiene
X23 · Unguarded diagnostic materialisation
X27 · Collection changed while being enumerated
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 82% | Checked 4 of 11 | Solid. |
| Architecture | 91% | Adequate — gated by D26 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Maturity | 53% | Adequate — gated by M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 52% | Adequate — gated by D8, P3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 57% | Checked 4 of 10 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Performance | 100% | Exemplary | Strongest area. |
Not evidenced — 4 control(s) we could not find positive evidence for
- C3 Audit Trail — Not assessed: these audit controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks audit controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- C4 Data Retention — Not assessed: these retention controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks retention controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- C5 Data-Subject Rights — Not assessed: these data-subject rights controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks data-subject rights controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 74 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.
- AX1 Captive dependencies — Not applicable: this repository's F# imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's.
- AX2 Stateful singletons — Not applicable: Its F# is compiled by Fable to JavaScript, which runs on one event loop, so no two requests write a shared object at the same instant. TypeScript/JavaScript runs each process's requests on one event loop, so no two requests write a shared object at the same instant (interleaving across an await is a different defect).
- AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX6 Interface segregation — not assessed — interface segregation is computed over a type surface that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AX8 Test isolation — no test/production split to check
- AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
- AXB1 Runtime evidence locked — no reproducible boot — This repository has nothing the runtime tiers could boot or serve — no markup, no UI framework or web-server dependency, no UI component source, no native UI project and no API definition — nothing here is a surface to boot — so runtime a11y/egress/header evidence has no subject here. Not applicable: this is neither a gap in the scan nor a finding about your code.
- C1 Data Protection — Not assessed: these personal data controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks personal data controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- C2 Access Controls — Not assessed: these authorization controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks authorization controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- D10 Test Quality — No tests were found in the analyzed repository to assess for quality.
- D11 Test Reliability — No test suite was found to re-run, so reliability couldn't be assessed. Two searches produced that zero and both came back empty: the classifier that reads the loaded workspace recognised no suite it could run, and a walk of the source on disk — which covers the JS/TS `*.test.*` and `*.spec.*` conventions and probes for a Pester suite — found no test source in any other ecosystem either. Neither search reaches a suite that is missing from the loaded workspace and carries no name either walk recognises, so this is 'no suite found by those two searches', not a verdict that the repository has none.
- D17 Explicit Debt — the C# workspace loaded 0 projects, so explicit-debt density could not be measured
- D18 Solution Shape — D18 scores the shape of a C#/VB .NET solution; this repository's .NET projects are all F# (.fsproj), which the C#/VB workspace does not load, so the dimension does not apply.
- D20 ADR Quality — N/A — ADRs are expected on deployable products with a user-facing host, not consumed libraries; no ADR log is required here.
- D21 Naming Consistency — Naming consistency is measured on C# and TypeScript only; F#, JavaScript not measured.
- D22 Internal API Consistency — The exposed public-API surface could not be collected — no C#/VB projects loaded.
- D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D24 Comment Value — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only; comments in this repository's .fs source were not judged.
- D25 ADR Conformance — no ADRs to check
- D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
- D32 Data Compliance (PII/GDPR) — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D7 Architectural Integrity — no checkable ADRs and no dependency cycles — architectural integrity not assessed
- DM1 Domain Modelling — applicable but not scored (2 of 3 signals for this style — below the bar we score at): 27 value object(s); 3 domain event(s); its domain events are published by services or handlers — no domain entity raises one
- ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
- ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
- P2 Observability — This repository's F# source (1 module(s), 33 file(s) read) declares no entry point and bootstraps no server, and nothing here deploys a service — it is a library, run inside whatever hosts it, so production observability (structured logging, tracing/metrics, health checks) is N/A. If it grows a binary or a service, the dimension reactivates.
- P7 Outbound HTTP resilience — not measured — the application kind could not be determined for this repo
- P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
- P9 Domain vs controller coverage — coverage not measured: this check compares the coverage of the analyzer's own test run across the domain and web layers, and that run measured none here — Test coverage (D8) says why
- PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for a BenchmarkDotNet reference in an .fsproj or .vbproj, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
- PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
- S1 Web-Security Posture — Not assessed: these web-security controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks web-security controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X1 Async correctness — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X10 Duplicated predicate — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X12 Unreachable branch — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X13 Undrained process stream — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X14 Bypassable address classification — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X15 Unvalidated length from an untrusted reader — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X16 Unfloored truncation loop — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X17 Uncapped recursion over a caller-supplied document — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X18 Disposal-pattern correctness — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X19 Unrestored process-global state — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X2 Cancellation propagation — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X20 Mistyped argument guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X21 Side-effecting pattern guard — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X22 Contradicted release guard — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X24 Document value interpolated into markup unescaped — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X25 Inert configuration knob — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X26 Unsynchronised callback handoff — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X28 Index access outside its own emptiness guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X29 Per-element action decided by a fixed element — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X3 Exception handling — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X30 Support guard that admits what it rejects — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X32 Type resolved by simple name across every loaded assembly — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X4 Structured logging — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X5 Nullable reference types — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X6 Hand-rolled structured-format parsing — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- 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 — 17 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- No automated tests
Serious — 44 finding(s)
- FileTooLong: Components/SolutionExplorer.fs src/Components/SolutionExplorer.fs
- FileTooLong: Core/LanguageService.fs src/Core/LanguageService.fs
- FileTooLong: Core/Project.fs src/Core/Project.fs
- FileTooLong: Components/Fsi.fs src/Components/Fsi.fs
- Duplicated block (9 lines × 2) src/Components/SolutionExplorer.fs:198
- Duplicated block (9 lines × 2) src/Components/SolutionExplorer.fs:1063
- Duplicated block (9 lines × 2) src/Core/LanguageService.fs:555
- Duplicated block (9 lines × 2) src/Components/SolutionExplorer.fs:974
- Hotspot: src/Core/LanguageService.fs src/Core/LanguageService.fs:934
- Hotspot: src/Components/SolutionExplorer.fs src/Components/SolutionExplorer.fs:938
- Hotspot: src/Components/TestExplorer.fs src/Components/TestExplorer.fs:1479
- Duplicated block (12 lines × 3) src/Components/MSBuild.fs:139
- Duplicated block (12 lines × 3) src/Core/LanguageService.fs:497
- Duplicated block (7 lines × 2) src/Components/SolutionExplorer.fs:1077
- Duplicated block (7 lines × 2) src/Core/LanguageService.fs:463
- Duplicated block (13 lines × 2) src/Core/LanguageService.fs:538
- Duplicated block (13 lines × 2) src/Components/TestExplorer.fs:1082
- SolutionExplorer.activate (cyclomatic 76) src/Components/SolutionExplorer.fs:938
- SolutionExplorer.createProvider (cyclomatic 43) src/Components/SolutionExplorer.fs:454
- LanguageService.getOptions (cyclomatic 40) src/Core/LanguageService.fs:934
- SolutionExplorer.getSolutionModel (cyclomatic 20) src/Components/SolutionExplorer.fs:287
- SolutionExplorer.newProject (cyclomatic 16) src/Components/SolutionExplorer.fs:858
- SolutionExplorer.activate (cognitive 91) src/Components/SolutionExplorer.fs:938
- SolutionExplorer.newProject (cognitive 47) src/Components/SolutionExplorer.fs:858
- LanguageService.getOptions (cognitive 36) src/Core/LanguageService.fs:934
- Debugger.makeDebugConfigFor (cognitive 25) src/Components/Debugger.fs:237
- Panel.mapContent (cognitive 22) src/Components/InfoPanel.fs:68
- Document.|FSharp|CSharp|VB|FSharpScript|Markdown|Other| (cognitive 21) src/Core/Utils.fs:122
- SolutionExplorer.getSolutionModel (cognitive 20) src/Components/SolutionExplorer.fs:287
- Watcher.handler (cognitive 17) src/Components/Fsi.fs:138
- REDACTED
- REDACTED
- REDACTED
- Duplicated block (20 lines × 2) src/Components/Fsi.fs:549
- Duplicated block (16 lines × 2) src/Components/MSBuild.fs:142
- Duplicated block (12 lines × 2) src/Core/Project.fs:131
- Duplicated block (10 lines × 3) src/Core/Project.fs:134
- Duplicated block (15 lines × 2) src/Components/QuickInfo.fs:20
- Duplicated block (10 lines × 2) src/Core/LanguageService.fs:365
- Duplicated block (8 lines × 3) src/Core/LanguageService.fs:367
- Duplicated block (6 lines × 2) src/Components/SolutionExplorer.fs:552
- Duplicated block (11 lines × 2) src/Components/LineLens/LineLens.fs:4
- Duplicated block (11 lines × 5) src/Core/LanguageService.fs:531
- Duplicated block (10 lines × 4) src/Core/LanguageService.fs:354
Minor — 26 finding(s)
- Outdated (npm): balanced-match
- Outdated (npm): brace-expansion
- Outdated (npm): domhandler
- Outdated (npm): entities
- Outdated (npm): htmlparser2 package.json:7
- Outdated (npm): minimatch
- Outdated (npm): vscode-languageclient package.json:10
- Outdated (npm): which
- Orphaned file src/Core/Logging.fs:1
- Orphaned file src/Components/QuickInfo.fs:1
- Orphaned file src/Components/LineLens/LineLens.fs:1
- Orphaned file src/Components/QuickInfoProject.fs:1
- Orphaned file src/Components/LineLens/PipelineHints.fs:1
- Orphaned file src/Core/FsProjEdit.fs:1
- Orphaned file src/Components/Gitignore.fs:1
- Orphaned file src/Core/Environment.fs:1
- Off-boarding risk: anonymized user #1
- Projects may be oversized for their cohesion
- Orphaned files with no living knowledge
- REDACTED
- REDACTED
- REDACTED
- No ADRs
- No architecture diagram/doc
- README/code drift README.md:25
- No SAST REDACTED:7
Minor — 16 finding(s)
- Outdated (npm): @xmldom/xmldom
- Outdated (npm): concat-map
- Outdated (npm): dom-serializer
- Outdated (npm): domelementtype
- Outdated (npm): domutils
- Outdated (npm): isexe
- Outdated (npm): marked
- Outdated (npm): path-key
- Outdated (npm): semver
- Outdated (npm): shebang-regex
- Outdated (npm): vscode-jsonrpc
- Outdated (npm): vscode-languageserver-protocol
- Outdated (npm): vscode-languageserver-types
- Outdated (npm): xpath
- Outdated: Fable.Core
- Outdated: FSharp.Core
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-3f8dce48d3ac4c51aceac9645ef335a4/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-3f8dce48d3ac4c51aceac9645ef335a4/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 . | 17 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | dotnet | — | dotnet list ionide-fsharp-vscode.slnx package --vulnerable --include-transitive --format json | 1 | artifacts/raw/dotnet-vulnerable.json |
| D31 · IaC & Container Security | trivy | — | trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan. | 0 | — |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. | 0 | — |
| D37 · Vulnerability-disclosure Policy | disclosure | — | disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . | 0 | artifacts/raw/trivy-fs.json |