Kotlin/kotlin-lsp

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 55 out of 100 and is rated Adequate, and none of its 11 critical findings concern security.

Production Readiness, at 45, 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. Recording design decisions comes next, worth about 2 points. Raising Production Readiness to 70 would lift the score to about 63.

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 35,989 lines, about €52,000 to rebuild.

Code Health 77 Strong Architecture 62 Adequate, capped by Slice cohesion Maturity 59 Adequate, capped by Architecture documentation Production Readiness 45 Weak, capped by CI/CD gates and Security & performance tooling Security and Compliance 100 ★ Exemplary Performance 61 Adequate

A lens is capped at Adequate while one of its dimensions scores below 4 out of 10, however well the rest of the lens does. That way a serious problem in one place always shows in the lens's rating.

How the score is built: what each lens counts for The lenses don't count equally. The weakest lens counts most, the next weakest a little less, and so on, so a weak area pulls the score down instead of being averaged away. In the bar below, each part's width shows how much that lens counts and its colour shows its rating. Improving the widest part moves the score most, and as that lens improves, it counts for less, because another lens becomes the weakest.

Production Readiness 45 · counts for 46%Maturity 59 · counts for 25%Performance 61 · counts for 14%Architecture 62 · counts for 8%Code Health 77 · counts for 4%Security and Compliance 100 · counts for 2%

If Production Readiness rose from 45 to 70, the lowest score rated Strong, the score would rise from 55 to about 63.

Code composition: what the lines of code are

Product code 75%Tests 25%

New since the last survey: 32 findings

These 32 critical or serious findings weren't in the previous survey, on 12 October 2026.

Cognitive Complexity · KotlinMultiplatformMapper.map (cognitive 21) workspace-import/src/com/jetbrains/ls/imports/gradle/kmp/KotlinMultiplatformMapper.kt
Cognitive Complexity · RunStepsKt.run (cognitive 18) buildtool.api/src/com/jetbrains/ls/buildtool/api/run/RunSteps.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
Churn × Complexity Hotspots · 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
Cyclomatic Complexity · Complex function computeStatusTooltipContent (cyclomatic 14, cognitive 13) vscode-extension-core/src/statusBarModel.ts
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/gradle-plugin/src/com/jetbrains/ls/imports/gradle/model/builder/KotlinMultiplatformModelBuilder.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
Exception handling · Swallowed exception (empty catch) vscode-extension-core/src/lspClient.ts
Exception handling · Swallowed exception (empty catch) vscode-extension-core/src/serverBundleDownload.ts
Exception handling · Swallowed exception (empty catch) kotlin-vscode/launch-vscode.mjs
Slice cohesion · Cross-slice coupling: codeActions → commands api.features/src/com/jetbrains/ls/api/features/codeActions/LSSimpleCodeActionProvider.kt
Slice cohesion · Cross-slice coupling: resolve → configuration api.features/src/com/jetbrains/ls/api/features/resolve/ResolveDataWithConfigurationEntryId.kt
Slice cohesion · Cross-slice coupling: impl → configuration features-impl/common/src/com/jetbrains/ls/api/features/impl/common/callHierarchy/LSCallHierarchyProviderBase.kt
Slice cohesion · Cross-slice coupling: impl → commands features-impl/common/src/com/jetbrains/ls/api/features/impl/common/decompiler/LSDecompileCommandDescriptorProvider.kt
Slice cohesion · Cross-slice coupling: impl → commands features-impl/common/src/com/jetbrains/ls/api/features/impl/common/fileTemplates/LSInterpolateFileTemplateCommandDescriptorProvider.kt
Slice cohesion · Cross-slice coupling: impl → configuration features-impl/common/src/com/jetbrains/ls/api/features/impl/common/inlayHints/LSInlayHintsProviderBase.kt
Slice cohesion · Cross-slice coupling: impl → configuration features-impl/common/src/com/jetbrains/ls/api/features/impl/common/inlayHints/LSInlayHintsProviderBase.kt
Slice cohesion · Cross-slice coupling: impl → commands features-impl/common/src/com/jetbrains/ls/api/features/impl/common/modcommands/LSApplyFixCommandDescriptorProvider.kt
Slice cohesion · Cross-slice coupling: impl → configuration features-impl/kotlin/src/com/jetbrains/ls/api/features/impl/kotlin/callHierarchy/LSKotlinCallHierarchyProvider.kt
Slice cohesion · Cross-slice coupling: impl → configuration features-impl/kotlin/src/com/jetbrains/ls/api/features/impl/kotlin/completion/LSKotlinCompletionProvider.kt
Slice cohesion · Cross-slice coupling: impl → configuration features-impl/kotlin/src/com/jetbrains/ls/api/features/impl/kotlin/typeHierarchy/LSKotlinTypeHierarchyProvider.kt
Async & latency hygiene · Sync-over-async blocking vscode-extension-core/src/serverBundleDownload.ts
Async & latency hygiene · Sync-over-async blocking vscode-extension-core/src/serverBundleDownload.ts
Async & latency hygiene · Sync-over-async blocking vscode-extension-core/src/serverBundleDownload.ts
Async & latency hygiene · Sync-over-async blocking vscode-extension-core/src/serverBundleDownload.ts
Async & latency hygiene · Sync-over-async blocking vscode-extension-core/src/serverBundleDownload.ts
Async & latency hygiene · Sync-over-async blocking vscode-extension-core/src/serverBundleDownload.ts
Async & latency hygiene · Sync-over-async blocking vscode-extension-core/src/serverBundleDownload.ts
Async & latency hygiene · Sync-over-async blocking vscode-extension-core/src/serverBundleDownload.ts

Watchdog compares every finding with the previous survey's. A finding that has only moved to another line in the same file counts as the same finding, so only new findings appear here. Advisory notes from the AI model are left out, because the model words them afresh in every survey.

Fixed since the last survey: 9 findings

These 9 critical or serious findings were in the previous survey, on 12 October 2026, and are gone from this one.

Code Duplication · Duplicated block (6 lines × 2) workspace-import/src/com/jetbrains/ls/imports/gradle/GradleTool.kt
Churn × Complexity Hotspots · Hotspot: vscode-language-kotlin/src/kotlin/keyHandler.ts vscode-language-kotlin/src/kotlin/keyHandler.ts
Change Coupling · Change coupling: LSCommonInspectionFixesCodeActionProvider.kt ↔ LSKotlinCompilerDiagnosticsFixesCodeActionProvider.kt features-impl/common/src/com/jetbrains/ls/api/features/impl/common/diagnostics/LSCommonInspectionFixesCodeActionProvider.kt
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
Large Files · vscode-extension-core/src/lspClient.ts: 1257 lines of code vscode-extension-core/src/lspClient.ts
Async & latency hygiene · Sync-over-async blocking vscode-extension-core/src/serverBundleDownload.ts
Async & latency hygiene · Sync-over-async blocking vscode-extension-core/src/serverBundleDownload.ts
Async & latency hygiene · Sync-over-async blocking vscode-extension-core/src/serverBundleDownload.ts

Rebuild cost: about €52,000 · Estimate

Cost to rebuild	€17,000 to €87,000, for 289 to 917 hours of work, about 0.4 person-years for one engineer
Difficulty of the problem	Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write.
Quality factor	×0.8 at a score of 55. 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: 35,989 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.

How the estimate is made: Watchdog prices the hours a team would need to write this code again, at €60 to €95 an hour. Declarations and boilerplate are priced at a fast rate and logic at a slower one, and the logic is then multiplied by the difficulty of the problem and by the quality factor. The estimate can be about 30% off either way, and it moves most with the hourly rate and the difficulty. For this code, every line is priced as straight logic, which keeps the estimate on the low side.

Top priorities

The three actions that raise the score most for the work they take. The full ranked list is in the Roadmap.

Add a CI workflow that builds and runs the test suite on every push/PR.

Raises the score by about 7 points · Medium effort · CI/CD gates

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.

Raises the score by about 2 points · Medium effort · Architecture documentation

Add eslint as package.json scripts and run them in CI.

Raises the score by about 2 points · Medium effort · Tooling

Diagnosis: what the measurements show together

Each conclusion below combines several dimensions into one point that no single dimension shows, and lists the measurements it rests on.

Where the investment is most exposed · Value at risk

This code would cost about €52,000 to build again, about 0.4 person-years of work. Its weakest lens is Production Readiness, at 45 (Weak). Production Readiness is about whether the product is ready to run in production and to change without breaking. Because the weakest lens counts most in the score, work on Production Readiness also moves the score most.

Based on: the rebuild estimate · the Production Readiness grade · how much each lens counts

What to do: Start with the Production Readiness actions in Top priorities.

If you do one thing first · First action

Add a CI workflow that builds and runs the test suite on every push/PR. Of all the actions in this report, it raises the score most for the work it takes: about 7 points for medium effort. The next survey will show the change in the score.

Based on: the ranked actions in Top priorities, by score gain and effort

Architecture: which parts of the code depend on which

The code is divided into modules, groups of code that each handle one part of the product, and a module depends on another when it uses code from it. The table lists the modules both down the side and across the top, in an order where each module should only use modules listed above it. A number in a cell means the module on that row uses the module in that column, and it counts the pairs of building blocks (types) that connect them. The one thing to look for is a mark above the diagonal line. It means two or more modules use each other in a loop (a dependency cycle), so none of them can be changed, tested or released on its own.

274 modules, with 386 dependencies between them. 11 loops run through 27 of the modules, marked above the diagonal.

The table shows the 40 modules with the most connections; 234 more are left out to keep it readable.

Which modules use which. The module on each row uses the module in each column, and the number counts the pairs of types that connect them. A cell above the diagonal is part of a loop.
uses →	1 com.jetbrains.ls.api.features.configuration.LSUniqueConfigurationEntry	3 com.jetbrains.ls.api.features.impl.common.utils.LSRefactoringMemberProviderBase	4 com.jetbrains.ls.api.features.utils	5 com.jetbrains.ls.imports.gradle.model	8 vscode-testing.src.testTree	9 com.jetbrains.ls.api.features.commands	10 com.jetbrains.ls.api.features.impl.common.callHierarchy.LSCallHierarchyProviderBase	11 com.jetbrains.ls.api.features.impl.common.inlayHints.LSInlayHintsProviderBase	12 com.jetbrains.ls.api.features.language	13 com.jetbrains.ls.buildtool.api.run	14 com.jetbrains.ls.kotlinLsp.requests.core.ModCommandData	15 vscode-testing.src.testRunReport	16 com.jetbrains.ls.api.features	17 com.jetbrains.ls.api.features.impl.common.codeLens	20 com.jetbrains.ls.buildtool.api	21 com.jetbrains.ls.kotlinLsp.requests.core	22 vscode-testing.src.testLanguage	23 com.jetbrains.ls.api.features.codeActions	24 com.jetbrains.ls.api.features.configuration	25 com.jetbrains.ls.api.features.impl.common.modcommands	27 com.jetbrains.ls.imports.json	29 com.jetbrains.ls.api.features.completion	30 com.jetbrains.ls.api.features.impl.common.diagnostics	33 com.jetbrains.ls.imports.gradle.kmp	35 com.jetbrains.ls.api.features.impl.common.completion.LSCompletionProviderHelper	38 com.jetbrains.ls.imports.gradle	39 com.jetbrains.ls.api.features.impl.common.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.imports.gradle.model
6 com.jetbrains.ls.imports.gradle.utils
7 vscode-extension-core.src
8 vscode-testing.src.testTree
9 com.jetbrains.ls.api.features.commands													1
10 com.jetbrains.ls.api.features.impl.common.callHierarchy.LSCallHierarchyProviderBase	1		1
11 com.jetbrains.ls.api.features.impl.common.inlayHints.LSInlayHintsProviderBase	1
12 com.jetbrains.ls.api.features.language													1
13 com.jetbrains.ls.buildtool.api.run															1
14 com.jetbrains.ls.kotlinLsp.requests.core.ModCommandData																16
15 vscode-testing.src.testRunReport					1												1
16 com.jetbrains.ls.api.features	1					1			4
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.api.features.impl.kotlin.callHierarchy	1		1				2		2
20 com.jetbrains.ls.buildtool.api										2
21 com.jetbrains.ls.kotlinLsp.requests.core											2
22 vscode-testing.src.testLanguage												1
23 com.jetbrains.ls.api.features.codeActions						2							1
24 com.jetbrains.ls.api.features.configuration	1												1
25 com.jetbrains.ls.api.features.impl.common.modcommands						2					1					2
26 com.jetbrains.ls.api.features.semanticTokens													2
27 com.jetbrains.ls.imports.json															7
28 vscode-testing.src					2												4
29 com.jetbrains.ls.api.features.completion													1						1
30 com.jetbrains.ls.api.features.impl.common.diagnostics									7							1		3		2
31 com.jetbrains.ls.api.features.impl.common.utils		3				2												1
32 com.jetbrains.ls.api.features.impl.kotlin.inline						2			1									1
33 com.jetbrains.ls.imports.gradle.kmp				4																	5					1
34 com.jetbrains.ls.imports.maven										5					9						4
35 com.jetbrains.ls.api.features.impl.common.completion.LSCompletionProviderHelper									1													1					1
36 com.jetbrains.ls.api.features.impl.javaBase									6				1	1								2
37 com.jetbrains.ls.api.features.impl.kotlin.diagnostics.compiler			1			2			2									1		1			3
38 com.jetbrains.ls.imports.gradle				4						5					9						10			2
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

Uses a module listed above itPart of a loopThe module itself

At a glance — Code Health · 77% · Strong ·

The Good

D1 · Kotlin Cyclomatic Complexity 7.3 D3 · Kotlin God Classes 8.9 D4 · Kotlin Code Duplication 9.9 D17 · Kotlin Explicit Debt 9.9 R1 · React / TS Type Safety 9.6 R10 · React / TS Code Duplication 9.6 R2 · React / TS Cyclomatic Complexity 8.9 R3 · React / TS Large Files 7.9 R7 · React / TS Dead Code 10.0 X1 · Repo Async correctness 10.0 X12 · Repo Unreachable branch 10.0 X13 · Repo Undrained process stream 10.0 X16 · Repo Unfloored truncation loop 10.0 X19 · Repo Unrestored process-global state 10.0 X2 · Repo Cancellation propagation 8.0 X20 · Repo Mistyped argument guard 10.0 X21 · Repo Side-effecting pattern guard 10.0 X22 · Repo Contradicted release guard 10.0 X23 · Repo Unguarded diagnostic materialisation 10.0 X25 · Repo Inert configuration knob 10.0 X26 · Repo Unsynchronised callback handoff 10.0 X27 · Repo Collection changed while being enumerated 10.0 X28 · Repo Index access outside its own emptiness guard 10.0 X29 · Repo Per-element action decided by a fixed element 10.0 X30 · Repo Support guard that admits what it rejects 10.0 X5 · Repo Nullable reference types 9.9

The Bad

D2 · Kotlin Cognitive Complexity 6.6 X18 · Repo Disposal-pattern correctness 5.3 X3 · Repo Exception handling 5.3

At a glance — Architecture · 62% · Adequate · gated by AX7 ·

The Good

D5 · Kotlin Coupling 10.0 D6 · Kotlin Cohesion (LCOM4) 10.0 D35 · Kotlin Change Coupling 9.0 AX3 · Repo Project dependency cycles 10.0 AX5 · Repo Architecture & structure 10.0 AX6 · Repo Interface segregation 10.0 R9 · React / TS Circular Imports 7.5

The Bad

AX10 · Repo Code composition 6.3

The Ugly

AX7 · Repo Slice cohesion 1.8

At a glance — Maturity · 59% · Adequate · gated by M2 ·

The Good

D15 · Kotlin Churn × Complexity Hotspots 9.7 D16 · Kotlin Bus Factor 8.4 D19 · Kotlin Documentation Quality 10.0 D34 · Kotlin Knowledge Freshness 9.6 M1 · Repo Documentation (README) 7.3 M3 · Repo Folder & project structure 10.0 M4 · Repo Documentation accuracy 10.0

The Ugly

M2 · Repo Architecture documentation 0.0

At a glance — Readiness · 45% · Weak · gated by P1, P3 ·

The Good

D9 · Kotlin Test Distribution 10.0 D10 · Kotlin Test Quality 10.0 D13 · Kotlin Secret Scanning 10.0 D14 · Kotlin License Compliance 10.0 P10 · Repo Library API & versioning 10.0 P6 · Repo Release Hygiene 10.0 R4 · React / TS Test Coverage 9.3 R8 · React / TS Dependency Hygiene 8.0

The Bad

R6 · React / TS Tooling 6.7

The Ugly

P1 · Repo CI/CD gates 0.0 P3 · Repo Security & performance tooling 0.0

At a glance — Security · 100% · Exemplary ·

The Good

D28 · Kotlin Secrets (history) 10.0 D29 · Kotlin Static Analysis (SAST) 10.0 D30 · Kotlin Dependency Vulnerabilities 10.0 D43 · Kotlin Malicious Dependencies 10.0 D44 · Kotlin Platform End-of-Life 10.0 X14 · Repo Bypassable address classification 10.0 X15 · Repo Unvalidated length from an untrusted reader 10.0 X17 · Repo Uncapped recursion over a caller-supplied document 10.0 X24 · Repo Document value interpolated into markup unescaped 10.0

At a glance — Performance · 61% · Adequate ·

The Bad

PF2 · Repo Allocation hygiene 6.2 PF3 · Repo Async & latency hygiene 6.0

Roadmap

First, establish a CI workflow that builds and tests on every push to ensure immediate feedback. Next, document key design decisions in a dedicated folder to preserve architectural context and rationale. Then, integrate linting into your package scripts and CI pipeline to maintain code quality standards. Finally, ensure slice independence by sharing contracts rather than direct references, and replace synchronous APIs with their asynchronous counterparts to improve performance.

Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.

Do this	Helps	Effort	Dimension
Add a CI workflow that builds and runs the test suite on every push/PR.	+7.3 pts	Medium	CI/CD gates
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.	+2.3 pts	Medium	Architecture documentation
Add eslint as package.json scripts and run them in CI.	+1.9 pts	Medium	Tooling
Keep slices independent: share cross-slice needs via an explicit contract/shared-kernel, not direct references between slices.	+1.4 pts	Medium	Slice cohesion
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.	+1.4 pts	Medium	Async & latency hygiene
Resolve the 3 Off-boarding risk finding(s) in Bus Factor.	+0.7 pts	Low	Bus Factor
Raise allocation-aware density on the hot paths — currently 9 use(s) across 27,878 production line(s) (~0.3/1k). More of the idioms below on the allocation-heavy paths climbs this toward 10.	+1.3 pts	Medium	Allocation hygiene
Resolve the 9 Boundary-crossing change coupling finding(s) in Change Coupling — start with LSSimpleCodeActionProvider.kt (9).	+0.5 pts	Low	Change Coupling

File quality

Per-file score 0–10 — a quality signature. Of 39 files carrying findings, judged against the Production bar: 0% slop · 46% mixed · 54% near-clean.

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
workspace-import/src/com/jetbrains/ls/imports/json/conversion.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 ↔ LSKotlinIntentionCodeActionProvider.kt
features-impl/common/src/com/jetbrains/ls/api/features/impl/common/diagnostics/LSCommonIntentionFixesCodeActionProvider.kt	6.7	Mixed	Explicit Debt: TodoComment
vscode-language-kotlin/src/kotlin/keyHandler.ts	7.1	Mixed	Cyclomatic Complexity: keyHandler.handleEnter (cyclomatic 19)
features-impl/common/src/com/jetbrains/ls/api/features/impl/common/completion/ModCompletionCommandConverter.kt	7.2	Mixed	Cyclomatic Complexity: ModCompletionCommandConverter.split (cyclomatic 27)
vscode-extension-core/src/serverBundleDownload.ts	7.2	Mixed	Cyclomatic Complexity: serverBundleDownload.downloadFile (cyclomatic 24)
workspace-import/src/com/jetbrains/ls/imports/jps/JpsBuildTool.kt	7.2	Mixed	Cyclomatic Complexity: JpsBuildTool.importJpsModel (cyclomatic 19)
api.features/src/com/jetbrains/ls/api/features/commands/document/LSDocumentCommandComandExecutor.kt	7.3	Mixed	Explicit Debt: TodoComment
workspace-import/maven-plugin/src/com/jetbrains/ls/imports/maven/util.kt	7.4	Mixed	Cyclomatic Complexity: UtilKt.doGetCompilerProp (cyclomatic 16)
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)
workspace-import/src/com/jetbrains/ls/imports/json/dependencyFlattening.kt	7.8	Mixed	Cyclomatic Complexity: DependencyFlatteningKt.flattenExportedDependencies (cyclomatic 18)
workspace-import/maven-plugin/src/com/jetbrains/ls/imports/maven/converter.kt	7.8	Mixed	Cognitive Complexity: ConverterKt.mapModuleNames (cognitive 29)
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/LSCommonInspectionDiagnosticProvider.kt	7.8	Mixed	Change Coupling: Change coupling: LSCommonInspectionDiagnosticProvider.kt ↔ LSKotlinCompilerDiagnosticsProvider.kt
workspace-import/test/test/com/jetbrains/ls/imports/GradleProjectImportTest.kt	8.2	Near-clean	Explicit Debt: TodoComment
features-impl/kotlin/src/com/jetbrains/ls/api/features/impl/kotlin/hover/LSKotlinMarkdownDocProvider.kt	8.2	Near-clean	Explicit Debt: TodoComment

How the grades work

Every finding carries one of four grades. Three say how serious it is. The fourth says this survey could not settle it — and it is a grade, not a gap.

Critical — 11

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.

Serious — 186

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.

Minor — 23

Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.

Could not be resolved — 16

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

Watchdog 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. 68 of 68 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); none rely on LLM judgement. Overall confidence is 0.8 — the weighted average across measured dimensions; it falls as more of the score leans on LLM-assisted judgement and rises when it's fully tool-backed.

Every figure here is one of three kinds, and we label which: ✓ Measured — a deterministic fact (LoC, complexity, coverage); ~ Modeled — an estimate from a stated model (cost, effort, value-at-risk), always a range with its assumptions, never a precise fact; ◐ Advisory — an LLM prose judgement. We never present a modelled estimate as if it were measured. Perfect or absent scores carry their provenance too (ADR-0011): ✓ Tool-verified means the property itself was measured across the surface; ○ Nothing flagged means the probes came back clean — a claim bounded by what a repository can show; ⊘ Not evidenced means a working control (a tested restore, an automated rollback) showed no positive evidence — absence of evidence is not evidence of a control, so it's excluded from the score rather than awarded a spurious 10; ◐ Sampled · advisory marks an LLM verdict over a bounded sample — advisory, never a deterministic measurement.

What we checked — 68 dimensions across the health lenses

D1D2D3D4D5D6D9D10D13D14D15D16D17D19D28D29D30D34D35D43D44AX10AX3AX5AX6AX7M1M2M3M4P1P10P3P6PF2PF3R1R10R2R3R4R6R7R8R9X1X12X13X14X15X16X17X18X19X2X20X21X22X23X24X25X26X27X28X29X3X30X5

