Executive summary
JetBrains/resharper-fsharp falls short of our standard for production, in part because it has sets of compiler warnings switched off in projects. It scores 42 out of 100 and is rated Weak, and 20 of its 31 critical findings are security problems.
Code Health, at 29, is the weakest lens and counts most in the score. The best first step is fixing the silenced warnings, worth about 12 points. Replacing the six exposed passwords or keys and switching the old ones off comes next, worth about 4 points. Raising Code Health to 70 would lift the score to about 52.
Six passwords or keys in the code and six in the code's history are open to anyone who can read the repository. Six pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with, and two weaknesses in the code could be used by an attacker. Replacing each exposed password or key, pinning each tool to an exact version and fixing the weaknesses the scanner points to would close these risks. The 11 sets of compiler warnings switched off in projects need turning back on in the build file.
The product code is 71,226 lines, about €160,000 to rebuild. The check for malicious packages couldn't finish, so that result is missing, not a clean pass.
If Code Health rose from 29 to 70, the lowest score rated Strong, the score would rise from 42 to about 52.
New since the last survey: 25 findings
- Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/CodeCompletion/Rules/GenerateLambdaRule.fs
- Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/CodeCompletion/Rules/NameSuggestionRule.fs
- Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) ReSharper.FSharp/src/FSharp/FSharp.Psi.Intentions/src/QuickFixes/ImportMemberFix.fs
- Code Duplication · Edited copies of one member (3 members, 19+ corresponding lines) ReSharper.FSharp/src/FSharp/FSharp.Psi.Intentions/src/QuickFixes/RemoveRedundantAttributeParensFix.fs
- Code Duplication · Edited copy of a member (20 corresponding lines) ReSharper.FSharp/src/FSharp/FSharp.Psi.Intentions/src/QuickFixes/RemoveUnnecessaryUpcastFix.fs
- Code Duplication · Edited copy of a member (15 corresponding lines) rider-fsharp/src/main/java/com/jetbrains/rider/plugins/fsharp/projectView/FSharpMoveProviderExtension.kt
- Code Duplication · Edited copy of a member (17 corresponding lines) ReSharper.FSharp/src/FSharp/FSharp.Psi.Intentions/src/QuickFixes/RemoveConstructorFix.fs
- Code Duplication · Edited copy of a member (9 corresponding lines) ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/Comment/FSharpDocCommentElementsItemsProvider.fs
- Code Duplication · Edited copies of one member (4 members, 7+ corresponding lines) ReSharper.FSharp/src/FSharp/FSharp.Common/src/ProjectModel/Host/ZoneMarker.fs
- Code Duplication · Edited copy of a member (8 corresponding lines) ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/AI/ZoneMarker.fs
- Code Duplication · Edited copies of one member (3 members, 8+ corresponding lines) ReSharper.FSharp/src/FSharp/FSharp.Common/src/Checker/ZoneMarker.fs
- Code Duplication · Edited copies of one member (4 members, 8+ corresponding lines) ReSharper.FSharp/src/FSharp/FSharp.Psi.Daemon/PsiFeaturesNamespaceZoneMarker.fs
- Code Duplication · Duplicated block (20–22 lines × 2) ReSharper.FSharp/src/FSharp/FSharp.Psi.Services/src/Util/StringLiteralsUtil.fs
- Code Duplication · Duplicated block (9 lines × 2) ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/CodeCompletion/Rules/GenerateMatchExprPatternsRule.fs
- Code Duplication · Duplicated block (5 lines × 2) ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/CodeCompletion/Rules/GenerateMatchExprPatternsRule.fs
- Change Coupling · Change coupling: FsiHost.fs ↔ SandboxDocumentLanguageSupportFSharpScript.fs ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/Fsi/FsiHost.fs
- Platform End-of-Life · End-of-life runtime: .NET net6.0 rider-fsharp/src/test/testData/solutions/ConsoleAppTwoTargetFrameworks/CoreConsoleApp.fsproj
- Platform End-of-Life · End-of-life runtime: .NET net6.0 rider-fsharp/src/test/testData/solutions/CoreConsoleApp/CoreConsoleApp.fsproj
- Platform End-of-Life · End-of-life runtime: .NET net6.0 rider-fsharp/src/test/testData/solutions/CsvTypeProvider/TypeProviderLibrary/TypeProviderLibrary.fsproj
- Platform End-of-Life · End-of-life runtime: .NET net6.0 rider-fsharp/src/test/testData/solutions/FableApp/FableApp.fsproj
- Platform End-of-Life · End-of-life runtime: .NET net6.0 rider-fsharp/src/test/testData/solutions/ReferencesOrder/ReferencesOrder.fsproj
- Platform End-of-Life · End-of-life runtime: .NET net6.0 rider-fsharp/src/test/testData/solutions/SwaggerProviderCSharp/CSharpLibrary/CSharpLibrary.csproj
- Platform End-of-Life · End-of-life runtime: .NET net6.0 rider-fsharp/src/test/testData/solutions/SwaggerProviderCSharp/SwaggerProviderLibrary/SwaggerProviderLibrary.fsproj
- Platform End-of-Life · End-of-life runtime: .NET netcoreapp3.1 ReSharper.FSharp/src/FSharp.TypeProviders.Host/FSharp.TypeProviders.Host.NetCore/FSharp.TypeProviders.Host.NetCore.csproj
- Platform End-of-Life · End-of-life runtime: .NET netcoreapp3.1 rider-fsharp/src/test/testData/solutions/FormatCodeApp/FormatCodeApp/FormatCodeApp.fsproj
Fixed since the last survey: 16 findings
- Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/CodeCompletion/Rules/GenerateLambdaRule.fs
- Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/CodeCompletion/Rules/NameSuggestionRule.fs
- Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) ReSharper.FSharp/src/FSharp/FSharp.Psi.Intentions/src/QuickFixes/ImportMemberFix.fs
- Code Duplication · Duplicated block (6 lines × 2) ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/CodeCompletion/Rules/UnionCasePatternRule.fs
- Code Duplication · Duplicated block (6 lines × 2) ReSharper.FSharp/src/FSharp/FSharp.Psi.Services/src/Util/FSharpBindUtil.fs
- Code Duplication · Duplicated block (27 lines × 2) rider-fsharp/projectTemplates/FSharpClassLibraryTemplate/AssemblyInfo.fs
- Code Coverage · Coverage not measured — no coverage collector is wired up
- Test Distribution · Tests outside the analyzed solution
- Change Coupling · Change coupling clique: FSharpVcsCodeVisionRangesProviderStage.fs, FsiHost.fs, SandboxDocumentLanguageSupportFSharpScript.fs ReSharper.FSharp/src/FSharp/FSharp.Psi.Daemon/src/Stages/FSharpVcsCodeVisionRangesProviderStage.fs
- Change Coupling · Change coupling: FsiOptionsPage.fs ↔ FSharpQuickDefinitionService.fs ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/Fsi/FsiOptionsPage.fs
- Change Coupling · Change coupling: FSharpGeneratedMemberBase.cs ↔ FSharpTypeMember.cs ReSharper.FSharp/src/FSharp/FSharp.Psi/src/Impl/DeclaredElement/CompilerGenerated/FSharpGeneratedMemberBase.cs
- Change Coupling · Change coupling: REDACTED ↔ REDACTED REDACTED
- Change Coupling · Change coupling: FSharpCodeStructure.fs ↔ FSharpQuickDefinitionService.fs ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/CodeStructure/FSharpCodeStructure.fs
- Platform End-of-Life · End-of-life runtime: .NET net6.0 rider-fsharp/src/test/testData/solutions/SwaggerProviderCSharp/CSharpLibrary/CSharpLibrary.csproj
- Platform End-of-Life · End-of-life runtime: .NET netcoreapp3.1 ReSharper.FSharp/src/FSharp.TypeProviders.Host/FSharp.TypeProviders.Host.NetCore/FSharp.TypeProviders.Host.NetCore.csproj
- Documentation (README) · README may be stale
Rebuild cost: about €160,000 · Estimate
| Cost to rebuild | €54,000 to €270,000, for 896 to 2,864 hours of work, about 1.1 person-years for 1 to 3 engineers |
|---|---|
| Difficulty of the problem | Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.7 at a score of 42. 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 | Medium: 71,226 lines of product code |
| Comment lines | The estimate prices 70,731 lines. Comment lines count towards the size of 71,226 lines but aren't priced as work. |
| What it is not | Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one. |
Top priorities
Diagnosis: what the measurements show together
Architecture — bounded-context dependency graph
Architecture: which parts of the code depend on which
| uses → | 1 DocumentRangeExtensions | 2 FSharpFileSystemPathExtensions | 3 JetBrains.ReSharper.Plugins.FSharp.Checker.FcsCheckerService | 4 JetBrains.ReSharper.Plugins.FSharp.Psi.Daemon.Analyzers.Util | 5 JetBrains.ReSharper.Plugins.FSharp.Psi.Features | 6 JetBrains.ReSharper.Plugins.FSharp.Util.SettingsStoreUtil | 7 com.jetbrains.rider.ideaInterop.fileTypes.fsharp.lexer | 8 JetBrains.ReSharper.Plugins.FSharp.ProjectModel.Util | 9 JetBrains.ReSharper.Plugins.FSharp.Psi.PsiUtil | 10 JetBrains.ReSharper.Plugins.FSharp.Util.CommonUtil | 11 com.jetbrains.rider.ideaInterop.fileTypes.fsharp.highlighting | 12 com.jetbrains.rider.ideaInterop.fileTypes.fsharp.psi | 13 JetBrains.ReSharper.Plugins.FSharp.Psi.Features.CodeCompletion | 14 JetBrains.ReSharper.Plugins.FSharp.Psi.Features.CodeCompletion.FSharpCodeCompletionContext | 15 JetBrains.ReSharper.Plugins.FSharp.Psi.Features.Daemon.Highlightings | 16 JetBrains.ReSharper.Plugins.FSharp.Psi.Features.Util.FcsTypeUtil | 17 JetBrains.ReSharper.Plugins.FSharp.Psi.LanguageService.Parsing | 18 JetBrains.ReSharper.Plugins.FSharp.Psi.Util.OpensUtil | 19 com.jetbrains.rider.ideaInterop.fileTypes.fsharp.psi.impl | 20 com.jetbrains.rider.plugins.fsharp.services.fsi | 21 JetBrains.ReSharper.Plugins.FSharp.Psi.Daemon.Stages | 22 JetBrains.ReSharper.Plugins.FSharp.Psi.Features.CodeCompletion.Rules.OverrideMemberRule | 23 JetBrains.ReSharper.Plugins.FSharp.Psi.Features.Util.FSharpNamingService | 24 JetBrains.ReSharper.Plugins.FSharp.Psi.Services.Util.FSharpCompletionUtil | 25 JetBrains.ReSharper.Plugins.FSharp.Util.FSharpSymbolUtil | 26 JetBrains.ReSharper.Plugins.FSharp.ProjectModel.Host.ProjectItems.ItemsContainer | 27 JetBrains.ReSharper.Plugins.FSharp.Psi.Features.Generate.GenerateOverrides | 28 JetBrains.ReSharper.Plugins.FSharp.Psi.Features.Intentions | 29 JetBrains.ReSharper.Plugins.FSharp.Psi.Features.ParameterInfo | 30 JetBrains.ReSharper.Plugins.FSharp.Settings | 31 JetBrains.ReSharper.Plugins.FSharp.Shim.FileSystem | 32 JetBrains.ReSharper.Plugins.FSharp.ProjectModel.Scripts | 33 JetBrains.ReSharper.Plugins.FSharp.Services.Formatter | 34 JetBrains.ReSharper.Plugins.FSharp.ProjectModel | 35 JetBrains.ReSharper.Plugins.FSharp.Shim.TypeProviders | 36 JetBrains.ReSharper.Plugins.FSharp.Checker | 37 JetBrains.ReSharper.Plugins.FSharp.Psi.Features.CodeCompletion.Rules | 38 JetBrains.ReSharper.Plugins.FSharp.Psi.Features.Fsi | 39 JetBrains.ReSharper.Plugins.FSharp.Psi.Daemon.Analyzers | 40 JetBrains.ReSharper.Plugins.FSharp.Shim.AssemblyReader |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 DocumentRangeExtensions | ||||||||||||||||||||||||||||||||||||||||
| 2 FSharpFileSystemPathExtensions | ||||||||||||||||||||||||||||||||||||||||
| 3 JetBrains.ReSharper.Plugins.FSharp.Checker.FcsCheckerService | ||||||||||||||||||||||||||||||||||||||||
| 4 JetBrains.ReSharper.Plugins.FSharp.Psi.Daemon.Analyzers.Util | ||||||||||||||||||||||||||||||||||||||||
| 5 JetBrains.ReSharper.Plugins.FSharp.Psi.Features | ||||||||||||||||||||||||||||||||||||||||
| 6 JetBrains.ReSharper.Plugins.FSharp.Util.SettingsStoreUtil | ||||||||||||||||||||||||||||||||||||||||
| 7 com.jetbrains.rider.ideaInterop.fileTypes.fsharp.lexer | ||||||||||||||||||||||||||||||||||||||||
| 8 JetBrains.ReSharper.Plugins.FSharp.ProjectModel.Util | 1 | |||||||||||||||||||||||||||||||||||||||
| 9 JetBrains.ReSharper.Plugins.FSharp.Psi.PsiUtil | 1 | |||||||||||||||||||||||||||||||||||||||
| 10 JetBrains.ReSharper.Plugins.FSharp.Util.CommonUtil | 1 | |||||||||||||||||||||||||||||||||||||||
| 11 com.jetbrains.rider.ideaInterop.fileTypes.fsharp.highlighting | 1 | |||||||||||||||||||||||||||||||||||||||
| 12 com.jetbrains.rider.ideaInterop.fileTypes.fsharp.psi | 1 | |||||||||||||||||||||||||||||||||||||||
| 13 JetBrains.ReSharper.Plugins.FSharp.Psi.Features.CodeCompletion | 1 | 2 | 2 | 2 | ||||||||||||||||||||||||||||||||||||
| 14 JetBrains.ReSharper.Plugins.FSharp.Psi.Features.CodeCompletion.FSharpCodeCompletionContext | 1 | |||||||||||||||||||||||||||||||||||||||
| 15 JetBrains.ReSharper.Plugins.FSharp.Psi.Features.Daemon.Highlightings | 3 | 1 | ||||||||||||||||||||||||||||||||||||||
| 16 JetBrains.ReSharper.Plugins.FSharp.Psi.Features.Util.FcsTypeUtil | 2 | |||||||||||||||||||||||||||||||||||||||
| 17 JetBrains.ReSharper.Plugins.FSharp.Psi.LanguageService.Parsing | 2 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 18 JetBrains.ReSharper.Plugins.FSharp.Psi.Util.OpensUtil | 1 | 1 | 2 | |||||||||||||||||||||||||||||||||||||
| 19 com.jetbrains.rider.ideaInterop.fileTypes.fsharp.psi.impl | 1 | 18 | ||||||||||||||||||||||||||||||||||||||
| 20 com.jetbrains.rider.plugins.fsharp.services.fsi | 2 | |||||||||||||||||||||||||||||||||||||||
| 21 JetBrains.ReSharper.Plugins.FSharp.Psi.Daemon.Stages | 1 | 3 | 6 | 1 | ||||||||||||||||||||||||||||||||||||
| 22 JetBrains.ReSharper.Plugins.FSharp.Psi.Features.CodeCompletion.Rules.OverrideMemberRule | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 23 JetBrains.ReSharper.Plugins.FSharp.Psi.Features.Util.FSharpNamingService | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 24 JetBrains.ReSharper.Plugins.FSharp.Psi.Services.Util.FSharpCompletionUtil | 1 | |||||||||||||||||||||||||||||||||||||||
| 25 JetBrains.ReSharper.Plugins.FSharp.Util.FSharpSymbolUtil | 1 | |||||||||||||||||||||||||||||||||||||||
| 26 JetBrains.ReSharper.Plugins.FSharp.ProjectModel.Host.ProjectItems.ItemsContainer | 6 | 1 | 6 | 2 | ||||||||||||||||||||||||||||||||||||
| 27 JetBrains.ReSharper.Plugins.FSharp.Psi.Features.Generate.GenerateOverrides | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 28 JetBrains.ReSharper.Plugins.FSharp.Psi.Features.Intentions | 1 | 4 | 2 | |||||||||||||||||||||||||||||||||||||
| 29 JetBrains.ReSharper.Plugins.FSharp.Psi.Features.ParameterInfo | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 30 JetBrains.ReSharper.Plugins.FSharp.Settings | 3 | 4 | 1 | |||||||||||||||||||||||||||||||||||||
| 31 JetBrains.ReSharper.Plugins.FSharp.Shim.FileSystem | 2 | 2 | 1 | |||||||||||||||||||||||||||||||||||||
| 32 JetBrains.ReSharper.Plugins.FSharp.ProjectModel.Scripts | 4 | 1 | 2 | 1 | 2 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||
| 33 JetBrains.ReSharper.Plugins.FSharp.Services.Formatter | 2 | 1 | 1 | 1 | 2 | |||||||||||||||||||||||||||||||||||
| 34 JetBrains.ReSharper.Plugins.FSharp.ProjectModel | 2 | 2 | 1 | |||||||||||||||||||||||||||||||||||||
| 35 JetBrains.ReSharper.Plugins.FSharp.Shim.TypeProviders | 1 | 1 | 1 | 2 | 2 | |||||||||||||||||||||||||||||||||||
| 36 JetBrains.ReSharper.Plugins.FSharp.Checker | 2 | 3 | 6 | 7 | 1 | 2 | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||
| 37 JetBrains.ReSharper.Plugins.FSharp.Psi.Features.CodeCompletion.Rules | 1 | 1 | 14 | 2 | 1 | 1 | ||||||||||||||||||||||||||||||||||
| 38 JetBrains.ReSharper.Plugins.FSharp.Psi.Features.Fsi | 2 | 1 | 2 | 1 | ||||||||||||||||||||||||||||||||||||
| 39 JetBrains.ReSharper.Plugins.FSharp.Psi.Daemon.Analyzers | 3 | 3 | 1 | |||||||||||||||||||||||||||||||||||||
| 40 JetBrains.ReSharper.Plugins.FSharp.Shim.AssemblyReader | 3 | 1 | 3 | 1 | 1 | 1 | 1 |
8→2 JetBrains.ReSharper.Plugins.FSharp.ProjectModel.Util uses FSharpFileSystemPathExtensions✕
- Connections
- 1 pair of types, where a type in JetBrains.ReSharper.Plugins.FSharp.ProjectModel.Util uses a type in FSharpFileSystemPathExtensions.
- The types involved
JetBrains.ReSharper.Plugins.FSharp.ProjectModel.Util.Util→FSharpFileSystemPathExtensions.VirtualFileSystemPath
- Direction
- JetBrains.ReSharper.Plugins.FSharp.ProjectModel.Util uses FSharpFileSystemPathExtensions, so a change to FSharpFileSystemPathExtensions can break JetBrains.ReSharper.Plugins.FSharp.ProjectModel.Util, while a change to JetBrains.ReSharper.Plugins.FSharp.ProjectModel.Util can't break FSharpFileSystemPathExtensions.
- Position
- Below the diagonal: JetBrains.ReSharper.Plugins.FSharp.ProjectModel.Util uses a module listed above it, which is the healthy direction.
9→1 JetBrains.ReSharper.Plugins.FSharp.Psi.PsiUtil uses DocumentRangeExtensions✕
- Connections
- 1 pair of types, where a type in JetBrains.ReSharper.Plugins.FSharp.Psi.PsiUtil uses a type in DocumentRangeExtensions.
- The types involved
JetBrains.ReSharper.Plugins.FSharp.Psi.PsiUtil.PsiUtil→DocumentRangeExtensions.DocumentRange
- Direction
- JetBrains.ReSharper.Plugins.FSharp.Psi.PsiUtil uses DocumentRangeExtensions, so a change to DocumentRangeExtensions can break JetBrains.ReSharper.Plugins.FSharp.Psi.PsiUtil, while a change to JetBrains.ReSharper.Plugins.FSharp.Psi.PsiUtil can't break DocumentRangeExtensions.
- Position
- Below the diagonal: JetBrains.ReSharper.Plugins.FSharp.Psi.PsiUtil uses a module listed above it, which is the healthy direction.
10→2 JetBrains.ReSharper.Plugins.FSharp.Util.CommonUtil uses FSharpFileSystemPathExtensions✕
- Connections
- 1 pair of types, where a type in JetBrains.ReSharper.Plugins.FSharp.Util.CommonUtil uses a type in FSharpFileSystemPathExtensions.
- The types involved
JetBrains.ReSharper.Plugins.FSharp.Util.CommonUtil.CommonUtil→FSharpFileSystemPathExtensions.VirtualFileSystemPath
- Direction
- JetBrains.ReSharper.Plugins.FSharp.Util.CommonUtil uses FSharpFileSystemPathExtensions, so a change to FSharpFileSystemPathExtensions can break JetBrains.ReSharper.Plugins.FSharp.Util.CommonUtil, while a change to JetBrains.ReSharper.Plugins.FSharp.Util.CommonUtil can't break FSharpFileSystemPathExtensions.
- Position
- Below the diagonal: JetBrains.ReSharper.Plugins.FSharp.Util.CommonUtil uses a module listed above it, which is the healthy direction.
11→7 com.jetbrains.rider.ideaInterop.fileTypes.fsharp.highlighting uses com.jetbrains.rider.ideaInterop.fileTypes.fsharp.lexer✕
- Connections
- 1 pair of types, where a type in com.jetbrains.rider.ideaInterop.fileTypes.fsharp.highlighting uses a type in com.jetbrains.rider.ideaInterop.fileTypes.fsharp.lexer.
- The types involved
com.jetbrains.rider.ideaInterop.fileTypes.fsharp.highlighting.FSharpSyntaxHighlighter→com.jetbrains.rider.ideaInterop.fileTypes.fsharp.lexer.FSharpLexer
- Direction
- com.jetbrains.rider.ideaInterop.fileTypes.fsharp.highlighting uses com.jetbrains.rider.ideaInterop.fileTypes.fsharp.lexer, so a change to com.jetbrains.rider.ideaInterop.fileTypes.fsharp.lexer can break com.jetbrains.rider.ideaInterop.fileTypes.fsharp.highlighting, while a change to com.jetbrains.rider.ideaInterop.fileTypes.fsharp.highlighting can't break com.jetbrains.rider.ideaInterop.fileTypes.fsharp.lexer.
- Position
- Below the diagonal: com.jetbrains.rider.ideaInterop.fileTypes.fsharp.highlighting uses a module listed above it, which is the healthy direction.
12→7 com.jetbrains.rider.ideaInterop.fileTypes.fsharp.psi uses com.jetbrains.rider.ideaInterop.fileTypes.fsharp.lexer✕
- Connections
- 1 pair of types, where a type in com.jetbrains.rider.ideaInterop.fileTypes.fsharp.psi uses a type in com.jetbrains.rider.ideaInterop.fileTypes.fsharp.lexer.
- The types involved
com.jetbrains.rider.ideaInterop.fileTypes.fsharp.psi.FSharpInterpolatedStringLiteralExpressionPart→com.jetbrains.rider.ideaInterop.fileTypes.fsharp.lexer.FSharpTokenNodeType
- Direction
- com.jetbrains.rider.ideaInterop.fileTypes.fsharp.psi uses com.jetbrains.rider.ideaInterop.fileTypes.fsharp.lexer, so a change to com.jetbrains.rider.ideaInterop.fileTypes.fsharp.lexer can break com.jetbrains.rider.ideaInterop.fileTypes.fsharp.psi, while a change to com.jetbrains.rider.ideaInterop.fileTypes.fsharp.psi can't break com.jetbrains.rider.ideaInterop.fileTypes.fsharp.lexer.
- Position
- Below the diagonal: com.jetbrains.rider.ideaInterop.fileTypes.fsharp.psi uses a module listed above it, which is the healthy direction.
13→1 JetBrains.ReSharper.Plugins.FSharp.Psi.Features.CodeCompletion uses DocumentRangeExtensions✕
- Connections
- 1 pair of types, where a type in JetBrains.ReSharper.Plugins.FSharp.Psi.Features.CodeCompletion uses a type in DocumentRangeExtensions.
- The types involved
JetBrains.ReSharper.Plugins.FSharp.Psi.Features.CodeCompletion.FSharpReparseContext→DocumentRangeExtensions.TreeTextRange
- Direction
- JetBrains.ReSharper.Plugins.FSharp.Psi.Features.CodeCompletion uses DocumentRangeExtensions, so a change to DocumentRangeExtensions can break JetBrains.ReSharper.Plugins.FSharp.Psi.Features.CodeCompletion, while a change to JetBrains.ReSharper.Plugins.FSharp.Psi.Features.CodeCompletion can't break DocumentRangeExtensions.
- Position
- Below the diagonal: JetBrains.ReSharper.Plugins.FSharp.Psi.Features.CodeCompletion uses a module listed above it, which is the healthy direction.
13→2 JetBrains.ReSharper.Plugins.FSharp.Psi.Features.CodeCompletion uses FSharpFileSystemPathExtensions✕
- Connections
- 2 pairs of types, where a type in JetBrains.ReSharper.Plugins.FSharp.Psi.Features.CodeCompletion uses a type in FSharpFileSystemPathExtensions.
- The types involved
JetBrains.ReSharper.Plugins.FSharp.Psi.Features.CodeCompletion.FSharpFolderCompletionItem→FSharpFileSystemPathExtensions.VirtualFileSystemPathJetBrains.ReSharper.Plugins.FSharp.Psi.Features.CodeCompletion.FSharpPathLookupItem→FSharpFileSystemPathExtensions.VirtualFileSystemPath
- Direction
- JetBrains.ReSharper.Plugins.FSharp.Psi.Features.CodeCompletion uses FSharpFileSystemPathExtensions, so a change to FSharpFileSystemPathExtensions can break JetBrains.ReSharper.Plugins.FSharp.Psi.Features.CodeCompletion, while a change to JetBrains.ReSharper.Plugins.FSharp.Psi.Features.CodeCompletion can't break FSharpFileSystemPathExtensions.
- Position
- Below the diagonal: JetBrains.ReSharper.Plugins.FSharp.Psi.Features.CodeCompletion uses a module listed above it, which is the healthy direction.
13→5 JetBrains.ReSharper.Plugins.FSharp.Psi.Features.CodeCompletion uses JetBrains.ReSharper.Plugins.FSharp.Psi.Features✕
- Connections
- 2 pairs of types, where a type in JetBrains.ReSharper.Plugins.FSharp.Psi.Features.CodeCompletion uses a type in JetBrains.ReSharper.Plugins.FSharp.Psi.Features.
- The types involved
JetBrains.ReSharper.Plugins.FSharp.Psi.Features.CodeCompletion.FSharpCodeCompletionContextProvider→JetBrains.ReSharper.Plugins.FSharp.Psi.Features.FSharpXmlDocServiceJetBrains.ReSharper.Plugins.FSharp.Psi.Features.CodeCompletion.FcsLookupCandidate→JetBrains.ReSharper.Plugins.FSharp.Psi.Features.FSharpXmlDocService
- Direction
- JetBrains.ReSharper.Plugins.FSharp.Psi.Features.CodeCompletion uses JetBrains.ReSharper.Plugins.FSharp.Psi.Features, so a change to JetBrains.ReSharper.Plugins.FSharp.Psi.Features can break JetBrains.ReSharper.Plugins.FSharp.Psi.Features.CodeCompletion, while a change to JetBrains.ReSharper.Plugins.FSharp.Psi.Features.CodeCompletion can't break JetBrains.ReSharper.Plugins.FSharp.Psi.Features.
- Position
- Below the diagonal: JetBrains.ReSharper.Plugins.FSharp.Psi.Features.CodeCompletion uses a module listed above it, which is the healthy direction.
13→9 JetBrains.ReSharper.Plugins.FSharp.Psi.Features.CodeCompletion uses JetBrains.ReSharper.Plugins.FSharp.Psi.PsiUtil✕
- Connections
- 2 pairs of types, where a type in JetBrains.ReSharper.Plugins.FSharp.Psi.Features.CodeCompletion uses a type in JetBrains.ReSharper.Plugins.FSharp.Psi.PsiUtil.
- The types involved
JetBrains.ReSharper.Plugins.FSharp.Psi.Features.CodeCompletion.FSharpCodeCompletionContext→JetBrains.ReSharper.Plugins.FSharp.Psi.PsiUtil.ITreeNodeJetBrains.ReSharper.Plugins.FSharp.Psi.Features.CodeCompletion.FSharpReparsedCodeCompletionContext→JetBrains.ReSharper.Plugins.FSharp.Psi.PsiUtil.ITreeNode
- Direction
- JetBrains.ReSharper.Plugins.FSharp.Psi.Features.CodeCompletion uses JetBrains.ReSharper.Plugins.FSharp.Psi.PsiUtil, so a change to JetBrains.ReSharper.Plugins.FSharp.Psi.PsiUtil can break JetBrains.ReSharper.Plugins.FSharp.Psi.Features.CodeCompletion, while a change to JetBrains.ReSharper.Plugins.FSharp.Psi.Features.CodeCompletion can't break JetBrains.ReSharper.Plugins.FSharp.Psi.PsiUtil.
- Position
- Below the diagonal: JetBrains.ReSharper.Plugins.FSharp.Psi.Features.CodeCompletion uses a module listed above it, which is the healthy direction.
14→9 JetBrains.ReSharper.Plugins.FSharp.Psi.Features.CodeCompletion.FSharpCodeCompletionContext uses JetBrains.ReSharper.Plugins.FSharp.Psi.PsiUtil✕
- Connections
- 1 pair of types, where a type in JetBrains.ReSharper.Plugins.FSharp.Psi.Features.CodeCompletion.FSharpCodeCompletionContext uses a type in JetBrains.ReSharper.Plugins.FSharp.Psi.PsiUtil.
- The types involved
JetBrains.ReSharper.Plugins.FSharp.Psi.Features.CodeCompletion.FSharpCodeCompletionContext.FSharpCodeCompletionContext→JetBrains.ReSharper.Plugins.FSharp.Psi.PsiUtil.ITreeNode
- Direction
- JetBrains.ReSharper.Plugins.FSharp.Psi.Features.CodeCompletion.FSharpCodeCompletionContext uses JetBrains.ReSharper.Plugins.FSharp.Psi.PsiUtil, so a change to JetBrains.ReSharper.Plugins.FSharp.Psi.PsiUtil can break JetBrains.ReSharper.Plugins.FSharp.Psi.Features.CodeCompletion.FSharpCodeCompletionContext, while a change to JetBrains.ReSharper.Plugins.FSharp.Psi.Features.CodeCompletion.FSharpCodeCompletionContext can't break JetBrains.ReSharper.Plugins.FSharp.Psi.PsiUtil.
- Position
- Below the diagonal: JetBrains.ReSharper.Plugins.FSharp.Psi.Features.CodeCompletion.FSharpCodeCompletionContext uses a module listed above it, which is the healthy direction.
15→1 JetBrains.ReSharper.Plugins.FSharp.Psi.Features.Daemon.Highlightings uses DocumentRangeExtensions✕
- Connections
- 3 pairs of types, where a type in JetBrains.ReSharper.Plugins.FSharp.Psi.Features.Daemon.Highlightings uses a type in DocumentRangeExtensions.
- The types involved
JetBrains.ReSharper.Plugins.FSharp.Psi.Features.Daemon.Highlightings.FSharpErrorHighlightingBase→DocumentRangeExtensions.DocumentRangeJetBrains.ReSharper.Plugins.FSharp.Psi.Features.Daemon.Highlightings.FcsDiagnosticHighlighting→DocumentRangeExtensions.DocumentRangeJetBrains.ReSharper.Plugins.FSharp.Psi.Features.Daemon.Highlightings.TypeHintHighlighting→DocumentRangeExtensions.DocumentRange
- Direction
- JetBrains.ReSharper.Plugins.FSharp.Psi.Features.Daemon.Highlightings uses DocumentRangeExtensions, so a change to DocumentRangeExtensions can break JetBrains.ReSharper.Plugins.FSharp.Psi.Features.Daemon.Highlightings, while a change to JetBrains.ReSharper.Plugins.FSharp.Psi.Features.Daemon.Highlightings can't break DocumentRangeExtensions.
- Position
- Below the diagonal: JetBrains.ReSharper.Plugins.FSharp.Psi.Features.Daemon.Highlightings uses a module listed above it, which is the healthy direction.
15→9 JetBrains.ReSharper.Plugins.FSharp.Psi.Features.Daemon.Highlightings uses JetBrains.ReSharper.Plugins.FSharp.Psi.PsiUtil✕
- Connections
- 1 pair of types, where a type in JetBrains.ReSharper.Plugins.FSharp.Psi.Features.Daemon.Highlightings uses a type in JetBrains.ReSharper.Plugins.FSharp.Psi.PsiUtil.
- The types involved
JetBrains.ReSharper.Plugins.FSharp.Psi.Features.Daemon.Highlightings.TypeHintHighlighting→JetBrains.ReSharper.Plugins.FSharp.Psi.PsiUtil.ITreeNode
- Direction
- JetBrains.ReSharper.Plugins.FSharp.Psi.Features.Daemon.Highlightings uses JetBrains.ReSharper.Plugins.FSharp.Psi.PsiUtil, so a change to JetBrains.ReSharper.Plugins.FSharp.Psi.PsiUtil can break JetBrains.ReSharper.Plugins.FSharp.Psi.Features.Daemon.Highlightings, while a change to JetBrains.ReSharper.Plugins.FSharp.Psi.Features.Daemon.Highlightings can't break JetBrains.ReSharper.Plugins.FSharp.Psi.PsiUtil.
- Position
- Below the diagonal: JetBrains.ReSharper.Plugins.FSharp.Psi.Features.Daemon.Highlightings uses a module listed above it, which is the healthy direction.
16→9 JetBrains.ReSharper.Plugins.FSharp.Psi.Features.Util.FcsTypeUtil uses JetBrains.ReSharper.Plugins.FSharp.Psi.PsiUtil✕
- Connections
- 2 pairs of types, where a type in JetBrains.ReSharper.Plugins.FSharp.Psi.Features.Util.FcsTypeUtil uses a type in JetBrains.ReSharper.Plugins.FSharp.Psi.PsiUtil.
- The types involved
JetBrains.ReSharper.Plugins.FSharp.Psi.Features.Util.FcsTypeUtil.FSharpType→JetBrains.ReSharper.Plugins.FSharp.Psi.PsiUtil.ITreeNodeJetBrains.ReSharper.Plugins.FSharp.Psi.Features.Util.FcsTypeUtil.FcsTypeUtil→JetBrains.ReSharper.Plugins.FSharp.Psi.PsiUtil.ITreeNode
- Direction
- JetBrains.ReSharper.Plugins.FSharp.Psi.Features.Util.FcsTypeUtil uses JetBrains.ReSharper.Plugins.FSharp.Psi.PsiUtil, so a change to JetBrains.ReSharper.Plugins.FSharp.Psi.PsiUtil can break JetBrains.ReSharper.Plugins.FSharp.Psi.Features.Util.FcsTypeUtil, while a change to JetBrains.ReSharper.Plugins.FSharp.Psi.Features.Util.FcsTypeUtil can't break JetBrains.ReSharper.Plugins.FSharp.Psi.PsiUtil.
- Position
- Below the diagonal: JetBrains.ReSharper.Plugins.FSharp.Psi.Features.Util.FcsTypeUtil uses a module listed above it, which is the healthy direction.
17→2 JetBrains.ReSharper.Plugins.FSharp.Psi.LanguageService.Parsing uses FSharpFileSystemPathExtensions✕
- Connections
- 2 pairs of types, where a type in JetBrains.ReSharper.Plugins.FSharp.Psi.LanguageService.Parsing uses a type in FSharpFileSystemPathExtensions.
- The types involved
JetBrains.ReSharper.Plugins.FSharp.Psi.LanguageService.Parsing.FSharpParser→FSharpFileSystemPathExtensions.VirtualFileSystemPathJetBrains.ReSharper.Plugins.FSharp.Psi.LanguageService.Parsing.FSharpTreeBuilderBase→FSharpFileSystemPathExtensions.VirtualFileSystemPath
- Direction
- JetBrains.ReSharper.Plugins.FSharp.Psi.LanguageService.Parsing uses FSharpFileSystemPathExtensions, so a change to FSharpFileSystemPathExtensions can break JetBrains.ReSharper.Plugins.FSharp.Psi.LanguageService.Parsing, while a change to JetBrains.ReSharper.Plugins.FSharp.Psi.LanguageService.Parsing can't break FSharpFileSystemPathExtensions.
- Position
- Below the diagonal: JetBrains.ReSharper.Plugins.FSharp.Psi.LanguageService.Parsing uses a module listed above it, which is the healthy direction.
17→3 JetBrains.ReSharper.Plugins.FSharp.Psi.LanguageService.Parsing uses JetBrains.ReSharper.Plugins.FSharp.Checker.FcsCheckerService✕
- Connections
- 1 pair of types, where a type in JetBrains.ReSharper.Plugins.FSharp.Psi.LanguageService.Parsing uses a type in JetBrains.ReSharper.Plugins.FSharp.Checker.FcsCheckerService.
- The types involved
JetBrains.ReSharper.Plugins.FSharp.Psi.LanguageService.Parsing.FSharpParser→JetBrains.ReSharper.Plugins.FSharp.Checker.FcsCheckerService.FcsCheckerService
- Direction
- JetBrains.ReSharper.Plugins.FSharp.Psi.LanguageService.Parsing uses JetBrains.ReSharper.Plugins.FSharp.Checker.FcsCheckerService, so a change to JetBrains.ReSharper.Plugins.FSharp.Checker.FcsCheckerService can break JetBrains.ReSharper.Plugins.FSharp.Psi.LanguageService.Parsing, while a change to JetBrains.ReSharper.Plugins.FSharp.Psi.LanguageService.Parsing can't break JetBrains.ReSharper.Plugins.FSharp.Checker.FcsCheckerService.
- Position
- Below the diagonal: JetBrains.ReSharper.Plugins.FSharp.Psi.LanguageService.Parsing uses a module listed above it, which is the healthy direction.
17→9 JetBrains.ReSharper.Plugins.FSharp.Psi.LanguageService.Parsing uses JetBrains.ReSharper.Plugins.FSharp.Psi.PsiUtil✕
- Connections
- 1 pair of types, where a type in JetBrains.ReSharper.Plugins.FSharp.Psi.LanguageService.Parsing uses a type in JetBrains.ReSharper.Plugins.FSharp.Psi.PsiUtil.
- The types involved
JetBrains.ReSharper.Plugins.FSharp.Psi.LanguageService.Parsing.FSharpParser→JetBrains.ReSharper.Plugins.FSharp.Psi.PsiUtil.IPsiSourceFile
- Direction
- JetBrains.ReSharper.Plugins.FSharp.Psi.LanguageService.Parsing uses JetBrains.ReSharper.Plugins.FSharp.Psi.PsiUtil, so a change to JetBrains.ReSharper.Plugins.FSharp.Psi.PsiUtil can break JetBrains.ReSharper.Plugins.FSharp.Psi.LanguageService.Parsing, while a change to JetBrains.ReSharper.Plugins.FSharp.Psi.LanguageService.Parsing can't break JetBrains.ReSharper.Plugins.FSharp.Psi.PsiUtil.
- Position
- Below the diagonal: JetBrains.ReSharper.Plugins.FSharp.Psi.LanguageService.Parsing uses a module listed above it, which is the healthy direction.
17→10 JetBrains.ReSharper.Plugins.FSharp.Psi.LanguageService.Parsing uses JetBrains.ReSharper.Plugins.FSharp.Util.CommonUtil✕
- Connections
- 1 pair of types, where a type in JetBrains.ReSharper.Plugins.FSharp.Psi.LanguageService.Parsing uses a type in JetBrains.ReSharper.Plugins.FSharp.Util.CommonUtil.
- The types involved
JetBrains.ReSharper.Plugins.FSharp.Psi.LanguageService.Parsing.FSharpTreeBuilderBase→JetBrains.ReSharper.Plugins.FSharp.Util.CommonUtil.Lifetime
- Direction
- JetBrains.ReSharper.Plugins.FSharp.Psi.LanguageService.Parsing uses JetBrains.ReSharper.Plugins.FSharp.Util.CommonUtil, so a change to JetBrains.ReSharper.Plugins.FSharp.Util.CommonUtil can break JetBrains.ReSharper.Plugins.FSharp.Psi.LanguageService.Parsing, while a change to JetBrains.ReSharper.Plugins.FSharp.Psi.LanguageService.Parsing can't break JetBrains.ReSharper.Plugins.FSharp.Util.CommonUtil.
- Position
- Below the diagonal: JetBrains.ReSharper.Plugins.FSharp.Psi.LanguageService.Parsing uses a module listed above it, which is the healthy direction.
18→1 JetBrains.ReSharper.Plugins.FSharp.Psi.Util.OpensUtil uses DocumentRangeExtensions✕
- Connections
- 1 pair of types, where a type in JetBrains.ReSharper.Plugins.FSharp.Psi.Util.OpensUtil uses a type in DocumentRangeExtensions.
- The types involved
JetBrains.ReSharper.Plugins.FSharp.Psi.Util.OpensUtil.OpenScope→DocumentRangeExtensions.TreeTextRange
- Direction
- JetBrains.ReSharper.Plugins.FSharp.Psi.Util.OpensUtil uses DocumentRangeExtensions, so a change to DocumentRangeExtensions can break JetBrains.ReSharper.Plugins.FSharp.Psi.Util.OpensUtil, while a change to JetBrains.ReSharper.Plugins.FSharp.Psi.Util.OpensUtil can't break DocumentRangeExtensions.
- Position
- Below the diagonal: JetBrains.ReSharper.Plugins.FSharp.Psi.Util.OpensUtil uses a module listed above it, which is the healthy direction.
18→6 JetBrains.ReSharper.Plugins.FSharp.Psi.Util.OpensUtil uses JetBrains.ReSharper.Plugins.FSharp.Util.SettingsStoreUtil✕
- Connections
- 1 pair of types, where a type in JetBrains.ReSharper.Plugins.FSharp.Psi.Util.OpensUtil uses a type in JetBrains.ReSharper.Plugins.FSharp.Util.SettingsStoreUtil.
- The types involved
JetBrains.ReSharper.Plugins.FSharp.Psi.Util.OpensUtil.OpensUtil→JetBrains.ReSharper.Plugins.FSharp.Util.SettingsStoreUtil.IContextBoundSettingsStore
- Direction
- JetBrains.ReSharper.Plugins.FSharp.Psi.Util.OpensUtil uses JetBrains.ReSharper.Plugins.FSharp.Util.SettingsStoreUtil, so a change to JetBrains.ReSharper.Plugins.FSharp.Util.SettingsStoreUtil can break JetBrains.ReSharper.Plugins.FSharp.Psi.Util.OpensUtil, while a change to JetBrains.ReSharper.Plugins.FSharp.Psi.Util.OpensUtil can't break JetBrains.ReSharper.Plugins.FSharp.Util.SettingsStoreUtil.
- Position
- Below the diagonal: JetBrains.ReSharper.Plugins.FSharp.Psi.Util.OpensUtil uses a module listed above it, which is the healthy direction.
18→9 JetBrains.ReSharper.Plugins.FSharp.Psi.Util.OpensUtil uses JetBrains.ReSharper.Plugins.FSharp.Psi.PsiUtil✕
- Connections
- 2 pairs of types, where a type in JetBrains.ReSharper.Plugins.FSharp.Psi.Util.OpensUtil uses a type in JetBrains.ReSharper.Plugins.FSharp.Psi.PsiUtil.
- The types involved
JetBrains.ReSharper.Plugins.FSharp.Psi.Util.OpensUtil.OpenedModulesProvider→JetBrains.ReSharper.Plugins.FSharp.Psi.PsiUtil.ITreeNodeJetBrains.ReSharper.Plugins.FSharp.Psi.Util.OpensUtil.OpensUtil→JetBrains.ReSharper.Plugins.FSharp.Psi.PsiUtil.ITreeNode
- Direction
- JetBrains.ReSharper.Plugins.FSharp.Psi.Util.OpensUtil uses JetBrains.ReSharper.Plugins.FSharp.Psi.PsiUtil, so a change to JetBrains.ReSharper.Plugins.FSharp.Psi.PsiUtil can break JetBrains.ReSharper.Plugins.FSharp.Psi.Util.OpensUtil, while a change to JetBrains.ReSharper.Plugins.FSharp.Psi.Util.OpensUtil can't break JetBrains.ReSharper.Plugins.FSharp.Psi.PsiUtil.
- Position
- Below the diagonal: JetBrains.ReSharper.Plugins.FSharp.Psi.Util.OpensUtil uses a module listed above it, which is the healthy direction.
19→7 com.jetbrains.rider.ideaInterop.fileTypes.fsharp.psi.impl uses com.jetbrains.rider.ideaInterop.fileTypes.fsharp.lexer✕
- Connections
- 1 pair of types, where a type in com.jetbrains.rider.ideaInterop.fileTypes.fsharp.psi.impl uses a type in com.jetbrains.rider.ideaInterop.fileTypes.fsharp.lexer.
- The types involved
com.jetbrains.rider.ideaInterop.fileTypes.fsharp.psi.impl.FSharpInterpolatedStringLiteralExpressionPartImpl→com.jetbrains.rider.ideaInterop.fileTypes.fsharp.lexer.FSharpTokenNodeType
- Direction
- com.jetbrains.rider.ideaInterop.fileTypes.fsharp.psi.impl uses com.jetbrains.rider.ideaInterop.fileTypes.fsharp.lexer, so a change to com.jetbrains.rider.ideaInterop.fileTypes.fsharp.lexer can break com.jetbrains.rider.ideaInterop.fileTypes.fsharp.psi.impl, while a change to com.jetbrains.rider.ideaInterop.fileTypes.fsharp.psi.impl can't break com.jetbrains.rider.ideaInterop.fileTypes.fsharp.lexer.
- Position
- Below the diagonal: com.jetbrains.rider.ideaInterop.fileTypes.fsharp.psi.impl uses a module listed above it, which is the healthy direction.
19→12 com.jetbrains.rider.ideaInterop.fileTypes.fsharp.psi.impl uses com.jetbrains.rider.ideaInterop.fileTypes.fsharp.psi✕
- Connections
- 18 pairs of types, where a type in com.jetbrains.rider.ideaInterop.fileTypes.fsharp.psi.impl uses a type in com.jetbrains.rider.ideaInterop.fileTypes.fsharp.psi.
- The types involved
com.jetbrains.rider.ideaInterop.fileTypes.fsharp.psi.impl.FSharpElementTypes→com.jetbrains.rider.ideaInterop.fileTypes.fsharp.psi.FSharpCompositeElementTypecom.jetbrains.rider.ideaInterop.fileTypes.fsharp.psi.impl.FSharpElementTypes→com.jetbrains.rider.ideaInterop.fileTypes.fsharp.psi.FSharpFileElementTypecom.jetbrains.rider.ideaInterop.fileTypes.fsharp.psi.impl.FSharpExpressionImpl→com.jetbrains.rider.ideaInterop.fileTypes.fsharp.psi.FSharpElementTypecom.jetbrains.rider.ideaInterop.fileTypes.fsharp.psi.impl.FSharpExpressionImpl→com.jetbrains.rider.ideaInterop.fileTypes.fsharp.psi.FSharpExpressioncom.jetbrains.rider.ideaInterop.fileTypes.fsharp.psi.impl.FSharpFileImpl→com.jetbrains.rider.ideaInterop.fileTypes.fsharp.psi.FSharpFilecom.jetbrains.rider.ideaInterop.fileTypes.fsharp.psi.impl.FSharpInterpolatedStringLiteralExpressionImpl→com.jetbrains.rider.ideaInterop.fileTypes.fsharp.psi.FSharpElementTypecom.jetbrains.rider.ideaInterop.fileTypes.fsharp.psi.impl.FSharpInterpolatedStringLiteralExpressionImpl→com.jetbrains.rider.ideaInterop.fileTypes.fsharp.psi.FSharpInterpolatedStringLiteralExpressioncom.jetbrains.rider.ideaInterop.fileTypes.fsharp.psi.impl.FSharpInterpolatedStringLiteralExpressionImpl→com.jetbrains.rider.ideaInterop.fileTypes.fsharp.psi.FSharpStringLiteralTypecom.jetbrains.rider.ideaInterop.fileTypes.fsharp.psi.impl.FSharpInterpolatedStringLiteralExpressionPartImpl→com.jetbrains.rider.ideaInterop.fileTypes.fsharp.psi.FSharpElementTypecom.jetbrains.rider.ideaInterop.fileTypes.fsharp.psi.impl.FSharpInterpolatedStringLiteralExpressionPartImpl→com.jetbrains.rider.ideaInterop.fileTypes.fsharp.psi.FSharpInterpolatedStringLiteralExpressionPartcom.jetbrains.rider.ideaInterop.fileTypes.fsharp.psi.impl.FSharpPsiElementBase→com.jetbrains.rider.ideaInterop.fileTypes.fsharp.psi.FSharpElementcom.jetbrains.rider.ideaInterop.fileTypes.fsharp.psi.impl.FSharpPsiElementBase→com.jetbrains.rider.ideaInterop.fileTypes.fsharp.psi.FSharpElementTypecom.jetbrains.rider.ideaInterop.fileTypes.fsharp.psi.impl.FSharpScriptFileImpl→com.jetbrains.rider.ideaInterop.fileTypes.fsharp.psi.FSharpFilecom.jetbrains.rider.ideaInterop.fileTypes.fsharp.psi.impl.FSharpSignatureFileImpl→com.jetbrains.rider.ideaInterop.fileTypes.fsharp.psi.FSharpFilecom.jetbrains.rider.ideaInterop.fileTypes.fsharp.psi.impl.FSharpStringLiteralExpressionBase→com.jetbrains.rider.ideaInterop.fileTypes.fsharp.psi.FSharpElementTypecom.jetbrains.rider.ideaInterop.fileTypes.fsharp.psi.impl.FSharpStringLiteralExpressionBase→com.jetbrains.rider.ideaInterop.fileTypes.fsharp.psi.FSharpStringLiteralExpressioncom.jetbrains.rider.ideaInterop.fileTypes.fsharp.psi.impl.FSharpStringLiteralExpressionImpl→com.jetbrains.rider.ideaInterop.fileTypes.fsharp.psi.FSharpElementTypecom.jetbrains.rider.ideaInterop.fileTypes.fsharp.psi.impl.FSharpStringLiteralExpressionImpl→com.jetbrains.rider.ideaInterop.fileTypes.fsharp.psi.FSharpStringLiteralType
- Direction
- com.jetbrains.rider.ideaInterop.fileTypes.fsharp.psi.impl uses com.jetbrains.rider.ideaInterop.fileTypes.fsharp.psi, so a change to com.jetbrains.rider.ideaInterop.fileTypes.fsharp.psi can break com.jetbrains.rider.ideaInterop.fileTypes.fsharp.psi.impl, while a change to com.jetbrains.rider.ideaInterop.fileTypes.fsharp.psi.impl can't break com.jetbrains.rider.ideaInterop.fileTypes.fsharp.psi.
- Position
- Below the diagonal: com.jetbrains.rider.ideaInterop.fileTypes.fsharp.psi.impl uses a module listed above it, which is the healthy direction.
20→11 com.jetbrains.rider.plugins.fsharp.services.fsi uses com.jetbrains.rider.ideaInterop.fileTypes.fsharp.highlighting✕
- Connections
- 2 pairs of types, where a type in com.jetbrains.rider.plugins.fsharp.services.fsi uses a type in com.jetbrains.rider.ideaInterop.fileTypes.fsharp.highlighting.
- The types involved
com.jetbrains.rider.plugins.fsharp.services.fsi.FsiInputOutputProcessor→com.jetbrains.rider.ideaInterop.fileTypes.fsharp.highlighting.FSharpSyntaxHighlightercom.jetbrains.rider.plugins.fsharp.services.fsi.FsiInputOutputProcessor→com.jetbrains.rider.ideaInterop.fileTypes.fsharp.highlighting.FsiOutputSyntaxHighlighter
- Direction
- com.jetbrains.rider.plugins.fsharp.services.fsi uses com.jetbrains.rider.ideaInterop.fileTypes.fsharp.highlighting, so a change to com.jetbrains.rider.ideaInterop.fileTypes.fsharp.highlighting can break com.jetbrains.rider.plugins.fsharp.services.fsi, while a change to com.jetbrains.rider.plugins.fsharp.services.fsi can't break com.jetbrains.rider.ideaInterop.fileTypes.fsharp.highlighting.
- Position
- Below the diagonal: com.jetbrains.rider.plugins.fsharp.services.fsi uses a module listed above it, which is the healthy direction.
21→1 JetBrains.ReSharper.Plugins.FSharp.Psi.Daemon.Stages uses DocumentRangeExtensions✕
- Connections
- 1 pair of types, where a type in JetBrains.ReSharper.Plugins.FSharp.Psi.Daemon.Stages uses a type in DocumentRangeExtensions.
- The types involved
JetBrains.ReSharper.Plugins.FSharp.Psi.Daemon.Stages.FcsErrorsStageProcessBase→DocumentRangeExtensions.DocumentRange
- Direction
- JetBrains.ReSharper.Plugins.FSharp.Psi.Daemon.Stages uses DocumentRangeExtensions, so a change to DocumentRangeExtensions can break JetBrains.ReSharper.Plugins.FSharp.Psi.Daemon.Stages, while a change to JetBrains.ReSharper.Plugins.FSharp.Psi.Daemon.Stages can't break DocumentRangeExtensions.
- Position
- Below the diagonal: JetBrains.ReSharper.Plugins.FSharp.Psi.Daemon.Stages uses a module listed above it, which is the healthy direction.
21→6 JetBrains.ReSharper.Plugins.FSharp.Psi.Daemon.Stages uses JetBrains.ReSharper.Plugins.FSharp.Util.SettingsStoreUtil✕
- Connections
- 3 pairs of types, where a type in JetBrains.ReSharper.Plugins.FSharp.Psi.Daemon.Stages uses a type in JetBrains.ReSharper.Plugins.FSharp.Util.SettingsStoreUtil.
- The types involved
JetBrains.ReSharper.Plugins.FSharp.Psi.Daemon.Stages.FSharpTypeHintSettings→JetBrains.ReSharper.Plugins.FSharp.Util.SettingsStoreUtil.IContextBoundSettingsStoreJetBrains.ReSharper.Plugins.FSharp.Psi.Daemon.Stages.PatternsHighlightingProcess→JetBrains.ReSharper.Plugins.FSharp.Util.SettingsStoreUtil.IContextBoundSettingsStoreJetBrains.ReSharper.Plugins.FSharp.Psi.Daemon.Stages.PipeChainHighlightingProcess→JetBrains.ReSharper.Plugins.FSharp.Util.SettingsStoreUtil.IContextBoundSettingsStore
- Direction
- JetBrains.ReSharper.Plugins.FSharp.Psi.Daemon.Stages uses JetBrains.ReSharper.Plugins.FSharp.Util.SettingsStoreUtil, so a change to JetBrains.ReSharper.Plugins.FSharp.Util.SettingsStoreUtil can break JetBrains.ReSharper.Plugins.FSharp.Psi.Daemon.Stages, while a change to JetBrains.ReSharper.Plugins.FSharp.Psi.Daemon.Stages can't break JetBrains.ReSharper.Plugins.FSharp.Util.SettingsStoreUtil.
- Position
- Below the diagonal: JetBrains.ReSharper.Plugins.FSharp.Psi.Daemon.Stages uses a module listed above it, which is the healthy direction.
21→9 JetBrains.ReSharper.Plugins.FSharp.Psi.Daemon.Stages uses JetBrains.ReSharper.Plugins.FSharp.Psi.PsiUtil✕
- Connections
- 6 pairs of types, where a type in JetBrains.ReSharper.Plugins.FSharp.Psi.Daemon.Stages uses a type in JetBrains.ReSharper.Plugins.FSharp.Psi.PsiUtil.
- The types involved
JetBrains.ReSharper.Plugins.FSharp.Psi.Daemon.Stages.FSharpCompilerWarningProcessor→JetBrains.ReSharper.Plugins.FSharp.Psi.PsiUtil.IFileJetBrains.ReSharper.Plugins.FSharp.Psi.Daemon.Stages.GlobalProcessor→JetBrains.ReSharper.Plugins.FSharp.Psi.PsiUtil.ITreeNodeJetBrains.ReSharper.Plugins.FSharp.Psi.Daemon.Stages.MembersVisitor→JetBrains.ReSharper.Plugins.FSharp.Psi.PsiUtil.ITreeNodeJetBrains.ReSharper.Plugins.FSharp.Psi.Daemon.Stages.PatternsHighlightingProcess→JetBrains.ReSharper.Plugins.FSharp.Psi.PsiUtil.ITreeNodeJetBrains.ReSharper.Plugins.FSharp.Psi.Daemon.Stages.PipeChainHighlightingProcess→JetBrains.ReSharper.Plugins.FSharp.Psi.PsiUtil.ITreeNodeJetBrains.ReSharper.Plugins.FSharp.Psi.Daemon.Stages.Processor→JetBrains.ReSharper.Plugins.FSharp.Psi.PsiUtil.ITreeNode
- Direction
- JetBrains.ReSharper.Plugins.FSharp.Psi.Daemon.Stages uses JetBrains.ReSharper.Plugins.FSharp.Psi.PsiUtil, so a change to JetBrains.ReSharper.Plugins.FSharp.Psi.PsiUtil can break JetBrains.ReSharper.Plugins.FSharp.Psi.Daemon.Stages, while a change to JetBrains.ReSharper.Plugins.FSharp.Psi.Daemon.Stages can't break JetBrains.ReSharper.Plugins.FSharp.Psi.PsiUtil.
- Position
- Below the diagonal: JetBrains.ReSharper.Plugins.FSharp.Psi.Daemon.Stages uses a module listed above it, which is the healthy direction.
21→16 JetBrains.ReSharper.Plugins.FSharp.Psi.Daemon.Stages uses JetBrains.ReSharper.Plugins.FSharp.Psi.Features.Util.FcsTypeUtil✕
- Connections
- 1 pair of types, where a type in JetBrains.ReSharper.Plugins.FSharp.Psi.Daemon.Stages uses a type in JetBrains.ReSharper.Plugins.FSharp.Psi.Features.Util.FcsTypeUtil.
- The types involved
JetBrains.ReSharper.Plugins.FSharp.Psi.Daemon.Stages.PipeChainHighlightingProcess→JetBrains.ReSharper.Plugins.FSharp.Psi.Features.Util.FcsTypeUtil.FSharpType
- Direction
- JetBrains.ReSharper.Plugins.FSharp.Psi.Daemon.Stages uses JetBrains.ReSharper.Plugins.FSharp.Psi.Features.Util.FcsTypeUtil, so a change to JetBrains.ReSharper.Plugins.FSharp.Psi.Features.Util.FcsTypeUtil can break JetBrains.ReSharper.Plugins.FSharp.Psi.Daemon.Stages, while a change to JetBrains.ReSharper.Plugins.FSharp.Psi.Daemon.Stages can't break JetBrains.ReSharper.Plugins.FSharp.Psi.Features.Util.FcsTypeUtil.
- Position
- Below the diagonal: JetBrains.ReSharper.Plugins.FSharp.Psi.Daemon.Stages uses a module listed above it, which is the healthy direction.
22→9 JetBrains.ReSharper.Plugins.FSharp.Psi.Features.CodeCompletion.Rules.OverrideMemberRule uses JetBrains.ReSharper.Plugins.FSharp.Psi.PsiUtil✕
- Connections
- 1 pair of types, where a type in JetBrains.ReSharper.Plugins.FSharp.Psi.Features.CodeCompletion.Rules.OverrideMemberRule uses a type in JetBrains.ReSharper.Plugins.FSharp.Psi.PsiUtil.
- The types involved
JetBrains.ReSharper.Plugins.FSharp.Psi.Features.CodeCompletion.Rules.OverrideMemberRule.OverrideMemberRule→JetBrains.ReSharper.Plugins.FSharp.Psi.PsiUtil.ITreeNode
- Direction
- JetBrains.ReSharper.Plugins.FSharp.Psi.Features.CodeCompletion.Rules.OverrideMemberRule uses JetBrains.ReSharper.Plugins.FSharp.Psi.PsiUtil, so a change to JetBrains.ReSharper.Plugins.FSharp.Psi.PsiUtil can break JetBrains.ReSharper.Plugins.FSharp.Psi.Features.CodeCompletion.Rules.OverrideMemberRule, while a change to JetBrains.ReSharper.Plugins.FSharp.Psi.Features.CodeCompletion.Rules.OverrideMemberRule can't break JetBrains.ReSharper.Plugins.FSharp.Psi.PsiUtil.
- Position
- Below the diagonal: JetBrains.ReSharper.Plugins.FSharp.Psi.Features.CodeCompletion.Rules.OverrideMemberRule uses a module listed above it, which is the healthy direction.
22→14 JetBrains.ReSharper.Plugins.FSharp.Psi.Features.CodeCompletion.Rules.OverrideMemberRule uses JetBrains.ReSharper.Plugins.FSharp.Psi.Features.CodeCompletion.FSharpCodeCompletionContext✕
- Connections
- 1 pair of types, where a type in JetBrains.ReSharper.Plugins.FSharp.Psi.Features.CodeCompletion.Rules.OverrideMemberRule uses a type in JetBrains.ReSharper.Plugins.FSharp.Psi.Features.CodeCompletion.FSharpCodeCompletionContext.
- The types involved
JetBrains.ReSharper.Plugins.FSharp.Psi.Features.CodeCompletion.Rules.OverrideMemberRule.OverrideMemberRule→JetBrains.ReSharper.Plugins.FSharp.Psi.Features.CodeCompletion.FSharpCodeCompletionContext.FSharpCodeCompletionContext
- Direction
- JetBrains.ReSharper.Plugins.FSharp.Psi.Features.CodeCompletion.Rules.OverrideMemberRule uses JetBrains.ReSharper.Plugins.FSharp.Psi.Features.CodeCompletion.FSharpCodeCompletionContext, so a change to JetBrains.ReSharper.Plugins.FSharp.Psi.Features.CodeCompletion.FSharpCodeCompletionContext can break JetBrains.ReSharper.Plugins.FSharp.Psi.Features.CodeCompletion.Rules.OverrideMemberRule, while a change to JetBrains.ReSharper.Plugins.FSharp.Psi.Features.CodeCompletion.Rules.OverrideMemberRule can't break JetBrains.ReSharper.Plugins.FSharp.Psi.Features.CodeCompletion.FSharpCodeCompletionContext.
- Position
- Below the diagonal: JetBrains.ReSharper.Plugins.FSharp.Psi.Features.CodeCompletion.Rules.OverrideMemberRule uses a module listed above it, which is the healthy direction.
23→9 JetBrains.ReSharper.Plugins.FSharp.Psi.Features.Util.FSharpNamingService uses JetBrains.ReSharper.Plugins.FSharp.Psi.PsiUtil✕
- Connections
- 1 pair of types, where a type in JetBrains.ReSharper.Plugins.FSharp.Psi.Features.Util.FSharpNamingService uses a type in JetBrains.ReSharper.Plugins.FSharp.Psi.PsiUtil.
- The types involved
JetBrains.ReSharper.Plugins.FSharp.Psi.Features.Util.FSharpNamingService.FSharpNamingService→JetBrains.ReSharper.Plugins.FSharp.Psi.PsiUtil.ITreeNode
- Direction
- JetBrains.ReSharper.Plugins.FSharp.Psi.Features.Util.FSharpNamingService uses JetBrains.ReSharper.Plugins.FSharp.Psi.PsiUtil, so a change to JetBrains.ReSharper.Plugins.FSharp.Psi.PsiUtil can break JetBrains.ReSharper.Plugins.FSharp.Psi.Features.Util.FSharpNamingService, while a change to JetBrains.ReSharper.Plugins.FSharp.Psi.Features.Util.FSharpNamingService can't break JetBrains.ReSharper.Plugins.FSharp.Psi.PsiUtil.
- Position
- Below the diagonal: JetBrains.ReSharper.Plugins.FSharp.Psi.Features.Util.FSharpNamingService uses a module listed above it, which is the healthy direction.
23→10 JetBrains.ReSharper.Plugins.FSharp.Psi.Features.Util.FSharpNamingService uses JetBrains.ReSharper.Plugins.FSharp.Util.CommonUtil✕
- Connections
- 1 pair of types, where a type in JetBrains.ReSharper.Plugins.FSharp.Psi.Features.Util.FSharpNamingService uses a type in JetBrains.ReSharper.Plugins.FSharp.Util.CommonUtil.
- The types involved
JetBrains.ReSharper.Plugins.FSharp.Psi.Features.Util.FSharpNamingService.FSharpNamingService→JetBrains.ReSharper.Plugins.FSharp.Util.CommonUtil.ISet
- Direction
- JetBrains.ReSharper.Plugins.FSharp.Psi.Features.Util.FSharpNamingService uses JetBrains.ReSharper.Plugins.FSharp.Util.CommonUtil, so a change to JetBrains.ReSharper.Plugins.FSharp.Util.CommonUtil can break JetBrains.ReSharper.Plugins.FSharp.Psi.Features.Util.FSharpNamingService, while a change to JetBrains.ReSharper.Plugins.FSharp.Psi.Features.Util.FSharpNamingService can't break JetBrains.ReSharper.Plugins.FSharp.Util.CommonUtil.
- Position
- Below the diagonal: JetBrains.ReSharper.Plugins.FSharp.Psi.Features.Util.FSharpNamingService uses a module listed above it, which is the healthy direction.
23→16 JetBrains.ReSharper.Plugins.FSharp.Psi.Features.Util.FSharpNamingService uses JetBrains.ReSharper.Plugins.FSharp.Psi.Features.Util.FcsTypeUtil✕
- Connections
- 1 pair of types, where a type in JetBrains.ReSharper.Plugins.FSharp.Psi.Features.Util.FSharpNamingService uses a type in JetBrains.ReSharper.Plugins.FSharp.Psi.Features.Util.FcsTypeUtil.
- The types involved
JetBrains.ReSharper.Plugins.FSharp.Psi.Features.Util.FSharpNamingService.FSharpNamingService→JetBrains.ReSharper.Plugins.FSharp.Psi.Features.Util.FcsTypeUtil.FSharpType
- Direction
- JetBrains.ReSharper.Plugins.FSharp.Psi.Features.Util.FSharpNamingService uses JetBrains.ReSharper.Plugins.FSharp.Psi.Features.Util.FcsTypeUtil, so a change to JetBrains.ReSharper.Plugins.FSharp.Psi.Features.Util.FcsTypeUtil can break JetBrains.ReSharper.Plugins.FSharp.Psi.Features.Util.FSharpNamingService, while a change to JetBrains.ReSharper.Plugins.FSharp.Psi.Features.Util.FSharpNamingService can't break JetBrains.ReSharper.Plugins.FSharp.Psi.Features.Util.FcsTypeUtil.
- Position
- Below the diagonal: JetBrains.ReSharper.Plugins.FSharp.Psi.Features.Util.FSharpNamingService uses a module listed above it, which is the healthy direction.
24→14 JetBrains.ReSharper.Plugins.FSharp.Psi.Services.Util.FSharpCompletionUtil uses JetBrains.ReSharper.Plugins.FSharp.Psi.Features.CodeCompletion.FSharpCodeCompletionContext✕
- Connections
- 1 pair of types, where a type in JetBrains.ReSharper.Plugins.FSharp.Psi.Services.Util.FSharpCompletionUtil uses a type in JetBrains.ReSharper.Plugins.FSharp.Psi.Features.CodeCompletion.FSharpCodeCompletionContext.
- The types involved
JetBrains.ReSharper.Plugins.FSharp.Psi.Services.Util.FSharpCompletionUtil.FSharpCompletionUtil→JetBrains.ReSharper.Plugins.FSharp.Psi.Features.CodeCompletion.FSharpCodeCompletionContext.FSharpCodeCompletionContext
- Direction
- JetBrains.ReSharper.Plugins.FSharp.Psi.Services.Util.FSharpCompletionUtil uses JetBrains.ReSharper.Plugins.FSharp.Psi.Features.CodeCompletion.FSharpCodeCompletionContext, so a change to JetBrains.ReSharper.Plugins.FSharp.Psi.Features.CodeCompletion.FSharpCodeCompletionContext can break JetBrains.ReSharper.Plugins.FSharp.Psi.Services.Util.FSharpCompletionUtil, while a change to JetBrains.ReSharper.Plugins.FSharp.Psi.Services.Util.FSharpCompletionUtil can't break JetBrains.ReSharper.Plugins.FSharp.Psi.Features.CodeCompletion.FSharpCodeCompletionContext.
- Position
- Below the diagonal: JetBrains.ReSharper.Plugins.FSharp.Psi.Services.Util.FSharpCompletionUtil uses a module listed above it, which is the healthy direction.
25→16 JetBrains.ReSharper.Plugins.FSharp.Util.FSharpSymbolUtil uses JetBrains.ReSharper.Plugins.FSharp.Psi.Features.Util.FcsTypeUtil✕
- Connections
- 1 pair of types, where a type in JetBrains.ReSharper.Plugins.FSharp.Util.FSharpSymbolUtil uses a type in JetBrains.ReSharper.Plugins.FSharp.Psi.Features.Util.FcsTypeUtil.
- The types involved
JetBrains.ReSharper.Plugins.FSharp.Util.FSharpSymbolUtil.FSharpSymbolUtil→JetBrains.ReSharper.Plugins.FSharp.Psi.Features.Util.FcsTypeUtil.FSharpType
- Direction
- JetBrains.ReSharper.Plugins.FSharp.Util.FSharpSymbolUtil uses JetBrains.ReSharper.Plugins.FSharp.Psi.Features.Util.FcsTypeUtil, so a change to JetBrains.ReSharper.Plugins.FSharp.Psi.Features.Util.FcsTypeUtil can break JetBrains.ReSharper.Plugins.FSharp.Util.FSharpSymbolUtil, while a change to JetBrains.ReSharper.Plugins.FSharp.Util.FSharpSymbolUtil can't break JetBrains.ReSharper.Plugins.FSharp.Psi.Features.Util.FcsTypeUtil.
- Position
- Below the diagonal: JetBrains.ReSharper.Plugins.FSharp.Util.FSharpSymbolUtil uses a module listed above it, which is the healthy direction.
26→2 JetBrains.ReSharper.Plugins.FSharp.ProjectModel.Host.ProjectItems.ItemsContainer uses FSharpFileSystemPathExtensions✕
- Connections
- 6 pairs of types, where a type in JetBrains.ReSharper.Plugins.FSharp.ProjectModel.Host.ProjectItems.ItemsContainer uses a type in FSharpFileSystemPathExtensions.
- The types involved
JetBrains.ReSharper.Plugins.FSharp.ProjectModel.Host.ProjectItems.ItemsContainer.FSharpProjectItem→FSharpFileSystemPathExtensions.VirtualFileSystemPathJetBrains.ReSharper.Plugins.FSharp.ProjectModel.Host.ProjectItems.ItemsContainer.FSharpProjectModelElement→FSharpFileSystemPathExtensions.VirtualFileSystemPathJetBrains.ReSharper.Plugins.FSharp.ProjectModel.Host.ProjectItems.ItemsContainer.ItemInfo→FSharpFileSystemPathExtensions.VirtualFileSystemPathJetBrains.ReSharper.Plugins.FSharp.ProjectModel.Host.ProjectItems.ItemsContainer.ItemsContainer→FSharpFileSystemPathExtensions.VirtualFileSystemPathJetBrains.ReSharper.Plugins.FSharp.ProjectModel.Host.ProjectItems.ItemsContainer.ProjectMapping→FSharpFileSystemPathExtensions.VirtualFileSystemPathJetBrains.ReSharper.Plugins.FSharp.ProjectModel.Host.ProjectItems.ItemsContainer.State→FSharpFileSystemPathExtensions.VirtualFileSystemPath
- Direction
- JetBrains.ReSharper.Plugins.FSharp.ProjectModel.Host.ProjectItems.ItemsContainer uses FSharpFileSystemPathExtensions, so a change to FSharpFileSystemPathExtensions can break JetBrains.ReSharper.Plugins.FSharp.ProjectModel.Host.ProjectItems.ItemsContainer, while a change to JetBrains.ReSharper.Plugins.FSharp.ProjectModel.Host.ProjectItems.ItemsContainer can't break FSharpFileSystemPathExtensions.
- Position
- Below the diagonal: JetBrains.ReSharper.Plugins.FSharp.ProjectModel.Host.ProjectItems.ItemsContainer uses a module listed above it, which is the healthy direction.
26→8 JetBrains.ReSharper.Plugins.FSharp.ProjectModel.Host.ProjectItems.ItemsContainer uses JetBrains.ReSharper.Plugins.FSharp.ProjectModel.Util✕
- Connections
- 1 pair of types, where a type in JetBrains.ReSharper.Plugins.FSharp.ProjectModel.Host.ProjectItems.ItemsContainer uses a type in JetBrains.ReSharper.Plugins.FSharp.ProjectModel.Util.
- The types involved
JetBrains.ReSharper.Plugins.FSharp.ProjectModel.Host.ProjectItems.ItemsContainer.IFSharpItemsContainer→JetBrains.ReSharper.Plugins.FSharp.ProjectModel.Util.IProject
- Direction
- JetBrains.ReSharper.Plugins.FSharp.ProjectModel.Host.ProjectItems.ItemsContainer uses JetBrains.ReSharper.Plugins.FSharp.ProjectModel.Util, so a change to JetBrains.ReSharper.Plugins.FSharp.ProjectModel.Util can break JetBrains.ReSharper.Plugins.FSharp.ProjectModel.Host.ProjectItems.ItemsContainer, while a change to JetBrains.ReSharper.Plugins.FSharp.ProjectModel.Host.ProjectItems.ItemsContainer can't break JetBrains.ReSharper.Plugins.FSharp.ProjectModel.Util.
- Position
- Below the diagonal: JetBrains.ReSharper.Plugins.FSharp.ProjectModel.Host.ProjectItems.ItemsContainer uses a module listed above it, which is the healthy direction.
26→10 JetBrains.ReSharper.Plugins.FSharp.ProjectModel.Host.ProjectItems.ItemsContainer uses JetBrains.ReSharper.Plugins.FSharp.Util.CommonUtil✕
- Connections
- 6 pairs of types, where a type in JetBrains.ReSharper.Plugins.FSharp.ProjectModel.Host.ProjectItems.ItemsContainer uses a type in JetBrains.ReSharper.Plugins.FSharp.Util.CommonUtil.
- The types involved
JetBrains.ReSharper.Plugins.FSharp.ProjectModel.Host.ProjectItems.ItemsContainer.FSharpItemsContainer→JetBrains.ReSharper.Plugins.FSharp.Util.CommonUtil.LifetimeJetBrains.ReSharper.Plugins.FSharp.ProjectModel.Host.ProjectItems.ItemsContainer.FSharpItemsContainerLoader→JetBrains.ReSharper.Plugins.FSharp.Util.CommonUtil.IDictionaryJetBrains.ReSharper.Plugins.FSharp.ProjectModel.Host.ProjectItems.ItemsContainer.FSharpItemsContainerLoader→JetBrains.ReSharper.Plugins.FSharp.Util.CommonUtil.LifetimeJetBrains.ReSharper.Plugins.FSharp.ProjectModel.Host.ProjectItems.ItemsContainer.FSharpItemsContainerRefresher→JetBrains.ReSharper.Plugins.FSharp.Util.CommonUtil.LifetimeJetBrains.ReSharper.Plugins.FSharp.ProjectModel.Host.ProjectItems.ItemsContainer.FSharpProjectItem→JetBrains.ReSharper.Plugins.FSharp.Util.CommonUtil.ISetJetBrains.ReSharper.Plugins.FSharp.ProjectModel.Host.ProjectItems.ItemsContainer.ProjectMapping→JetBrains.ReSharper.Plugins.FSharp.Util.CommonUtil.ISet
- Direction
- JetBrains.ReSharper.Plugins.FSharp.ProjectModel.Host.ProjectItems.ItemsContainer uses JetBrains.ReSharper.Plugins.FSharp.Util.CommonUtil, so a change to JetBrains.ReSharper.Plugins.FSharp.Util.CommonUtil can break JetBrains.ReSharper.Plugins.FSharp.ProjectModel.Host.ProjectItems.ItemsContainer, while a change to JetBrains.ReSharper.Plugins.FSharp.ProjectModel.Host.ProjectItems.ItemsContainer can't break JetBrains.ReSharper.Plugins.FSharp.Util.CommonUtil.
- Position
- Below the diagonal: JetBrains.ReSharper.Plugins.FSharp.ProjectModel.Host.ProjectItems.ItemsContainer uses a module listed above it, which is the healthy direction.
26→24 JetBrains.ReSharper.Plugins.FSharp.ProjectModel.Host.ProjectItems.ItemsContainer uses JetBrains.ReSharper.Plugins.FSharp.Psi.Services.Util.FSharpCompletionUtil✕
- Connections
- 2 pairs of types, where a type in JetBrains.ReSharper.Plugins.FSharp.ProjectModel.Host.ProjectItems.ItemsContainer uses a type in JetBrains.ReSharper.Plugins.FSharp.Psi.Services.Util.FSharpCompletionUtil.
- The types involved
JetBrains.ReSharper.Plugins.FSharp.ProjectModel.Host.ProjectItems.ItemsContainer.FSharpItemsContainerLoader→JetBrains.ReSharper.Plugins.FSharp.Psi.Services.Util.FSharpCompletionUtil.ISolutionJetBrains.ReSharper.Plugins.FSharp.ProjectModel.Host.ProjectItems.ItemsContainer.FSharpItemsContainerRefresher→JetBrains.ReSharper.Plugins.FSharp.Psi.Services.Util.FSharpCompletionUtil.ISolution
- Direction
- JetBrains.ReSharper.Plugins.FSharp.ProjectModel.Host.ProjectItems.ItemsContainer uses JetBrains.ReSharper.Plugins.FSharp.Psi.Services.Util.FSharpCompletionUtil, so a change to JetBrains.ReSharper.Plugins.FSharp.Psi.Services.Util.FSharpCompletionUtil can break JetBrains.ReSharper.Plugins.FSharp.ProjectModel.Host.ProjectItems.ItemsContainer, while a change to JetBrains.ReSharper.Plugins.FSharp.ProjectModel.Host.ProjectItems.ItemsContainer can't break JetBrains.ReSharper.Plugins.FSharp.Psi.Services.Util.FSharpCompletionUtil.
- Position
- Below the diagonal: JetBrains.ReSharper.Plugins.FSharp.ProjectModel.Host.ProjectItems.ItemsContainer uses a module listed above it, which is the healthy direction.
27→9 JetBrains.ReSharper.Plugins.FSharp.Psi.Features.Generate.GenerateOverrides uses JetBrains.ReSharper.Plugins.FSharp.Psi.PsiUtil✕
- Connections
- 1 pair of types, where a type in JetBrains.ReSharper.Plugins.FSharp.Psi.Features.Generate.GenerateOverrides uses a type in JetBrains.ReSharper.Plugins.FSharp.Psi.PsiUtil.
- The types involved
JetBrains.ReSharper.Plugins.FSharp.Psi.Features.Generate.GenerateOverrides.GenerateOverrides→JetBrains.ReSharper.Plugins.FSharp.Psi.PsiUtil.ITreeNode
- Direction
- JetBrains.ReSharper.Plugins.FSharp.Psi.Features.Generate.GenerateOverrides uses JetBrains.ReSharper.Plugins.FSharp.Psi.PsiUtil, so a change to JetBrains.ReSharper.Plugins.FSharp.Psi.PsiUtil can break JetBrains.ReSharper.Plugins.FSharp.Psi.Features.Generate.GenerateOverrides, while a change to JetBrains.ReSharper.Plugins.FSharp.Psi.Features.Generate.GenerateOverrides can't break JetBrains.ReSharper.Plugins.FSharp.Psi.PsiUtil.
- Position
- Below the diagonal: JetBrains.ReSharper.Plugins.FSharp.Psi.Features.Generate.GenerateOverrides uses a module listed above it, which is the healthy direction.
27→25 JetBrains.ReSharper.Plugins.FSharp.Psi.Features.Generate.GenerateOverrides uses JetBrains.ReSharper.Plugins.FSharp.Util.FSharpSymbolUtil✕
- Connections
- 1 pair of types, where a type in JetBrains.ReSharper.Plugins.FSharp.Psi.Features.Generate.GenerateOverrides uses a type in JetBrains.ReSharper.Plugins.FSharp.Util.FSharpSymbolUtil.
- The types involved
JetBrains.ReSharper.Plugins.FSharp.Psi.Features.Generate.GenerateOverrides.GenerateOverrides→JetBrains.ReSharper.Plugins.FSharp.Util.FSharpSymbolUtil.FcsMfvInstance
- Direction
- JetBrains.ReSharper.Plugins.FSharp.Psi.Features.Generate.GenerateOverrides uses JetBrains.ReSharper.Plugins.FSharp.Util.FSharpSymbolUtil, so a change to JetBrains.ReSharper.Plugins.FSharp.Util.FSharpSymbolUtil can break JetBrains.ReSharper.Plugins.FSharp.Psi.Features.Generate.GenerateOverrides, while a change to JetBrains.ReSharper.Plugins.FSharp.Psi.Features.Generate.GenerateOverrides can't break JetBrains.ReSharper.Plugins.FSharp.Util.FSharpSymbolUtil.
- Position
- Below the diagonal: JetBrains.ReSharper.Plugins.FSharp.Psi.Features.Generate.GenerateOverrides uses a module listed above it, which is the healthy direction.
28→1 JetBrains.ReSharper.Plugins.FSharp.Psi.Features.Intentions uses DocumentRangeExtensions✕
- Connections
- 1 pair of types, where a type in JetBrains.ReSharper.Plugins.FSharp.Psi.Features.Intentions uses a type in DocumentRangeExtensions.
- The types involved
JetBrains.ReSharper.Plugins.FSharp.Psi.Features.Intentions.DisableWarningActionBase→DocumentRangeExtensions.DocumentRange
- Direction
- JetBrains.ReSharper.Plugins.FSharp.Psi.Features.Intentions uses DocumentRangeExtensions, so a change to DocumentRangeExtensions can break JetBrains.ReSharper.Plugins.FSharp.Psi.Features.Intentions, while a change to JetBrains.ReSharper.Plugins.FSharp.Psi.Features.Intentions can't break DocumentRangeExtensions.
- Position
- Below the diagonal: JetBrains.ReSharper.Plugins.FSharp.Psi.Features.Intentions uses a module listed above it, which is the healthy direction.
28→9 JetBrains.ReSharper.Plugins.FSharp.Psi.Features.Intentions uses JetBrains.ReSharper.Plugins.FSharp.Psi.PsiUtil✕
- Connections
- 4 pairs of types, where a type in JetBrains.ReSharper.Plugins.FSharp.Psi.Features.Intentions uses a type in JetBrains.ReSharper.Plugins.FSharp.Psi.PsiUtil.
- The types involved
JetBrains.ReSharper.Plugins.FSharp.Psi.Features.Intentions.DisableWarningActionBase→JetBrains.ReSharper.Plugins.FSharp.Psi.PsiUtil.ITreeNodeJetBrains.ReSharper.Plugins.FSharp.Psi.Features.Intentions.FSharpContextActionBase→JetBrains.ReSharper.Plugins.FSharp.Psi.PsiUtil.ITreeNodeJetBrains.ReSharper.Plugins.FSharp.Psi.Features.Intentions.SpecifyTypeAction→JetBrains.ReSharper.Plugins.FSharp.Psi.PsiUtil.ITreeNodeJetBrains.ReSharper.Plugins.FSharp.Psi.Features.Intentions.SpecifyTypeActionsProvider→JetBrains.ReSharper.Plugins.FSharp.Psi.PsiUtil.ITreeNode
- Direction
- JetBrains.ReSharper.Plugins.FSharp.Psi.Features.Intentions uses JetBrains.ReSharper.Plugins.FSharp.Psi.PsiUtil, so a change to JetBrains.ReSharper.Plugins.FSharp.Psi.PsiUtil can break JetBrains.ReSharper.Plugins.FSharp.Psi.Features.Intentions, while a change to JetBrains.ReSharper.Plugins.FSharp.Psi.Features.Intentions can't break JetBrains.ReSharper.Plugins.FSharp.Psi.PsiUtil.
- Position
- Below the diagonal: JetBrains.ReSharper.Plugins.FSharp.Psi.Features.Intentions uses a module listed above it, which is the healthy direction.
28→24 JetBrains.ReSharper.Plugins.FSharp.Psi.Features.Intentions uses JetBrains.ReSharper.Plugins.FSharp.Psi.Services.Util.FSharpCompletionUtil✕
- Connections
- 2 pairs of types, where a type in JetBrains.ReSharper.Plugins.FSharp.Psi.Features.Intentions uses a type in JetBrains.ReSharper.Plugins.FSharp.Psi.Services.Util.FSharpCompletionUtil.
- The types involved
JetBrains.ReSharper.Plugins.FSharp.Psi.Features.Intentions.FSharpContextActionBase→JetBrains.ReSharper.Plugins.FSharp.Psi.Services.Util.FSharpCompletionUtil.ISolutionJetBrains.ReSharper.Plugins.FSharp.Psi.Features.Intentions.FSharpLegacyContextActionBase→JetBrains.ReSharper.Plugins.FSharp.Psi.Services.Util.FSharpCompletionUtil.ISolution
- Direction
- JetBrains.ReSharper.Plugins.FSharp.Psi.Features.Intentions uses JetBrains.ReSharper.Plugins.FSharp.Psi.Services.Util.FSharpCompletionUtil, so a change to JetBrains.ReSharper.Plugins.FSharp.Psi.Services.Util.FSharpCompletionUtil can break JetBrains.ReSharper.Plugins.FSharp.Psi.Features.Intentions, while a change to JetBrains.ReSharper.Plugins.FSharp.Psi.Features.Intentions can't break JetBrains.ReSharper.Plugins.FSharp.Psi.Services.Util.FSharpCompletionUtil.
- Position
- Below the diagonal: JetBrains.ReSharper.Plugins.FSharp.Psi.Features.Intentions uses a module listed above it, which is the healthy direction.
29→1 JetBrains.ReSharper.Plugins.FSharp.Psi.Features.ParameterInfo uses DocumentRangeExtensions✕
- Connections
- 1 pair of types, where a type in JetBrains.ReSharper.Plugins.FSharp.Psi.Features.ParameterInfo uses a type in DocumentRangeExtensions.
- The types involved
JetBrains.ReSharper.Plugins.FSharp.Psi.Features.ParameterInfo.FSharpParameterInfoContextFactory→DocumentRangeExtensions.DocumentRange
- Direction
- JetBrains.ReSharper.Plugins.FSharp.Psi.Features.ParameterInfo uses DocumentRangeExtensions, so a change to DocumentRangeExtensions can break JetBrains.ReSharper.Plugins.FSharp.Psi.Features.ParameterInfo, while a change to JetBrains.ReSharper.Plugins.FSharp.Psi.Features.ParameterInfo can't break DocumentRangeExtensions.
- Position
- Below the diagonal: JetBrains.ReSharper.Plugins.FSharp.Psi.Features.ParameterInfo uses a module listed above it, which is the healthy direction.
29→16 JetBrains.ReSharper.Plugins.FSharp.Psi.Features.ParameterInfo uses JetBrains.ReSharper.Plugins.FSharp.Psi.Features.Util.FcsTypeUtil✕
- Connections
- 1 pair of types, where a type in JetBrains.ReSharper.Plugins.FSharp.Psi.Features.ParameterInfo uses a type in JetBrains.ReSharper.Plugins.FSharp.Psi.Features.Util.FcsTypeUtil.
- The types involved
JetBrains.ReSharper.Plugins.FSharp.Psi.Features.ParameterInfo.FcsParameterInfoCandidateBase→JetBrains.ReSharper.Plugins.FSharp.Psi.Features.Util.FcsTypeUtil.FSharpType
- Direction
- JetBrains.ReSharper.Plugins.FSharp.Psi.Features.ParameterInfo uses JetBrains.ReSharper.Plugins.FSharp.Psi.Features.Util.FcsTypeUtil, so a change to JetBrains.ReSharper.Plugins.FSharp.Psi.Features.Util.FcsTypeUtil can break JetBrains.ReSharper.Plugins.FSharp.Psi.Features.ParameterInfo, while a change to JetBrains.ReSharper.Plugins.FSharp.Psi.Features.ParameterInfo can't break JetBrains.ReSharper.Plugins.FSharp.Psi.Features.Util.FcsTypeUtil.
- Position
- Below the diagonal: JetBrains.ReSharper.Plugins.FSharp.Psi.Features.ParameterInfo uses a module listed above it, which is the healthy direction.
29→24 JetBrains.ReSharper.Plugins.FSharp.Psi.Features.ParameterInfo uses JetBrains.ReSharper.Plugins.FSharp.Psi.Services.Util.FSharpCompletionUtil✕
- Connections
- 1 pair of types, where a type in JetBrains.ReSharper.Plugins.FSharp.Psi.Features.ParameterInfo uses a type in JetBrains.ReSharper.Plugins.FSharp.Psi.Services.Util.FSharpCompletionUtil.
- The types involved
JetBrains.ReSharper.Plugins.FSharp.Psi.Features.ParameterInfo.FSharpParameterInfoContextFactory→JetBrains.ReSharper.Plugins.FSharp.Psi.Services.Util.FSharpCompletionUtil.ISolution
- Direction
- JetBrains.ReSharper.Plugins.FSharp.Psi.Features.ParameterInfo uses JetBrains.ReSharper.Plugins.FSharp.Psi.Services.Util.FSharpCompletionUtil, so a change to JetBrains.ReSharper.Plugins.FSharp.Psi.Services.Util.FSharpCompletionUtil can break JetBrains.ReSharper.Plugins.FSharp.Psi.Features.ParameterInfo, while a change to JetBrains.ReSharper.Plugins.FSharp.Psi.Features.ParameterInfo can't break JetBrains.ReSharper.Plugins.FSharp.Psi.Services.Util.FSharpCompletionUtil.
- Position
- Below the diagonal: JetBrains.ReSharper.Plugins.FSharp.Psi.Features.ParameterInfo uses a module listed above it, which is the healthy direction.
29→25 JetBrains.ReSharper.Plugins.FSharp.Psi.Features.ParameterInfo uses JetBrains.ReSharper.Plugins.FSharp.Util.FSharpSymbolUtil✕
- Connections
- 1 pair of types, where a type in JetBrains.ReSharper.Plugins.FSharp.Psi.Features.ParameterInfo uses a type in JetBrains.ReSharper.Plugins.FSharp.Util.FSharpSymbolUtil.
- The types involved
JetBrains.ReSharper.Plugins.FSharp.Psi.Features.ParameterInfo.FcsDelegateParameterInfoCandidate→JetBrains.ReSharper.Plugins.FSharp.Util.FSharpSymbolUtil.FcsEntityInstance
- Direction
- JetBrains.ReSharper.Plugins.FSharp.Psi.Features.ParameterInfo uses JetBrains.ReSharper.Plugins.FSharp.Util.FSharpSymbolUtil, so a change to JetBrains.ReSharper.Plugins.FSharp.Util.FSharpSymbolUtil can break JetBrains.ReSharper.Plugins.FSharp.Psi.Features.ParameterInfo, while a change to JetBrains.ReSharper.Plugins.FSharp.Psi.Features.ParameterInfo can't break JetBrains.ReSharper.Plugins.FSharp.Util.FSharpSymbolUtil.
- Position
- Below the diagonal: JetBrains.ReSharper.Plugins.FSharp.Psi.Features.ParameterInfo uses a module listed above it, which is the healthy direction.
30→10 JetBrains.ReSharper.Plugins.FSharp.Settings uses JetBrains.ReSharper.Plugins.FSharp.Util.CommonUtil✕
- Connections
- 3 pairs of types, where a type in JetBrains.ReSharper.Plugins.FSharp.Settings uses a type in JetBrains.ReSharper.Plugins.FSharp.Util.CommonUtil.
- The types involved
JetBrains.ReSharper.Plugins.FSharp.Settings.FSharpOptionsPage→JetBrains.ReSharper.Plugins.FSharp.Util.CommonUtil.LifetimeJetBrains.ReSharper.Plugins.FSharp.Settings.FSharpSettingsProviderBase→JetBrains.ReSharper.Plugins.FSharp.Util.CommonUtil.LifetimeJetBrains.ReSharper.Plugins.FSharp.Settings.FSharpTypeHintOptionsStore→JetBrains.ReSharper.Plugins.FSharp.Util.CommonUtil.Lifetime
- Direction
- JetBrains.ReSharper.Plugins.FSharp.Settings uses JetBrains.ReSharper.Plugins.FSharp.Util.CommonUtil, so a change to JetBrains.ReSharper.Plugins.FSharp.Util.CommonUtil can break JetBrains.ReSharper.Plugins.FSharp.Settings, while a change to JetBrains.ReSharper.Plugins.FSharp.Settings can't break JetBrains.ReSharper.Plugins.FSharp.Util.CommonUtil.
- Position
- Below the diagonal: JetBrains.ReSharper.Plugins.FSharp.Settings uses a module listed above it, which is the healthy direction.
30→24 JetBrains.ReSharper.Plugins.FSharp.Settings uses JetBrains.ReSharper.Plugins.FSharp.Psi.Services.Util.FSharpCompletionUtil✕
- Connections
- 4 pairs of types, where a type in JetBrains.ReSharper.Plugins.FSharp.Settings uses a type in JetBrains.ReSharper.Plugins.FSharp.Psi.Services.Util.FSharpCompletionUtil.
- The types involved
JetBrains.ReSharper.Plugins.FSharp.Settings.FSharpExperimentalFeaturesProvider→JetBrains.ReSharper.Plugins.FSharp.Psi.Services.Util.FSharpCompletionUtil.ISolutionJetBrains.ReSharper.Plugins.FSharp.Settings.FSharpFantomasSettingsProvider→JetBrains.ReSharper.Plugins.FSharp.Psi.Services.Util.FSharpCompletionUtil.ISolutionJetBrains.ReSharper.Plugins.FSharp.Settings.FSharpOptionsProvider→JetBrains.ReSharper.Plugins.FSharp.Psi.Services.Util.FSharpCompletionUtil.ISolutionJetBrains.ReSharper.Plugins.FSharp.Settings.FSharpScriptSettingsProvider→JetBrains.ReSharper.Plugins.FSharp.Psi.Services.Util.FSharpCompletionUtil.ISolution
- Direction
- JetBrains.ReSharper.Plugins.FSharp.Settings uses JetBrains.ReSharper.Plugins.FSharp.Psi.Services.Util.FSharpCompletionUtil, so a change to JetBrains.ReSharper.Plugins.FSharp.Psi.Services.Util.FSharpCompletionUtil can break JetBrains.ReSharper.Plugins.FSharp.Settings, while a change to JetBrains.ReSharper.Plugins.FSharp.Settings can't break JetBrains.ReSharper.Plugins.FSharp.Psi.Services.Util.FSharpCompletionUtil.
- Position
- Below the diagonal: JetBrains.ReSharper.Plugins.FSharp.Settings uses a module listed above it, which is the healthy direction.
30→34 JetBrains.ReSharper.Plugins.FSharp.Settings uses JetBrains.ReSharper.Plugins.FSharp.ProjectModel part of a loop✕
- Connections
- 1 pair of types, where a type in JetBrains.ReSharper.Plugins.FSharp.Settings uses a type in JetBrains.ReSharper.Plugins.FSharp.ProjectModel.
- The types involved
JetBrains.ReSharper.Plugins.FSharp.Settings.FSharpScriptOptions→JetBrains.ReSharper.Plugins.FSharp.ProjectModel.FSharpLanguageVersion
- Direction
- JetBrains.ReSharper.Plugins.FSharp.Settings uses JetBrains.ReSharper.Plugins.FSharp.ProjectModel, so a change to JetBrains.ReSharper.Plugins.FSharp.ProjectModel can break JetBrains.ReSharper.Plugins.FSharp.Settings, while a change to JetBrains.ReSharper.Plugins.FSharp.Settings can't break JetBrains.ReSharper.Plugins.FSharp.ProjectModel.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
31→2 JetBrains.ReSharper.Plugins.FSharp.Shim.FileSystem uses FSharpFileSystemPathExtensions✕
- Connections
- 2 pairs of types, where a type in JetBrains.ReSharper.Plugins.FSharp.Shim.FileSystem uses a type in FSharpFileSystemPathExtensions.
- The types involved
JetBrains.ReSharper.Plugins.FSharp.Shim.FileSystem.AssemblyInfoShim→FSharpFileSystemPathExtensions.VirtualFileSystemPathJetBrains.ReSharper.Plugins.FSharp.Shim.FileSystem.FSharpSourceCache→FSharpFileSystemPathExtensions.VirtualFileSystemPath
- Direction
- JetBrains.ReSharper.Plugins.FSharp.Shim.FileSystem uses FSharpFileSystemPathExtensions, so a change to FSharpFileSystemPathExtensions can break JetBrains.ReSharper.Plugins.FSharp.Shim.FileSystem, while a change to JetBrains.ReSharper.Plugins.FSharp.Shim.FileSystem can't break FSharpFileSystemPathExtensions.
- Position
- Below the diagonal: JetBrains.ReSharper.Plugins.FSharp.Shim.FileSystem uses a module listed above it, which is the healthy direction.
31→10 JetBrains.ReSharper.Plugins.FSharp.Shim.FileSystem uses JetBrains.ReSharper.Plugins.FSharp.Util.CommonUtil✕
- Connections
- 2 pairs of types, where a type in JetBrains.ReSharper.Plugins.FSharp.Shim.FileSystem uses a type in JetBrains.ReSharper.Plugins.FSharp.Util.CommonUtil.
- The types involved
JetBrains.ReSharper.Plugins.FSharp.Shim.FileSystem.AssemblyInfoShim→JetBrains.ReSharper.Plugins.FSharp.Util.CommonUtil.LifetimeJetBrains.ReSharper.Plugins.FSharp.Shim.FileSystem.FSharpSourceCache→JetBrains.ReSharper.Plugins.FSharp.Util.CommonUtil.Lifetime
- Direction
- JetBrains.ReSharper.Plugins.FSharp.Shim.FileSystem uses JetBrains.ReSharper.Plugins.FSharp.Util.CommonUtil, so a change to JetBrains.ReSharper.Plugins.FSharp.Util.CommonUtil can break JetBrains.ReSharper.Plugins.FSharp.Shim.FileSystem, while a change to JetBrains.ReSharper.Plugins.FSharp.Shim.FileSystem can't break JetBrains.ReSharper.Plugins.FSharp.Util.CommonUtil.
- Position
- Below the diagonal: JetBrains.ReSharper.Plugins.FSharp.Shim.FileSystem uses a module listed above it, which is the healthy direction.
31→24 JetBrains.ReSharper.Plugins.FSharp.Shim.FileSystem uses JetBrains.ReSharper.Plugins.FSharp.Psi.Services.Util.FSharpCompletionUtil✕
- Connections
- 1 pair of types, where a type in JetBrains.ReSharper.Plugins.FSharp.Shim.FileSystem uses a type in JetBrains.ReSharper.Plugins.FSharp.Psi.Services.Util.FSharpCompletionUtil.
- The types involved
JetBrains.ReSharper.Plugins.FSharp.Shim.FileSystem.FSharpSourceCache→JetBrains.ReSharper.Plugins.FSharp.Psi.Services.Util.FSharpCompletionUtil.ISolution
- Direction
- JetBrains.ReSharper.Plugins.FSharp.Shim.FileSystem uses JetBrains.ReSharper.Plugins.FSharp.Psi.Services.Util.FSharpCompletionUtil, so a change to JetBrains.ReSharper.Plugins.FSharp.Psi.Services.Util.FSharpCompletionUtil can break JetBrains.ReSharper.Plugins.FSharp.Shim.FileSystem, while a change to JetBrains.ReSharper.Plugins.FSharp.Shim.FileSystem can't break JetBrains.ReSharper.Plugins.FSharp.Psi.Services.Util.FSharpCompletionUtil.
- Position
- Below the diagonal: JetBrains.ReSharper.Plugins.FSharp.Shim.FileSystem uses a module listed above it, which is the healthy direction.
32→2 JetBrains.ReSharper.Plugins.FSharp.ProjectModel.Scripts uses FSharpFileSystemPathExtensions✕
- Connections
- 4 pairs of types, where a type in JetBrains.ReSharper.Plugins.FSharp.ProjectModel.Scripts uses a type in FSharpFileSystemPathExtensions.
- The types involved
JetBrains.ReSharper.Plugins.FSharp.ProjectModel.Scripts.FSharpScriptModule→FSharpFileSystemPathExtensions.VirtualFileSystemPathJetBrains.ReSharper.Plugins.FSharp.ProjectModel.Scripts.FSharpScriptPsiModule→FSharpFileSystemPathExtensions.VirtualFileSystemPathJetBrains.ReSharper.Plugins.FSharp.ProjectModel.Scripts.FSharpScriptPsiModulesProvider→FSharpFileSystemPathExtensions.VirtualFileSystemPathJetBrains.ReSharper.Plugins.FSharp.ProjectModel.Scripts.IFSharpFileService→FSharpFileSystemPathExtensions.VirtualFileSystemPath
- Direction
- JetBrains.ReSharper.Plugins.FSharp.ProjectModel.Scripts uses FSharpFileSystemPathExtensions, so a change to FSharpFileSystemPathExtensions can break JetBrains.ReSharper.Plugins.FSharp.ProjectModel.Scripts, while a change to JetBrains.ReSharper.Plugins.FSharp.ProjectModel.Scripts can't break FSharpFileSystemPathExtensions.
- Position
- Below the diagonal: JetBrains.ReSharper.Plugins.FSharp.ProjectModel.Scripts uses a module listed above it, which is the healthy direction.
32→3 JetBrains.ReSharper.Plugins.FSharp.ProjectModel.Scripts uses JetBrains.ReSharper.Plugins.FSharp.Checker.FcsCheckerService✕
- Connections
- 1 pair of types, where a type in JetBrains.ReSharper.Plugins.FSharp.ProjectModel.Scripts uses a type in JetBrains.ReSharper.Plugins.FSharp.Checker.FcsCheckerService.
- The types involved
JetBrains.ReSharper.Plugins.FSharp.ProjectModel.Scripts.FSharpScriptPsiModulesProvider→JetBrains.ReSharper.Plugins.FSharp.Checker.FcsCheckerService.FcsCheckerService
- Direction
- JetBrains.ReSharper.Plugins.FSharp.ProjectModel.Scripts uses JetBrains.ReSharper.Plugins.FSharp.Checker.FcsCheckerService, so a change to JetBrains.ReSharper.Plugins.FSharp.Checker.FcsCheckerService can break JetBrains.ReSharper.Plugins.FSharp.ProjectModel.Scripts, while a change to JetBrains.ReSharper.Plugins.FSharp.ProjectModel.Scripts can't break JetBrains.ReSharper.Plugins.FSharp.Checker.FcsCheckerService.
- Position
- Below the diagonal: JetBrains.ReSharper.Plugins.FSharp.ProjectModel.Scripts uses a module listed above it, which is the healthy direction.
32→9 JetBrains.ReSharper.Plugins.FSharp.ProjectModel.Scripts uses JetBrains.ReSharper.Plugins.FSharp.Psi.PsiUtil✕
- Connections
- 2 pairs of types, where a type in JetBrains.ReSharper.Plugins.FSharp.ProjectModel.Scripts uses a type in JetBrains.ReSharper.Plugins.FSharp.Psi.PsiUtil.
- The types involved
JetBrains.ReSharper.Plugins.FSharp.ProjectModel.Scripts.FSharpScriptPsiModule→JetBrains.ReSharper.Plugins.FSharp.Psi.PsiUtil.IPsiSourceFileJetBrains.ReSharper.Plugins.FSharp.ProjectModel.Scripts.IFSharpFileService→JetBrains.ReSharper.Plugins.FSharp.Psi.PsiUtil.IPsiSourceFile
- Direction
- JetBrains.ReSharper.Plugins.FSharp.ProjectModel.Scripts uses JetBrains.ReSharper.Plugins.FSharp.Psi.PsiUtil, so a change to JetBrains.ReSharper.Plugins.FSharp.Psi.PsiUtil can break JetBrains.ReSharper.Plugins.FSharp.ProjectModel.Scripts, while a change to JetBrains.ReSharper.Plugins.FSharp.ProjectModel.Scripts can't break JetBrains.ReSharper.Plugins.FSharp.Psi.PsiUtil.
- Position
- Below the diagonal: JetBrains.ReSharper.Plugins.FSharp.ProjectModel.Scripts uses a module listed above it, which is the healthy direction.
32→10 JetBrains.ReSharper.Plugins.FSharp.ProjectModel.Scripts uses JetBrains.ReSharper.Plugins.FSharp.Util.CommonUtil✕
- Connections
- 1 pair of types, where a type in JetBrains.ReSharper.Plugins.FSharp.ProjectModel.Scripts uses a type in JetBrains.ReSharper.Plugins.FSharp.Util.CommonUtil.
- The types involved
JetBrains.ReSharper.Plugins.FSharp.ProjectModel.Scripts.FSharpScriptPsiModulesProvider→JetBrains.ReSharper.Plugins.FSharp.Util.CommonUtil.Lifetime
- Direction
- JetBrains.ReSharper.Plugins.FSharp.ProjectModel.Scripts uses JetBrains.ReSharper.Plugins.FSharp.Util.CommonUtil, so a change to JetBrains.ReSharper.Plugins.FSharp.Util.CommonUtil can break JetBrains.ReSharper.Plugins.FSharp.ProjectModel.Scripts, while a change to JetBrains.ReSharper.Plugins.FSharp.ProjectModel.Scripts can't break JetBrains.ReSharper.Plugins.FSharp.Util.CommonUtil.
- Position
- Below the diagonal: JetBrains.ReSharper.Plugins.FSharp.ProjectModel.Scripts uses a module listed above it, which is the healthy direction.
32→24 JetBrains.ReSharper.Plugins.FSharp.ProjectModel.Scripts uses JetBrains.ReSharper.Plugins.FSharp.Psi.Services.Util.FSharpCompletionUtil✕
- Connections
- 2 pairs of types, where a type in JetBrains.ReSharper.Plugins.FSharp.ProjectModel.Scripts uses a type in JetBrains.ReSharper.Plugins.FSharp.Psi.Services.Util.FSharpCompletionUtil.
- The types involved
JetBrains.ReSharper.Plugins.FSharp.ProjectModel.Scripts.FSharpScriptModule→JetBrains.ReSharper.Plugins.FSharp.Psi.Services.Util.FSharpCompletionUtil.ISolutionJetBrains.ReSharper.Plugins.FSharp.ProjectModel.Scripts.FSharpScriptPsiModulesProvider→JetBrains.ReSharper.Plugins.FSharp.Psi.Services.Util.FSharpCompletionUtil.ISolution
- Direction
- JetBrains.ReSharper.Plugins.FSharp.ProjectModel.Scripts uses JetBrains.ReSharper.Plugins.FSharp.Psi.Services.Util.FSharpCompletionUtil, so a change to JetBrains.ReSharper.Plugins.FSharp.Psi.Services.Util.FSharpCompletionUtil can break JetBrains.ReSharper.Plugins.FSharp.ProjectModel.Scripts, while a change to JetBrains.ReSharper.Plugins.FSharp.ProjectModel.Scripts can't break JetBrains.ReSharper.Plugins.FSharp.Psi.Services.Util.FSharpCompletionUtil.
- Position
- Below the diagonal: JetBrains.ReSharper.Plugins.FSharp.ProjectModel.Scripts uses a module listed above it, which is the healthy direction.
32→30 JetBrains.ReSharper.Plugins.FSharp.ProjectModel.Scripts uses JetBrains.ReSharper.Plugins.FSharp.Settings✕
- Connections
- 1 pair of types, where a type in JetBrains.ReSharper.Plugins.FSharp.ProjectModel.Scripts uses a type in JetBrains.ReSharper.Plugins.FSharp.Settings.
- The types involved
JetBrains.ReSharper.Plugins.FSharp.ProjectModel.Scripts.FSharpScriptLanguageLevelProvider→JetBrains.ReSharper.Plugins.FSharp.Settings.FSharpScriptSettingsProvider
- Direction
- JetBrains.ReSharper.Plugins.FSharp.ProjectModel.Scripts uses JetBrains.ReSharper.Plugins.FSharp.Settings, so a change to JetBrains.ReSharper.Plugins.FSharp.Settings can break JetBrains.ReSharper.Plugins.FSharp.ProjectModel.Scripts, while a change to JetBrains.ReSharper.Plugins.FSharp.ProjectModel.Scripts can't break JetBrains.ReSharper.Plugins.FSharp.Settings.
- Position
- Below the diagonal: JetBrains.ReSharper.Plugins.FSharp.ProjectModel.Scripts uses a module listed above it, which is the healthy direction.
32→34 JetBrains.ReSharper.Plugins.FSharp.ProjectModel.Scripts uses JetBrains.ReSharper.Plugins.FSharp.ProjectModel part of a loop✕
- Connections
- 1 pair of types, where a type in JetBrains.ReSharper.Plugins.FSharp.ProjectModel.Scripts uses a type in JetBrains.ReSharper.Plugins.FSharp.ProjectModel.
- The types involved
JetBrains.ReSharper.Plugins.FSharp.ProjectModel.Scripts.FSharpScriptLanguageLevelProvider→JetBrains.ReSharper.Plugins.FSharp.ProjectModel.FSharpLanguageLevelProviderForAnyModule
- Direction
- JetBrains.ReSharper.Plugins.FSharp.ProjectModel.Scripts uses JetBrains.ReSharper.Plugins.FSharp.ProjectModel, so a change to JetBrains.ReSharper.Plugins.FSharp.ProjectModel can break JetBrains.ReSharper.Plugins.FSharp.ProjectModel.Scripts, while a change to JetBrains.ReSharper.Plugins.FSharp.ProjectModel.Scripts can't break JetBrains.ReSharper.Plugins.FSharp.ProjectModel.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
32→36 JetBrains.ReSharper.Plugins.FSharp.ProjectModel.Scripts uses JetBrains.ReSharper.Plugins.FSharp.Checker part of a loop✕
- Connections
- 1 pair of types, where a type in JetBrains.ReSharper.Plugins.FSharp.ProjectModel.Scripts uses a type in JetBrains.ReSharper.Plugins.FSharp.Checker.
- The types involved
JetBrains.ReSharper.Plugins.FSharp.ProjectModel.Scripts.FSharpScriptPsiModulesProvider→JetBrains.ReSharper.Plugins.FSharp.Checker.IScriptFcsProjectProvider
- Direction
- JetBrains.ReSharper.Plugins.FSharp.ProjectModel.Scripts uses JetBrains.ReSharper.Plugins.FSharp.Checker, so a change to JetBrains.ReSharper.Plugins.FSharp.Checker can break JetBrains.ReSharper.Plugins.FSharp.ProjectModel.Scripts, while a change to JetBrains.ReSharper.Plugins.FSharp.ProjectModel.Scripts can't break JetBrains.ReSharper.Plugins.FSharp.Checker.
- 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.
33→2 JetBrains.ReSharper.Plugins.FSharp.Services.Formatter uses FSharpFileSystemPathExtensions✕
- Connections
- 2 pairs of types, where a type in JetBrains.ReSharper.Plugins.FSharp.Services.Formatter uses a type in FSharpFileSystemPathExtensions.
- The types involved
JetBrains.ReSharper.Plugins.FSharp.Services.Formatter.FantomasDetector→FSharpFileSystemPathExtensions.VirtualFileSystemPathJetBrains.ReSharper.Plugins.FSharp.Services.Formatter.FantomasRunSettings→FSharpFileSystemPathExtensions.VirtualFileSystemPath
- Direction
- JetBrains.ReSharper.Plugins.FSharp.Services.Formatter uses FSharpFileSystemPathExtensions, so a change to FSharpFileSystemPathExtensions can break JetBrains.ReSharper.Plugins.FSharp.Services.Formatter, while a change to JetBrains.ReSharper.Plugins.FSharp.Services.Formatter can't break FSharpFileSystemPathExtensions.
- Position
- Below the diagonal: JetBrains.ReSharper.Plugins.FSharp.Services.Formatter uses a module listed above it, which is the healthy direction.
33→6 JetBrains.ReSharper.Plugins.FSharp.Services.Formatter uses JetBrains.ReSharper.Plugins.FSharp.Util.SettingsStoreUtil✕
- Connections
- 1 pair of types, where a type in JetBrains.ReSharper.Plugins.FSharp.Services.Formatter uses a type in JetBrains.ReSharper.Plugins.FSharp.Util.SettingsStoreUtil.
- The types involved
JetBrains.ReSharper.Plugins.FSharp.Services.Formatter.FantomasHost→JetBrains.ReSharper.Plugins.FSharp.Util.SettingsStoreUtil.IContextBoundSettingsStore
- Direction
- JetBrains.ReSharper.Plugins.FSharp.Services.Formatter uses JetBrains.ReSharper.Plugins.FSharp.Util.SettingsStoreUtil, so a change to JetBrains.ReSharper.Plugins.FSharp.Util.SettingsStoreUtil can break JetBrains.ReSharper.Plugins.FSharp.Services.Formatter, while a change to JetBrains.ReSharper.Plugins.FSharp.Services.Formatter can't break JetBrains.ReSharper.Plugins.FSharp.Util.SettingsStoreUtil.
- Position
- Below the diagonal: JetBrains.ReSharper.Plugins.FSharp.Services.Formatter uses a module listed above it, which is the healthy direction.
33→9 JetBrains.ReSharper.Plugins.FSharp.Services.Formatter uses JetBrains.ReSharper.Plugins.FSharp.Psi.PsiUtil✕
- Connections
- 1 pair of types, where a type in JetBrains.ReSharper.Plugins.FSharp.Services.Formatter uses a type in JetBrains.ReSharper.Plugins.FSharp.Psi.PsiUtil.
- The types involved
JetBrains.ReSharper.Plugins.FSharp.Services.Formatter.FSharpReformatCode→JetBrains.ReSharper.Plugins.FSharp.Psi.PsiUtil.IPsiSourceFile
- Direction
- JetBrains.ReSharper.Plugins.FSharp.Services.Formatter uses JetBrains.ReSharper.Plugins.FSharp.Psi.PsiUtil, so a change to JetBrains.ReSharper.Plugins.FSharp.Psi.PsiUtil can break JetBrains.ReSharper.Plugins.FSharp.Services.Formatter, while a change to JetBrains.ReSharper.Plugins.FSharp.Services.Formatter can't break JetBrains.ReSharper.Plugins.FSharp.Psi.PsiUtil.
- Position
- Below the diagonal: JetBrains.ReSharper.Plugins.FSharp.Services.Formatter uses a module listed above it, which is the healthy direction.
33→24 JetBrains.ReSharper.Plugins.FSharp.Services.Formatter uses JetBrains.ReSharper.Plugins.FSharp.Psi.Services.Util.FSharpCompletionUtil✕
- Connections
- 1 pair of types, where a type in JetBrains.ReSharper.Plugins.FSharp.Services.Formatter uses a type in JetBrains.ReSharper.Plugins.FSharp.Psi.Services.Util.FSharpCompletionUtil.
- The types involved
JetBrains.ReSharper.Plugins.FSharp.Services.Formatter.FantomasHost→JetBrains.ReSharper.Plugins.FSharp.Psi.Services.Util.FSharpCompletionUtil.ISolution
- Direction
- JetBrains.ReSharper.Plugins.FSharp.Services.Formatter uses JetBrains.ReSharper.Plugins.FSharp.Psi.Services.Util.FSharpCompletionUtil, so a change to JetBrains.ReSharper.Plugins.FSharp.Psi.Services.Util.FSharpCompletionUtil can break JetBrains.ReSharper.Plugins.FSharp.Services.Formatter, while a change to JetBrains.ReSharper.Plugins.FSharp.Services.Formatter can't break JetBrains.ReSharper.Plugins.FSharp.Psi.Services.Util.FSharpCompletionUtil.
- Position
- Below the diagonal: JetBrains.ReSharper.Plugins.FSharp.Services.Formatter uses a module listed above it, which is the healthy direction.
33→30 JetBrains.ReSharper.Plugins.FSharp.Services.Formatter uses JetBrains.ReSharper.Plugins.FSharp.Settings✕
- Connections
- 2 pairs of types, where a type in JetBrains.ReSharper.Plugins.FSharp.Services.Formatter uses a type in JetBrains.ReSharper.Plugins.FSharp.Settings.
- The types involved
JetBrains.ReSharper.Plugins.FSharp.Services.Formatter.FantomasDetector→JetBrains.ReSharper.Plugins.FSharp.Settings.FSharpFantomasSettingsProviderJetBrains.ReSharper.Plugins.FSharp.Services.Formatter.FantomasPage→JetBrains.ReSharper.Plugins.FSharp.Settings.FSharpOptionsPageBase
- Direction
- JetBrains.ReSharper.Plugins.FSharp.Services.Formatter uses JetBrains.ReSharper.Plugins.FSharp.Settings, so a change to JetBrains.ReSharper.Plugins.FSharp.Settings can break JetBrains.ReSharper.Plugins.FSharp.Services.Formatter, while a change to JetBrains.ReSharper.Plugins.FSharp.Services.Formatter can't break JetBrains.ReSharper.Plugins.FSharp.Settings.
- Position
- Below the diagonal: JetBrains.ReSharper.Plugins.FSharp.Services.Formatter uses a module listed above it, which is the healthy direction.
34→2 JetBrains.ReSharper.Plugins.FSharp.ProjectModel uses FSharpFileSystemPathExtensions✕
- Connections
- 2 pairs of types, where a type in JetBrains.ReSharper.Plugins.FSharp.ProjectModel uses a type in FSharpFileSystemPathExtensions.
- The types involved
JetBrains.ReSharper.Plugins.FSharp.ProjectModel.FSharpFileService→FSharpFileSystemPathExtensions.VirtualFileSystemPathJetBrains.ReSharper.Plugins.FSharp.ProjectModel.FSharpLanguageLevelProjectProperty→FSharpFileSystemPathExtensions.VirtualFileSystemPath
- Direction
- JetBrains.ReSharper.Plugins.FSharp.ProjectModel uses FSharpFileSystemPathExtensions, so a change to FSharpFileSystemPathExtensions can break JetBrains.ReSharper.Plugins.FSharp.ProjectModel, while a change to JetBrains.ReSharper.Plugins.FSharp.ProjectModel can't break FSharpFileSystemPathExtensions.
- Position
- Below the diagonal: JetBrains.ReSharper.Plugins.FSharp.ProjectModel uses a module listed above it, which is the healthy direction.
34→8 JetBrains.ReSharper.Plugins.FSharp.ProjectModel uses JetBrains.ReSharper.Plugins.FSharp.ProjectModel.Util✕
- Connections
- 2 pairs of types, where a type in JetBrains.ReSharper.Plugins.FSharp.ProjectModel uses a type in JetBrains.ReSharper.Plugins.FSharp.ProjectModel.Util.
- The types involved
JetBrains.ReSharper.Plugins.FSharp.ProjectModel.FSharpLanguageLevelProjectProperty→JetBrains.ReSharper.Plugins.FSharp.ProjectModel.Util.IProjectJetBrains.ReSharper.Plugins.FSharp.ProjectModel.FSharpLanguageSpecificItemsProvider→JetBrains.ReSharper.Plugins.FSharp.ProjectModel.Util.IProject
- Direction
- JetBrains.ReSharper.Plugins.FSharp.ProjectModel uses JetBrains.ReSharper.Plugins.FSharp.ProjectModel.Util, so a change to JetBrains.ReSharper.Plugins.FSharp.ProjectModel.Util can break JetBrains.ReSharper.Plugins.FSharp.ProjectModel, while a change to JetBrains.ReSharper.Plugins.FSharp.ProjectModel can't break JetBrains.ReSharper.Plugins.FSharp.ProjectModel.Util.
- Position
- Below the diagonal: JetBrains.ReSharper.Plugins.FSharp.ProjectModel uses a module listed above it, which is the healthy direction.
34→32 JetBrains.ReSharper.Plugins.FSharp.ProjectModel uses JetBrains.ReSharper.Plugins.FSharp.ProjectModel.Scripts✕
- Connections
- 1 pair of types, where a type in JetBrains.ReSharper.Plugins.FSharp.ProjectModel uses a type in JetBrains.ReSharper.Plugins.FSharp.ProjectModel.Scripts.
- The types involved
JetBrains.ReSharper.Plugins.FSharp.ProjectModel.FSharpFileService→JetBrains.ReSharper.Plugins.FSharp.ProjectModel.Scripts.IFSharpFileService
- Direction
- JetBrains.ReSharper.Plugins.FSharp.ProjectModel uses JetBrains.ReSharper.Plugins.FSharp.ProjectModel.Scripts, so a change to JetBrains.ReSharper.Plugins.FSharp.ProjectModel.Scripts can break JetBrains.ReSharper.Plugins.FSharp.ProjectModel, while a change to JetBrains.ReSharper.Plugins.FSharp.ProjectModel can't break JetBrains.ReSharper.Plugins.FSharp.ProjectModel.Scripts.
- Position
- Below the diagonal: JetBrains.ReSharper.Plugins.FSharp.ProjectModel uses a module listed above it, which is the healthy direction.
35→8 JetBrains.ReSharper.Plugins.FSharp.Shim.TypeProviders uses JetBrains.ReSharper.Plugins.FSharp.ProjectModel.Util✕
- Connections
- 1 pair of types, where a type in JetBrains.ReSharper.Plugins.FSharp.Shim.TypeProviders uses a type in JetBrains.ReSharper.Plugins.FSharp.ProjectModel.Util.
- The types involved
JetBrains.ReSharper.Plugins.FSharp.Shim.TypeProviders.SolutionTypeProvidersClient→JetBrains.ReSharper.Plugins.FSharp.ProjectModel.Util.IProject
- Direction
- JetBrains.ReSharper.Plugins.FSharp.Shim.TypeProviders uses JetBrains.ReSharper.Plugins.FSharp.ProjectModel.Util, so a change to JetBrains.ReSharper.Plugins.FSharp.ProjectModel.Util can break JetBrains.ReSharper.Plugins.FSharp.Shim.TypeProviders, while a change to JetBrains.ReSharper.Plugins.FSharp.Shim.TypeProviders can't break JetBrains.ReSharper.Plugins.FSharp.ProjectModel.Util.
- Position
- Below the diagonal: JetBrains.ReSharper.Plugins.FSharp.Shim.TypeProviders uses a module listed above it, which is the healthy direction.
35→24 JetBrains.ReSharper.Plugins.FSharp.Shim.TypeProviders uses JetBrains.ReSharper.Plugins.FSharp.Psi.Services.Util.FSharpCompletionUtil✕
- Connections
- 1 pair of types, where a type in JetBrains.ReSharper.Plugins.FSharp.Shim.TypeProviders uses a type in JetBrains.ReSharper.Plugins.FSharp.Psi.Services.Util.FSharpCompletionUtil.
- The types involved
JetBrains.ReSharper.Plugins.FSharp.Shim.TypeProviders.TypeProvidersShim→JetBrains.ReSharper.Plugins.FSharp.Psi.Services.Util.FSharpCompletionUtil.ISolution
- Direction
- JetBrains.ReSharper.Plugins.FSharp.Shim.TypeProviders uses JetBrains.ReSharper.Plugins.FSharp.Psi.Services.Util.FSharpCompletionUtil, so a change to JetBrains.ReSharper.Plugins.FSharp.Psi.Services.Util.FSharpCompletionUtil can break JetBrains.ReSharper.Plugins.FSharp.Shim.TypeProviders, while a change to JetBrains.ReSharper.Plugins.FSharp.Shim.TypeProviders can't break JetBrains.ReSharper.Plugins.FSharp.Psi.Services.Util.FSharpCompletionUtil.
- Position
- Below the diagonal: JetBrains.ReSharper.Plugins.FSharp.Shim.TypeProviders uses a module listed above it, which is the healthy direction.
35→30 JetBrains.ReSharper.Plugins.FSharp.Shim.TypeProviders uses JetBrains.ReSharper.Plugins.FSharp.Settings✕
- Connections
- 1 pair of types, where a type in JetBrains.ReSharper.Plugins.FSharp.Shim.TypeProviders uses a type in JetBrains.ReSharper.Plugins.FSharp.Settings.
- The types involved
JetBrains.ReSharper.Plugins.FSharp.Shim.TypeProviders.TypeProvidersShim→JetBrains.ReSharper.Plugins.FSharp.Settings.FSharpExperimentalFeaturesProvider
- Direction
- JetBrains.ReSharper.Plugins.FSharp.Shim.TypeProviders uses JetBrains.ReSharper.Plugins.FSharp.Settings, so a change to JetBrains.ReSharper.Plugins.FSharp.Settings can break JetBrains.ReSharper.Plugins.FSharp.Shim.TypeProviders, while a change to JetBrains.ReSharper.Plugins.FSharp.Shim.TypeProviders can't break JetBrains.ReSharper.Plugins.FSharp.Settings.
- Position
- Below the diagonal: JetBrains.ReSharper.Plugins.FSharp.Shim.TypeProviders uses a module listed above it, which is the healthy direction.
35→32 JetBrains.ReSharper.Plugins.FSharp.Shim.TypeProviders uses JetBrains.ReSharper.Plugins.FSharp.ProjectModel.Scripts✕
- Connections
- 2 pairs of types, where a type in JetBrains.ReSharper.Plugins.FSharp.Shim.TypeProviders uses a type in JetBrains.ReSharper.Plugins.FSharp.ProjectModel.Scripts.
- The types involved
JetBrains.ReSharper.Plugins.FSharp.Shim.TypeProviders.ScriptTypeProvidersClient→JetBrains.ReSharper.Plugins.FSharp.ProjectModel.Scripts.FSharpScriptPsiModulesProviderJetBrains.ReSharper.Plugins.FSharp.Shim.TypeProviders.TypeProvidersShim→JetBrains.ReSharper.Plugins.FSharp.ProjectModel.Scripts.FSharpScriptPsiModulesProvider
- Direction
- JetBrains.ReSharper.Plugins.FSharp.Shim.TypeProviders uses JetBrains.ReSharper.Plugins.FSharp.ProjectModel.Scripts, so a change to JetBrains.ReSharper.Plugins.FSharp.ProjectModel.Scripts can break JetBrains.ReSharper.Plugins.FSharp.Shim.TypeProviders, while a change to JetBrains.ReSharper.Plugins.FSharp.Shim.TypeProviders can't break JetBrains.ReSharper.Plugins.FSharp.ProjectModel.Scripts.
- Position
- Below the diagonal: JetBrains.ReSharper.Plugins.FSharp.Shim.TypeProviders uses a module listed above it, which is the healthy direction.
35→36 JetBrains.ReSharper.Plugins.FSharp.Shim.TypeProviders uses JetBrains.ReSharper.Plugins.FSharp.Checker part of a loop✕
- Connections
- 2 pairs of types, where a type in JetBrains.ReSharper.Plugins.FSharp.Shim.TypeProviders uses a type in JetBrains.ReSharper.Plugins.FSharp.Checker.
- The types involved
JetBrains.ReSharper.Plugins.FSharp.Shim.TypeProviders.SolutionTypeProvidersClient→JetBrains.ReSharper.Plugins.FSharp.Checker.IFcsProjectProviderJetBrains.ReSharper.Plugins.FSharp.Shim.TypeProviders.TypeProvidersShim→JetBrains.ReSharper.Plugins.FSharp.Checker.IFcsProjectProvider
- Direction
- JetBrains.ReSharper.Plugins.FSharp.Shim.TypeProviders uses JetBrains.ReSharper.Plugins.FSharp.Checker, so a change to JetBrains.ReSharper.Plugins.FSharp.Checker can break JetBrains.ReSharper.Plugins.FSharp.Shim.TypeProviders, while a change to JetBrains.ReSharper.Plugins.FSharp.Shim.TypeProviders can't break JetBrains.ReSharper.Plugins.FSharp.Checker.
- 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.
36→2 JetBrains.ReSharper.Plugins.FSharp.Checker uses FSharpFileSystemPathExtensions✕
- Connections
- 2 pairs of types, where a type in JetBrains.ReSharper.Plugins.FSharp.Checker uses a type in FSharpFileSystemPathExtensions.
- The types involved
JetBrains.ReSharper.Plugins.FSharp.Checker.FcsProject→FSharpFileSystemPathExtensions.VirtualFileSystemPathJetBrains.ReSharper.Plugins.FSharp.Checker.ScriptFcsProjectProvider→FSharpFileSystemPathExtensions.VirtualFileSystemPath
- Direction
- JetBrains.ReSharper.Plugins.FSharp.Checker uses FSharpFileSystemPathExtensions, so a change to FSharpFileSystemPathExtensions can break JetBrains.ReSharper.Plugins.FSharp.Checker, while a change to JetBrains.ReSharper.Plugins.FSharp.Checker can't break FSharpFileSystemPathExtensions.
- Position
- Below the diagonal: JetBrains.ReSharper.Plugins.FSharp.Checker uses a module listed above it, which is the healthy direction.
36→8 JetBrains.ReSharper.Plugins.FSharp.Checker uses JetBrains.ReSharper.Plugins.FSharp.ProjectModel.Util✕
- Connections
- 3 pairs of types, where a type in JetBrains.ReSharper.Plugins.FSharp.Checker uses a type in JetBrains.ReSharper.Plugins.FSharp.ProjectModel.Util.
- The types involved
JetBrains.ReSharper.Plugins.FSharp.Checker.FcsProjectKey→JetBrains.ReSharper.Plugins.FSharp.ProjectModel.Util.IProjectJetBrains.ReSharper.Plugins.FSharp.Checker.FcsProjectProvider→JetBrains.ReSharper.Plugins.FSharp.ProjectModel.Util.IProjectJetBrains.ReSharper.Plugins.FSharp.Checker.IFcsProjectProvider→JetBrains.ReSharper.Plugins.FSharp.ProjectModel.Util.IProject
- Direction
- JetBrains.ReSharper.Plugins.FSharp.Checker uses JetBrains.ReSharper.Plugins.FSharp.ProjectModel.Util, so a change to JetBrains.ReSharper.Plugins.FSharp.ProjectModel.Util can break JetBrains.ReSharper.Plugins.FSharp.Checker, while a change to JetBrains.ReSharper.Plugins.FSharp.Checker can't break JetBrains.ReSharper.Plugins.FSharp.ProjectModel.Util.
- Position
- Below the diagonal: JetBrains.ReSharper.Plugins.FSharp.Checker uses a module listed above it, which is the healthy direction.
36→9 JetBrains.ReSharper.Plugins.FSharp.Checker uses JetBrains.ReSharper.Plugins.FSharp.Psi.PsiUtil✕
- Connections
- 6 pairs of types, where a type in JetBrains.ReSharper.Plugins.FSharp.Checker uses a type in JetBrains.ReSharper.Plugins.FSharp.Psi.PsiUtil.
- The types involved
JetBrains.ReSharper.Plugins.FSharp.Checker.FcsProject→JetBrains.ReSharper.Plugins.FSharp.Psi.PsiUtil.IPsiSourceFileJetBrains.ReSharper.Plugins.FSharp.Checker.FcsProjectProvider→JetBrains.ReSharper.Plugins.FSharp.Psi.PsiUtil.IPsiSourceFileJetBrains.ReSharper.Plugins.FSharp.Checker.IFcsProjectProvider→JetBrains.ReSharper.Plugins.FSharp.Psi.PsiUtil.IPsiSourceFileJetBrains.ReSharper.Plugins.FSharp.Checker.IScriptFcsProjectProvider→JetBrains.ReSharper.Plugins.FSharp.Psi.PsiUtil.IPsiSourceFileJetBrains.ReSharper.Plugins.FSharp.Checker.LightweightFcsProjectProvider→JetBrains.ReSharper.Plugins.FSharp.Psi.PsiUtil.IPsiSourceFileJetBrains.ReSharper.Plugins.FSharp.Checker.ScriptFcsProjectProvider→JetBrains.ReSharper.Plugins.FSharp.Psi.PsiUtil.IPsiSourceFile
- Direction
- JetBrains.ReSharper.Plugins.FSharp.Checker uses JetBrains.ReSharper.Plugins.FSharp.Psi.PsiUtil, so a change to JetBrains.ReSharper.Plugins.FSharp.Psi.PsiUtil can break JetBrains.ReSharper.Plugins.FSharp.Checker, while a change to JetBrains.ReSharper.Plugins.FSharp.Checker can't break JetBrains.ReSharper.Plugins.FSharp.Psi.PsiUtil.
- Position
- Below the diagonal: JetBrains.ReSharper.Plugins.FSharp.Checker uses a module listed above it, which is the healthy direction.
36→10 JetBrains.ReSharper.Plugins.FSharp.Checker uses JetBrains.ReSharper.Plugins.FSharp.Util.CommonUtil✕
- Connections
- 7 pairs of types, where a type in JetBrains.ReSharper.Plugins.FSharp.Checker uses a type in JetBrains.ReSharper.Plugins.FSharp.Util.CommonUtil.
- The types involved
JetBrains.ReSharper.Plugins.FSharp.Checker.FcsCheckerService→JetBrains.ReSharper.Plugins.FSharp.Util.CommonUtil.LifetimeJetBrains.ReSharper.Plugins.FSharp.Checker.FcsProject→JetBrains.ReSharper.Plugins.FSharp.Util.CommonUtil.IDictionaryJetBrains.ReSharper.Plugins.FSharp.Checker.FcsProject→JetBrains.ReSharper.Plugins.FSharp.Util.CommonUtil.ISetJetBrains.ReSharper.Plugins.FSharp.Checker.FcsProjectProvider→JetBrains.ReSharper.Plugins.FSharp.Util.CommonUtil.LifetimeJetBrains.ReSharper.Plugins.FSharp.Checker.LightweightFcsProjectProvider→JetBrains.ReSharper.Plugins.FSharp.Util.CommonUtil.LifetimeJetBrains.ReSharper.Plugins.FSharp.Checker.OutputAssemblyChangeInvalidator→JetBrains.ReSharper.Plugins.FSharp.Util.CommonUtil.LifetimeJetBrains.ReSharper.Plugins.FSharp.Checker.ScriptFcsProjectProvider→JetBrains.ReSharper.Plugins.FSharp.Util.CommonUtil.Lifetime
- Direction
- JetBrains.ReSharper.Plugins.FSharp.Checker uses JetBrains.ReSharper.Plugins.FSharp.Util.CommonUtil, so a change to JetBrains.ReSharper.Plugins.FSharp.Util.CommonUtil can break JetBrains.ReSharper.Plugins.FSharp.Checker, while a change to JetBrains.ReSharper.Plugins.FSharp.Checker can't break JetBrains.ReSharper.Plugins.FSharp.Util.CommonUtil.
- Position
- Below the diagonal: JetBrains.ReSharper.Plugins.FSharp.Checker uses a module listed above it, which is the healthy direction.
36→24 JetBrains.ReSharper.Plugins.FSharp.Checker uses JetBrains.ReSharper.Plugins.FSharp.Psi.Services.Util.FSharpCompletionUtil✕
- Connections
- 1 pair of types, where a type in JetBrains.ReSharper.Plugins.FSharp.Checker uses a type in JetBrains.ReSharper.Plugins.FSharp.Psi.Services.Util.FSharpCompletionUtil.
- The types involved
JetBrains.ReSharper.Plugins.FSharp.Checker.FcsProjectProvider→JetBrains.ReSharper.Plugins.FSharp.Psi.Services.Util.FSharpCompletionUtil.ISolution
- Direction
- JetBrains.ReSharper.Plugins.FSharp.Checker uses JetBrains.ReSharper.Plugins.FSharp.Psi.Services.Util.FSharpCompletionUtil, so a change to JetBrains.ReSharper.Plugins.FSharp.Psi.Services.Util.FSharpCompletionUtil can break JetBrains.ReSharper.Plugins.FSharp.Checker, while a change to JetBrains.ReSharper.Plugins.FSharp.Checker can't break JetBrains.ReSharper.Plugins.FSharp.Psi.Services.Util.FSharpCompletionUtil.
- Position
- Below the diagonal: JetBrains.ReSharper.Plugins.FSharp.Checker uses a module listed above it, which is the healthy direction.
36→26 JetBrains.ReSharper.Plugins.FSharp.Checker uses JetBrains.ReSharper.Plugins.FSharp.ProjectModel.Host.ProjectItems.ItemsContainer✕
- Connections
- 2 pairs of types, where a type in JetBrains.ReSharper.Plugins.FSharp.Checker uses a type in JetBrains.ReSharper.Plugins.FSharp.ProjectModel.Host.ProjectItems.ItemsContainer.
- The types involved
JetBrains.ReSharper.Plugins.FSharp.Checker.FcsProjectBuilder→JetBrains.ReSharper.Plugins.FSharp.ProjectModel.Host.ProjectItems.ItemsContainer.IFSharpItemsContainerJetBrains.ReSharper.Plugins.FSharp.Checker.FcsProjectProvider→JetBrains.ReSharper.Plugins.FSharp.ProjectModel.Host.ProjectItems.ItemsContainer.IFSharpItemsContainer
- Direction
- JetBrains.ReSharper.Plugins.FSharp.Checker uses JetBrains.ReSharper.Plugins.FSharp.ProjectModel.Host.ProjectItems.ItemsContainer, so a change to JetBrains.ReSharper.Plugins.FSharp.ProjectModel.Host.ProjectItems.ItemsContainer can break JetBrains.ReSharper.Plugins.FSharp.Checker, while a change to JetBrains.ReSharper.Plugins.FSharp.Checker can't break JetBrains.ReSharper.Plugins.FSharp.ProjectModel.Host.ProjectItems.ItemsContainer.
- Position
- Below the diagonal: JetBrains.ReSharper.Plugins.FSharp.Checker uses a module listed above it, which is the healthy direction.
36→30 JetBrains.ReSharper.Plugins.FSharp.Checker uses JetBrains.ReSharper.Plugins.FSharp.Settings✕
- Connections
- 1 pair of types, where a type in JetBrains.ReSharper.Plugins.FSharp.Checker uses a type in JetBrains.ReSharper.Plugins.FSharp.Settings.
- The types involved
JetBrains.ReSharper.Plugins.FSharp.Checker.ScriptFcsProjectProvider→JetBrains.ReSharper.Plugins.FSharp.Settings.FSharpScriptSettingsProvider
- Direction
- JetBrains.ReSharper.Plugins.FSharp.Checker uses JetBrains.ReSharper.Plugins.FSharp.Settings, so a change to JetBrains.ReSharper.Plugins.FSharp.Settings can break JetBrains.ReSharper.Plugins.FSharp.Checker, while a change to JetBrains.ReSharper.Plugins.FSharp.Checker can't break JetBrains.ReSharper.Plugins.FSharp.Settings.
- Position
- Below the diagonal: JetBrains.ReSharper.Plugins.FSharp.Checker uses a module listed above it, which is the healthy direction.
36→32 JetBrains.ReSharper.Plugins.FSharp.Checker uses JetBrains.ReSharper.Plugins.FSharp.ProjectModel.Scripts✕
- Connections
- 1 pair of types, where a type in JetBrains.ReSharper.Plugins.FSharp.Checker uses a type in JetBrains.ReSharper.Plugins.FSharp.ProjectModel.Scripts.
- The types involved
JetBrains.ReSharper.Plugins.FSharp.Checker.FcsProjectProvider→JetBrains.ReSharper.Plugins.FSharp.ProjectModel.Scripts.IFSharpFileService
- Direction
- JetBrains.ReSharper.Plugins.FSharp.Checker uses JetBrains.ReSharper.Plugins.FSharp.ProjectModel.Scripts, so a change to JetBrains.ReSharper.Plugins.FSharp.ProjectModel.Scripts can break JetBrains.ReSharper.Plugins.FSharp.Checker, while a change to JetBrains.ReSharper.Plugins.FSharp.Checker can't break JetBrains.ReSharper.Plugins.FSharp.ProjectModel.Scripts.
- Position
- Below the diagonal: JetBrains.ReSharper.Plugins.FSharp.Checker uses a module listed above it, which is the healthy direction.
36→34 JetBrains.ReSharper.Plugins.FSharp.Checker uses JetBrains.ReSharper.Plugins.FSharp.ProjectModel✕
- Connections
- 1 pair of types, where a type in JetBrains.ReSharper.Plugins.FSharp.Checker uses a type in JetBrains.ReSharper.Plugins.FSharp.ProjectModel.
- The types involved
JetBrains.ReSharper.Plugins.FSharp.Checker.FcsProjectBuilder→JetBrains.ReSharper.Plugins.FSharp.ProjectModel.FSharpLanguageLevelProjectProperty
- Direction
- JetBrains.ReSharper.Plugins.FSharp.Checker uses JetBrains.ReSharper.Plugins.FSharp.ProjectModel, so a change to JetBrains.ReSharper.Plugins.FSharp.ProjectModel can break JetBrains.ReSharper.Plugins.FSharp.Checker, while a change to JetBrains.ReSharper.Plugins.FSharp.Checker can't break JetBrains.ReSharper.Plugins.FSharp.ProjectModel.
- Position
- Below the diagonal: JetBrains.ReSharper.Plugins.FSharp.Checker uses a module listed above it, which is the healthy direction.
36→35 JetBrains.ReSharper.Plugins.FSharp.Checker uses JetBrains.ReSharper.Plugins.FSharp.Shim.TypeProviders✕
- Connections
- 1 pair of types, where a type in JetBrains.ReSharper.Plugins.FSharp.Checker uses a type in JetBrains.ReSharper.Plugins.FSharp.Shim.TypeProviders.
- The types involved
JetBrains.ReSharper.Plugins.FSharp.Checker.OutputAssemblyChangeInvalidator→JetBrains.ReSharper.Plugins.FSharp.Shim.TypeProviders.ITypeProvidersShim
- Direction
- JetBrains.ReSharper.Plugins.FSharp.Checker uses JetBrains.ReSharper.Plugins.FSharp.Shim.TypeProviders, so a change to JetBrains.ReSharper.Plugins.FSharp.Shim.TypeProviders can break JetBrains.ReSharper.Plugins.FSharp.Checker, while a change to JetBrains.ReSharper.Plugins.FSharp.Checker can't break JetBrains.ReSharper.Plugins.FSharp.Shim.TypeProviders.
- Position
- Below the diagonal: JetBrains.ReSharper.Plugins.FSharp.Checker uses a module listed above it, which is the healthy direction.
37→9 JetBrains.ReSharper.Plugins.FSharp.Psi.Features.CodeCompletion.Rules uses JetBrains.ReSharper.Plugins.FSharp.Psi.PsiUtil✕
- Connections
- 1 pair of types, where a type in JetBrains.ReSharper.Plugins.FSharp.Psi.Features.CodeCompletion.Rules uses a type in JetBrains.ReSharper.Plugins.FSharp.Psi.PsiUtil.
- The types involved
JetBrains.ReSharper.Plugins.FSharp.Psi.Features.CodeCompletion.Rules.NamedArgumentsRule→JetBrains.ReSharper.Plugins.FSharp.Psi.PsiUtil.ITreeNode
- Direction
- JetBrains.ReSharper.Plugins.FSharp.Psi.Features.CodeCompletion.Rules uses JetBrains.ReSharper.Plugins.FSharp.Psi.PsiUtil, so a change to JetBrains.ReSharper.Plugins.FSharp.Psi.PsiUtil can break JetBrains.ReSharper.Plugins.FSharp.Psi.Features.CodeCompletion.Rules, while a change to JetBrains.ReSharper.Plugins.FSharp.Psi.Features.CodeCompletion.Rules can't break JetBrains.ReSharper.Plugins.FSharp.Psi.PsiUtil.
- Position
- Below the diagonal: JetBrains.ReSharper.Plugins.FSharp.Psi.Features.CodeCompletion.Rules uses a module listed above it, which is the healthy direction.
37→13 JetBrains.ReSharper.Plugins.FSharp.Psi.Features.CodeCompletion.Rules uses JetBrains.ReSharper.Plugins.FSharp.Psi.Features.CodeCompletion✕
- Connections
- 1 pair of types, where a type in JetBrains.ReSharper.Plugins.FSharp.Psi.Features.CodeCompletion.Rules uses a type in JetBrains.ReSharper.Plugins.FSharp.Psi.Features.CodeCompletion.
- The types involved
JetBrains.ReSharper.Plugins.FSharp.Psi.Features.CodeCompletion.Rules.EnumCaseLikePatternInfo→JetBrains.ReSharper.Plugins.FSharp.Psi.Features.CodeCompletion.FcsSymbolInfo
- Direction
- JetBrains.ReSharper.Plugins.FSharp.Psi.Features.CodeCompletion.Rules uses JetBrains.ReSharper.Plugins.FSharp.Psi.Features.CodeCompletion, so a change to JetBrains.ReSharper.Plugins.FSharp.Psi.Features.CodeCompletion can break JetBrains.ReSharper.Plugins.FSharp.Psi.Features.CodeCompletion.Rules, while a change to JetBrains.ReSharper.Plugins.FSharp.Psi.Features.CodeCompletion.Rules can't break JetBrains.ReSharper.Plugins.FSharp.Psi.Features.CodeCompletion.
- Position
- Below the diagonal: JetBrains.ReSharper.Plugins.FSharp.Psi.Features.CodeCompletion.Rules uses a module listed above it, which is the healthy direction.
37→14 JetBrains.ReSharper.Plugins.FSharp.Psi.Features.CodeCompletion.Rules uses JetBrains.ReSharper.Plugins.FSharp.Psi.Features.CodeCompletion.FSharpCodeCompletionContext✕
- Connections
- 14 pairs of types, where a type in JetBrains.ReSharper.Plugins.FSharp.Psi.Features.CodeCompletion.Rules uses a type in JetBrains.ReSharper.Plugins.FSharp.Psi.Features.CodeCompletion.FSharpCodeCompletionContext.
- The types involved
JetBrains.ReSharper.Plugins.FSharp.Psi.Features.CodeCompletion.Rules.EnumCaseLikePatternInfo→JetBrains.ReSharper.Plugins.FSharp.Psi.Features.CodeCompletion.FSharpCodeCompletionContext.FSharpCodeCompletionContextJetBrains.ReSharper.Plugins.FSharp.Psi.Features.CodeCompletion.Rules.FSharpImportTypeElementRule→JetBrains.ReSharper.Plugins.FSharp.Psi.Features.CodeCompletion.FSharpCodeCompletionContext.FSharpCodeCompletionContextJetBrains.ReSharper.Plugins.FSharp.Psi.Features.CodeCompletion.Rules.GenerateMatchExprPatternsInfo→JetBrains.ReSharper.Plugins.FSharp.Psi.Features.CodeCompletion.FSharpCodeCompletionContext.FSharpCodeCompletionContextJetBrains.ReSharper.Plugins.FSharp.Psi.Features.CodeCompletion.Rules.GenerateMatchExprPatternsRule→JetBrains.ReSharper.Plugins.FSharp.Psi.Features.CodeCompletion.FSharpCodeCompletionContext.FSharpCodeCompletionContextJetBrains.ReSharper.Plugins.FSharp.Psi.Features.CodeCompletion.Rules.ImplementAllMembersInfo→JetBrains.ReSharper.Plugins.FSharp.Psi.Features.CodeCompletion.FSharpCodeCompletionContext.FSharpCodeCompletionContextJetBrains.ReSharper.Plugins.FSharp.Psi.Features.CodeCompletion.Rules.ImplementInterfaceMemberRule→JetBrains.ReSharper.Plugins.FSharp.Psi.Features.CodeCompletion.FSharpCodeCompletionContext.FSharpCodeCompletionContextJetBrains.ReSharper.Plugins.FSharp.Psi.Features.CodeCompletion.Rules.ImportDeclaredElementInfo→JetBrains.ReSharper.Plugins.FSharp.Psi.Features.CodeCompletion.FSharpCodeCompletionContext.FSharpCodeCompletionContextJetBrains.ReSharper.Plugins.FSharp.Psi.Features.CodeCompletion.Rules.ImportModuleMemberInfo→JetBrains.ReSharper.Plugins.FSharp.Psi.Features.CodeCompletion.FSharpCodeCompletionContext.FSharpCodeCompletionContextJetBrains.ReSharper.Plugins.FSharp.Psi.Features.CodeCompletion.Rules.ImportStaticMemberRule→JetBrains.ReSharper.Plugins.FSharp.Psi.Features.CodeCompletion.FSharpCodeCompletionContext.FSharpCodeCompletionContextJetBrains.ReSharper.Plugins.FSharp.Psi.Features.CodeCompletion.Rules.NameSuggestionFromAsInstanceOfRule→JetBrains.ReSharper.Plugins.FSharp.Psi.Features.CodeCompletion.FSharpCodeCompletionContext.FSharpCodeCompletionContextJetBrains.ReSharper.Plugins.FSharp.Psi.Features.CodeCompletion.Rules.NameSuggestionFromTypeRule→JetBrains.ReSharper.Plugins.FSharp.Psi.Features.CodeCompletion.FSharpCodeCompletionContext.FSharpCodeCompletionContextJetBrains.ReSharper.Plugins.FSharp.Psi.Features.CodeCompletion.Rules.NamedArgumentsRule→JetBrains.ReSharper.Plugins.FSharp.Psi.Features.CodeCompletion.FSharpCodeCompletionContext.FSharpCodeCompletionContextJetBrains.ReSharper.Plugins.FSharp.Psi.Features.CodeCompletion.Rules.RecordFieldRule→JetBrains.ReSharper.Plugins.FSharp.Psi.Features.CodeCompletion.FSharpCodeCompletionContext.FSharpCodeCompletionContextJetBrains.ReSharper.Plugins.FSharp.Psi.Features.CodeCompletion.Rules.UnionCaseFieldsPatternRule→JetBrains.ReSharper.Plugins.FSharp.Psi.Features.CodeCompletion.FSharpCodeCompletionContext.FSharpCodeCompletionContext
- Direction
- JetBrains.ReSharper.Plugins.FSharp.Psi.Features.CodeCompletion.Rules uses JetBrains.ReSharper.Plugins.FSharp.Psi.Features.CodeCompletion.FSharpCodeCompletionContext, so a change to JetBrains.ReSharper.Plugins.FSharp.Psi.Features.CodeCompletion.FSharpCodeCompletionContext can break JetBrains.ReSharper.Plugins.FSharp.Psi.Features.CodeCompletion.Rules, while a change to JetBrains.ReSharper.Plugins.FSharp.Psi.Features.CodeCompletion.Rules can't break JetBrains.ReSharper.Plugins.FSharp.Psi.Features.CodeCompletion.FSharpCodeCompletionContext.
- Position
- Below the diagonal: JetBrains.ReSharper.Plugins.FSharp.Psi.Features.CodeCompletion.Rules uses a module listed above it, which is the healthy direction.
37→24 JetBrains.ReSharper.Plugins.FSharp.Psi.Features.CodeCompletion.Rules uses JetBrains.ReSharper.Plugins.FSharp.Psi.Services.Util.FSharpCompletionUtil✕
- Connections
- 2 pairs of types, where a type in JetBrains.ReSharper.Plugins.FSharp.Psi.Features.CodeCompletion.Rules uses a type in JetBrains.ReSharper.Plugins.FSharp.Psi.Services.Util.FSharpCompletionUtil.
- The types involved
JetBrains.ReSharper.Plugins.FSharp.Psi.Features.CodeCompletion.Rules.FSharpRelevanceRule→JetBrains.ReSharper.Plugins.FSharp.Psi.Services.Util.FSharpCompletionUtil.ILookupItemJetBrains.ReSharper.Plugins.FSharp.Psi.Features.CodeCompletion.Rules.NamedArgumentsRule→JetBrains.ReSharper.Plugins.FSharp.Psi.Services.Util.FSharpCompletionUtil.ILookupItem
- Direction
- JetBrains.ReSharper.Plugins.FSharp.Psi.Features.CodeCompletion.Rules uses JetBrains.ReSharper.Plugins.FSharp.Psi.Services.Util.FSharpCompletionUtil, so a change to JetBrains.ReSharper.Plugins.FSharp.Psi.Services.Util.FSharpCompletionUtil can break JetBrains.ReSharper.Plugins.FSharp.Psi.Features.CodeCompletion.Rules, while a change to JetBrains.ReSharper.Plugins.FSharp.Psi.Features.CodeCompletion.Rules can't break JetBrains.ReSharper.Plugins.FSharp.Psi.Services.Util.FSharpCompletionUtil.
- Position
- Below the diagonal: JetBrains.ReSharper.Plugins.FSharp.Psi.Features.CodeCompletion.Rules uses a module listed above it, which is the healthy direction.
37→25 JetBrains.ReSharper.Plugins.FSharp.Psi.Features.CodeCompletion.Rules uses JetBrains.ReSharper.Plugins.FSharp.Util.FSharpSymbolUtil✕
- Connections
- 1 pair of types, where a type in JetBrains.ReSharper.Plugins.FSharp.Psi.Features.CodeCompletion.Rules uses a type in JetBrains.ReSharper.Plugins.FSharp.Util.FSharpSymbolUtil.
- The types involved
JetBrains.ReSharper.Plugins.FSharp.Psi.Features.CodeCompletion.Rules.EnumCaseLikePatternInfo→JetBrains.ReSharper.Plugins.FSharp.Util.FSharpSymbolUtil.FcsEntityInstance
- Direction
- JetBrains.ReSharper.Plugins.FSharp.Psi.Features.CodeCompletion.Rules uses JetBrains.ReSharper.Plugins.FSharp.Util.FSharpSymbolUtil, so a change to JetBrains.ReSharper.Plugins.FSharp.Util.FSharpSymbolUtil can break JetBrains.ReSharper.Plugins.FSharp.Psi.Features.CodeCompletion.Rules, while a change to JetBrains.ReSharper.Plugins.FSharp.Psi.Features.CodeCompletion.Rules can't break JetBrains.ReSharper.Plugins.FSharp.Util.FSharpSymbolUtil.
- Position
- Below the diagonal: JetBrains.ReSharper.Plugins.FSharp.Psi.Features.CodeCompletion.Rules uses a module listed above it, which is the healthy direction.
37→34 JetBrains.ReSharper.Plugins.FSharp.Psi.Features.CodeCompletion.Rules uses JetBrains.ReSharper.Plugins.FSharp.ProjectModel✕
- Connections
- 1 pair of types, where a type in JetBrains.ReSharper.Plugins.FSharp.Psi.Features.CodeCompletion.Rules uses a type in JetBrains.ReSharper.Plugins.FSharp.ProjectModel.
- The types involved
JetBrains.ReSharper.Plugins.FSharp.Psi.Features.CodeCompletion.Rules.FSharpKeywordsRule→JetBrains.ReSharper.Plugins.FSharp.ProjectModel.FSharpLanguageLevel
- Direction
- JetBrains.ReSharper.Plugins.FSharp.Psi.Features.CodeCompletion.Rules uses JetBrains.ReSharper.Plugins.FSharp.ProjectModel, so a change to JetBrains.ReSharper.Plugins.FSharp.ProjectModel can break JetBrains.ReSharper.Plugins.FSharp.Psi.Features.CodeCompletion.Rules, while a change to JetBrains.ReSharper.Plugins.FSharp.Psi.Features.CodeCompletion.Rules can't break JetBrains.ReSharper.Plugins.FSharp.ProjectModel.
- Position
- Below the diagonal: JetBrains.ReSharper.Plugins.FSharp.Psi.Features.CodeCompletion.Rules uses a module listed above it, which is the healthy direction.
38→10 JetBrains.ReSharper.Plugins.FSharp.Psi.Features.Fsi uses JetBrains.ReSharper.Plugins.FSharp.Util.CommonUtil✕
- Connections
- 2 pairs of types, where a type in JetBrains.ReSharper.Plugins.FSharp.Psi.Features.Fsi uses a type in JetBrains.ReSharper.Plugins.FSharp.Util.CommonUtil.
- The types involved
JetBrains.ReSharper.Plugins.FSharp.Psi.Features.Fsi.FsiHost→JetBrains.ReSharper.Plugins.FSharp.Util.CommonUtil.LifetimeJetBrains.ReSharper.Plugins.FSharp.Psi.Features.Fsi.FsiOptionsPage→JetBrains.ReSharper.Plugins.FSharp.Util.CommonUtil.Lifetime
- Direction
- JetBrains.ReSharper.Plugins.FSharp.Psi.Features.Fsi uses JetBrains.ReSharper.Plugins.FSharp.Util.CommonUtil, so a change to JetBrains.ReSharper.Plugins.FSharp.Util.CommonUtil can break JetBrains.ReSharper.Plugins.FSharp.Psi.Features.Fsi, while a change to JetBrains.ReSharper.Plugins.FSharp.Psi.Features.Fsi can't break JetBrains.ReSharper.Plugins.FSharp.Util.CommonUtil.
- Position
- Below the diagonal: JetBrains.ReSharper.Plugins.FSharp.Psi.Features.Fsi uses a module listed above it, which is the healthy direction.
38→24 JetBrains.ReSharper.Plugins.FSharp.Psi.Features.Fsi uses JetBrains.ReSharper.Plugins.FSharp.Psi.Services.Util.FSharpCompletionUtil✕
- Connections
- 1 pair of types, where a type in JetBrains.ReSharper.Plugins.FSharp.Psi.Features.Fsi uses a type in JetBrains.ReSharper.Plugins.FSharp.Psi.Services.Util.FSharpCompletionUtil.
- The types involved
JetBrains.ReSharper.Plugins.FSharp.Psi.Features.Fsi.FsiHost→JetBrains.ReSharper.Plugins.FSharp.Psi.Services.Util.FSharpCompletionUtil.ISolution
- Direction
- JetBrains.ReSharper.Plugins.FSharp.Psi.Features.Fsi uses JetBrains.ReSharper.Plugins.FSharp.Psi.Services.Util.FSharpCompletionUtil, so a change to JetBrains.ReSharper.Plugins.FSharp.Psi.Services.Util.FSharpCompletionUtil can break JetBrains.ReSharper.Plugins.FSharp.Psi.Features.Fsi, while a change to JetBrains.ReSharper.Plugins.FSharp.Psi.Features.Fsi can't break JetBrains.ReSharper.Plugins.FSharp.Psi.Services.Util.FSharpCompletionUtil.
- Position
- Below the diagonal: JetBrains.ReSharper.Plugins.FSharp.Psi.Features.Fsi uses a module listed above it, which is the healthy direction.
38→30 JetBrains.ReSharper.Plugins.FSharp.Psi.Features.Fsi uses JetBrains.ReSharper.Plugins.FSharp.Settings✕
- Connections
- 2 pairs of types, where a type in JetBrains.ReSharper.Plugins.FSharp.Psi.Features.Fsi uses a type in JetBrains.ReSharper.Plugins.FSharp.Settings.
- The types involved
JetBrains.ReSharper.Plugins.FSharp.Psi.Features.Fsi.FsiOptionsPage→JetBrains.ReSharper.Plugins.FSharp.Settings.FSharpOptionsPageBaseJetBrains.ReSharper.Plugins.FSharp.Psi.Features.Fsi.FsiOptionsProvider→JetBrains.ReSharper.Plugins.FSharp.Settings.FSharpSettingsProviderBase
- Direction
- JetBrains.ReSharper.Plugins.FSharp.Psi.Features.Fsi uses JetBrains.ReSharper.Plugins.FSharp.Settings, so a change to JetBrains.ReSharper.Plugins.FSharp.Settings can break JetBrains.ReSharper.Plugins.FSharp.Psi.Features.Fsi, while a change to JetBrains.ReSharper.Plugins.FSharp.Psi.Features.Fsi can't break JetBrains.ReSharper.Plugins.FSharp.Settings.
- Position
- Below the diagonal: JetBrains.ReSharper.Plugins.FSharp.Psi.Features.Fsi uses a module listed above it, which is the healthy direction.
38→34 JetBrains.ReSharper.Plugins.FSharp.Psi.Features.Fsi uses JetBrains.ReSharper.Plugins.FSharp.ProjectModel✕
- Connections
- 1 pair of types, where a type in JetBrains.ReSharper.Plugins.FSharp.Psi.Features.Fsi uses a type in JetBrains.ReSharper.Plugins.FSharp.ProjectModel.
- The types involved
JetBrains.ReSharper.Plugins.FSharp.Psi.Features.Fsi.FsiOptions→JetBrains.ReSharper.Plugins.FSharp.ProjectModel.FSharpLanguageVersion
- Direction
- JetBrains.ReSharper.Plugins.FSharp.Psi.Features.Fsi uses JetBrains.ReSharper.Plugins.FSharp.ProjectModel, so a change to JetBrains.ReSharper.Plugins.FSharp.ProjectModel can break JetBrains.ReSharper.Plugins.FSharp.Psi.Features.Fsi, while a change to JetBrains.ReSharper.Plugins.FSharp.Psi.Features.Fsi can't break JetBrains.ReSharper.Plugins.FSharp.ProjectModel.
- Position
- Below the diagonal: JetBrains.ReSharper.Plugins.FSharp.Psi.Features.Fsi uses a module listed above it, which is the healthy direction.
39→4 JetBrains.ReSharper.Plugins.FSharp.Psi.Daemon.Analyzers uses JetBrains.ReSharper.Plugins.FSharp.Psi.Daemon.Analyzers.Util✕
- Connections
- 3 pairs of types, where a type in JetBrains.ReSharper.Plugins.FSharp.Psi.Daemon.Analyzers uses a type in JetBrains.ReSharper.Plugins.FSharp.Psi.Daemon.Analyzers.Util.
- The types involved
JetBrains.ReSharper.Plugins.FSharp.Psi.Daemon.Analyzers.InterpolatedStringCandidateAnalyzer→JetBrains.ReSharper.Plugins.FSharp.Psi.Daemon.Analyzers.Util.ElementProblemAnalyzerDataJetBrains.ReSharper.Plugins.FSharp.Psi.Daemon.Analyzers.RedundantParenExprAnalyzer→JetBrains.ReSharper.Plugins.FSharp.Psi.Daemon.Analyzers.Util.ElementProblemAnalyzerDataJetBrains.ReSharper.Plugins.FSharp.Psi.Daemon.Analyzers.XmlDocBlockAnalyzer→JetBrains.ReSharper.Plugins.FSharp.Psi.Daemon.Analyzers.Util.ElementProblemAnalyzerData
- Direction
- JetBrains.ReSharper.Plugins.FSharp.Psi.Daemon.Analyzers uses JetBrains.ReSharper.Plugins.FSharp.Psi.Daemon.Analyzers.Util, so a change to JetBrains.ReSharper.Plugins.FSharp.Psi.Daemon.Analyzers.Util can break JetBrains.ReSharper.Plugins.FSharp.Psi.Daemon.Analyzers, while a change to JetBrains.ReSharper.Plugins.FSharp.Psi.Daemon.Analyzers can't break JetBrains.ReSharper.Plugins.FSharp.Psi.Daemon.Analyzers.Util.
- Position
- Below the diagonal: JetBrains.ReSharper.Plugins.FSharp.Psi.Daemon.Analyzers uses a module listed above it, which is the healthy direction.
39→9 JetBrains.ReSharper.Plugins.FSharp.Psi.Daemon.Analyzers uses JetBrains.ReSharper.Plugins.FSharp.Psi.PsiUtil✕
- Connections
- 3 pairs of types, where a type in JetBrains.ReSharper.Plugins.FSharp.Psi.Daemon.Analyzers uses a type in JetBrains.ReSharper.Plugins.FSharp.Psi.PsiUtil.
- The types involved
JetBrains.ReSharper.Plugins.FSharp.Psi.Daemon.Analyzers.FSharpRecursionGutterHighlighting→JetBrains.ReSharper.Plugins.FSharp.Psi.PsiUtil.ITreeNodeJetBrains.ReSharper.Plugins.FSharp.Psi.Daemon.Analyzers.LambdaAnalyzer→JetBrains.ReSharper.Plugins.FSharp.Psi.PsiUtil.ITreeNodeJetBrains.ReSharper.Plugins.FSharp.Psi.Daemon.Analyzers.XmlDocBlockAnalyzer→JetBrains.ReSharper.Plugins.FSharp.Psi.PsiUtil.ITreeNode
- Direction
- JetBrains.ReSharper.Plugins.FSharp.Psi.Daemon.Analyzers uses JetBrains.ReSharper.Plugins.FSharp.Psi.PsiUtil, so a change to JetBrains.ReSharper.Plugins.FSharp.Psi.PsiUtil can break JetBrains.ReSharper.Plugins.FSharp.Psi.Daemon.Analyzers, while a change to JetBrains.ReSharper.Plugins.FSharp.Psi.Daemon.Analyzers can't break JetBrains.ReSharper.Plugins.FSharp.Psi.PsiUtil.
- Position
- Below the diagonal: JetBrains.ReSharper.Plugins.FSharp.Psi.Daemon.Analyzers uses a module listed above it, which is the healthy direction.
39→36 JetBrains.ReSharper.Plugins.FSharp.Psi.Daemon.Analyzers uses JetBrains.ReSharper.Plugins.FSharp.Checker✕
- Connections
- 1 pair of types, where a type in JetBrains.ReSharper.Plugins.FSharp.Psi.Daemon.Analyzers uses a type in JetBrains.ReSharper.Plugins.FSharp.Checker.
- The types involved
JetBrains.ReSharper.Plugins.FSharp.Psi.Daemon.Analyzers.InterpolatedStringCandidateAnalyzer→JetBrains.ReSharper.Plugins.FSharp.Checker.FSharpParseAndCheckResults
- Direction
- JetBrains.ReSharper.Plugins.FSharp.Psi.Daemon.Analyzers uses JetBrains.ReSharper.Plugins.FSharp.Checker, so a change to JetBrains.ReSharper.Plugins.FSharp.Checker can break JetBrains.ReSharper.Plugins.FSharp.Psi.Daemon.Analyzers, while a change to JetBrains.ReSharper.Plugins.FSharp.Psi.Daemon.Analyzers can't break JetBrains.ReSharper.Plugins.FSharp.Checker.
- Position
- Below the diagonal: JetBrains.ReSharper.Plugins.FSharp.Psi.Daemon.Analyzers uses a module listed above it, which is the healthy direction.
40→2 JetBrains.ReSharper.Plugins.FSharp.Shim.AssemblyReader uses FSharpFileSystemPathExtensions✕
- Connections
- 3 pairs of types, where a type in JetBrains.ReSharper.Plugins.FSharp.Shim.AssemblyReader uses a type in FSharpFileSystemPathExtensions.
- The types involved
JetBrains.ReSharper.Plugins.FSharp.Shim.AssemblyReader.AssemblyReaderShim→FSharpFileSystemPathExtensions.VirtualFileSystemPathJetBrains.ReSharper.Plugins.FSharp.Shim.AssemblyReader.IFcsAssemblyReaderShim→FSharpFileSystemPathExtensions.VirtualFileSystemPathJetBrains.ReSharper.Plugins.FSharp.Shim.AssemblyReader.IProjectFcsModuleReader→FSharpFileSystemPathExtensions.VirtualFileSystemPath
- Direction
- JetBrains.ReSharper.Plugins.FSharp.Shim.AssemblyReader uses FSharpFileSystemPathExtensions, so a change to FSharpFileSystemPathExtensions can break JetBrains.ReSharper.Plugins.FSharp.Shim.AssemblyReader, while a change to JetBrains.ReSharper.Plugins.FSharp.Shim.AssemblyReader can't break FSharpFileSystemPathExtensions.
- Position
- Below the diagonal: JetBrains.ReSharper.Plugins.FSharp.Shim.AssemblyReader uses a module listed above it, which is the healthy direction.
40→8 JetBrains.ReSharper.Plugins.FSharp.Shim.AssemblyReader uses JetBrains.ReSharper.Plugins.FSharp.ProjectModel.Util✕
- Connections
- 1 pair of types, where a type in JetBrains.ReSharper.Plugins.FSharp.Shim.AssemblyReader uses a type in JetBrains.ReSharper.Plugins.FSharp.ProjectModel.Util.
- The types involved
JetBrains.ReSharper.Plugins.FSharp.Shim.AssemblyReader.ProjectFcsModuleReader→JetBrains.ReSharper.Plugins.FSharp.ProjectModel.Util.IProject
- Direction
- JetBrains.ReSharper.Plugins.FSharp.Shim.AssemblyReader uses JetBrains.ReSharper.Plugins.FSharp.ProjectModel.Util, so a change to JetBrains.ReSharper.Plugins.FSharp.ProjectModel.Util can break JetBrains.ReSharper.Plugins.FSharp.Shim.AssemblyReader, while a change to JetBrains.ReSharper.Plugins.FSharp.Shim.AssemblyReader can't break JetBrains.ReSharper.Plugins.FSharp.ProjectModel.Util.
- Position
- Below the diagonal: JetBrains.ReSharper.Plugins.FSharp.Shim.AssemblyReader uses a module listed above it, which is the healthy direction.
40→10 JetBrains.ReSharper.Plugins.FSharp.Shim.AssemblyReader uses JetBrains.ReSharper.Plugins.FSharp.Util.CommonUtil✕
- Connections
- 3 pairs of types, where a type in JetBrains.ReSharper.Plugins.FSharp.Shim.AssemblyReader uses a type in JetBrains.ReSharper.Plugins.FSharp.Util.CommonUtil.
- The types involved
JetBrains.ReSharper.Plugins.FSharp.Shim.AssemblyReader.AssemblyReaderShim→JetBrains.ReSharper.Plugins.FSharp.Util.CommonUtil.LifetimeJetBrains.ReSharper.Plugins.FSharp.Shim.AssemblyReader.FcsModuleReaderCommonCache→JetBrains.ReSharper.Plugins.FSharp.Util.CommonUtil.LifetimeJetBrains.ReSharper.Plugins.FSharp.Shim.AssemblyReader.ProjectFcsModuleReader→JetBrains.ReSharper.Plugins.FSharp.Util.CommonUtil.IDictionary
- Direction
- JetBrains.ReSharper.Plugins.FSharp.Shim.AssemblyReader uses JetBrains.ReSharper.Plugins.FSharp.Util.CommonUtil, so a change to JetBrains.ReSharper.Plugins.FSharp.Util.CommonUtil can break JetBrains.ReSharper.Plugins.FSharp.Shim.AssemblyReader, while a change to JetBrains.ReSharper.Plugins.FSharp.Shim.AssemblyReader can't break JetBrains.ReSharper.Plugins.FSharp.Util.CommonUtil.
- Position
- Below the diagonal: JetBrains.ReSharper.Plugins.FSharp.Shim.AssemblyReader uses a module listed above it, which is the healthy direction.
40→24 JetBrains.ReSharper.Plugins.FSharp.Shim.AssemblyReader uses JetBrains.ReSharper.Plugins.FSharp.Psi.Services.Util.FSharpCompletionUtil✕
- Connections
- 1 pair of types, where a type in JetBrains.ReSharper.Plugins.FSharp.Shim.AssemblyReader uses a type in JetBrains.ReSharper.Plugins.FSharp.Psi.Services.Util.FSharpCompletionUtil.
- The types involved
JetBrains.ReSharper.Plugins.FSharp.Shim.AssemblyReader.AssemblyReaderShim→JetBrains.ReSharper.Plugins.FSharp.Psi.Services.Util.FSharpCompletionUtil.ISolution
- Direction
- JetBrains.ReSharper.Plugins.FSharp.Shim.AssemblyReader uses JetBrains.ReSharper.Plugins.FSharp.Psi.Services.Util.FSharpCompletionUtil, so a change to JetBrains.ReSharper.Plugins.FSharp.Psi.Services.Util.FSharpCompletionUtil can break JetBrains.ReSharper.Plugins.FSharp.Shim.AssemblyReader, while a change to JetBrains.ReSharper.Plugins.FSharp.Shim.AssemblyReader can't break JetBrains.ReSharper.Plugins.FSharp.Psi.Services.Util.FSharpCompletionUtil.
- Position
- Below the diagonal: JetBrains.ReSharper.Plugins.FSharp.Shim.AssemblyReader uses a module listed above it, which is the healthy direction.
40→30 JetBrains.ReSharper.Plugins.FSharp.Shim.AssemblyReader uses JetBrains.ReSharper.Plugins.FSharp.Settings✕
- Connections
- 1 pair of types, where a type in JetBrains.ReSharper.Plugins.FSharp.Shim.AssemblyReader uses a type in JetBrains.ReSharper.Plugins.FSharp.Settings.
- The types involved
JetBrains.ReSharper.Plugins.FSharp.Shim.AssemblyReader.AssemblyReaderShim→JetBrains.ReSharper.Plugins.FSharp.Settings.FSharpOptionsProvider
- Direction
- JetBrains.ReSharper.Plugins.FSharp.Shim.AssemblyReader uses JetBrains.ReSharper.Plugins.FSharp.Settings, so a change to JetBrains.ReSharper.Plugins.FSharp.Settings can break JetBrains.ReSharper.Plugins.FSharp.Shim.AssemblyReader, while a change to JetBrains.ReSharper.Plugins.FSharp.Shim.AssemblyReader can't break JetBrains.ReSharper.Plugins.FSharp.Settings.
- Position
- Below the diagonal: JetBrains.ReSharper.Plugins.FSharp.Shim.AssemblyReader uses a module listed above it, which is the healthy direction.
40→31 JetBrains.ReSharper.Plugins.FSharp.Shim.AssemblyReader uses JetBrains.ReSharper.Plugins.FSharp.Shim.FileSystem✕
- Connections
- 1 pair of types, where a type in JetBrains.ReSharper.Plugins.FSharp.Shim.AssemblyReader uses a type in JetBrains.ReSharper.Plugins.FSharp.Shim.FileSystem.
- The types involved
JetBrains.ReSharper.Plugins.FSharp.Shim.AssemblyReader.AssemblyReaderShim→JetBrains.ReSharper.Plugins.FSharp.Shim.FileSystem.AssemblyInfoShim
- Direction
- JetBrains.ReSharper.Plugins.FSharp.Shim.AssemblyReader uses JetBrains.ReSharper.Plugins.FSharp.Shim.FileSystem, so a change to JetBrains.ReSharper.Plugins.FSharp.Shim.FileSystem can break JetBrains.ReSharper.Plugins.FSharp.Shim.AssemblyReader, while a change to JetBrains.ReSharper.Plugins.FSharp.Shim.AssemblyReader can't break JetBrains.ReSharper.Plugins.FSharp.Shim.FileSystem.
- Position
- Below the diagonal: JetBrains.ReSharper.Plugins.FSharp.Shim.AssemblyReader uses a module listed above it, which is the healthy direction.
40→36 JetBrains.ReSharper.Plugins.FSharp.Shim.AssemblyReader uses JetBrains.ReSharper.Plugins.FSharp.Checker✕
- Connections
- 1 pair of types, where a type in JetBrains.ReSharper.Plugins.FSharp.Shim.AssemblyReader uses a type in JetBrains.ReSharper.Plugins.FSharp.Checker.
- The types involved
JetBrains.ReSharper.Plugins.FSharp.Shim.AssemblyReader.AssemblyReaderShim→JetBrains.ReSharper.Plugins.FSharp.Checker.FcsProjectKey
- Direction
- JetBrains.ReSharper.Plugins.FSharp.Shim.AssemblyReader uses JetBrains.ReSharper.Plugins.FSharp.Checker, so a change to JetBrains.ReSharper.Plugins.FSharp.Checker can break JetBrains.ReSharper.Plugins.FSharp.Shim.AssemblyReader, while a change to JetBrains.ReSharper.Plugins.FSharp.Shim.AssemblyReader can't break JetBrains.ReSharper.Plugins.FSharp.Checker.
- Position
- Below the diagonal: JetBrains.ReSharper.Plugins.FSharp.Shim.AssemblyReader 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 |
|---|---|---|
| A07:2025 — Authentication Failures | 12 | High / Critical |
| A05:2025 — Injection | 9 | High / Critical |
Roadmap
Top priorities: Resolve the 11 NoWarnInCsproj finding(s) in Explicit Debt — start with FSharp.Fantomas.Host.csproj (2), FSharp.TypeProviders.Host.NetCore.csproj (2), FSharp.Debugger.csproj; Enable <Nullable>enable</Nullable> across all projects and resolve warnings rather than suppressing with `!`; Resolve the 6 Leaked secret finding(s) in Secret Scanning — start with REDACTED (5), REDACTED.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 11 NoWarnInCsproj finding(s) in Explicit Debt — start with FSharp.Fantomas.Host.csproj (2), FSharp.TypeProviders.Host.NetCore.csproj (2), FSharp.Debugger.csproj. | +12.3 pts | Medium | Explicit Debt |
| Resolve the 6 Leaked secret finding(s) in Secret Scanning — start with REDACTED (5), REDACTED. | +4.4 pts | Low | Secret Scanning |
| Enable <Nullable>enable</Nullable> across all projects and resolve warnings rather than suppressing with `!`. | +8.5 pts | Medium | Nullable reference types |
| Resolve the 1 FixmeComment finding(s) in Explicit Debt — start with ExemptFromZoningValidation.cs. | +3.9 pts | Low | Explicit Debt |
| Resolve the 1 No ADRs found finding(s) in ADR Quality — start with FSharp.Fantomas.Host.csproj. | +3.3 pts | Low | ADR Quality |
| Resolve the 6 High secret finding(s) in Secrets (history) — start with REDACTED (5), REDACTED. | +3.2 pts | Low | Secrets (history) |
| Resolve the 10 End-of-life runtime finding(s) in Platform End-of-Life — start with CoreConsoleApp.fsproj (2), ClassLibrary1.fsproj, TypeProviderLibrary.fsproj. | +3.7 pts | Medium | Platform End-of-Life |
| Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED, REDACTED. | +1.7 pts | Low | Static Analysis (SAST) |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 1.3 | Slop | Static Analysis (SAST): High: REDACTED |
| ReSharper.FSharp/src/FSharp.TypeProviders.Host/FSharp.TypeProviders.Host.NetCore/FSharp.TypeProviders.Host.NetCore.csproj | 4.3 | Mixed | Explicit Debt: NoWarnInCsproj |
| REDACTED | 4.4 | Mixed | Secret Scanning: Leaked secret: REDACTED |
| REDACTED | 4.4 | Mixed | Secret Scanning: Leaked secret: REDACTED |
| REDACTED | 4.4 | Mixed | Secret Scanning: Leaked secret: REDACTED |
| REDACTED | 4.4 | Mixed | Secret Scanning: Leaked secret: REDACTED |
| REDACTED | 4.4 | Mixed | Secret Scanning: Leaked secret: REDACTED |
| REDACTED | 4.4 | Mixed | Secret Scanning: Leaked secret: REDACTED |
| ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/PostfixTemplates/ForPostfixTemplate.fs | 5.9 | Mixed | Code Duplication: Duplicated block (11 lines × 2) |
| ReSharper.FSharp/src/FSharp.Fantomas.Host/FSharp.Fantomas.Host.csproj | 5.9 | Mixed | Explicit Debt: NoWarnInCsproj |
| ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/Parsing/FSharpImplTreeBuilder.fs | 7.1 | Mixed | God Classes: FileTooLong: Parsing/FSharpImplTreeBuilder.fs |
| REDACTED | 7.2 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 7.2 | Mixed | Static Analysis (SAST): High: REDACTED |
| ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/FSharpTypingAssist.fs | 7.4 | Mixed | God Classes: FileTooLong: src/FSharpTypingAssist.fs |
| ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/CodeCompletion/Rules/GenerateLambdaRule.fs | 7.4 | Mixed | Code Duplication: Members sharing a duplicated core (4 members, 50+ identical tokens) |
| ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/CodeCompletion/Rules/ImportModuleMemberRule.fs | 7.4 | Mixed | Code Duplication: Duplicated block (12–13 lines × 2) |
| ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/CodeCompletion/Rules/GenerateMatchExprPatternsRule.fs | 7.4 | Mixed | Code Duplication: Duplicated block (11 lines × 2) |
| ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/CodeCompletion/Rules/ImportExtensionMemberRule.fs | 7.4 | Mixed | Code Duplication: Duplicated block (6 lines × 2) |
| ReSharper.FSharp/src/FSharp.Debugger/FSharp.Debugger.csproj | 7.6 | Mixed | Explicit Debt: NoWarnInCsproj |
| ReSharper.FSharp/src/FSharp/FSharp.Fantomas.Protocol/FSharp.Fantomas.Protocol.csproj | 7.6 | Mixed | Explicit Debt: NoWarnInCsproj |
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 31 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.8, the weighted average across measured dimensions.
What we checked — 31 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, 170 of 181 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
- D1 Cyclomatic Complexity — 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. Most of this repository's production source (.cs, .fs) had no cyclomatic complexity computed for it: no method bodies were exposed for those file kinds by any language model this pass could load.
- D2 Cognitive Complexity — 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. Most of this repository's production source (.cs, .fs) had no cognitive complexity computed for it: no method bodies were exposed for those file kinds by any language model this pass could load.
- D4 Code Duplication — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. The 49 duplicated block group(s) on this row were found in the languages this pass could tokenize, and they do NOT cover all of this repository's production source: .cs (28,469 lines, 40% of production source) went unread, because no language model this pass could load exposed a clone-unit token stream for those file kinds. Duplication in that source is UNMEASURED — its absence from the count above is a gap in this analyzer's language coverage, not a finding that the code is free of duplication.
- D6 Cohesion (LCOM4) — 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. 417 of 417 class(es) with two or more methods were found, but the language model this pass loaded exposed none of their method bodies, so which method touches which field could not be seen.
- D8 Code Coverage — 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. Coverage NOT MEASURED: `--collect:"XPlat Code Coverage"` names a data collector that ships in the `coverlet.collector` package, and this repository wires up none — no test project references it and no runsettings declares one. The absence of coverage here is therefore not evidence about the suite or about our analyzer environment: without a collector, `--collect` produces nothing even from a suite that builds and passes. Add a `coverlet.collector` PackageReference to the test project(s) (or commit the Cobertura/OpenCover/lcov report your CI produces) and real coverage will be measured. It is excluded from the score rather than counted as a near-zero defect. You can widen what we reach: add the `coverlet.collector` package to the test projects to enable coverage (or commit the Cobertura/OpenCover/lcov report your CI produces).
- D11 Test Reliability — 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. Test reliability NOT MEASURED: the analyzer environment could not build/run the test suite (a target framework / SDK band or targeting pack the analyzer image doesn't carry), so no test ever ran. This is OUR limitation, not a defect in the repo — it is excluded from the score. We track the analyzer-image gap so it can be closed.
- D12 Dependency Hygiene — 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. `dotnet list package` did not return usable output (restore or query failed); no outdated/vulnerable/deprecated data to assess. The tool said: `dotnet list package` exited 1 with no output.
- D14 License Compliance — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This repository declares a Gradle build (build.gradle/build.gradle.kts), but the licence verdict published here was taken over its NuGet package dependencies. Nothing was read about its Gradle dependencies' licensing in either direction, and a clean score on this card must not be read as covering them.
- D15 Churn × Complexity Hotspots — 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. A hotspot is churn × complexity. Churn was measured (145256 line(s) across the 90-day window), but no complexity could be computed for .cs, .fs, which is most of this repository's production code — so every churned file would score as complexity 0 and the hotspot list would be empty no matter how tangled the code is. Not scored — this is a gap in the analysis run, not a finding about this repository.
- D17 Explicit Debt — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. The C# workspace loaded this repository's projects but reported a load failure, and the dead-code reference search is unreliable over a graph that did not load cleanly, so it was skipped. The other debt markers on this row were read; dead symbols were not, and their absence from the score is not a finding that the code has none. First load diagnostic: Failure: Msbuild failed when processing the file 'ReSharper.FSharp/src/FSharp/FSharp.Psi/FSharp.Psi.csproj' with message: The SDK 'JetBrains.Toolset.MainSolution.Sdk/20200625.1.1.2' specified could not be found. ReSharper.FSharp/src/FSharp/FSharp.Psi/FSharp.Psi.csproj.
- D17 Explicit Debt — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. The 12 deducted marker(s) and the 5.1/KLoC density on this row were taken over this repository's .NET projects ALONE: .fs (38,098 lines, 53% of production source), .cs (28,469 lines, 40% of production source) went unread, because every marker collector on this path is reached through a C# workspace. D17's marker collectors need a compiler we do not have for that language, so none of its nine marker kinds were read there. The debt in that source is UNMEASURED — its absence from the score above is a gap in this analyzer's language coverage, not a finding that the code carries none.
- D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
- D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This kind did not reach the 95 % precision gate in three adjudicated runs (docs/plans/deterministic-engine/adjudication/D19-sample3-v3.md), so by the pre-registered fallback it publishes no row until a re-measurement shows it does. The candidates are counted here, not reported as findings, and the score does not include them.
- D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D21's deterministic naming rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. Until then its declarations carry no naming verdict this run — this says nothing about whether its names are consistent.
- D22 Internal API Consistency — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. The loaded project set declares no packable project and no `.Contracts` project, so there is no intentionally-exposed surface for API consistency to be judged over.
- D23 Boundary Type-Coupling — 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. Large codebase (71,226 production LoC in the .NET projects) with no declared bounded contexts — cross-boundary type coupling is unassessed Bounded contexts cannot be inferred from a codebase that is not physically organised by them (D-321), so with none declared there are no boundaries for the coupling pass to measure across. You can widen what we reach: name this codebase's bounded contexts (≥2 module groups, e.g. per subsystem) so cross-boundary type coupling can 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 — 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.
- D32 Data Compliance (PII/GDPR) — 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. `ReSharper.FSharp/src/FSharp.Debugger/src/FSharpAsyncStepper.cs`, `ReSharper.FSharp/src/FSharp.Debugger/src/FSharpSequencePointInvokedMethodsProvider.cs`, `ReSharper.FSharp/src/FSharp.Debugger/src/FSharpUnitReturnValueFilter.cs`, `ReSharper.FSharp/src/FSharp/FSharp.ProjectModelBase/src/FSharpAsyncUtil.cs`, `ReSharper.FSharp/src/FSharp/FSharp.ProjectModelBase/src/FSharpZones.cs`, … (+94 more) produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
- D43 Malicious Dependencies — 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. Osv: osv-scanner exited 127 with no findings — dependency CVEs were not measured. 'osv-scanner' exited 127 and produced no findings, and that exit code has no documented repo-side meaning — so this run measured nothing, and nothing here is a statement about the repository.
- 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's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
- AXB1 Runtime evidence locked — no reproducible boot — 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. Subject: 1 markup document(s) — HTML, Razor, JSX, Vue, Svelte or server templates. The Runtime Evidence tier boots an app only via docker-compose, an Aspire AppHost, a Dockerfile, an npm dev script, a web service's own toolchain entry point (cargo, go, dotnet, Python, Spring Boot), or an Android app's own Gradle wrapper (run on an emulator); an Apple or Flutter app needs a host it lacks. None applied, so no live runtime a11y/egress/header evidence was collected. You can widen what we reach: add a docker-compose.yml (or an Aspire AppHost) that brings the app up with its dependencies. We then boot it in an isolated sandbox and gathers real runtime evidence — you change nothing in your pipeline (no CI step, no SDK).
- 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's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
- 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.
- 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's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
- X23 Unguarded diagnostic materialisation — 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's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
- X28 Index access outside its own emptiness 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's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
- Package restore incomplete — third-party types were unresolved in part of the solution — NuGet restore did not complete for ReSharper.FSharp/src/FSharp/FSharp.Psi/FSharp.Psi.csproj, ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/FSharp.Psi.Features.fsproj, ReSharper.FSharp/src/FSharp/FSharp.Common/FSharp.Common.fsproj, ReSharper.FSharp/src/FSharp/FSharp.ProjectModelBase/FSharp.ProjectModelBase.csproj, ReSharper.FSharp/test/src/FSharp.Tests/FSharp.Tests.fsproj and 14 more, so those projects were analysed with framework references only: every check keyed on a third-party type saw an error type there and reported nothing. Findings on those projects are a lower bound; run `dotnet restore` on them and rescan.
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
- 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.
- 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.
- 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.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
- D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
- 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").
- 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.
- 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.
- 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
D3 · God Classes
22 god class(es) detected.
What to do
- Resolve the 10 FileTooLong finding(s) in God Classes — start with ProjectFcsModuleReader.fs, FSharpTypingAssist.fs, FSharpImplTreeBuilder.fs. — One of this dimension's main actionable groups (10 warning-level).
- Resolve the 7 TooManyMethods finding(s) in God Classes — start with ProjectFcsModuleReader.fs, FSharpTreeBuilderBase.fs, FSharpTypingAssist.fs. — One of this dimension's main actionable groups (7 warning-level).
- Resolve the 3 TooManyFunctions finding(s) in God Classes — start with PsiUtil.fs, FcsErrorsStageProcessBase.fs, FSharpHighlightingAttributeIds.fs. — One of this dimension's main actionable groups (3 warning-level).
D4 · Code Duplication
49 duplicated block group(s) detected. A further 14 rows report members as variants of one another; they aggregate block groups already counted above and are not themselves counted. Measured on part of this repository only: .cs (40% of production source) was not exposed to the token comparison, so duplication there is unmeasured and is not in this count.
What to do
- Resolve the 12 Duplicated block (5 lines × 2) finding(s) in Code Duplication — start with AppExpressionAnalyzer.fs, AsPatAnalyzer.fs, IndexerExprAnalyzer.fs. — One of this dimension's main actionable groups (12 warning-level).
- Resolve the 6 Duplicated block (7 lines × 2) finding(s) in Code Duplication — start with FSharpSourceCallableExpressionsProvider.fs, FSharpTypingAssist.fs, FSharpImplTreeBuilder.fs. — One of this dimension's main actionable groups (6 warning-level).
- Resolve the 5 Duplicated block (6 lines × 2) finding(s) in Code Duplication — start with RedundantQualifierAnalyzer.fs, ImportExtensionMemberRule.fs, FSharpInternalActionGroup.fs. — One of this dimension's main actionable groups (5 warning-level).
D5 · Coupling
10 projects, 0 dependency cycle(s), 0 unstable depended-on project(s).
D13 · Secret Scanning
6 secret(s) detected.
What to do
- Resolve the 6 Leaked secret finding(s) in Secret Scanning — start with REDACTED (5), REDACTED. — One of this dimension's main actionable groups (6 issue-level).
D14 · License Compliance
0 of 101 packages use a banned license. ★ DEPTH: this repository's MSBuild projects declare 32 direct `PackageReference`(s), and 76 further package(s) were reached beyond them by closing the graph over nuget.org's own nuspec dependency graph — so a banned licence pulled in only by a dependency's OWN dependencies is inside this verdict. A package whose licence nuget.org could not be asked for is not graded, and version ranges are taken at their lower bound, so this is the closure as that graph states it rather than a restored consumer's exact resolution. ★ COVERAGE OF THIS VERDICT: it grades this repository's NuGet package dependencies and nothing else. The repository also declares a Gradle build (build.gradle/build.gradle.kts), and the licences of those dependencies were NOT read by this pass — a gap in this engine's coverage, not a statement about them. So this result says the graded closure carries no banned licence; it does NOT say this repository's licensing is clear.
D16 · Bus Factor
42 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is ReSharper.FSharp/src/FSharp/FSharp.Common/src/Shim/AssemblyReader/ProjectFcsModuleReader.fs. Counted over 327 of the 1005 production source files in this repository: 674 are under the ~2,400-byte size floor this dimension measures over, and the remaining 4 have no attributable history left to measure.
What to do
- Resolve the 3 Off-boarding risk finding(s) in Bus Factor. — One of this dimension's main actionable groups (3 recommendation-level).
- Resolve the 1 Further sole-owners (lower concentration) finding(s) in Bus Factor. — One of this dimension's main actionable groups (1 recommendation-level).
D17 · Explicit Debt
12 deducted debt markers + unmeasured dead symbols across 186 LoC in the .NET projects (5.1/KLoC) → score 0.0. Dead code not measured: the solution did not load cleanly, so the reference search was skipped. Measured on the .NET source only: .fs, .cs (93% of production source) was not read, and carries at least 0 uncounted task marker(s) in 0 file(s).
What to do
- Resolve the 11 NoWarnInCsproj finding(s) in Explicit Debt — start with FSharp.Fantomas.Host.csproj (2), FSharp.TypeProviders.Host.NetCore.csproj (2), FSharp.Debugger.csproj. — One of this dimension's main actionable groups (11 issue-level).
- Resolve the 1 FixmeComment finding(s) in Explicit Debt — start with ExemptFromZoningValidation.cs. — One of this dimension's main actionable groups (1 warning-level).
D19 · Documentation Quality
2 of 2 documentation facets pass in full. 2 document(s) read across 11 unit(s).
D20 · ADR Quality
No architecture decision records were found.
What to do
- Resolve the 1 No ADRs found finding(s) in ADR Quality — start with FSharp.Fantomas.Host.csproj. — One of this dimension's main actionable groups (1 recommendation-level).
D26 · Project Cohesion
0 of 10 projects flagged as possibly oversized/incoherent.
D28 · Secrets (history)
6 finding(s): 0 critical, 6 high, 0 medium, 0 low.
What to do
- Resolve the 6 High secret finding(s) in Secrets (history) — start with REDACTED (5), REDACTED. — One of this dimension's main actionable groups (6 issue-level).
D29 · Static Analysis (SAST)
9 finding(s): 0 critical, 8 high, 1 medium, 0 low. 6 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. semgrep hit a parse error in 98 file(s) — `ReSharper.FSharp/src/FSharp.Debugger/src/FSharpAsyncStepper.cs` (line 27), `ReSharper.FSharp/src/FSharp.Debugger/src/FSharpSequencePointInvokedMethodsProvider.cs` (line 21), `ReSharper.FSharp/src/FSharp.Debugger/src/FSharpUnitReturnValueFilter.cs` (line 10), `ReSharper.FSharp/src/FSharp/FSharp.ProjectModelBase/src/FSharpAsyncUtil.cs` (lines 189–209), `ReSharper.FSharp/src/FSharp/FSharp.ProjectModelBase/src/FSharpZones.cs` (lines 14–29), … (+93 more) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them. In 70 of those file(s) — `ReSharper.FSharp/src/FSharp.Debugger/src/FSharpAsyncStepper.cs`, `ReSharper.FSharp/src/FSharp.Debugger/src/FSharpSequencePointInvokedMethodsProvider.cs`, `ReSharper.FSharp/src/FSharp.Debugger/src/FSharpUnitReturnValueFilter.cs`, `ReSharper.FSharp/src/FSharp/FSharp.Psi/src/Annotations/FSharpAnnotatedCacheProcessor.cs`, `ReSharper.FSharp/src/FSharp/FSharp.Psi/src/CodeFormatter/FSharpCodeFormatter.cs`, … (+65 more) — the break is a C# primary constructor, which semgrep's grammar cannot parse and which hides the type from every rule scoped to it; those files were re-scanned from a shadow copy with the constructor's parameter list blanked (line and column preserving), which restores the type to the rules, and 0 additional row(s) came from that pass. Only the header's own parameter list is unread in them.
What to do
- Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 issue-level).
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
- No action in Static Analysis (SAST) — all 6 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 (6 issue-level, 0 of them charged here).
D34 · Knowledge Freshness
8 of 331 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is ReSharper.FSharp/src/FSharp/FSharp.Psi/src/Parsing/FSharpPreprocessedLexer.cs. Counted over 331 of the 1005 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
D35 · Change Coupling
Strongest change-coupling: ForPostfixTemplate.fs↔MatchPostfixTemplate.fs 55%; ClassPart.cs↔FSharpImplUtil.cs 54%; FsiHost.fs↔SandboxDocumentLanguageSupportFSharpScript.fs 50%
What to do
- Resolve the 3 Change coupling finding(s) in Change Coupling — start with ForPostfixTemplate.fs, ClassPart.cs, FsiHost.fs. — One of this dimension's main actionable groups (3 warning-level).
D44 · Platform End-of-Life
3 end-of-life runtime(s) and 0 end-of-life framework(s), read from 80 platform declaration(s) and 4 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.
What to do
- Resolve the 10 End-of-life runtime finding(s) in Platform End-of-Life — start with CoreConsoleApp.fsproj (2), ClassLibrary1.fsproj, TypeProviderLibrary.fsproj. — One of this dimension's main actionable groups (10 warning-level).
Frontend & cross-cutting dimensions
AX10 · Code composition
AX3 · Project dependency cycles
AX5 · Architecture & structure
AX7 · Slice cohesion
AX8 · Test isolation
GD1 · Unfinished & placeholder code
- A shipped binding's whole body still raises a "not implemented" error — generated scaffolding that was never completed. Implement it or remove the dead surface. (×23) — ReSharper.FSharp/src/FSharp/FSharp.Psi.Services/src/Util/FSharpStringLexer.fs:69, ReSharper.FSharp/src/FSharp/FSharp.Psi.Services/src/Util/FSharpStringLexer.fs:108, ReSharper.FSharp/src/FSharp/FSharp.Psi.Services/src/Util/FSharpStringLexer.fs:179, …
What to do
- Finish or delete NotImplementedException stubs and replace placeholder literals before shipping.
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
P1 · CI/CD gates
P2 · Observability
- Only 5/6 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `rider-fsharp/projectTemplates/FSharpConsoleApplicationTemplate`.
What to do
- Extend structured logging to the remaining runnable modules so everything you run is diagnosable in production.
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 1 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:6
- `ReSharper.FSharp/Directory.Build.props` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`. — ReSharper.FSharp/Directory.Build.props:17
What to do
- Add a SAST step to CI running what this repository's stack ships: `semgrep --config=auto` plus gitleaks for committed secrets (F# is not a CodeQL language and has no language-specific SAST engine) — so a security regression fails the build instead of landing.
- Enable Dependabot/Renovate or a dependency-review gate.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P6 · Release Hygiene
PF3 · Async & latency hygiene
X5 · Nullable reference types
- 0/2 NRT-eligible project(s) enable <Nullable>enable</Nullable> (projects targeting a pre-C#-8 framework are excluded — NRTs aren't available there). NRTs catch a whole class of null-deref bugs at compile time.
What to do
- Enable <Nullable>enable</Nullable> across all projects and resolve warnings rather than suppressing with `!`.
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 29% | Weak — gated by D17, X5 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 100% | Exemplary | Solid. |
| Maturity | 58% | Adequate — gated by M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 48% | Weak — gated by D13, P3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 42% | Weak — gated by D44 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Performance | 100% | Exemplary | Strongest area. |
Unscored — 3 check(s) recorded observations but carry no score
- D36 Supply-chain Provenance & Signing — 1 observation(s) recorded · The CI pipeline publishes no artifact — no package publish, container push or release with files to download. Supply-chain provenance, signing and an SBOM describe a PUBLISHED artifact for the people who obtain it, so there is nothing to attest here; a deployment of the service itself publishes nothing for anyone else to verify. Add them to the release pipeline when this repo starts publishing artifacts (a package, a container image, or a release with downloadable files). Build integrity and workflow-token hygiene are reported below: they describe what the CI runs and the token it runs with, neither of which is affected by whether the pipeline ships an artifact.
- SC1 Supply-chain hygiene — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X10 Duplicated predicate — 4 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 2 control(s) we could not find positive evidence for
- P4 Deployment & Rollback — not evidenced — no deploy/rollback/approval signal in the repo; absence of evidence is not evidence of a manual release
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 81 check(s) not relevant to this codebase
- AC1 Text alternatives — No user-facing web UI (the repo is a library/CLI/worker/headless service) — accessibility is not applicable.
- AC2 Forms & labels — No user-facing web UI (the repo is a library/CLI/worker/headless service) — accessibility is not applicable.
- AC3 Page structure — No user-facing web UI (the repo is a library/CLI/worker/headless service) — accessibility is not applicable.
- AC4 Keyboard semantics — No user-facing web UI (the repo is a library/CLI/worker/headless service) — accessibility is not applicable.
- AC5 ARIA correctness — No user-facing web UI (the repo is a library/CLI/worker/headless service) — accessibility is not applicable.
- AC6 Visual & motion safety — No user-facing web UI (the repo is a library/CLI/worker/headless service) — accessibility is not applicable.
- AX1 Captive dependencies — no DI registrations detected
- AX2 Stateful singletons — no singleton implementations detected
- AX4 Dependency direction — not applicable to a vertical-slice architecture (the inward-dependency rule is for layered/clean styles)
- AX6 Interface segregation — AX6 reached only 41% of this repository's production lines — fsharp (38,098 lines), kotlin (4,142 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
- AXB1 Runtime evidence locked — no reproducible boot — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- C1 Data Protection — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
- C2 Access Controls — No access-control surface detected in the analyzed source — no web/app surface to authorize (no HTTP API or web-UI project) and no authorization code at all (no [Authorize]/policies, no imperative guard methods). Access control is therefore N/A here — this is a library/CLI, which is authorized by its CALLER, not by itself. If this codebase grows request handlers, the dimension reactivates and a default-deny posture is expected then.
- C3 Audit Trail — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
- C4 Data Retention — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
- C5 Data-Subject Rights — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
- D1 Cyclomatic Complexity — cyclomatic complexity not measured — .cs, .fs exposed no member bodies
- D10 Test Quality — ~51094 lines of test source are present (.fs, .kt) but no test cases reached the test census for this repository — no test root we could resolve declared them, or the files we read declare no cases in a test framework we recognise — so skipped/assertion-free tests couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
- D11 Test Reliability — Test reliability not measured — analyzer environment
- D12 Dependency Hygiene — Dependency hygiene not measured
- D15 Churn × Complexity Hotspots — complexity unreadable for .cs, .fs — churn × complexity hotspots could not be measured
- D18 Solution Shape — D18 scores the shape of a C#/VB .NET solution, but this repository's production source is mostly .fs, .java, .kt, which the C#/VB workspace does not load — the projects that loaded are an immaterial minority, so solution shape was not assessed for this repository. Not scored — this is a gap in the analyzer's reach, not a verdict about this repository.
- D2 Cognitive Complexity — cognitive complexity not measured — .cs, .fs exposed no member bodies
- D21 Naming Consistency — Naming consistency is measured on C# and TypeScript only; F#, Java, Kotlin not measured.
- D22 Internal API Consistency — No intentionally-exposed public API to evaluate for consistency.
- D23 Boundary Type-Coupling — Cross-context type coupling could not be assessed — this codebase's bounded contexts are neither declared nor inferable.
- D24 Comment Value — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only; comments in this repository's .fs, .java, .kt source were not judged.
- D25 ADR Conformance — no ADRs to check
- D27 Navigability — No calls could be sampled, so navigability was not assessed — tracing effort is measured over resolved call sites and this target exposed none. Not scored — this is a gap in the analyzer's reach, not a verdict about this repository.
- D30 Dependency Vulnerabilities — nuget: the solution did not restore on the analyzer's .NET SDK (an SDK/target-framework/restore mismatch, common for an older codebase), so there was no restored dependency graph to scan; nuget packages.config: osv-scanner exited 127 with no findings — dependency CVEs were not measured
- 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) — 99 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
- 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.
- D43 Malicious Dependencies — Scanner failed to run — not a clean result
- D6 Cohesion (LCOM4) — cohesion (LCOM4) not measured — the code model exposed no member bodies
- D7 Architectural Integrity — no checkable ADRs and no dependency cycles — architectural integrity not assessed
- D8 Code Coverage — Coverage not measured — no coverage collector is wired up
- DM1 Domain Modelling — not scored — this repository shows only 1 of the 3 signals this lens looks for (34 value object(s))
- 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 — IC1 reached only 40% of this repository's production lines — fsharp (38,098 lines), kotlin (4,142 lines), java (517 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
- P7 Outbound HTTP resilience — not applicable — this isn't a service/API/worker
- P8 Schema migrations — no EF Core usage detected
- 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 — Performance is assessed only for perf-relevant repos — a packaged library, one that ships benchmarks, or one already using allocation-aware APIs. This repo isn't one, so the Performance lens is not applicable and is excluded from the score.
- PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
- S1 Web-Security Posture — No web surface detected in the analyzed source — no HTTP API or web-UI project (no controllers/minimal-API endpoints, no Razor/Blazor views) and no web middleware (HTTPS redirection, HSTS, security headers, cookies). Transport security, security headers, secure cookies, CSRF/input-validation and middleware-order controls are therefore N/A here — this is a library/CLI/worker, not a web app. Crypto hygiene was still checked and found nothing to flag. If this codebase becomes web-facing, the dimension reactivates automatically.
- X1 Async correctness — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X12 Unreachable branch — X12 reached only 40% of this repository's production lines — fsharp (38,098 lines), kotlin (4,142 lines), java (517 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- X13 Undrained process stream — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X14 Bypassable address classification — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X16 Unfloored truncation loop — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X17 Uncapped recursion over a caller-supplied document — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X18 Disposal-pattern correctness — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X19 Unrestored process-global state — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X2 Cancellation propagation — no async method does work a token could cancel
- X20 Mistyped argument guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X21 Side-effecting pattern guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X22 Contradicted release guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X23 Unguarded diagnostic materialisation — X23 reached only 40% of this repository's production lines — fsharp (38,098 lines), kotlin (4,142 lines), java (517 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- X24 Document value interpolated into markup unescaped — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X25 Inert configuration knob — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X26 Unsynchronised callback handoff — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X27 Collection changed while being enumerated — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X28 Index access outside its own emptiness guard — X28 reached only 40% of this repository's production lines — fsharp (38,098 lines), kotlin (4,142 lines), java (517 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- X29 Per-element action decided by a fixed element — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X3 Exception handling — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X30 Support guard that admits what it rejects — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X32 Type resolved by simple name across every loaded assembly — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X4 Structured logging — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X7 Silent fallback defaults — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
Critical — 31 finding(s)
- NoWarnInCsproj ReSharper.FSharp/src/FSharp.Debugger/FSharp.Debugger.csproj:13
- NoWarnInCsproj ReSharper.FSharp/src/FSharp.Fantomas.Host/FSharp.Fantomas.Host.csproj:15
- NoWarnInCsproj ReSharper.FSharp/src/FSharp/FSharp.Fantomas.Protocol/FSharp.Fantomas.Protocol.csproj:12
- NoWarnInCsproj ReSharper.FSharp/src/FSharp/FSharp.ProjectModelBase/FSharp.ProjectModelBase.csproj:12
- NoWarnInCsproj ReSharper.FSharp/src/FSharp/FSharp.Psi/FSharp.Psi.csproj:12
- NoWarnInCsproj ReSharper.FSharp/src/FSharp/FSharp.TypeProviders.Protocol/FSharp.TypeProviders.Protocol.csproj:12
- NoWarnInCsproj ReSharper.FSharp/src/FSharp.TypeProviders.Host/FSharp.TypeProviders.Host/FSharp.TypeProviders.Host.csproj:15
- NoWarnInCsproj ReSharper.FSharp/src/FSharp.TypeProviders.Host/FSharp.TypeProviders.Host.NetCore/FSharp.TypeProviders.Host.NetCore.csproj:14
- NoWarnInCsproj ReSharper.FSharp/src/FSharp.RiderPlugin/proj/src/FSharp.RiderPlugin.csproj:12
- NoWarnInCsproj ReSharper.FSharp/src/FSharp.Fantomas.Host/FSharp.Fantomas.Host.csproj:15
- NoWarnInCsproj ReSharper.FSharp/src/FSharp.TypeProviders.Host/FSharp.TypeProviders.Host.NetCore/FSharp.TypeProviders.Host.NetCore.csproj:14
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
Serious — 125 finding(s)
- Unfinished stub — raises a "not implemented" error ReSharper.FSharp/src/FSharp/FSharp.Psi.Services/src/Util/FSharpStringLexer.fs:69
- Unfinished stub — raises a "not implemented" error ReSharper.FSharp/src/FSharp/FSharp.Psi.Services/src/Util/FSharpStringLexer.fs:108
- Unfinished stub — raises a "not implemented" error ReSharper.FSharp/src/FSharp/FSharp.Psi.Services/src/Util/FSharpStringLexer.fs:179
- Unfinished stub — raises a "not implemented" error ReSharper.FSharp/src/FSharp/FSharp.Psi.Services/src/Util/FSharpStringLexer.fs:202
- Unfinished stub — raises a "not implemented" error ReSharper.FSharp/src/FSharp/FSharp.Psi.Services/src/Refactorings/FSharpInlineVariable.fs:25
- Unfinished stub — raises a "not implemented" error ReSharper.FSharp/src/FSharp/FSharp.Psi.Services/src/Refactorings/FSharpInlineVariable.fs:26
- Unfinished stub — raises a "not implemented" error ReSharper.FSharp/src/FSharp/FSharp.Psi.Services/src/Refactorings/FSharpInlineVariable.fs:27
- Unfinished stub — raises a "not implemented" error ReSharper.FSharp/src/FSharp/FSharp.Psi.Services/src/Refactorings/FSharpInlineVariable.fs:28
- Unfinished stub — raises a "not implemented" error ReSharper.FSharp/src/FSharp/FSharp.Psi.Services/src/Refactorings/FSharpInlineVariable.fs:29
- Unfinished stub — raises a "not implemented" error ReSharper.FSharp/src/FSharp/FSharp.Psi.Services/src/Refactorings/FSharpInlineVariable.fs:30
- Unfinished stub — raises a "not implemented" error ReSharper.FSharp/src/FSharp/FSharp.Psi.Services/src/Refactorings/FSharpInlineVariable.fs:31
- Unfinished stub — raises a "not implemented" error ReSharper.FSharp/src/FSharp/FSharp.Psi.Services/src/Refactorings/FSharpInlineVariable.fs:32
- Unfinished stub — raises a "not implemented" error ReSharper.FSharp/src/FSharp/FSharp.Psi.Services/src/Refactorings/FSharpInlineVariable.fs:33
- Unfinished stub — raises a "not implemented" error ReSharper.FSharp/src/FSharp/FSharp.Psi.Services/src/Refactorings/FSharpInlineVariable.fs:34
- Unfinished stub — raises a "not implemented" error ReSharper.FSharp/src/FSharp/FSharp.Psi.Services/src/Refactorings/FSharpInlineVariable.fs:35
- Unfinished stub — raises a "not implemented" error ReSharper.FSharp/src/FSharp/FSharp.Psi.Services/src/Refactorings/FSharpInlineVariable.fs:36
- Unfinished stub — raises a "not implemented" error ReSharper.FSharp/src/FSharp/FSharp.Psi.Services/src/Refactorings/FSharpInlineVariable.fs:37
- Unfinished stub — raises a "not implemented" error ReSharper.FSharp/src/FSharp/FSharp.Psi.Services/src/Refactorings/FSharpInlineVariable.fs:38
- Unfinished stub — raises a "not implemented" error ReSharper.FSharp/src/FSharp/FSharp.Psi.Intentions/src/QuickFixes/ImportMemberFix.fs:99
- Unfinished stub — raises a "not implemented" error ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/Search/FSharpPathReference.fs:73
- Unfinished stub — raises a "not implemented" error ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/Search/FSharpPathReference.fs:74
- Unfinished stub — raises a "not implemented" error ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/Search/FSharpPathReference.fs:75
- Unfinished stub — raises a "not implemented" error ReSharper.FSharp/src/FSharp/FSharp.Common/src/ProjectModel/FSharpLanguageLevelProvider.fs:190
- Duplicated block (5 lines × 2) ReSharper.FSharp/src/FSharp/FSharp.Psi.Daemon/src/Analyzers/AppExpressionAnalyzer.fs:5
- Duplicated block (5 lines × 2) ReSharper.FSharp/src/FSharp/FSharp.Psi.Daemon/src/Analyzers/AsPatAnalyzer.fs:1
- Duplicated block (5 lines × 2) ReSharper.FSharp/src/FSharp/FSharp.Psi.Daemon/src/Analyzers/IndexerExprAnalyzer.fs:1
- Duplicated block (5 lines × 2) ReSharper.FSharp/src/FSharp/FSharp.Psi.Daemon/src/Analyzers/RecursiveInvocationAnalyzer.fs:1
- Duplicated block (5 lines × 2) ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/CodeCompletion/Rules/GenerateMatchExprPatternsRule.fs:1
- Duplicated block (5 lines × 2) ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/PostfixTemplates/ForPostfixTemplate.fs:9
- Duplicated block (5 lines × 2) ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/PostfixTemplates/NewObjPostfixTemplate.fs:1
- Duplicated block (5 lines × 2) ReSharper.FSharp/src/FSharp/FSharp.Psi.Intentions/src/Intentions/InvertIfAction.fs:1
- Duplicated block (5 lines × 2) ReSharper.FSharp/src/FSharp/FSharp.Psi.Intentions/src/QuickFixes/RemovePatternArgumentFix.fs:5
- Duplicated block (5 lines × 2) ReSharper.FSharp/src/FSharp/FSharp.Psi.Intentions/src/QuickFixes/ReplaceLetWithExpressionFix.fs:1
- Duplicated block (5 lines × 2) ReSharper.FSharp/src/FSharp/FSharp.Psi.Intentions/src/QuickFixes/ReplaceWithAbbreviatedTypeFix.fs:8
- Duplicated block (5 lines × 2) ReSharper.FSharp/src/FSharp/FSharp.Psi.Daemon/src/Stages/InferredTypeCodeVisionProvider.fs:12
- FileTooLong: AssemblyReader/ProjectFcsModuleReader.fs ReSharper.FSharp/src/FSharp/FSharp.Common/src/Shim/AssemblyReader/ProjectFcsModuleReader.fs
- FileTooLong: src/FSharpTypingAssist.fs ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/FSharpTypingAssist.fs
- FileTooLong: Parsing/FSharpImplTreeBuilder.fs ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/Parsing/FSharpImplTreeBuilder.fs
- FileTooLong: ProjectItems/FSharpItemsContainer.fs ReSharper.FSharp/src/FSharp/FSharp.Common/src/ProjectModel/Host/ProjectItems/FSharpItemsContainer.fs
- FileTooLong: ParameterInfo/FSharpParameterInfo.fs ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/ParameterInfo/FSharpParameterInfo.fs
- FileTooLong: Util/MatchTree.fs ReSharper.FSharp/src/FSharp/FSharp.Psi.Services/src/Util/MatchTree.fs
- FileTooLong: Parsing/FSharpTreeBuilderBase.fs ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/Parsing/FSharpTreeBuilderBase.fs
- FileTooLong: Generate/GenerateOverrides.fs ReSharper.FSharp/src/FSharp/FSharp.Psi.Services/src/Generate/GenerateOverrides.fs
- FileTooLong: Refactorings/IntroduceVariable.fs ReSharper.FSharp/src/FSharp/FSharp.Psi.Services/src/Refactorings/IntroduceVariable.fs
- FileTooLong: editorActions/FSharpEnterHandlerDelegate.kt rider-fsharp/src/main/java/com/jetbrains/rider/plugins/fsharp/editorActions/FSharpEnterHandlerDelegate.kt
- End-of-life runtime: .NET net5.0 rider-fsharp/src/test/testData/solutions/SplitNestedWithFile/ClassLibrary1/ClassLibrary1.fsproj:3
- End-of-life runtime: .NET net6.0 rider-fsharp/src/test/testData/solutions/ConsoleAppTwoTargetFrameworks/CoreConsoleApp.fsproj:5
- End-of-life runtime: .NET net6.0 rider-fsharp/src/test/testData/solutions/CoreConsoleApp/CoreConsoleApp.fsproj:5
- End-of-life runtime: .NET net6.0 rider-fsharp/src/test/testData/solutions/CsvTypeProvider/TypeProviderLibrary/TypeProviderLibrary.fsproj:4
- End-of-life runtime: .NET net6.0 rider-fsharp/src/test/testData/solutions/FableApp/FableApp.fsproj:5
- End-of-life runtime: .NET net6.0 rider-fsharp/src/test/testData/solutions/ReferencesOrder/ReferencesOrder.fsproj:5
- End-of-life runtime: .NET net6.0 rider-fsharp/src/test/testData/solutions/SwaggerProviderCSharp/CSharpLibrary/CSharpLibrary.csproj:4
- End-of-life runtime: .NET net6.0 rider-fsharp/src/test/testData/solutions/SwaggerProviderCSharp/SwaggerProviderLibrary/SwaggerProviderLibrary.fsproj:5
- End-of-life runtime: .NET netcoreapp3.1 ReSharper.FSharp/src/FSharp.TypeProviders.Host/FSharp.TypeProviders.Host.NetCore/FSharp.TypeProviders.Host.NetCore.csproj:18
- End-of-life runtime: .NET netcoreapp3.1 rider-fsharp/src/test/testData/solutions/FormatCodeApp/FormatCodeApp/FormatCodeApp.fsproj:5
- TooManyMethods: ProjectFcsModuleReader ReSharper.FSharp/src/FSharp/FSharp.Common/src/Shim/AssemblyReader/ProjectFcsModuleReader.fs:138
- TooManyMethods: FSharpTreeBuilderBase ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/Parsing/FSharpTreeBuilderBase.fs:25
- TooManyMethods: FSharpTypingAssist ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/FSharpTypingAssist.fs:35
- TooManyMethods: FSharpElementFactory ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/LanguageService/FSharpElementFactory.fs:20
- TooManyMethods: ProjectMapping ReSharper.FSharp/src/FSharp/FSharp.Common/src/ProjectModel/Host/ProjectItems/FSharpItemsContainer.fs:421
- TooManyMethods: FcsProjectProvider ReSharper.FSharp/src/FSharp/FSharp.Common/src/Checker/FcsProjectProvider.fs:71
- TooManyMethods: FSharpExpressionTreeBuilder ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/Parsing/FSharpImplTreeBuilder.fs:713
- Duplicated block (7 lines × 2) ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/Debugger/FSharpSourceCallableExpressionsProvider.fs:262
- Duplicated block (7 lines × 2) ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/FSharpTypingAssist.fs:1046
- Duplicated block (7 lines × 2) ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/Parsing/FSharpImplTreeBuilder.fs:164
- Duplicated block (7 lines × 2) ReSharper.FSharp/src/FSharp/FSharp.Psi.Intentions/src/Intentions/ElifToIfAction.fs:4
- Duplicated block (7 lines × 2) ReSharper.FSharp/src/FSharp/FSharp.Psi.Intentions/src/Intentions/IfToElifAction.fs:7
- Duplicated block (7 lines × 2) ReSharper.FSharp/src/FSharp/FSharp.Psi.Intentions/src/QuickFixes/UpdateRecordFieldTypeInSignatureFix.fs:1
- Duplicated block (6 lines × 2) ReSharper.FSharp/src/FSharp/FSharp.Psi.Daemon/src/Analyzers/RedundantQualifierAnalyzer.fs:8
- Duplicated block (6 lines × 2) ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/CodeCompletion/Rules/ImportExtensionMemberRule.fs:56
- Duplicated block (6 lines × 2) ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/Internal/FSharpInternalActionGroup.fs:21
- Duplicated block (6 lines × 2) ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/PostfixTemplates/MatchPostfixTemplate.fs:37
- Duplicated block (6 lines × 2) ReSharper.FSharp/src/FSharp/FSharp.Psi.Intentions/src/QuickFixes/ChangeTypeFix.fs:14
- Duplicated block (5 lines × 3) ReSharper.FSharp/src/FSharp/FSharp.Psi.Daemon/src/Analyzers/RedundantQualifierAnalyzer.fs:7
- Duplicated block (5 lines × 3) ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/CodeCompletion/Rules/GenerateLambdaRule.fs:19
- Duplicated block (5 lines × 3) ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/CodeCompletion/Rules/ImportModuleMemberRule.fs:46
- Duplicated block (5 lines × 3) ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/PostfixTemplates/ForPostfixTemplate.fs:143
- TooManyFunctions: PsiUtil ReSharper.FSharp/src/FSharp/FSharp.Psi.Services/src/Util/PsiUtil.fs:2
- TooManyFunctions: FSharpErrors ReSharper.FSharp/src/FSharp/FSharp.Psi.Daemon/src/Stages/FcsErrorsStageProcessBase.fs:40
- TooManyFunctions: FSharpHighlightingAttributeIds ReSharper.FSharp/src/FSharp/FSharp.Common/src/Util/FSharpHighlightingAttributeIds.fs:12
- Change coupling: ForPostfixTemplate.fs ↔ MatchPostfixTemplate.fs ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/PostfixTemplates/ForPostfixTemplate.fs:1
- Change coupling: ClassPart.cs ↔ FSharpImplUtil.cs ReSharper.FSharp/src/FSharp/FSharp.Psi/src/Impl/Cache2/Parts/ClassPart.cs:1
- Change coupling: FsiHost.fs ↔ SandboxDocumentLanguageSupportFSharpScript.fs ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/Fsi/FsiHost.fs:1
- Members sharing a duplicated core (4 members, 50+ identical tokens) ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/CodeCompletion/Rules/GenerateLambdaRule.fs:1
- Members sharing a duplicated core (4 members, 50+ identical tokens) ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/CodeCompletion/Rules/NameSuggestionRule.fs:1
- Members sharing a duplicated core (4 members, 50+ identical tokens) ReSharper.FSharp/src/FSharp/FSharp.Psi.Intentions/src/QuickFixes/ImportMemberFix.fs:1
- Duplicated block (11 lines × 2) ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/CodeCompletion/Rules/GenerateMatchExprPatternsRule.fs:76
- Duplicated block (11 lines × 2) ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/Parsing/FSharpImplTreeBuilder.fs:640
- Duplicated block (11 lines × 2) ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/PostfixTemplates/ForPostfixTemplate.fs:144
- Duplicated block (5 lines × 4) ReSharper.FSharp/src/FSharp/FSharp.Psi.Daemon/src/Analyzers/AppExpressionAnalyzer.fs:1
- Duplicated block (5 lines × 4) ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/CodeCompletion/Rules/ImportExtensionMemberRule.fs:4
- Duplicated block (5 lines × 4) ReSharper.FSharp/src/FSharp/FSharp.Psi.Intentions/src/QuickFixes/ImportMemberFix.fs:25
- ClassTooLong: FSharpEnterHandlerDelegate rider-fsharp/src/main/java/com/jetbrains/rider/plugins/fsharp/editorActions/FSharpEnterHandlerDelegate.kt:33
- ClassTooLong: FSharpTokenType rider-fsharp/src/main/java/com/jetbrains/rider/ideaInterop/fileTypes/fsharp/lexer/FSharpTokenType.java:13
- Duplicated block (12–13 lines × 2) ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/CodeCompletion/Rules/ImportModuleMemberRule.fs:68
- Duplicated block (12–13 lines × 2) ReSharper.FSharp/src/FSharp/FSharp.Psi.Intentions/src/QuickFixes/ChangeTypeFix.fs:84
- Duplicated block (9 lines × 2) ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/CodeCompletion/Rules/GenerateMatchExprPatternsRule.fs:14
- Duplicated block (9 lines × 2) ReSharper.FSharp/src/FSharp/FSharp.Psi.Services/src/Refactorings/IntroduceVariable.fs:21
- Duplicated block (6 lines × 3) ReSharper.FSharp/src/FSharp/FSharp.Psi.Intentions/src/Intentions/ElifToIfAction.fs:6
- Duplicated block (6 lines × 3) ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/CodeCompletion/Rules/ImportExtensionMemberRule.fs:9
- Duplicated block (4–5 lines × 4) ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/CodeCompletion/Rules/GenerateLambdaRule.fs:14
- Duplicated block (4–5 lines × 4) ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/CodeCompletion/Rules/NameSuggestionRule.fs:1
- FixmeComment ReSharper.FSharp/src/FSharp.RiderPlugin/src/Install/ExemptFromZoningValidation.cs:13
- REDACTED
- REDACTED
- Members sharing a duplicated core (10 members, 50+ identical tokens) ReSharper.FSharp/src/FSharp/FSharp.Psi.Intentions/src/QuickFixes/AddExtensionAttributeFix.fs:1
- Members sharing a duplicated core (5 members, 50+ identical tokens) ReSharper.FSharp/src/FSharp/FSharp.Psi.Intentions/src/QuickFixes/AddParensToTypedLikeExprFix.fs:1
- Edited copies of one member (3 members, 19+ corresponding lines) ReSharper.FSharp/src/FSharp/FSharp.Psi.Intentions/src/QuickFixes/RemoveRedundantAttributeParensFix.fs:1
- Edited copy of a member (20 corresponding lines) ReSharper.FSharp/src/FSharp/FSharp.Psi.Intentions/src/QuickFixes/RemoveUnnecessaryUpcastFix.fs:1
- Edited copy of a member (15 corresponding lines) rider-fsharp/src/main/java/com/jetbrains/rider/plugins/fsharp/projectView/FSharpMoveProviderExtension.kt:176
- Edited copy of a member (17 corresponding lines) ReSharper.FSharp/src/FSharp/FSharp.Psi.Intentions/src/QuickFixes/RemoveConstructorFix.fs:1
- Edited copy of a member (9 corresponding lines) ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/Comment/FSharpDocCommentElementsItemsProvider.fs:1
- Edited copies of one member (4 members, 7+ corresponding lines) ReSharper.FSharp/src/FSharp/FSharp.Common/src/ProjectModel/Host/ZoneMarker.fs:1
- Edited copy of a member (8 corresponding lines) ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/AI/ZoneMarker.fs:1
- Edited copies of one member (3 members, 8+ corresponding lines) ReSharper.FSharp/src/FSharp/FSharp.Common/src/Checker/ZoneMarker.fs:1
- Edited copies of one member (4 members, 8+ corresponding lines) ReSharper.FSharp/src/FSharp/FSharp.Psi.Daemon/PsiFeaturesNamespaceZoneMarker.fs:1
- Duplicated block (20–22 lines × 2) ReSharper.FSharp/src/FSharp/FSharp.Psi.Services/src/Util/StringLiteralsUtil.fs:153
- Duplicated block (19–20 lines × 2) ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/Parsing/FSharpImplTreeBuilder.fs:138
- Duplicated block (9–10 lines × 2) ReSharper.FSharp/src/FSharp/FSharp.Psi.Daemon/src/Stages/PatternTypeHintsStage.fs:1
- Duplicated block (2–7 lines × 10) ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/CodeCompletion/FSharpScriptReferenceCompletionProvider.fs:11
- Duplicated block (5 lines × 10) ReSharper.FSharp/src/FSharp/FSharp.Psi.Intentions/src/QuickFixes/AddExtensionAttributeFix.fs:1
- Duplicated block (5 lines × 5) ReSharper.FSharp/src/FSharp/FSharp.Psi.Intentions/src/QuickFixes/AddParensToTypedLikeExprFix.fs:1
- Duplicated block (4–5 lines × 3) ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/CodeCompletion/Rules/ImportModuleMemberRule.fs:18
- Duplicated block (8 lines × 2) ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/ZoneMarker.fs:1
- NuGet dependencies are not locked
Minor — 25 finding(s)
- Orphaned file ReSharper.FSharp/src/FSharp/FSharp.Psi/src/Parsing/FSharpPreprocessedLexer.cs:1
- Orphaned file ReSharper.FSharp/src/FSharp/FSharp.Psi.Services/src/Util/FSharpStringLexer.fs:1
- Orphaned file ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/Injected/FSharpRegexNodeProvider.fs:1
- Orphaned file ReSharper.FSharp/src/FSharp/FSharp.Psi/src/Parsing/FSharpPreprocessor.cs:1
- Orphaned file ReSharper.FSharp/src/FSharp/FSharp.Psi.Intentions/src/Intentions/UseNamedAccessAction.fs:1
- Orphaned file ReSharper.FSharp/src/FSharp/FSharp.Psi.Intentions/src/QuickFixes/UpdateParameterNameInSignatureFix.fs:1
- Orphaned file ReSharper.FSharp/src/FSharp/FSharp.Psi.Intentions/src/QuickFixes/ReplaceWithTripleQuotedInterpolatedStringFix.fs:1
- Orphaned file ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/Injected/FSharpRegexProviders.fs:1
- Duplicated predicate ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/CodeCompletion/Rules/ImportModuleMemberRule.fs:72
- Duplicated predicate ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/CodeCompletion/Rules/ImportModuleMemberRule.fs:69
- Duplicated predicate ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/CodeCompletion/Rules/FilterFcsItemsRules.fs:52
- Duplicated predicate ReSharper.FSharp/src/FSharp/FSharp.Psi.Features/src/CodeCompletion/FcsLookupItemsProvider.fs:99
- Off-boarding risk: anonymized user #1
- Off-boarding risk: anonymized user #2
- Off-boarding risk: anonymized user #3
- Further sole-owners (lower concentration)
- No ADRs found ReSharper.FSharp/src/FSharp.Fantomas.Host/FSharp.Fantomas.Host.csproj:16
- Orphaned files with no living knowledge
- REDACTED
- No ADRs
- No architecture diagram/doc
- Logging is not universal
- No SAST REDACTED:6
- No dependency-update automation ReSharper.FSharp/Directory.Build.props:17
- Nullable reference types not enabled everywhere
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-b82c657c041446379c867b745cd933cb/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-b82c657c041446379c867b745cd933cb/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 --exclude rider-fsharp/src/test/testData/solutions/AsyncProgram/obj --exclude rider-fsharp/src/test/testData/solutions/CeSteppingTests/obj --exclude rider-fsharp/src/test/testData/solutions/ConsoleAppTwoTargetFrameworks/obj --exclude rider-fsharp/src/test/testData/solutions/CoreConsoleApp/obj --exclude rider-fsharp/src/test/testData/solutions/CoreTypeProviderLibrary/TypeProviderLibrary/obj --exclude rider-fsharp/src/test/testData/solutions/CsvTypeProvider/TypeProviderLibrary/obj --exclude rider-fsharp/src/test/testData/solutions/EmptyFolders/ClassLibrary1/obj --exclude rider-fsharp/src/test/testData/solutions/FSharpProjectTree/ClassLibrary1/obj --exclude rider-fsharp/src/test/testData/solutions/FableApp/obj --exclude rider-fsharp/src/test/testData/solutions/FileNesting/ClassLibrary1/obj --exclude rider-fsharp/src/test/testData/solutions/FolderWithEmptySub/ClassLibrary1/obj --exclude rider-fsharp/src/test/testData/solutions/FormatCodeApp/FormatCodeApp/obj --exclude rider-fsharp/src/test/testData/solutions/FsprojWithTwoFiles/ClassLibrary1/obj --exclude rider-fsharp/src/test/testData/solutions/InterleavedFolder/ClassLibrary1/obj --exclude rider-fsharp/src/test/testData/solutions/LegacyTypeProviderLibrary/TypeProviderLibrary/obj --exclude rider-fsharp/src/test/testData/solutions/LinkBase/ClassLibrary1/obj --exclude rider-fsharp/src/test/testData/solutions/MoveProviderSolution1/obj --exclude rider-fsharp/src/test/testData/solutions/MoveProviderSolution2/obj --exclude rider-fsharp/src/test/testData/solutions/MoveProviderSolution3/obj --exclude rider-fsharp/src/test/testData/solutions/ProjectReferencesCSharp/FSharpProject/obj --exclude rider-fsharp/src/test/testData/solutions/ProjectReferencesCSharp2/CSharpProject/obj --exclude rider-fsharp/src/test/testData/solutions/ProjectReferencesCSharp2/FSharpProject/obj --exclude rider-fsharp/src/test/testData/solutions/ProjectReferencesCSharp3/CSharpProject/obj --exclude rider-fsharp/src/test/testData/solutions/ProjectReferencesCSharp3/FSharpProject/obj --exclude rider-fsharp/src/test/testData/solutions/ProjectReferencesFSharp/ReferenceFrom/obj --exclude rider-fsharp/src/test/testData/solutions/ProjectReferencesFSharp/ReferenceTo/obj --exclude rider-fsharp/src/test/testData/solutions/ReferencesOrder/obj --exclude rider-fsharp/src/test/testData/solutions/ReturnValueTest/obj --exclude rider-fsharp/src/test/testData/solutions/SmartStepIntoTest/obj --exclude rider-fsharp/src/test/testData/solutions/SolutionWithDuplicateTargets/SolutionWithDuplicateTargets/obj --exclude rider-fsharp/src/test/testData/solutions/SolutionWithExplicitItemBetweenSources/App/obj --exclude rider-fsharp/src/test/testData/solutions/SolutionWithGlobInFolderItem/Tests/obj --exclude rider-fsharp/src/test/testData/solutions/SolutionWithImportedXamlItems/App/obj --exclude rider-fsharp/src/test/testData/solutions/SplitNested/ClassLibrary1/obj --exclude rider-fsharp/src/test/testData/solutions/SplitNestedTwoFolders/ClassLibrary1/obj --exclude rider-fsharp/src/test/testData/solutions/SplitNestedWithFile/ClassLibrary1/obj --exclude rider-fsharp/src/test/testData/solutions/SteppingTests/obj --exclude rider-fsharp/src/test/testData/solutions/SwaggerProviderCSharp/SwaggerProviderLibrary/obj --exclude rider-fsharp/src/test/testData/solutions/TypeProviderLibrary/GenerativeTypeLibrary/obj --exclude rider-fsharp/src/test/testData/solutions/TypeProviderLibrary/GenerativeTypeProvider/obj --exclude rider-fsharp/src/test/testData/solutions/TypeProviderLibrary/TypeProviderLibrary/obj --exclude rider-fsharp/src/test/testData/solutions/TypeProviderLibrary/TypeProviderLibrary2/obj . | 9 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | nuget | — | nuget: not applicable — nuget: the solution did not restore on the analyzer's .NET SDK (an SDK/target-framework/restore mismatch, common for an older codebase), so there was no restored dependency graph to scan; nuget packages.config: osv-scanner exited 127 with no findings — dependency CVEs were not measured | 0 | — |
| 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. semgrep could not parse 99 file(s) — `ReSharper.FSharp/src/FSharp.Debugger/src/FSharpAsyncStepper.cs`, `ReSharper.FSharp/src/FSharp.Debugger/src/FSharpSequencePointInvokedMethodsProvider.cs`, `ReSharper.FSharp/src/FSharp.Debugger/src/FSharpUnitReturnValueFilter.cs`, `ReSharper.FSharp/src/FSharp/FSharp.ProjectModelBase/src/FSharpAsyncUtil.cs`, `ReSharper.FSharp/src/FSharp/FSharp.ProjectModelBase/src/FSharpZones.cs`, … (+94 more) — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real. | 0 | — |
| D37 · Vulnerability-disclosure Policy | disclosure | — | disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . /tmp/codehealth-osv-sbom-131c1a97cc8f44b8a8edf8f1178c273c | 0 | artifacts/raw/osv-scanner.json |