Executive summary
Kotlin/kotlin-lsp falls short of our standard for production because we found no working pipeline that builds or tests changes to the code and no automated security scanning of the code, its secrets or its dependencies. It scores 53 out of 100 and is rated Adequate, and none of its 11 critical findings concern security.
Production Readiness, at 44, is the weakest lens and counts most in the score. The best first step is adding an automated build and test pipeline, worth about 7 points. Removing the blocking calls is another step, worth about 2 points. Raising Production Readiness to 70 would lift the score to about 61.
Nine sets of files in separate parts keep changing together, which points to hidden dependencies. Making the hidden dependencies explicit would close this risk. The loop of files that import each other needs breaking.
The product code is 28,799 lines, about €40,000 to rebuild.
If Production Readiness rose from 44 to 70, the lowest score rated Strong, the score would rise from 53 to about 61.
New since the last survey: 44 findings
- Cyclomatic Complexity · OptionPaneReader.read (cyclomatic 25) features-impl/common/src/com/jetbrains/ls/api/features/impl/common/modcommands/EditOptions.kt
- Cyclomatic Complexity · FormRenderer.component (cyclomatic 21) vscode-extension-core/src/editOptionsModel.ts
- Code Duplication · Members sharing a duplicated core (5 members, 50+ identical tokens) features-impl/common/src/com/jetbrains/ls/api/features/impl/common/diagnostics/LSCommonInjectionSyntaxErrorDiagnosticProvider.kt
- Code Duplication · Edited copy of a member (41 corresponding lines) features-impl/common/src/com/jetbrains/ls/api/features/impl/common/completion/ModCompletionCommandConverter.kt
- Code Duplication · Edited copy of a member (21 corresponding lines) features-impl/java-base/src/com/jetbrains/ls/api/features/impl/javaBase/LSJavaPackageDefinitionProvider.kt
- Code Duplication · Edited copy of a member (21 corresponding lines) features-impl/common/src/com/jetbrains/ls/api/features/impl/common/callHierarchy/LSCallHierarchyProviderBase.kt
- Code Duplication · Edited copy of a member (16 corresponding lines) features-impl/kotlin/src/com/jetbrains/ls/api/features/impl/kotlin/typeHierarchy/LSKotlinTypeHierarchyProvider.kt
- Code Duplication · Edited copy of a member (14 corresponding lines) features-impl/kotlin/src/com/jetbrains/ls/api/features/impl/kotlin/typeHierarchy/LSKotlinTypeHierarchyProvider.kt
- Code Duplication · Edited copy of a member (12 corresponding lines) features-impl/common/src/com/jetbrains/ls/api/features/impl/common/callHierarchy/LSCallHierarchyProviderBase.kt
- Code Duplication · Edited copy of a member (15 corresponding lines) api.features/src/com/jetbrains/ls/api/features/implementation/LSImplementation.kt
- Code Duplication · Edited copy of a member (17 corresponding lines) api.features/src/com/jetbrains/ls/api/features/diagnostics/LSDiagnostic.kt
- Code Duplication · Edited copy of a member (8 corresponding lines) api.features/src/com/jetbrains/ls/api/features/semanticTokens/LSSemanticTokens.kt
- Code Duplication · Edited copy of a member (15 corresponding lines) features-impl/common/src/com/jetbrains/ls/api/features/impl/common/rename/renameUtils.kt
- Code Duplication · Edited copy of a member (5 corresponding lines) api.features/src/com/jetbrains/ls/api/features/callHierarchy/LSCallHierarchy.kt
- Code Duplication · Edited copy of a member (5 corresponding lines) api.features/src/com/jetbrains/ls/api/features/callHierarchy/LSCallHierarchy.kt
- Code Duplication · Edited copy of a member (9 corresponding lines) features-impl/common/src/com/jetbrains/ls/api/features/impl/common/callHierarchy/LSCallHierarchyProviderBase.kt
- Code Duplication · Edited copy of a member (5 corresponding lines) features-impl/common/src/com/jetbrains/ls/api/features/impl/common/diagnostics/LSCommonSyntaxErrorDiagnosticProvider.kt
- Code Duplication · Duplicated block (12–16 lines × 2) buildtool.api/src/com/jetbrains/ls/buildtool/api/run/RunSteps.kt
- Code Duplication · Duplicated block (4–5 lines × 5) features-impl/common/src/com/jetbrains/ls/api/features/impl/common/diagnostics/LSCommonInjectionSyntaxErrorDiagnosticProvider.kt
- Code Duplication · Duplicated block (5 lines × 2) features-impl/kotlin/src/com/jetbrains/ls/api/features/impl/kotlin/superDeclarations/LSKotlinSuperDeclarationsProvider.kt
- Explicit Debt · TodoComment features-impl/common/src/com/jetbrains/ls/api/features/impl/common/modcommands/ModCommandData.kt
- Explicit Debt · TodoComment api.features/src/com/jetbrains/ls/api/features/commands/document/LSDocumentCommandComandExecutor.kt
- Change Coupling · Change-coupling hub: LSKotlinPackageDefinitionProvider.kt → LSCommonDefinitionProvider.kt, LSCommonInspectionDiagnosticProvider.kt, LSCommonSyntaxErrorDiagnosticProvider.kt, LSHoverProviderBase.kt, LSCommonReferencesProvider.kt, LSKotlinSemanticTokensProvider.kt features-impl/kotlin/src/com/jetbrains/ls/api/features/impl/kotlin/definitions/LSKotlinPackageDefinitionProvider.kt
- Change Coupling · Change-coupling hub: LSCommonSyntaxErrorDiagnosticProvider.kt → LSCommonInspectionDiagnosticProvider.kt, LSKotlinCompilerDiagnosticsFixesCodeActionProvider.kt, LSKotlinCompilerDiagnosticsProvider.kt, LSKotlinIntentionCodeActionProvider.kt features-impl/common/src/com/jetbrains/ls/api/features/impl/common/diagnostics/LSCommonSyntaxErrorDiagnosticProvider.kt
- Code Duplication · Duplicated block (9 lines × 2 locations) vscode-extension-core/src/keyHandlerUtils.ts
- Import Boundaries · Boundary violation [package:relative-cross-package] vscode-extension-core/src/keyHandlerTestUtils.ts
- Cyclomatic Complexity · Complex function component (cyclomatic 20, cognitive 10) vscode-extension-core/src/editOptionsModel.ts
- Cyclomatic Complexity · Complex function configOf (cyclomatic 15, cognitive 14) vscode-jvm-testing/src/jvmTestLanguage.ts
- Cyclomatic Complexity · Complex function getRegularEnterResult (cyclomatic 12, cognitive 12) vscode-extension-core/src/keyHandlerUtils.ts
- Cyclomatic Complexity · Complex function (anonymous) (cyclomatic 12, cognitive 10) vscode-testing/src/testPlan.ts
- Cyclomatic Complexity · Complex function feed (cyclomatic 11, cognitive 13) vscode-extension-core/src/runTerminalModel.ts
- Cyclomatic Complexity · Complex function choose (cyclomatic 11, cognitive 12) vscode-jvm-testing/src/jvmTestConfig.ts
- Cyclomatic Complexity · Complex function getClosedBlockCommentBodyIndent (cyclomatic 11, cognitive 10) vscode-language-kotlin/src/kotlin/keyHandler.ts
- Cyclomatic Complexity · Complex function computeStatusText (cyclomatic 11, cognitive 9) vscode-extension-core/src/statusBarModel.ts
- Large Files · vscode-extension-core/src/lspClient.ts: 1352 lines of code vscode-extension-core/src/lspClient.ts
- Large Files · vscode-extension-core/src/editOptionsModel.ts: 513 lines of code vscode-extension-core/src/editOptionsModel.ts
- Cancellation propagation · Async function without AbortSignal: downloadFile vscode-extension-core/src/serverBundleDownload.ts
- Exception handling · Swallowed exception (empty catch) vscode-extension-core/src/editOptions.ts
- Exception handling · Swallowed exception (empty catch) vscode-extension-core/src/intellijExtensions.ts
- Exception handling · Swallowed exception (empty catch) vscode-extension-core/src/intellijExtensions.ts
- Slice cohesion · Cross-slice coupling: impl → utils features-impl/common/src/com/jetbrains/ls/api/features/impl/common/callHierarchy/LSCallHierarchyProviderBase.kt
- Slice cohesion · Cross-slice coupling: impl → utils features-impl/common/src/com/jetbrains/ls/api/features/impl/common/callHierarchy/LSCallHierarchyProviderBase.kt
- Slice cohesion · Cross-slice coupling: impl → codeActions features-impl/common/src/com/jetbrains/ls/api/features/impl/common/diagnostics/LSCommonInspectionOptionsCodeActionProvider.kt
- Slice cohesion · Cross-slice coupling: impl → commands features-impl/common/src/com/jetbrains/ls/api/features/impl/common/stackTrace/LSStackTraceCommandDescriptorProvider.kt
Fixed since the last survey: 54 findings
- Cyclomatic Complexity · ConversionKt.importWorkspaceData (cyclomatic 25) workspace-import/src/com/jetbrains/ls/imports/json/conversion.kt
- Cyclomatic Complexity · JpsBuildTool.importJpsModel (cyclomatic 19) workspace-import/src/com/jetbrains/ls/imports/jps/JpsBuildTool.kt
- Cyclomatic Complexity · DependencyFlatteningKt.flattenExportedDependencies (cyclomatic 18) workspace-import/src/com/jetbrains/ls/imports/json/dependencyFlattening.kt
- Cyclomatic Complexity · UtilKt.doGetCompilerProp (cyclomatic 16) workspace-import/maven-plugin/src/com/jetbrains/ls/imports/maven/util.kt
- Cognitive Complexity · DependencyFlatteningKt.flattenExportedDependencies (cognitive 39) workspace-import/src/com/jetbrains/ls/imports/json/dependencyFlattening.kt
- Cognitive Complexity · ProjectMetadataBuilder.resolveModels (cognitive 32) workspace-import/gradle-plugin/src/com/jetbrains/ls/imports/gradle/action/ProjectMetadataBuilder.java
- Cognitive Complexity · ConverterKt.mapModuleNames (cognitive 29) workspace-import/maven-plugin/src/com/jetbrains/ls/imports/maven/converter.kt
- Cognitive Complexity · UtilKt.doGetCompilerProp (cognitive 29) workspace-import/maven-plugin/src/com/jetbrains/ls/imports/maven/util.kt
- Cognitive Complexity · ConversionKt.importWorkspaceData (cognitive 28) workspace-import/src/com/jetbrains/ls/imports/json/conversion.kt
- Cognitive Complexity · KotlinMultiplatformMapper.map (cognitive 21) workspace-import/src/com/jetbrains/ls/imports/gradle/kmp/KotlinMultiplatformMapper.kt
- Cognitive Complexity · JpsBuildTool.importJpsModel (cognitive 20) workspace-import/src/com/jetbrains/ls/imports/jps/JpsBuildTool.kt
- Cognitive Complexity · GradleContentRootResolver.getContentRoots (cognitive 17) workspace-import/src/com/jetbrains/ls/imports/gradle/GradleContentRootResolver.kt
- Cognitive Complexity · MavenRunCommandsKt.mavenArgs (cognitive 16) workspace-import/src/com/jetbrains/ls/imports/maven/MavenRunCommands.kt
- God Classes · MethodTooLong: JpsBuildTool.importJpsModel workspace-import/src/com/jetbrains/ls/imports/jps/JpsBuildTool.kt
- God Classes · MethodTooLong: ConversionKt.importWorkspaceData workspace-import/src/com/jetbrains/ls/imports/json/conversion.kt
- God Classes · FileTooLong: jps/JpsBuildTool.kt workspace-import/src/com/jetbrains/ls/imports/jps/JpsBuildTool.kt
- God Classes · FileTooLong: maven/converter.kt workspace-import/maven-plugin/src/com/jetbrains/ls/imports/maven/converter.kt
- God Classes · FileTooLong: json/conversion.kt workspace-import/src/com/jetbrains/ls/imports/json/conversion.kt
- Code Duplication · Duplicated block (12–16 lines × 2) buildtool.api/src/com/jetbrains/ls/buildtool/api/run/RunSteps.kt
- Code Duplication · Duplicated block (8–14 lines × 2) workspace-import/src/com/jetbrains/ls/imports/json/conversion.kt
- Code Duplication · Duplicated block (5 lines × 2) workspace-import/maven-plugin/src/com/jetbrains/ls/imports/maven/util.kt
- Churn × Complexity Hotspots · Hotspot: workspace-import/src/com/jetbrains/ls/imports/jps/JpsBuildTool.kt workspace-import/src/com/jetbrains/ls/imports/jps/JpsBuildTool.kt
- Churn × Complexity Hotspots · Hotspot: workspace-import/src/com/jetbrains/ls/imports/json/conversion.kt workspace-import/src/com/jetbrains/ls/imports/json/conversion.kt
- Churn × Complexity Hotspots · Hotspot: vscode-extension-core/src/initializationSettings.ts vscode-extension-core/src/initializationSettings.ts
- Explicit Debt · TodoComment workspace-import/test/test/com/jetbrains/ls/imports/GradleProjectImportTest.kt
- Explicit Debt · TodoComment workspace-import/src/com/jetbrains/ls/imports/json/conversion.kt
- Explicit Debt · TodoComment features-impl/kotlin/src/com/jetbrains/ls/api/features/impl/kotlin/hover/LSKotlinMarkdownDocProvider.kt
- Explicit Debt · TodoComment features-impl/common/src/com/jetbrains/ls/api/features/impl/common/modcommands/ModCommandData.kt
- Explicit Debt · TodoComment features-impl/common/src/com/jetbrains/ls/api/features/impl/common/modcommands/ModCommandData.kt
- Explicit Debt · TodoComment api.features/src/com/jetbrains/ls/api/features/commands/document/LSDocumentCommandComandExecutor.kt
- Explicit Debt · TodoComment api.features/src/com/jetbrains/ls/api/features/commands/document/LSDocumentCommandComandExecutor.kt
- Change Coupling · Change coupling: ModuleSourceSetImpl.kt ↔ IdeaProjectMapper.kt workspace-import/gradle-plugin/src/com/jetbrains/ls/imports/gradle/model/impl/ModuleSourceSetImpl.kt
- Change Coupling · Change-coupling hub: LSKotlinPackageDefinitionProvider.kt → LSCommonDefinitionProvider.kt, LSCommonInspectionDiagnosticProvider.kt, LSHoverProviderBase.kt, LSCommonReferencesProvider.kt, LSKotlinSemanticTokensProvider.kt features-impl/kotlin/src/com/jetbrains/ls/api/features/impl/kotlin/definitions/LSKotlinPackageDefinitionProvider.kt
- Change Coupling · Change-coupling hub: LSCommonSyntaxErrorDiagnosticProvider.kt → LSCommonDefinitionProvider.kt, LSCommonInspectionDiagnosticProvider.kt, LSCommonReferencesProvider.kt, LSKotlinPackageDefinitionProvider.kt, LSKotlinCompilerDiagnosticsFixesCodeActionProvider.kt, LSKotlinCompilerDiagnosticsProvider.kt, LSKotlinIntentionCodeActionProvider.kt features-impl/common/src/com/jetbrains/ls/api/features/impl/common/diagnostics/LSCommonSyntaxErrorDiagnosticProvider.kt
- Change Coupling · Change coupling: ModuleSourceSetsModelBuilder.kt ↔ IdeaProjectMapper.kt workspace-import/gradle-plugin/src/com/jetbrains/ls/imports/gradle/model/builder/ModuleSourceSetsModelBuilder.kt
- Change Coupling · Change coupling: GradleTool.kt ↔ GradleToolingApiHelper.kt workspace-import/src/com/jetbrains/ls/imports/gradle/GradleTool.kt
- Change Coupling · Change coupling: LSCommonInspectionDiagnosticProvider.kt ↔ LSCommonReferencesProvider.kt features-impl/common/src/com/jetbrains/ls/api/features/impl/common/diagnostics/LSCommonInspectionDiagnosticProvider.kt
- Large Files · vscode-extension-core/src/lspClient.ts: 1273 lines of code vscode-extension-core/src/lspClient.ts
- Exception handling · Swallowed exception (caught, then discarded) workspace-import/src/com/jetbrains/ls/imports/java/JavaRunCommands.kt
- Exception handling · Swallowed exception (caught, then discarded) workspace-import/src/com/jetbrains/ls/imports/gradle/GradleToolingApiHelper.kt
- Exception handling · Swallowed exception (caught, then discarded) workspace-import/src/com/jetbrains/ls/imports/gradle/GradleToolingApiHelper.kt
- Exception handling · Swallowed exception (caught, then discarded) workspace-import/src/com/jetbrains/ls/imports/gradle/GradleToolingApiHelper.kt
- Exception handling · Swallowed exception (caught, then discarded) workspace-import/gradle-plugin/src/com/jetbrains/ls/imports/gradle/utils/SourceSetArtifactExtractor.java
- Exception handling · Swallowed exception (empty catch) workspace-import/gradle-plugin/src/com/jetbrains/ls/imports/gradle/model/builder/KotlinMetadataModelBuilder.java
- Exception handling · Swallowed exception (caught, then discarded) workspace-import/gradle-plugin/src/com/jetbrains/ls/imports/gradle/model/builder/KotlinVersionReflectiveUtils.java
- Exception handling · Swallowed exception (caught, then discarded) workspace-import/gradle-plugin/src/com/jetbrains/ls/imports/gradle/model/builder/KotlinVersionReflectiveUtils.java
- Exception handling · Swallowed exception (caught, then discarded) workspace-import/gradle-plugin/src/com/jetbrains/ls/imports/gradle/model/builder/KotlinMultiplatformModelBuilder.kt
- Exception handling · Swallowed exception (empty catch) workspace-import/gradle-plugin/src/com/jetbrains/ls/imports/gradle/model/builder/ModuleSourceSetsModelBuilder.kt
- Exception handling · Swallowed exception (empty catch) vscode-extension-core/src/intellijExtensions.ts
- Exception handling · Swallowed exception (empty catch) vscode-extension-core/src/intellijExtensions.ts
- Slice cohesion · Cross-slice coupling: impl → utils features-impl/common/src/com/jetbrains/ls/api/features/impl/common/callHierarchy/LSCallHierarchyProviderBase.kt
- Slice cohesion · Cross-slice coupling: impl → utils features-impl/common/src/com/jetbrains/ls/api/features/impl/common/callHierarchy/LSCallHierarchyProviderBase.kt
- Slice cohesion · Cross-slice coupling: impl → utils features-impl/common/src/com/jetbrains/ls/api/features/impl/common/callHierarchy/LSCallHierarchyProviderBase.kt
- Slice cohesion · Cross-slice coupling: impl → utils features-impl/common/src/com/jetbrains/ls/api/features/impl/common/callHierarchy/LSCallHierarchyProviderBase.kt
Rebuild cost: about €40,000 · Estimate
| Cost to rebuild | €13,000 to €67,000, for 222 to 703 hours of work, about 0.3 person-years for one engineer |
|---|---|
| Difficulty of the problem | Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.7 at a score of 53. 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: 28,799 lines of product code |
| What it is not | Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one. |
Top priorities
Diagnosis: what the measurements show together
Architecture: which parts of the code depend on which
| uses → | 1 com.jetbrains.ls.api.features.configuration.LSUniqueConfigurationEntry | 2 com.jetbrains.ls.api.features.impl.common.move | 3 com.jetbrains.ls.api.features.impl.common.utils.LSRefactoringMemberProviderBase | 4 com.jetbrains.ls.api.features.utils | 5 com.jetbrains.ls.buildtool.api | 6 vscode-extension-core.src | 7 vscode-testing.src.testProtocol | 8 com.jetbrains.ls.api.features.commands | 9 com.jetbrains.ls.api.features.impl.common.callHierarchy.LSCallHierarchyProviderBase | 10 com.jetbrains.ls.api.features.impl.common.inlayHints.LSInlayHintsProviderBase | 11 com.jetbrains.ls.api.features.impl.kotlin.typeHierarchy.LSKotlinTypeHierarchyProvider | 12 com.jetbrains.ls.api.features.language | 13 com.jetbrains.ls.kotlinLsp.requests.core.ModCommandData | 14 vscode-testing.src.testTree | 15 com.jetbrains.ls.api.features | 16 com.jetbrains.ls.api.features.impl.common.callHierarchy.LSCallHierarchyProviderBase.CallHierarchyTarget | 17 com.jetbrains.ls.api.features.impl.common.codeLens | 18 com.jetbrains.ls.api.features.impl.common.inlayHints | 19 com.jetbrains.ls.kotlinLsp.requests.core | 20 vscode-testing.src.testRunReport | 21 com.jetbrains.ls.api.features.codeActions | 22 com.jetbrains.ls.api.features.configuration | 23 com.jetbrains.ls.api.features.definition | 24 com.jetbrains.ls.api.features.impl.common.callHierarchy | 25 com.jetbrains.ls.api.features.impl.common.modcommands | 26 com.jetbrains.ls.api.features.semanticTokens | 27 vscode-testing.src.testLanguage | 28 com.jetbrains.ls.api.features.completion | 29 com.jetbrains.ls.api.features.impl.common.configuration | 30 com.jetbrains.ls.api.features.impl.common.diagnostics | 31 com.jetbrains.ls.api.features.impl.common.utils | 32 com.jetbrains.ls.api.features.impl.kotlin.inline | 33 com.jetbrains.ls.api.features.impl.kotlin.typeHierarchy | 34 vscode-jvm-testing.src | 35 vscode-testing.src | 36 com.jetbrains.ls.api.features.impl.common.completion.LSCompletionProviderHelper | 37 com.jetbrains.ls.api.features.impl.javaBase | 38 com.jetbrains.ls.api.features.impl.kotlin.diagnostics.compiler | 39 com.jetbrains.ls.api.features.impl.common.completion | 40 com.jetbrains.ls.api.features.impl.kotlin.completion |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 com.jetbrains.ls.api.features.configuration.LSUniqueConfigurationEntry | ||||||||||||||||||||||||||||||||||||||||
| 2 com.jetbrains.ls.api.features.impl.common.move | ||||||||||||||||||||||||||||||||||||||||
| 3 com.jetbrains.ls.api.features.impl.common.utils.LSRefactoringMemberProviderBase | ||||||||||||||||||||||||||||||||||||||||
| 4 com.jetbrains.ls.api.features.utils | ||||||||||||||||||||||||||||||||||||||||
| 5 com.jetbrains.ls.buildtool.api | ||||||||||||||||||||||||||||||||||||||||
| 6 vscode-extension-core.src | ||||||||||||||||||||||||||||||||||||||||
| 7 vscode-testing.src.testProtocol | ||||||||||||||||||||||||||||||||||||||||
| 8 com.jetbrains.ls.api.features.commands | 1 | |||||||||||||||||||||||||||||||||||||||
| 9 com.jetbrains.ls.api.features.impl.common.callHierarchy.LSCallHierarchyProviderBase | 1 | |||||||||||||||||||||||||||||||||||||||
| 10 com.jetbrains.ls.api.features.impl.common.inlayHints.LSInlayHintsProviderBase | 1 | |||||||||||||||||||||||||||||||||||||||
| 11 com.jetbrains.ls.api.features.impl.kotlin.typeHierarchy.LSKotlinTypeHierarchyProvider | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 12 com.jetbrains.ls.api.features.language | 1 | |||||||||||||||||||||||||||||||||||||||
| 13 com.jetbrains.ls.kotlinLsp.requests.core.ModCommandData | 17 | 1 | ||||||||||||||||||||||||||||||||||||||
| 14 vscode-testing.src.testTree | 3 | |||||||||||||||||||||||||||||||||||||||
| 15 com.jetbrains.ls.api.features | 1 | 1 | 4 | |||||||||||||||||||||||||||||||||||||
| 16 com.jetbrains.ls.api.features.impl.common.callHierarchy.LSCallHierarchyProviderBase.CallHierarchyTarget | 2 | 2 | ||||||||||||||||||||||||||||||||||||||
| 17 com.jetbrains.ls.api.features.impl.common.codeLens | 1 | |||||||||||||||||||||||||||||||||||||||
| 18 com.jetbrains.ls.api.features.impl.common.inlayHints | 1 | 4 | 1 | |||||||||||||||||||||||||||||||||||||
| 19 com.jetbrains.ls.kotlinLsp.requests.core | 2 | 1 | ||||||||||||||||||||||||||||||||||||||
| 20 vscode-testing.src.testRunReport | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 21 com.jetbrains.ls.api.features.codeActions | 2 | 1 | ||||||||||||||||||||||||||||||||||||||
| 22 com.jetbrains.ls.api.features.configuration | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 23 com.jetbrains.ls.api.features.definition | 1 | |||||||||||||||||||||||||||||||||||||||
| 24 com.jetbrains.ls.api.features.impl.common.callHierarchy | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 25 com.jetbrains.ls.api.features.impl.common.modcommands | 2 | 3 | 2 | |||||||||||||||||||||||||||||||||||||
| 26 com.jetbrains.ls.api.features.semanticTokens | 2 | |||||||||||||||||||||||||||||||||||||||
| 27 vscode-testing.src.testLanguage | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 28 com.jetbrains.ls.api.features.completion | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 29 com.jetbrains.ls.api.features.impl.common.configuration | 2 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 30 com.jetbrains.ls.api.features.impl.common.diagnostics | 7 | 1 | 4 | 3 | ||||||||||||||||||||||||||||||||||||
| 31 com.jetbrains.ls.api.features.impl.common.utils | 3 | 2 | 1 | |||||||||||||||||||||||||||||||||||||
| 32 com.jetbrains.ls.api.features.impl.kotlin.inline | 2 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 33 com.jetbrains.ls.api.features.impl.kotlin.typeHierarchy | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 34 vscode-jvm-testing.src | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 35 vscode-testing.src | 5 | 2 | 4 | |||||||||||||||||||||||||||||||||||||
| 36 com.jetbrains.ls.api.features.impl.common.completion.LSCompletionProviderHelper | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 37 com.jetbrains.ls.api.features.impl.javaBase | 6 | 1 | 1 | 1 | 2 | |||||||||||||||||||||||||||||||||||
| 38 com.jetbrains.ls.api.features.impl.kotlin.diagnostics.compiler | 1 | 2 | 2 | 1 | 2 | 3 | ||||||||||||||||||||||||||||||||||
| 39 com.jetbrains.ls.api.features.impl.common.completion | 1 | 1 | 1 | 2 | 5 | |||||||||||||||||||||||||||||||||||
| 40 com.jetbrains.ls.api.features.impl.kotlin.completion | 1 | 2 | 1 | 3 | 1 | 1 |
8→15 com.jetbrains.ls.api.features.commands uses com.jetbrains.ls.api.features part of a loop✕
- Connections
- 1 pair of types, where a type in com.jetbrains.ls.api.features.commands uses a type in com.jetbrains.ls.api.features.
- The types involved
com.jetbrains.ls.api.features.commands.LSCommandDescriptorProvider→com.jetbrains.ls.api.features.LSConfigurationEntry
- Direction
- com.jetbrains.ls.api.features.commands uses com.jetbrains.ls.api.features, so a change to com.jetbrains.ls.api.features can break com.jetbrains.ls.api.features.commands, while a change to com.jetbrains.ls.api.features.commands can't break com.jetbrains.ls.api.features.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
9→1 com.jetbrains.ls.api.features.impl.common.callHierarchy.LSCallHierarchyProviderBase uses com.jetbrains.ls.api.features.configuration.LSUniqueConfigurationEntry✕
- Connections
- 1 pair of types, where a type in com.jetbrains.ls.api.features.impl.common.callHierarchy.LSCallHierarchyProviderBase uses a type in com.jetbrains.ls.api.features.configuration.LSUniqueConfigurationEntry.
- The types involved
com.jetbrains.ls.api.features.impl.common.callHierarchy.LSCallHierarchyProviderBase.CallHierarchyItemData→com.jetbrains.ls.api.features.configuration.LSUniqueConfigurationEntry.UniqueId
- Direction
- com.jetbrains.ls.api.features.impl.common.callHierarchy.LSCallHierarchyProviderBase uses com.jetbrains.ls.api.features.configuration.LSUniqueConfigurationEntry, so a change to com.jetbrains.ls.api.features.configuration.LSUniqueConfigurationEntry can break com.jetbrains.ls.api.features.impl.common.callHierarchy.LSCallHierarchyProviderBase, while a change to com.jetbrains.ls.api.features.impl.common.callHierarchy.LSCallHierarchyProviderBase can't break com.jetbrains.ls.api.features.configuration.LSUniqueConfigurationEntry.
- Position
- Below the diagonal: com.jetbrains.ls.api.features.impl.common.callHierarchy.LSCallHierarchyProviderBase uses a module listed above it, which is the healthy direction.
10→1 com.jetbrains.ls.api.features.impl.common.inlayHints.LSInlayHintsProviderBase uses com.jetbrains.ls.api.features.configuration.LSUniqueConfigurationEntry✕
- Connections
- 1 pair of types, where a type in com.jetbrains.ls.api.features.impl.common.inlayHints.LSInlayHintsProviderBase uses a type in com.jetbrains.ls.api.features.configuration.LSUniqueConfigurationEntry.
- The types involved
com.jetbrains.ls.api.features.impl.common.inlayHints.LSInlayHintsProviderBase.InlayHintResolveData→com.jetbrains.ls.api.features.configuration.LSUniqueConfigurationEntry.UniqueId
- Direction
- com.jetbrains.ls.api.features.impl.common.inlayHints.LSInlayHintsProviderBase uses com.jetbrains.ls.api.features.configuration.LSUniqueConfigurationEntry, so a change to com.jetbrains.ls.api.features.configuration.LSUniqueConfigurationEntry can break com.jetbrains.ls.api.features.impl.common.inlayHints.LSInlayHintsProviderBase, while a change to com.jetbrains.ls.api.features.impl.common.inlayHints.LSInlayHintsProviderBase can't break com.jetbrains.ls.api.features.configuration.LSUniqueConfigurationEntry.
- Position
- Below the diagonal: com.jetbrains.ls.api.features.impl.common.inlayHints.LSInlayHintsProviderBase uses a module listed above it, which is the healthy direction.
11→1 com.jetbrains.ls.api.features.impl.kotlin.typeHierarchy.LSKotlinTypeHierarchyProvider uses com.jetbrains.ls.api.features.configuration.LSUniqueConfigurationEntry✕
- Connections
- 1 pair of types, where a type in com.jetbrains.ls.api.features.impl.kotlin.typeHierarchy.LSKotlinTypeHierarchyProvider uses a type in com.jetbrains.ls.api.features.configuration.LSUniqueConfigurationEntry.
- The types involved
com.jetbrains.ls.api.features.impl.kotlin.typeHierarchy.LSKotlinTypeHierarchyProvider.TypeHierarchyItemData→com.jetbrains.ls.api.features.configuration.LSUniqueConfigurationEntry.UniqueId
- Direction
- com.jetbrains.ls.api.features.impl.kotlin.typeHierarchy.LSKotlinTypeHierarchyProvider uses com.jetbrains.ls.api.features.configuration.LSUniqueConfigurationEntry, so a change to com.jetbrains.ls.api.features.configuration.LSUniqueConfigurationEntry can break com.jetbrains.ls.api.features.impl.kotlin.typeHierarchy.LSKotlinTypeHierarchyProvider, while a change to com.jetbrains.ls.api.features.impl.kotlin.typeHierarchy.LSKotlinTypeHierarchyProvider can't break com.jetbrains.ls.api.features.configuration.LSUniqueConfigurationEntry.
- Position
- Below the diagonal: com.jetbrains.ls.api.features.impl.kotlin.typeHierarchy.LSKotlinTypeHierarchyProvider uses a module listed above it, which is the healthy direction.
11→4 com.jetbrains.ls.api.features.impl.kotlin.typeHierarchy.LSKotlinTypeHierarchyProvider uses com.jetbrains.ls.api.features.utils✕
- Connections
- 1 pair of types, where a type in com.jetbrains.ls.api.features.impl.kotlin.typeHierarchy.LSKotlinTypeHierarchyProvider uses a type in com.jetbrains.ls.api.features.utils.
- The types involved
com.jetbrains.ls.api.features.impl.kotlin.typeHierarchy.LSKotlinTypeHierarchyProvider.TypeHierarchyItemData→com.jetbrains.ls.api.features.utils.PsiSerializablePointer
- Direction
- com.jetbrains.ls.api.features.impl.kotlin.typeHierarchy.LSKotlinTypeHierarchyProvider uses com.jetbrains.ls.api.features.utils, so a change to com.jetbrains.ls.api.features.utils can break com.jetbrains.ls.api.features.impl.kotlin.typeHierarchy.LSKotlinTypeHierarchyProvider, while a change to com.jetbrains.ls.api.features.impl.kotlin.typeHierarchy.LSKotlinTypeHierarchyProvider can't break com.jetbrains.ls.api.features.utils.
- Position
- Below the diagonal: com.jetbrains.ls.api.features.impl.kotlin.typeHierarchy.LSKotlinTypeHierarchyProvider uses a module listed above it, which is the healthy direction.
12→15 com.jetbrains.ls.api.features.language uses com.jetbrains.ls.api.features part of a loop✕
- Connections
- 1 pair of types, where a type in com.jetbrains.ls.api.features.language uses a type in com.jetbrains.ls.api.features.
- The types involved
com.jetbrains.ls.api.features.language.LSConfigurationPiece→com.jetbrains.ls.api.features.LSConfigurationEntry
- Direction
- com.jetbrains.ls.api.features.language uses com.jetbrains.ls.api.features, so a change to com.jetbrains.ls.api.features can break com.jetbrains.ls.api.features.language, while a change to com.jetbrains.ls.api.features.language can't break com.jetbrains.ls.api.features.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
13→19 com.jetbrains.ls.kotlinLsp.requests.core.ModCommandData uses com.jetbrains.ls.kotlinLsp.requests.core part of a loop✕
- Connections
- 17 pairs of types, where a type in com.jetbrains.ls.kotlinLsp.requests.core.ModCommandData uses a type in com.jetbrains.ls.kotlinLsp.requests.core.
- The types involved
com.jetbrains.ls.kotlinLsp.requests.core.ModCommandData.ChooseAction→com.jetbrains.ls.kotlinLsp.requests.core.ModCommandDatacom.jetbrains.ls.kotlinLsp.requests.core.ModCommandData.Companion→com.jetbrains.ls.kotlinLsp.requests.core.ModCommandDatacom.jetbrains.ls.kotlinLsp.requests.core.ModCommandData.Composite→com.jetbrains.ls.kotlinLsp.requests.core.ModCommandDatacom.jetbrains.ls.kotlinLsp.requests.core.ModCommandData.CopyToClipboard→com.jetbrains.ls.kotlinLsp.requests.core.ModCommandDatacom.jetbrains.ls.kotlinLsp.requests.core.ModCommandData.CreateFile→com.jetbrains.ls.kotlinLsp.requests.core.ModCommandDatacom.jetbrains.ls.kotlinLsp.requests.core.ModCommandData.DeleteFile→com.jetbrains.ls.kotlinLsp.requests.core.ModCommandDatacom.jetbrains.ls.kotlinLsp.requests.core.ModCommandData.DisplayMessage→com.jetbrains.ls.kotlinLsp.requests.core.ModCommandDatacom.jetbrains.ls.kotlinLsp.requests.core.ModCommandData.EditOptions→com.jetbrains.ls.kotlinLsp.requests.core.ModCommandDatacom.jetbrains.ls.kotlinLsp.requests.core.ModCommandData.LaunchEditorAction→com.jetbrains.ls.kotlinLsp.requests.core.ModCommandDatacom.jetbrains.ls.kotlinLsp.requests.core.ModCommandData.LazyAction→com.jetbrains.ls.kotlinLsp.requests.core.ModCommandDatacom.jetbrains.ls.kotlinLsp.requests.core.ModCommandData.MoveFile→com.jetbrains.ls.kotlinLsp.requests.core.ModCommandDatacom.jetbrains.ls.kotlinLsp.requests.core.ModCommandData.Navigate→com.jetbrains.ls.kotlinLsp.requests.core.ModCommandDatacom.jetbrains.ls.kotlinLsp.requests.core.ModCommandData.Nothing→com.jetbrains.ls.kotlinLsp.requests.core.ModCommandDatacom.jetbrains.ls.kotlinLsp.requests.core.ModCommandData.ShowConflicts→com.jetbrains.ls.kotlinLsp.requests.core.ModCommandDatacom.jetbrains.ls.kotlinLsp.requests.core.ModCommandData.Snippet→com.jetbrains.ls.kotlinLsp.requests.core.ModCommandDatacom.jetbrains.ls.kotlinLsp.requests.core.ModCommandData.StartRename→com.jetbrains.ls.kotlinLsp.requests.core.ModCommandDatacom.jetbrains.ls.kotlinLsp.requests.core.ModCommandData.UpdateFileText→com.jetbrains.ls.kotlinLsp.requests.core.ModCommandData
- Direction
- com.jetbrains.ls.kotlinLsp.requests.core.ModCommandData uses com.jetbrains.ls.kotlinLsp.requests.core, so a change to com.jetbrains.ls.kotlinLsp.requests.core can break com.jetbrains.ls.kotlinLsp.requests.core.ModCommandData, while a change to com.jetbrains.ls.kotlinLsp.requests.core.ModCommandData can't break com.jetbrains.ls.kotlinLsp.requests.core.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
13→25 com.jetbrains.ls.kotlinLsp.requests.core.ModCommandData uses com.jetbrains.ls.api.features.impl.common.modcommands part of a loop✕
- Connections
- 1 pair of types, where a type in com.jetbrains.ls.kotlinLsp.requests.core.ModCommandData uses a type in com.jetbrains.ls.api.features.impl.common.modcommands.
- The types involved
com.jetbrains.ls.kotlinLsp.requests.core.ModCommandData.EditOptions→com.jetbrains.ls.api.features.impl.common.modcommands.OptionComponentData
- Direction
- com.jetbrains.ls.kotlinLsp.requests.core.ModCommandData uses com.jetbrains.ls.api.features.impl.common.modcommands, so a change to com.jetbrains.ls.api.features.impl.common.modcommands can break com.jetbrains.ls.kotlinLsp.requests.core.ModCommandData, while a change to com.jetbrains.ls.kotlinLsp.requests.core.ModCommandData can't break com.jetbrains.ls.api.features.impl.common.modcommands.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
14→7 vscode-testing.src.testTree uses vscode-testing.src.testProtocol✕
- Connections
- 3 pairs of types, where a type in vscode-testing.src.testTree uses a type in vscode-testing.src.testProtocol.
- The types involved
vscode-testing.src.testTree.DiscoveredTestEntry→vscode-testing.src.testProtocol.TestItemDtovscode-testing.src.testTree.RuntimeTestEntry→vscode-testing.src.testProtocol.TestItemDtovscode-testing.src.testTree.TestTree→vscode-testing.src.testProtocol.TestItemDto
- Direction
- vscode-testing.src.testTree uses vscode-testing.src.testProtocol, so a change to vscode-testing.src.testProtocol can break vscode-testing.src.testTree, while a change to vscode-testing.src.testTree can't break vscode-testing.src.testProtocol.
- Position
- Below the diagonal: vscode-testing.src.testTree uses a module listed above it, which is the healthy direction.
15→1 com.jetbrains.ls.api.features uses com.jetbrains.ls.api.features.configuration.LSUniqueConfigurationEntry✕
- Connections
- 1 pair of types, where a type in com.jetbrains.ls.api.features uses a type in com.jetbrains.ls.api.features.configuration.LSUniqueConfigurationEntry.
- The types involved
com.jetbrains.ls.api.features.LSConfiguration→com.jetbrains.ls.api.features.configuration.LSUniqueConfigurationEntry.UniqueId
- Direction
- com.jetbrains.ls.api.features uses com.jetbrains.ls.api.features.configuration.LSUniqueConfigurationEntry, so a change to com.jetbrains.ls.api.features.configuration.LSUniqueConfigurationEntry can break com.jetbrains.ls.api.features, while a change to com.jetbrains.ls.api.features can't break com.jetbrains.ls.api.features.configuration.LSUniqueConfigurationEntry.
- Position
- Below the diagonal: com.jetbrains.ls.api.features uses a module listed above it, which is the healthy direction.
15→8 com.jetbrains.ls.api.features uses com.jetbrains.ls.api.features.commands✕
- Connections
- 1 pair of types, where a type in com.jetbrains.ls.api.features uses a type in com.jetbrains.ls.api.features.commands.
- The types involved
com.jetbrains.ls.api.features.LSConfiguration→com.jetbrains.ls.api.features.commands.LSCommandDescriptor
- Direction
- com.jetbrains.ls.api.features uses com.jetbrains.ls.api.features.commands, so a change to com.jetbrains.ls.api.features.commands can break com.jetbrains.ls.api.features, while a change to com.jetbrains.ls.api.features can't break com.jetbrains.ls.api.features.commands.
- Position
- Below the diagonal: com.jetbrains.ls.api.features uses a module listed above it, which is the healthy direction.
15→12 com.jetbrains.ls.api.features uses com.jetbrains.ls.api.features.language✕
- Connections
- 4 pairs of types, where a type in com.jetbrains.ls.api.features uses a type in com.jetbrains.ls.api.features.language.
- The types involved
com.jetbrains.ls.api.features.LSConfiguration→com.jetbrains.ls.api.features.language.LSLanguagecom.jetbrains.ls.api.features.LSConfigurationKt→com.jetbrains.ls.api.features.language.LSConfigurationPiececom.jetbrains.ls.api.features.LSLanguageSpecificConfigurationEntry→com.jetbrains.ls.api.features.language.LSLanguagecom.jetbrains.ls.api.features.LanguageServerExtension→com.jetbrains.ls.api.features.language.LSConfigurationPiece
- Direction
- com.jetbrains.ls.api.features uses com.jetbrains.ls.api.features.language, so a change to com.jetbrains.ls.api.features.language can break com.jetbrains.ls.api.features, while a change to com.jetbrains.ls.api.features can't break com.jetbrains.ls.api.features.language.
- Position
- Below the diagonal: com.jetbrains.ls.api.features uses a module listed above it, which is the healthy direction.
16→4 com.jetbrains.ls.api.features.impl.common.callHierarchy.LSCallHierarchyProviderBase.CallHierarchyTarget uses com.jetbrains.ls.api.features.utils✕
- Connections
- 2 pairs of types, where a type in com.jetbrains.ls.api.features.impl.common.callHierarchy.LSCallHierarchyProviderBase.CallHierarchyTarget uses a type in com.jetbrains.ls.api.features.utils.
- The types involved
com.jetbrains.ls.api.features.impl.common.callHierarchy.LSCallHierarchyProviderBase.CallHierarchyTarget.Declaration→com.jetbrains.ls.api.features.utils.PsiSerializablePointercom.jetbrains.ls.api.features.impl.common.callHierarchy.LSCallHierarchyProviderBase.CallHierarchyTarget.ImplicitMember→com.jetbrains.ls.api.features.utils.PsiSerializablePointer
- Direction
- com.jetbrains.ls.api.features.impl.common.callHierarchy.LSCallHierarchyProviderBase.CallHierarchyTarget uses com.jetbrains.ls.api.features.utils, so a change to com.jetbrains.ls.api.features.utils can break com.jetbrains.ls.api.features.impl.common.callHierarchy.LSCallHierarchyProviderBase.CallHierarchyTarget, while a change to com.jetbrains.ls.api.features.impl.common.callHierarchy.LSCallHierarchyProviderBase.CallHierarchyTarget can't break com.jetbrains.ls.api.features.utils.
- Position
- Below the diagonal: com.jetbrains.ls.api.features.impl.common.callHierarchy.LSCallHierarchyProviderBase.CallHierarchyTarget uses a module listed above it, which is the healthy direction.
16→9 com.jetbrains.ls.api.features.impl.common.callHierarchy.LSCallHierarchyProviderBase.CallHierarchyTarget uses com.jetbrains.ls.api.features.impl.common.callHierarchy.LSCallHierarchyProviderBase✕
- Connections
- 2 pairs of types, where a type in com.jetbrains.ls.api.features.impl.common.callHierarchy.LSCallHierarchyProviderBase.CallHierarchyTarget uses a type in com.jetbrains.ls.api.features.impl.common.callHierarchy.LSCallHierarchyProviderBase.
- The types involved
com.jetbrains.ls.api.features.impl.common.callHierarchy.LSCallHierarchyProviderBase.CallHierarchyTarget.Declaration→com.jetbrains.ls.api.features.impl.common.callHierarchy.LSCallHierarchyProviderBase.CallHierarchyTargetcom.jetbrains.ls.api.features.impl.common.callHierarchy.LSCallHierarchyProviderBase.CallHierarchyTarget.ImplicitMember→com.jetbrains.ls.api.features.impl.common.callHierarchy.LSCallHierarchyProviderBase.CallHierarchyTarget
- Direction
- com.jetbrains.ls.api.features.impl.common.callHierarchy.LSCallHierarchyProviderBase.CallHierarchyTarget uses com.jetbrains.ls.api.features.impl.common.callHierarchy.LSCallHierarchyProviderBase, so a change to com.jetbrains.ls.api.features.impl.common.callHierarchy.LSCallHierarchyProviderBase can break com.jetbrains.ls.api.features.impl.common.callHierarchy.LSCallHierarchyProviderBase.CallHierarchyTarget, while a change to com.jetbrains.ls.api.features.impl.common.callHierarchy.LSCallHierarchyProviderBase.CallHierarchyTarget can't break com.jetbrains.ls.api.features.impl.common.callHierarchy.LSCallHierarchyProviderBase.
- Position
- Below the diagonal: com.jetbrains.ls.api.features.impl.common.callHierarchy.LSCallHierarchyProviderBase.CallHierarchyTarget uses a module listed above it, which is the healthy direction.
17→12 com.jetbrains.ls.api.features.impl.common.codeLens uses com.jetbrains.ls.api.features.language✕
- Connections
- 1 pair of types, where a type in com.jetbrains.ls.api.features.impl.common.codeLens uses a type in com.jetbrains.ls.api.features.language.
- The types involved
com.jetbrains.ls.api.features.impl.common.codeLens.LSRelatedItemsCodeLensProvider→com.jetbrains.ls.api.features.language.LSLanguage
- Direction
- com.jetbrains.ls.api.features.impl.common.codeLens uses com.jetbrains.ls.api.features.language, so a change to com.jetbrains.ls.api.features.language can break com.jetbrains.ls.api.features.impl.common.codeLens, while a change to com.jetbrains.ls.api.features.impl.common.codeLens can't break com.jetbrains.ls.api.features.language.
- Position
- Below the diagonal: com.jetbrains.ls.api.features.impl.common.codeLens uses a module listed above it, which is the healthy direction.
18→1 com.jetbrains.ls.api.features.impl.common.inlayHints uses com.jetbrains.ls.api.features.configuration.LSUniqueConfigurationEntry✕
- Connections
- 1 pair of types, where a type in com.jetbrains.ls.api.features.impl.common.inlayHints uses a type in com.jetbrains.ls.api.features.configuration.LSUniqueConfigurationEntry.
- The types involved
com.jetbrains.ls.api.features.impl.common.inlayHints.LSInlayHintsProviderBase→com.jetbrains.ls.api.features.configuration.LSUniqueConfigurationEntry.UniqueId
- Direction
- com.jetbrains.ls.api.features.impl.common.inlayHints uses com.jetbrains.ls.api.features.configuration.LSUniqueConfigurationEntry, so a change to com.jetbrains.ls.api.features.configuration.LSUniqueConfigurationEntry can break com.jetbrains.ls.api.features.impl.common.inlayHints, while a change to com.jetbrains.ls.api.features.impl.common.inlayHints can't break com.jetbrains.ls.api.features.configuration.LSUniqueConfigurationEntry.
- Position
- Below the diagonal: com.jetbrains.ls.api.features.impl.common.inlayHints uses a module listed above it, which is the healthy direction.
18→10 com.jetbrains.ls.api.features.impl.common.inlayHints uses com.jetbrains.ls.api.features.impl.common.inlayHints.LSInlayHintsProviderBase✕
- Connections
- 4 pairs of types, where a type in com.jetbrains.ls.api.features.impl.common.inlayHints uses a type in com.jetbrains.ls.api.features.impl.common.inlayHints.LSInlayHintsProviderBase.
- The types involved
com.jetbrains.ls.api.features.impl.common.inlayHints.LSInlayHintsProviderBase→com.jetbrains.ls.api.features.impl.common.inlayHints.LSInlayHintsProviderBase.InlayOptionscom.jetbrains.ls.api.features.impl.common.inlayHints.LSInlayHintsProviderBase→com.jetbrains.ls.api.features.impl.common.inlayHints.LSInlayHintsProviderBase.LSCommonInlayTreeSinkcom.jetbrains.ls.api.features.impl.common.inlayHints.LSInlayHintsProviderBase→com.jetbrains.ls.api.features.impl.common.inlayHints.LSInlayHintsProviderBase.Presentationcom.jetbrains.ls.api.features.impl.common.inlayHints.LSInlayHintsProviderBase→com.jetbrains.ls.api.features.impl.common.inlayHints.LSInlayHintsProviderBase.Provider
- Direction
- com.jetbrains.ls.api.features.impl.common.inlayHints uses com.jetbrains.ls.api.features.impl.common.inlayHints.LSInlayHintsProviderBase, so a change to com.jetbrains.ls.api.features.impl.common.inlayHints.LSInlayHintsProviderBase can break com.jetbrains.ls.api.features.impl.common.inlayHints, while a change to com.jetbrains.ls.api.features.impl.common.inlayHints can't break com.jetbrains.ls.api.features.impl.common.inlayHints.LSInlayHintsProviderBase.
- Position
- Below the diagonal: com.jetbrains.ls.api.features.impl.common.inlayHints uses a module listed above it, which is the healthy direction.
18→12 com.jetbrains.ls.api.features.impl.common.inlayHints uses com.jetbrains.ls.api.features.language✕
- Connections
- 1 pair of types, where a type in com.jetbrains.ls.api.features.impl.common.inlayHints uses a type in com.jetbrains.ls.api.features.language.
- The types involved
com.jetbrains.ls.api.features.impl.common.inlayHints.LSInlayHintsProviderBase→com.jetbrains.ls.api.features.language.LSLanguage
- Direction
- com.jetbrains.ls.api.features.impl.common.inlayHints uses com.jetbrains.ls.api.features.language, so a change to com.jetbrains.ls.api.features.language can break com.jetbrains.ls.api.features.impl.common.inlayHints, while a change to com.jetbrains.ls.api.features.impl.common.inlayHints can't break com.jetbrains.ls.api.features.language.
- Position
- Below the diagonal: com.jetbrains.ls.api.features.impl.common.inlayHints uses a module listed above it, which is the healthy direction.
19→13 com.jetbrains.ls.kotlinLsp.requests.core uses com.jetbrains.ls.kotlinLsp.requests.core.ModCommandData✕
- Connections
- 2 pairs of types, where a type in com.jetbrains.ls.kotlinLsp.requests.core uses a type in com.jetbrains.ls.kotlinLsp.requests.core.ModCommandData.
- The types involved
com.jetbrains.ls.kotlinLsp.requests.core.ModCommandDataKt→com.jetbrains.ls.kotlinLsp.requests.core.ModCommandData.Editcom.jetbrains.ls.kotlinLsp.requests.core.ModCommandDataKt→com.jetbrains.ls.kotlinLsp.requests.core.ModCommandData.ShowConflicts
- Direction
- com.jetbrains.ls.kotlinLsp.requests.core uses com.jetbrains.ls.kotlinLsp.requests.core.ModCommandData, so a change to com.jetbrains.ls.kotlinLsp.requests.core.ModCommandData can break com.jetbrains.ls.kotlinLsp.requests.core, while a change to com.jetbrains.ls.kotlinLsp.requests.core can't break com.jetbrains.ls.kotlinLsp.requests.core.ModCommandData.
- Position
- Below the diagonal: com.jetbrains.ls.kotlinLsp.requests.core uses a module listed above it, which is the healthy direction.
19→25 com.jetbrains.ls.kotlinLsp.requests.core uses com.jetbrains.ls.api.features.impl.common.modcommands part of a loop✕
- Connections
- 1 pair of types, where a type in com.jetbrains.ls.kotlinLsp.requests.core uses a type in com.jetbrains.ls.api.features.impl.common.modcommands.
- The types involved
com.jetbrains.ls.kotlinLsp.requests.core.ModCommandDataKt→com.jetbrains.ls.api.features.impl.common.modcommands.DocumentStamp
- Direction
- com.jetbrains.ls.kotlinLsp.requests.core uses com.jetbrains.ls.api.features.impl.common.modcommands, so a change to com.jetbrains.ls.api.features.impl.common.modcommands can break com.jetbrains.ls.kotlinLsp.requests.core, while a change to com.jetbrains.ls.kotlinLsp.requests.core can't break com.jetbrains.ls.api.features.impl.common.modcommands.
- 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.
20→14 vscode-testing.src.testRunReport uses vscode-testing.src.testTree✕
- Connections
- 1 pair of types, where a type in vscode-testing.src.testRunReport uses a type in vscode-testing.src.testTree.
- The types involved
vscode-testing.src.testRunReport.GroupReportOptions→vscode-testing.src.testTree.TestTree
- Direction
- vscode-testing.src.testRunReport uses vscode-testing.src.testTree, so a change to vscode-testing.src.testTree can break vscode-testing.src.testRunReport, while a change to vscode-testing.src.testRunReport can't break vscode-testing.src.testTree.
- Position
- Below the diagonal: vscode-testing.src.testRunReport uses a module listed above it, which is the healthy direction.
20→27 vscode-testing.src.testRunReport uses vscode-testing.src.testLanguage part of a loop✕
- Connections
- 1 pair of types, where a type in vscode-testing.src.testRunReport uses a type in vscode-testing.src.testLanguage.
- The types involved
vscode-testing.src.testRunReport.GroupReport→vscode-testing.src.testLanguage.UnreportedNodes
- Direction
- vscode-testing.src.testRunReport uses vscode-testing.src.testLanguage, so a change to vscode-testing.src.testLanguage can break vscode-testing.src.testRunReport, while a change to vscode-testing.src.testRunReport can't break vscode-testing.src.testLanguage.
- 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.
21→8 com.jetbrains.ls.api.features.codeActions uses com.jetbrains.ls.api.features.commands✕
- Connections
- 2 pairs of types, where a type in com.jetbrains.ls.api.features.codeActions uses a type in com.jetbrains.ls.api.features.commands.
- The types involved
com.jetbrains.ls.api.features.codeActions.LSSimpleCodeActionProvider→com.jetbrains.ls.api.features.commands.LSCommandDescriptorcom.jetbrains.ls.api.features.codeActions.LSSimpleCodeActionProvider→com.jetbrains.ls.api.features.commands.LSCommandDescriptorProvider
- Direction
- com.jetbrains.ls.api.features.codeActions uses com.jetbrains.ls.api.features.commands, so a change to com.jetbrains.ls.api.features.commands can break com.jetbrains.ls.api.features.codeActions, while a change to com.jetbrains.ls.api.features.codeActions can't break com.jetbrains.ls.api.features.commands.
- Position
- Below the diagonal: com.jetbrains.ls.api.features.codeActions uses a module listed above it, which is the healthy direction.
21→15 com.jetbrains.ls.api.features.codeActions uses com.jetbrains.ls.api.features✕
- Connections
- 1 pair of types, where a type in com.jetbrains.ls.api.features.codeActions uses a type in com.jetbrains.ls.api.features.
- The types involved
com.jetbrains.ls.api.features.codeActions.LSCodeActionProvider→com.jetbrains.ls.api.features.LSLanguageSpecificConfigurationEntry
- Direction
- com.jetbrains.ls.api.features.codeActions uses com.jetbrains.ls.api.features, so a change to com.jetbrains.ls.api.features can break com.jetbrains.ls.api.features.codeActions, while a change to com.jetbrains.ls.api.features.codeActions can't break com.jetbrains.ls.api.features.
- Position
- Below the diagonal: com.jetbrains.ls.api.features.codeActions uses a module listed above it, which is the healthy direction.
22→1 com.jetbrains.ls.api.features.configuration uses com.jetbrains.ls.api.features.configuration.LSUniqueConfigurationEntry✕
- Connections
- 1 pair of types, where a type in com.jetbrains.ls.api.features.configuration uses a type in com.jetbrains.ls.api.features.configuration.LSUniqueConfigurationEntry.
- The types involved
com.jetbrains.ls.api.features.configuration.LSUniqueConfigurationEntry→com.jetbrains.ls.api.features.configuration.LSUniqueConfigurationEntry.UniqueId
- Direction
- com.jetbrains.ls.api.features.configuration uses com.jetbrains.ls.api.features.configuration.LSUniqueConfigurationEntry, so a change to com.jetbrains.ls.api.features.configuration.LSUniqueConfigurationEntry can break com.jetbrains.ls.api.features.configuration, while a change to com.jetbrains.ls.api.features.configuration can't break com.jetbrains.ls.api.features.configuration.LSUniqueConfigurationEntry.
- Position
- Below the diagonal: com.jetbrains.ls.api.features.configuration uses a module listed above it, which is the healthy direction.
22→15 com.jetbrains.ls.api.features.configuration uses com.jetbrains.ls.api.features✕
- Connections
- 1 pair of types, where a type in com.jetbrains.ls.api.features.configuration uses a type in com.jetbrains.ls.api.features.
- The types involved
com.jetbrains.ls.api.features.configuration.LSUniqueConfigurationEntry→com.jetbrains.ls.api.features.LSConfigurationEntry
- Direction
- com.jetbrains.ls.api.features.configuration uses com.jetbrains.ls.api.features, so a change to com.jetbrains.ls.api.features can break com.jetbrains.ls.api.features.configuration, while a change to com.jetbrains.ls.api.features.configuration can't break com.jetbrains.ls.api.features.
- Position
- Below the diagonal: com.jetbrains.ls.api.features.configuration uses a module listed above it, which is the healthy direction.
23→15 com.jetbrains.ls.api.features.definition uses com.jetbrains.ls.api.features✕
- Connections
- 1 pair of types, where a type in com.jetbrains.ls.api.features.definition uses a type in com.jetbrains.ls.api.features.
- The types involved
com.jetbrains.ls.api.features.definition.LSDefinitionProvider→com.jetbrains.ls.api.features.LSLanguageSpecificConfigurationEntry
- Direction
- com.jetbrains.ls.api.features.definition uses com.jetbrains.ls.api.features, so a change to com.jetbrains.ls.api.features can break com.jetbrains.ls.api.features.definition, while a change to com.jetbrains.ls.api.features.definition can't break com.jetbrains.ls.api.features.
- Position
- Below the diagonal: com.jetbrains.ls.api.features.definition uses a module listed above it, which is the healthy direction.
24→9 com.jetbrains.ls.api.features.impl.common.callHierarchy uses com.jetbrains.ls.api.features.impl.common.callHierarchy.LSCallHierarchyProviderBase✕
- Connections
- 1 pair of types, where a type in com.jetbrains.ls.api.features.impl.common.callHierarchy uses a type in com.jetbrains.ls.api.features.impl.common.callHierarchy.LSCallHierarchyProviderBase.
- The types involved
com.jetbrains.ls.api.features.impl.common.callHierarchy.LSCallHierarchyProviderBase→com.jetbrains.ls.api.features.impl.common.callHierarchy.LSCallHierarchyProviderBase.CallHierarchyItemData
- Direction
- com.jetbrains.ls.api.features.impl.common.callHierarchy uses com.jetbrains.ls.api.features.impl.common.callHierarchy.LSCallHierarchyProviderBase, so a change to com.jetbrains.ls.api.features.impl.common.callHierarchy.LSCallHierarchyProviderBase can break com.jetbrains.ls.api.features.impl.common.callHierarchy, while a change to com.jetbrains.ls.api.features.impl.common.callHierarchy can't break com.jetbrains.ls.api.features.impl.common.callHierarchy.LSCallHierarchyProviderBase.
- Position
- Below the diagonal: com.jetbrains.ls.api.features.impl.common.callHierarchy uses a module listed above it, which is the healthy direction.
24→15 com.jetbrains.ls.api.features.impl.common.callHierarchy uses com.jetbrains.ls.api.features✕
- Connections
- 1 pair of types, where a type in com.jetbrains.ls.api.features.impl.common.callHierarchy uses a type in com.jetbrains.ls.api.features.
- The types involved
com.jetbrains.ls.api.features.impl.common.callHierarchy.LSCallHierarchyRenderer→com.jetbrains.ls.api.features.LSLanguageSpecificConfigurationEntry
- Direction
- com.jetbrains.ls.api.features.impl.common.callHierarchy uses com.jetbrains.ls.api.features, so a change to com.jetbrains.ls.api.features can break com.jetbrains.ls.api.features.impl.common.callHierarchy, while a change to com.jetbrains.ls.api.features.impl.common.callHierarchy can't break com.jetbrains.ls.api.features.
- Position
- Below the diagonal: com.jetbrains.ls.api.features.impl.common.callHierarchy uses a module listed above it, which is the healthy direction.
24→16 com.jetbrains.ls.api.features.impl.common.callHierarchy uses com.jetbrains.ls.api.features.impl.common.callHierarchy.LSCallHierarchyProviderBase.CallHierarchyTarget✕
- Connections
- 1 pair of types, where a type in com.jetbrains.ls.api.features.impl.common.callHierarchy uses a type in com.jetbrains.ls.api.features.impl.common.callHierarchy.LSCallHierarchyProviderBase.CallHierarchyTarget.
- The types involved
com.jetbrains.ls.api.features.impl.common.callHierarchy.LSCallHierarchyProviderBase→com.jetbrains.ls.api.features.impl.common.callHierarchy.LSCallHierarchyProviderBase.CallHierarchyTarget.Declaration
- Direction
- com.jetbrains.ls.api.features.impl.common.callHierarchy uses com.jetbrains.ls.api.features.impl.common.callHierarchy.LSCallHierarchyProviderBase.CallHierarchyTarget, so a change to com.jetbrains.ls.api.features.impl.common.callHierarchy.LSCallHierarchyProviderBase.CallHierarchyTarget can break com.jetbrains.ls.api.features.impl.common.callHierarchy, while a change to com.jetbrains.ls.api.features.impl.common.callHierarchy can't break com.jetbrains.ls.api.features.impl.common.callHierarchy.LSCallHierarchyProviderBase.CallHierarchyTarget.
- Position
- Below the diagonal: com.jetbrains.ls.api.features.impl.common.callHierarchy uses a module listed above it, which is the healthy direction.
25→8 com.jetbrains.ls.api.features.impl.common.modcommands uses com.jetbrains.ls.api.features.commands✕
- Connections
- 2 pairs of types, where a type in com.jetbrains.ls.api.features.impl.common.modcommands uses a type in com.jetbrains.ls.api.features.commands.
- The types involved
com.jetbrains.ls.api.features.impl.common.modcommands.LSApplyFixCommandDescriptorProvider→com.jetbrains.ls.api.features.commands.LSCommandDescriptorcom.jetbrains.ls.api.features.impl.common.modcommands.LSApplyFixCommandDescriptorProvider→com.jetbrains.ls.api.features.commands.LSCommandDescriptorProvider
- Direction
- com.jetbrains.ls.api.features.impl.common.modcommands uses com.jetbrains.ls.api.features.commands, so a change to com.jetbrains.ls.api.features.commands can break com.jetbrains.ls.api.features.impl.common.modcommands, while a change to com.jetbrains.ls.api.features.impl.common.modcommands can't break com.jetbrains.ls.api.features.commands.
- Position
- Below the diagonal: com.jetbrains.ls.api.features.impl.common.modcommands uses a module listed above it, which is the healthy direction.
25→13 com.jetbrains.ls.api.features.impl.common.modcommands uses com.jetbrains.ls.kotlinLsp.requests.core.ModCommandData✕
- Connections
- 3 pairs of types, where a type in com.jetbrains.ls.api.features.impl.common.modcommands uses a type in com.jetbrains.ls.kotlinLsp.requests.core.ModCommandData.
- The types involved
com.jetbrains.ls.api.features.impl.common.modcommands.EditOptionsKt→com.jetbrains.ls.kotlinLsp.requests.core.ModCommandData.EditOptionscom.jetbrains.ls.api.features.impl.common.modcommands.LSApplyFixCommandDescriptorProviderKt→com.jetbrains.ls.kotlinLsp.requests.core.ModCommandData.LazyActioncom.jetbrains.ls.api.features.impl.common.modcommands.LazyFixKt→com.jetbrains.ls.kotlinLsp.requests.core.ModCommandData.LazyAction
- Direction
- com.jetbrains.ls.api.features.impl.common.modcommands uses com.jetbrains.ls.kotlinLsp.requests.core.ModCommandData, so a change to com.jetbrains.ls.kotlinLsp.requests.core.ModCommandData can break com.jetbrains.ls.api.features.impl.common.modcommands, while a change to com.jetbrains.ls.api.features.impl.common.modcommands can't break com.jetbrains.ls.kotlinLsp.requests.core.ModCommandData.
- Position
- Below the diagonal: com.jetbrains.ls.api.features.impl.common.modcommands uses a module listed above it, which is the healthy direction.
25→19 com.jetbrains.ls.api.features.impl.common.modcommands uses com.jetbrains.ls.kotlinLsp.requests.core✕
- Connections
- 2 pairs of types, where a type in com.jetbrains.ls.api.features.impl.common.modcommands uses a type in com.jetbrains.ls.kotlinLsp.requests.core.
- The types involved
com.jetbrains.ls.api.features.impl.common.modcommands.LSApplyFixCommandDescriptorProviderKt→com.jetbrains.ls.kotlinLsp.requests.core.ModCommandDatacom.jetbrains.ls.api.features.impl.common.modcommands.ModCommandFix→com.jetbrains.ls.kotlinLsp.requests.core.ModCommandData
- Direction
- com.jetbrains.ls.api.features.impl.common.modcommands uses com.jetbrains.ls.kotlinLsp.requests.core, so a change to com.jetbrains.ls.kotlinLsp.requests.core can break com.jetbrains.ls.api.features.impl.common.modcommands, while a change to com.jetbrains.ls.api.features.impl.common.modcommands can't break com.jetbrains.ls.kotlinLsp.requests.core.
- Position
- Below the diagonal: com.jetbrains.ls.api.features.impl.common.modcommands uses a module listed above it, which is the healthy direction.
26→15 com.jetbrains.ls.api.features.semanticTokens uses com.jetbrains.ls.api.features✕
- Connections
- 2 pairs of types, where a type in com.jetbrains.ls.api.features.semanticTokens uses a type in com.jetbrains.ls.api.features.
- The types involved
com.jetbrains.ls.api.features.semanticTokens.LSInjectedSemanticTokensFallback→com.jetbrains.ls.api.features.LSConfigurationEntrycom.jetbrains.ls.api.features.semanticTokens.LSSemanticTokensProvider→com.jetbrains.ls.api.features.LSLanguageSpecificConfigurationEntry
- Direction
- com.jetbrains.ls.api.features.semanticTokens uses com.jetbrains.ls.api.features, so a change to com.jetbrains.ls.api.features can break com.jetbrains.ls.api.features.semanticTokens, while a change to com.jetbrains.ls.api.features.semanticTokens can't break com.jetbrains.ls.api.features.
- Position
- Below the diagonal: com.jetbrains.ls.api.features.semanticTokens uses a module listed above it, which is the healthy direction.
27→7 vscode-testing.src.testLanguage uses vscode-testing.src.testProtocol✕
- Connections
- 1 pair of types, where a type in vscode-testing.src.testLanguage uses a type in vscode-testing.src.testProtocol.
- The types involved
vscode-testing.src.testLanguage.UnreportedNodes→vscode-testing.src.testProtocol.TestItemDto
- Direction
- vscode-testing.src.testLanguage uses vscode-testing.src.testProtocol, so a change to vscode-testing.src.testProtocol can break vscode-testing.src.testLanguage, while a change to vscode-testing.src.testLanguage can't break vscode-testing.src.testProtocol.
- Position
- Below the diagonal: vscode-testing.src.testLanguage uses a module listed above it, which is the healthy direction.
27→20 vscode-testing.src.testLanguage uses vscode-testing.src.testRunReport✕
- Connections
- 1 pair of types, where a type in vscode-testing.src.testLanguage uses a type in vscode-testing.src.testRunReport.
- The types involved
vscode-testing.src.testLanguage.TestRunInput→vscode-testing.src.testRunReport.TestRunReport
- Direction
- vscode-testing.src.testLanguage uses vscode-testing.src.testRunReport, so a change to vscode-testing.src.testRunReport can break vscode-testing.src.testLanguage, while a change to vscode-testing.src.testLanguage can't break vscode-testing.src.testRunReport.
- Position
- Below the diagonal: vscode-testing.src.testLanguage uses a module listed above it, which is the healthy direction.
28→15 com.jetbrains.ls.api.features.completion uses com.jetbrains.ls.api.features✕
- Connections
- 1 pair of types, where a type in com.jetbrains.ls.api.features.completion uses a type in com.jetbrains.ls.api.features.
- The types involved
com.jetbrains.ls.api.features.completion.LSCompletionProvider→com.jetbrains.ls.api.features.LSLanguageSpecificConfigurationEntry
- Direction
- com.jetbrains.ls.api.features.completion uses com.jetbrains.ls.api.features, so a change to com.jetbrains.ls.api.features can break com.jetbrains.ls.api.features.completion, while a change to com.jetbrains.ls.api.features.completion can't break com.jetbrains.ls.api.features.
- Position
- Below the diagonal: com.jetbrains.ls.api.features.completion uses a module listed above it, which is the healthy direction.
28→22 com.jetbrains.ls.api.features.completion uses com.jetbrains.ls.api.features.configuration✕
- Connections
- 1 pair of types, where a type in com.jetbrains.ls.api.features.completion uses a type in com.jetbrains.ls.api.features.configuration.
- The types involved
com.jetbrains.ls.api.features.completion.LSCompletionProvider→com.jetbrains.ls.api.features.configuration.LSUniqueConfigurationEntry
- Direction
- com.jetbrains.ls.api.features.completion uses com.jetbrains.ls.api.features.configuration, so a change to com.jetbrains.ls.api.features.configuration can break com.jetbrains.ls.api.features.completion, while a change to com.jetbrains.ls.api.features.completion can't break com.jetbrains.ls.api.features.configuration.
- Position
- Below the diagonal: com.jetbrains.ls.api.features.completion uses a module listed above it, which is the healthy direction.
29→12 com.jetbrains.ls.api.features.impl.common.configuration uses com.jetbrains.ls.api.features.language✕
- Connections
- 2 pairs of types, where a type in com.jetbrains.ls.api.features.impl.common.configuration uses a type in com.jetbrains.ls.api.features.language.
- The types involved
com.jetbrains.ls.api.features.impl.common.configuration.LSCommonConfigurationKt→com.jetbrains.ls.api.features.language.LSConfigurationPiececom.jetbrains.ls.api.features.impl.common.configuration.LSCommonServerExtension→com.jetbrains.ls.api.features.language.LSConfigurationPiece
- Direction
- com.jetbrains.ls.api.features.impl.common.configuration uses com.jetbrains.ls.api.features.language, so a change to com.jetbrains.ls.api.features.language can break com.jetbrains.ls.api.features.impl.common.configuration, while a change to com.jetbrains.ls.api.features.impl.common.configuration can't break com.jetbrains.ls.api.features.language.
- Position
- Below the diagonal: com.jetbrains.ls.api.features.impl.common.configuration uses a module listed above it, which is the healthy direction.
29→15 com.jetbrains.ls.api.features.impl.common.configuration uses com.jetbrains.ls.api.features✕
- Connections
- 1 pair of types, where a type in com.jetbrains.ls.api.features.impl.common.configuration uses a type in com.jetbrains.ls.api.features.
- The types involved
com.jetbrains.ls.api.features.impl.common.configuration.LSCommonServerExtension→com.jetbrains.ls.api.features.LanguageServerExtension
- Direction
- com.jetbrains.ls.api.features.impl.common.configuration uses com.jetbrains.ls.api.features, so a change to com.jetbrains.ls.api.features can break com.jetbrains.ls.api.features.impl.common.configuration, while a change to com.jetbrains.ls.api.features.impl.common.configuration can't break com.jetbrains.ls.api.features.
- Position
- Below the diagonal: com.jetbrains.ls.api.features.impl.common.configuration uses a module listed above it, which is the healthy direction.
29→25 com.jetbrains.ls.api.features.impl.common.configuration uses com.jetbrains.ls.api.features.impl.common.modcommands✕
- Connections
- 1 pair of types, where a type in com.jetbrains.ls.api.features.impl.common.configuration uses a type in com.jetbrains.ls.api.features.impl.common.modcommands.
- The types involved
com.jetbrains.ls.api.features.impl.common.configuration.LSCurrentProfileOptionsCommandProvider→com.jetbrains.ls.api.features.impl.common.modcommands.LSSystemOptionsCommandProvider
- Direction
- com.jetbrains.ls.api.features.impl.common.configuration uses com.jetbrains.ls.api.features.impl.common.modcommands, so a change to com.jetbrains.ls.api.features.impl.common.modcommands can break com.jetbrains.ls.api.features.impl.common.configuration, while a change to com.jetbrains.ls.api.features.impl.common.configuration can't break com.jetbrains.ls.api.features.impl.common.modcommands.
- Position
- Below the diagonal: com.jetbrains.ls.api.features.impl.common.configuration uses a module listed above it, which is the healthy direction.
30→12 com.jetbrains.ls.api.features.impl.common.diagnostics uses com.jetbrains.ls.api.features.language✕
- Connections
- 7 pairs of types, where a type in com.jetbrains.ls.api.features.impl.common.diagnostics uses a type in com.jetbrains.ls.api.features.language.
- The types involved
com.jetbrains.ls.api.features.impl.common.diagnostics.LSCommonInjectionInspectionDiagnosticProvider→com.jetbrains.ls.api.features.language.LSLanguagecom.jetbrains.ls.api.features.impl.common.diagnostics.LSCommonInjectionSyntaxErrorDiagnosticProvider→com.jetbrains.ls.api.features.language.LSLanguagecom.jetbrains.ls.api.features.impl.common.diagnostics.LSCommonInspectionDiagnosticProvider→com.jetbrains.ls.api.features.language.LSLanguagecom.jetbrains.ls.api.features.impl.common.diagnostics.LSCommonInspectionFixesCodeActionProvider→com.jetbrains.ls.api.features.language.LSLanguagecom.jetbrains.ls.api.features.impl.common.diagnostics.LSCommonInspectionOptionsCodeActionProvider→com.jetbrains.ls.api.features.language.LSLanguagecom.jetbrains.ls.api.features.impl.common.diagnostics.LSCommonIntentionFixesCodeActionProvider→com.jetbrains.ls.api.features.language.LSLanguagecom.jetbrains.ls.api.features.impl.common.diagnostics.LSCommonSyntaxErrorDiagnosticProvider→com.jetbrains.ls.api.features.language.LSLanguage
- Direction
- com.jetbrains.ls.api.features.impl.common.diagnostics uses com.jetbrains.ls.api.features.language, so a change to com.jetbrains.ls.api.features.language can break com.jetbrains.ls.api.features.impl.common.diagnostics, while a change to com.jetbrains.ls.api.features.impl.common.diagnostics can't break com.jetbrains.ls.api.features.language.
- Position
- Below the diagonal: com.jetbrains.ls.api.features.impl.common.diagnostics uses a module listed above it, which is the healthy direction.
30→19 com.jetbrains.ls.api.features.impl.common.diagnostics uses com.jetbrains.ls.kotlinLsp.requests.core✕
- Connections
- 1 pair of types, where a type in com.jetbrains.ls.api.features.impl.common.diagnostics uses a type in com.jetbrains.ls.kotlinLsp.requests.core.
- The types involved
com.jetbrains.ls.api.features.impl.common.diagnostics.SimpleDiagnosticQuickfixData→com.jetbrains.ls.kotlinLsp.requests.core.ModCommandData
- Direction
- com.jetbrains.ls.api.features.impl.common.diagnostics uses com.jetbrains.ls.kotlinLsp.requests.core, so a change to com.jetbrains.ls.kotlinLsp.requests.core can break com.jetbrains.ls.api.features.impl.common.diagnostics, while a change to com.jetbrains.ls.api.features.impl.common.diagnostics can't break com.jetbrains.ls.kotlinLsp.requests.core.
- Position
- Below the diagonal: com.jetbrains.ls.api.features.impl.common.diagnostics uses a module listed above it, which is the healthy direction.
30→21 com.jetbrains.ls.api.features.impl.common.diagnostics uses com.jetbrains.ls.api.features.codeActions✕
- Connections
- 4 pairs of types, where a type in com.jetbrains.ls.api.features.impl.common.diagnostics uses a type in com.jetbrains.ls.api.features.codeActions.
- The types involved
com.jetbrains.ls.api.features.impl.common.diagnostics.LSCommonInspectionFixesCodeActionProvider→com.jetbrains.ls.api.features.codeActions.LSCodeActionProvidercom.jetbrains.ls.api.features.impl.common.diagnostics.LSCommonInspectionOptionsCodeActionProvider→com.jetbrains.ls.api.features.codeActions.LSCodeActionGroupcom.jetbrains.ls.api.features.impl.common.diagnostics.LSCommonInspectionOptionsCodeActionProvider→com.jetbrains.ls.api.features.codeActions.LSCodeActionProvidercom.jetbrains.ls.api.features.impl.common.diagnostics.LSCommonIntentionFixesCodeActionProvider→com.jetbrains.ls.api.features.codeActions.LSCodeActionProvider
- Direction
- com.jetbrains.ls.api.features.impl.common.diagnostics uses com.jetbrains.ls.api.features.codeActions, so a change to com.jetbrains.ls.api.features.codeActions can break com.jetbrains.ls.api.features.impl.common.diagnostics, while a change to com.jetbrains.ls.api.features.impl.common.diagnostics can't break com.jetbrains.ls.api.features.codeActions.
- Position
- Below the diagonal: com.jetbrains.ls.api.features.impl.common.diagnostics uses a module listed above it, which is the healthy direction.
30→25 com.jetbrains.ls.api.features.impl.common.diagnostics uses com.jetbrains.ls.api.features.impl.common.modcommands✕
- Connections
- 3 pairs of types, where a type in com.jetbrains.ls.api.features.impl.common.diagnostics uses a type in com.jetbrains.ls.api.features.impl.common.modcommands.
- The types involved
com.jetbrains.ls.api.features.impl.common.diagnostics.DiagnosticDataKt→com.jetbrains.ls.api.features.impl.common.modcommands.DocumentStampcom.jetbrains.ls.api.features.impl.common.diagnostics.LSInspectionManager→com.jetbrains.ls.api.features.impl.common.modcommands.LazyFixcom.jetbrains.ls.api.features.impl.common.diagnostics.SimpleDiagnosticQuickfixData→com.jetbrains.ls.api.features.impl.common.modcommands.DocumentStamp
- Direction
- com.jetbrains.ls.api.features.impl.common.diagnostics uses com.jetbrains.ls.api.features.impl.common.modcommands, so a change to com.jetbrains.ls.api.features.impl.common.modcommands can break com.jetbrains.ls.api.features.impl.common.diagnostics, while a change to com.jetbrains.ls.api.features.impl.common.diagnostics can't break com.jetbrains.ls.api.features.impl.common.modcommands.
- Position
- Below the diagonal: com.jetbrains.ls.api.features.impl.common.diagnostics uses a module listed above it, which is the healthy direction.
31→3 com.jetbrains.ls.api.features.impl.common.utils uses com.jetbrains.ls.api.features.impl.common.utils.LSRefactoringMemberProviderBase✕
- Connections
- 3 pairs of types, where a type in com.jetbrains.ls.api.features.impl.common.utils uses a type in com.jetbrains.ls.api.features.impl.common.utils.LSRefactoringMemberProviderBase.
- The types involved
com.jetbrains.ls.api.features.impl.common.utils.LSRefactoringMemberProviderBase→com.jetbrains.ls.api.features.impl.common.utils.LSRefactoringMemberProviderBase.ChoicesResultcom.jetbrains.ls.api.features.impl.common.utils.LSRefactoringMemberProviderBase→com.jetbrains.ls.api.features.impl.common.utils.LSRefactoringMemberProviderBase.Payloadcom.jetbrains.ls.api.features.impl.common.utils.LSRefactoringMemberProviderBase→com.jetbrains.ls.api.features.impl.common.utils.LSRefactoringMemberProviderBase.RefactoringResult
- Direction
- com.jetbrains.ls.api.features.impl.common.utils uses com.jetbrains.ls.api.features.impl.common.utils.LSRefactoringMemberProviderBase, so a change to com.jetbrains.ls.api.features.impl.common.utils.LSRefactoringMemberProviderBase can break com.jetbrains.ls.api.features.impl.common.utils, while a change to com.jetbrains.ls.api.features.impl.common.utils can't break com.jetbrains.ls.api.features.impl.common.utils.LSRefactoringMemberProviderBase.
- Position
- Below the diagonal: com.jetbrains.ls.api.features.impl.common.utils uses a module listed above it, which is the healthy direction.
31→8 com.jetbrains.ls.api.features.impl.common.utils uses com.jetbrains.ls.api.features.commands✕
- Connections
- 2 pairs of types, where a type in com.jetbrains.ls.api.features.impl.common.utils uses a type in com.jetbrains.ls.api.features.commands.
- The types involved
com.jetbrains.ls.api.features.impl.common.utils.LSRefactoringMemberProviderBase→com.jetbrains.ls.api.features.commands.LSCommandDescriptorcom.jetbrains.ls.api.features.impl.common.utils.LSRefactoringMemberProviderBase→com.jetbrains.ls.api.features.commands.LSCommandDescriptorProvider
- Direction
- com.jetbrains.ls.api.features.impl.common.utils uses com.jetbrains.ls.api.features.commands, so a change to com.jetbrains.ls.api.features.commands can break com.jetbrains.ls.api.features.impl.common.utils, while a change to com.jetbrains.ls.api.features.impl.common.utils can't break com.jetbrains.ls.api.features.commands.
- Position
- Below the diagonal: com.jetbrains.ls.api.features.impl.common.utils uses a module listed above it, which is the healthy direction.
31→21 com.jetbrains.ls.api.features.impl.common.utils uses com.jetbrains.ls.api.features.codeActions✕
- Connections
- 1 pair of types, where a type in com.jetbrains.ls.api.features.impl.common.utils uses a type in com.jetbrains.ls.api.features.codeActions.
- The types involved
com.jetbrains.ls.api.features.impl.common.utils.LSRefactoringMemberProviderBase→com.jetbrains.ls.api.features.codeActions.LSCodeActionProvider
- Direction
- com.jetbrains.ls.api.features.impl.common.utils uses com.jetbrains.ls.api.features.codeActions, so a change to com.jetbrains.ls.api.features.codeActions can break com.jetbrains.ls.api.features.impl.common.utils, while a change to com.jetbrains.ls.api.features.impl.common.utils can't break com.jetbrains.ls.api.features.codeActions.
- Position
- Below the diagonal: com.jetbrains.ls.api.features.impl.common.utils uses a module listed above it, which is the healthy direction.
32→8 com.jetbrains.ls.api.features.impl.kotlin.inline uses com.jetbrains.ls.api.features.commands✕
- Connections
- 2 pairs of types, where a type in com.jetbrains.ls.api.features.impl.kotlin.inline uses a type in com.jetbrains.ls.api.features.commands.
- The types involved
com.jetbrains.ls.api.features.impl.kotlin.inline.LSKotlinInlineVariableProvider→com.jetbrains.ls.api.features.commands.LSCommandDescriptorcom.jetbrains.ls.api.features.impl.kotlin.inline.LSKotlinInlineVariableProvider→com.jetbrains.ls.api.features.commands.LSCommandDescriptorProvider
- Direction
- com.jetbrains.ls.api.features.impl.kotlin.inline uses com.jetbrains.ls.api.features.commands, so a change to com.jetbrains.ls.api.features.commands can break com.jetbrains.ls.api.features.impl.kotlin.inline, while a change to com.jetbrains.ls.api.features.impl.kotlin.inline can't break com.jetbrains.ls.api.features.commands.
- Position
- Below the diagonal: com.jetbrains.ls.api.features.impl.kotlin.inline uses a module listed above it, which is the healthy direction.
32→12 com.jetbrains.ls.api.features.impl.kotlin.inline uses com.jetbrains.ls.api.features.language✕
- Connections
- 1 pair of types, where a type in com.jetbrains.ls.api.features.impl.kotlin.inline uses a type in com.jetbrains.ls.api.features.language.
- The types involved
com.jetbrains.ls.api.features.impl.kotlin.inline.LSKotlinInlineVariableProvider→com.jetbrains.ls.api.features.language.LSLanguage
- Direction
- com.jetbrains.ls.api.features.impl.kotlin.inline uses com.jetbrains.ls.api.features.language, so a change to com.jetbrains.ls.api.features.language can break com.jetbrains.ls.api.features.impl.kotlin.inline, while a change to com.jetbrains.ls.api.features.impl.kotlin.inline can't break com.jetbrains.ls.api.features.language.
- Position
- Below the diagonal: com.jetbrains.ls.api.features.impl.kotlin.inline uses a module listed above it, which is the healthy direction.
32→21 com.jetbrains.ls.api.features.impl.kotlin.inline uses com.jetbrains.ls.api.features.codeActions✕
- Connections
- 1 pair of types, where a type in com.jetbrains.ls.api.features.impl.kotlin.inline uses a type in com.jetbrains.ls.api.features.codeActions.
- The types involved
com.jetbrains.ls.api.features.impl.kotlin.inline.LSKotlinInlineVariableProvider→com.jetbrains.ls.api.features.codeActions.LSCodeActionProvider
- Direction
- com.jetbrains.ls.api.features.impl.kotlin.inline uses com.jetbrains.ls.api.features.codeActions, so a change to com.jetbrains.ls.api.features.codeActions can break com.jetbrains.ls.api.features.impl.kotlin.inline, while a change to com.jetbrains.ls.api.features.impl.kotlin.inline can't break com.jetbrains.ls.api.features.codeActions.
- Position
- Below the diagonal: com.jetbrains.ls.api.features.impl.kotlin.inline uses a module listed above it, which is the healthy direction.
32→25 com.jetbrains.ls.api.features.impl.kotlin.inline uses com.jetbrains.ls.api.features.impl.common.modcommands✕
- Connections
- 1 pair of types, where a type in com.jetbrains.ls.api.features.impl.kotlin.inline uses a type in com.jetbrains.ls.api.features.impl.common.modcommands.
- The types involved
com.jetbrains.ls.api.features.impl.kotlin.inline.LSKotlinInlineVariableProvider→com.jetbrains.ls.api.features.impl.common.modcommands.DocumentStamp
- Direction
- com.jetbrains.ls.api.features.impl.kotlin.inline uses com.jetbrains.ls.api.features.impl.common.modcommands, so a change to com.jetbrains.ls.api.features.impl.common.modcommands can break com.jetbrains.ls.api.features.impl.kotlin.inline, while a change to com.jetbrains.ls.api.features.impl.kotlin.inline can't break com.jetbrains.ls.api.features.impl.common.modcommands.
- Position
- Below the diagonal: com.jetbrains.ls.api.features.impl.kotlin.inline uses a module listed above it, which is the healthy direction.
33→1 com.jetbrains.ls.api.features.impl.kotlin.typeHierarchy uses com.jetbrains.ls.api.features.configuration.LSUniqueConfigurationEntry✕
- Connections
- 1 pair of types, where a type in com.jetbrains.ls.api.features.impl.kotlin.typeHierarchy uses a type in com.jetbrains.ls.api.features.configuration.LSUniqueConfigurationEntry.
- The types involved
com.jetbrains.ls.api.features.impl.kotlin.typeHierarchy.LSKotlinTypeHierarchyProvider→com.jetbrains.ls.api.features.configuration.LSUniqueConfigurationEntry.UniqueId
- Direction
- com.jetbrains.ls.api.features.impl.kotlin.typeHierarchy uses com.jetbrains.ls.api.features.configuration.LSUniqueConfigurationEntry, so a change to com.jetbrains.ls.api.features.configuration.LSUniqueConfigurationEntry can break com.jetbrains.ls.api.features.impl.kotlin.typeHierarchy, while a change to com.jetbrains.ls.api.features.impl.kotlin.typeHierarchy can't break com.jetbrains.ls.api.features.configuration.LSUniqueConfigurationEntry.
- Position
- Below the diagonal: com.jetbrains.ls.api.features.impl.kotlin.typeHierarchy uses a module listed above it, which is the healthy direction.
33→11 com.jetbrains.ls.api.features.impl.kotlin.typeHierarchy uses com.jetbrains.ls.api.features.impl.kotlin.typeHierarchy.LSKotlinTypeHierarchyProvider✕
- Connections
- 1 pair of types, where a type in com.jetbrains.ls.api.features.impl.kotlin.typeHierarchy uses a type in com.jetbrains.ls.api.features.impl.kotlin.typeHierarchy.LSKotlinTypeHierarchyProvider.
- The types involved
com.jetbrains.ls.api.features.impl.kotlin.typeHierarchy.LSKotlinTypeHierarchyProvider→com.jetbrains.ls.api.features.impl.kotlin.typeHierarchy.LSKotlinTypeHierarchyProvider.ItemLocation
- Direction
- com.jetbrains.ls.api.features.impl.kotlin.typeHierarchy uses com.jetbrains.ls.api.features.impl.kotlin.typeHierarchy.LSKotlinTypeHierarchyProvider, so a change to com.jetbrains.ls.api.features.impl.kotlin.typeHierarchy.LSKotlinTypeHierarchyProvider can break com.jetbrains.ls.api.features.impl.kotlin.typeHierarchy, while a change to com.jetbrains.ls.api.features.impl.kotlin.typeHierarchy can't break com.jetbrains.ls.api.features.impl.kotlin.typeHierarchy.LSKotlinTypeHierarchyProvider.
- Position
- Below the diagonal: com.jetbrains.ls.api.features.impl.kotlin.typeHierarchy uses a module listed above it, which is the healthy direction.
33→12 com.jetbrains.ls.api.features.impl.kotlin.typeHierarchy uses com.jetbrains.ls.api.features.language✕
- Connections
- 1 pair of types, where a type in com.jetbrains.ls.api.features.impl.kotlin.typeHierarchy uses a type in com.jetbrains.ls.api.features.language.
- The types involved
com.jetbrains.ls.api.features.impl.kotlin.typeHierarchy.LSKotlinTypeHierarchyProvider→com.jetbrains.ls.api.features.language.LSLanguage
- Direction
- com.jetbrains.ls.api.features.impl.kotlin.typeHierarchy uses com.jetbrains.ls.api.features.language, so a change to com.jetbrains.ls.api.features.language can break com.jetbrains.ls.api.features.impl.kotlin.typeHierarchy, while a change to com.jetbrains.ls.api.features.impl.kotlin.typeHierarchy can't break com.jetbrains.ls.api.features.language.
- Position
- Below the diagonal: com.jetbrains.ls.api.features.impl.kotlin.typeHierarchy uses a module listed above it, which is the healthy direction.
33→22 com.jetbrains.ls.api.features.impl.kotlin.typeHierarchy uses com.jetbrains.ls.api.features.configuration✕
- Connections
- 1 pair of types, where a type in com.jetbrains.ls.api.features.impl.kotlin.typeHierarchy uses a type in com.jetbrains.ls.api.features.configuration.
- The types involved
com.jetbrains.ls.api.features.impl.kotlin.typeHierarchy.LSKotlinTypeHierarchyProvider→com.jetbrains.ls.api.features.configuration.LSUniqueConfigurationEntry
- Direction
- com.jetbrains.ls.api.features.impl.kotlin.typeHierarchy uses com.jetbrains.ls.api.features.configuration, so a change to com.jetbrains.ls.api.features.configuration can break com.jetbrains.ls.api.features.impl.kotlin.typeHierarchy, while a change to com.jetbrains.ls.api.features.impl.kotlin.typeHierarchy can't break com.jetbrains.ls.api.features.configuration.
- Position
- Below the diagonal: com.jetbrains.ls.api.features.impl.kotlin.typeHierarchy uses a module listed above it, which is the healthy direction.
34→20 vscode-jvm-testing.src uses vscode-testing.src.testRunReport✕
- Connections
- 1 pair of types, where a type in vscode-jvm-testing.src uses a type in vscode-testing.src.testRunReport.
- The types involved
vscode-jvm-testing.src.jvmTestBuild→vscode-testing.src.testRunReport.TestRunReport
- Direction
- vscode-jvm-testing.src uses vscode-testing.src.testRunReport, so a change to vscode-testing.src.testRunReport can break vscode-jvm-testing.src, while a change to vscode-jvm-testing.src can't break vscode-testing.src.testRunReport.
- Position
- Below the diagonal: vscode-jvm-testing.src uses a module listed above it, which is the healthy direction.
34→27 vscode-jvm-testing.src uses vscode-testing.src.testLanguage✕
- Connections
- 1 pair of types, where a type in vscode-jvm-testing.src uses a type in vscode-testing.src.testLanguage.
- The types involved
vscode-jvm-testing.src.jvmTestLanguage→vscode-testing.src.testLanguage.TestRunGroup
- Direction
- vscode-jvm-testing.src uses vscode-testing.src.testLanguage, so a change to vscode-testing.src.testLanguage can break vscode-jvm-testing.src, while a change to vscode-jvm-testing.src can't break vscode-testing.src.testLanguage.
- Position
- Below the diagonal: vscode-jvm-testing.src uses a module listed above it, which is the healthy direction.
35→7 vscode-testing.src uses vscode-testing.src.testProtocol✕
- Connections
- 5 pairs of types, where a type in vscode-testing.src uses a type in vscode-testing.src.testProtocol.
- The types involved
vscode-testing.src.testGrouping→vscode-testing.src.testProtocol.TestItemDtovscode-testing.src.testPlan→vscode-testing.src.testProtocol.TestItemDtovscode-testing.src.testRunFixture→vscode-testing.src.testProtocol.TestItemDtovscode-testing.src.testScope→vscode-testing.src.testProtocol.TestItemDtovscode-testing.src.testTree→vscode-testing.src.testProtocol.TestItemDto
- Direction
- vscode-testing.src uses vscode-testing.src.testProtocol, so a change to vscode-testing.src.testProtocol can break vscode-testing.src, while a change to vscode-testing.src can't break vscode-testing.src.testProtocol.
- Position
- Below the diagonal: vscode-testing.src uses a module listed above it, which is the healthy direction.
35→14 vscode-testing.src uses vscode-testing.src.testTree✕
- Connections
- 2 pairs of types, where a type in vscode-testing.src uses a type in vscode-testing.src.testTree.
- The types involved
vscode-testing.src.testPlan→vscode-testing.src.testTree.TestTreevscode-testing.src.testTree→vscode-testing.src.testTree.TestEntry
- Direction
- vscode-testing.src uses vscode-testing.src.testTree, so a change to vscode-testing.src.testTree can break vscode-testing.src, while a change to vscode-testing.src can't break vscode-testing.src.testTree.
- Position
- Below the diagonal: vscode-testing.src uses a module listed above it, which is the healthy direction.
35→27 vscode-testing.src uses vscode-testing.src.testLanguage✕
- Connections
- 4 pairs of types, where a type in vscode-testing.src uses a type in vscode-testing.src.testLanguage.
- The types involved
vscode-testing.src.debugAdapterRunner→vscode-testing.src.testLanguage.TestRunnervscode-testing.src.lspDiscovery→vscode-testing.src.testLanguage.TestDiscoveryvscode-testing.src.module→vscode-testing.src.testLanguage.TestLanguagevscode-testing.src.testController→vscode-testing.src.testLanguage.TestLanguage
- Direction
- vscode-testing.src uses vscode-testing.src.testLanguage, so a change to vscode-testing.src.testLanguage can break vscode-testing.src, while a change to vscode-testing.src can't break vscode-testing.src.testLanguage.
- Position
- Below the diagonal: vscode-testing.src uses a module listed above it, which is the healthy direction.
36→12 com.jetbrains.ls.api.features.impl.common.completion.LSCompletionProviderHelper uses com.jetbrains.ls.api.features.language✕
- Connections
- 1 pair of types, where a type in com.jetbrains.ls.api.features.impl.common.completion.LSCompletionProviderHelper uses a type in com.jetbrains.ls.api.features.language.
- The types involved
com.jetbrains.ls.api.features.impl.common.completion.LSCompletionProviderHelper.CompletionCandidate→com.jetbrains.ls.api.features.language.LSLanguage
- Direction
- com.jetbrains.ls.api.features.impl.common.completion.LSCompletionProviderHelper uses com.jetbrains.ls.api.features.language, so a change to com.jetbrains.ls.api.features.language can break com.jetbrains.ls.api.features.impl.common.completion.LSCompletionProviderHelper, while a change to com.jetbrains.ls.api.features.impl.common.completion.LSCompletionProviderHelper can't break com.jetbrains.ls.api.features.language.
- Position
- Below the diagonal: com.jetbrains.ls.api.features.impl.common.completion.LSCompletionProviderHelper uses a module listed above it, which is the healthy direction.
36→28 com.jetbrains.ls.api.features.impl.common.completion.LSCompletionProviderHelper uses com.jetbrains.ls.api.features.completion✕
- Connections
- 1 pair of types, where a type in com.jetbrains.ls.api.features.impl.common.completion.LSCompletionProviderHelper uses a type in com.jetbrains.ls.api.features.completion.
- The types involved
com.jetbrains.ls.api.features.impl.common.completion.LSCompletionProviderHelper.CompletionCandidate→com.jetbrains.ls.api.features.completion.LSCompletionCandidate
- Direction
- com.jetbrains.ls.api.features.impl.common.completion.LSCompletionProviderHelper uses com.jetbrains.ls.api.features.completion, so a change to com.jetbrains.ls.api.features.completion can break com.jetbrains.ls.api.features.impl.common.completion.LSCompletionProviderHelper, while a change to com.jetbrains.ls.api.features.impl.common.completion.LSCompletionProviderHelper can't break com.jetbrains.ls.api.features.completion.
- Position
- Below the diagonal: com.jetbrains.ls.api.features.impl.common.completion.LSCompletionProviderHelper uses a module listed above it, which is the healthy direction.
36→39 com.jetbrains.ls.api.features.impl.common.completion.LSCompletionProviderHelper uses com.jetbrains.ls.api.features.impl.common.completion part of a loop✕
- Connections
- 1 pair of types, where a type in com.jetbrains.ls.api.features.impl.common.completion.LSCompletionProviderHelper uses a type in com.jetbrains.ls.api.features.impl.common.completion.
- The types involved
com.jetbrains.ls.api.features.impl.common.completion.LSCompletionProviderHelper.CompletionEntry→com.jetbrains.ls.api.features.impl.common.completion.LSCompletion
- Direction
- com.jetbrains.ls.api.features.impl.common.completion.LSCompletionProviderHelper uses com.jetbrains.ls.api.features.impl.common.completion, so a change to com.jetbrains.ls.api.features.impl.common.completion can break com.jetbrains.ls.api.features.impl.common.completion.LSCompletionProviderHelper, while a change to com.jetbrains.ls.api.features.impl.common.completion.LSCompletionProviderHelper can't break com.jetbrains.ls.api.features.impl.common.completion.
- 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.
37→12 com.jetbrains.ls.api.features.impl.javaBase uses com.jetbrains.ls.api.features.language✕
- Connections
- 6 pairs of types, where a type in com.jetbrains.ls.api.features.impl.javaBase uses a type in com.jetbrains.ls.api.features.language.
- The types involved
com.jetbrains.ls.api.features.impl.javaBase.JavaBaseLanguageServerExtension→com.jetbrains.ls.api.features.language.LSConfigurationPiececom.jetbrains.ls.api.features.impl.javaBase.LSJavaBaseLanguageConfigurationKt→com.jetbrains.ls.api.features.language.LSConfigurationPiececom.jetbrains.ls.api.features.impl.javaBase.LSJavaHoverProvider→com.jetbrains.ls.api.features.language.LSLanguagecom.jetbrains.ls.api.features.impl.javaBase.LSJavaLanguageKt→com.jetbrains.ls.api.features.language.LSLanguagecom.jetbrains.ls.api.features.impl.javaBase.LSJavaPackageDefinitionProvider→com.jetbrains.ls.api.features.language.LSLanguagecom.jetbrains.ls.api.features.impl.javaBase.LSJavaRunMainCodeLensProvider→com.jetbrains.ls.api.features.language.LSLanguage
- Direction
- com.jetbrains.ls.api.features.impl.javaBase uses com.jetbrains.ls.api.features.language, so a change to com.jetbrains.ls.api.features.language can break com.jetbrains.ls.api.features.impl.javaBase, while a change to com.jetbrains.ls.api.features.impl.javaBase can't break com.jetbrains.ls.api.features.language.
- Position
- Below the diagonal: com.jetbrains.ls.api.features.impl.javaBase uses a module listed above it, which is the healthy direction.
37→15 com.jetbrains.ls.api.features.impl.javaBase uses com.jetbrains.ls.api.features✕
- Connections
- 1 pair of types, where a type in com.jetbrains.ls.api.features.impl.javaBase uses a type in com.jetbrains.ls.api.features.
- The types involved
com.jetbrains.ls.api.features.impl.javaBase.JavaBaseLanguageServerExtension→com.jetbrains.ls.api.features.LanguageServerExtension
- Direction
- com.jetbrains.ls.api.features.impl.javaBase uses com.jetbrains.ls.api.features, so a change to com.jetbrains.ls.api.features can break com.jetbrains.ls.api.features.impl.javaBase, while a change to com.jetbrains.ls.api.features.impl.javaBase can't break com.jetbrains.ls.api.features.
- Position
- Below the diagonal: com.jetbrains.ls.api.features.impl.javaBase uses a module listed above it, which is the healthy direction.
37→17 com.jetbrains.ls.api.features.impl.javaBase uses com.jetbrains.ls.api.features.impl.common.codeLens✕
- Connections
- 1 pair of types, where a type in com.jetbrains.ls.api.features.impl.javaBase uses a type in com.jetbrains.ls.api.features.impl.common.codeLens.
- The types involved
com.jetbrains.ls.api.features.impl.javaBase.LSJavaRunMainCodeLensProvider→com.jetbrains.ls.api.features.impl.common.codeLens.LSJvmRunMainCodeLensProvider
- Direction
- com.jetbrains.ls.api.features.impl.javaBase uses com.jetbrains.ls.api.features.impl.common.codeLens, so a change to com.jetbrains.ls.api.features.impl.common.codeLens can break com.jetbrains.ls.api.features.impl.javaBase, while a change to com.jetbrains.ls.api.features.impl.javaBase can't break com.jetbrains.ls.api.features.impl.common.codeLens.
- Position
- Below the diagonal: com.jetbrains.ls.api.features.impl.javaBase uses a module listed above it, which is the healthy direction.
37→23 com.jetbrains.ls.api.features.impl.javaBase uses com.jetbrains.ls.api.features.definition✕
- Connections
- 1 pair of types, where a type in com.jetbrains.ls.api.features.impl.javaBase uses a type in com.jetbrains.ls.api.features.definition.
- The types involved
com.jetbrains.ls.api.features.impl.javaBase.LSJavaPackageDefinitionProvider→com.jetbrains.ls.api.features.definition.LSDefinitionProvider
- Direction
- com.jetbrains.ls.api.features.impl.javaBase uses com.jetbrains.ls.api.features.definition, so a change to com.jetbrains.ls.api.features.definition can break com.jetbrains.ls.api.features.impl.javaBase, while a change to com.jetbrains.ls.api.features.impl.javaBase can't break com.jetbrains.ls.api.features.definition.
- Position
- Below the diagonal: com.jetbrains.ls.api.features.impl.javaBase uses a module listed above it, which is the healthy direction.
37→28 com.jetbrains.ls.api.features.impl.javaBase uses com.jetbrains.ls.api.features.completion✕
- Connections
- 2 pairs of types, where a type in com.jetbrains.ls.api.features.impl.javaBase uses a type in com.jetbrains.ls.api.features.completion.
- The types involved
com.jetbrains.ls.api.features.impl.javaBase.LSJavaCompletionItemKindProvider→com.jetbrains.ls.api.features.completion.LSCompletionCandidatecom.jetbrains.ls.api.features.impl.javaBase.LSJavaCompletionItemKindProvider→com.jetbrains.ls.api.features.completion.LSCompletionItemKindProvider
- Direction
- com.jetbrains.ls.api.features.impl.javaBase uses com.jetbrains.ls.api.features.completion, so a change to com.jetbrains.ls.api.features.completion can break com.jetbrains.ls.api.features.impl.javaBase, while a change to com.jetbrains.ls.api.features.impl.javaBase can't break com.jetbrains.ls.api.features.completion.
- Position
- Below the diagonal: com.jetbrains.ls.api.features.impl.javaBase uses a module listed above it, which is the healthy direction.
38→4 com.jetbrains.ls.api.features.impl.kotlin.diagnostics.compiler uses com.jetbrains.ls.api.features.utils✕
- Connections
- 1 pair of types, where a type in com.jetbrains.ls.api.features.impl.kotlin.diagnostics.compiler uses a type in com.jetbrains.ls.api.features.utils.
- The types involved
com.jetbrains.ls.api.features.impl.kotlin.diagnostics.compiler.KotlinCompilerDiagnosticData→com.jetbrains.ls.api.features.utils.PsiSerializablePointer
- Direction
- com.jetbrains.ls.api.features.impl.kotlin.diagnostics.compiler uses com.jetbrains.ls.api.features.utils, so a change to com.jetbrains.ls.api.features.utils can break com.jetbrains.ls.api.features.impl.kotlin.diagnostics.compiler, while a change to com.jetbrains.ls.api.features.impl.kotlin.diagnostics.compiler can't break com.jetbrains.ls.api.features.utils.
- Position
- Below the diagonal: com.jetbrains.ls.api.features.impl.kotlin.diagnostics.compiler uses a module listed above it, which is the healthy direction.
38→8 com.jetbrains.ls.api.features.impl.kotlin.diagnostics.compiler uses com.jetbrains.ls.api.features.commands✕
- Connections
- 2 pairs of types, where a type in com.jetbrains.ls.api.features.impl.kotlin.diagnostics.compiler uses a type in com.jetbrains.ls.api.features.commands.
- The types involved
com.jetbrains.ls.api.features.impl.kotlin.diagnostics.compiler.LSKotlinCompilerDiagnosticsFixesCodeActionProvider→com.jetbrains.ls.api.features.commands.LSCommandDescriptorcom.jetbrains.ls.api.features.impl.kotlin.diagnostics.compiler.LSKotlinCompilerDiagnosticsFixesCodeActionProvider→com.jetbrains.ls.api.features.commands.LSCommandDescriptorProvider
- Direction
- com.jetbrains.ls.api.features.impl.kotlin.diagnostics.compiler uses com.jetbrains.ls.api.features.commands, so a change to com.jetbrains.ls.api.features.commands can break com.jetbrains.ls.api.features.impl.kotlin.diagnostics.compiler, while a change to com.jetbrains.ls.api.features.impl.kotlin.diagnostics.compiler can't break com.jetbrains.ls.api.features.commands.
- Position
- Below the diagonal: com.jetbrains.ls.api.features.impl.kotlin.diagnostics.compiler uses a module listed above it, which is the healthy direction.
38→12 com.jetbrains.ls.api.features.impl.kotlin.diagnostics.compiler uses com.jetbrains.ls.api.features.language✕
- Connections
- 2 pairs of types, where a type in com.jetbrains.ls.api.features.impl.kotlin.diagnostics.compiler uses a type in com.jetbrains.ls.api.features.language.
- The types involved
com.jetbrains.ls.api.features.impl.kotlin.diagnostics.compiler.LSKotlinCompilerDiagnosticsFixesCodeActionProvider→com.jetbrains.ls.api.features.language.LSLanguagecom.jetbrains.ls.api.features.impl.kotlin.diagnostics.compiler.LSKotlinCompilerDiagnosticsProvider→com.jetbrains.ls.api.features.language.LSLanguage
- Direction
- com.jetbrains.ls.api.features.impl.kotlin.diagnostics.compiler uses com.jetbrains.ls.api.features.language, so a change to com.jetbrains.ls.api.features.language can break com.jetbrains.ls.api.features.impl.kotlin.diagnostics.compiler, while a change to com.jetbrains.ls.api.features.impl.kotlin.diagnostics.compiler can't break com.jetbrains.ls.api.features.language.
- Position
- Below the diagonal: com.jetbrains.ls.api.features.impl.kotlin.diagnostics.compiler uses a module listed above it, which is the healthy direction.
38→21 com.jetbrains.ls.api.features.impl.kotlin.diagnostics.compiler uses com.jetbrains.ls.api.features.codeActions✕
- Connections
- 1 pair of types, where a type in com.jetbrains.ls.api.features.impl.kotlin.diagnostics.compiler uses a type in com.jetbrains.ls.api.features.codeActions.
- The types involved
com.jetbrains.ls.api.features.impl.kotlin.diagnostics.compiler.LSKotlinCompilerDiagnosticsFixesCodeActionProvider→com.jetbrains.ls.api.features.codeActions.LSCodeActionProvider
- Direction
- com.jetbrains.ls.api.features.impl.kotlin.diagnostics.compiler uses com.jetbrains.ls.api.features.codeActions, so a change to com.jetbrains.ls.api.features.codeActions can break com.jetbrains.ls.api.features.impl.kotlin.diagnostics.compiler, while a change to com.jetbrains.ls.api.features.impl.kotlin.diagnostics.compiler can't break com.jetbrains.ls.api.features.codeActions.
- Position
- Below the diagonal: com.jetbrains.ls.api.features.impl.kotlin.diagnostics.compiler uses a module listed above it, which is the healthy direction.
38→25 com.jetbrains.ls.api.features.impl.kotlin.diagnostics.compiler uses com.jetbrains.ls.api.features.impl.common.modcommands✕
- Connections
- 2 pairs of types, where a type in com.jetbrains.ls.api.features.impl.kotlin.diagnostics.compiler uses a type in com.jetbrains.ls.api.features.impl.common.modcommands.
- The types involved
com.jetbrains.ls.api.features.impl.kotlin.diagnostics.compiler.LSKotlinCompilerDiagnosticsFixesCodeActionProvider→com.jetbrains.ls.api.features.impl.common.modcommands.DocumentStampcom.jetbrains.ls.api.features.impl.kotlin.diagnostics.compiler.LSKotlinCompilerDiagnosticsFixesCodeActionProvider→com.jetbrains.ls.api.features.impl.common.modcommands.LazyFix
- Direction
- com.jetbrains.ls.api.features.impl.kotlin.diagnostics.compiler uses com.jetbrains.ls.api.features.impl.common.modcommands, so a change to com.jetbrains.ls.api.features.impl.common.modcommands can break com.jetbrains.ls.api.features.impl.kotlin.diagnostics.compiler, while a change to com.jetbrains.ls.api.features.impl.kotlin.diagnostics.compiler can't break com.jetbrains.ls.api.features.impl.common.modcommands.
- Position
- Below the diagonal: com.jetbrains.ls.api.features.impl.kotlin.diagnostics.compiler uses a module listed above it, which is the healthy direction.
38→30 com.jetbrains.ls.api.features.impl.kotlin.diagnostics.compiler uses com.jetbrains.ls.api.features.impl.common.diagnostics✕
- Connections
- 3 pairs of types, where a type in com.jetbrains.ls.api.features.impl.kotlin.diagnostics.compiler uses a type in com.jetbrains.ls.api.features.impl.common.diagnostics.
- The types involved
com.jetbrains.ls.api.features.impl.kotlin.diagnostics.compiler.KotlinCompilerDiagnosticData→com.jetbrains.ls.api.features.impl.common.diagnostics.DiagnosticDatacom.jetbrains.ls.api.features.impl.kotlin.diagnostics.compiler.KotlinCompilerDiagnosticData→com.jetbrains.ls.api.features.impl.common.diagnostics.DiagnosticSourcecom.jetbrains.ls.api.features.impl.kotlin.diagnostics.compiler.LSKotlinCompilerDiagnosticsFixesCodeActionProvider→com.jetbrains.ls.api.features.impl.common.diagnostics.DiagnosticWithData
- Direction
- com.jetbrains.ls.api.features.impl.kotlin.diagnostics.compiler uses com.jetbrains.ls.api.features.impl.common.diagnostics, so a change to com.jetbrains.ls.api.features.impl.common.diagnostics can break com.jetbrains.ls.api.features.impl.kotlin.diagnostics.compiler, while a change to com.jetbrains.ls.api.features.impl.kotlin.diagnostics.compiler can't break com.jetbrains.ls.api.features.impl.common.diagnostics.
- Position
- Below the diagonal: com.jetbrains.ls.api.features.impl.kotlin.diagnostics.compiler uses a module listed above it, which is the healthy direction.
39→1 com.jetbrains.ls.api.features.impl.common.completion uses com.jetbrains.ls.api.features.configuration.LSUniqueConfigurationEntry✕
- Connections
- 1 pair of types, where a type in com.jetbrains.ls.api.features.impl.common.completion uses a type in com.jetbrains.ls.api.features.configuration.LSUniqueConfigurationEntry.
- The types involved
com.jetbrains.ls.api.features.impl.common.completion.LSCompletionProviderHelper→com.jetbrains.ls.api.features.configuration.LSUniqueConfigurationEntry.UniqueId
- Direction
- com.jetbrains.ls.api.features.impl.common.completion uses com.jetbrains.ls.api.features.configuration.LSUniqueConfigurationEntry, so a change to com.jetbrains.ls.api.features.configuration.LSUniqueConfigurationEntry can break com.jetbrains.ls.api.features.impl.common.completion, while a change to com.jetbrains.ls.api.features.impl.common.completion can't break com.jetbrains.ls.api.features.configuration.LSUniqueConfigurationEntry.
- Position
- Below the diagonal: com.jetbrains.ls.api.features.impl.common.completion uses a module listed above it, which is the healthy direction.
39→8 com.jetbrains.ls.api.features.impl.common.completion uses com.jetbrains.ls.api.features.commands✕
- Connections
- 1 pair of types, where a type in com.jetbrains.ls.api.features.impl.common.completion uses a type in com.jetbrains.ls.api.features.commands.
- The types involved
com.jetbrains.ls.api.features.impl.common.completion.LSCompletionProviderHelper→com.jetbrains.ls.api.features.commands.LSCommandDescriptor
- Direction
- com.jetbrains.ls.api.features.impl.common.completion uses com.jetbrains.ls.api.features.commands, so a change to com.jetbrains.ls.api.features.commands can break com.jetbrains.ls.api.features.impl.common.completion, while a change to com.jetbrains.ls.api.features.impl.common.completion can't break com.jetbrains.ls.api.features.commands.
- Position
- Below the diagonal: com.jetbrains.ls.api.features.impl.common.completion uses a module listed above it, which is the healthy direction.
39→12 com.jetbrains.ls.api.features.impl.common.completion uses com.jetbrains.ls.api.features.language✕
- Connections
- 1 pair of types, where a type in com.jetbrains.ls.api.features.impl.common.completion uses a type in com.jetbrains.ls.api.features.language.
- The types involved
com.jetbrains.ls.api.features.impl.common.completion.LSCompletionProviderHelper→com.jetbrains.ls.api.features.language.LSLanguage
- Direction
- com.jetbrains.ls.api.features.impl.common.completion uses com.jetbrains.ls.api.features.language, so a change to com.jetbrains.ls.api.features.language can break com.jetbrains.ls.api.features.impl.common.completion, while a change to com.jetbrains.ls.api.features.impl.common.completion can't break com.jetbrains.ls.api.features.language.
- Position
- Below the diagonal: com.jetbrains.ls.api.features.impl.common.completion uses a module listed above it, which is the healthy direction.
39→28 com.jetbrains.ls.api.features.impl.common.completion uses com.jetbrains.ls.api.features.completion✕
- Connections
- 2 pairs of types, where a type in com.jetbrains.ls.api.features.impl.common.completion uses a type in com.jetbrains.ls.api.features.completion.
- The types involved
com.jetbrains.ls.api.features.impl.common.completion.LSAnyCompletionItemKindProvider→com.jetbrains.ls.api.features.completion.LSCompletionCandidatecom.jetbrains.ls.api.features.impl.common.completion.LSAnyCompletionItemKindProvider→com.jetbrains.ls.api.features.completion.LSCompletionItemKindProvider
- Direction
- com.jetbrains.ls.api.features.impl.common.completion uses com.jetbrains.ls.api.features.completion, so a change to com.jetbrains.ls.api.features.completion can break com.jetbrains.ls.api.features.impl.common.completion, while a change to com.jetbrains.ls.api.features.impl.common.completion can't break com.jetbrains.ls.api.features.completion.
- Position
- Below the diagonal: com.jetbrains.ls.api.features.impl.common.completion uses a module listed above it, which is the healthy direction.
39→36 com.jetbrains.ls.api.features.impl.common.completion uses com.jetbrains.ls.api.features.impl.common.completion.LSCompletionProviderHelper✕
- Connections
- 5 pairs of types, where a type in com.jetbrains.ls.api.features.impl.common.completion uses a type in com.jetbrains.ls.api.features.impl.common.completion.LSCompletionProviderHelper.
- The types involved
com.jetbrains.ls.api.features.impl.common.completion.LSCompletionProviderHelper→com.jetbrains.ls.api.features.impl.common.completion.LSCompletionProviderHelper.CompletionEntrycom.jetbrains.ls.api.features.impl.common.completion.LSCompletionProviderHelper→com.jetbrains.ls.api.features.impl.common.completion.LSCompletionProviderHelper.CompletionInsertionResultcom.jetbrains.ls.api.features.impl.common.completion.LSCompletionProviderHelper→com.jetbrains.ls.api.features.impl.common.completion.LSCompletionProviderHelper.FileForModificationProvidercom.jetbrains.ls.api.features.impl.common.completion.LSCompletionProviderHelper→com.jetbrains.ls.api.features.impl.common.completion.LSCompletionProviderHelper.LookupElementContextcom.jetbrains.ls.api.features.impl.common.completion.LSCompletionProviderHelper→com.jetbrains.ls.api.features.impl.common.completion.LSCompletionProviderHelper.LookupElementOverride
- Direction
- com.jetbrains.ls.api.features.impl.common.completion uses com.jetbrains.ls.api.features.impl.common.completion.LSCompletionProviderHelper, so a change to com.jetbrains.ls.api.features.impl.common.completion.LSCompletionProviderHelper can break com.jetbrains.ls.api.features.impl.common.completion, while a change to com.jetbrains.ls.api.features.impl.common.completion can't break com.jetbrains.ls.api.features.impl.common.completion.LSCompletionProviderHelper.
- Position
- Below the diagonal: com.jetbrains.ls.api.features.impl.common.completion uses a module listed above it, which is the healthy direction.
40→1 com.jetbrains.ls.api.features.impl.kotlin.completion uses com.jetbrains.ls.api.features.configuration.LSUniqueConfigurationEntry✕
- Connections
- 1 pair of types, where a type in com.jetbrains.ls.api.features.impl.kotlin.completion uses a type in com.jetbrains.ls.api.features.configuration.LSUniqueConfigurationEntry.
- The types involved
com.jetbrains.ls.api.features.impl.kotlin.completion.LSKotlinCompletionProvider→com.jetbrains.ls.api.features.configuration.LSUniqueConfigurationEntry.UniqueId
- Direction
- com.jetbrains.ls.api.features.impl.kotlin.completion uses com.jetbrains.ls.api.features.configuration.LSUniqueConfigurationEntry, so a change to com.jetbrains.ls.api.features.configuration.LSUniqueConfigurationEntry can break com.jetbrains.ls.api.features.impl.kotlin.completion, while a change to com.jetbrains.ls.api.features.impl.kotlin.completion can't break com.jetbrains.ls.api.features.configuration.LSUniqueConfigurationEntry.
- Position
- Below the diagonal: com.jetbrains.ls.api.features.impl.kotlin.completion uses a module listed above it, which is the healthy direction.
40→8 com.jetbrains.ls.api.features.impl.kotlin.completion uses com.jetbrains.ls.api.features.commands✕
- Connections
- 2 pairs of types, where a type in com.jetbrains.ls.api.features.impl.kotlin.completion uses a type in com.jetbrains.ls.api.features.commands.
- The types involved
com.jetbrains.ls.api.features.impl.kotlin.completion.LSKotlinCompletionProvider→com.jetbrains.ls.api.features.commands.LSCommandDescriptorcom.jetbrains.ls.api.features.impl.kotlin.completion.LSKotlinCompletionProvider→com.jetbrains.ls.api.features.commands.LSCommandDescriptorProvider
- Direction
- com.jetbrains.ls.api.features.impl.kotlin.completion uses com.jetbrains.ls.api.features.commands, so a change to com.jetbrains.ls.api.features.commands can break com.jetbrains.ls.api.features.impl.kotlin.completion, while a change to com.jetbrains.ls.api.features.impl.kotlin.completion can't break com.jetbrains.ls.api.features.commands.
- Position
- Below the diagonal: com.jetbrains.ls.api.features.impl.kotlin.completion uses a module listed above it, which is the healthy direction.
40→12 com.jetbrains.ls.api.features.impl.kotlin.completion uses com.jetbrains.ls.api.features.language✕
- Connections
- 1 pair of types, where a type in com.jetbrains.ls.api.features.impl.kotlin.completion uses a type in com.jetbrains.ls.api.features.language.
- The types involved
com.jetbrains.ls.api.features.impl.kotlin.completion.LSKotlinCompletionProvider→com.jetbrains.ls.api.features.language.LSLanguage
- Direction
- com.jetbrains.ls.api.features.impl.kotlin.completion uses com.jetbrains.ls.api.features.language, so a change to com.jetbrains.ls.api.features.language can break com.jetbrains.ls.api.features.impl.kotlin.completion, while a change to com.jetbrains.ls.api.features.impl.kotlin.completion can't break com.jetbrains.ls.api.features.language.
- Position
- Below the diagonal: com.jetbrains.ls.api.features.impl.kotlin.completion uses a module listed above it, which is the healthy direction.
40→28 com.jetbrains.ls.api.features.impl.kotlin.completion uses com.jetbrains.ls.api.features.completion✕
- Connections
- 3 pairs of types, where a type in com.jetbrains.ls.api.features.impl.kotlin.completion uses a type in com.jetbrains.ls.api.features.completion.
- The types involved
com.jetbrains.ls.api.features.impl.kotlin.completion.LSKotlinCompletionItemKindProvider→com.jetbrains.ls.api.features.completion.LSCompletionCandidatecom.jetbrains.ls.api.features.impl.kotlin.completion.LSKotlinCompletionItemKindProvider→com.jetbrains.ls.api.features.completion.LSCompletionItemKindProvidercom.jetbrains.ls.api.features.impl.kotlin.completion.LSKotlinCompletionProvider→com.jetbrains.ls.api.features.completion.LSCompletionProvider
- Direction
- com.jetbrains.ls.api.features.impl.kotlin.completion uses com.jetbrains.ls.api.features.completion, so a change to com.jetbrains.ls.api.features.completion can break com.jetbrains.ls.api.features.impl.kotlin.completion, while a change to com.jetbrains.ls.api.features.impl.kotlin.completion can't break com.jetbrains.ls.api.features.completion.
- Position
- Below the diagonal: com.jetbrains.ls.api.features.impl.kotlin.completion uses a module listed above it, which is the healthy direction.
40→36 com.jetbrains.ls.api.features.impl.kotlin.completion uses com.jetbrains.ls.api.features.impl.common.completion.LSCompletionProviderHelper✕
- Connections
- 1 pair of types, where a type in com.jetbrains.ls.api.features.impl.kotlin.completion uses a type in com.jetbrains.ls.api.features.impl.common.completion.LSCompletionProviderHelper.
- The types involved
com.jetbrains.ls.api.features.impl.kotlin.completion.LSKotlinCompletionProvider→com.jetbrains.ls.api.features.impl.common.completion.LSCompletionProviderHelper.FileForModificationProvider
- Direction
- com.jetbrains.ls.api.features.impl.kotlin.completion uses com.jetbrains.ls.api.features.impl.common.completion.LSCompletionProviderHelper, so a change to com.jetbrains.ls.api.features.impl.common.completion.LSCompletionProviderHelper can break com.jetbrains.ls.api.features.impl.kotlin.completion, while a change to com.jetbrains.ls.api.features.impl.kotlin.completion can't break com.jetbrains.ls.api.features.impl.common.completion.LSCompletionProviderHelper.
- Position
- Below the diagonal: com.jetbrains.ls.api.features.impl.kotlin.completion uses a module listed above it, which is the healthy direction.
40→39 com.jetbrains.ls.api.features.impl.kotlin.completion uses com.jetbrains.ls.api.features.impl.common.completion✕
- Connections
- 1 pair of types, where a type in com.jetbrains.ls.api.features.impl.kotlin.completion uses a type in com.jetbrains.ls.api.features.impl.common.completion.
- The types involved
com.jetbrains.ls.api.features.impl.kotlin.completion.LSKotlinCompletionProvider→com.jetbrains.ls.api.features.impl.common.completion.LSCompletionProviderHelper
- Direction
- com.jetbrains.ls.api.features.impl.kotlin.completion uses com.jetbrains.ls.api.features.impl.common.completion, so a change to com.jetbrains.ls.api.features.impl.common.completion can break com.jetbrains.ls.api.features.impl.kotlin.completion, while a change to com.jetbrains.ls.api.features.impl.kotlin.completion can't break com.jetbrains.ls.api.features.impl.common.completion.
- Position
- Below the diagonal: com.jetbrains.ls.api.features.impl.kotlin.completion 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
Roadmap
Top priorities: Add a CI workflow that builds and runs the test suite on every push/PR; TypeScript/JavaScript: use the promise APIs (fs/promises, a promisified child_process.execFile, the async zlib/crypto functions) and await them instead of the *Sync variants; Keep slices independent: share cross-slice needs via an explicit contract/shared-kernel, not direct references between slices.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Add a CI workflow that builds and runs the test suite on every push/PR. | +6.7 pts | Medium | CI/CD gates |
| Resolve the 9 Boundary-crossing change coupling finding(s) in Change Coupling — start with LSSimpleCodeActionProvider.kt (9). | +1.4 pts | Low | Change Coupling |
| TypeScript/JavaScript: use the promise APIs (fs/promises, a promisified child_process.execFile, the async zlib/crypto functions) and await them instead of the *Sync variants. | +2.3 pts | Medium | Async & latency hygiene |
| Keep slices independent: share cross-slice needs via an explicit contract/shared-kernel, not direct references between slices. | +2.0 pts | Medium | Slice cohesion |
| 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. | +1.9 pts | Medium | Architecture documentation |
| Add eslint as package.json scripts and run them in CI. | +1.5 pts | Medium | Tooling |
| Break each cycle by extracting the shared piece into a module both sides can import. | +1.0 pts | Medium | Circular Imports |
| Extend structured logging to the remaining runnable modules so everything you run is diagnosable in production. | +1.0 pts | Medium | Observability |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| features-impl/kotlin/src/com/jetbrains/ls/api/features/impl/kotlin/semanticTokens/LSKotlinSemanticTokensProvider.kt | 6.0 | Mixed | Explicit Debt: TodoComment |
| features-impl/common/src/com/jetbrains/ls/api/features/impl/common/modcommands/ModCommandData.kt | 6.0 | Mixed | Explicit Debt: TodoComment |
| vscode-extension-core/src/lspClient.ts | 6.0 | Mixed | Explicit Debt: TodoComment |
| api.features/src/com/jetbrains/ls/api/features/codeActions/LSSimpleCodeActionProvider.kt | 6.0 | Mixed | Change Coupling: Boundary-crossing change coupling: LSSimpleCodeActionProvider.kt ↔ LSKotlinCompilerDiagnosticsFixesCodeActionProvider.kt |
| features-impl/common/src/com/jetbrains/ls/api/features/impl/common/diagnostics/LSCommonIntentionFixesCodeActionProvider.kt | 6.7 | Mixed | Explicit Debt: TodoComment |
| api.features/src/com/jetbrains/ls/api/features/semanticTokens/LSSemanticTokens.kt | 6.7 | Mixed | Explicit Debt: TodoComment |
| features-impl/common/src/com/jetbrains/ls/api/features/impl/common/diagnostics/LSCommonSyntaxErrorDiagnosticProvider.kt | 7.0 | Mixed | Code Duplication: Edited copy of a member (5 corresponding lines) |
| features-impl/common/src/com/jetbrains/ls/api/features/impl/common/completion/ModCompletionCommandConverter.kt | 7.1 | Mixed | Cyclomatic Complexity: ModCompletionCommandConverter.split (cyclomatic 27) |
| vscode-language-kotlin/src/kotlin/keyHandler.ts | 7.1 | Mixed | Cyclomatic Complexity: keyHandler.handleEnter (cyclomatic 19) |
| vscode-extension-core/src/serverBundleDownload.ts | 7.2 | Mixed | Cyclomatic Complexity: serverBundleDownload.downloadFile (cyclomatic 24) |
| features-impl/common/src/com/jetbrains/ls/api/features/impl/common/callHierarchy/LSCallHierarchyProviderBase.kt | 7.4 | Mixed | Code Duplication: Edited copy of a member (21 corresponding lines) |
| vscode-extension-core/src/initializationSettings.ts | 7.8 | Mixed | Cyclomatic Complexity: initializationSettings.projectRejectionReason (cyclomatic 21) |
| features-impl/kotlin/psi/src/com/jetbrains/ls/api/features/impl/kotlin/psi/kinds.kt | 7.8 | Mixed | Cyclomatic Complexity: KindsKt.getKind (cyclomatic 20) |
| buildtool.api/src/com/jetbrains/ls/buildtool/api/run/RunSteps.kt | 7.8 | Mixed | Cognitive Complexity: RunStepsKt.run (cognitive 18) |
| features-impl/common/src/com/jetbrains/ls/api/features/impl/common/diagnostics/LSCommonInjectionSyntaxErrorDiagnosticProvider.kt | 7.8 | Mixed | Code Duplication: Members sharing a duplicated core (5 members, 50+ identical tokens) |
| features-impl/kotlin/src/com/jetbrains/ls/api/features/impl/kotlin/typeHierarchy/LSKotlinTypeHierarchyProvider.kt | 7.8 | Mixed | Code Duplication: Edited copy of a member (16 corresponding lines) |
| api.features/src/com/jetbrains/ls/api/features/callHierarchy/LSCallHierarchy.kt | 7.8 | Mixed | Code Duplication: Edited copy of a member (5 corresponding lines) |
| features-impl/kotlin/psi/src/com/jetbrains/ls/api/features/impl/kotlin/psi/LSKotlinDocumentSymbolCustomizer.kt | 8.2 | Near-clean | Explicit Debt: TodoComment |
| features-impl/kotlin/psi/src/com/jetbrains/ls/api/features/impl/kotlin/psi/LSKotlinWorkspaceSymbolCustomizer.kt | 8.2 | Near-clean | Explicit Debt: TodoComment |
| api.features/src/com/jetbrains/ls/api/features/diagnostics/LSDiagnosticProvider.kt | 8.2 | Near-clean | Explicit Debt: TodoComment |
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 56 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.7, the weighted average across measured dimensions.
What we checked — 56 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, 200 of 213 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
- D5 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. This check's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
- D8 Code Coverage — 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. Coverage NOT MEASURED: the JavaScript/TypeScript half could not be measured — the dependency install for vscode-extension-core/ failed in the analyzer sandbox (npm error code EUNSUPPORTEDPROTOCOL), so the suite never ran. Coverage is excluded from the score rather than counted as a near-zero. This is OUR limitation, not a defect in the repo.
- 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 JavaScript/TypeScript suite could not be re-run in the analyzer sandbox — the dependency install for vscode-extension-core/ failed in the analyzer sandbox (npm error code EUNSUPPORTEDPROTOCOL), so the suite never ran. This is OUR limitation, not a defect in the repo — it is excluded from the score.
- 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 for the node:test suite in vscode-extension-core/ was NOT MEASURED: the dependency install for vscode-extension-core/ failed in the analyzer sandbox (npm error code EUNSUPPORTEDPROTOCOL), so the suite never ran. This is OUR limitation, not a defect in the repository, and the suite is excluded from the measurement rather than counted against it.
- 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 for the node:test suite in vscode-jvm-testing/ was NOT MEASURED: the dependency install for vscode-jvm-testing/ failed in the analyzer sandbox (npm error code EUNSUPPORTEDPROTOCOL), so the suite never ran. This is OUR limitation, not a defect in the repository, and the suite is excluded from the measurement rather than counted against it.
- 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 for the node:test suite in vscode-language-kotlin/ was NOT MEASURED: the dependency install for vscode-language-kotlin/ failed in the analyzer sandbox (npm error code EUNSUPPORTEDPROTOCOL), so the suite never ran. This is OUR limitation, not a defect in the repository, and the suite is excluded from the measurement rather than counted against it.
- 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 for the node:test suite in vscode-testing/ was NOT MEASURED: the dependency install for vscode-testing/ failed in the analyzer sandbox (npm error code EUNSUPPORTEDPROTOCOL), so the suite never ran. This is OUR limitation, not a defect in the repository, and the suite is excluded from the measurement rather than counted against it.
- D12 Dependency Hygiene — 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. This repository's 5 package.json manifest(s) WERE read and their pinning discipline assessed; what went unanswered is the currency half, because answering it needs a lockfile resolved to CONCRETE versions and this repository commits none — a package.json states version RANGES, and a range names no particular release to be behind. So registry.npmjs.org was never asked, and there was nothing here for it to grade. This is a true statement about the repository and NOT a gap on our side: no lockfile reader we could write would find anything here to read, so there is no capability behind this row to build.
- D14 License Compliance — 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. Not scored — this repository declares package.json manifests but commits no lockfile this pass can resolve (npm, pnpm, yarn and bun each write a different one, and `bun.lockb` is a binary format with no published shape), so the set of packages it actually ships is not resolvable from the checkout: its declarations carry version RANGES, and grading whichever release happens to be newest today would be a verdict about a dependency graph this repository has not pinned. Commit the lock and this dimension grades its production dependencies against registry.npmjs.org. NOT a finding that this repository's licences are compliant: this dimension asserts nothing about its licensing in either direction.
- D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
- D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22 identifies the intentionally-exposed surface from `IsPackable` and `.Contracts` project names, MSBuild conventions read off the loaded project set. This target exposed no such projects, so the probe never ran; this says nothing about whether the repository has a public API. This repository commits no C#/VB source at all, so there was never an MSBuild project set to read these conventions off. That is OUR side and it is an ADMISSION gap, not an environment fault: it declares a published package (kotlin-vscode/package.json), but no published-package marker D22 reads admitted any project here. D22 DOES collect the public API of every language in this tree, and admits a project only when its manifest makes that ecosystem's publication act in a form the marker recognises — so what is missing is not a collector but an admission rule for the publication act this repository makes, if it makes one. The remedy is a better discriminator for that marker — not a collector, and no change to the scan image can close it. The marker's rules are measured to refuse applications, so one refused repository is the rule working as calibrated; several are the evidence that it is too strict. For npm the surface is what a published package.json's entry points (exports, main, module, types) export, followed through the source; an entry that names build output the tree does not commit (dist/, build/) is not followed back to source, because only a tsconfig outDir/rootDir pair states that mapping and a bundler's input lives in executable configuration this engine does not evaluate.
- D24 Comment Value — 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 source language's comment syntax, and the code a comment annotates in it, needs its own proof before D24 judges it. Until then those comments are left unread, not counted as clean.
- D26 Project Cohesion — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Project size and spread are measured over build units (a .NET project, a Maven or Gradle module, an npm, Deno or JSR package, a Go module, a Cargo crate, a Python, Composer, Bundler, RubyGems, Mix, rebar3, sbt, SwiftPM or pub package, an OTP application, an Xcode project or XcodeGen spec, or a checkout that declares no build at all) whose source a code model reads. This repository's production source is in a language no model reads, or in units whose build tool D26 does not recognise. That is a gap in this analyzer's language reach — not a finding that the repository's projects are cohesive.
- D27 Navigability — 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. Tracing effort is measured over resolved call sites, and all 220 sampled here came from .kt files. This repository's .ts source is a material share of its production lines and contributed none, so the score above is a verdict about the part that was read. Not a finding that the unread half navigates well — it is unmeasured.
- D30 Dependency Vulnerabilities — measured, with a gap in what it reached — 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 scanner produced no output at all, so no dependency was actually scanned. 1 of 2 declared ecosystem(s) (npm) WERE scanned and every vulnerability they reported is included in this result; osv was not, so this dimension's score covers less than the dependency surface this repository declares, and nothing here is evidence that osv is free of known-vulnerable dependencies. osv: the scanner produced no output at all, so no dependency was actually scanned. This is reported as a measurement gap rather than a clean pass. osv-scanner documents exit 128 as "no package sources found" — but this scan only invoked it because the tree declares a source it supports (`pom.xml` and the resolved lockfiles among them), so the tool's report and this repository disagree. Check that those sources are reachable from the directory the scan ran in before concluding anything is missing. If this tree really does commit only range-pinned manifests, commit the lockfile your package manager produces — but only where your ecosystem HAS one and commits it: Maven has none at all (osv-scanner reads `pom.xml` directly) and Gradle writes one only under opt-in dependency locking, while a published Composer package and a published Dart library both deliberately exclude theirs. In those three, generate one in CI before the scan instead — a resolved dependency list or an SBOM fed to the scanner.
- 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. `api.features/src/com/jetbrains/ls/api/features/LSConfiguration.kt`, `api.features/src/com/jetbrains/ls/api/features/LSConfigurationEntry.kt`, `api.features/src/com/jetbrains/ls/api/features/callHierarchy/LSCallHierarchy.kt`, `api.features/src/com/jetbrains/ls/api/features/callHierarchy/LSCallHierarchyProvider.kt`, `api.features/src/com/jetbrains/ls/api/features/codeActions/LSCodeActionProvider.kt`, … (+119 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 — measured, with a gap in what it reached — 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 scanner produced no output at all, so no dependency was actually scanned. 1 of 2 declared ecosystem(s) (npm) WERE scanned and every vulnerability they reported is included in this result; osv was not, so this dimension's score covers less than the dependency surface this repository declares, and nothing here is evidence that osv is free of known-vulnerable dependencies. osv: the scanner produced no output at all, so no dependency was actually scanned. This is reported as a measurement gap rather than a clean pass. osv-scanner documents exit 128 as "no package sources found" — but this scan only invoked it because the tree declares a source it supports (`pom.xml` and the resolved lockfiles among them), so the tool's report and this repository disagree. Check that those sources are reachable from the directory the scan ran in before concluding anything is missing. If this tree really does commit only range-pinned manifests, commit the lockfile your package manager produces — but only where your ecosystem HAS one and commits it: Maven has none at all (osv-scanner reads `pom.xml` directly) and Gradle writes one only under opt-in dependency locking, while a published Composer package and a published Dart library both deliberately exclude theirs. In those three, generate one in CI before the scan instead — a resolved dependency list or an SBOM fed to the scanner.
- D44 Platform End-of-Life — 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 dimension reads a project's own statement about the platform it runs on: a TargetFramework in a .NET project file, a .nvmrc or .python-version, a capped requires-python, a Rust toolchain file or Cargo.toml rust-version, a .go-version, .java-version, .ruby-version, .tool-versions or .sdkmanrc, a go.mod go directive, a Maven or Gradle Java level or toolchain, a Gemfile's ruby directive, a mix.exs elixir requirement, a rebar.config minimum_otp_vsn, a pubspec.yaml SDK constraint, a build.sbt scalaVersion, or a framework major pinned by a dependency constraint. This repository carries none of them, so nothing about its platform was established. That is a gap in this analyzer's coverage, NOT a finding that the platform is supported — a language whose runtime is declared elsewhere (Package.swift, a Dockerfile) is simply not read here yet.
- 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.
- C2 Access Controls — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These authorization controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks authorization controls.
- GD1 Unfinished & placeholder code — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, F#, JavaScript/TypeScript, Dart, Ruby and Scala source only, and this repository's Kotlin is most of its product and is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- 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 reads C# syntax, JavaScript/TypeScript, Java, Dart, Ruby and Scala source only, and this repository's Kotlin is most of its product and is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- M4 Documentation accuracy — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
- P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
- S1 Web-Security Posture — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These web-security controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks web-security controls.
- X24 Document value interpolated into markup unescaped — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check'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.
- X27 Collection changed while being enumerated — 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 check's reader does not cover every language in this repository. The score describes the part it read, which is most of the product; the rest is a gap in this analyzer's language reach.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
- 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").
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
- 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.
- D24 Comment Value: Comment value is measured as redundancy only: a comment that repeats its code's words is found, but a paraphrase in other words, a vague comment, or one the code contradicts is not, and whether a comment is valuable is not claimed. Comments in other scripts or languages, and outside C#, are not judged.
- D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- 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
D1 · Cyclomatic Complexity
17 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was LSKotlinSemanticTokensProvider.getRangeWithToken at 44. A further 3 method(s) were over the threshold but excluded as flat dispatchers (a long switch/match over independent cases: many branches, almost no nesting), the largest being OptionValidator.validate at 20 — they are counted neither in the figure above nor in this dimension's score.
What to do
- Bring the 17 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with LSKotlinSemanticTokensProvider.getRangeWithToken (cyclomatic 44), ModCommandData.from (cyclomatic 38), ModCommandDataKt.executeCommand (cyclomatic 35). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 17 together lifts Cyclomatic Complexity from 7.5 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
D2 · Cognitive Complexity
16 method(s) exceeded the cognitive complexity threshold of 15; the worst was ModCompletionCommandConverter.split at 57.
What to do
- Bring the 16 bodies over 15 down to 15 or less in Cognitive Complexity — start with ModCompletionCommandConverter.split (cognitive 57), ModCommandDataKt.executeCommand (cognitive 38), LSKotlinSemanticTokensProvider.getRangeWithToken (cognitive 38). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 16 together lifts Cognitive Complexity from 7.3 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
D3 · God Classes
6 over-large unit(s) detected — types, modules or files that carry too much.
What to do
- Resolve the 5 FileTooLong finding(s) in God Classes — start with keyHandler.ts, lspClient.ts, keyHandlerUtils.ts. — One of this dimension's main actionable groups (5 warning-level).
- Resolve the 1 MethodTooLong finding(s) in God Classes — start with ModCommandData.kt. — One of this dimension's main actionable groups (1 warning-level).
D4 · Code Duplication
4 duplicated block group(s) detected. 1.7 % of the production lines (491 of 28,799) are in a reported copy. A further 15 rows report members as variants of one another; the share counts each copied line once, however many rows cite it. Measured on part of this repository only: .ts (44% of production source) was not exposed to THIS dimension's token comparison and is not in this count; duplication there is measured by R10 Code Duplication, the frontend lens's card running the same clone algorithm over the JS/TS token stream.
What to do
- Resolve the 3 Edited copy of a member (5 corresponding lines) finding(s) in Code Duplication — start with LSCallHierarchy.kt (2), LSCommonSyntaxErrorDiagnosticProvider.kt. — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 2 Edited copy of a member (21 corresponding lines) finding(s) in Code Duplication — start with LSJavaPackageDefinitionProvider.kt, LSCallHierarchyProviderBase.kt. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 2 Edited copy of a member (15 corresponding lines) finding(s) in Code Duplication — start with LSImplementation.kt, renameUtils.kt. — One of this dimension's main actionable groups (2 warning-level).
D6 · Cohesion (LCOM4)
0 of 36 classes have LCOM4 above 3.
D10 · Test Quality
0 skipped, 0 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 648 tests.
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D15 · Churn × Complexity Hotspots
Top hotspots: features-impl/common/src/com/jetbrains/ls/api/features/impl/common/modcommands/ModCommandData.kt (30×38=1140); vscode-extension-core/src/lspClient.ts (26×19=494) Repeated repair below the complexity floor: features-impl/common/src/com/jetbrains/ls/api/features/impl/common/diagnostics/LSInspectionManager.kt (7 of 9 changes were fixes)
What to do
- Resolve the 2 Hotspot finding(s) in Churn × Complexity Hotspots — start with ModCommandData.kt, lspClient.ts. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 Repeated repair finding(s) in Churn × Complexity Hotspots — start with LSInspectionManager.kt. — One of this dimension's main actionable groups (1 warning-level).
D16 · Bus Factor
22 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is vscode-extension-core/src/keyHandlerUtils.ts. Counted over 153 of the 312 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
What to do
- Resolve the 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
9 deducted task-comment markers across 28799 LoC (0.0/KLoC) → score 9.9. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
What to do
- Resolve the 9 TodoComment finding(s) in Explicit Debt — start with lspClient.ts, LSKotlinSemanticTokensProvider.kt, LSKotlinDocumentSymbolCustomizer.kt. — One of this dimension's main actionable groups (9 warning-level).
D19 · Documentation Quality
2 of 2 documentation facets pass in full. 5 document(s) read across 6 unit(s).
D24 · Comment Value
0 of 217 judged comments only repeat the code they sit on (0.0 %). 1 comment(s) in another language or script were not judged.
D27 · Navigability
34 % of calls cross a namespace and 8 % go through an interface, but 100 % of collaborators are co-located — so a call's collaborators sit together and tracing stays easy. Baseline: small — navigation cost is tolerated. Measured over the .kt source only — this repository's .ts was not sampled for call sites, so this score covers part of the tree, not all of it.
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
semgrep found no security issues. semgrep hit a parse error in 31 file(s) — `api.features/src/com/jetbrains/ls/api/features/textEdits/PsiFileTextEditsCollector.kt` (line 26), `features-impl/common/src/com/jetbrains/ls/api/features/impl/common/codeLens/LSRelatedItemsCodeLensProvider.kt` (lines 70–72, line 72, line 91, …), `features-impl/common/src/com/jetbrains/ls/api/features/impl/common/completion/LSModCompletion.kt` (line 74, line 82, line 98, …), `features-impl/common/src/com/jetbrains/ls/api/features/impl/common/configuration/LSCurrentProfileOptionsCommandProvider.kt` (line 28), `features-impl/common/src/com/jetbrains/ls/api/features/impl/common/configuration/LSInspectionContext.kt` (line 59), … (+26 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.
D30 · Dependency Vulnerabilities
No known-vulnerable dependencies in the 1 ecosystem(s) that were scanned (npm). Partial dependency scan: 1 of 2 declared ecosystem(s) were scanned (npm), and the findings above are real and complete for them. osv was not scanned (osv: the scanner produced no output at all, so no dependency was actually scanned), so this is not the whole dependency surface and the result is reported at reduced confidence.
D34 · Knowledge Freshness
4 of 153 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is api.features/src/com/jetbrains/ls/api/features/semanticTokens/encoding/SemanticTokensEncoder.kt. Counted over 153 of the 312 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: LSSimpleCodeActionProvider.kt↔LSKotlinCompilerDiagnosticsFixesCodeActionProvider.kt 70%; LSSimpleCodeActionProvider.kt↔LSKotlinIntentionCodeActionProvider.kt 70%; LSCommonDefinitionProvider.kt↔LSKotlinPackageDefinitionProvider.kt 70%
What to do
- Resolve the 9 Boundary-crossing change coupling finding(s) in Change Coupling — start with LSSimpleCodeActionProvider.kt (9). — One of this dimension's main actionable groups (9 issue-level).
- Resolve the 4 Change coupling finding(s) in Change Coupling — start with LSJavaBaseLanguageConfiguration.kt, LSCommonInspectionDiagnosticProvider.kt, LSCommonDefinitionProvider.kt. — One of this dimension's main actionable groups (4 warning-level).
- Resolve the 2 Change-coupling hub finding(s) in Change Coupling — start with LSKotlinPackageDefinitionProvider.kt, LSCommonSyntaxErrorDiagnosticProvider.kt. — One of this dimension's main actionable groups (2 warning-level).
D43 · Malicious Dependencies
No known-vulnerable dependencies in the 1 ecosystem(s) that were scanned (npm). Partial dependency scan: 1 of 2 declared ecosystem(s) were scanned (npm), and the findings above are real and complete for them. osv was not scanned (osv: the scanner produced no output at all, so no dependency was actually scanned), so this is not the whole dependency surface and the result is reported at reduced confidence.
Frontend & cross-cutting dimensions
AX10 · Code composition
AX3 · Project dependency cycles
AX5 · Architecture & structure
AX7 · Slice cohesion
- `LSSimpleCodeActionProvider` (slice 'codeActions') depends on `LSCommandDescriptor` from slice 'commands'. — api.features/src/com/jetbrains/ls/api/features/codeActions/LSSimpleCodeActionProvider.kt:78
- `ResolveDataWithConfigurationEntryId` (slice 'resolve') depends on `UniqueId` from slice 'configuration'. — api.features/src/com/jetbrains/ls/api/features/resolve/ResolveDataWithConfigurationEntryId.kt:10
- `CallHierarchyItemData` (slice 'impl') depends on `UniqueId` from slice 'configuration'. — features-impl/common/src/com/jetbrains/ls/api/features/impl/common/callHierarchy/LSCallHierarchyProviderBase.kt:169
- `Declaration` (slice 'impl') depends on `PsiSerializablePointer` from slice 'utils'. — features-impl/common/src/com/jetbrains/ls/api/features/impl/common/callHierarchy/LSCallHierarchyProviderBase.kt:194
- `ImplicitMember` (slice 'impl') depends on `PsiSerializablePointer` from slice 'utils'. — features-impl/common/src/com/jetbrains/ls/api/features/impl/common/callHierarchy/LSCallHierarchyProviderBase.kt:204
- `LSCompletionProviderHelper` (slice 'impl') depends on `LSLanguage` from slice 'language'. — features-impl/common/src/com/jetbrains/ls/api/features/impl/common/completion/LSCompletionProviderHelper.kt:71
- `CompletionCandidate` (slice 'impl') depends on `LSLanguage` from slice 'language'. — features-impl/common/src/com/jetbrains/ls/api/features/impl/common/completion/LSCompletionProviderHelper.kt:343
- `LSCommonConfigurationKt` (slice 'impl') depends on `LSConfigurationPiece` from slice 'language'. — features-impl/common/src/com/jetbrains/ls/api/features/impl/common/configuration/LSCommonConfiguration.kt:28
- `LSCommonServerExtension` (slice 'impl') depends on `LSConfigurationPiece` from slice 'language'. — features-impl/common/src/com/jetbrains/ls/api/features/impl/common/configuration/LSCommonServerExtension.kt:8
- `LSDecompileCommandDescriptorProvider` (slice 'impl') depends on `LSCommandDescriptor` from slice 'commands'. — features-impl/common/src/com/jetbrains/ls/api/features/impl/common/decompiler/LSDecompileCommandDescriptorProvider.kt:22
- `LSCommonInspectionOptionsCodeActionProvider` (slice 'impl') depends on `LSCodeActionGroup` from slice 'codeActions'. — features-impl/common/src/com/jetbrains/ls/api/features/impl/common/diagnostics/LSCommonInspectionOptionsCodeActionProvider.kt:82
- `LSInterpolateFileTemplateCommandDescriptorProvider` (slice 'impl') depends on `LSCommandDescriptor` from slice 'commands'. — features-impl/common/src/com/jetbrains/ls/api/features/impl/common/fileTemplates/LSInterpolateFileTemplateCommandDescriptorProvider.kt:35
- `LSInlayHintsProviderBase` (slice 'impl') depends on `UniqueId` from slice 'configuration'. — features-impl/common/src/com/jetbrains/ls/api/features/impl/common/inlayHints/LSInlayHintsProviderBase.kt:70
- `PsiPointerInlayActionPayloadSerializable` (slice 'impl') depends on `PsiSerializablePointer` from slice 'utils'. — features-impl/common/src/com/jetbrains/ls/api/features/impl/common/inlayHints/LSInlayHintsProviderBase.kt:480
- `InlayHintResolveData` (slice 'impl') depends on `UniqueId` from slice 'configuration'. — features-impl/common/src/com/jetbrains/ls/api/features/impl/common/inlayHints/LSInlayHintsProviderBase.kt:493
- `LSApplyFixCommandDescriptorProvider` (slice 'impl') depends on `LSCommandDescriptor` from slice 'commands'. — features-impl/common/src/com/jetbrains/ls/api/features/impl/common/modcommands/LSApplyFixCommandDescriptorProvider.kt:42
- `Piece` (slice 'impl') depends on `LSSemanticTokenType` from slice 'semanticTokens'. — features-impl/common/src/com/jetbrains/ls/api/features/impl/common/semanticTokens/LSHighlightingSemanticTokens.kt:52
- `LSStackTraceCommandDescriptorProvider` (slice 'impl') depends on `LSCommandDescriptor` from slice 'commands'. — features-impl/common/src/com/jetbrains/ls/api/features/impl/common/stackTrace/LSStackTraceCommandDescriptorProvider.kt:37
- `JavaBaseLanguageServerExtension` (slice 'impl') depends on `LSConfigurationPiece` from slice 'language'. — features-impl/java-base/src/com/jetbrains/ls/api/features/impl/javaBase/JavaBaseLanguageServerExtension.kt:8
- `LSJavaBaseLanguageConfigurationKt` (slice 'impl') depends on `LSConfigurationPiece` from slice 'language'. — features-impl/java-base/src/com/jetbrains/ls/api/features/impl/javaBase/LSJavaBaseLanguageConfiguration.kt:13
- `LSJavaLanguageKt` (slice 'impl') depends on `LSLanguage` from slice 'language'. — features-impl/java-base/src/com/jetbrains/ls/api/features/impl/javaBase/LSJavaLanguage.kt:7
- `LSKotlinCallHierarchyProvider` (slice 'impl') depends on `UniqueId` from slice 'configuration'. — features-impl/kotlin/src/com/jetbrains/ls/api/features/impl/kotlin/callHierarchy/LSKotlinCallHierarchyProvider.kt:26
- `LSKotlinCompletionProvider` (slice 'impl') depends on `UniqueId` from slice 'configuration'. — features-impl/kotlin/src/com/jetbrains/ls/api/features/impl/kotlin/completion/LSKotlinCompletionProvider.kt:28
- `KotlinLanguageServerExtension` (slice 'impl') depends on `LSConfigurationPiece` from slice 'language'. — features-impl/kotlin/src/com/jetbrains/ls/api/features/impl/kotlin/configuration/KotlinLanguageServerExtension.kt:8
- `LSKotlinLanguageConfigurationKt` (slice 'impl') depends on `LSConfigurationPiece` from slice 'language'. — features-impl/kotlin/src/com/jetbrains/ls/api/features/impl/kotlin/configuration/LSKotlinLanguageConfiguration.kt:72
- `KotlinCompilerDiagnosticData` (slice 'impl') depends on `PsiSerializablePointer` from slice 'utils'. — features-impl/kotlin/src/com/jetbrains/ls/api/features/impl/kotlin/diagnostics/compiler/KotlinCompilerDiagnosticData.kt:15
- `LSKotlinLanguageKt` (slice 'impl') depends on `LSLanguage` from slice 'language'. — features-impl/kotlin/src/com/jetbrains/ls/api/features/impl/kotlin/language/LSKotlinLanguage.kt:7
- `LSKotlinSemanticTokensProviderKt` (slice 'impl') depends on `LSSemanticTokenModifierCustom` from slice 'semanticTokens'. — features-impl/kotlin/src/com/jetbrains/ls/api/features/impl/kotlin/semanticTokens/LSKotlinSemanticTokensProvider.kt:68
- `LSKotlinTypeHierarchyProvider` (slice 'impl') depends on `UniqueId` from slice 'configuration'. — features-impl/kotlin/src/com/jetbrains/ls/api/features/impl/kotlin/typeHierarchy/LSKotlinTypeHierarchyProvider.kt:95
- `TypeHierarchyItemData` (slice 'impl') depends on `PsiSerializablePointer` from slice 'utils'. — features-impl/kotlin/src/com/jetbrains/ls/api/features/impl/kotlin/typeHierarchy/LSKotlinTypeHierarchyProvider.kt:385
What to do
- Keep slices independent: share cross-slice needs via an explicit contract/shared-kernel, not direct references between slices.
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
- No CI workflow found (.github/workflows, azure-pipelines.yml, .gitlab-ci.yml, …) — changes aren't gated by an automated build/test.
What to do
- Add a CI workflow that builds and runs the test suite on every push/PR.
P10 · Library API & versioning
P2 · Observability
- Only 1/2 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `vscode-extension-core`.
What to do
- Extend structured logging to the remaining runnable modules so everything you run is diagnosable in production.
- Add a health-check endpoint (Spring Boot Actuator's /actuator/health, or a /health route) so orchestrators and load balancers can probe liveness/readiness.
P3 · Security & performance tooling
- No static application security testing detected. For this repository's stack, add spotbugs with find-sec-bugs (or `semgrep --config=auto`, which runs on any language) — this repository has no CI pipeline yet, so run it locally to clear the existing findings, then make it a step of the first workflow you add so a regression fails the build. What was searched, so you can tell an absence from a miss: the 0 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.
- `kotlin-vscode/package.json` 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`. — kotlin-vscode/package.json:41
What to do
- Run what this repository's stack ships: spotbugs with find-sec-bugs — or `semgrep --config=auto`, which runs on any language — locally for now, since there is no CI pipeline here yet, and as a step of the first workflow you add 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
- `chmodSync` in `ensureBundledServerLauncher` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — vscode-extension-core/src/lspClient.ts:840
- `fs.existsSync` in `ensureServerLauncher` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. (×4) — vscode-extension-core/src/serverBundleDownload.ts:100, vscode-extension-core/src/serverBundleDownload.ts:106, vscode-extension-core/src/serverBundleDownload.ts:117, …
- `fs.existsSync` in `anonymous function` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. (×2) — vscode-extension-core/src/serverBundleDownload.ts:121, vscode-extension-core/src/serverBundleDownload.ts:129
- `fs.existsSync` in `findCachedServerLauncher` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — vscode-extension-core/src/serverBundleDownload.ts:162
- `fs.existsSync` in `publishExtractedServerBundle` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — vscode-extension-core/src/serverBundleDownload.ts:362
What to do
- TypeScript/JavaScript: use the promise APIs (fs/promises, a promisified child_process.execFile, the async zlib/crypto functions) and await them instead of the *Sync variants.
R1 · Type Safety
R10 · Code Duplication
- vscode-language-kotlin/src/kotlin/keyHandler.ts:609 · vscode-language-kotlin/src/kotlin/keyHandler.ts:639 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — vscode-language-kotlin/src/kotlin/keyHandler.ts:609
- vscode-extension-core/src/keyHandlerUtils.ts:119 · vscode-extension-core/src/keyHandlerUtils.ts:134 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — vscode-extension-core/src/keyHandlerUtils.ts:119
- vscode-extension-core/src/keyHandlerUtils.ts:668 · vscode-language-kotlin/src/kotlin/keyHandler.ts:371 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — vscode-extension-core/src/keyHandlerUtils.ts:668
- vscode-extension-core/src/keyHandlerUtils.ts:406 · vscode-language-kotlin/src/kotlin/keyHandler.ts:578 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — vscode-extension-core/src/keyHandlerUtils.ts:406
- vscode-extension-core/src/serverBundleDownload.ts:783 · vscode-extension-core/src/testing/archiveExtraction.ts:170 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — vscode-extension-core/src/serverBundleDownload.ts:783
- vscode-language-kotlin/src/kotlin/keyHandler.ts:173 · vscode-language-kotlin/src/kotlin/keyHandler.ts:280 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — vscode-language-kotlin/src/kotlin/keyHandler.ts:173
- vscode-extension-core/src/keyHandlerUtils.ts:573 · vscode-language-kotlin/src/kotlin/keyHandler.ts:883 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — vscode-extension-core/src/keyHandlerUtils.ts:573
- vscode-extension-core/src/serverBundleDownload.ts:370 · vscode-extension-core/src/serverBundleDownload.ts:641 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — vscode-extension-core/src/serverBundleDownload.ts:370
- vscode-testing/src/testTree.ts:175 · vscode-testing/src/testTree.ts:197 — the two spans are one implementation copied and then locally edited — 100 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — vscode-testing/src/testTree.ts:175
- vscode-extension-core/src/keyHandlerUtils.ts:178 · vscode-extension-core/src/keyHandlerUtils.ts:188 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — vscode-extension-core/src/keyHandlerUtils.ts:178
- vscode-language-kotlin/src/kotlin/keyHandler.ts:875 · vscode-language-kotlin/src/kotlin/keyHandler.ts:906 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — vscode-language-kotlin/src/kotlin/keyHandler.ts:875
What to do
- Act on each finding's own remediation rather than one rule: the move depends on what recurs. Where the copies are executable blocks, give the shared part one home and call it from each site; where they are declarations, a listing, a specialisation already delegating to its base, or one shape repeated per entity, there is no call site and the move is a shared type, a generated set or a factory — sometimes there is nothing to extract.
R11 · Import Boundaries
- vscode-extension-core/src/keyHandlerTestUtils.ts:8 reaches into another package with a relative path (../node_modules/web-tree-sitter/web-tree-sitter.wasm) — import the package by name instead. — vscode-extension-core/src/keyHandlerTestUtils.ts:8
What to do
- Fix the listed violations: import through public entries (package exports / slice index), never reach into another layer or package's internals.
R2 · Cyclomatic Complexity
- projectRejectionReason has cyclomatic complexity 21 and cognitive complexity 25; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — vscode-extension-core/src/initializationSettings.ts:166
- (anonymous) has cyclomatic complexity 20 and cognitive complexity 18; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — vscode-extension-core/src/serverBundleDownload.ts:399
- component has cyclomatic complexity 20 and cognitive complexity 10; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — vscode-extension-core/src/editOptionsModel.ts:181
- (anonymous) has cyclomatic complexity 19 and cognitive complexity 18; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — vscode-language-kotlin/src/kotlin/keyHandler.ts:334
- startServer has cyclomatic complexity 18 and cognitive complexity 19; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — vscode-extension-core/src/lspClient.ts:931
- handleDoubleQuoteKey has cyclomatic complexity 17 and cognitive complexity 16; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — vscode-language-kotlin/src/kotlin/keyHandler.ts:142
- handleStringLiteralKey has cyclomatic complexity 16 and cognitive complexity 26; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — vscode-language-kotlin/src/kotlin/keyHandler.ts:243
- (anonymous) has cyclomatic complexity 16 and cognitive complexity 13; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — vscode-extension-core/src/handleKeyType.ts:37
- shouldAutoCloseOpeningDelimiter has cyclomatic complexity 16 and cognitive complexity 9; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — vscode-extension-core/src/keyHandlerUtils.ts:885
- (anonymous) has cyclomatic complexity 15 and cognitive complexity 15; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — vscode-extension-core/src/lspClient.ts:1133
- configOf has cyclomatic complexity 15 and cognitive complexity 14; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — vscode-jvm-testing/src/jvmTestLanguage.ts:179
- clearCachesAndRestart has cyclomatic complexity 14 and cognitive complexity 16; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — vscode-extension-core/src/lspClient.ts:281
- handleMultilineStringLiteralEnter has cyclomatic complexity 14 and cognitive complexity 16; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — vscode-language-kotlin/src/kotlin/keyHandler.ts:1223
- readServerBundleMetadata has cyclomatic complexity 14 and cognitive complexity 15; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — vscode-extension-core/src/serverBundleDownload.ts:175
- locate has cyclomatic complexity 14 and cognitive complexity 15; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — vscode-testing/src/teamCityReader.ts:136
- computeStatusTooltipContent has cyclomatic complexity 14 and cognitive complexity 13; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — vscode-extension-core/src/statusBarModel.ts:133
- handleRegularEnter has cyclomatic complexity 14 and cognitive complexity 11; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — vscode-language-kotlin/src/kotlin/keyHandler.ts:437
- handleFileCreated has cyclomatic complexity 13 and cognitive complexity 13; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — vscode-extension-core/src/fileTemplates.ts:24
- withInstallLock has cyclomatic complexity 12 and cognitive complexity 28; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — vscode-extension-core/src/serverBundleDownload.ts:509
- doStartLspClient has cyclomatic complexity 12 and cognitive complexity 26; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — vscode-extension-core/src/lspClient.ts:498
- getRegularEnterResult has cyclomatic complexity 12 and cognitive complexity 12; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — vscode-extension-core/src/keyHandlerUtils.ts:362
- (anonymous) has cyclomatic complexity 12 and cognitive complexity 10; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — vscode-testing/src/testPlan.ts:61
- feed has cyclomatic complexity 11 and cognitive complexity 13; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — vscode-extension-core/src/runTerminalModel.ts:70
- choose has cyclomatic complexity 11 and cognitive complexity 12; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — vscode-jvm-testing/src/jvmTestConfig.ts:122
- getClosedBlockCommentBodyIndent has cyclomatic complexity 11 and cognitive complexity 10; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — vscode-language-kotlin/src/kotlin/keyHandler.ts:870
- computeStatusText has cyclomatic complexity 11 and cognitive complexity 9; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — vscode-extension-core/src/statusBarModel.ts:114
R3 · Large Files
- vscode-language-kotlin/src/kotlin/keyHandler.ts has 1543 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — vscode-language-kotlin/src/kotlin/keyHandler.ts:1
- vscode-extension-core/src/lspClient.ts has 1352 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — vscode-extension-core/src/lspClient.ts:1
- vscode-extension-core/src/keyHandlerUtils.ts has 958 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — vscode-extension-core/src/keyHandlerUtils.ts:1
- vscode-extension-core/src/serverBundleDownload.ts has 763 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — vscode-extension-core/src/serverBundleDownload.ts:1
- vscode-extension-core/src/editOptionsModel.ts has 513 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — vscode-extension-core/src/editOptionsModel.ts:1
What to do
- Split each oversized file along the responsibilities already in it, into smaller focused modules in the same package.
R4 · Test Coverage
- No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one. (×5) — kotlin-vscode/launch-vscode.mjs:1, kotlin-vscode/unpack-server.mjs:1, kotlin-vscode/src/extension.ts:1, …
What to do
- Add tests that import the unreached modules (directly or through their public entry).
R6 · Tooling
- test ✓ · lint ✗ · typecheck ✓ — read from this repository's package.json scripts and corroborated against its CI workflows. A script counts when its name or command matches the step: `test` for the suite, `lint` or `prettier` for linting, `typecheck`/`type-check`/`tsc` for type checking. ✗ therefore means no script or CI step under those names was found, NOT that the step is absent from your pipeline — a task invoked by a runner this check does not read, or named something else entirely, is not seen and is worth confirming before acting on a cross. A ✓ means the wiring is DECLARED — a script or CI step under those names exists. It is not a statement that the step passes, or that it runs at all: nothing here installs a dependency or executes a suite.
What to do
- Add eslint as package.json scripts and run them in CI.
R7 · Dead Code
R8 · Dependency Hygiene
- Imported but not declared in any reachable package.json — installs work only by hoisting accident. — kotlin-vscode/rspack.base.config.ts:3
What to do
- Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.
R9 · Circular Imports
- vscode-extension-core/src/buildTask.ts → vscode-extension-core/src/lspClient.ts → vscode-extension-core/src/buildTask.ts (one verified cycle inside a mutually-dependent group of 15 files) — vscode-extension-core/src/buildTask.ts:35
What to do
- Break each cycle by extracting the shared piece into a module both sides can import.
X1 · Async correctness
X12 · Unreachable branch
X13 · Undrained process stream
X16 · Unfloored truncation loop
X18 · Disposal-pattern correctness
- `RunOutputTerminal` declares a disposal member — so it has told every caller it holds something worth releasing — and it constructs `writeEmitter` itself (line 102, `new EventEmitter`), which makes that instance its own. But `writeEmitter` is named in none of the methods the disposal search covered: `dispose` (line 149) — that is the disposal member plus every method it calls on `this` BY NAME, so a release reached through a base class, a callback or a registry is not followed and is worth checking before acting. The field is released nowhere else in the class and is never handed to anything else, so no other owner can be releasing it. On what was read, the class's disposal releases everything except the one thing it owns. Whatever `EventEmitter` holds until its own `dispose()` runs — the listeners subscribed to it, a pending timer, GPU memory — outlives this instance's disposal: a subscriber that registered through it stays attached, and anything that holds the subscription keeps the whole chain reachable. Release it in the disposal member (`this.writeEmitter.dispose()`), or, if it truly does not need releasing, drop the disposal member so the claim and the behaviour agree. — vscode-extension-core/src/runTerminal.ts:102
What to do
- Each finding names the value and the span that decides who owns it — the `new` that created it, or the constructor parameter that handed it over. Confirm ownership from that span, then make the disposal match it: release what this type created, leave what it was injected with to whoever created THAT, and drop a finalizer whose type holds nothing unmanaged to release.
X2 · Cancellation propagation
- Only 3/5 async functions that make a cancellable request (fetch, axios, ky, ofetch, got, undici, node:http) accept an AbortSignal or pass one on, so a request keeps running after whatever wanted it has given up — a page navigated away from, an unmounted component, a timed-out job. Take a `signal` (or an options object that carries one) and hand it to the request; where nothing could ever cancel the call, omitting it is a deliberate choice — judge against how the function is used.
- `checkGeoRestricted` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. — vscode-extension-core/src/geoRestriction.ts:13
- `downloadFile` holds an AbortSignal but calls `pipeline(…)` without it, so its caller's cancellation never reaches that call and it runs to its end after whatever wanted it has given up. Hand the signal on: `pipeline(…, { signal })`. — vscode-extension-core/src/serverBundleDownload.ts:381
What to do
- Thread an AbortSignal through async functions that make requests, so the work stops when its caller gives up.
X21 · Side-effecting pattern guard
X23 · Unguarded diagnostic materialisation
X25 · Inert configuration knob
X27 · Collection changed while being enumerated
X29 · Per-element action decided by a fixed element
X3 · Exception handling
- An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it. (×4) — vscode-extension-core/src/editOptions.ts:97, vscode-extension-core/src/intellijExtensions.ts:268, vscode-extension-core/src/lspClient.ts:554, …
- `.then(…, () => {})` handles the rejection by doing nothing — the failure is discarded with no log and no rethrow, and the chain carries on as if the work succeeded. Log it through whatever this codebase already uses to report problems, hand it to a caller that can (`next(error)`, a returned rejection), or don't catch it. — vscode-extension-core/src/intellijExtensions.ts:101
- `.catch(() => {})` handles the rejection by doing nothing — the failure is discarded with no log and no rethrow, and the chain carries on as if the work succeeded. Log it through whatever this codebase already uses to report problems, hand it to a caller that can (`next(error)`, a returned rejection), or don't catch it. — vscode-extension-core/src/serverBundleDownload.ts:561
- `catch (_: Exception)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. — features-impl/kotlin/src/com/jetbrains/ls/api/features/impl/kotlin/typeHierarchy/LSKotlinTypeHierarchyProvider.kt:395
What to do
- Swallowed exception (empty catch)
X5 · Nullable reference types
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 78% | Strong | Solid. |
| Architecture | 56% | Adequate — gated by AX7 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Maturity | 60% | Adequate — gated by M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 44% | Weak — gated by P1, P3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 100% | Checked 2 of 5 | Strongest area. |
| Performance | 60% | Adequate | Acceptable, with room to improve. |
Unscored — 3 check(s) recorded observations but carry no score
- SC1 Supply-chain hygiene — 5 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
- X10 Duplicated predicate — 4 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
- X7 Silent fallback defaults — 1 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 — 67 check(s) not relevant to this codebase
- AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
- AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
- AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
- AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
- AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
- AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
- AX1 Captive dependencies — Not applicable: this repository's Kotlin imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's; this repository's JavaScript imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's; this repository's TypeScript imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's.
- AX2 Stateful singletons — No container singleton was found, so there is no shared instance for concurrent requests to race on. No class in this Kotlin code is a Spring, JSR-330 or CDI singleton bean. TypeScript/JavaScript runs each process's requests on one event loop, so no two requests write a shared object at the same instant (interleaving across an await is a different defect).
- 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 44% of this repository's production lines — kotlin (16,255 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- AX8 Test isolation — no test/production split to check
- AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
- AXB1 Runtime evidence locked — no reproducible boot — This repository has nothing the runtime tiers could boot or serve — no markup, no UI framework or web-server dependency, no UI component source, no native UI project and no API definition — nothing here is a surface to boot — so runtime a11y/egress/header evidence has no subject here. Not applicable: this is neither a gap in the scan nor a finding about your code.
- C1 Data Protection — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a Room, JPA or MongoDB entity, an Exposed or Ktorm table, or in a SQL CREATE TABLE or ALTER TABLE — and no database or data-store client (Room, Exposed, SQLDelight, Realm, JPA, JDBC, MongoDB, Firebase, …) imported either, so this repository keeps no data at rest for these controls to protect.
- C2 Access Controls — Not assessed: these authorization controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks authorization controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- C3 Audit Trail — No personal data detected in a persisted data model — no PII-named column (email, first_name, date_of_birth, phone_number, …) or stored credential on a Room, JPA or MongoDB entity, an Exposed or Ktorm table, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store client (Room, Exposed, SQLDelight, Realm, JPA, JDBC, MongoDB, Firebase, …) imported either, so this repository keeps no sensitive data whose changes an audit trail would record. If it does (through a store configured outside this repository, for instance), the trail belongs to wherever that data is stored.
- C4 Data Retention — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a Room, JPA or MongoDB entity, an Exposed or Ktorm table, or in a SQL CREATE TABLE or ALTER TABLE — and no database or data-store client (Room, Exposed, SQLDelight, Realm, JPA, JDBC, MongoDB, Firebase, …) imported either, so this repository keeps no personal data whose lifetime a retention limit would bound.
- C5 Data-Subject Rights — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a Room, JPA or MongoDB entity, an Exposed or Ktorm table, or in a SQL CREATE TABLE or ALTER TABLE — and no database or data-store client (Room, Exposed, SQLDelight, Realm, JPA, JDBC, MongoDB, Firebase, …) imported either, so this repository keeps no personal data for a data subject to erase, export or consent over.
- D11 Test Reliability — Test reliability not measured — JavaScript/TypeScript suite did not run
- D12 Dependency Hygiene — Dependency currency not established — this repository commits no lockfile to resolve
- D14 License Compliance — npm licences not graded — this npm repository commits no lockfile this pass can resolve
- D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
- D20 ADR Quality — N/A — ADRs are expected on deployable products with a user-facing host, not consumed libraries; no ADR log is required here.
- D21 Naming Consistency — D21 withholds its case and prefix conventions rows: 8 candidate(s) found and not reported.
- D22 Internal API Consistency — The exposed public-API surface could not be collected — no C#/VB projects loaded.
- D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D25 ADR Conformance — no ADRs to check
- D26 Project Cohesion — D26 measured no build unit over this repository's .kt source. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
- D32 Data Compliance (PII/GDPR) — 124 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
- D36 Supply-chain Provenance & Signing — No CI/build pipeline found (.github/.forgejo/.gitea workflows, .circleci, .buildkite, .woodpecker, .teamcity, .gitlab-ci.yml, .travis.yml, bitbucket-pipelines.yml, .drone.yml, .cirrus.yml, .woodpecker.yml, appveyor.yml, azure-pipelines*.yml, .pipelines/, .vsts-ci/, .azuredevops/, Jenkinsfile); there is no build to attest provenance for.
- 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.
- D44 Platform End-of-Life — Platform end-of-life not assessed — this repository declares no platform this pass reads
- D5 Coupling — D5 reads a .NET project-reference graph only — this repository's production source is .kt, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
- D8 Code Coverage — Coverage not measured — JavaScript/TypeScript suite
- DM1 Domain Modelling — applicable but not scored (2 of 3 signals for this style — below the bar we score at): 4 value object(s); 4 domain event(s); its domain events are published by services or handlers — no domain entity raises one
- ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
- ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- GD1 Unfinished & placeholder code — no source files were read — this check reads C#, F#, JavaScript/TypeScript, Dart, Ruby and Scala, and none was read for this repository's product. That is a limit of the analyzer, not a finding about your code.
- IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- P12 CI test-gate honesty — no CI workflow found
- P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the JVM, JavaScript/TypeScript source, so there is no service whose uptime a failing dependency could take down
- P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
- P9 Domain vs controller coverage — coverage not measured: this check compares the coverage of the analyzer's own test run across the domain and web layers, and that run measured none here — Test coverage (D8) says why
- PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for `@Benchmark` in a Java, Kotlin or Scala file importing JMH or kotlinx-benchmark, Jetpack Benchmark's `measureRepeated` in a file importing androidx.benchmark, or JMH/kotlinx-benchmark/androidx.benchmark in a pom.xml, Gradle or sbt build, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
- PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
- R5 Dependency Freshness — no package-lock.json — dependency freshness not measured (would require an npm lockfile); JS/npm CVEs are scored in D30 (Dependency Vulnerabilities), which answers every ecosystem
- S1 Web-Security Posture — Not assessed: these web-security controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks web-security controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- X14 Bypassable address classification — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X17 Uncapped recursion over a caller-supplied document — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- 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
- 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
- X22 Contradicted release guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X24 Document value interpolated into markup unescaped — X24 reached only 44% of this repository's production lines — kotlin (16,255 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- 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
- X28 Index access outside its own emptiness guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- 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 — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X4 Structured logging — This check asks whether log calls keep a message's values apart from its text, which needs a logger that can carry them as fields. This repository's Kotlin was read, and it logs through none that an assembled message defeats: Android's `Log` and Timber, java.util.logging and log4j-api-kotlin take one finished message (as log4net does in C#), or it makes no call through a named logger at all. Calls made through SLF4J, log4j 2 or kotlin-logging (`LoggerFactory.getLogger`, `KotlinLogging.logger {}`) would be judged.
- X6 Hand-rolled structured-format parsing — 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 — 11 finding(s)
- Boundary-crossing change coupling: LSSimpleCodeActionProvider.kt ↔ LSKotlinCompilerDiagnosticsFixesCodeActionProvider.kt api.features/src/com/jetbrains/ls/api/features/codeActions/LSSimpleCodeActionProvider.kt:1
- Boundary-crossing change coupling: LSSimpleCodeActionProvider.kt ↔ LSKotlinIntentionCodeActionProvider.kt api.features/src/com/jetbrains/ls/api/features/codeActions/LSSimpleCodeActionProvider.kt:1
- Boundary-crossing change coupling: LSSimpleCodeActionProvider.kt ↔ LSCommonSyntaxErrorDiagnosticProvider.kt api.features/src/com/jetbrains/ls/api/features/codeActions/LSSimpleCodeActionProvider.kt:1
- Boundary-crossing change coupling: LSSimpleCodeActionProvider.kt ↔ LSKotlinCompilerDiagnosticsProvider.kt api.features/src/com/jetbrains/ls/api/features/codeActions/LSSimpleCodeActionProvider.kt:1
- Boundary-crossing change coupling: LSSimpleCodeActionProvider.kt ↔ LSCommonInspectionDiagnosticProvider.kt api.features/src/com/jetbrains/ls/api/features/codeActions/LSSimpleCodeActionProvider.kt:1
- Boundary-crossing change coupling: LSSimpleCodeActionProvider.kt ↔ LSCommonDefinitionProvider.kt api.features/src/com/jetbrains/ls/api/features/codeActions/LSSimpleCodeActionProvider.kt:1
- Boundary-crossing change coupling: LSSimpleCodeActionProvider.kt ↔ LSCommonReferencesProvider.kt api.features/src/com/jetbrains/ls/api/features/codeActions/LSSimpleCodeActionProvider.kt:1
- Boundary-crossing change coupling: LSSimpleCodeActionProvider.kt ↔ LSKotlinPackageDefinitionProvider.kt api.features/src/com/jetbrains/ls/api/features/codeActions/LSSimpleCodeActionProvider.kt:1
- Boundary-crossing change coupling: LSSimpleCodeActionProvider.kt ↔ LSKotlinSemanticTokensProvider.kt api.features/src/com/jetbrains/ls/api/features/codeActions/LSSimpleCodeActionProvider.kt:1
- Unlisted import 'ts-checker-rspack-plugin' kotlin-vscode/rspack.base.config.ts:3
- Import cycle (2 files) vscode-extension-core/src/buildTask.ts:35
Serious — 180 finding(s)
- Cross-slice coupling: codeActions → commands api.features/src/com/jetbrains/ls/api/features/codeActions/LSSimpleCodeActionProvider.kt:78
- Cross-slice coupling: resolve → configuration api.features/src/com/jetbrains/ls/api/features/resolve/ResolveDataWithConfigurationEntryId.kt:10
- Cross-slice coupling: impl → configuration features-impl/common/src/com/jetbrains/ls/api/features/impl/common/callHierarchy/LSCallHierarchyProviderBase.kt:169
- Cross-slice coupling: impl → utils features-impl/common/src/com/jetbrains/ls/api/features/impl/common/callHierarchy/LSCallHierarchyProviderBase.kt:194
- Cross-slice coupling: impl → utils features-impl/common/src/com/jetbrains/ls/api/features/impl/common/callHierarchy/LSCallHierarchyProviderBase.kt:204
- Cross-slice coupling: impl → language features-impl/common/src/com/jetbrains/ls/api/features/impl/common/completion/LSCompletionProviderHelper.kt:71
- Cross-slice coupling: impl → language features-impl/common/src/com/jetbrains/ls/api/features/impl/common/completion/LSCompletionProviderHelper.kt:343
- Cross-slice coupling: impl → language features-impl/common/src/com/jetbrains/ls/api/features/impl/common/configuration/LSCommonConfiguration.kt:28
- Cross-slice coupling: impl → language features-impl/common/src/com/jetbrains/ls/api/features/impl/common/configuration/LSCommonServerExtension.kt:8
- Cross-slice coupling: impl → commands features-impl/common/src/com/jetbrains/ls/api/features/impl/common/decompiler/LSDecompileCommandDescriptorProvider.kt:22
- Cross-slice coupling: impl → codeActions features-impl/common/src/com/jetbrains/ls/api/features/impl/common/diagnostics/LSCommonInspectionOptionsCodeActionProvider.kt:82
- Cross-slice coupling: impl → commands features-impl/common/src/com/jetbrains/ls/api/features/impl/common/fileTemplates/LSInterpolateFileTemplateCommandDescriptorProvider.kt:35
- Cross-slice coupling: impl → configuration features-impl/common/src/com/jetbrains/ls/api/features/impl/common/inlayHints/LSInlayHintsProviderBase.kt:70
- Cross-slice coupling: impl → utils features-impl/common/src/com/jetbrains/ls/api/features/impl/common/inlayHints/LSInlayHintsProviderBase.kt:480
- Cross-slice coupling: impl → configuration features-impl/common/src/com/jetbrains/ls/api/features/impl/common/inlayHints/LSInlayHintsProviderBase.kt:493
- Cross-slice coupling: impl → commands features-impl/common/src/com/jetbrains/ls/api/features/impl/common/modcommands/LSApplyFixCommandDescriptorProvider.kt:42
- Cross-slice coupling: impl → semanticTokens features-impl/common/src/com/jetbrains/ls/api/features/impl/common/semanticTokens/LSHighlightingSemanticTokens.kt:52
- Cross-slice coupling: impl → commands features-impl/common/src/com/jetbrains/ls/api/features/impl/common/stackTrace/LSStackTraceCommandDescriptorProvider.kt:37
- Cross-slice coupling: impl → language features-impl/java-base/src/com/jetbrains/ls/api/features/impl/javaBase/JavaBaseLanguageServerExtension.kt:8
- Cross-slice coupling: impl → language features-impl/java-base/src/com/jetbrains/ls/api/features/impl/javaBase/LSJavaBaseLanguageConfiguration.kt:13
- Cross-slice coupling: impl → language features-impl/java-base/src/com/jetbrains/ls/api/features/impl/javaBase/LSJavaLanguage.kt:7
- Cross-slice coupling: impl → configuration features-impl/kotlin/src/com/jetbrains/ls/api/features/impl/kotlin/callHierarchy/LSKotlinCallHierarchyProvider.kt:26
- Cross-slice coupling: impl → configuration features-impl/kotlin/src/com/jetbrains/ls/api/features/impl/kotlin/completion/LSKotlinCompletionProvider.kt:28
- Cross-slice coupling: impl → language features-impl/kotlin/src/com/jetbrains/ls/api/features/impl/kotlin/configuration/KotlinLanguageServerExtension.kt:8
- Cross-slice coupling: impl → language features-impl/kotlin/src/com/jetbrains/ls/api/features/impl/kotlin/configuration/LSKotlinLanguageConfiguration.kt:72
- TodoComment vscode-extension-core/src/lspClient.ts:753
- TodoComment features-impl/kotlin/src/com/jetbrains/ls/api/features/impl/kotlin/semanticTokens/LSKotlinSemanticTokensProvider.kt:117
- TodoComment features-impl/kotlin/psi/src/com/jetbrains/ls/api/features/impl/kotlin/psi/LSKotlinDocumentSymbolCustomizer.kt:96
- TodoComment features-impl/kotlin/psi/src/com/jetbrains/ls/api/features/impl/kotlin/psi/LSKotlinWorkspaceSymbolCustomizer.kt:47
- TodoComment features-impl/common/src/com/jetbrains/ls/api/features/impl/common/modcommands/ModCommandData.kt:503
- TodoComment features-impl/common/src/com/jetbrains/ls/api/features/impl/common/diagnostics/LSCommonIntentionFixesCodeActionProvider.kt:73
- TodoComment api.features/src/com/jetbrains/ls/api/features/semanticTokens/LSSemanticTokens.kt:31
- TodoComment api.features/src/com/jetbrains/ls/api/features/diagnostics/LSDiagnosticProvider.kt:16
- TodoComment api.features/src/com/jetbrains/ls/api/features/commands/document/LSDocumentCommandComandExecutor.kt:37
- Sync-over-async blocking vscode-extension-core/src/lspClient.ts:840
- Sync-over-async blocking vscode-extension-core/src/serverBundleDownload.ts:100
- Sync-over-async blocking vscode-extension-core/src/serverBundleDownload.ts:106
- Sync-over-async blocking vscode-extension-core/src/serverBundleDownload.ts:117
- Sync-over-async blocking vscode-extension-core/src/serverBundleDownload.ts:121
- Sync-over-async blocking vscode-extension-core/src/serverBundleDownload.ts:129
- Sync-over-async blocking vscode-extension-core/src/serverBundleDownload.ts:144
- Sync-over-async blocking vscode-extension-core/src/serverBundleDownload.ts:162
- Sync-over-async blocking vscode-extension-core/src/serverBundleDownload.ts:362
- Swallowed exception (empty catch) vscode-extension-core/src/editOptions.ts:97
- Swallowed exception (empty catch) vscode-extension-core/src/intellijExtensions.ts:101
- Swallowed exception (empty catch) vscode-extension-core/src/intellijExtensions.ts:268
- Swallowed exception (empty catch) vscode-extension-core/src/lspClient.ts:554
- Swallowed exception (empty catch) vscode-extension-core/src/serverBundleDownload.ts:561
- Swallowed exception (empty catch) kotlin-vscode/launch-vscode.mjs:209
- FileTooLong: kotlin/keyHandler.ts vscode-language-kotlin/src/kotlin/keyHandler.ts
- FileTooLong: src/lspClient.ts vscode-extension-core/src/lspClient.ts
- FileTooLong: src/keyHandlerUtils.ts vscode-extension-core/src/keyHandlerUtils.ts
- FileTooLong: src/serverBundleDownload.ts vscode-extension-core/src/serverBundleDownload.ts
- FileTooLong: modcommands/ModCommandData.kt features-impl/common/src/com/jetbrains/ls/api/features/impl/common/modcommands/ModCommandData.kt
- No test reaches this file kotlin-vscode/launch-vscode.mjs:1
- No test reaches this file kotlin-vscode/unpack-server.mjs:1
- No test reaches this file kotlin-vscode/src/extension.ts:1
- No test reaches this file vscode-language-kotlin/src/kotlin/module.ts:1
- No test reaches this file vscode-jvm-testing/src/module.ts:1
- JavaScript dependencies are not locked kotlin-vscode/package.json:41
- JavaScript dependencies are not locked vscode-extension-core/package.json:26
- JavaScript dependencies are not locked vscode-jvm-testing/package.json:13
- JavaScript dependencies are not locked vscode-language-kotlin/package.json:13
- JavaScript dependencies are not locked vscode-testing/package.json:14
- Change coupling: LSJavaBaseLanguageConfiguration.kt ↔ LSKotlinLanguageConfiguration.kt features-impl/java-base/src/com/jetbrains/ls/api/features/impl/javaBase/LSJavaBaseLanguageConfiguration.kt:1
- Change coupling: LSCommonInspectionDiagnosticProvider.kt ↔ LSKotlinCompilerDiagnosticsProvider.kt features-impl/common/src/com/jetbrains/ls/api/features/impl/common/diagnostics/LSCommonInspectionDiagnosticProvider.kt:1
- Change coupling: LSCommonDefinitionProvider.kt ↔ LSCommonReferencesProvider.kt features-impl/common/src/com/jetbrains/ls/api/features/impl/common/definitions/LSCommonDefinitionProvider.kt:1
- Change coupling: LSKotlinCompilerDiagnosticsProvider.kt ↔ LSKotlinIntentionCodeActionProvider.kt features-impl/kotlin/src/com/jetbrains/ls/api/features/impl/kotlin/diagnostics/compiler/LSKotlinCompilerDiagnosticsProvider.kt:1
- Edited copy of a member (5 corresponding lines) api.features/src/com/jetbrains/ls/api/features/callHierarchy/LSCallHierarchy.kt:24
- Edited copy of a member (5 corresponding lines) api.features/src/com/jetbrains/ls/api/features/callHierarchy/LSCallHierarchy.kt:31
- Edited copy of a member (5 corresponding lines) features-impl/common/src/com/jetbrains/ls/api/features/impl/common/diagnostics/LSCommonSyntaxErrorDiagnosticProvider.kt:22
- KindsKt.getKind (cyclomatic 20) features-impl/kotlin/psi/src/com/jetbrains/ls/api/features/impl/kotlin/psi/kinds.kt:21
- KindsKt.getKind (cyclomatic 20) features-impl/kotlin/src/com/jetbrains/ls/api/features/impl/kotlin/symbols/kinds.kt:21
- Hotspot: features-impl/common/src/com/jetbrains/ls/api/features/impl/common/modcommands/ModCommandData.kt features-impl/common/src/com/jetbrains/ls/api/features/impl/common/modcommands/ModCommandData.kt:334
- Hotspot: vscode-extension-core/src/lspClient.ts vscode-extension-core/src/lspClient.ts:1123
- Change-coupling hub: LSKotlinPackageDefinitionProvider.kt → LSCommonDefinitionProvider.kt, LSCommonInspectionDiagnosticProvider.kt, LSCommonSyntaxErrorDiagnosticProvider.kt, LSHoverProviderBase.kt, LSCommonReferencesProvider.kt, LSKotlinSemanticTokensProvider.kt features-impl/kotlin/src/com/jetbrains/ls/api/features/impl/kotlin/definitions/LSKotlinPackageDefinitionProvider.kt
- Change-coupling hub: LSCommonSyntaxErrorDiagnosticProvider.kt → LSCommonInspectionDiagnosticProvider.kt, LSKotlinCompilerDiagnosticsFixesCodeActionProvider.kt, LSKotlinCompilerDiagnosticsProvider.kt, LSKotlinIntentionCodeActionProvider.kt features-impl/common/src/com/jetbrains/ls/api/features/impl/common/diagnostics/LSCommonSyntaxErrorDiagnosticProvider.kt
- Edited copy of a member (21 corresponding lines) features-impl/java-base/src/com/jetbrains/ls/api/features/impl/javaBase/LSJavaPackageDefinitionProvider.kt:35
- Edited copy of a member (21 corresponding lines) features-impl/common/src/com/jetbrains/ls/api/features/impl/common/callHierarchy/LSCallHierarchyProviderBase.kt:58
- Edited copy of a member (15 corresponding lines) api.features/src/com/jetbrains/ls/api/features/implementation/LSImplementation.kt:20
- Edited copy of a member (15 corresponding lines) features-impl/common/src/com/jetbrains/ls/api/features/impl/common/rename/renameUtils.kt:23
- Duplicated block (14 lines × 2 locations) vscode-extension-core/src/keyHandlerUtils.ts:119
- Duplicated block (14 lines × 2 locations) vscode-extension-core/src/keyHandlerUtils.ts:668
- Duplicated block (13 lines × 2 locations) vscode-extension-core/src/keyHandlerUtils.ts:406
- Duplicated block (13 lines × 2 locations) vscode-extension-core/src/serverBundleDownload.ts:783
- Duplicated block (10 lines × 2 locations) vscode-extension-core/src/keyHandlerUtils.ts:573
- Duplicated block (10 lines × 2 locations) vscode-extension-core/src/serverBundleDownload.ts:370
- Async function without AbortSignal: checkGeoRestricted vscode-extension-core/src/geoRestriction.ts:13
- Async function without AbortSignal: downloadFile vscode-extension-core/src/serverBundleDownload.ts:381
- LSKotlinSemanticTokensProvider.getRangeWithToken (cyclomatic 44) features-impl/kotlin/src/com/jetbrains/ls/api/features/impl/kotlin/semanticTokens/LSKotlinSemanticTokensProvider.kt:138
- ModCommandData.from (cyclomatic 38) features-impl/common/src/com/jetbrains/ls/api/features/impl/common/modcommands/ModCommandData.kt:334
- ModCommandDataKt.executeCommand (cyclomatic 35) features-impl/common/src/com/jetbrains/ls/api/features/impl/common/modcommands/ModCommandData.kt:554
- ModCompletionCommandConverter.split (cyclomatic 27) features-impl/common/src/com/jetbrains/ls/api/features/impl/common/completion/ModCompletionCommandConverter.kt:215
- OptionPaneReader.read (cyclomatic 25) features-impl/common/src/com/jetbrains/ls/api/features/impl/common/modcommands/EditOptions.kt:406
- serverBundleDownload.downloadFile (cyclomatic 24) vscode-extension-core/src/serverBundleDownload.ts:381
- initializationSettings.projectRejectionReason (cyclomatic 21) vscode-extension-core/src/initializationSettings.ts:166
- FormRenderer.component (cyclomatic 21) vscode-extension-core/src/editOptionsModel.ts:181
- lspClient.registerSettingsChangeWatcher (cyclomatic 19) vscode-extension-core/src/lspClient.ts:1123
- keyHandler.handleEnter (cyclomatic 19) vscode-language-kotlin/src/kotlin/keyHandler.ts:318
- keyHandler.handleDoubleQuoteKey (cyclomatic 17) vscode-language-kotlin/src/kotlin/keyHandler.ts:142
- MainEdit.convertTemplate (cyclomatic 16) features-impl/common/src/com/jetbrains/ls/api/features/impl/common/completion/ModCompletionCommandConverter.kt:90
- lspClient.doStartLspClient (cyclomatic 16) vscode-extension-core/src/lspClient.ts:498
- lspClient.startServer (cyclomatic 16) vscode-extension-core/src/lspClient.ts:931
- handleKeyType.registerHandleKeyType (cyclomatic 16) vscode-extension-core/src/handleKeyType.ts:29
- Repeated repair: features-impl/common/src/com/jetbrains/ls/api/features/impl/common/diagnostics/LSInspectionManager.kt features-impl/common/src/com/jetbrains/ls/api/features/impl/common/diagnostics/LSInspectionManager.kt:64
- ModCompletionCommandConverter.split (cognitive 57) features-impl/common/src/com/jetbrains/ls/api/features/impl/common/completion/ModCompletionCommandConverter.kt:215
- ModCommandDataKt.executeCommand (cognitive 38) features-impl/common/src/com/jetbrains/ls/api/features/impl/common/modcommands/ModCommandData.kt:554
- LSKotlinSemanticTokensProvider.getRangeWithToken (cognitive 38) features-impl/kotlin/src/com/jetbrains/ls/api/features/impl/kotlin/semanticTokens/LSKotlinSemanticTokensProvider.kt:138
- lspClient.doStartLspClient (cognitive 38) vscode-extension-core/src/lspClient.ts:498
- ModCommandData.from (cognitive 34) features-impl/common/src/com/jetbrains/ls/api/features/impl/common/modcommands/ModCommandData.kt:334
- serverBundleDownload.withInstallLock (cognitive 28) vscode-extension-core/src/serverBundleDownload.ts:509
- LSCommonIntentionFixesCodeActionProvider.infoInspections (cognitive 26) features-impl/common/src/com/jetbrains/ls/api/features/impl/common/diagnostics/LSCommonIntentionFixesCodeActionProvider.kt:87
- MainEdit.convertTemplate (cognitive 25) features-impl/common/src/com/jetbrains/ls/api/features/impl/common/completion/ModCompletionCommandConverter.kt:90
- initializationSettings.projectRejectionReason (cognitive 25) vscode-extension-core/src/initializationSettings.ts:166
- keyHandler.handleStringLiteralKey (cognitive 25) vscode-language-kotlin/src/kotlin/keyHandler.ts:243
- serverBundleDownload.downloadFile (cognitive 22) vscode-extension-core/src/serverBundleDownload.ts:381
- lspClient.ensureBundledServerLauncher (cognitive 21) vscode-extension-core/src/lspClient.ts:759
- lspClient.registerSettingsChangeWatcher (cognitive 19) vscode-extension-core/src/lspClient.ts:1123
- RunStepsKt.run (cognitive 18) buildtool.api/src/com/jetbrains/ls/buildtool/api/run/RunSteps.kt:29
- lspClient.startServer (cognitive 17) vscode-extension-core/src/lspClient.ts:931
- keyHandler.handleEnter (cognitive 16) vscode-language-kotlin/src/kotlin/keyHandler.ts:318
- MethodTooLong: ModCommandDataKt.executeCommand features-impl/common/src/com/jetbrains/ls/api/features/impl/common/modcommands/ModCommandData.kt:554
- Members sharing a duplicated core (5 members, 50+ identical tokens) features-impl/common/src/com/jetbrains/ls/api/features/impl/common/diagnostics/LSCommonInjectionSyntaxErrorDiagnosticProvider.kt:33
- Edited copy of a member (41 corresponding lines) features-impl/common/src/com/jetbrains/ls/api/features/impl/common/completion/ModCompletionCommandConverter.kt:90
- Edited copy of a member (16 corresponding lines) features-impl/kotlin/src/com/jetbrains/ls/api/features/impl/kotlin/typeHierarchy/LSKotlinTypeHierarchyProvider.kt:277
- Edited copy of a member (14 corresponding lines) features-impl/kotlin/src/com/jetbrains/ls/api/features/impl/kotlin/typeHierarchy/LSKotlinTypeHierarchyProvider.kt:116
- Edited copy of a member (12 corresponding lines) features-impl/common/src/com/jetbrains/ls/api/features/impl/common/callHierarchy/LSCallHierarchyProviderBase.kt:44
- Edited copy of a member (17 corresponding lines) api.features/src/com/jetbrains/ls/api/features/diagnostics/LSDiagnostic.kt:21
- Edited copy of a member (8 corresponding lines) api.features/src/com/jetbrains/ls/api/features/semanticTokens/LSSemanticTokens.kt:34
- Edited copy of a member (9 corresponding lines) features-impl/common/src/com/jetbrains/ls/api/features/impl/common/callHierarchy/LSCallHierarchyProviderBase.kt:172
- Duplicated block (32 lines × 2) features-impl/kotlin/psi/src/com/jetbrains/ls/api/features/impl/kotlin/psi/kinds.kt:21
- Duplicated block (12–16 lines × 2) buildtool.api/src/com/jetbrains/ls/buildtool/api/run/RunSteps.kt:79
- Duplicated block (4–5 lines × 5) features-impl/common/src/com/jetbrains/ls/api/features/impl/common/diagnostics/LSCommonInjectionSyntaxErrorDiagnosticProvider.kt:36
- Duplicated block (5 lines × 2) features-impl/kotlin/src/com/jetbrains/ls/api/features/impl/kotlin/superDeclarations/LSKotlinSuperDeclarationsProvider.kt:47
- No CI pipeline
- Duplicated block (15 lines × 2 locations) vscode-language-kotlin/src/kotlin/keyHandler.ts:609
- Duplicated block (11 lines × 2 locations) vscode-language-kotlin/src/kotlin/keyHandler.ts:173
- Duplicated block with local edits (10 matched lines × 2 locations) vscode-testing/src/testTree.ts:175
- Duplicated block (9 lines × 2 locations) vscode-extension-core/src/keyHandlerUtils.ts:178
- Duplicated block (7 lines × 2 locations) vscode-language-kotlin/src/kotlin/keyHandler.ts:875
- Boundary violation [package:relative-cross-package] vscode-extension-core/src/keyHandlerTestUtils.ts:8
- Complex function projectRejectionReason (cyclomatic 21, cognitive 25) vscode-extension-core/src/initializationSettings.ts:166
- Complex function (anonymous) (cyclomatic 20, cognitive 18) vscode-extension-core/src/serverBundleDownload.ts:399
- Complex function component (cyclomatic 20, cognitive 10) vscode-extension-core/src/editOptionsModel.ts:181
- Complex function (anonymous) (cyclomatic 19, cognitive 18) vscode-language-kotlin/src/kotlin/keyHandler.ts:334
- Complex function startServer (cyclomatic 18, cognitive 19) vscode-extension-core/src/lspClient.ts:931
- Complex function handleDoubleQuoteKey (cyclomatic 17, cognitive 16) vscode-language-kotlin/src/kotlin/keyHandler.ts:142
- Complex function handleStringLiteralKey (cyclomatic 16, cognitive 26) vscode-language-kotlin/src/kotlin/keyHandler.ts:243
- Complex function (anonymous) (cyclomatic 16, cognitive 13) vscode-extension-core/src/handleKeyType.ts:37
- Complex function shouldAutoCloseOpeningDelimiter (cyclomatic 16, cognitive 9) vscode-extension-core/src/keyHandlerUtils.ts:885
- Complex function (anonymous) (cyclomatic 15, cognitive 15) vscode-extension-core/src/lspClient.ts:1133
- Complex function configOf (cyclomatic 15, cognitive 14) vscode-jvm-testing/src/jvmTestLanguage.ts:179
- Complex function clearCachesAndRestart (cyclomatic 14, cognitive 16) vscode-extension-core/src/lspClient.ts:281
- Complex function handleMultilineStringLiteralEnter (cyclomatic 14, cognitive 16) vscode-language-kotlin/src/kotlin/keyHandler.ts:1223
- Complex function readServerBundleMetadata (cyclomatic 14, cognitive 15) vscode-extension-core/src/serverBundleDownload.ts:175
- Complex function locate (cyclomatic 14, cognitive 15) vscode-testing/src/teamCityReader.ts:136
- Complex function computeStatusTooltipContent (cyclomatic 14, cognitive 13) vscode-extension-core/src/statusBarModel.ts:133
- Complex function handleRegularEnter (cyclomatic 14, cognitive 11) vscode-language-kotlin/src/kotlin/keyHandler.ts:437
- Complex function handleFileCreated (cyclomatic 13, cognitive 13) vscode-extension-core/src/fileTemplates.ts:24
- Complex function withInstallLock (cyclomatic 12, cognitive 28) vscode-extension-core/src/serverBundleDownload.ts:509
- Complex function doStartLspClient (cyclomatic 12, cognitive 26) vscode-extension-core/src/lspClient.ts:498
- Complex function getRegularEnterResult (cyclomatic 12, cognitive 12) vscode-extension-core/src/keyHandlerUtils.ts:362
- Complex function (anonymous) (cyclomatic 12, cognitive 10) vscode-testing/src/testPlan.ts:61
- Complex function feed (cyclomatic 11, cognitive 13) vscode-extension-core/src/runTerminalModel.ts:70
- Complex function choose (cyclomatic 11, cognitive 12) vscode-jvm-testing/src/jvmTestConfig.ts:122
- Complex function getClosedBlockCommentBodyIndent (cyclomatic 11, cognitive 10) vscode-language-kotlin/src/kotlin/keyHandler.ts:870
- Complex function computeStatusText (cyclomatic 11, cognitive 9) vscode-extension-core/src/statusBarModel.ts:114
- vscode-language-kotlin/src/kotlin/keyHandler.ts: 1543 lines of code vscode-language-kotlin/src/kotlin/keyHandler.ts:1
- vscode-extension-core/src/lspClient.ts: 1352 lines of code vscode-extension-core/src/lspClient.ts:1
- vscode-extension-core/src/keyHandlerUtils.ts: 958 lines of code vscode-extension-core/src/keyHandlerUtils.ts:1
- vscode-extension-core/src/serverBundleDownload.ts: 763 lines of code vscode-extension-core/src/serverBundleDownload.ts:1
- vscode-extension-core/src/editOptionsModel.ts: 513 lines of code vscode-extension-core/src/editOptionsModel.ts:1
- No lint script
- Owned disposable field is never released vscode-extension-core/src/runTerminal.ts:102
- Swallowed exception (caught, then discarded) features-impl/kotlin/src/com/jetbrains/ls/api/features/impl/kotlin/typeHierarchy/LSKotlinTypeHierarchyProvider.kt:395
Minor — 20 finding(s)
- Orphaned file api.features/src/com/jetbrains/ls/api/features/semanticTokens/encoding/SemanticTokensEncoder.kt:1
- Orphaned file api.features/src/com/jetbrains/ls/api/features/semanticTokens/encoding/SemanticTokensDecoder.kt:1
- Orphaned file api.features/src/com/jetbrains/ls/api/features/semanticTokens/LSSemanticTokenModifier.kt:1
- Orphaned file kotlin-vscode/testSources/tokenization/sample.kt:1
- Duplicated predicate vscode-extension-core/src/extension.ts:171
- Duplicated predicate kotlin-vscode/unpack-server.mjs:57
- Duplicated predicate vscode-extension-core/src/keyHandlerUtils.ts:408
- Duplicated predicate vscode-extension-core/src/initializationSettings.ts:159
- Off-boarding risk: anonymized user #1
- Off-boarding risk: anonymized user #2
- Off-boarding risk: anonymized user #3
- Further sole-owners (lower concentration)
- Orphaned files with no living knowledge
- No ADRs
- No architecture diagram/doc
- Logging is not universal
- No SAST
- No dependency-update automation kotlin-vscode/package.json:41
- Not all async functions that make a request accept an AbortSignal
- Silent fallback default in catch vscode-extension-core/src/proxySettings.ts:16
Minor — 2 finding(s)
- Dependency hygiene PARTLY measured — npm pinning read, dependency currency not (no committed lockfile, so no resolved version to grade)
- doc comments repeat the names vscode-extension-core/src/serverObservers.ts:47
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-4f8d03ce380e40359fef89790487f688/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-4f8d03ce380e40359fef89790487f688/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 . | 0 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . | 0 | — |
| D30 · Dependency Vulnerabilities | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . | 0 | artifacts/raw/trivy-fs.json |
| 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 124 file(s) — `api.features/src/com/jetbrains/ls/api/features/LSConfiguration.kt`, `api.features/src/com/jetbrains/ls/api/features/LSConfigurationEntry.kt`, `api.features/src/com/jetbrains/ls/api/features/callHierarchy/LSCallHierarchy.kt`, `api.features/src/com/jetbrains/ls/api/features/callHierarchy/LSCallHierarchyProvider.kt`, `api.features/src/com/jetbrains/ls/api/features/codeActions/LSCodeActionProvider.kt`, … (+119 more) — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real. | 0 | — |
| D36 · Supply-chain Provenance & Signing | provenance | — | provenance: not applicable — No CI/build pipeline found (.github/.forgejo/.gitea workflows, .circleci, .buildkite, .woodpecker, .teamcity, .gitlab-ci.yml, .travis.yml, bitbucket-pipelines.yml, .drone.yml, .cirrus.yml, .woodpecker.yml, appveyor.yml, azure-pipelines*.yml, .pipelines/, .vsts-ci/, .azuredevops/, Jenkinsfile); there is no build to attest provenance for. | 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 . | 0 | — |
| D43 · Malicious Dependencies | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . | 0 | artifacts/raw/trivy-fs.json |