Each chip is a dimension scored from real signals across architecture, testing, dependencies, security & compliance, documentation, git-history and code quality — in one coherent pass. A surface report typically covers a handful.

How to trust any code-health report — three questions

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, 208 of 220 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line. (Every path in this report is repo-relative by construction: paths are normalized at the producer and the report is rejected if any rooted path leaks through.)
Is there a tool behind the number? Every score below names the method that produced it — Roslyn, git, a scanner, or (for a handful of documentation/naming dimensions) an LLM labelled sampled · advisory — 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.

This report answers yes to all three. That's the bar to hold any assessment to.

Tools & methods

The actual versions used this run (captured at analysis time) — re-run on the same commit for the identical score.

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
Watchdog 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
LLM (sampled · advisory)	Documentation quality, ADR conformance, naming — sampled over a bounded sample; advisory, never a deterministic measurement	—	◐ LLM · sampled · advisory

Every finding is locatable in findings.md. Run 01a17a1c-a4e9-7337-b50e-0c5082515f0e.

The exact command behind every deep-scan dimension — tool, version, invocation and retained raw output — is in Appendix B — Reproduction & audit trail.

Run transparency — what happened this run

What ran differently this time — a tool absent, degraded, or that fell back to an estimate. Named openly, not folded silently into the scores. A degraded run also records its exact cause in diagnostics.md.

D8 Code Coverage — not measured this run — Watchdog 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. In the meantime, commit (or publish into the working tree) the lcov/Cobertura report your CI produces and the real number is read on the next scan. You can widen what we reach: optional: commit the lcov/Cobertura report your CI produces, and the real number is read on the next scan.
D10 Test Quality — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. The 578 test(s) behind this row are the ones the JavaScript/TypeScript census could read, and this repository also carries at least 107 test source file(s) (.kt, .java) that it cannot: it reads JavaScript/TypeScript test declarations off disk, so a JUnit/pytest-style suite is invisible to it. Skipped tests, zero-assertion tests and the other quality signals on this row are UNMEASURED in that suite — their absence from the counts above is a gap in this analyzer's language coverage, not a finding that those tests are sound.
D11 Test Reliability — not measured this run — Watchdog 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 — Watchdog 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 — Watchdog 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 — Watchdog 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 — Watchdog 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 — Watchdog 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 — 70 Maven/Gradle manifest(s) were read, stating a version for 67 dependency(ies) and leaving 1 to a parent or an imported BOM, but no build resolved the dependency graph, so the outdated signal was not established. NOT a finding that these dependencies are current or healthy.
D14 License Compliance — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This repository declares package.json, but the licence verdict published here was taken over its JVM dependencies. Nothing was read about its npm dependencies' licensing in either direction, and a clean score on this card must not be read as covering them.
D19 Documentation Quality — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
D21 Naming Consistency — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D21's deterministic naming rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. Until then its declarations carry no naming verdict this run — this says nothing about whether its names are consistent.
D22 Internal API Consistency — not measured this run — Watchdog 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 — not measured this run — Watchdog 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.
D26 Project Cohesion — not measured this run — Watchdog 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 — not measured this run — Watchdog 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. Navigability is taken over call sites whose callee resolved. For C# that population includes calls into referenced assemblies; for this language only calls declared inside the repository count, so the abstention threshold reads the repository's use of its standard library as a resolution failure. That is a limit of this analyzer, not a build problem in this repository.
D32 Data Compliance (PII/GDPR) — not measured this run — Watchdog 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`, … (+113 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.
AX1 Captive dependencies — not measured this run — Watchdog 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 Microsoft.Extensions.DependencyInjection registrations in C# and Spring beans in Java/Kotlin only, and this repository's container is an unrecognised JSR-330 (javax.inject / jakarta.inject) container, whose lifetimes are not modelled 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.
AXB1 Runtime evidence locked — no reproducible boot — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Subject: a native UI project (workspace-import/test/testData/gradle/GradleKotlinKmpProject/app/iosApp/iosApp.xcodeproj/project.pbxproj). The Runtime Evidence tier boots an app only via docker-compose, an Aspire AppHost, a Dockerfile, an npm dev script, a web service's own toolchain entry point (cargo, go, dotnet, Python, Spring Boot), or an Android app's own Gradle wrapper (run on an emulator); an Apple or Flutter app needs a host it lacks. None applied, so no live runtime a11y/egress/header evidence was collected. You can widen what we reach: add a docker-compose.yml (or an Aspire AppHost) that brings the app up with its dependencies. Watchdog then boots it in an isolated sandbox and gathers real runtime evidence — you change nothing in your pipeline (no CI step, no SDK).
C2 Access Controls — not measured this run — Watchdog 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 — Watchdog 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 Java, 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 — Watchdog 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 — Watchdog measured this, but not all of it. What it 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). 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.
S1 Web-Security Posture — not measured this run — Watchdog 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.

Repo exclusion declarations (.gitattributes linguist-generated/vendored, .editorconfig generated_code): none declared — every source file was scored.

Limitations & what we did not check

Watchdog assesses the repository exactly as committed, and only the repository. By design it does 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

For each dimension that was measured, what a static, repo-only scan structurally cannot see — the honest edge of the measurement, not a failure of it.

D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
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").
D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
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.
D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
M4 Documentation accuracy: Onboarding quality is an LLM read of the docs/setup present — it cannot run the onboarding or measure how long a real new joiner takes; the verdict is sampled and advisory.
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 Complexity7.3 / 10Strong✓ Tool-verified

What it measures: How tangled the control flow is — methods with many branches are hard to test and change.

Method: Cyclomatic complexity per method (1 + decision points), computed exhaustively across production source; test projects separated by convention. Deterministic.

Maturity: Documented → Verified → Prevented · effective 7.3 / 10 · rule-coverage 100% · ceiling Prevented

19 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was LSKotlinSemanticTokensProvider.getRangeWithToken at 44. A further 1 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 ModCommandDataKt.writtenFileUrls at 16 — they are counted neither in the figure above nor in this dimension's score.

KindsKt.getKind (cyclomatic 20) · ×2features-impl/kotlin/psi/src/com/jetbrains/ls/api/features/impl/kotlin/psi/kinds.kt:21

LSKotlinSemanticTokensProvider.getRangeWithToken (cyclomatic 44)features-impl/kotlin/src/com/jetbrains/ls/api/features/impl/kotlin/semanticTokens/LSKotlinSemanticTokensProvider.kt:138

ModCommandData.from (cyclomatic 35)features-impl/common/src/com/jetbrains/ls/api/features/impl/common/modcommands/ModCommandData.kt:303

ModCommandDataKt.executeCommand (cyclomatic 34)features-impl/common/src/com/jetbrains/ls/api/features/impl/common/modcommands/ModCommandData.kt:486

ModCompletionCommandConverter.split (cyclomatic 27)features-impl/common/src/com/jetbrains/ls/api/features/impl/common/completion/ModCompletionCommandConverter.kt:215

+ 13 more group(s) — more in Appendix A; the complete list is findings.md.

What to do

Bring the 19 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with LSKotlinSemanticTokensProvider.getRangeWithToken (cyclomatic 44), ModCommandData.from (cyclomatic 35), ModCommandDataKt.executeCommand (cyclomatic 34). — 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 19 together lifts Cyclomatic Complexity from 7.4 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
Stand up a CI pipeline, then gate Cyclomatic Complexity in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

Detailed fixes: d1_recommendation.md · top locations in Appendix A, every location in findings.md.

Do you agree with this assessment?

D2 · Cognitive Complexity6.6 / 10Adequate✓ Tool-verified

What it measures: How hard the code is for a person to follow, beyond raw branching.

Method: Cognitive complexity per method (Sonar-style nesting-penalized score), computed exhaustively over production code, excluding test projects. Deterministic.

Maturity: Documented → Verified → Prevented · effective 6.6 / 10 · rule-coverage 100% · ceiling Prevented

25 method(s) exceeded the cognitive complexity threshold of 15; the worst was ModCompletionCommandConverter.split at 57.

ModCompletionCommandConverter.split (cognitive 57)features-impl/common/src/com/jetbrains/ls/api/features/impl/common/completion/ModCompletionCommandConverter.kt:215

DependencyFlatteningKt.flattenExportedDependencies (cognitive 39)workspace-import/src/com/jetbrains/ls/imports/json/dependencyFlattening.kt:19

ModCommandDataKt.executeCommand (cognitive 38)features-impl/common/src/com/jetbrains/ls/api/features/impl/common/modcommands/ModCommandData.kt:486

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:487

+ 20 more group(s) — more in Appendix A; the complete list is findings.md.

What to do

Bring the 25 bodies over 15 down to 15 or less in Cognitive Complexity — start with ModCompletionCommandConverter.split (cognitive 57), DependencyFlatteningKt.flattenExportedDependencies (cognitive 39), ModCommandDataKt.executeCommand (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 25 together lifts Cognitive Complexity from 6.6 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
Stand up a CI pipeline, then gate Cognitive Complexity in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

Detailed fixes: d2_recommendation.md · top locations in Appendix A, every location in findings.md.

Do you agree with this assessment?

D3 · God Classes8.9 / 10Strong✓ Tool-verified

What it measures: Over-large classes that try to do too much ("god classes").

Method: God-class detection by line and method-count thresholds per logical type (partial classes unified), filtered for generated code and registration/contract false positives. Deterministic.

Maturity: Documented → Verified → Prevented · effective 8.9 / 10 · rule-coverage 100% · ceiling Prevented

11 over-large unit(s) detected — types, modules or files that carry too much.

FileTooLong: kotlin/keyHandler.ts · ×8vscode-language-kotlin/src/kotlin/keyHandler.ts

MethodTooLong: JpsBuildTool.importJpsModel · ×3workspace-import/src/com/jetbrains/ls/imports/jps/JpsBuildTool.kt:265

What to do

Resolve the 8 FileTooLong finding(s) in God Classes — start with keyHandler.ts, lspClient.ts, keyHandlerUtils.ts. — One of this dimension's main actionable groups (8 warning-level).
Resolve the 3 MethodTooLong finding(s) in God Classes — start with JpsBuildTool.kt, ModCommandData.kt, conversion.kt. — One of this dimension's main actionable groups (3 warning-level).
Stand up a CI pipeline, then gate God Classes in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

Detailed fixes: d3_recommendation.md · top locations in Appendix A, every location in findings.md.

Do you agree with this assessment?

D4 · Code Duplication9.9 / 10Stronggated by 4 serious findings✓ Tool-verified

What it measures: Copy-pasted code that should be shared instead.

Method: Code duplication via token-stream sliding windows with type-aware normalization (locals masked, type names preserved), density-scored per KLoC of production code. Deterministic.

Maturity: Documented → Verified → Prevented · effective 9.9 / 10 · rule-coverage 100% · ceiling Verified

4 duplicated block group(s) detected. Measured on part of this repository only: .ts (30% 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.

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 (8–14 lines × 2)workspace-import/src/com/jetbrains/ls/imports/json/conversion.kt:354

Duplicated block (5 lines × 2)workspace-import/maven-plugin/src/com/jetbrains/ls/imports/maven/util.kt:190

What to do

Resolve the 1 Duplicated block (32 lines × 2) finding(s) in Code Duplication — start with kinds.kt. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 Duplicated block (12–16 lines × 2) finding(s) in Code Duplication — start with RunSteps.kt. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 Duplicated block (8–14 lines × 2) finding(s) in Code Duplication — start with conversion.kt. — One of this dimension's main actionable groups (1 warning-level).
Stand up a CI pipeline, then gate Code Duplication in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. Hardens enforcement from Documented toward Verified — provenance only; does not change the score.

Detailed fixes: d4_recommendation.md · top locations in Appendix A, every location in findings.md.

Do you agree with this assessment?

D5 · Coupling10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether volatile projects sit underneath others that depend on them (so their churn ripples upward), and whether project dependencies form cycles. A widely-depended-on but stable shared/kernel project is healthy, not penalised.

Method: Dependency cycles via elementary-DFS over real .csproj references, plus Martin instability (afferent/efferent) per project. Exhaustive over the reference graph, deterministic.

Coverage: Exhaustive · type-level: afferent/efferent coupling + cycles computed over every production type — the population is all types, not a name convention.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Prevented

6 production modules (Maven+npm), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; 0 module(s) off the main sequence, with abstractness counted on 5 of the 6 (the rest declare no modelled class or interface, export only macros, declare types in source no model reads, or have no source directory of their own).

✓ On the Gold path — maintain.

Detailed fixes: d5_recommendation.md.

Do you agree with this assessment?

D6 · Cohesion (LCOM4)10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether a class's methods are focused on a single responsibility.

Method: LCOM4 cohesion per production class with at least two methods: connected components of methods sharing state or calls, computed syntactically. Deterministic, not a proxy.

Coverage: Exhaustive · type-level: LCOM4 cohesion computed over every production class — the population is all types, not a name convention.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Verified

0 of 46 classes have LCOM4 above 3.

✓ On the Gold path — maintain.

Detailed fixes: d6_recommendation.md.

Do you agree with this assessment?

D9 · Test Distribution10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether the test suite has a healthy mix of unit / integration / end-to-end tests.

Method: Test projects classified (Unit/Integration/BDD/E2E) from compiled metadata; test methods counted exhaustively across projects with placement-agnostic disk fallback. Deterministic.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

579 test methods: 579 unit, 0 integration, 0 BDD, 0 e2e. The JavaScript/TypeScript suite contributes 578 `it`/`test` case(s) across 34 test file(s) declaring at least one beside 1 .NET test method(s); its tier split is read from package names and paths only.

✓ On the Gold path — maintain.

Detailed fixes: d9_recommendation.md.

Do you agree with this assessment?

D10 · Test Quality10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether the tests truly assert behaviour rather than just running the code.

Method: Per-test assertions, skips, and mock references analyzed via Roslyn; structured skip-reason tags (BUG:/ENV:) separate documented deferrals from debt. Deterministic.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Prevented

0 skipped, 0 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 578 tests. Measured on the JavaScript/TypeScript suite only — at least 107 test source file(s) (.kt, .java) went unread, so its test quality is unmeasured and is not in these counts.

✓ On the Gold path — maintain.

Detailed fixes: d10_recommendation.md.

Do you agree with this assessment?

D13 · Secret Scanning10.0 / 10Exemplary○ Nothing flagged

What it measures: Whether any secrets (keys, tokens, passwords) have leaked into the code.

Method: In-process native secret scanner (entropy plus signature patterns) across all tracked files; no external tool. A clean result is a measured 10, not no-data zero. Deterministic.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Prevented

Secret scan ran and found no leaked secrets.

✓ On the Gold path — maintain.

Detailed fixes: d13_recommendation.md.

Do you agree with this assessment?

D14 · License Compliance10.0 / 10Exemplary○ Nothing flagged

What it measures: Whether the licenses of third-party packages are compatible with your policy.

Method: Third-party package licenses resolved from declared package metadata and checked against the configured policy (allow/deny/copyleft). Deterministic; clean = no incompatible license found at metadata depth.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Verified

0 of 38 declared JVM dependency artifact(s) use a banned license. Licences were resolved from the POMs Maven Central publishes, over the coordinates this repository's 70 Maven/Gradle manifest(s) declare with a version resolvable from the manifest itself — the same declaration-site closure this analysis reads for dependency currency. The JVM has no lockfile a checkout is guaranteed to carry, so this is deliberately NOT the transitive closure. 1 further coordinate(s) are declared with no version at the declaration site — inherited from a parent POM, a BOM or an unresolved Gradle version reference — and are NOT graded: this verdict covers what the checkout pins, not the full transitive graph. A further 15 coordinate(s) are not published to Maven Central — another repository (Google's Maven hosts androidx), a SNAPSHOT, or a private artifact — so their licences are not readable from here and they are outside this verdict. ★ COVERAGE OF THIS VERDICT: it grades this repository's JVM dependencies and nothing else. The repository also declares package.json, and the licences of those dependencies were NOT read by this pass — a gap in this engine's coverage, not a statement about them. So this result says the graded closure carries no banned licence; it does NOT say this repository's licensing is clear.

✓ On the Gold path — maintain.

Detailed fixes: d14_recommendation.md.

Do you agree with this assessment?

D15 · Churn × Complexity Hotspots9.7 / 10Stronggated by 6 serious findings✓ Tool-verified

What it measures: Files that change often and are also complex — the riskiest hotspots.

Method: Per production file churn times cyclomatic complexity over a rolling window, computed from git and Roslyn/JS/Razor analysis. Exhaustive, deterministic per commit date.

Maturity: Documented → Verified → Prevented · effective 9.7 / 10 · rule-coverage 100% · ceiling Documented

Top hotspots: vscode-extension-core/src/lspClient.ts (36×19=684); features-impl/common/src/com/jetbrains/ls/api/features/impl/common/modcommands/ModCommandData.kt (18×35=630); workspace-import/src/com/jetbrains/ls/imports/jps/JpsBuildTool.kt (33×19=627) Repeated repair below the complexity floor: features-impl/common/src/com/jetbrains/ls/api/features/impl/common/diagnostics/LSInspectionManager.kt (5 of 8 changes were fixes)

Hotspot: vscode-extension-core/src/lspClient.ts · ×5vscode-extension-core/src/lspClient.ts:1043

Repeated repair: features-impl/common/src/com/jetbrains/ls/api/features/impl/common/diagnostics/LSInspectionManager.ktfeatures-impl/common/src/com/jetbrains/ls/api/features/impl/common/diagnostics/LSInspectionManager.kt:55

What to do

Resolve the 5 Hotspot finding(s) in Churn × Complexity Hotspots — start with lspClient.ts, ModCommandData.kt, JpsBuildTool.kt. — One of this dimension's main actionable groups (5 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).

Detailed fixes: d15_recommendation.md · top locations in Appendix A, every location in findings.md.

Do you agree with this assessment?

D16 · Bus Factor8.4 / 10Strong✓ Tool-verified

What it measures: Whether knowledge is concentrated in too few people (the "bus factor").

Method: Living knowledge per author via time-decayed commit attribution (6-month half-life, focus weighting) across largest source files. Deterministic, avoids blame's mechanical-refactor false positives.

Maturity: Documented → Verified → Prevented · effective 8.4 / 10 · rule-coverage 100% · ceiling Documented

29 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 177 of the 383 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.

Off-boarding risk: anonymized user #1 · ×3

Further sole-owners (lower concentration)

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).

Detailed fixes: d16_recommendation.md · top locations in Appendix A, every location in findings.md.

Do you agree with this assessment?

D17 · Explicit Debt9.9 / 10Stronggated by 14 serious findings✓ Tool-verified

What it measures: Acknowledged debt left in the code — TODOs, dead code, suppressed warnings.

Method: Roslyn syntactic debt markers (suppressions/TODO/FIXME/HACK/empty-catch/commented-code/Obsolete) plus SymbolFinder dead-code analysis; weighted-debt-per-KLoC density deducted 2.0x per unit. Deterministic, exhaustive.

Maturity: Documented → Verified → Prevented · effective 9.9 / 10 · rule-coverage 100% · ceiling Prevented

14 deducted task-comment markers across 35989 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.

TodoComment · ×14workspace-import/test/test/com/jetbrains/ls/imports/GradleProjectImportTest.kt:99

What to do

Resolve the 14 TodoComment finding(s) in Explicit Debt — start with ModCommandData.kt (2), LSDocumentCommandComandExecutor.kt (2), GradleProjectImportTest.kt. — One of this dimension's main actionable groups (14 warning-level).
Stand up a CI pipeline, then gate Explicit Debt in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

Detailed fixes: d17_recommendation.md · top locations in Appendix A, every location in findings.md.

Do you agree with this assessment?

D19 · Documentation Quality10.0 / 10Exemplary○ Nothing flagged

What it measures: Whether the project's documentation is clear, complete, and useful.

Method: Every README, docs/ document and root guide parsed by its markup and measured in Unicode letters. Published: a runnable or packaged .NET project whose README (or a document it links, or a root guide) shows no example, and a root README naming none of three or more projects. Overview, licence, boilerplate, wall-of-text, empty-section and XML-doc rows are measured and withheld (counted in gaps) after adjudication. Deterministic, exhaustive, advisory.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

1 of 1 documentation facets pass in full. 5 document(s) read across 1 unit(s).

✓ On the Gold path — maintain.

Detailed fixes: d19_recommendation.md.

Do you agree with this assessment?

D28 · Secrets (history)10.0 / 10Exemplary○ Nothing flagged

What it measures: Whether any secrets were ever committed — scanned across the full git history, not just now.

Method: Secret scan via TWO gitleaks detect passes in an isolated checkout — the full git history, then a second --no-git pass over the working tree as it stands — merged and de-duplicated by (rule, file, line); each match flagged High. Both invocations are recorded in the audit trail. Exhaustive; when the tool is absent, or when its output cannot be parsed into the expected shape, the dimension is WITHHELD as an explicit measurement gap on our side — unscored and excluded from the lens, never a hedged middling score.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

gitleaks scanned the full history AND the current working tree and found no secrets.

✓ On the Gold path — maintain.

Detailed fixes: d28_recommendation.md.

Do you agree with this assessment?

D29 · Static Analysis (SAST)10.0 / 10Exemplary○ Nothing flagged

What it measures: Real static-analysis (SAST) findings — likely security bugs in the code, any language.

Method: Polyglot static analysis via semgrep across the repo using the pinned, image-baked p/security-audit + p/owasp-top-ten rulesets (no scan-time registry fetch); severity rules (ERROR/WARNING/INFO) map to a full-band severity-weighted score. Exhaustive, deterministic; degrades on parse failure.

Coverage: semgrep pattern rules over all files — exhaustive for the rule set, blind to classes of bug without a rule (clean = no rule matched).

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

semgrep found no security issues. semgrep hit a parse error in 27 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/diagnostics/LSCommonInjectionInspectionDiagnosticProvider.kt` (lines 38–42, line 42, line 65, …), `features-impl/common/src/com/jetbrains/ls/api/features/impl/common/diagnostics/LSCommonInjectionSyntaxErrorDiagnosticProvider.kt` (lines 31–33, line 33, line 50), `features-impl/common/src/com/jetbrains/ls/api/features/impl/common/diagnostics/LSCommonInspectionSuppressionCodeActionProvider.kt` (line 70, line 121), … (+22 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.

✓ On the Gold path — maintain.

Detailed fixes: d29_recommendation.md.

Do you agree with this assessment?

D30 · Dependency Vulnerabilities10.0 / 10Exemplary○ Nothing flagged

What it measures: Whether any dependency has a known published vulnerability (CVE), direct or transitive, in ANY ecosystem the repository declares — Dart pub, Elixir and Erlang via Hex, Go modules, Java and Kotlin via Maven/Gradle, JavaScript/npm, .NET/NuGet, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift.

Method: Dependency-CVE scan across every ecosystem the repository declares, scored ONCE. Three sources are unioned and deduplicated by advisory identity (rule id + alias closure, CVE<->GHSA) scoped to package+version, keeping the worst severity: `osv-scanner --recursive` over osv.dev for Dart pub, Elixir/Hex (and Erlang, whose `rebar.lock` syft first converts to a CycloneDX SBOM the scanner reads, with rows attributed back to the lock), Go, Java and Kotlin via Maven/Gradle (and Scala, whose sbt build's pinned direct declarations are written into a CycloneDX SBOM the scanner reads, with rows attributed back to the build file), npm, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift; `trivy fs --scanners vuln` for npm lockfiles; and `dotnet list package --vulnerable --include-transitive` for NuGet (with per-advisory collapse of the project x target-framework fan-out), plus a DECLARED-dependency arm that resolves a published gem's gemspec against rubygems.org where no Gemfile.lock is committed. `SeverityScore(c,h,m,l, normalizer 8.0)`. NotApplicable only when NO ecosystem is readable; if any applicable ecosystem could not be scanned the findings are REPORTED and the score is withheld. Supersedes the npm and OSV arms, retired 2026-09-05.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

No known-vulnerable dependencies in any ecosystem this repository declares.

✓ On the Gold path — maintain.

Detailed fixes: d30_recommendation.md.

Do you agree with this assessment?

D34 · Knowledge Freshness9.6 / 10Exemplary✓ Tool-verified

What it measures: Whether anyone still has living knowledge of each file, or it has been orphaned — last understood long ago by someone now gone quiet. The sibling of the bus factor: D16 asks who owns it, D34 asks whether anyone still knows it.

Method: File orphaning as total living-knowledge decay below one focused-commit's worth within a year, computed per-file from the D16 decay model. Exhaustive, deterministic over fixed history.

Maturity: Documented → Verified → Prevented · effective 9.6 / 10 · rule-coverage 100% · ceiling Documented

7 of 177 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is workspace-import/gradle-plugin/src/com/jetbrains/ls/imports/gradle/utils/androidReflection.kt. Counted over 177 of the 383 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.

Orphaned file · ×7workspace-import/gradle-plugin/src/com/jetbrains/ls/imports/gradle/utils/androidReflection.kt:1

Orphaned files with no living knowledge

✓ On the Gold path — maintain.

Detailed fixes: d34_recommendation.md · top locations in Appendix A, every location in findings.md.

Do you agree with this assessment?

D35 · Change Coupling9.0 / 10Adequategated by 9 critical findings✓ Tool-verified

What it measures: Whether files that change together actually belong together — pairs that repeatedly co-change in git history despite having no explicit code dependency, surfacing the hidden/logical coupling (and boundaries in the wrong place) a static scan can't see.

Method: Pairwise co-occurrence over the per-commit file sets in git history (production source only — tests and generated dropped): Degree-of-Coupling = shared ÷ min individual revisions, reported above noise floors (each file ≥10 revisions, ≥5 shared commits, ≥50% strength); sweeping commits excluded. Deterministic over fixed history.

Coverage: Population: PRODUCTION source files only — test and generated files are dropped before pairing, so a class co-changing with its own test (trivially ~100%) can't drown the real production↔production coupling. Pairs ranked by Degree-of-Coupling. A non-source file is never a coupling PARTICIPANT either: documentation, schemas, config and data files are dropped with the rest, so a code↔docs pair — a command and the reference page that restates it — is not reported however strongly the two co-change; nor is coupling that runs THROUGH a build step or config file.

Maturity: Documented → Verified → Prevented · effective 9.0 / 10 · rule-coverage 100% · ceiling Documented

Strongest change-coupling: ModuleSourceSetImpl.kt↔IdeaProjectMapper.kt 90%; LSCommonDefinitionProvider.kt↔LSKotlinPackageDefinitionProvider.kt 80%; LSCommonInspectionDiagnosticProvider.kt↔LSCommonSyntaxErrorDiagnosticProvider.kt 73%

Boundary-crossing change coupling: LSSimpleCodeActionProvider.kt ↔ LSKotlinIntentionCodeActionProvider.kt · ×9api.features/src/com/jetbrains/ls/api/features/codeActions/LSSimpleCodeActionProvider.kt:1

Change coupling: ModuleSourceSetImpl.kt ↔ IdeaProjectMapper.kt · ×8workspace-import/gradle-plugin/src/com/jetbrains/ls/imports/gradle/model/impl/ModuleSourceSetImpl.kt:1

Change-coupling hub: LSKotlinPackageDefinitionProvider.kt → LSCommonDefinitionProvider.kt, LSCommonInspectionDiagnosticProvider.kt, LSHoverProviderBase.kt, LSCommonReferencesProvider.kt, LSKotlinSemanticTokensProvider.kt · ×2features-impl/kotlin/src/com/jetbrains/ls/api/features/impl/kotlin/definitions/LSKotlinPackageDefinitionProvider.kt

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 8 Change coupling finding(s) in Change Coupling — start with LSCommonInspectionDiagnosticProvider.kt (2), ModuleSourceSetImpl.kt, ModuleSourceSetsModelBuilder.kt. — One of this dimension's main actionable groups (8 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).

Detailed fixes: d35_recommendation.md · top locations in Appendix A, every location in findings.md.

Do you agree with this assessment?

D43 · Malicious Dependencies10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether any dependency the repository declares is published as MALICIOUS rather than merely vulnerable — a package that is an attacker's work, in any ecosystem osv-scanner reads. Scored apart from D30 because the answer is binary: there is no safe version to upgrade to, and the fix is to remove the package and rotate every credential it could have read.

Method: The same dependency scan D30 reads, partitioned on the scanner's own classification rather than rescanned: a row is MALICIOUS when its id is in the `MAL-` space (the ossf/malicious-packages feed) OR its `database_specific.cwe_ids` carries `CWE-506` ("Embedded Malicious Code"). Both channels are structural; the summary text is deliberately NOT read, because a malicious-package record whose summary says only "Critical severity vulnerability" is a real shape ([GHSA redacted]) and a text matcher misses it. Scored BINARY: any surviving row is 0, whatever its severity and however many CVEs sit beside it — a hostile dependency is not a quantity. Applicability and degradation are D30's: NotApplicable only when no ecosystem is readable, and an unscannable ecosystem degrades rather than reading clean. SCORED, not informational.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

No dependency in any ecosystem this repository declares is published as malicious.

✓ On the Gold path — maintain.

Detailed fixes: d43_recommendation.md.

Do you agree with this assessment?

D44 · Platform End-of-Life10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether anyone still ships security patches for the platform this repository RUNS ON — the runtime it pins and the framework majors its own constraints hold it to. Separate from D12 because the question differs: a current Django on an end-of-life Python is perfectly up to date and completely unsupported, and the fix is a migration rather than a version bump. What the repository says it merely SUPPORTS is never charged.

Method: End-of-life PLATFORM read from the repository's own declarations and graded against a FROZEN, dated table of vendor support dates — no network, no feed, no API, so this dimension answers identically inside a closed scan fence. Two subjects: a RUNTIME the project pins (a single or all-end-of-life TargetFramework, a .nvmrc or .python-version, a requires-python CAP) and a FRAMEWORK major a dependency constraint cannot move off (a caret, tilde or exact version; `vue@^2.7.16` pins Vue 2). A FLOOR is deliberately never charged — `requires-python = ">=3.8"` states what a package SUPPORTS, not what it runs on — and a multi-target project is charged only when EVERY target is out of support. Runtime 4.0/product capped 8.0, framework 1.5 capped 4.5. The table is safe to freeze because a statement about support that ended in the past cannot become false: it loses recall as it ages, never precision, and a test asserts every entry predates the freeze date. Disjoint from D31 (a container image's OS layer) and D29 (the toolchain a CI workflow installs). Abstains when the repository declares no platform this pass reads — never scores it clean.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 32 platform declaration(s) and 80 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.

✓ On the Gold path — maintain.

Detailed fixes: d44_recommendation.md.

Do you agree with this assessment?

Frontend & cross-cutting dimensions

R = React/JS · M = Maturity · P = Readiness.

AX10 · Code composition6.3 / 10Adequate✓ Tool-verified

Other · Architecture — How the codebase splits by code ROLE — domain, application, infrastructure, test, generated. The significance map behind the knowledge/coupling weighting, and a DDD signal in its own right: a thin domain core under fat infrastructure is the anemic-domain smell, quantified. How each file's role is decided, because the split is only as good as that: a generated name or a build-output tree makes it Generated, a test project makes it Test, and otherwise the file's NAMESPACE and PATH words are matched against fixed vocabularies in a fixed ORDER — domain, then infrastructure, then application — so a file whose words hit two layers is counted under the earlier one. A production file matching none of them counts as application, so that share reads 'application or unclassified' rather than a measured application layer. Roles come from naming convention, never from what the code does. On this repository the split was taken from the source tree on disk rather than from a loaded .NET workspace, so a file's role is decided by its PATH segments alone — no declared namespace was available to add to the evidence — and generated output is excluded from the census entirely rather than counted as a generated share.

Method: Roslyn line-count by code ROLE: every source file classified Domain/Application/Infrastructure/Test/Generated by namespace + path convention (the shared CodeRoleClassifier), then significant lines summed per role. Deterministic; the advisory score is the business-logic (domain+application) share of production code.

Coverage: Population: ALL source files, each bucketed into ONE of five roles (Domain/Application/Infrastructure/Test/Generated) by namespace + path convention — a file whose layer isn't named in the convention falls to Application (the neutral default), and the split is line-count, not semantic depth or business value.

What to do

The domain core is a small share of production code, but most of the rest matched no layer vocabulary at all — so this is not yet an anemic-domain finding. The namespace/path convention could not place that code, which makes the composition above a statement about the naming, not about the design. Name the layers (or check that the repository's conventions differ from the ones this check knows) before reading a thin domain into it.

Do you agree with this assessment?

AX3 · Project dependency cycles10.0 / 10Exemplary✓ Tool-verified

Other · Architecture — Whether the project-reference graph is acyclic (cycles block independent build/deploy and signal eroding boundaries).

Method: Project reference cycles via elementary-DFS over real .csproj references, using the engine shared with D5/D7; cyclic versus acyclic. Exhaustive, deterministic.

Do you agree with this assessment?

AX5 · Architecture & structure10.0 / 10Exemplary✓ Tool-verified

Other · Architecture — Whether the codebase has a recognisable, scale-appropriate structure (a named architectural style, or modular enough for its size) rather than being an ad-hoc ball of mud.

Method: Roslyn plus csproj analysis: architecture style detection (DDD, clean, vertical-slice, CQRS) and structure fitness for repo size. Deterministic.

Do you agree with this assessment?

AX6 · Interface segregation10.0 / 10Exemplary✓ Tool-verified

Other · Architecture — Whether interfaces stay focused rather than fat — the Interface-Segregation principle (SOLID 'I').

Method: Roslyn scan: public interface declared-member counts (accessors fold into their property/event); fat-interface threshold (over 15 declared members) flagged per type. Each finding also reports the distinct-OPERATION count — members counted by name, so an overload group counts once — which decides whether it states the caller-side ISP harm or the implementer-side burden of an overload set. TypeScript: exported interfaces that declare behaviour, counted over their REQUIRED operations (method signatures and function-typed properties with no `?`, once per signature) — data-shape interfaces and ambient .d.ts declarations are outside the population; JavaScript declares no interfaces and is not applicable. Deterministic, type-level.

Do you agree with this assessment?

AX7 · Slice cohesion1.8 / 10Critical✓ Tool-verified

Other · Architecture — Whether feature slices stay independent (no direct cross-slice references) — the discipline that makes vertical-slice architecture pay off.

Method: Roslyn scan (vertical-slice gated): feature slices resolved from namespaces (.Features.*, .Slices.*) or project names; cross-slice type references detected. Deterministic, traceable.

`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:127
`NameData` (slice 'impl') depends on `PsiSerializablePointer` from slice 'utils'. — features-impl/common/src/com/jetbrains/ls/api/features/impl/common/callHierarchy/LSCallHierarchyProviderBase.kt:150
`ClassNameData` (slice 'impl') depends on `PsiSerializablePointer` from slice 'utils'. — features-impl/common/src/com/jetbrains/ls/api/features/impl/common/callHierarchy/LSCallHierarchyProviderBase.kt:153
`MethodNameData` (slice 'impl') depends on `PsiSerializablePointer` from slice 'utils'. — features-impl/common/src/com/jetbrains/ls/api/features/impl/common/callHierarchy/LSCallHierarchyProviderBase.kt:165
`FieldNameData` (slice 'impl') depends on `PsiSerializablePointer` from slice 'utils'. — features-impl/common/src/com/jetbrains/ls/api/features/impl/common/callHierarchy/LSCallHierarchyProviderBase.kt:172
`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:342
`LSCommonConfigurationKt` (slice 'impl') depends on `LSConfigurationPiece` from slice 'language'. — features-impl/common/src/com/jetbrains/ls/api/features/impl/common/configuration/LSCommonConfiguration.kt:23
`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
`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:27
`Piece` (slice 'impl') depends on `LSSemanticTokenType` from slice 'semanticTokens'. — features-impl/common/src/com/jetbrains/ls/api/features/impl/common/semanticTokens/LSHighlightingSemanticTokens.kt:52
`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:30
`LSKotlinCompletionProvider` (slice 'impl') depends on `UniqueId` from slice 'configuration'. — features-impl/kotlin/src/com/jetbrains/ls/api/features/impl/kotlin/completion/LSKotlinCompletionProvider.kt:27
`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:70
`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.

Do you agree with this assessment?

M1 · Documentation (README)7.3 / 10Strong✓ Tool-verified

Maturity · Maturity — Whether the repo and its projects have a README, and whether it's substantive and current.

Method: Filesystem scan: README presence, word count, and headings for depth; git history for staleness. Exhaustive across root and project dirs, deterministic.

What to do

Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
Add a README to the 4 of 6 project(s) that lack one — worth up to 1.3 pts.

Do you agree with this assessment?

M2 · Architecture documentation0.0 / 10Critical✓ Tool-verified

Maturity · Maturity — Whether key decisions (ADRs) and the high-level shape (C4/diagrams) are written down.

Method: Filesystem scan: ADR folder/naming conventions or content, plus Mermaid/PlantUML/C4/architecture.md discovery. Exhaustive, deterministic.

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.

Do you agree with this assessment?

M3 · Folder & project structure10.0 / 10Exemplary✓ Tool-verified

Maturity · Maturity — Whether the repo is organised deliberately — src/test separation and consistent project naming.

Method: Filesystem scan: src/test folder separation and namespace-prefix consistency (majority RootNamespace agreement). Exhaustive across projects, deterministic.

Do you agree with this assessment?

M4 · Documentation accuracy10.0 / 10Exemplary○ Nothing flagged

Maturity · Maturity — Whether the README actually describes the code that exists (LLM-judged, advisory).

Method: Judged by language model at low temperature: README accuracy versus actual projects, within a disclosed tolerance. Advisory, not a measured number.

Do you agree with this assessment?

P1 · CI/CD gates0.0 / 10Critical✓ Tool-verified

Readiness · Readiness — Whether an automated pipeline builds and tests every change.

Method: Filesystem scan: CI workflow files (.github/workflows, .gitlab-ci.yml, etc.) for build and test stages. Exhaustive, deterministic.

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.

Do you agree with this assessment?

P10 · Library API & versioning10.0 / 10Exemplary○ Nothing flagged

Readiness · Readiness — For a library: a deliberate (small) public API surface and explicit semantic versioning so consumers can depend on it safely.

Method: Roslyn scan: public API surface area and semantic-versioning markers (SemVer attributes, changelog entries) for libraries; off .NET, a library is the ecosystem's publication act (an npm package that is not private and names an entry point, a PyPI distribution with a build system, a Rust library crate, a Maven/Gradle module that publishes, a Go module with no package main, a gemspec, a Composer library, a SwiftPM library product, a pub.dev or Hex package), its surface is the share of types the language model records as public (Rust, Swift, Java, Kotlin, Go, Dart; not measured where the model records no type visibility or, as in TypeScript, only module-level export), and its version is read from the manifest, a semver CHANGELOG, release tooling or semver git tags. Exhaustive, deterministic.

Do you agree with this assessment?

P3 · Security & performance tooling0.0 / 10Critical✓ Tool-verified

Readiness · Readiness — Whether SAST, secret/dependency scanning and performance benchmarking are wired in (presence, not runtime).

Method: Filesystem scan: SAST configuration, dependency-update automation, secret scanning, and a benchmark harness or benchmark step — in this repository's own ecosystem. Exhaustive, deterministic.

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.

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.

Do you agree with this assessment?

P6 · Release Hygiene10.0 / 10Exemplary✓ Tool-verified

Readiness · Readiness — Whether releases are traceable — a maintained changelog and explicit version stamping.

Method: Filesystem scan: changelog file presence and version tags in csproj or git tags. Exhaustive, deterministic.

Do you agree with this assessment?

PF2 · Allocation hygiene6.2 / 10Adequate✓ Tool-verified

Readiness · Performance — Whether the code is written to minimise allocations so it doesn't pressure its host's memory manager — buffer/slice views over copies, object pooling, stack or value-type allocation, and buffer writers. Reward-only: credited where present, never penalised where a simpler style is fine.

Method: Production-source scan: density (per 1k LoC) of allocation-aware APIs — in .NET Span/Memory, ArrayPool/ObjectPool, stackalloc, ValueTask, value-type structs, IBufferWriter, string.Create, SkipLocalsInit; off .NET, with comments and strings blanked, Go's sync.Pool, preallocated slices/maps, Grow, strconv.Append* and buf[:0] reuse; the JVM's NIO buffer views, MemorySegment, primitive collections, pools and literal presizes (plus Kotlin primitive arrays and value classes, Scala AnyVal and @specialized); Swift's reserveCapacity, ContiguousArray, withUnsafe* access and ~Copyable. Activated off .NET on the same floor (400 lines, and benchmarks or 8 uses); Rust and garbage-collected scripting languages are not applicable. Reward-only. Deterministic, syntax/text detection.

What to do

Raise allocation-aware density on the hot paths — currently 9 use(s) across 27,878 production line(s) (~0.3/1k). More of the idioms below on the allocation-heavy paths climbs this toward 10.
Java: on hot paths, work through buffer views (ByteBuffer/LongBuffer slices, MemorySegment) instead of copies, avoid boxing with primitive collections (fastutil, Eclipse Collections, HPPC, Trove), presize collections and StringBuilders, and pool expensive buffers (Netty's pooled allocator, commons-pool).
Kotlin: on hot paths, use primitive arrays (IntArray, LongArray …) and @JvmInline value classes instead of boxed values, primitive collections (androidx.collection, fastutil) instead of boxed ones, and presize collections and StringBuilders.

Do you agree with this assessment?

PF3 · Async & latency hygiene6.0 / 10Adequate✓ Tool-verified

Readiness · Performance — Whether asynchronous code stays responsive — it avoids sync-over-async blocking (a .NET .Wait()/.GetAwaiter().GetResult(), a time.sleep or blocking HTTP call inside a Python coroutine, a *Sync call inside an async JavaScript function, block_on inside a Rust async fn, runBlocking inside a Kotlin suspend function, block() inside a Reactor publisher) that stalls a thread or event loop and risks deadlock, and, where the code is a reusable library on .NET, awaits with ConfigureAwait(false) so it never captures and stalls its caller's context.

Method: Production-source scan: sync-over-async blocking counted everywhere — .Wait()/.GetAwaiter().GetResult() in .NET; off .NET, read from the language model, a blocking call inside an async function (Python, TS/JS, Rust, Kotlin, Swift, Dart) or inside a Java method returning a Reactor Mono/Flux or a Scala method returning a Future or effect — and, for a .NET library with ≥5 awaits, the share of awaits using ConfigureAwait(false). Deterministic, syntax/text detection.

`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:773
`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.

Do you agree with this assessment?

R1 · Type Safety9.6 / 10Exemplary✓ Tool-verified

React / JS · Code Health — How much of the frontend is typed TypeScript vs untyped JavaScript.

Method: Frontend file inventory: the share of typed TypeScript vs untyped JavaScript across the source tree. Deterministic, exhaustive over frontend files.

What to do

Migrate the remaining .js/.jsx files to TypeScript.

Do you agree with this assessment?

R10 · Code Duplication9.6 / 10Exemplary✓ Tool-verified

React / JS · Code Health — Near-exact copy-pasted blocks of substantial extent across the frontend (the D4 clone algorithm over JS/TS tokens, D-386): a block is reported only where its copies still agree on most of their own identifiers and literals, or were renamed as they were pasted but kept most of their constants, and where the copies carry enough code to stand on their own or the copied extent reaches 30 lines — so a re-implementation sharing neither names nor values, and a small pasted declaration, are both found and deliberately not reported, and a clean R10 is not a claim that nothing was copied.

Method: Near-exact copy-pasted blocks of substantial extent across the frontend (the D4 clone algorithm run over JS/TS tokens). Masking finds the candidates; a block is reported when its copies still agree on most of their own identifiers and literals, or when a renamed copy still agrees on most of its constants, AND the copies carry enough code to stand on their own — or when the copied extent reaches 30 lines. So a re-implementation sharing neither names nor values, and a small pasted declaration, are deliberately not counted. Deterministic.

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-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.

Do you agree with this assessment?

R2 · Cyclomatic Complexity8.9 / 10Strong✓ Tool-verified

React / JS · Code Health — Per-function cyclomatic/cognitive complexity from the token-level function scanner (D-386) — real branching, not a regex heuristic.

Method: Per-function cyclomatic/cognitive complexity from a token-level function scanner (real branching, not a regex heuristic), computed over every frontend function. Deterministic.

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:161
(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
(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:864
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:1053
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:271
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:487

What to do

Break down the listed branch-heavy functions; aim P95 cyclomatic ≤ 5.

Do you agree with this assessment?

R3 · Large Files7.9 / 10Strong✓ Tool-verified

React / JS · Code Health — How many source files exceed the large-file threshold.

Method: Components/modules exceeding the large-file threshold, counted exhaustively across the frontend source tree. Deterministic.

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 1273 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

What to do

Split each oversized file along the responsibilities already in it, into smaller focused modules in the same package.

Do you agree with this assessment?

R4 · Test Coverage9.3 / 10Exemplary✓ Tool-verified

React / JS · Readiness — Static test reachability (D-386): the share of production files reachable from any test via the import graph — measured without running anything.

Method: Static test reachability: the share of production files reachable from any test via the import graph — measured without running anything. Deterministic.

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).

Do you agree with this assessment?

R6 · Tooling6.7 / 10Adequate✓ Tool-verified

React / JS · Readiness — Whether the project wires up test, lint and typecheck — detected from each package.json script's COMMAND (eslint / tsc / vitest / jest / playwright), not just its name, and corroborated against CI-workflow invocations so a tool run only in CI still counts.

Method: package.json scanned for test/lint/typecheck script wiring. Deterministic presence check.

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.

Do you agree with this assessment?

R7 · Dead Code10.0 / 10Exemplary✓ Tool-verified

React / JS · Code Health — Files unreachable from every application/tooling/test entry point, and exports nothing imports (module-graph reachability, D-386).

Method: Dead code: files unreachable from every application/tooling/test entry point plus exports nothing imports, via module-graph reachability. Deterministic, exhaustive over the import graph.

Do you agree with this assessment?

R8 · Dependency Hygiene8.0 / 10Strong✓ Tool-verified

React / JS · Readiness — npm dependency truthfulness (D-386): unused dependencies, imports not declared anywhere, and type-/test-only packages shipped as production deps.

Method: npm dependency truthfulness: unused dependencies, imports declared nowhere, and type-/test-only packages shipped as production deps — from the manifest + import graph. Deterministic.

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.

Do you agree with this assessment?

R9 · Circular Imports7.5 / 10Strong✓ Tool-verified

React / JS · Architecture — Import cycles in the module graph (D-386) — files that can only be understood and changed together.

Method: Import cycles in the module graph, detected exhaustively over JS/TS imports (the same cycle detection as the .NET coupling dimension). Deterministic.

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 10 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.

Do you agree with this assessment?

X1 · Async correctness10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether the code avoids sync-over-async (deadlock-prone blocking on tasks) and async void.

Method: Roslyn syntax scan: async methods scanned for .Wait()/.GetAwaiter().GetResult() and async-void outside event handlers. Deterministic, hard fact per invocation.

Do you agree with this assessment?

X12 · Unreachable branch10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether any branch is dead by construction — a switch arm whose label can never equal a case-normalised subject, or an `else if` whose predicate the arm above has already swallowed.

Method: Roslyn syntax + semantics: switch labels compared against the subject's own case normaliser, and if/else-if chains checked for a literal an earlier arm's containment test already swallows. Deterministic, provable per finding. Advisory.

Do you agree with this assessment?

X13 · Undrained process stream10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a child process that has BOTH standard streams redirected drains both — reading one to the end while the other is never read deadlocks once the child fills the unread pipe.

Method: Roslyn syntax + semantics: ProcessStartInfo launches with both streams redirected, checked for a drain of each stream across the enclosing type. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `spawn` imported from `child_process` whose stdout and stderr are both pipes (no options, no `stdio`, or `stdio` of `'pipe'`), bound to a local that never leaves its scope, where exactly one of the two streams is read, the other never, and the child’s `close`/`exit` (or the read stream’s end) is awaited; a shell redirect in the call’s arguments or a `kill` of the child suppresses it. The same rule reads Python’s `subprocess.Popen`, Dart’s `Process.start`, Ruby’s `Open3.popen3`, and Scala’s JDK process starts (`new ProcessBuilder(…).start()` with no `redirectErrorStream`/`redirectError`/`redirectOutput`/`inheritIO`, `Runtime.getRuntime.exec`) where one of `getInputStream`/`getErrorStream` is read and the other never while `waitFor()` is called or the read stream is read to its end. Deterministic, provable per finding. Advisory.

Do you agree with this assessment?

X14 · Bypassable address classification10.0 / 10Exemplary○ Nothing flagged

Other · Security — Whether a hand-rolled public/private IP check can be walked past — a method that unwraps IPv4-mapped IPv6 but returns the opposite verdict for the same host written as IPv4-compatible, 6to4 or NAT64.

Method: Roslyn syntax + semantics: methods that unwrap IPv4-mapped IPv6 and hand-roll IPv4 range carve-outs, checked for whether the IPv6 branch also accounts for the IPv4-compatible, 6to4 and NAT64 embeddings. Deterministic, provable per finding. Advisory.

Do you agree with this assessment?

X15 · Unvalidated length from an untrusted reader10.0 / 10Exemplary○ Nothing flagged

Other · Security — Whether a length read out of the stream being parsed is bounded before it is allocated or read — an unchecked count taken from the input lets the input choose the allocation.

Method: Roslyn syntax + semantics: integer lengths read from a BinaryReader and spent on a bulk read or an array allocation, checked for any comparison or bounding call on the value anywhere in the method. Deterministic, provable per finding. Advisory.

Do you agree with this assessment?

X16 · Unfloored truncation loop10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a loop that shortens a string until it fits a length budget has a floor — one with none grinds the value down to the empty string, or past it into a negative-length `Substring`.

Method: Roslyn syntax + semantics: while/do loops whose body's only effect on a string is to drop its last character, checked for whether anything — a direct comparison on the length, a body guard, a break — bounds that length below. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `while`/`do` loop whose body’s one assignment to a value is `x = x.slice(0, -1)` or `x = x.slice|substring|substr(0, x.length - 1)`, driven by a condition that reads `x.length` only as a term of a larger expression — never compared directly, never tested for truthiness, and with no other read of `x` — and whose body has no `break`, `return`, `throw` or `if` naming `x`. Deterministic, provable per finding. Advisory.

Do you agree with this assessment?

X17 · Uncapped recursion over a caller-supplied document10.0 / 10Exemplary○ Nothing flagged

Other · Security — Whether a walk that recurses through a JSON/XML tree handed in by its caller bounds how deep it will go — an uncapped walk lets the document's nesting choose the stack depth, and the resulting StackOverflowException cannot be caught.

Method: Roslyn syntax + semantics: methods that take a JSON/XML document node and call themselves with a child of it, reachable from an externally-callable member of the same type that accepts a document, checked for any depth parameter, descent counter or threaded arithmetic anywhere in the walk. On a repository with no .NET source it reads TypeScript off the engine’s own token stream (test, vendored, generated and minified paths and `.d.ts` not) with the same rule: a function or method with a parameter typed as a document value — `unknown`, `any`, `object`, `Record<string, unknown|any>`, a JSON alias (`JsonValue`, `JSONObject`, …) or a DOM node global the file does not rebind — that calls itself (bare, or through `this` for a method, or hands itself to a call over the value as in `value.map(walk)`) with something it took out of that value and never through an ancestor accessor such as `closest()` or `parentElement`, that is exported or reached from an exported function (a public method of the same exported class) taking such a value, and that names no depth, level, nesting, recursion, remaining or budget anywhere and threads no `+`/`-` arithmetic through a self-call. Plain JavaScript is not read: with no annotation nothing tells a parsed document from a tree the code built itself. Deterministic, provable per finding. Advisory.

Do you agree with this assessment?

X18 · Disposal-pattern correctness5.3 / 10Adequate✓ Tool-verified

Other · Code Health — Whether a type's disposal matches what it OWNS — releasing what it created, leaving alone what it was handed, and not declaring a finalizer for state that has nothing unmanaged to finalize.

Method: Roslyn syntax + semantics: every assignment to a disposable field is read to decide whether the type CREATED the value or was handed it, and the type's disposal is checked against that answer — an injected interface it disposes, a value it constructed and never releases, a finalizer on a type holding nothing unmanaged, and a disposable local whose every reference is a plain member read. A value handed to a container that disposes its contents (a parent control's `Controls` collection, a component `IContainer`) is released by that container and is not reported; generated code is out of population. On a repository with no .NET source the same ownership questions are read in JavaScript/TypeScript off the engine’s own token stream (test, vendored, generated and minified paths not): a class declaring `dispose()`, `[Symbol.dispose]()` or `[Symbol.asyncDispose]()` that disposes a field it was handed through a constructor parameter typed as a repository interface or resolved by a dependency-injection container; that assigns a field only ever from `new X(…)` of a disposable class and neither releases it anywhere in the class nor names it in its disposal member or a method that member calls, nor hands it to anything else; and a `const`/`let` local built from literals only whose every reference opens a statement operating on a non-release member of it. A class is disposable when every repository declaration of its name declares or inherits a disposal member, or when it is a documented library disposable (`vscode` EventEmitter, CancellationTokenSource and Disposable; three.js geometries, materials, textures, render targets, renderers, controls and composers). The finalizer arm has no JavaScript counterpart: a class cannot declare one. Dart is read for the owned-and-never-released arm: a Flutter `State` (or a class declaring `dispose()`/`close()`) whose library-private field is written only with direct creations of a framework controller, `FocusNode`, `StreamController` or periodic `Timer` (or a `.listen(…)` into a field declared `StreamSubscription`), which nothing in the class or its library releases (`dispose`/`close`/`cancel`) and which is never handed on except as a named argument. Ruby is read for the owned-and-never-released arm and the abandoned-local arm: a class declaring an instance `close`, `dispose`, `shutdown`, `stop`, `disconnect` or `terminate` whose instance variable is written only with a blockless core descriptor creation (`File.open`/`new`, `Tempfile`, `Dir.open`, `IO.popen`, the `socket` and `openssl` socket classes) that no method of the class closes and that is never handed on (passed, returned, stored, exposed by `attr_reader`, delegated) — a class whose superclass or mixin lies outside the repository is not judged — and a blockless creation read through and dropped (`File.open(path).read`) or held in a local that is never closed, returned, passed or stored (a `&:read` block-pass, an `autoclose: false` borrow and a `fileno` hand-over are not abandonment). PHP is read for the same two arms: a class (not a trait, and not one using a trait) declaring an instance `close`, `dispose`, `shutdown`, `stop`, `disconnect` or `terminate` whose `private` property (or a `final` class's `protected` one) is written only with a direct core `fopen`, `tmpfile`, `popen`, `proc_open`, `fsockopen`, `stream_socket_client`/`server` or `opendir` that nothing in the class closes (`fclose`, `pclose`, `closedir`, `unset`, a reset to `null`) and that is never handed on, and a handle held in a function's local, or read through as the argument of a reader, that is never closed, returned, passed, captured or stored; a `php://` stream, `curl_init`, `SplFileObject`, `PDO` and a function the repository declares under the core name are not read. Deterministic, provable per finding. Advisory.

`RunOutputTerminal` declares a disposal member — so it has told every caller it holds something worth releasing — and it constructs `writeEmitter` itself (line 59, `new EventEmitter`), which makes that instance its own. But `writeEmitter` is named in none of the methods the disposal search covered: `dispose` (line 88) — 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:59

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.

Do you agree with this assessment?

X19 · Unrestored process-global state10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a method that temporarily changes state belonging to the whole process — the working directory, an environment variable — puts it back on EVERY path: a restore reached only when nothing throws leaks the change to the rest of the process.

Method: Roslyn syntax + semantics: method bodies that write the process working directory or an environment variable and write it back in the same body, checked for whether that restore sits in a `finally`/`catch` or only on the straight-line path. On a repository with no .NET source the same rule reads production JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not): `process.chdir`, `process.env.NAME =`/`["NAME"] =` and `delete process.env.NAME`, and Deno’s `Deno.chdir`/`Deno.env.set`/`Deno.env.delete`, paired per function body (a nested function or arrow is its own body, and module top-level code is none), where the last write puts back a local the body captured from the same global or deletes a variable the first write set, with at least one statement between them; a write in a `catch`/`finally` of that body silences it. Deterministic, provable per finding. Advisory.

Do you agree with this assessment?

X2 · Cancellation propagation8.0 / 10Strong✓ Tool-verified

Other · Code Health — Whether async functions that make a cancellable request accept or pass on an AbortSignal (adoption curve).

Method: Roslyn scan: every async method (excluding framework-fixed overrides/Blazor handlers) checked for CancellationToken parameter presence. Deterministic, adoption percentage. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same question: every named async function that itself makes a request an AbortSignal can cancel (global `fetch`, axios and its file-local instances, ky, ofetch) counts, and it is compliant when its parameters or body name a signal or it hands one of its own parameters to the request as options; signatures a framework fixes (JSX event handlers, route and lifecycle exports, request-first handlers, `override`, `'use server'` modules, TanStack `mutationFn`) are exempt unless they take a signal. Deterministic, adoption percentage.

Only 2/3 async functions that make a cancellable request (fetch, axios, ky, ofetch) 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

What to do

Thread an AbortSignal through async functions that make requests, so the work stops when its caller gives up.

Do you agree with this assessment?

X20 · Mistyped argument guard10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether an argument guard throws the exception its own condition describes — a guard that rejects a value for being EMPTY and reports it as `NullPointerException` (Java, Kotlin, Scala), `ArgumentError.notNull` (Dart) or `ArgumentNullException` (F#'s `nullArg`) tells the caller a parameter was null when it provably was not.

Method: Roslyn syntax: `throw new ArgumentNullException(nameof(p))` statements controlled by an `if`, whose condition is read for a test that is true of a NON-null `p` — an emptiness test that dereferences it (`p.Count == 0`, `!p.Any()`) or a BCL predicate documented true of the empty value (`string.IsNullOrEmpty(p)`). Deterministic, provable per finding. Advisory.

Do you agree with this assessment?

X21 · Side-effecting pattern guard10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a `when` guard is free of side effects — a guard that increments a counter or assigns while deciding whether its arm matches applies that change during PATTERN MATCHING, on an arm that may not be selected, and skips it entirely when a short-circuit to its left answers first.

Method: Roslyn syntax: `when` guards on case labels and switch-expression arms, read for a mutation (`++`/`--`/assignment) sitting in a position the guard's own `&&`/`||`/`??`/`?:`/`?.` can skip. Deterministic, provable per finding. Advisory.

Do you agree with this assessment?

X22 · Contradicted release guard10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a method that TAKES a lock or semaphore and gives it back from a flag-guarded `finally` returns the value that flag implies — reporting success while the guard hands the primitive back admits a second caller the exclusion was there to keep out, and reporting failure while the guard keeps it leaves nothing to ever give it back.

Method: Roslyn syntax: `try` statements whose `finally` releases a synchronisation primitive under a bare local-bool guard, where the method also TOOK that same primitive before the `try`, checked for a `return` of a bool literal whose value disagrees with the flag state the method's own straight-line assignments put it in. Deterministic, provable per finding. Advisory.

Do you agree with this assessment?

X23 · Unguarded diagnostic materialisation10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether the work a diagnostic log line costs is paid only when that line is wanted — C# evaluates a call's arguments BEFORE the call, so a trace/debug message joined or projected out of a collection is built in full on every pass, and then discarded by a sink the shipped configuration leaves switched off.

Method: Roslyn syntax: log calls at a diagnostic level (a `Log`-prefixed method naming Trace/Debug/Verbose, or a bare `Debug`/`Trace`/`Verbose` on a receiver named for a logger), whose argument list is read for a call whose cost scales with a sequence — a LINQ operator, a materialisation, `string.Join`, a serializer — with no enclosing level check or conditional-compilation region. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `debug`/`trace`/`verbose` call on a receiver named for a logger, or a `log`-prefixed method naming the level, whose argument calls an array operator (`map`/`filter`/`reduce`/`sort`/…), `Array.from`, `Object.keys/values/entries`, `JSON.stringify`/`util.inspect` over anything but a literal, or an array `join` — outside any arrow or function passed as an argument, which the logger calls only when the level is on — with no enclosing `if`, `&&` or `?:` whose condition names a level, a level string, or the `NODE_ENV`/`__DEV__`/`DEV` build switch. Deterministic, provable per finding. Advisory.

Do you agree with this assessment?

X24 · Document value interpolated into markup unescaped10.0 / 10Exemplary○ Nothing flagged

Other · Security — Whether text read out of the document being converted is escaped before it is written into generated markup — a value the document's author chose, interpolated into an attribute the surrounding literal delimits, can close that attribute and open another.

Method: Roslyn semantic model over the whole compilation: a string-typed `Value`/`InnerText`/`InnerXml`/`Text` member declared inside `DocumentFormat.OpenXml` or `System.Xml` is a taint SOURCE, propagated through assignments, returns, arguments, tuple elements and string composition to its transitive closure, then read at interpolated-string holes that sit in a markup position the surrounding literal itself delimits. Escaper/encoder calls and enclosing validator conditions cut the flow. Flow- and container-insensitive by construction. A second arm needs no provenance at all and reports a type that CONTRADICTS ITSELF — the same expression escaped at one delimited markup hole and interpolated raw at another hole in the same markup position of the same type, which the type's own escaping proves is a defect without knowing where the value came from. On a repository with no .NET source it reads JavaScript/TypeScript off the token stream with the same rule: a DOM read of raw document text (`getAttribute`, `textContent`, `innerText`, `nodeValue`) is the source, propagated through local bindings and string composition, and judged at template-literal and concatenation holes in the same two delimited markup positions; escapers and validating conditions cut it, and documentation-site, test, vendored and minified scripts are not read. Deterministic, provable per finding. Advisory.

Do you agree with this assessment?

X25 · Inert configuration knob10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a value the caller is invited to supply is the value the type actually uses — a constructor parameter stored in a private field that nothing ever reads while the default it was given is spelled out a second time at the site that should have read it, a keyed lookup that falls back to a different setting than the one its key names while the same type falls back to the matching one for that same key, or a culture-sensitive parse given no format provider by a type that feeds its own settable culture to the same kind of parse elsewhere, or a number an entry point writes to standard output under the host's culture while the same entry point formats with the invariant culture elsewhere. Either way, every caller who supplies a value silently gets something else.

Method: Roslyn syntax: private instance fields of a non-partial type assigned in a constructor from one of its own parameters with a `??` fallback, checked for whether anything in the type body reads the field and whether that same fallback expression is spelled out again outside the constructor; and `??` fallbacks onto a member access from a lookup call carrying exactly one string literal, grouped by that key across the type and checked for a fallback member whose folded name disagrees with the key while a sibling site for the same key agrees with it. On a repository with no .NET source the first two arms read JavaScript/TypeScript off the engine’s own token stream (tests included, bundles and vendored paths not): a `#x`, `private` or `private` parameter-property instance field filled in the constructor from a parameter (or one member of one) through `??`/`||` or a parameter default, never read anywhere in the file by name, whose constructed default is spelled again in the class body; and `lookup("key") ?? s.member` grouped by key per class, or per module outside every class. The culture arm has no JavaScript counterpart: its parses take no locale. Deterministic, provable per finding. Advisory.

Do you agree with this assessment?

X26 · Unsynchronised callback handoff10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a value handed from a callback to the body that waits on it crosses on something built to be crossed — a `Queue<T>`/`List<T>`/`Dictionary<K,V>` written inside an event handler and read back outside it is mutated by two flows at once, and the semaphore or completion source beside it orders how MANY items exist while leaving the collection's own head, tail and backing array unprotected.

Method: Roslyn syntax: method, accessor, local-function and lambda bodies that declare BOTH a non-thread-safe generic collection (`Queue`/`Stack`/`List`/`Dictionary`/`HashSet`/`Sorted*`/`LinkedList`) and a synchronisation primitive (`SemaphoreSlim`/`TaskCompletionSource`/`ManualResetEvent(Slim)`/`AutoResetEvent`/`CountdownEvent`) as locals, then read for a `+=`-registered lambda that raises that primitive while the body outside every lambda waits on it — and, in that scope, a mutating call on the collection inside the lambda paired with a mention of it outside. Any `lock` in the scope abstains it. On a repository with no .NET source the same handoff is read in Java off the engine’s own token stream (test source sets, vendored and demonstration paths not): an `ArrayList`/`LinkedList`/`ArrayDeque`/`PriorityQueue`/`Hash*`/`LinkedHash*`/`Tree*` local and a `CountDownLatch`/`Semaphore`/`CompletableFuture` local, a lambda or anonymous class that raises the primitive and mutates the collection, and a wait outside it; any `synchronized` or `lock()` abstains the body. Because each of those primitives orders what the callback wrote before raising it, only a touch that provably overlaps the callback is convicted: one after the registration and before the next wait, or one in a loop registered-before, waiting on every pass and not declaring the collection. Deterministic, provable per finding. Advisory.

Do you agree with this assessment?

X27 · Collection changed while being enumerated10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether an enhanced `for` leaves the collection it is walking alone — a body that adds to or removes from the very collection the loop is iterating invalidates the fail-fast iterator it is holding, so the next `next()` throws `ConcurrentModificationException` and the remaining elements are never seen. Whether a `for (x in c)` or `c.forEach { … }` leaves the collection it is walking alone — a `mutableListOf`/`ArrayList`, `mutableMapOf`/`HashMap` or `mutableSetOf`/`HashSet` is a `java.util` collection on the JVM and is walked by its own fail-fast iterator, so a body that adds to or removes from the very collection the loop is walking makes the next step throw `ConcurrentModificationException` and the remaining elements are never seen.

Method: Roslyn syntax + semantics: `foreach` statements whose body calls a structural mutator (`Add`/`Remove`/`Clear`/`Insert`/…) on the very expression the loop is enumerating. Two arms. ARM A — the source is a concrete fragile BCL collection, or a live `Keys`/`Values` view over one, and the mutator resolves to that same collection's own member; concurrent and immutable collections and arrays are outside the population by construction, since their enumerators survive a structural change. ARM B — the source is an argument-less accessor CALL on a receiver whose body is in source: the accessor must return a stored field VERBATIM and a sibling member must structurally change that same field, both read off the implementations rather than from the members' names. A mutation the loop provably exits immediately after (`break`/`return`/`throw`/`goto`), or one written inside a nested loop or a lambda, is counted and never reported. Deterministic, provable per finding. Advisory.

Do you agree with this assessment?

X28 · Index access outside its own emptiness guard10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a condition that tests a value for emptiness indexes that same value only where the test holds — an `||` written one parenthesis too far to the left leaves an index access outside the guard beside it, so the empty case the guard exists to anticipate reaches the index and throws.

Method: Roslyn syntax only, no semantic model: the OUTERMOST `&&`/`||` of every boolean condition, read for a symbol the condition tests for emptiness (`string.IsNullOrEmpty`/`IsNullOrWhiteSpace`, a `Length`/`Count` comparison against a literal, `Any()`, a `Length`/`Count` pattern, or a comparison against `""`) and ALSO indexes. Each `symbol[...]` access is placed by a boolean-reachability walk from the access up to the outermost connective: an access is COVERED when some enclosing step has it in the right operand and the left operand, under the truth value that step forces, proves the symbol non-empty — a recursion over `&&`/`||` whose true- and false-directions are asymmetric. A finding needs BOTH an uncovered access and a covered one on the same symbol in the same condition, which is the agreeing twin that separates a misplaced parenthesis from an unrelated length test. Bare index accesses with no emptiness test in the condition are neither counted nor reported; a non-identifier receiver and a lambda nested inside the condition are outside the population. Deterministic, provable per finding. Advisory.

Do you agree with this assessment?

X29 · Per-element action decided by a fixed element10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a decision taken once per element is taken ABOUT that element — a test inside a counted loop that reads a fixed subscript of the very collection its guarded statement indexes by the loop variable applies element zero's answer to all of them, so the elements that differ from it are all handled wrongly, and in the same direction.

Method: Roslyn syntax only, no semantic model: every `for` statement declaring exactly ONE loop variable, and every `if` inside its body that is not under a nested loop or a lambda. A site enters the population when the `if`’s condition never mentions the loop variable while the statement it guards indexes some collection by that variable ALONE (`c[i]`; `c[i + 1]` and `c[i, j]` are outside it). A finding additionally needs the AGREEING TWIN at the same-collection grain: the condition must read THAT SAME collection at a subscript that does not move — written into the condition, or reached through a local declared BEFORE the loop, so an alias bound inside the body is not followed. Both collection expressions must be simple identifiers. On a repository with no .NET source the same rule reads JavaScript/TypeScript off the engine’s own token stream (tests included, bundles and vendored paths not): a `for (let|var|const x = …; …; …)` with one declarator and a braced body, an alias followed only when it is declared before the loop in a block that encloses it and never assigned inside the loop. Deterministic, provable per finding. Advisory.

Do you agree with this assessment?

X3 · Exception handling5.3 / 10Adequate✓ Tool-verified

Other · Code Health — Whether exceptions are handled rather than silently swallowed or rethrown with lost stack traces.

Method: Roslyn syntax scan: every catch clause counted; empty catches and bare rethrows flagged. Population is all catch clauses, not estimated. Deterministic, hard fact.

`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. (×6) — workspace-import/src/com/jetbrains/ls/imports/java/JavaRunCommands.kt:163, workspace-import/src/com/jetbrains/ls/imports/gradle/GradleToolingApiHelper.kt:353, workspace-import/src/com/jetbrains/ls/imports/gradle/GradleToolingApiHelper.kt:362, …
`catch (Throwable)` 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. (×3) — workspace-import/gradle-plugin/src/com/jetbrains/ls/imports/gradle/utils/SourceSetArtifactExtractor.java:52, workspace-import/gradle-plugin/src/com/jetbrains/ls/imports/gradle/model/builder/KotlinVersionReflectiveUtils.java:30, workspace-import/gradle-plugin/src/com/jetbrains/ls/imports/gradle/model/builder/KotlinVersionReflectiveUtils.java:49
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. (×5) — workspace-import/gradle-plugin/src/com/jetbrains/ls/imports/gradle/model/builder/KotlinMetadataModelBuilder.java:172, workspace-import/gradle-plugin/src/com/jetbrains/ls/imports/gradle/model/builder/ModuleSourceSetsModelBuilder.kt:154, vscode-extension-core/src/intellijExtensions.ts:272, …
`.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:105
`.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

What to do

Swallowed exception (caught, then discarded)

Do you agree with this assessment?

X30 · Support guard that admits what it rejects10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a guard written as a NEGATED `||` says what its author meant — `!(a || b || x != k)` is `!a && !b && x == k` by De Morgan, so a bail-out that mixes capabilities the code needs with a fault it refuses turns inside out: it fires only where the capabilities are ABSENT, and lets every value the fault term names walk straight into the body that cannot handle it.

Method: Roslyn syntax only, no semantic model: every logical-not whose operand is a parenthesised `||` chain of two or more disjuncts, flattened (a left-nested `a || b || c` read once would see `(a || b)` as one disjunct). A site enters the population on that shape alone. A finding additionally needs the disjuncts to DISAGREE in polarity: at least one bare boolean read — an identifier or member access, never an invocation, which is a predicate rather than a capability flag — and at least one `x != <constant>`, the only form that negates into an exact-value pin (`== null` negates into a looser requirement and is outside the fault set). Consistently-polarised disjunctions, all-fault or all-capability, are counted and never reported; a negated `&&` is outside the population entirely. No same-receiver gate: it was measured to cost a real defect and remove no false positive. Deterministic, provable per finding. Advisory.

Do you agree with this assessment?

X5 · Nullable reference types9.9 / 10Exemplary✓ Tool-verified

Other · Code Health — Whether Kotlin's null safety is not undermined by not-null assertions — `String` cannot hold null and `String?` must be checked before use in every Kotlin module, and each `!!` is a run-time `NullPointerException` the author has told the compiler cannot happen.

Method: Roslyn compiler-options scan: NullableContextOptions per project; null-forgiving (!) suppression density per 1k syntax nodes. Deterministic, adoption plus suppression penalty.

Do you agree with this assessment?

Reference — by lens

The score is the rank-weighted fold of these lenses (worst-heaviest), each including its meta-dimensions; a lens with a Critical contributor is capped at Fair (its band reads "gated by …") and is never the strongest area however high its average.

Lens	Score	Rating	Impact
Code Health	77%	Strong	Solid.
Architecture	62%	Adequate — gated by AX7	Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Maturity	59%	Adequate — gated by M2	Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Readiness	45%	Weak — gated by P1, P3	Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Security	100%	Exemplary	Strongest area.
Performance	61%	Adequate	Acceptable, with room to improve.

Unscored — 3 check(s) recorded observations but carry no score

These checks ran and found something, but they do not carry a score — either by design (an advisory check reports evidence rather than grading it) or because they could not be scored here. They are excluded from the score for that reason, not because there was nothing to see.

SC1 Supply-chain hygiene — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X10 Duplicated predicate — 5 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
X7 Silent fallback defaults — 2 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

These checks grade a working control, and the repository shows no evidence of one. That is deliberately not scored as a zero: a repository cannot show an ops runbook, a database TTL or an infrastructure-side audit log, so absence of evidence here is not evidence the control is missing. It is also not a statement that the check is irrelevant to this codebase — the thing it grades applies; we just could not see it. Excluded from the score either way.

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 — 59 check(s) not relevant to this codebase

These checks had nothing to measure here (no tests, no git history, the codebase is small, or the architecture style doesn't apply), so they're omitted above rather than scored low.

AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
AC7 A11y enforcement — No web markup found — accessibility is not applicable to this repository.
AX1 Captive dependencies — 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
AX2 Stateful singletons — No container singleton was found, so there is no shared instance for concurrent requests to race on. No class in this Java code is a Spring, JSR-330 or CDI singleton bean. 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)
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 — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
C1 Data Protection — No personal data detected in 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 — Not scored — 70 Maven/Gradle manifest(s) were read, stating a version for 67 dependency(ies) and leaving 1 to a parent or an imported BOM, but no build resolved the dependency graph, so the outdated signal was not established. NOT a finding that these dependencies are current or healthy.
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 — Naming consistency is measured on C# only; Java, JavaScript, Kotlin, Swift, TypeScript not measured.
D22 Internal API Consistency — The exposed public-API surface could not be collected — no C#/VB projects loaded.
D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ projects each declaring an entity of their own. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
D24 Comment Value — D24 reads C# and Visual Basic comments only — this repository's production source is .java, .kt, .ts, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
D25 ADR Conformance — no ADRs to check
D26 Project Cohesion — D26 measured no build unit over this repository's .java, .kt source. Not scored: this is a gap in the analyzer, not a verdict about this repository.
D27 Navigability — D27 counts a call into the standard library or a dependency as unresolved for this repository's language (.kt), so too few call sites counted as resolved to assess navigability. 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) — 118 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.
D39 IL Efficiency — D39 measures the IL emitted by a .NET build; this repository has no .NET solution or project files, so the dimension does not apply.
D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
D7 Architectural Integrity — no checkable ADRs, and no 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): 66 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
P2 Observability — This repository's JVM, JavaScript/TypeScript source (6 module(s), 386 file(s) read) declares no entry point and bootstraps no server, and nothing here deploys a service — it is a library, run inside whatever hosts it, so production observability (structured logging, tracing/metrics, health checks) is N/A. If it grows a binary or a service, the dimension reactivates.
P7 Outbound HTTP resilience — not 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 — no coverage report found on disk — produce a coverage report in a standard format (JaCoCo XML — `mvn jacoco:report` or the Gradle `jacocoTestReport` task) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures, or wire coverage collection into CI, to enable this cross-layer check
PF1 Benchmark discipline — 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.
R11 Import Boundaries — No recognizable feature-sliced/layered src layout — boundary rules not applicable.
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.
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)

The findings behind the scores, grouped by severity, then by dimension and kind. The high-severity issues are enumerated in full below; items per group are capped at 25 with any overflow stated explicitly per group, never silently truncated. The complete machine-readable list of every finding (all severities) is the companion findings.md in this report's bundle.

Critical — 11 finding(s)

D35 · Change Coupling · Boundary-crossing change coupling · ×9

Boundary-crossing change coupling: LSSimpleCodeActionProvider.kt ↔ LSKotlinIntentionCodeActionProvider.kt api.features/src/com/jetbrains/ls/api/features/codeActions/LSSimpleCodeActionProvider.kt:1 — `api.features/src/com/jetbrains/ls/api/features/codeActions/LSSimpleCodeActionProvider.kt` (context api.features) and `features-impl/kotlin/src/com/jetbrains/ls/api/features/impl/kotlin/diagnostics/intentions/LSKotlinIntentionCodeActionProvider.kt` (context features-impl) sit in DIFFERENT parts of the tree yet change together 70% of the time (7 of the 10 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 7 shared commits counted here, the most recent 3 are `4089b84c` [Analyzer] LSP-480 Change API to support file settings configuration; `22a992b1` cleanup [lsp]: replace `file` with `virtualFile` for clarity in varia… (at that commit the file was still `features-impl/kotlin/src/com/jetbrains/ls/api/features/impl/common/kotlin/diagnostics/intentions/LSKotlinIntentionCodeActionProvider.kt`); `06b47afa` cleanup [lsp]: access function `LSServer#withAnalysisContext` from co… (at that commit the file was still `features-impl/kotlin/src/com/jetbrains/ls/api/features/impl/common/kotlin/diagnostics/intentions/LSKotlinIntentionCodeActionProvider.kt`) — run `git show` on any of them.
Boundary-crossing change coupling: LSSimpleCodeActionProvider.kt ↔ LSKotlinCompilerDiagnosticsFixesCodeActionProvider.kt api.features/src/com/jetbrains/ls/api/features/codeActions/LSSimpleCodeActionProvider.kt:1 — `api.features/src/com/jetbrains/ls/api/features/codeActions/LSSimpleCodeActionProvider.kt` (context api.features) and `features-impl/kotlin/src/com/jetbrains/ls/api/features/impl/kotlin/diagnostics/compiler/LSKotlinCompilerDiagnosticsFixesCodeActionProvider.kt` (context features-impl) sit in DIFFERENT parts of the tree yet change together 70% of the time (7 of the 10 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 7 shared commits counted here, the most recent 3 are `4089b84c` [Analyzer] LSP-480 Change API to support file settings configuration; `22a992b1` cleanup [lsp]: replace `file` with `virtualFile` for clarity in varia… (at that commit the file was still `features-impl/kotlin/src/com/jetbrains/ls/api/features/impl/common/kotlin/diagnostics/compiler/LSKotlinCompilerDiagnosticsFixesCodeActionProvider.kt`); `06b47afa` cleanup [lsp]: access function `LSServer#withAnalysisContext` from co… (at that commit the file was still `features-impl/kotlin/src/com/jetbrains/ls/api/features/impl/common/kotlin/diagnostics/compiler/LSKotlinCompilerDiagnosticsFixesCodeActionProvider.kt`) — run `git show` on any of them.
Boundary-crossing change coupling: LSSimpleCodeActionProvider.kt ↔ LSKotlinCompilerDiagnosticsProvider.kt api.features/src/com/jetbrains/ls/api/features/codeActions/LSSimpleCodeActionProvider.kt:1 — `api.features/src/com/jetbrains/ls/api/features/codeActions/LSSimpleCodeActionProvider.kt` (context api.features) and `features-impl/kotlin/src/com/jetbrains/ls/api/features/impl/kotlin/diagnostics/compiler/LSKotlinCompilerDiagnosticsProvider.kt` (context features-impl) sit in DIFFERENT parts of the tree yet change together 60% of the time (6 of the 10 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 6 shared commits counted here, the most recent 3 are `4089b84c` [Analyzer] LSP-480 Change API to support file settings configuration; `22a992b1` cleanup [lsp]: replace `file` with `virtualFile` for clarity in varia… (at that commit the file was still `features-impl/kotlin/src/com/jetbrains/ls/api/features/impl/common/kotlin/diagnostics/compiler/LSKotlinCompilerDiagnosticsProvider.kt`); `06b47afa` cleanup [lsp]: access function `LSServer#withAnalysisContext` from co… (at that commit the file was still `features-impl/kotlin/src/com/jetbrains/ls/api/features/impl/common/kotlin/diagnostics/compiler/LSKotlinCompilerDiagnosticsProvider.kt`) — run `git show` on any of them.
Boundary-crossing change coupling: LSSimpleCodeActionProvider.kt ↔ LSCommonInspectionDiagnosticProvider.kt api.features/src/com/jetbrains/ls/api/features/codeActions/LSSimpleCodeActionProvider.kt:1 — `api.features/src/com/jetbrains/ls/api/features/codeActions/LSSimpleCodeActionProvider.kt` (context api.features) and `features-impl/common/src/com/jetbrains/ls/api/features/impl/common/diagnostics/LSCommonInspectionDiagnosticProvider.kt` (context features-impl) sit in DIFFERENT parts of the tree yet change together 60% of the time (6 of the 10 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 6 shared commits counted here, the most recent 3 are `4089b84c` [Analyzer] LSP-480 Change API to support file settings configuration; `22a992b1` cleanup [lsp]: replace `file` with `virtualFile` for clarity in varia… (at that commit the file was still `features-impl/common/src/com/jetbrains/ls/api/features/impl/common/diagnostics/inspections/LSCommonInspectionDiagnosticProvider.kt`); `06b47afa` cleanup [lsp]: access function `LSServer#withAnalysisContext` from co… (at that commit the file was still `features-impl/common/src/com/jetbrains/ls/api/features/impl/common/diagnostics/inspections/LSCommonInspectionDiagnosticProvider.kt`) — run `git show` on any of them.
Boundary-crossing change coupling: LSSimpleCodeActionProvider.kt ↔ LSCommonSyntaxErrorDiagnosticProvider.kt api.features/src/com/jetbrains/ls/api/features/codeActions/LSSimpleCodeActionProvider.kt:1 — `api.features/src/com/jetbrains/ls/api/features/codeActions/LSSimpleCodeActionProvider.kt` (context api.features) and `features-impl/common/src/com/jetbrains/ls/api/features/impl/common/diagnostics/LSCommonSyntaxErrorDiagnosticProvider.kt` (context features-impl) sit in DIFFERENT parts of the tree yet change together 60% of the time (6 of the 10 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 6 shared commits counted here, the most recent 3 are `4089b84c` [Analyzer] LSP-480 Change API to support file settings configuration; `22a992b1` cleanup [lsp]: replace `file` with `virtualFile` for clarity in varia… (at that commit the file was still `features-impl/common/src/com/jetbrains/ls/api/features/impl/common/diagnostics/LSSyntaxErrorDiagnosticProvider.kt`); `06b47afa` cleanup [lsp]: access function `LSServer#withAnalysisContext` from co… (at that commit the file was still `features-impl/common/src/com/jetbrains/ls/api/features/impl/common/diagnostics/LSSyntaxErrorDiagnosticProvider.kt`) — run `git show` on any of them.
Boundary-crossing change coupling: LSSimpleCodeActionProvider.kt ↔ LSKotlinPackageDefinitionProvider.kt api.features/src/com/jetbrains/ls/api/features/codeActions/LSSimpleCodeActionProvider.kt:1 — `api.features/src/com/jetbrains/ls/api/features/codeActions/LSSimpleCodeActionProvider.kt` (context api.features) and `features-impl/kotlin/src/com/jetbrains/ls/api/features/impl/kotlin/definitions/LSKotlinPackageDefinitionProvider.kt` (context features-impl) sit in DIFFERENT parts of the tree yet change together 50% of the time (5 of the 10 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 5 shared commits counted here, the most recent 3 are `22a992b1` cleanup [lsp]: replace `file` with `virtualFile` for clarity in varia… (at that commit the file was still `features-impl/kotlin/src/com/jetbrains/ls/api/features/impl/common/kotlin/definitions/LSKotlinPackageDefinitionProvider.kt`); `06b47afa` cleanup [lsp]: access function `LSServer#withAnalysisContext` from co… (at that commit the file was still `features-impl/kotlin/src/com/jetbrains/ls/api/features/impl/common/kotlin/definitions/LSKotlinPackageDefinitionProvider.kt`); `5bc427f1` [lsp] cleanup: migrate (almost) all usages of 'runReadAction {}' to '… (at that commit the file was still `features-impl/kotlin/src/com/jetbrains/ls/api/features/impl/common/kotlin/definitions/LSKotlinPackageDefinitionProvider.kt`) — run `git show` on any of them.
Boundary-crossing change coupling: LSSimpleCodeActionProvider.kt ↔ LSKotlinSemanticTokensProvider.kt api.features/src/com/jetbrains/ls/api/features/codeActions/LSSimpleCodeActionProvider.kt:1 — `api.features/src/com/jetbrains/ls/api/features/codeActions/LSSimpleCodeActionProvider.kt` (context api.features) and `features-impl/kotlin/src/com/jetbrains/ls/api/features/impl/kotlin/semanticTokens/LSKotlinSemanticTokensProvider.kt` (context features-impl) sit in DIFFERENT parts of the tree yet change together 50% of the time (5 of the 10 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 5 shared commits counted here, the most recent 3 are `22a992b1` cleanup [lsp]: replace `file` with `virtualFile` for clarity in varia… (at that commit the file was still `features-impl/kotlin/src/com/jetbrains/ls/api/features/impl/common/kotlin/semanticTokens/LSKotlinSemanticTokensProvider.kt`); `06b47afa` cleanup [lsp]: access function `LSServer#withAnalysisContext` from co… (at that commit the file was still `features-impl/kotlin/src/com/jetbrains/ls/api/features/impl/common/kotlin/semanticTokens/LSKotlinSemanticTokensProvider.kt`); `5bc427f1` [lsp] cleanup: migrate (almost) all usages of 'runReadAction {}' to '… (at that commit the file was still `features-impl/kotlin/src/com/jetbrains/ls/api/features/impl/common/kotlin/semanticTokens/LSSemanticTokensProviderKotlinImpl.kt`) — run `git show` on any of them.
Boundary-crossing change coupling: LSSimpleCodeActionProvider.kt ↔ LSCommonReferencesProvider.kt api.features/src/com/jetbrains/ls/api/features/codeActions/LSSimpleCodeActionProvider.kt:1 — `api.features/src/com/jetbrains/ls/api/features/codeActions/LSSimpleCodeActionProvider.kt` (context api.features) and `features-impl/common/src/com/jetbrains/ls/api/features/impl/common/references/LSCommonReferencesProvider.kt` (context features-impl) sit in DIFFERENT parts of the tree yet change together 50% of the time (5 of the 10 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 5 shared commits counted here, the most recent 3 are `22a992b1` cleanup [lsp]: replace `file` with `virtualFile` for clarity in varia…; `06b47afa` cleanup [lsp]: access function `LSServer#withAnalysisContext` from co…; `5bc427f1` [lsp] cleanup: migrate (almost) all usages of 'runReadAction {}' to '… (at that commit the file was still `features-impl/common/src/com/jetbrains/ls/api/features/impl/common/references/LSReferencesProviderCommonImpl.kt`) — run `git show` on any of them.
Boundary-crossing change coupling: LSSimpleCodeActionProvider.kt ↔ LSCommonDefinitionProvider.kt api.features/src/com/jetbrains/ls/api/features/codeActions/LSSimpleCodeActionProvider.kt:1 — `api.features/src/com/jetbrains/ls/api/features/codeActions/LSSimpleCodeActionProvider.kt` (context api.features) and `features-impl/common/src/com/jetbrains/ls/api/features/impl/common/definitions/LSCommonDefinitionProvider.kt` (context features-impl) sit in DIFFERENT parts of the tree yet change together 50% of the time (5 of the 10 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 5 shared commits counted here, the most recent 3 are `22a992b1` cleanup [lsp]: replace `file` with `virtualFile` for clarity in varia…; `06b47afa` cleanup [lsp]: access function `LSServer#withAnalysisContext` from co…; `5bc427f1` [lsp] cleanup: migrate (almost) all usages of 'runReadAction {}' to '… (at that commit the file was still `features-impl/common/src/com/jetbrains/ls/api/features/impl/common/definitions/LSDefinitionProviderCommonImpl.kt`) — run `git show` on any of them.

R8 · Dependency Hygiene · Unlisted import 'ts-checker-rspack-plugin' · ×1

Unlisted import 'ts-checker-rspack-plugin' kotlin-vscode/rspack.base.config.ts:3 — Imported but not declared in any reachable package.json — installs work only by hoisting accident.

R9 · Circular Imports · Import cycle (2 files) · ×1

Import cycle (2 files) vscode-extension-core/src/buildTask.ts:35 — 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 10 files)

Serious — 186 finding(s)

AX7 · Slice cohesion · Cross-slice coupling · ×30

Cross-slice coupling: codeActions → commands api.features/src/com/jetbrains/ls/api/features/codeActions/LSSimpleCodeActionProvider.kt:78 — `LSSimpleCodeActionProvider` (slice 'codeActions') depends on `LSCommandDescriptor` from slice 'commands'.
Cross-slice coupling: resolve → configuration api.features/src/com/jetbrains/ls/api/features/resolve/ResolveDataWithConfigurationEntryId.kt:10 — `ResolveDataWithConfigurationEntryId` (slice 'resolve') depends on `UniqueId` from slice 'configuration'.
Cross-slice coupling: impl → configuration features-impl/common/src/com/jetbrains/ls/api/features/impl/common/callHierarchy/LSCallHierarchyProviderBase.kt:127 — `CallHierarchyItemData` (slice 'impl') depends on `UniqueId` from slice 'configuration'.
Cross-slice coupling: impl → utils features-impl/common/src/com/jetbrains/ls/api/features/impl/common/callHierarchy/LSCallHierarchyProviderBase.kt:150 — `NameData` (slice 'impl') depends on `PsiSerializablePointer` from slice 'utils'.
Cross-slice coupling: impl → utils features-impl/common/src/com/jetbrains/ls/api/features/impl/common/callHierarchy/LSCallHierarchyProviderBase.kt:153 — `ClassNameData` (slice 'impl') depends on `PsiSerializablePointer` from slice 'utils'.
Cross-slice coupling: impl → utils features-impl/common/src/com/jetbrains/ls/api/features/impl/common/callHierarchy/LSCallHierarchyProviderBase.kt:165 — `MethodNameData` (slice 'impl') depends on `PsiSerializablePointer` from slice 'utils'.
Cross-slice coupling: impl → utils features-impl/common/src/com/jetbrains/ls/api/features/impl/common/callHierarchy/LSCallHierarchyProviderBase.kt:172 — `FieldNameData` (slice 'impl') depends on `PsiSerializablePointer` from slice 'utils'.
Cross-slice coupling: impl → language features-impl/common/src/com/jetbrains/ls/api/features/impl/common/completion/LSCompletionProviderHelper.kt:71 — `LSCompletionProviderHelper` (slice 'impl') depends on `LSLanguage` from slice 'language'.
Cross-slice coupling: impl → language features-impl/common/src/com/jetbrains/ls/api/features/impl/common/completion/LSCompletionProviderHelper.kt:342 — `CompletionCandidate` (slice 'impl') depends on `LSLanguage` from slice 'language'.
Cross-slice coupling: impl → language features-impl/common/src/com/jetbrains/ls/api/features/impl/common/configuration/LSCommonConfiguration.kt:23 — `LSCommonConfigurationKt` (slice 'impl') depends on `LSConfigurationPiece` from slice 'language'.
Cross-slice coupling: impl → language features-impl/common/src/com/jetbrains/ls/api/features/impl/common/configuration/LSCommonServerExtension.kt:8 — `LSCommonServerExtension` (slice 'impl') depends on `LSConfigurationPiece` from slice 'language'.
Cross-slice coupling: impl → commands features-impl/common/src/com/jetbrains/ls/api/features/impl/common/decompiler/LSDecompileCommandDescriptorProvider.kt:22 — `LSDecompileCommandDescriptorProvider` (slice 'impl') depends on `LSCommandDescriptor` from slice 'commands'.
Cross-slice coupling: impl → commands features-impl/common/src/com/jetbrains/ls/api/features/impl/common/fileTemplates/LSInterpolateFileTemplateCommandDescriptorProvider.kt:35 — `LSInterpolateFileTemplateCommandDescriptorProvider` (slice 'impl') depends on `LSCommandDescriptor` from slice 'commands'.
Cross-slice coupling: impl → configuration features-impl/common/src/com/jetbrains/ls/api/features/impl/common/inlayHints/LSInlayHintsProviderBase.kt:70 — `LSInlayHintsProviderBase` (slice 'impl') depends on `UniqueId` from slice 'configuration'.
Cross-slice coupling: impl → utils features-impl/common/src/com/jetbrains/ls/api/features/impl/common/inlayHints/LSInlayHintsProviderBase.kt:480 — `PsiPointerInlayActionPayloadSerializable` (slice 'impl') depends on `PsiSerializablePointer` from slice 'utils'.
Cross-slice coupling: impl → configuration features-impl/common/src/com/jetbrains/ls/api/features/impl/common/inlayHints/LSInlayHintsProviderBase.kt:493 — `InlayHintResolveData` (slice 'impl') depends on `UniqueId` from slice 'configuration'.
Cross-slice coupling: impl → commands features-impl/common/src/com/jetbrains/ls/api/features/impl/common/modcommands/LSApplyFixCommandDescriptorProvider.kt:27 — `LSApplyFixCommandDescriptorProvider` (slice 'impl') depends on `LSCommandDescriptor` from slice 'commands'.
Cross-slice coupling: impl → semanticTokens features-impl/common/src/com/jetbrains/ls/api/features/impl/common/semanticTokens/LSHighlightingSemanticTokens.kt:52 — `Piece` (slice 'impl') depends on `LSSemanticTokenType` from slice 'semanticTokens'.
Cross-slice coupling: impl → language features-impl/java-base/src/com/jetbrains/ls/api/features/impl/javaBase/JavaBaseLanguageServerExtension.kt:8 — `JavaBaseLanguageServerExtension` (slice 'impl') depends on `LSConfigurationPiece` from slice 'language'.
Cross-slice coupling: impl → language features-impl/java-base/src/com/jetbrains/ls/api/features/impl/javaBase/LSJavaBaseLanguageConfiguration.kt:13 — `LSJavaBaseLanguageConfigurationKt` (slice 'impl') depends on `LSConfigurationPiece` from slice 'language'.
Cross-slice coupling: impl → language features-impl/java-base/src/com/jetbrains/ls/api/features/impl/javaBase/LSJavaLanguage.kt:7 — `LSJavaLanguageKt` (slice 'impl') depends on `LSLanguage` from slice 'language'.
Cross-slice coupling: impl → configuration features-impl/kotlin/src/com/jetbrains/ls/api/features/impl/kotlin/callHierarchy/LSKotlinCallHierarchyProvider.kt:30 — `LSKotlinCallHierarchyProvider` (slice 'impl') depends on `UniqueId` from slice 'configuration'.
Cross-slice coupling: impl → configuration features-impl/kotlin/src/com/jetbrains/ls/api/features/impl/kotlin/completion/LSKotlinCompletionProvider.kt:27 — `LSKotlinCompletionProvider` (slice 'impl') depends on `UniqueId` from slice 'configuration'.
Cross-slice coupling: impl → language features-impl/kotlin/src/com/jetbrains/ls/api/features/impl/kotlin/configuration/KotlinLanguageServerExtension.kt:8 — `KotlinLanguageServerExtension` (slice 'impl') depends on `LSConfigurationPiece` from slice 'language'.
Cross-slice coupling: impl → language features-impl/kotlin/src/com/jetbrains/ls/api/features/impl/kotlin/configuration/LSKotlinLanguageConfiguration.kt:70 — `LSKotlinLanguageConfigurationKt` (slice 'impl') depends on `LSConfigurationPiece` from slice 'language'.
+ 5 more in this group — see findings.md.

D17 · Explicit Debt · TodoComment · ×14

TodoComment workspace-import/test/test/com/jetbrains/ls/imports/GradleProjectImportTest.kt:99 — // TODO: Check that missing dependencies are reported — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment workspace-import/src/com/jetbrains/ls/imports/json/conversion.kt:248 — // TODO: Store relative paths where possible — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment vscode-extension-core/src/lspClient.ts:686 — // TODO drop fallback — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment features-impl/kotlin/src/com/jetbrains/ls/api/features/impl/kotlin/semanticTokens/LSKotlinSemanticTokensProvider.kt:117 — // todo should probably be implemented on the vscode side — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment features-impl/kotlin/src/com/jetbrains/ls/api/features/impl/kotlin/hover/LSKotlinMarkdownDocProvider.kt:17 — // TODO LSP-239 should be rendered as proper markdown
TodoComment features-impl/kotlin/psi/src/com/jetbrains/ls/api/features/impl/kotlin/psi/LSKotlinDocumentSymbolCustomizer.kt:76 — // TODO: Something more robust — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment features-impl/kotlin/psi/src/com/jetbrains/ls/api/features/impl/kotlin/psi/LSKotlinWorkspaceSymbolCustomizer.kt:44 — // TODO: Handle deprecated declarations. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment features-impl/common/src/com/jetbrains/ls/api/features/impl/common/modcommands/ModCommandData.kt:406 — // TODO: support ModEditOptions UI — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment features-impl/common/src/com/jetbrains/ls/api/features/impl/common/modcommands/ModCommandData.kt:450 — // TODO: check newtext equality, see how it's implemented in LSJavaCompletionProvider — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment features-impl/common/src/com/jetbrains/ls/api/features/impl/common/diagnostics/LSCommonIntentionFixesCodeActionProvider.kt:71 — // TODO(bartekpacia): centralize common logging so it's not repeated N times across all LS*Providers — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment api.features/src/com/jetbrains/ls/api/features/semanticTokens/LSSemanticTokens.kt:31 — // TODO LSP-236 send partial results here
TodoComment api.features/src/com/jetbrains/ls/api/features/diagnostics/LSDiagnosticProvider.kt:16 — // TODO LSP-237 handle other parts of `DocumentDiagnosticReport`
TodoComment api.features/src/com/jetbrains/ls/api/features/commands/document/LSDocumentCommandComandExecutor.kt:29 — // TODO LSP-235 handle errors during application
TodoComment api.features/src/com/jetbrains/ls/api/features/commands/document/LSDocumentCommandComandExecutor.kt:40 — // TODO we just need to return smth, not sure that the result is used — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.

PF3 · Async & latency hygiene · Sync-over-async blocking · ×9

Sync-over-async blocking vscode-extension-core/src/lspClient.ts:773 — `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.
Sync-over-async blocking vscode-extension-core/src/serverBundleDownload.ts:100 — `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.
Sync-over-async blocking vscode-extension-core/src/serverBundleDownload.ts:106 — `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.
Sync-over-async blocking vscode-extension-core/src/serverBundleDownload.ts:117 — `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.
Sync-over-async blocking vscode-extension-core/src/serverBundleDownload.ts:121 — `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.
Sync-over-async blocking vscode-extension-core/src/serverBundleDownload.ts:129 — `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.
Sync-over-async blocking vscode-extension-core/src/serverBundleDownload.ts:144 — `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.
Sync-over-async blocking vscode-extension-core/src/serverBundleDownload.ts:162 — `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.
Sync-over-async blocking vscode-extension-core/src/serverBundleDownload.ts:362 — `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.

X3 · Exception handling · Swallowed exception (caught, then discarded) · ×9

Swallowed exception (caught, then discarded) workspace-import/src/com/jetbrains/ls/imports/java/JavaRunCommands.kt:163 — `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.
Swallowed exception (caught, then discarded) workspace-import/src/com/jetbrains/ls/imports/gradle/GradleToolingApiHelper.kt:353 — `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.
Swallowed exception (caught, then discarded) workspace-import/src/com/jetbrains/ls/imports/gradle/GradleToolingApiHelper.kt:362 — `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.
Swallowed exception (caught, then discarded) workspace-import/src/com/jetbrains/ls/imports/gradle/GradleToolingApiHelper.kt:396 — `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.
Swallowed exception (caught, then discarded) workspace-import/gradle-plugin/src/com/jetbrains/ls/imports/gradle/utils/SourceSetArtifactExtractor.java:52 — `catch (Throwable)` 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.
Swallowed exception (caught, then discarded) workspace-import/gradle-plugin/src/com/jetbrains/ls/imports/gradle/model/builder/KotlinVersionReflectiveUtils.java:30 — `catch (Throwable)` 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.
Swallowed exception (caught, then discarded) workspace-import/gradle-plugin/src/com/jetbrains/ls/imports/gradle/model/builder/KotlinVersionReflectiveUtils.java:49 — `catch (Throwable)` 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.
Swallowed exception (caught, then discarded) workspace-import/gradle-plugin/src/com/jetbrains/ls/imports/gradle/model/builder/KotlinMultiplatformModelBuilder.kt:252 — `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.
Swallowed exception (caught, then discarded) features-impl/kotlin/src/com/jetbrains/ls/api/features/impl/kotlin/typeHierarchy/LSKotlinTypeHierarchyProvider.kt:395 — `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.

D3 · God Classes · FileTooLong · ×8

FileTooLong: kotlin/keyHandler.ts vscode-language-kotlin/src/kotlin/keyHandler.ts — FileTooLong — 1203 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 703 over it, 2.41× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: src/lspClient.ts vscode-extension-core/src/lspClient.ts — FileTooLong — 902 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 402 over it, 1.80× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: src/keyHandlerUtils.ts vscode-extension-core/src/keyHandlerUtils.ts — FileTooLong — 760 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 260 over it, 1.52× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: src/serverBundleDownload.ts vscode-extension-core/src/serverBundleDownload.ts — FileTooLong — 617 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 117 over it, 1.23× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: jps/JpsBuildTool.kt workspace-import/src/com/jetbrains/ls/imports/jps/JpsBuildTool.kt — FileTooLong — 598 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 98 over it, 1.20× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: maven/converter.kt workspace-import/maven-plugin/src/com/jetbrains/ls/imports/maven/converter.kt — FileTooLong — 540 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 40 over it, 1.08× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: modcommands/ModCommandData.kt features-impl/common/src/com/jetbrains/ls/api/features/impl/common/modcommands/ModCommandData.kt — FileTooLong — 523 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 23 over it, 1.05× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: json/conversion.kt workspace-import/src/com/jetbrains/ls/imports/json/conversion.kt — FileTooLong — 501 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 1 over it, 1.00× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.

D35 · Change Coupling · Change coupling · ×8

Change coupling: ModuleSourceSetImpl.kt ↔ IdeaProjectMapper.kt workspace-import/gradle-plugin/src/com/jetbrains/ls/imports/gradle/model/impl/ModuleSourceSetImpl.kt:1 — `workspace-import/gradle-plugin/src/com/jetbrains/ls/imports/gradle/model/impl/ModuleSourceSetImpl.kt` and `workspace-import/src/com/jetbrains/ls/imports/gradle/IdeaProjectMapper.kt` change together 90% of the time (9 of the 10 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 9 shared commits counted here, the most recent 3 are `77d91e13` [gradle][LSP-1698] Converted ModuleSourceSet related classes from Jav…; `51ade87f` [gradle][LSP-1698] ModuleSourceSet refactoring (at that commit the file was still `workspace-import/gradle-plugin/src/com/jetbrains/ls/imports/gradle/model/impl/ModuleSourceSetImpl.java`); `68512d41` [gradle][LSP-1686] added support for Java_PREVIEW language level (at that commit the file was still `workspace-import/gradle-plugin/src/com/jetbrains/ls/imports/gradle/model/impl/ModuleSourceSetImpl.java`) — run `git show` on any of them.
Change coupling: ModuleSourceSetsModelBuilder.kt ↔ IdeaProjectMapper.kt workspace-import/gradle-plugin/src/com/jetbrains/ls/imports/gradle/model/builder/ModuleSourceSetsModelBuilder.kt:1 — `workspace-import/gradle-plugin/src/com/jetbrains/ls/imports/gradle/model/builder/ModuleSourceSetsModelBuilder.kt` and `workspace-import/src/com/jetbrains/ls/imports/gradle/IdeaProjectMapper.kt` change together 65% of the time (11 of the 17 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 11 shared commits counted here, the most recent 3 are `77d91e13` [gradle][LSP-1698] Converted ModuleSourceSet related classes from Jav…; `51ade87f` [gradle][LSP-1698] ModuleSourceSet refactoring (at that commit the file was still `workspace-import/gradle-plugin/src/com/jetbrains/ls/imports/gradle/model/builder/ModuleSourceSetsModelBuilder.java`); `68512d41` [gradle][LSP-1686] added support for Java_PREVIEW language level (at that commit the file was still `workspace-import/gradle-plugin/src/com/jetbrains/ls/imports/gradle/model/builder/ModuleSourceSetsModelBuilder.java`) — run `git show` on any of them.
Change coupling: LSCommonDefinitionProvider.kt ↔ LSCommonReferencesProvider.kt features-impl/common/src/com/jetbrains/ls/api/features/impl/common/definitions/LSCommonDefinitionProvider.kt:1 — `features-impl/common/src/com/jetbrains/ls/api/features/impl/common/definitions/LSCommonDefinitionProvider.kt` and `features-impl/common/src/com/jetbrains/ls/api/features/impl/common/references/LSCommonReferencesProvider.kt` change together 62% of the time (10 of the 16 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 10 shared commits counted here, the most recent 3 are `e54836f1` misc lsp: reuse implementations of definitions, references and implem…; `3892e258` misc LSP: extract more copy-pasted code into module shared between ID…; `d87d46b0` [Java] LSP-981: Make reference resolved at the end of identifier poss… — run `git show` on any of them.
Change coupling: LSCommonInspectionDiagnosticProvider.kt ↔ LSKotlinCompilerDiagnosticsProvider.kt features-impl/common/src/com/jetbrains/ls/api/features/impl/common/diagnostics/LSCommonInspectionDiagnosticProvider.kt:1 — `features-impl/common/src/com/jetbrains/ls/api/features/impl/common/diagnostics/LSCommonInspectionDiagnosticProvider.kt` and `features-impl/kotlin/src/com/jetbrains/ls/api/features/impl/kotlin/diagnostics/compiler/LSKotlinCompilerDiagnosticsProvider.kt` change together 57% of the time (8 of the 14 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 8 shared commits counted here, the most recent 3 are `b3b19934` LSP-514: Do not show any diagnostics except to syntax errors for file…; `4089b84c` [Analyzer] LSP-480 Change API to support file settings configuration; `22a992b1` cleanup [lsp]: replace `file` with `virtualFile` for clarity in varia… (at that commit the files were still `features-impl/common/src/com/jetbrains/ls/api/features/impl/common/diagnostics/inspections/LSCommonInspectionDiagnosticProvider.kt` and `features-impl/kotlin/src/com/jetbrains/ls/api/features/impl/common/kotlin/diagnostics/compiler/LSKotlinCompilerDiagnosticsProvider.kt`) — run `git show` on any of them.
Change coupling: LSJavaBaseLanguageConfiguration.kt ↔ LSKotlinLanguageConfiguration.kt features-impl/java-base/src/com/jetbrains/ls/api/features/impl/javaBase/LSJavaBaseLanguageConfiguration.kt:1 — `features-impl/java-base/src/com/jetbrains/ls/api/features/impl/javaBase/LSJavaBaseLanguageConfiguration.kt` and `features-impl/kotlin/src/com/jetbrains/ls/api/features/impl/kotlin/configuration/LSKotlinLanguageConfiguration.kt` change together 57% of the time (8 of the 14 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 8 shared commits counted here, the most recent 3 are `3892e258` misc LSP: extract more copy-pasted code into module shared between ID…; `2912dc0e` refactor [analyzer] move java/kotlin inits to XML; `182ad99e` LSP-1069 lsp: allow specifying bazel projectview file in settings — run `git show` on any of them.
Change coupling: GradleTool.kt ↔ GradleToolingApiHelper.kt workspace-import/src/com/jetbrains/ls/imports/gradle/GradleTool.kt:1 — `workspace-import/src/com/jetbrains/ls/imports/gradle/GradleTool.kt` and `workspace-import/src/com/jetbrains/ls/imports/gradle/GradleToolingApiHelper.kt` change together 53% of the time (10 of the 19 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets). They sit in the same directory, and in this ecosystem sibling files there normally share one namespace/package — so a direct reference between them needs no import and this pass cannot see whether one exists. Read the pair before acting: if one file only DECLARES what the other consumes (a constants/types file beside its user), the co-change is definitional and the question is whether the split earns its keep; if they duplicate structure, extract the common part into a shared function or type they both call; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 10 shared commits counted here, the most recent 3 are `d2c860d3` LSP-1982: Do not use project in Build tool context. Preparation to mo…; `afabb1ad` cleanup lsp import: Move ImportEvent out of WorkspaceImporter; `6964f63d` LSP-882 [import] make Gradle import honors JAVA_HOME (at that commit the file was still `workspace-import/src/com/jetbrains/ls/imports/gradle/GradleWorkspaceImporter.kt`) — run `git show` on any of them.
Change coupling: LSCommonInspectionDiagnosticProvider.kt ↔ LSCommonReferencesProvider.kt features-impl/common/src/com/jetbrains/ls/api/features/impl/common/diagnostics/LSCommonInspectionDiagnosticProvider.kt:1 — `features-impl/common/src/com/jetbrains/ls/api/features/impl/common/diagnostics/LSCommonInspectionDiagnosticProvider.kt` and `features-impl/common/src/com/jetbrains/ls/api/features/impl/common/references/LSCommonReferencesProvider.kt` change together 50% of the time (8 of the 16 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 8 shared commits counted here, the most recent 3 are `22a992b1` cleanup [lsp]: replace `file` with `virtualFile` for clarity in varia… (at that commit the file was still `features-impl/common/src/com/jetbrains/ls/api/features/impl/common/diagnostics/inspections/LSCommonInspectionDiagnosticProvider.kt`); `c8255297` cleanup [lsp]: explicitly name `LspHandlerContext` parameter in conte… (at that commit the file was still `features-impl/common/src/com/jetbrains/ls/api/features/impl/common/diagnostics/inspections/LSCommonInspectionDiagnosticProvider.kt`); `06b47afa` cleanup [lsp]: access function `LSServer#withAnalysisContext` from co… (at that commit the file was still `features-impl/common/src/com/jetbrains/ls/api/features/impl/common/diagnostics/inspections/LSCommonInspectionDiagnosticProvider.kt`) — run `git show` on any of them.
Change coupling: LSKotlinCompilerDiagnosticsProvider.kt ↔ LSKotlinIntentionCodeActionProvider.kt features-impl/kotlin/src/com/jetbrains/ls/api/features/impl/kotlin/diagnostics/compiler/LSKotlinCompilerDiagnosticsProvider.kt:1 — `features-impl/kotlin/src/com/jetbrains/ls/api/features/impl/kotlin/diagnostics/compiler/LSKotlinCompilerDiagnosticsProvider.kt` and `features-impl/kotlin/src/com/jetbrains/ls/api/features/impl/kotlin/diagnostics/intentions/LSKotlinIntentionCodeActionProvider.kt` change together 50% of the time (7 of the 14 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 7 shared commits counted here, the most recent 3 are `4089b84c` [Analyzer] LSP-480 Change API to support file settings configuration; `546c9d4d` cleanup [lsp]: remove "common" package prefix from Kotlin implementation; `22a992b1` cleanup [lsp]: replace `file` with `virtualFile` for clarity in varia… (at that commit the files were still `features-impl/kotlin/src/com/jetbrains/ls/api/features/impl/common/kotlin/diagnostics/compiler/LSKotlinCompilerDiagnosticsProvider.kt` and `features-impl/kotlin/src/com/jetbrains/ls/api/features/impl/common/kotlin/diagnostics/intentions/LSKotlinIntentionCodeActionProvider.kt`) — run `git show` on any of them.

X3 · Exception handling · Swallowed exception (empty catch) · ×7

Swallowed exception (empty catch) workspace-import/gradle-plugin/src/com/jetbrains/ls/imports/gradle/model/builder/KotlinMetadataModelBuilder.java:172 — 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.
Swallowed exception (empty catch) workspace-import/gradle-plugin/src/com/jetbrains/ls/imports/gradle/model/builder/ModuleSourceSetsModelBuilder.kt:154 — 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.
Swallowed exception (empty catch) vscode-extension-core/src/intellijExtensions.ts:105 — `.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.
Swallowed exception (empty catch) vscode-extension-core/src/intellijExtensions.ts:272 — 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.
Swallowed exception (empty catch) vscode-extension-core/src/lspClient.ts:542 — 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.
Swallowed exception (empty catch) vscode-extension-core/src/serverBundleDownload.ts:561 — `.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.
Swallowed exception (empty catch) kotlin-vscode/launch-vscode.mjs:209 — 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.

D15 · Churn × Complexity Hotspots · Hotspot · ×5

Hotspot: vscode-extension-core/src/lspClient.ts vscode-extension-core/src/lspClient.ts:1043 — vscode-extension-core/src/lspClient.ts changed 36 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 19 in lspClient.registerSettingsChangeWatcher at line 1043. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-28..2026-10-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-28 16:46:18 +00:00' --until='2026-10-26 16:46:18 +00:00' --full-history --no-merges -- vscode-extension-core/src/lspClient.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
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:303 — features-impl/common/src/com/jetbrains/ls/api/features/impl/common/modcommands/ModCommandData.kt changed 18 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 35 in ModCommandData.from at line 303. 2 of those changes were fix/bug commits, and the other 16 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-07-28..2026-10-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-28 16:46:18 +00:00' --until='2026-10-26 16:46:18 +00:00' --full-history --no-merges -- features-impl/common/src/com/jetbrains/ls/api/features/impl/common/modcommands/ModCommandData.kt`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: workspace-import/src/com/jetbrains/ls/imports/jps/JpsBuildTool.kt workspace-import/src/com/jetbrains/ls/imports/jps/JpsBuildTool.kt:265 — workspace-import/src/com/jetbrains/ls/imports/jps/JpsBuildTool.kt changed 33 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 19 in JpsBuildTool.importJpsModel at line 265. 1 of those changes was a fix/bug commit, and the other 32 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-07-28..2026-10-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-28 16:46:18 +00:00' --until='2026-10-26 16:46:18 +00:00' --full-history --no-merges -- workspace-import/src/com/jetbrains/ls/imports/jps/JpsBuildTool.kt`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: workspace-import/src/com/jetbrains/ls/imports/json/conversion.kt workspace-import/src/com/jetbrains/ls/imports/json/conversion.kt:318 — workspace-import/src/com/jetbrains/ls/imports/json/conversion.kt changed 8 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 25 in ConversionKt.importWorkspaceData at line 318. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-28..2026-10-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-28 16:46:18 +00:00' --until='2026-10-26 16:46:18 +00:00' --full-history --no-merges -- workspace-import/src/com/jetbrains/ls/imports/json/conversion.kt`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: vscode-extension-core/src/initializationSettings.ts vscode-extension-core/src/initializationSettings.ts:161 — vscode-extension-core/src/initializationSettings.ts changed 9 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 21 in initializationSettings.projectRejectionReason at line 161. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-28..2026-10-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-28 16:46:18 +00:00' --until='2026-10-26 16:46:18 +00:00' --full-history --no-merges -- vscode-extension-core/src/initializationSettings.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.

R4 · Test Coverage · No test reaches this file · ×5

No test reaches this file kotlin-vscode/launch-vscode.mjs:1 — 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.
No test reaches this file kotlin-vscode/unpack-server.mjs:1 — 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.
No test reaches this file kotlin-vscode/src/extension.ts:1 — 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.
No test reaches this file vscode-language-kotlin/src/kotlin/module.ts:1 — 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.
No test reaches this file vscode-jvm-testing/src/module.ts:1 — 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.

D3 · God Classes · MethodTooLong · ×3

MethodTooLong: JpsBuildTool.importJpsModel workspace-import/src/com/jetbrains/ls/imports/jps/JpsBuildTool.kt:265 — MethodTooLong — importJpsModel runs 161 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 61 over it, 1.61× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: ModCommandDataKt.executeCommand features-impl/common/src/com/jetbrains/ls/api/features/impl/common/modcommands/ModCommandData.kt:486 — MethodTooLong — executeCommand runs 135 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 35 over it, 1.35× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: ConversionKt.importWorkspaceData workspace-import/src/com/jetbrains/ls/imports/json/conversion.kt:318 — MethodTooLong — importWorkspaceData runs 123 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 23 over it, 1.23× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.

D1 · Cyclomatic Complexity · KindsKt.getKind (cyclomatic 20) · ×2

KindsKt.getKind (cyclomatic 20) features-impl/kotlin/psi/src/com/jetbrains/ls/api/features/impl/kotlin/psi/kinds.kt:21 — KindsKt.getKind has cyclomatic complexity 20 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
KindsKt.getKind (cyclomatic 20) features-impl/kotlin/src/com/jetbrains/ls/api/features/impl/kotlin/symbols/kinds.kt:21 — KindsKt.getKind has cyclomatic complexity 20 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.

D35 · Change Coupling · Change-coupling hub · ×2

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 — `features-impl/kotlin/src/com/jetbrains/ls/api/features/impl/kotlin/definitions/LSKotlinPackageDefinitionProvider.kt` changes together with 5 other files — `features-impl/common/src/com/jetbrains/ls/api/features/impl/common/definitions/LSCommonDefinitionProvider.kt`, `features-impl/common/src/com/jetbrains/ls/api/features/impl/common/diagnostics/LSCommonInspectionDiagnosticProvider.kt`, `features-impl/common/src/com/jetbrains/ls/api/features/impl/common/hover/LSHoverProviderBase.kt`, `features-impl/common/src/com/jetbrains/ls/api/features/impl/common/references/LSCommonReferencesProvider.kt`, `features-impl/kotlin/src/com/jetbrains/ls/api/features/impl/kotlin/semanticTokens/LSKotlinSemanticTokensProvider.kt` — none of which declares a dependency on it: one file is the hub of 5 separate couplings, not 5 unrelated pairs. Read the hub first: if the others each duplicate a part of what it does, the shared concern belongs in ONE unit and extracting it clears every edge at once; if the hub is a registry, dispatcher or barrel that must name each of them, the coupling is structural and the question is whether that list can be discovered instead of enumerated. Fixing the hub is one change; breaking the couplings one pair at a time is 5.
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 — `features-impl/common/src/com/jetbrains/ls/api/features/impl/common/diagnostics/LSCommonSyntaxErrorDiagnosticProvider.kt` changes together with 7 other files — `features-impl/common/src/com/jetbrains/ls/api/features/impl/common/definitions/LSCommonDefinitionProvider.kt`, `features-impl/common/src/com/jetbrains/ls/api/features/impl/common/diagnostics/LSCommonInspectionDiagnosticProvider.kt`, `features-impl/common/src/com/jetbrains/ls/api/features/impl/common/references/LSCommonReferencesProvider.kt`, `features-impl/kotlin/src/com/jetbrains/ls/api/features/impl/kotlin/definitions/LSKotlinPackageDefinitionProvider.kt`, `features-impl/kotlin/src/com/jetbrains/ls/api/features/impl/kotlin/diagnostics/compiler/LSKotlinCompilerDiagnosticsFixesCodeActionProvider.kt`, `features-impl/kotlin/src/com/jetbrains/ls/api/features/impl/kotlin/diagnostics/compiler/LSKotlinCompilerDiagnosticsProvider.kt`, `features-impl/kotlin/src/com/jetbrains/ls/api/features/impl/kotlin/diagnostics/intentions/LSKotlinIntentionCodeActionProvider.kt` — none of which declares a dependency on it: one file is the hub of 7 separate couplings, not 7 unrelated pairs. Read the hub first: if the others each duplicate a part of what it does, the shared concern belongs in ONE unit and extracting it clears every edge at once; if the hub is a registry, dispatcher or barrel that must name each of them, the coupling is structural and the question is whether that list can be discovered instead of enumerated. Fixing the hub is one change; breaking the couplings one pair at a time is 7.

R10 · Code Duplication · Duplicated block (14 lines × 2 locations) · ×2

Duplicated block (14 lines × 2 locations) vscode-extension-core/src/keyHandlerUtils.ts:119 — 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.
Duplicated block (14 lines × 2 locations) vscode-extension-core/src/keyHandlerUtils.ts:668 — 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.

R10 · Code Duplication · Duplicated block (13 lines × 2 locations) · ×2

Duplicated block (13 lines × 2 locations) vscode-extension-core/src/keyHandlerUtils.ts:406 — 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.
Duplicated block (13 lines × 2 locations) vscode-extension-core/src/serverBundleDownload.ts:783 — 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.

R10 · Code Duplication · Duplicated block (10 lines × 2 locations) · ×2

Duplicated block (10 lines × 2 locations) vscode-extension-core/src/keyHandlerUtils.ts:573 — 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.
Duplicated block (10 lines × 2 locations) vscode-extension-core/src/serverBundleDownload.ts:370 — 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.

D1 · Cyclomatic Complexity · LSKotlinSemanticTokensProvider.getRangeWithToken (cyclomatic 44) · ×1

LSKotlinSemanticTokensProvider.getRangeWithToken (cyclomatic 44) features-impl/kotlin/src/com/jetbrains/ls/api/features/impl/kotlin/semanticTokens/LSKotlinSemanticTokensProvider.kt:138 — LSKotlinSemanticTokensProvider.getRangeWithToken has cyclomatic complexity 44 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.

D1 · Cyclomatic Complexity · ModCommandData.from (cyclomatic 35) · ×1

ModCommandData.from (cyclomatic 35) features-impl/common/src/com/jetbrains/ls/api/features/impl/common/modcommands/ModCommandData.kt:303 — ModCommandData.from has cyclomatic complexity 35 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.

D1 · Cyclomatic Complexity · ModCommandDataKt.executeCommand (cyclomatic 34) · ×1

ModCommandDataKt.executeCommand (cyclomatic 34) features-impl/common/src/com/jetbrains/ls/api/features/impl/common/modcommands/ModCommandData.kt:486 — ModCommandDataKt.executeCommand has cyclomatic complexity 34 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.

D1 · Cyclomatic Complexity · ModCompletionCommandConverter.split (cyclomatic 27) · ×1

ModCompletionCommandConverter.split (cyclomatic 27) features-impl/common/src/com/jetbrains/ls/api/features/impl/common/completion/ModCompletionCommandConverter.kt:215 — ModCompletionCommandConverter.split has cyclomatic complexity 27 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · ConversionKt.importWorkspaceData (cyclomatic 25) · ×1

ConversionKt.importWorkspaceData (cyclomatic 25) workspace-import/src/com/jetbrains/ls/imports/json/conversion.kt:318 — ConversionKt.importWorkspaceData has cyclomatic complexity 25 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.

D1 · Cyclomatic Complexity · serverBundleDownload.downloadFile (cyclomatic 24) · ×1

serverBundleDownload.downloadFile (cyclomatic 24) vscode-extension-core/src/serverBundleDownload.ts:381 — serverBundleDownload.downloadFile has cyclomatic complexity 24 (threshold 15). Most of this is not in the body itself: 6 of the 24 points are its own statements and the rest belongs to one function literal inside it that branches (line 399). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.

D1 · Cyclomatic Complexity · initializationSettings.projectRejectionReason (cyclomatic 21) · ×1

initializationSettings.projectRejectionReason (cyclomatic 21) vscode-extension-core/src/initializationSettings.ts:161 — initializationSettings.projectRejectionReason has cyclomatic complexity 21 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · JpsBuildTool.importJpsModel (cyclomatic 19) · ×1

JpsBuildTool.importJpsModel (cyclomatic 19) workspace-import/src/com/jetbrains/ls/imports/jps/JpsBuildTool.kt:265 — JpsBuildTool.importJpsModel has cyclomatic complexity 19 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.

D1 · Cyclomatic Complexity · lspClient.registerSettingsChangeWatcher (cyclomatic 19) · ×1

lspClient.registerSettingsChangeWatcher (cyclomatic 19) vscode-extension-core/src/lspClient.ts:1043 — lspClient.registerSettingsChangeWatcher has cyclomatic complexity 19 (threshold 15). Most of this is not in the body itself: 1 of the 19 points is its own statement and the rest belongs to 4 function items inside it that branch (prompt, a function literal at line 1105, schedule, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.

D1 · Cyclomatic Complexity · keyHandler.handleEnter (cyclomatic 19) · ×1

keyHandler.handleEnter (cyclomatic 19) vscode-language-kotlin/src/kotlin/keyHandler.ts:318 — keyHandler.handleEnter has cyclomatic complexity 19 (threshold 15). Most of this is not in the body itself: 1 of the 19 points is its own statement and the rest belongs to 2 function literals inside it that branch (lines 334, 328). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.

D1 · Cyclomatic Complexity · DependencyFlatteningKt.flattenExportedDependencies (cyclomatic 18) · ×1

DependencyFlatteningKt.flattenExportedDependencies (cyclomatic 18) workspace-import/src/com/jetbrains/ls/imports/json/dependencyFlattening.kt:19 — DependencyFlatteningKt.flattenExportedDependencies has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · keyHandler.handleDoubleQuoteKey (cyclomatic 17) · ×1

keyHandler.handleDoubleQuoteKey (cyclomatic 17) vscode-language-kotlin/src/kotlin/keyHandler.ts:142 — keyHandler.handleDoubleQuoteKey has cyclomatic complexity 17 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.

D1 · Cyclomatic Complexity · MainEdit.convertTemplate (cyclomatic 16) · ×1

MainEdit.convertTemplate (cyclomatic 16) features-impl/common/src/com/jetbrains/ls/api/features/impl/common/completion/ModCompletionCommandConverter.kt:90 — MainEdit.convertTemplate has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · UtilKt.doGetCompilerProp (cyclomatic 16) · ×1

UtilKt.doGetCompilerProp (cyclomatic 16) workspace-import/maven-plugin/src/com/jetbrains/ls/imports/maven/util.kt:179 — UtilKt.doGetCompilerProp has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · lspClient.doStartLspClient (cyclomatic 16) · ×1

lspClient.doStartLspClient (cyclomatic 16) vscode-extension-core/src/lspClient.ts:487 — lspClient.doStartLspClient has cyclomatic complexity 16 (threshold 15). Of this number, 10 points are the body's own statements and 6 belong to 2 function literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · lspClient.startServer (cyclomatic 16) · ×1

lspClient.startServer (cyclomatic 16) vscode-extension-core/src/lspClient.ts:864 — lspClient.startServer has cyclomatic complexity 16 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.

D1 · Cyclomatic Complexity · handleKeyType.registerHandleKeyType (cyclomatic 16) · ×1

handleKeyType.registerHandleKeyType (cyclomatic 16) vscode-extension-core/src/handleKeyType.ts:29 — handleKeyType.registerHandleKeyType has cyclomatic complexity 16 (threshold 15). Most of this is not in the body itself: 1 of the 16 points is its own statement and the rest belongs to one function literal inside it that branches (line 37). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.

D15 · Churn × Complexity Hotspots · Repeated repair · ×1

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:55 — features-impl/common/src/com/jetbrains/ls/api/features/impl/common/diagnostics/LSInspectionManager.kt changed 8 times in last 90 days and 5 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 8 (its worst body is LSInspectionManager.getLazyFix at line 55), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “DBE-25878 [datagrip]: Refactor DataGrip quick fixes to use ModCommand API for the LSP”; “LSP-1990 [lsp] Display name rather than familyName for ModCommandAction-based quick-fixes”; “cleanup [lsp]: Use fix name from presentation when possible.”; “cleanup [lsp] Remove HTML from quick-fix name”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-07-28..2026-10-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-28 16:46:18 +00:00' --until='2026-10-26 16:46:18 +00:00' --full-history --no-merges -- features-impl/common/src/com/jetbrains/ls/api/features/impl/common/diagnostics/LSInspectionManager.kt`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.

D2 · Cognitive Complexity · ModCompletionCommandConverter.split (cognitive 57) · ×1

ModCompletionCommandConverter.split (cognitive 57) features-impl/common/src/com/jetbrains/ls/api/features/impl/common/completion/ModCompletionCommandConverter.kt:215 — ModCompletionCommandConverter.split has cognitive complexity 57 (threshold 15). Drivers by points: if/else 18 (41 pts), boolean chains 8, loops 2 (4 pts), match/switch 1 (4 pts) (nesting depth added 28). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · DependencyFlatteningKt.flattenExportedDependencies (cognitive 39) · ×1

DependencyFlatteningKt.flattenExportedDependencies (cognitive 39) workspace-import/src/com/jetbrains/ls/imports/json/dependencyFlattening.kt:19 — DependencyFlatteningKt.flattenExportedDependencies has cognitive complexity 39 (threshold 15). Drivers by points: if/else 8 (21 pts), loops 6 (12 pts), match/switch 2 (5 pts), boolean chains 1 (nesting depth added 22). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · ModCommandDataKt.executeCommand (cognitive 38) · ×1

ModCommandDataKt.executeCommand (cognitive 38) features-impl/common/src/com/jetbrains/ls/api/features/impl/common/modcommands/ModCommandData.kt:486 — ModCommandDataKt.executeCommand has cognitive complexity 38 (threshold 15). Drivers by points: if/else 11 (21 pts), match/switch 6 (13 pts), boolean chains 2, loops 1 (2 pts) (nesting depth added 18). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.

D2 · Cognitive Complexity · LSKotlinSemanticTokensProvider.getRangeWithToken (cognitive 38) · ×1

LSKotlinSemanticTokensProvider.getRangeWithToken (cognitive 38) features-impl/kotlin/src/com/jetbrains/ls/api/features/impl/kotlin/semanticTokens/LSKotlinSemanticTokensProvider.kt:138 — LSKotlinSemanticTokensProvider.getRangeWithToken has cognitive complexity 38 (threshold 15). Drivers by points: if/else 15 (20 pts), match/switch 7 (15 pts), boolean chains 3 (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · lspClient.doStartLspClient (cognitive 38) · ×1

lspClient.doStartLspClient (cognitive 38) vscode-extension-core/src/lspClient.ts:487 — lspClient.doStartLspClient has cognitive complexity 38 (threshold 15). Drivers by points: if/else 7 (18 pts), ternaries 3 (9 pts), error handling 3 (8 pts), loops 2 (3 pts) (nesting depth added 23). Of this number, 23 points are the body's own statements and 15 belong to 2 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · ProjectMetadataBuilder.resolveModels (cognitive 32) · ×1

ProjectMetadataBuilder.resolveModels (cognitive 32) workspace-import/gradle-plugin/src/com/jetbrains/ls/imports/gradle/action/ProjectMetadataBuilder.java:88 — ProjectMetadataBuilder.resolveModels has cognitive complexity 32 (threshold 15). Drivers by points: if/else 5 (15 pts), ternaries 4 (12 pts), loops 2 (3 pts), boolean chains 2 (nesting depth added 19). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · ModCommandData.from (cognitive 31) · ×1

ModCommandData.from (cognitive 31) features-impl/common/src/com/jetbrains/ls/api/features/impl/common/modcommands/ModCommandData.kt:303 — ModCommandData.from has cognitive complexity 31 (threshold 15). Drivers by points: match/switch 10 (20 pts), if/else 9, boolean chains 2 (nesting depth added 10). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.

D2 · Cognitive Complexity · ConverterKt.mapModuleNames (cognitive 29) · ×1

ConverterKt.mapModuleNames (cognitive 29) workspace-import/maven-plugin/src/com/jetbrains/ls/imports/maven/converter.kt:89 — ConverterKt.mapModuleNames has cognitive complexity 29 (threshold 15). Drivers by points: if/else 7 (20 pts), loops 6 (9 pts) (nesting depth added 16). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · UtilKt.doGetCompilerProp (cognitive 29) · ×1

UtilKt.doGetCompilerProp (cognitive 29) workspace-import/maven-plugin/src/com/jetbrains/ls/imports/maven/util.kt:179 — UtilKt.doGetCompilerProp has cognitive complexity 29 (threshold 15). Drivers by points: if/else 9 (23 pts), boolean chains 6 (nesting depth added 14). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.

D2 · Cognitive Complexity · ConversionKt.importWorkspaceData (cognitive 28) · ×1

ConversionKt.importWorkspaceData (cognitive 28) workspace-import/src/com/jetbrains/ls/imports/json/conversion.kt:318 — ConversionKt.importWorkspaceData has cognitive complexity 28 (threshold 15). Drivers by points: if/else 8 (12 pts), match/switch 4 (8 pts), loops 5, boolean chains 3 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · serverBundleDownload.withInstallLock (cognitive 28) · ×1

serverBundleDownload.withInstallLock (cognitive 28) vscode-extension-core/src/serverBundleDownload.ts:509 — serverBundleDownload.withInstallLock has cognitive complexity 28 (threshold 15). Drivers by points: if/else 8 (24 pts), error handling 1 (2 pts), boolean chains 1, loops 1 (nesting depth added 17). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · LSCommonIntentionFixesCodeActionProvider.infoInspections (cognitive 26) · ×1

LSCommonIntentionFixesCodeActionProvider.infoInspections (cognitive 26) features-impl/common/src/com/jetbrains/ls/api/features/impl/common/diagnostics/LSCommonIntentionFixesCodeActionProvider.kt:85 — LSCommonIntentionFixesCodeActionProvider.infoInspections has cognitive complexity 26 (threshold 15). Drivers by points: if/else 4 (13 pts), loops 4 (11 pts), boolean chains 2 (nesting depth added 16). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · MainEdit.convertTemplate (cognitive 25) · ×1

MainEdit.convertTemplate (cognitive 25) features-impl/common/src/com/jetbrains/ls/api/features/impl/common/completion/ModCompletionCommandConverter.kt:90 — MainEdit.convertTemplate has cognitive complexity 25 (threshold 15). Drivers by points: if/else 8 (17 pts), boolean chains 4, loops 2, match/switch 1 (2 pts) (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · initializationSettings.projectRejectionReason (cognitive 25) · ×1

initializationSettings.projectRejectionReason (cognitive 25) vscode-extension-core/src/initializationSettings.ts:161 — initializationSettings.projectRejectionReason has cognitive complexity 25 (threshold 15). Drivers by points: if/else 9 (14 pts), boolean chains 7, loops 4 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · keyHandler.handleStringLiteralKey (cognitive 25) · ×1

keyHandler.handleStringLiteralKey (cognitive 25) vscode-language-kotlin/src/kotlin/keyHandler.ts:243 — keyHandler.handleStringLiteralKey has cognitive complexity 25 (threshold 15). Drivers by points: if/else 7 (16 pts), match/switch 2 (6 pts), boolean chains 2, ternaries 1 (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · serverBundleDownload.downloadFile (cognitive 22) · ×1

serverBundleDownload.downloadFile (cognitive 22) vscode-extension-core/src/serverBundleDownload.ts:381 — serverBundleDownload.downloadFile has cognitive complexity 22 (threshold 15). Drivers by points: if/else 7 (9 pts), ternaries 7, boolean chains 6 (nesting depth added 2). Most of this is not in the body itself: 5 of the 22 points are its own statements and the rest belongs to one function literal inside it that branches (line 399). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.

D2 · Cognitive Complexity · KotlinMultiplatformMapper.map (cognitive 21) · ×1

KotlinMultiplatformMapper.map (cognitive 21) workspace-import/src/com/jetbrains/ls/imports/gradle/kmp/KotlinMultiplatformMapper.kt:175 — KotlinMultiplatformMapper.map has cognitive complexity 21 (threshold 15). Drivers by points: if/else 10 (16 pts), loops 3, boolean chains 2 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · lspClient.ensureBundledServerLauncher (cognitive 21) · ×1

lspClient.ensureBundledServerLauncher (cognitive 21) vscode-extension-core/src/lspClient.ts:692 — lspClient.ensureBundledServerLauncher has cognitive complexity 21 (threshold 15). Drivers by points: if/else 7 (13 pts), error handling 2 (4 pts), ternaries 1 (4 pts) (nesting depth added 11). Of this number, 14 points are the body's own statements and 7 belong to 2 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · JpsBuildTool.importJpsModel (cognitive 20) · ×1

JpsBuildTool.importJpsModel (cognitive 20) workspace-import/src/com/jetbrains/ls/imports/jps/JpsBuildTool.kt:265 — JpsBuildTool.importJpsModel has cognitive complexity 20 (threshold 15). Drivers by points: if/else 11 (14 pts), match/switch 5, boolean chains 1 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.

D2 · Cognitive Complexity · lspClient.registerSettingsChangeWatcher (cognitive 19) · ×1

lspClient.registerSettingsChangeWatcher (cognitive 19) vscode-extension-core/src/lspClient.ts:1043 — lspClient.registerSettingsChangeWatcher has cognitive complexity 19 (threshold 15). Drivers by points: if/else 13, boolean chains 6. None of this is in the body itself: all 19 points belong to 4 function items inside it that branch (prompt, a function literal at line 1105, schedule, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.

D2 · Cognitive Complexity · RunStepsKt.run (cognitive 18) · ×1

RunStepsKt.run (cognitive 18) buildtool.api/src/com/jetbrains/ls/buildtool/api/run/RunSteps.kt:29 — RunStepsKt.run has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (11 pts), loops 2 (4 pts), match/switch 1 (2 pts), boolean chains 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · GradleContentRootResolver.getContentRoots (cognitive 17) · ×1

GradleContentRootResolver.getContentRoots (cognitive 17) workspace-import/src/com/jetbrains/ls/imports/gradle/GradleContentRootResolver.kt:43 — GradleContentRootResolver.getContentRoots has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (12 pts), boolean chains 3, loops 2 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · lspClient.startServer (cognitive 17) · ×1

lspClient.startServer (cognitive 17) vscode-extension-core/src/lspClient.ts:864 — lspClient.startServer has cognitive complexity 17 (threshold 15). Drivers by points: if/else 10, ternaries 6 (7 pts) (nesting depth added 1). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.

D2 · Cognitive Complexity · MavenRunCommandsKt.mavenArgs (cognitive 16) · ×1

MavenRunCommandsKt.mavenArgs (cognitive 16) workspace-import/src/com/jetbrains/ls/imports/maven/MavenRunCommands.kt:49 — MavenRunCommandsKt.mavenArgs has cognitive complexity 16 (threshold 15). Drivers by points: if/else 9 (14 pts), boolean chains 1, match/switch 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · keyHandler.handleEnter (cognitive 16) · ×1

keyHandler.handleEnter (cognitive 16) vscode-language-kotlin/src/kotlin/keyHandler.ts:318 — keyHandler.handleEnter has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (9 pts), boolean chains 5, ternaries 2 (nesting depth added 3). None of this is in the body itself: all 16 points belong to 2 function literals inside it that branch (lines 334, 328). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.

D4 · Code Duplication · Duplicated block (32 lines × 2) · ×1

Duplicated block (32 lines × 2) features-impl/kotlin/psi/src/com/jetbrains/ls/api/features/impl/kotlin/psi/kinds.kt:21 — features-impl/kotlin/psi/src/com/jetbrains/ls/api/features/impl/kotlin/psi/kinds.kt:21-52 | features-impl/kotlin/src/com/jetbrains/ls/api/features/impl/kotlin/symbols/kinds.kt:21-52 — before extracting anything, compare `features-impl/kotlin/psi/src/com/jetbrains/ls/api/features/impl/kotlin/psi/kinds.kt` and `features-impl/kotlin/src/com/jetbrains/ls/api/features/impl/kotlin/symbols/kinds.kt` as WHOLE FILES: 88% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.

D4 · Code Duplication · Duplicated block (12–16 lines × 2) · ×1

Duplicated block (12–16 lines × 2) buildtool.api/src/com/jetbrains/ls/buildtool/api/run/RunSteps.kt:79 — buildtool.api/src/com/jetbrains/ls/buildtool/api/run/RunSteps.kt:79-90 | buildtool.api/src/com/jetbrains/ls/buildtool/api/run/processRunHandle.kt:81-96 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `buildtool.api/src/com/jetbrains/ls/buildtool/api/run/RunSteps.kt:79` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.

D4 · Code Duplication · Duplicated block (8–14 lines × 2) · ×1

Duplicated block (8–14 lines × 2) workspace-import/src/com/jetbrains/ls/imports/json/conversion.kt:354 — workspace-import/src/com/jetbrains/ls/imports/json/conversion.kt:354-367 | workspace-import/src/com/jetbrains/ls/imports/utils/defaultSdk.kt:45-52 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `workspace-import/src/com/jetbrains/ls/imports/json/conversion.kt:354` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.

D4 · Code Duplication · Duplicated block (5 lines × 2) · ×1

Duplicated block (5 lines × 2) workspace-import/maven-plugin/src/com/jetbrains/ls/imports/maven/util.kt:190 — workspace-import/maven-plugin/src/com/jetbrains/ls/imports/maven/util.kt:190-194 | workspace-import/maven-plugin/src/com/jetbrains/ls/imports/maven/util.kt:202-206 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `workspace-import/maven-plugin/src/com/jetbrains/ls/imports/maven/util.kt:190` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.

P1 · CI/CD gates · No CI pipeline · ×1

No CI pipeline — No CI workflow found (.github/workflows, azure-pipelines.yml, .gitlab-ci.yml, …) — changes aren't gated by an automated build/test.

R10 · Code Duplication · Duplicated block (15 lines × 2 locations) · ×1

Duplicated block (15 lines × 2 locations) vscode-language-kotlin/src/kotlin/keyHandler.ts:609 — 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.

R10 · Code Duplication · Duplicated block (11 lines × 2 locations) · ×1

Duplicated block (11 lines × 2 locations) vscode-language-kotlin/src/kotlin/keyHandler.ts:173 — 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.

R10 · Code Duplication · Duplicated block with local edits (10 matched lines × 2 locations) · ×1

Duplicated block with local edits (10 matched lines × 2 locations) vscode-testing/src/testTree.ts:175 — 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.

R10 · Code Duplication · Duplicated block (7 lines × 2 locations) · ×1

Duplicated block (7 lines × 2 locations) vscode-language-kotlin/src/kotlin/keyHandler.ts:875 — 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.

R2 · Cyclomatic Complexity · Complex function projectRejectionReason (cyclomatic 21, cognitive 25) · ×1

Complex function projectRejectionReason (cyclomatic 21, cognitive 25) vscode-extension-core/src/initializationSettings.ts:161 — 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.

R2 · Cyclomatic Complexity · Complex function (anonymous) (cyclomatic 20, cognitive 18) · ×1

Complex function (anonymous) (cyclomatic 20, cognitive 18) vscode-extension-core/src/serverBundleDownload.ts:399 — (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.

R2 · Cyclomatic Complexity · Complex function (anonymous) (cyclomatic 19, cognitive 18) · ×1

Complex function (anonymous) (cyclomatic 19, cognitive 18) vscode-language-kotlin/src/kotlin/keyHandler.ts:334 — (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.

R2 · Cyclomatic Complexity · Complex function startServer (cyclomatic 18, cognitive 19) · ×1

Complex function startServer (cyclomatic 18, cognitive 19) vscode-extension-core/src/lspClient.ts:864 — 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.

R2 · Cyclomatic Complexity · Complex function handleDoubleQuoteKey (cyclomatic 17, cognitive 16) · ×1

Complex function handleDoubleQuoteKey (cyclomatic 17, cognitive 16) vscode-language-kotlin/src/kotlin/keyHandler.ts:142 — 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.

R2 · Cyclomatic Complexity · Complex function handleStringLiteralKey (cyclomatic 16, cognitive 26) · ×1

Complex function handleStringLiteralKey (cyclomatic 16, cognitive 26) vscode-language-kotlin/src/kotlin/keyHandler.ts:243 — 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.

R2 · Cyclomatic Complexity · Complex function (anonymous) (cyclomatic 16, cognitive 13) · ×1

Complex function (anonymous) (cyclomatic 16, cognitive 13) vscode-extension-core/src/handleKeyType.ts:37 — (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.

R2 · Cyclomatic Complexity · Complex function shouldAutoCloseOpeningDelimiter (cyclomatic 16, cognitive 9) · ×1

Complex function shouldAutoCloseOpeningDelimiter (cyclomatic 16, cognitive 9) vscode-extension-core/src/keyHandlerUtils.ts:885 — 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.

R2 · Cyclomatic Complexity · Complex function (anonymous) (cyclomatic 15, cognitive 15) · ×1

Complex function (anonymous) (cyclomatic 15, cognitive 15) vscode-extension-core/src/lspClient.ts:1053 — (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.

R2 · Cyclomatic Complexity · Complex function clearCachesAndRestart (cyclomatic 14, cognitive 16) · ×1

Complex function clearCachesAndRestart (cyclomatic 14, cognitive 16) vscode-extension-core/src/lspClient.ts:271 — 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.

R2 · Cyclomatic Complexity · Complex function handleMultilineStringLiteralEnter (cyclomatic 14, cognitive 16) · ×1

Complex function handleMultilineStringLiteralEnter (cyclomatic 14, cognitive 16) vscode-language-kotlin/src/kotlin/keyHandler.ts:1223 — 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.

R2 · Cyclomatic Complexity · Complex function readServerBundleMetadata (cyclomatic 14, cognitive 15) · ×1

Complex function readServerBundleMetadata (cyclomatic 14, cognitive 15) vscode-extension-core/src/serverBundleDownload.ts:175 — 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.

R2 · Cyclomatic Complexity · Complex function locate (cyclomatic 14, cognitive 15) · ×1

Complex function locate (cyclomatic 14, cognitive 15) vscode-testing/src/teamCityReader.ts:136 — 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.

R2 · Cyclomatic Complexity · Complex function computeStatusTooltipContent (cyclomatic 14, cognitive 13) · ×1

Complex function computeStatusTooltipContent (cyclomatic 14, cognitive 13) vscode-extension-core/src/statusBarModel.ts:133 — 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.

R2 · Cyclomatic Complexity · Complex function handleRegularEnter (cyclomatic 14, cognitive 11) · ×1

Complex function handleRegularEnter (cyclomatic 14, cognitive 11) vscode-language-kotlin/src/kotlin/keyHandler.ts:437 — 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.

R2 · Cyclomatic Complexity · Complex function handleFileCreated (cyclomatic 13, cognitive 13) · ×1

Complex function handleFileCreated (cyclomatic 13, cognitive 13) vscode-extension-core/src/fileTemplates.ts:24 — 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.

R2 · Cyclomatic Complexity · Complex function withInstallLock (cyclomatic 12, cognitive 28) · ×1

Complex function withInstallLock (cyclomatic 12, cognitive 28) vscode-extension-core/src/serverBundleDownload.ts:509 — 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.

R2 · Cyclomatic Complexity · Complex function doStartLspClient (cyclomatic 12, cognitive 26) · ×1

Complex function doStartLspClient (cyclomatic 12, cognitive 26) vscode-extension-core/src/lspClient.ts:487 — 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.

R3 · Large Files · vscode-language-kotlin/src/kotlin/keyHandler.ts · ×1

vscode-language-kotlin/src/kotlin/keyHandler.ts: 1543 lines of code vscode-language-kotlin/src/kotlin/keyHandler.ts:1 — 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.

R3 · Large Files · vscode-extension-core/src/lspClient.ts · ×1

vscode-extension-core/src/lspClient.ts: 1273 lines of code vscode-extension-core/src/lspClient.ts:1 — vscode-extension-core/src/lspClient.ts has 1273 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.

R3 · Large Files · vscode-extension-core/src/keyHandlerUtils.ts · ×1

vscode-extension-core/src/keyHandlerUtils.ts: 958 lines of code vscode-extension-core/src/keyHandlerUtils.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.

R3 · Large Files · vscode-extension-core/src/serverBundleDownload.ts · ×1

vscode-extension-core/src/serverBundleDownload.ts: 763 lines of code vscode-extension-core/src/serverBundleDownload.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.

R6 · Tooling · No lint script · ×1

No lint script — 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.

SC1 · Supply-chain hygiene · JavaScript dependencies are not locked · ×1

JavaScript dependencies are not locked — No package-lock.json / yarn.lock / pnpm-lock.yaml / bun.lock — JS installs aren't reproducible (SSDF PW.4.4). Commit your package manager's lockfile and install from it (`npm ci`, `yarn --immutable`, `pnpm i --frozen-lockfile` or `bun i --frozen-lockfile`). Advisory — never scored.

X18 · Disposal-pattern correctness · Owned disposable field is never released · ×1

Owned disposable field is never released vscode-extension-core/src/runTerminal.ts:59 — `RunOutputTerminal` declares a disposal member — so it has told every caller it holds something worth releasing — and it constructs `writeEmitter` itself (line 59, `new EventEmitter`), which makes that instance its own. But `writeEmitter` is named in none of the methods the disposal search covered: `dispose` (line 88) — 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.

X2 · Cancellation propagation · Async function without AbortSignal · ×1

Async function without AbortSignal: checkGeoRestricted vscode-extension-core/src/geoRestriction.ts:13 — `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 })`.

Minor — 23 finding(s)

D34 · Knowledge Freshness · Orphaned file · ×7

Orphaned file workspace-import/gradle-plugin/src/com/jetbrains/ls/imports/gradle/utils/androidReflection.kt:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file api.features/src/com/jetbrains/ls/api/features/semanticTokens/encoding/SemanticTokensEncoder.kt:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file workspace-import/gradle-plugin/src/com/jetbrains/ls/imports/gradle/utils/reflectionUtils.kt:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file api.features/src/com/jetbrains/ls/api/features/semanticTokens/encoding/SemanticTokensDecoder.kt:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file workspace-import/gradle-plugin/src/com/jetbrains/ls/imports/gradle/utils/kotlinReflection.kt:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file api.features/src/com/jetbrains/ls/api/features/semanticTokens/LSSemanticTokenModifier.kt:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file kotlin-vscode/testSources/tokenization/sample.kt:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.

X10 · Duplicated predicate · Duplicated predicate · ×5

Duplicated predicate vscode-extension-core/src/extension.ts:168 — `client === undefined || client.initializeResult === undefined` appears character-identically in 2 files — vscode-extension-core/src/extension.ts, vscode-extension-core/src/fileTemplates.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate kotlin-vscode/unpack-server.mjs:57 — `lower.endsWith('.tar.gz') || lower.endsWith('.tgz')` appears character-identically in 2 files — kotlin-vscode/unpack-server.mjs, vscode-extension-core/src/serverBundleDownload.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate vscode-extension-core/src/keyHandlerUtils.ts:408 — `node === null || getPreviousSignificantChar(text, index) !== ','` appears character-identically in 2 files — vscode-extension-core/src/keyHandlerUtils.ts, vscode-language-kotlin/src/kotlin/keyHandler.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate vscode-extension-core/src/initializationSettings.ts:154 — `typeof value === 'object' && value !== null && !Array.isArray(value)` appears character-identically in 2 files — vscode-extension-core/src/initializationSettings.ts, vscode-jvm-testing/src/jvmTestConfig.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate workspace-import/maven-plugin/src/com/jetbrains/ls/imports/maven/converter.kt:345 — `executions == null || executions.isEmpty()` appears character-identically in 2 files — workspace-import/maven-plugin/src/com/jetbrains/ls/imports/maven/converter.kt, workspace-import/maven-plugin/src/com/jetbrains/ls/imports/maven/util.kt. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.

D16 · Bus Factor · Off-boarding risk · ×3

Off-boarding risk: anonymized user #1 — If anonymized user #1 becomes unavailable, 6 significant file(s) lose their only recent owner: workspace-import/gradle-plugin/src/com/jetbrains/ls/imports/gradle/model/builder/ExternalModuleDependencySetModuleBuilder.java, workspace-import/gradle-plugin/src/com/jetbrains/ls/imports/gradle/utils/SourceSetArtifactExtractor.java, workspace-import/src/com/jetbrains/ls/imports/gradle/util/ProjectLibraryIndex.kt, workspace-import/gradle-plugin/src/com/jetbrains/ls/imports/gradle/model/InternalIdeaModule.java, workspace-import/gradle-plugin/src/com/jetbrains/ls/imports/gradle/model/builder/PrepareKotlinIdeaImportTasksModelBuilder.kt, workspace-import/gradle-plugin/src/com/jetbrains/ls/imports/gradle/model/InternalIdeaProject.java. Pair on, review, or document these before any departure.
Off-boarding risk: anonymized user #2 — If anonymized user #2 becomes unavailable, 7 significant file(s) lose their only recent owner: features-impl/kotlin/src/com/jetbrains/ls/api/features/impl/kotlin/typeHierarchy/LSKotlinTypeHierarchyProvider.kt, features-impl/kotlin/src/com/jetbrains/ls/api/features/impl/kotlin/extract/LSKotlinExtractVariableProvider.kt, features-impl/common/src/com/jetbrains/ls/api/features/impl/common/codeLens/LSRelatedItemsCodeLensProvider.kt, features-impl/common/src/com/jetbrains/ls/api/features/impl/common/documentHighlight/LSCommonDocumentHighlightProvider.kt, api.features/src/com/jetbrains/ls/api/features/semanticTokens/LSSemanticTokenType.kt, workspace-import/src/com/jetbrains/ls/imports/json/dependencyFlattening.kt, features-impl/common/src/com/jetbrains/ls/api/features/impl/common/diagnostics/LSCommonInjectionSyntaxErrorDiagnosticProvider.kt. Pair on, review, or document these before any departure.
Off-boarding risk: anonymized user #3 — If anonymized user #3 becomes unavailable, 7 significant file(s) lose their only recent owner: features-impl/common/src/com/jetbrains/ls/api/features/impl/common/callHierarchy/LSCallHierarchyProviderBase.kt, features-impl/kotlin/src/com/jetbrains/ls/api/features/impl/kotlin/callHierarchy/LSKotlinCallHierarchyRenderer.kt, features-impl/common/src/com/jetbrains/ls/api/features/impl/common/move/LSCommonMoveProvider.kt, features-impl/common/src/com/jetbrains/ls/api/features/impl/common/move/LSMoveFilesOrDirectoriesProcessor.kt, features-impl/kotlin/src/com/jetbrains/ls/api/features/impl/kotlin/callHierarchy/LSKotlinCallHierarchyProvider.kt, features-impl/kotlin/src/com/jetbrains/ls/api/features/impl/kotlin/processors/LSMoveKotlinFileProcessor.kt, features-impl/common/src/com/jetbrains/ls/api/features/impl/common/rename/renameUtils.kt. Pair on, review, or document these before any departure.

X7 · Silent fallback defaults · Silent fallback default in catch · ×2

Silent fallback default in catch workspace-import/gradle-plugin/src/com/jetbrains/ls/imports/gradle/model/builder/KotlinMetadataModelBuilder.java:101 — `extractPluginOption` swallows every exception into `return Collections.emptyList()` — a data error becomes a silent behavior change with no trail. Log the failure or let it propagate. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment in the catch or in the Javadoc, and the row stops firing.
Silent fallback default in catch vscode-extension-core/src/proxySettings.ts:16 — `proxyJvmOptions` swallows every exception into `return []` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.

D16 · Bus Factor · Further sole-owners (lower concentration) · ×1

Further sole-owners (lower concentration) — 7 other contributor(s) are each the sole owner of a small amount of code below the off-boarding threshold — folded into the bus-factor score and metrics (29 single-owned of 177 analysed files in total, counted over production source files of roughly 2,400 bytes or more, excluding vendored, generated, example/demo and scaffolding-template trees and test files identified by path convention, largest first; 177 of the 383 production source files in this repository met that bar). They are anonymized user #4 (2 file(s)), anonymized user #5 (2 file(s)), anonymized user #6 (1 file(s)), anonymized user #7 (1 file(s)), anonymized user #8 (1 file(s)), anonymized user #9 (1 file(s)) (+1 more) — spread or document their files in the same way, at lower priority than the named off-boarding risks above. The files folded here: vscode-testing/src/serviceMessages.ts, vscode-testing/src/testTree.ts, features-impl/kotlin/src/com/jetbrains/ls/api/features/impl/kotlin/apiImpl/KotlinFirCacheImpl.kt, vscode-extension-core/src/lspRouter.ts, vscode-extension-core/src/keyHandlerUtils.ts, vscode-extension-core/src/extensionConflict.ts, workspace-import/gradle-plugin/src/com/jetbrains/ls/imports/gradle/utils/androidReflection.kt, vscode-extension-core/src/showConflictsModel.ts (+1 more).

D34 · Knowledge Freshness · Orphaned files with no living knowledge · ×1

Orphaned files with no living knowledge — 7 of 177 analysed file(s) have no living knowledge left — their last meaningful change has decayed away, so if one breaks, no one currently understands it (counted over production source files of roughly 2,400 bytes or more, excluding vendored, generated, example/demo and scaffolding-template trees and test files identified by path convention, largest first; 177 of the 383 production source files in this repository met that bar). None is large enough to earn a read-through of its own, so this row stands in for the per-file rows rather than raising one each — most significant first: workspace-import/gradle-plugin/src/com/jetbrains/ls/imports/gradle/utils/androidReflection.kt, workspace-import/gradle-plugin/src/com/jetbrains/ls/imports/gradle/utils/reflectionUtils.kt, workspace-import/gradle-plugin/src/com/jetbrains/ls/imports/gradle/utils/kotlinReflection.kt, kotlin-vscode/testSources/tokenization/sample.kt, api.features/src/com/jetbrains/ls/api/features/semanticTokens/encoding/SemanticTokensEncoder.kt, api.features/src/com/jetbrains/ls/api/features/semanticTokens/encoding/SemanticTokensDecoder.kt, api.features/src/com/jetbrains/ls/api/features/semanticTokens/LSSemanticTokenModifier.kt. Attach the read to the next change that touches one of them: have a second person review that change, and leave behind a short comment or test recording what the file is for, so the knowledge comes back at the cost of a change you were making anyway.

M2 · Architecture documentation · No ADRs · ×1

No ADRs — 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.

M2 · Architecture documentation · No architecture diagram/doc · ×1

No architecture diagram/doc — 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.

P3 · Security & performance tooling · No SAST · ×1

No SAST — 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.

X2 · Cancellation propagation · Not all async functions that make a request accept an AbortSignal · ×1

Not all async functions that make a request accept an AbortSignal — Only 2/3 async functions that make a cancellable request (fetch, axios, ky, ofetch) 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.

Appendix B — Reproduction & audit trail

Every external tool invocation behind a deep-scan dimension — the tool, its captured version, the exact command, how many findings it yielded, and a link to the retained raw output. To reproduce any finding: check out the same commit and run the command shown (repo-relative — never an absolute scratch path). The complete raw scanner output is retained verbatim under artifacts/raw/ (indexed in artifacts/raw/index.json); per-invocation exit codes and wall-clock durations are in sidecar.json — kept out of this table so the rendered report stays byte-identical across runs of the same commit.

Dimension	Tool	Version	Command	Raw output
D28 · Secrets (history)	gitleaks	—	gitleaks detect --no-banner --config /opt/gitleaks-rules/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-d300e75bda334e8ea1a98bcc87c16055/history.json --exit-code 0 --source .	artifacts/raw/gitleaks-history.json
D28 · Secrets (history)	gitleaks	—	gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-d300e75bda334e8ea1a98bcc87c16055/tree.json --exit-code 0 --source .	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/watchdog-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 .	artifacts/raw/semgrep.json
D30 · Dependency Vulnerabilities	trivy	—	trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs /bin/ --skip-dirs /obj/ . --skip-db-update	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.	—
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 118 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`, … (+113 more) — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real.	—
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.	—
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.	—
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.	—
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.	—
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.	—
D43 · Malicious Dependencies	trivy	—	trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs /bin/ --skip-dirs /obj/ . --skip-db-update	artifacts/raw/trivy-fs.json

Run 01a17a1c-a4e9-7337-b50e-0c5082515f0e · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.

Findings by how serious they are

This survey was produced by

Executive summary

Top priorities

Diagnosis: what the measurements show together

Architecture: which parts of the code depend on which

At a glance — Code Health · 77% · Strong ·

At a glance — Architecture · 62% · Adequate · gated by AX7 ·

At a glance — Maturity · 59% · Adequate · gated by M2 ·

At a glance — Readiness · 45% · Weak · gated by P1, P3 ·

At a glance — Security · 100% · Exemplary ·

At a glance — Performance · 61% · Adequate ·

Roadmap

File quality

How the grades work

Methodology & how to trust this report

Tools & methods

Run transparency — what happened this run

Limitations & what we did not check

Per-dimension blind spots

Dimensions

Frontend & cross-cutting dimensions

Reference — by lens

Appendix A — Findings (grouped)

Appendix B — Reproduction & audit trail

Downloadable artifacts