Public report of swiftlang/sourcekit-lsp, published 14 November 2026. It has the same score, grades and number of
findings as the full report. The details of security findings (where they are in the code, which known
vulnerabilities and which passwords or keys were found) are left out, so nobody can use them against the project.
Public
Executive reportMeasured under the Code Assurance Index, an open standard for code quality, using its published scoring rules (rubric version 2026.11.4). Assert signed this survey and filed it in the standard's public register, where anyone can look it up by its survey ID. Check this survey →
Signed and filed in the standard's public register, 14 November 2026, 22:18 UTC · Survey ID cd_c4870d6d60a04fc59ef35656be2ef310
swiftlang/sourcekit-lsp
Measured 14 November 2026, 22:16 UTC, at code version c2eb46c
Test reliability is not measured: The suite could not be re-run, but the repository declares tests of its own unreliable.
CAI scoreAdequate
CriticalWeakAdequateStrongExemplary
Up 1 since the last survey
The score is built from these lenses. Each lens grades one area of the code, such as how easy it is to change or how well it is protected. The weakest lens counts most, so one weak area pulls the score down instead of being averaged away.
A medium codebase: 58,509 lines of product code in 58 projects, tests not counted · Estimated rebuild effort: about 0.8 person-years · Weakest lens: Production Readiness, 30
Findings by how serious they are
3 critical344 serious276 minor
24 dimensions are left out of the score. For each one, we either couldn't measure it in this code, or found no evidence of the safeguard we look for, such as a tested backup restore. They count neither for nor against the score, and Limitations lists each one with its reason.
This survey was produced by
Canine Code Analyzer
Producer
Canine Development
Analyzer
Canine Code Analyzer engine 1.0.0
Measured
14 November 2026, 22:16 UTC
A measurement, not a certificate. The Code Assurance Index records a number
together with the evidence it was worked out from, so anyone can recalculate it, but it doesn't certify or guarantee
the code. The standard was written by Canine Development, which also builds the Canine Code Analyzer. It is open to any tool that
implements it, and today the Canine Code Analyzer is the only one that does.
The score is deterministic, which means the same code always gets the same score. We work it out with tools that follow published rules, and an AI model never decides it, so anyone who applies the same rules to the same code gets the same number. How it is done is explained under Methodology ▸
37of 37 dimensions measured by tools.
600of 623 findings point to an exact file and line, so you can open each one in the code. The other 23 concern the repository as a whole, such as missing documentation.
37dimensions across 6 lenses, read from 58,509 lines of product code in 58 projects.
swiftlang/sourcekit-lsp falls short of our standard for production because we found no working pipeline that builds or tests changes to the code and no automated security scanning of the code, its secrets or its dependencies. It scores 53 out of 100 and is rated Adequate, and none of its three critical findings concern security.
Production Readiness, at 30, is the weakest lens and counts most in the score. The best first step for the work it takes is recording design decisions, worth about 5 points. Adding an automated build and test pipeline would lift Production Readiness itself, worth about 8 points. Raising Production Readiness to 70 would lift the score to about 71.
Two parts of the code are no longer understood by anyone working on it. Having someone learn the forgotten files would close this risk. The test the project itself marks as unreliable needs fixing or deleting.
The product code is 58,509 lines, about €110,000 to rebuild.
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 forThe 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.
If Production Readiness rose from 30 to 70, the lowest score rated Strong, the score would rise from 53 to about 71.
Code composition: what the lines of code are
Product code 52%Tests 48%
New since the last survey: 60 findings
These 60 critical or serious findings weren't in the previous survey, on 28 October 2026.
Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) Sources/SKUtilities/LineTable.swift
Code Duplication · Edited copy of a member (30 corresponding lines) Sources/SwiftSourceKitPlugin/SKDResponseArrayBuilder.swift
Code Duplication · Edited copy of a member (29 corresponding lines) Sources/SwiftLanguageService/CodeCompletionSession.swift
Code Duplication · Edited copy of a member (24 corresponding lines) Sources/SourceKitD/SKDRequestArray.swift
Code Duplication · Edited copy of a member (41 corresponding lines) Sources/SwiftSyntaxCodeActions/PackageManifestEdits.swift
Code Duplication · Edited copy of a member (20 corresponding lines) Sources/Diagnose/DiagnoseCommand.swift
Code Duplication · Edited copy of a member (33 corresponding lines) Sources/SwiftLanguageService/SelectionRange.swift
Code Duplication · Edited copy of a member (17 corresponding lines) Sources/SwiftSyntaxCodeActions/GenerateEnumCaseAccessors.swift
Code Duplication · Edited copy of a member (21 corresponding lines) Sources/SKUtilities/LineTable.swift
Code Duplication · Edited copy of a member (20 corresponding lines) Sources/BuildServerIntegration/BuildTargetIdentifierExtensions.swift
Code Duplication · Edited copy of a member (20 corresponding lines) Sources/BuildServerIntegration/BuildTargetIdentifierExtensions.swift
Code Duplication · Edited copy of a member (18 corresponding lines) Sources/BuildServerIntegration/SwiftToolchainResolver.swift
Code Duplication · Edited copy of a member (25 corresponding lines) Sources/SemanticIndex/CheckedIndex.swift
Code Duplication · Edited copy of a member (30 corresponding lines) Sources/BuildServerIntegration/BuildServerMessageDependencyTracker.swift
Code Duplication · Edited copy of a member (25 corresponding lines) Sources/CompletionScoring/Text/Pattern.swift
Code Duplication · Edited copy of a member (17 corresponding lines) Sources/SourceKitLSP/LSP+CopiedFileMap.swift
Code Duplication · Edited copy of a member (19 corresponding lines) Sources/BuildServerIntegration/SplitShellCommand.swift
Code Duplication · Edited copies of one member (4 members, 12+ corresponding lines) Sources/Diagnose/SourceReducer.swift
Code Duplication · Edited copy of a member (15 corresponding lines) Sources/SwiftLanguageService/SwiftTestingScanner.swift
Code Duplication · Edited copy of a member (11 corresponding lines) Sources/CompletionScoring/Semantics/Components/ModuleProximity.swift
Code Duplication · Edited copy of a member (10 corresponding lines) Sources/SKTestSupport/FileManager+findFiles.swift
Code Duplication · Edited copy of a member (11 corresponding lines) Sources/BuildServerIntegration/FixedCompilationDatabaseBuildServer.swift
Code Duplication · Edited copy of a member (17 corresponding lines) Sources/CompletionScoring/Text/Pattern.swift
Code Duplication · Edited copy of a member (12 corresponding lines) Sources/SwiftLanguageService/AdjustPositionToStartOfArgument.swift
Code Duplication · Edited copy of a member (19 corresponding lines) Sources/SourceKitLSP/CapabilityRegistry.swift
Code Duplication · Edited copies of one member (3 members, 9+ corresponding lines) Sources/SourceKitLSP/DocumentSnapshot+PositionConversions.swift
Code Duplication · Edited copy of a member (12 corresponding lines) Sources/SwiftLanguageService/SelectionRange.swift
Code Duplication · Edited copy of a member (14 corresponding lines) Sources/SwiftSyntaxCodeActions/AddDocumentation.swift
Code Duplication · Edited copy of a member (14 corresponding lines) Sources/SwiftLanguageService/CodeCompletionSession.swift
Code Duplication · Edited copy of a member (12 corresponding lines) Sources/BuildServerIntegration/FixedCompilationDatabaseBuildServer.swift
Code Duplication · Edited copy of a member (10 corresponding lines) Sources/Diagnose/CommandLineArgumentsReducer.swift
Code Duplication · Edited copies of one member (4 members, 12+ corresponding lines) Sources/CompletionScoring/Semantics/Components/Availability.swift
Code Duplication · Edited copy of a member (12 corresponding lines) Sources/SwiftSourceKitPlugin/CompletionProvider.swift
Code Duplication · Edited copy of a member (18 corresponding lines) Sources/ToolchainRegistry/ToolchainRegistry.swift
Code Duplication · Edited copy of a member (7 corresponding lines) Sources/BuildServerIntegration/CompilationDatabase.swift
Code Duplication · Edited copies of one member (6 members, 12+ corresponding lines) Sources/CompletionScoring/Semantics/Components/Availability.swift
Code Duplication · Edited copy of a member (8 corresponding lines) Sources/CompletionScoring/Text/CandidateBatch.swift
Code Duplication · Edited copy of a member (7 corresponding lines) Sources/CompletionScoring/Text/CandidateBatch.swift
Code Duplication · Edited copy of a member (8 corresponding lines) Sources/SKTestSupport/Assertions.swift
Code Duplication · Edited copy of a member (8 corresponding lines) Sources/DocumentationLanguageService/DocCSymbolInformation.swift
Code Duplication · Edited copies of one member (3 members, 9+ corresponding lines) Sources/SourceKitD/SourceKitDCore.swift
Code Duplication · Edited copies of one member (3 members, 8+ corresponding lines) Sources/SKTestSupport/Assertions.swift
Code Duplication · Edited copy of a member (11 corresponding lines) Sources/SourceKitD/SKDResponseArray.swift
Code Duplication · Edited copies of one member (3 members, 12+ corresponding lines) Sources/CompletionScoring/Semantics/SemanticClassification.swift
Code Duplication · Edited copy of a member (8 corresponding lines) Sources/BuildServerIntegration/BuildSettingsLogger.swift
Code Duplication · Edited copy of a member (7 corresponding lines) Sources/SourceKitD/SKDRequestDictionary.swift
Code Duplication · Edited copy of a member (6 corresponding lines) Sources/CompletionScoring/Utilities/Serialization/Conformances/Array+BinaryCodable.swift
We compare 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: 14 findings
These 14 critical or serious findings were in the previous survey, on 28 October 2026, and are gone from this one.
Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) Sources/SourceKitD/sourcekitd_functions.swift
€36,000 to €180,000, for 606 to 1,921 hours of work, about 0.8 person-years for 1 to 2 engineers
Difficulty of the problem
Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write.
Quality factor
×0.7 at a score of 53. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it.
Size
Medium: 58,509 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: We price 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.
1
Resolve the 1 No ADRs found finding(s) in ADR Quality — start with Package.swift.
Raises the score by about 5 points · Low effort · ADR Quality
2
Add a CI workflow that builds and runs the test suite on every push/PR.
Raises the score by about 8 points · Medium effort · CI/CD gates
3
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.
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 €110,000 to build again, about 0.8 person-years of work. Its weakest lens is Production Readiness, at 30 (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
Resolve the 1 No ADRs found finding(s) in ADR Quality. Of all the actions in this report, it raises the score most for the work it takes: about 5 points for low effort, because it clears the 1 ADR Quality findings. The next survey will show the change in the score.
Based on: the ranked actions in Top priorities, by score gain and effort
What hard-to-read code costs each year · Cost
Four dimensions measure how easy the code is to work in: two measure how tangled its logic is, one how much of it is copied, and one how well each part sticks to a single job. In this codebase they average 7.3 out of 10. Code at that level is slower to change than clean code, and we estimate the extra work at 2% to 5% on every change. The history of the code shows how much it changes: about 9,021 lines over the last 90 days, which is about 36,585 lines a year. At that pace, the extra work comes to an estimated 1.8 to 12.2 engineer-days a year, and it grows as more code changes.
How this is estimated: The number of changed lines is measured from the history of the code. The rest rests on two assumptions of our own: code scoring 8 out of 10 or more adds no extra work, and each point below 8 adds 2.5% to 5.6% to every change, never less than 2% to 5% and never more than 40% to 60% in all; and an engineer changes 150 to 400 lines in a day. The result is a range for planning, not a measurement.
Based on: Cyclomatic Complexity · Cognitive Complexity · Code Duplication · Cohesion (LCOM4) · the code's change history
What to do: Start with the files listed under Churn × Complexity Hotspots, which change often and are hard to read, because that is where the extra work is paid most often.
Architecture — module dependency graph
Project dependencies, layered top-to-bottom; arrows show direction. Any dashed red edge points upward or sideways, which only happens where the projects form a dependency cycle. A graph without cycles has none.
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.
27 modules, with 157 dependencies between them. One loop runs through 20 of the modules, marked above the diagonal.
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.
SwiftExtensions uses SemanticIndex, so a change to SemanticIndex can break SwiftExtensions, while a change to SwiftExtensions can't break SemanticIndex.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
5→24 SwiftExtensions uses BuildServerIntegrationpart of a loop✕
Connections
1 pair of types, where a type in SwiftExtensions uses a type in BuildServerIntegration.
SwiftExtensions uses BuildServerIntegration, so a change to BuildServerIntegration can break SwiftExtensions, while a change to SwiftExtensions can't break BuildServerIntegration.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
6→9 SwiftSourceKitPluginCommon uses SourceKitDpart of a loop✕
Connections
2 pairs of types, where a type in SwiftSourceKitPluginCommon uses a type in SourceKitD.
SwiftSourceKitPluginCommon uses SourceKitD, so a change to SourceKitD can break SwiftSourceKitPluginCommon, while a change to SwiftSourceKitPluginCommon can't break SourceKitD.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
6→17 SwiftSourceKitPluginCommon uses SwiftSourceKitPluginpart of a loop✕
Connections
5 pairs of types, where a type in SwiftSourceKitPluginCommon uses a type in SwiftSourceKitPlugin.
SwiftSourceKitPluginCommon uses SwiftSourceKitPlugin, so a change to SwiftSourceKitPlugin can break SwiftSourceKitPluginCommon, while a change to SwiftSourceKitPluginCommon can't break SwiftSourceKitPlugin.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
6→22 SwiftSourceKitPluginCommon uses ClangLanguageServicepart of a loop✕
Connections
1 pair of types, where a type in SwiftSourceKitPluginCommon uses a type in ClangLanguageService.
SwiftSourceKitPluginCommon uses ClangLanguageService, so a change to ClangLanguageService can break SwiftSourceKitPluginCommon, while a change to SwiftSourceKitPluginCommon can't break ClangLanguageService.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
6→23 SwiftSourceKitPluginCommon uses CompletionScoringpart of a loop✕
Connections
4 pairs of types, where a type in SwiftSourceKitPluginCommon uses a type in CompletionScoring.
SwiftSourceKitPluginCommon uses CompletionScoring, so a change to CompletionScoring can break SwiftSourceKitPluginCommon, while a change to SwiftSourceKitPluginCommon can't break CompletionScoring.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
7→11 SwiftSyntaxCodeActions uses SwiftLanguageServicepart of a loop✕
Connections
48 pairs of types, where a type in SwiftSyntaxCodeActions uses a type in SwiftLanguageService. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
SwiftSyntaxCodeActions uses SwiftLanguageService, so a change to SwiftLanguageService can break SwiftSyntaxCodeActions, while a change to SwiftSyntaxCodeActions can't break SwiftLanguageService.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
7→17 SwiftSyntaxCodeActions uses SwiftSourceKitPluginpart of a loop✕
Connections
15 pairs of types, where a type in SwiftSyntaxCodeActions uses a type in SwiftSourceKitPlugin.
SwiftSyntaxCodeActions uses SwiftSourceKitPlugin, so a change to SwiftSourceKitPlugin can break SwiftSyntaxCodeActions, while a change to SwiftSyntaxCodeActions can't break SwiftSourceKitPlugin.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
7→19 SwiftSyntaxCodeActions uses Diagnosepart of a loop✕
Connections
3 pairs of types, where a type in SwiftSyntaxCodeActions uses a type in Diagnose.
SwiftSyntaxCodeActions uses Diagnose, so a change to Diagnose can break SwiftSyntaxCodeActions, while a change to SwiftSyntaxCodeActions can't break Diagnose.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
7→20 SwiftSyntaxCodeActions uses SourceKitLSPpart of a loop✕
Connections
13 pairs of types, where a type in SwiftSyntaxCodeActions uses a type in SourceKitLSP.
SwiftSyntaxCodeActions uses SourceKitLSP, so a change to SourceKitLSP can break SwiftSyntaxCodeActions, while a change to SwiftSyntaxCodeActions can't break SourceKitLSP.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
7→24 SwiftSyntaxCodeActions uses BuildServerIntegrationpart of a loop✕
Connections
31 pairs of types, where a type in SwiftSyntaxCodeActions uses a type in BuildServerIntegration. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
SwiftSyntaxCodeActions uses BuildServerIntegration, so a change to BuildServerIntegration can break SwiftSyntaxCodeActions, while a change to SwiftSyntaxCodeActions can't break BuildServerIntegration.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
8→17 TSCExtensions uses SwiftSourceKitPluginpart of a loop✕
Connections
1 pair of types, where a type in TSCExtensions uses a type in SwiftSourceKitPlugin.
TSCExtensions uses SwiftSourceKitPlugin, so a change to SwiftSourceKitPlugin can break TSCExtensions, while a change to TSCExtensions can't break SwiftSourceKitPlugin.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
8→23 TSCExtensions uses CompletionScoringpart of a loop✕
Connections
1 pair of types, where a type in TSCExtensions uses a type in CompletionScoring.
TSCExtensions uses CompletionScoring, so a change to CompletionScoring can break TSCExtensions, while a change to TSCExtensions can't break CompletionScoring.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
8→24 TSCExtensions uses BuildServerIntegrationpart of a loop✕
Connections
1 pair of types, where a type in TSCExtensions uses a type in BuildServerIntegration.
TSCExtensions uses BuildServerIntegration, so a change to BuildServerIntegration can break TSCExtensions, while a change to TSCExtensions can't break BuildServerIntegration.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
SourceKitD uses SwiftSourceKitPluginCommon, so a change to SwiftSourceKitPluginCommon can break SourceKitD, while a change to SourceKitD can't break SwiftSourceKitPluginCommon.
Position
Below the diagonal: SourceKitD uses a module listed above it, which is the healthy direction.
9→17 SourceKitD uses SwiftSourceKitPluginpart of a loop✕
Connections
8 pairs of types, where a type in SourceKitD uses a type in SwiftSourceKitPlugin.
SourceKitD uses SwiftSourceKitPlugin, so a change to SwiftSourceKitPlugin can break SourceKitD, while a change to SourceKitD can't break SwiftSourceKitPlugin.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
SourceKitD uses BuildServerIntegration, so a change to BuildServerIntegration can break SourceKitD, while a change to SourceKitD can't break BuildServerIntegration.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
ToolchainRegistry uses SwiftSourceKitPlugin, so a change to SwiftSourceKitPlugin can break ToolchainRegistry, while a change to ToolchainRegistry can't break SwiftSourceKitPlugin.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
10→23 ToolchainRegistry uses CompletionScoringpart of a loop✕
Connections
2 pairs of types, where a type in ToolchainRegistry uses a type in CompletionScoring.
ToolchainRegistry uses CompletionScoring, so a change to CompletionScoring can break ToolchainRegistry, while a change to ToolchainRegistry can't break CompletionScoring.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
10→24 ToolchainRegistry uses BuildServerIntegrationpart of a loop✕
Connections
10 pairs of types, where a type in ToolchainRegistry uses a type in BuildServerIntegration.
ToolchainRegistry uses BuildServerIntegration, so a change to BuildServerIntegration can break ToolchainRegistry, while a change to ToolchainRegistry can't break BuildServerIntegration.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
SwiftLanguageService uses SwiftSyntaxExtensions, so a change to SwiftSyntaxExtensions can break SwiftLanguageService, while a change to SwiftLanguageService can't break SwiftSyntaxExtensions.
Position
Below the diagonal: SwiftLanguageService uses a module listed above it, which is the healthy direction.
SwiftLanguageService uses SwiftSyntaxCodeActions, so a change to SwiftSyntaxCodeActions can break SwiftLanguageService, while a change to SwiftLanguageService can't break SwiftSyntaxCodeActions.
Position
Below the diagonal: SwiftLanguageService uses a module listed above it, which is the healthy direction.
46 pairs of types, where a type in SwiftLanguageService uses a type in SourceKitD. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
SwiftLanguageService uses SourceKitD, so a change to SourceKitD can break SwiftLanguageService, while a change to SwiftLanguageService can't break SourceKitD.
Position
Below the diagonal: SwiftLanguageService uses a module listed above it, which is the healthy direction.
SwiftLanguageService uses ToolchainRegistry, so a change to ToolchainRegistry can break SwiftLanguageService, while a change to SwiftLanguageService can't break ToolchainRegistry.
Position
Below the diagonal: SwiftLanguageService uses a module listed above it, which is the healthy direction.
11→13 SwiftLanguageService uses SKTestSupportpart of a loop✕
Connections
6 pairs of types, where a type in SwiftLanguageService uses a type in SKTestSupport.
SwiftLanguageService uses SKTestSupport, so a change to SKTestSupport can break SwiftLanguageService, while a change to SwiftLanguageService can't break SKTestSupport.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
11→15 SwiftLanguageService uses SemanticIndexpart of a loop✕
Connections
2 pairs of types, where a type in SwiftLanguageService uses a type in SemanticIndex.
SwiftLanguageService uses SemanticIndex, so a change to SemanticIndex can break SwiftLanguageService, while a change to SwiftLanguageService can't break SemanticIndex.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
11→16 SwiftLanguageService uses SKUtilitiespart of a loop✕
Connections
4 pairs of types, where a type in SwiftLanguageService uses a type in SKUtilities.
SwiftLanguageService uses SKUtilities, so a change to SKUtilities can break SwiftLanguageService, while a change to SwiftLanguageService can't break SKUtilities.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
11→17 SwiftLanguageService uses SwiftSourceKitPluginpart of a loop✕
Connections
41 pairs of types, where a type in SwiftLanguageService uses a type in SwiftSourceKitPlugin. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
SwiftLanguageService uses SwiftSourceKitPlugin, so a change to SwiftSourceKitPlugin can break SwiftLanguageService, while a change to SwiftLanguageService can't break SwiftSourceKitPlugin.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
11→18 SwiftLanguageService uses SKOptionspart of a loop✕
Connections
3 pairs of types, where a type in SwiftLanguageService uses a type in SKOptions.
SwiftLanguageService uses SKOptions, so a change to SKOptions can break SwiftLanguageService, while a change to SwiftLanguageService can't break SKOptions.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
11→19 SwiftLanguageService uses Diagnosepart of a loop✕
Connections
6 pairs of types, where a type in SwiftLanguageService uses a type in Diagnose.
SwiftLanguageService uses Diagnose, so a change to Diagnose can break SwiftLanguageService, while a change to SwiftLanguageService can't break Diagnose.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
11→20 SwiftLanguageService uses SourceKitLSPpart of a loop✕
Connections
71 pairs of types, where a type in SwiftLanguageService uses a type in SourceKitLSP. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
SwiftLanguageService uses SourceKitLSP, so a change to SourceKitLSP can break SwiftLanguageService, while a change to SwiftLanguageService can't break SourceKitLSP.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
11→21 SwiftLanguageService uses LanguageServerProtocolExtensionspart of a loop✕
Connections
12 pairs of types, where a type in SwiftLanguageService uses a type in LanguageServerProtocolExtensions.
SwiftLanguageService uses LanguageServerProtocolExtensions, so a change to LanguageServerProtocolExtensions can break SwiftLanguageService, while a change to SwiftLanguageService can't break LanguageServerProtocolExtensions.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
11→22 SwiftLanguageService uses ClangLanguageServicepart of a loop✕
Connections
2 pairs of types, where a type in SwiftLanguageService uses a type in ClangLanguageService.
SwiftLanguageService uses ClangLanguageService, so a change to ClangLanguageService can break SwiftLanguageService, while a change to SwiftLanguageService can't break ClangLanguageService.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
11→24 SwiftLanguageService uses BuildServerIntegrationpart of a loop✕
Connections
47 pairs of types, where a type in SwiftLanguageService uses a type in BuildServerIntegration. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
SwiftLanguageService uses BuildServerIntegration, so a change to BuildServerIntegration can break SwiftLanguageService, while a change to SwiftLanguageService can't break BuildServerIntegration.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
SourceKitLSPDevUtils~ConfigSchemaGen uses SwiftSyntaxCodeActions, so a change to SwiftSyntaxCodeActions can break SourceKitLSPDevUtils~ConfigSchemaGen, while a change to SourceKitLSPDevUtils~ConfigSchemaGen can't break SwiftSyntaxCodeActions.
Position
Below the diagonal: SourceKitLSPDevUtils~ConfigSchemaGen uses a module listed above it, which is the healthy direction.
SourceKitLSPDevUtils~ConfigSchemaGen uses SwiftLanguageService, so a change to SwiftLanguageService can break SourceKitLSPDevUtils~ConfigSchemaGen, while a change to SourceKitLSPDevUtils~ConfigSchemaGen can't break SwiftLanguageService.
Position
Below the diagonal: SourceKitLSPDevUtils~ConfigSchemaGen uses a module listed above it, which is the healthy direction.
12→17 SourceKitLSPDevUtils~ConfigSchemaGen uses SwiftSourceKitPluginpart of a loop✕
Connections
3 pairs of types, where a type in SourceKitLSPDevUtils~ConfigSchemaGen uses a type in SwiftSourceKitPlugin.
SourceKitLSPDevUtils~ConfigSchemaGen uses SwiftSourceKitPlugin, so a change to SwiftSourceKitPlugin can break SourceKitLSPDevUtils~ConfigSchemaGen, while a change to SourceKitLSPDevUtils~ConfigSchemaGen can't break SwiftSourceKitPlugin.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
12→19 SourceKitLSPDevUtils~ConfigSchemaGen uses Diagnosepart of a loop✕
Connections
1 pair of types, where a type in SourceKitLSPDevUtils~ConfigSchemaGen uses a type in Diagnose.
SourceKitLSPDevUtils~ConfigSchemaGen uses Diagnose, so a change to Diagnose can break SourceKitLSPDevUtils~ConfigSchemaGen, while a change to SourceKitLSPDevUtils~ConfigSchemaGen can't break Diagnose.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
12→24 SourceKitLSPDevUtils~ConfigSchemaGen uses BuildServerIntegrationpart of a loop✕
Connections
11 pairs of types, where a type in SourceKitLSPDevUtils~ConfigSchemaGen uses a type in BuildServerIntegration.
SourceKitLSPDevUtils~ConfigSchemaGen uses BuildServerIntegration, so a change to BuildServerIntegration can break SourceKitLSPDevUtils~ConfigSchemaGen, while a change to SourceKitLSPDevUtils~ConfigSchemaGen can't break BuildServerIntegration.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
SKTestSupport uses SwiftSyntaxCodeActions, so a change to SwiftSyntaxCodeActions can break SKTestSupport, while a change to SKTestSupport can't break SwiftSyntaxCodeActions.
Position
Below the diagonal: SKTestSupport uses a module listed above it, which is the healthy direction.
SKTestSupport uses ToolchainRegistry, so a change to ToolchainRegistry can break SKTestSupport, while a change to SKTestSupport can't break ToolchainRegistry.
Position
Below the diagonal: SKTestSupport uses a module listed above it, which is the healthy direction.
SKTestSupport uses SwiftLanguageService, so a change to SwiftLanguageService can break SKTestSupport, while a change to SKTestSupport can't break SwiftLanguageService.
Position
Below the diagonal: SKTestSupport uses a module listed above it, which is the healthy direction.
SKTestSupport uses SourceKitLSPDevUtils~ConfigSchemaGen, so a change to SourceKitLSPDevUtils~ConfigSchemaGen can break SKTestSupport, while a change to SKTestSupport can't break SourceKitLSPDevUtils~ConfigSchemaGen.
Position
Below the diagonal: SKTestSupport uses a module listed above it, which is the healthy direction.
13→17 SKTestSupport uses SwiftSourceKitPluginpart of a loop✕
Connections
17 pairs of types, where a type in SKTestSupport uses a type in SwiftSourceKitPlugin.
SKTestSupport uses SwiftSourceKitPlugin, so a change to SwiftSourceKitPlugin can break SKTestSupport, while a change to SKTestSupport can't break SwiftSourceKitPlugin.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
SKTestSupport uses LanguageServerProtocolExtensions, so a change to LanguageServerProtocolExtensions can break SKTestSupport, while a change to SKTestSupport can't break LanguageServerProtocolExtensions.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
13→23 SKTestSupport uses CompletionScoringpart of a loop✕
Connections
8 pairs of types, where a type in SKTestSupport uses a type in CompletionScoring.
SKTestSupport uses CompletionScoring, so a change to CompletionScoring can break SKTestSupport, while a change to SKTestSupport can't break CompletionScoring.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
13→24 SKTestSupport uses BuildServerIntegrationpart of a loop✕
Connections
45 pairs of types, where a type in SKTestSupport uses a type in BuildServerIntegration. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
SKTestSupport uses BuildServerIntegration, so a change to BuildServerIntegration can break SKTestSupport, while a change to SKTestSupport can't break BuildServerIntegration.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
DocumentationLanguageService uses SourceKitD, so a change to SourceKitD can break DocumentationLanguageService, while a change to DocumentationLanguageService can't break SourceKitD.
Position
Below the diagonal: DocumentationLanguageService uses a module listed above it, which is the healthy direction.
DocumentationLanguageService uses ToolchainRegistry, so a change to ToolchainRegistry can break DocumentationLanguageService, while a change to DocumentationLanguageService can't break ToolchainRegistry.
Position
Below the diagonal: DocumentationLanguageService uses a module listed above it, which is the healthy direction.
DocumentationLanguageService uses SKTestSupport, so a change to SKTestSupport can break DocumentationLanguageService, while a change to DocumentationLanguageService can't break SKTestSupport.
Position
Below the diagonal: DocumentationLanguageService uses a module listed above it, which is the healthy direction.
14→15 DocumentationLanguageService uses SemanticIndexpart of a loop✕
Connections
1 pair of types, where a type in DocumentationLanguageService uses a type in SemanticIndex.
DocumentationLanguageService uses SemanticIndex, so a change to SemanticIndex can break DocumentationLanguageService, while a change to DocumentationLanguageService can't break SemanticIndex.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
14→16 DocumentationLanguageService uses SKUtilitiespart of a loop✕
Connections
1 pair of types, where a type in DocumentationLanguageService uses a type in SKUtilities.
DocumentationLanguageService uses SKUtilities, so a change to SKUtilities can break DocumentationLanguageService, while a change to DocumentationLanguageService can't break SKUtilities.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
14→17 DocumentationLanguageService uses SwiftSourceKitPluginpart of a loop✕
Connections
6 pairs of types, where a type in DocumentationLanguageService uses a type in SwiftSourceKitPlugin.
DocumentationLanguageService uses SwiftSourceKitPlugin, so a change to SwiftSourceKitPlugin can break DocumentationLanguageService, while a change to DocumentationLanguageService can't break SwiftSourceKitPlugin.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
14→18 DocumentationLanguageService uses SKOptionspart of a loop✕
Connections
1 pair of types, where a type in DocumentationLanguageService uses a type in SKOptions.
DocumentationLanguageService uses SKOptions, so a change to SKOptions can break DocumentationLanguageService, while a change to DocumentationLanguageService can't break SKOptions.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
14→19 DocumentationLanguageService uses Diagnosepart of a loop✕
Connections
1 pair of types, where a type in DocumentationLanguageService uses a type in Diagnose.
DocumentationLanguageService uses Diagnose, so a change to Diagnose can break DocumentationLanguageService, while a change to DocumentationLanguageService can't break Diagnose.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
14→20 DocumentationLanguageService uses SourceKitLSPpart of a loop✕
Connections
8 pairs of types, where a type in DocumentationLanguageService uses a type in SourceKitLSP.
DocumentationLanguageService uses SourceKitLSP, so a change to SourceKitLSP can break DocumentationLanguageService, while a change to DocumentationLanguageService can't break SourceKitLSP.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
14→21 DocumentationLanguageService uses LanguageServerProtocolExtensionspart of a loop✕
Connections
1 pair of types, where a type in DocumentationLanguageService uses a type in LanguageServerProtocolExtensions.
DocumentationLanguageService uses LanguageServerProtocolExtensions, so a change to LanguageServerProtocolExtensions can break DocumentationLanguageService, while a change to DocumentationLanguageService can't break LanguageServerProtocolExtensions.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
14→23 DocumentationLanguageService uses CompletionScoringpart of a loop✕
Connections
1 pair of types, where a type in DocumentationLanguageService uses a type in CompletionScoring.
DocumentationLanguageService uses CompletionScoring, so a change to CompletionScoring can break DocumentationLanguageService, while a change to DocumentationLanguageService can't break CompletionScoring.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
14→24 DocumentationLanguageService uses BuildServerIntegrationpart of a loop✕
Connections
25 pairs of types, where a type in DocumentationLanguageService uses a type in BuildServerIntegration.
DocumentationLanguageService uses BuildServerIntegration, so a change to BuildServerIntegration can break DocumentationLanguageService, while a change to DocumentationLanguageService can't break BuildServerIntegration.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
SemanticIndex uses ToolchainRegistry, so a change to ToolchainRegistry can break SemanticIndex, while a change to SemanticIndex can't break ToolchainRegistry.
Position
Below the diagonal: SemanticIndex uses a module listed above it, which is the healthy direction.
SemanticIndex uses DocumentationLanguageService, so a change to DocumentationLanguageService can break SemanticIndex, while a change to SemanticIndex can't break DocumentationLanguageService.
Position
Below the diagonal: SemanticIndex uses a module listed above it, which is the healthy direction.
15→17 SemanticIndex uses SwiftSourceKitPluginpart of a loop✕
Connections
18 pairs of types, where a type in SemanticIndex uses a type in SwiftSourceKitPlugin.
SemanticIndex uses SwiftSourceKitPlugin, so a change to SwiftSourceKitPlugin can break SemanticIndex, while a change to SemanticIndex can't break SwiftSourceKitPlugin.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
SemanticIndex uses LanguageServerProtocolExtensions, so a change to LanguageServerProtocolExtensions can break SemanticIndex, while a change to SemanticIndex can't break LanguageServerProtocolExtensions.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
15→22 SemanticIndex uses ClangLanguageServicepart of a loop✕
Connections
1 pair of types, where a type in SemanticIndex uses a type in ClangLanguageService.
SemanticIndex uses ClangLanguageService, so a change to ClangLanguageService can break SemanticIndex, while a change to SemanticIndex can't break ClangLanguageService.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
15→23 SemanticIndex uses CompletionScoringpart of a loop✕
Connections
3 pairs of types, where a type in SemanticIndex uses a type in CompletionScoring.
SemanticIndex uses CompletionScoring, so a change to CompletionScoring can break SemanticIndex, while a change to SemanticIndex can't break CompletionScoring.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
15→24 SemanticIndex uses BuildServerIntegrationpart of a loop✕
Connections
28 pairs of types, where a type in SemanticIndex uses a type in BuildServerIntegration. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
SemanticIndex uses BuildServerIntegration, so a change to BuildServerIntegration can break SemanticIndex, while a change to SemanticIndex can't break BuildServerIntegration.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
SKUtilities uses SwiftSyntaxCodeActions, so a change to SwiftSyntaxCodeActions can break SKUtilities, while a change to SKUtilities can't break SwiftSyntaxCodeActions.
Position
Below the diagonal: SKUtilities uses a module listed above it, which is the healthy direction.
SKUtilities uses SwiftLanguageService, so a change to SwiftLanguageService can break SKUtilities, while a change to SKUtilities can't break SwiftLanguageService.
Position
Below the diagonal: SKUtilities uses a module listed above it, which is the healthy direction.
SKUtilities uses SwiftSourceKitPlugin, so a change to SwiftSourceKitPlugin can break SKUtilities, while a change to SKUtilities can't break SwiftSourceKitPlugin.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
16→20 SKUtilities uses SourceKitLSPpart of a loop✕
Connections
1 pair of types, where a type in SKUtilities uses a type in SourceKitLSP.
The types involved
SKUtilities.Dictionary → SourceKitLSP.Sequence
Direction
SKUtilities uses SourceKitLSP, so a change to SourceKitLSP can break SKUtilities, while a change to SKUtilities can't break SourceKitLSP.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
16→23 SKUtilities uses CompletionScoringpart of a loop✕
Connections
4 pairs of types, where a type in SKUtilities uses a type in CompletionScoring.
SKUtilities uses CompletionScoring, so a change to CompletionScoring can break SKUtilities, while a change to SKUtilities can't break CompletionScoring.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
16→24 SKUtilities uses BuildServerIntegrationpart of a loop✕
Connections
1 pair of types, where a type in SKUtilities uses a type in BuildServerIntegration.
SKUtilities uses BuildServerIntegration, so a change to BuildServerIntegration can break SKUtilities, while a change to SKUtilities can't break BuildServerIntegration.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
SwiftSourceKitPlugin uses SwiftExtensions, so a change to SwiftExtensions can break SwiftSourceKitPlugin, while a change to SwiftSourceKitPlugin can't break SwiftExtensions.
Position
Below the diagonal: SwiftSourceKitPlugin uses a module listed above it, which is the healthy direction.
SwiftSourceKitPlugin uses SwiftSourceKitPluginCommon, so a change to SwiftSourceKitPluginCommon can break SwiftSourceKitPlugin, while a change to SwiftSourceKitPlugin can't break SwiftSourceKitPluginCommon.
Position
Below the diagonal: SwiftSourceKitPlugin uses a module listed above it, which is the healthy direction.
SwiftSourceKitPlugin uses SourceKitD, so a change to SourceKitD can break SwiftSourceKitPlugin, while a change to SwiftSourceKitPlugin can't break SourceKitD.
Position
Below the diagonal: SwiftSourceKitPlugin uses a module listed above it, which is the healthy direction.
SwiftSourceKitPlugin uses SwiftLanguageService, so a change to SwiftLanguageService can break SwiftSourceKitPlugin, while a change to SwiftSourceKitPlugin can't break SwiftLanguageService.
Position
Below the diagonal: SwiftSourceKitPlugin uses a module listed above it, which is the healthy direction.
SwiftSourceKitPlugin uses SKUtilities, so a change to SKUtilities can break SwiftSourceKitPlugin, while a change to SwiftSourceKitPlugin can't break SKUtilities.
Position
Below the diagonal: SwiftSourceKitPlugin uses a module listed above it, which is the healthy direction.
17→20 SwiftSourceKitPlugin uses SourceKitLSPpart of a loop✕
Connections
1 pair of types, where a type in SwiftSourceKitPlugin uses a type in SourceKitLSP.
SwiftSourceKitPlugin uses SourceKitLSP, so a change to SourceKitLSP can break SwiftSourceKitPlugin, while a change to SwiftSourceKitPlugin can't break SourceKitLSP.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
17→22 SwiftSourceKitPlugin uses ClangLanguageServicepart of a loop✕
Connections
2 pairs of types, where a type in SwiftSourceKitPlugin uses a type in ClangLanguageService.
SwiftSourceKitPlugin uses ClangLanguageService, so a change to ClangLanguageService can break SwiftSourceKitPlugin, while a change to SwiftSourceKitPlugin can't break ClangLanguageService.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
17→23 SwiftSourceKitPlugin uses CompletionScoringpart of a loop✕
Connections
28 pairs of types, where a type in SwiftSourceKitPlugin uses a type in CompletionScoring. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
SwiftSourceKitPlugin uses CompletionScoring, so a change to CompletionScoring can break SwiftSourceKitPlugin, while a change to SwiftSourceKitPlugin can't break CompletionScoring.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
17→24 SwiftSourceKitPlugin uses BuildServerIntegrationpart of a loop✕
Connections
20 pairs of types, where a type in SwiftSourceKitPlugin uses a type in BuildServerIntegration.
SwiftSourceKitPlugin uses BuildServerIntegration, so a change to BuildServerIntegration can break SwiftSourceKitPlugin, while a change to SwiftSourceKitPlugin can't break BuildServerIntegration.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
SKOptions uses SwiftSourceKitPlugin, so a change to SwiftSourceKitPlugin can break SKOptions, while a change to SKOptions can't break SwiftSourceKitPlugin.
Position
Below the diagonal: SKOptions uses a module listed above it, which is the healthy direction.
18→21 SKOptions uses LanguageServerProtocolExtensionspart of a loop✕
Connections
1 pair of types, where a type in SKOptions uses a type in LanguageServerProtocolExtensions.
SKOptions uses LanguageServerProtocolExtensions, so a change to LanguageServerProtocolExtensions can break SKOptions, while a change to SKOptions can't break LanguageServerProtocolExtensions.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
18→24 SKOptions uses BuildServerIntegrationpart of a loop✕
Connections
12 pairs of types, where a type in SKOptions uses a type in BuildServerIntegration.
SKOptions uses BuildServerIntegration, so a change to BuildServerIntegration can break SKOptions, while a change to SKOptions can't break BuildServerIntegration.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
Diagnose uses SwiftSyntaxCodeActions, so a change to SwiftSyntaxCodeActions can break Diagnose, while a change to Diagnose can't break SwiftSyntaxCodeActions.
Position
Below the diagonal: Diagnose uses a module listed above it, which is the healthy direction.
Diagnose uses SwiftLanguageService, so a change to SwiftLanguageService can break Diagnose, while a change to Diagnose can't break SwiftLanguageService.
Position
Below the diagonal: Diagnose uses a module listed above it, which is the healthy direction.
Diagnose uses SwiftSourceKitPlugin, so a change to SwiftSourceKitPlugin can break Diagnose, while a change to Diagnose can't break SwiftSourceKitPlugin.
Position
Below the diagonal: Diagnose uses a module listed above it, which is the healthy direction.
Diagnose uses CompletionScoring, so a change to CompletionScoring can break Diagnose, while a change to Diagnose can't break CompletionScoring.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
19→24 Diagnose uses BuildServerIntegrationpart of a loop✕
Connections
31 pairs of types, where a type in Diagnose uses a type in BuildServerIntegration. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
Diagnose uses BuildServerIntegration, so a change to BuildServerIntegration can break Diagnose, while a change to Diagnose can't break BuildServerIntegration.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
SourceKitLSP uses ToolchainRegistry, so a change to ToolchainRegistry can break SourceKitLSP, while a change to SourceKitLSP can't break ToolchainRegistry.
Position
Below the diagonal: SourceKitLSP uses a module listed above it, which is the healthy direction.
SourceKitLSP uses SwiftLanguageService, so a change to SwiftLanguageService can break SourceKitLSP, while a change to SourceKitLSP can't break SwiftLanguageService.
Position
Below the diagonal: SourceKitLSP uses a module listed above it, which is the healthy direction.
SourceKitLSP uses DocumentationLanguageService, so a change to DocumentationLanguageService can break SourceKitLSP, while a change to SourceKitLSP can't break DocumentationLanguageService.
Position
Below the diagonal: SourceKitLSP uses a module listed above it, which is the healthy direction.
32 pairs of types, where a type in SourceKitLSP uses a type in SwiftSourceKitPlugin. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
SourceKitLSP uses SwiftSourceKitPlugin, so a change to SwiftSourceKitPlugin can break SourceKitLSP, while a change to SourceKitLSP can't break SwiftSourceKitPlugin.
Position
Below the diagonal: SourceKitLSP uses a module listed above it, which is the healthy direction.
SourceKitLSP uses Diagnose, so a change to Diagnose can break SourceKitLSP, while a change to SourceKitLSP can't break Diagnose.
Position
Below the diagonal: SourceKitLSP uses a module listed above it, which is the healthy direction.
20→21 SourceKitLSP uses LanguageServerProtocolExtensionspart of a loop✕
Connections
33 pairs of types, where a type in SourceKitLSP uses a type in LanguageServerProtocolExtensions. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
SourceKitLSP uses LanguageServerProtocolExtensions, so a change to LanguageServerProtocolExtensions can break SourceKitLSP, while a change to SourceKitLSP can't break LanguageServerProtocolExtensions.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
20→22 SourceKitLSP uses ClangLanguageServicepart of a loop✕
Connections
1 pair of types, where a type in SourceKitLSP uses a type in ClangLanguageService.
SourceKitLSP uses ClangLanguageService, so a change to ClangLanguageService can break SourceKitLSP, while a change to SourceKitLSP can't break ClangLanguageService.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
20→23 SourceKitLSP uses CompletionScoringpart of a loop✕
Connections
4 pairs of types, where a type in SourceKitLSP uses a type in CompletionScoring.
SourceKitLSP uses CompletionScoring, so a change to CompletionScoring can break SourceKitLSP, while a change to SourceKitLSP can't break CompletionScoring.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
20→24 SourceKitLSP uses BuildServerIntegrationpart of a loop✕
Connections
39 pairs of types, where a type in SourceKitLSP uses a type in BuildServerIntegration. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
SourceKitLSP uses BuildServerIntegration, so a change to BuildServerIntegration can break SourceKitLSP, while a change to SourceKitLSP can't break BuildServerIntegration.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
LanguageServerProtocolExtensions uses SwiftSourceKitPlugin, so a change to SwiftSourceKitPlugin can break LanguageServerProtocolExtensions, while a change to LanguageServerProtocolExtensions can't break SwiftSourceKitPlugin.
Position
Below the diagonal: LanguageServerProtocolExtensions uses a module listed above it, which is the healthy direction.
LanguageServerProtocolExtensions uses SourceKitLSP, so a change to SourceKitLSP can break LanguageServerProtocolExtensions, while a change to LanguageServerProtocolExtensions can't break SourceKitLSP.
Position
Below the diagonal: LanguageServerProtocolExtensions uses a module listed above it, which is the healthy direction.
21→24 LanguageServerProtocolExtensions uses BuildServerIntegrationpart of a loop✕
Connections
3 pairs of types, where a type in LanguageServerProtocolExtensions uses a type in BuildServerIntegration.
LanguageServerProtocolExtensions uses BuildServerIntegration, so a change to BuildServerIntegration can break LanguageServerProtocolExtensions, while a change to LanguageServerProtocolExtensions can't break BuildServerIntegration.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
ClangLanguageService uses ToolchainRegistry, so a change to ToolchainRegistry can break ClangLanguageService, while a change to ClangLanguageService can't break ToolchainRegistry.
Position
Below the diagonal: ClangLanguageService uses a module listed above it, which is the healthy direction.
ClangLanguageService uses SwiftLanguageService, so a change to SwiftLanguageService can break ClangLanguageService, while a change to ClangLanguageService can't break SwiftLanguageService.
Position
Below the diagonal: ClangLanguageService uses a module listed above it, which is the healthy direction.
ClangLanguageService uses SKTestSupport, so a change to SKTestSupport can break ClangLanguageService, while a change to ClangLanguageService can't break SKTestSupport.
Position
Below the diagonal: ClangLanguageService uses a module listed above it, which is the healthy direction.
ClangLanguageService uses SemanticIndex, so a change to SemanticIndex can break ClangLanguageService, while a change to ClangLanguageService can't break SemanticIndex.
Position
Below the diagonal: ClangLanguageService uses a module listed above it, which is the healthy direction.
ClangLanguageService uses SwiftSourceKitPlugin, so a change to SwiftSourceKitPlugin can break ClangLanguageService, while a change to ClangLanguageService can't break SwiftSourceKitPlugin.
Position
Below the diagonal: ClangLanguageService uses a module listed above it, which is the healthy direction.
ClangLanguageService uses SKOptions, so a change to SKOptions can break ClangLanguageService, while a change to ClangLanguageService can't break SKOptions.
Position
Below the diagonal: ClangLanguageService uses a module listed above it, which is the healthy direction.
ClangLanguageService uses SourceKitLSP, so a change to SourceKitLSP can break ClangLanguageService, while a change to ClangLanguageService can't break SourceKitLSP.
Position
Below the diagonal: ClangLanguageService uses a module listed above it, which is the healthy direction.
ClangLanguageService uses LanguageServerProtocolExtensions, so a change to LanguageServerProtocolExtensions can break ClangLanguageService, while a change to ClangLanguageService can't break LanguageServerProtocolExtensions.
Position
Below the diagonal: ClangLanguageService uses a module listed above it, which is the healthy direction.
22→24 ClangLanguageService uses BuildServerIntegrationpart of a loop✕
Connections
5 pairs of types, where a type in ClangLanguageService uses a type in BuildServerIntegration.
ClangLanguageService uses BuildServerIntegration, so a change to BuildServerIntegration can break ClangLanguageService, while a change to ClangLanguageService can't break BuildServerIntegration.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
CompletionScoring uses SwiftLanguageService, so a change to SwiftLanguageService can break CompletionScoring, while a change to CompletionScoring can't break SwiftLanguageService.
Position
Below the diagonal: CompletionScoring uses a module listed above it, which is the healthy direction.
CompletionScoring uses SemanticIndex, so a change to SemanticIndex can break CompletionScoring, while a change to CompletionScoring can't break SemanticIndex.
Position
Below the diagonal: CompletionScoring uses a module listed above it, which is the healthy direction.
CompletionScoring uses SwiftSourceKitPlugin, so a change to SwiftSourceKitPlugin can break CompletionScoring, while a change to CompletionScoring can't break SwiftSourceKitPlugin.
Position
Below the diagonal: CompletionScoring uses a module listed above it, which is the healthy direction.
CompletionScoring uses SourceKitLSP, so a change to SourceKitLSP can break CompletionScoring, while a change to CompletionScoring can't break SourceKitLSP.
Position
Below the diagonal: CompletionScoring uses a module listed above it, which is the healthy direction.
CompletionScoring uses ClangLanguageService, so a change to ClangLanguageService can break CompletionScoring, while a change to CompletionScoring can't break ClangLanguageService.
Position
Below the diagonal: CompletionScoring uses a module listed above it, which is the healthy direction.
23→24 CompletionScoring uses BuildServerIntegrationpart of a loop✕
Connections
29 pairs of types, where a type in CompletionScoring uses a type in BuildServerIntegration. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
CompletionScoring uses BuildServerIntegration, so a change to BuildServerIntegration can break CompletionScoring, while a change to CompletionScoring can't break BuildServerIntegration.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
BuildServerIntegration uses SwiftExtensions, so a change to SwiftExtensions can break BuildServerIntegration, while a change to BuildServerIntegration can't break SwiftExtensions.
Position
Below the diagonal: BuildServerIntegration uses a module listed above it, which is the healthy direction.
BuildServerIntegration uses SwiftSyntaxCodeActions, so a change to SwiftSyntaxCodeActions can break BuildServerIntegration, while a change to BuildServerIntegration can't break SwiftSyntaxCodeActions.
Position
Below the diagonal: BuildServerIntegration uses a module listed above it, which is the healthy direction.
BuildServerIntegration uses ToolchainRegistry, so a change to ToolchainRegistry can break BuildServerIntegration, while a change to BuildServerIntegration can't break ToolchainRegistry.
Position
Below the diagonal: BuildServerIntegration uses a module listed above it, which is the healthy direction.
BuildServerIntegration uses SemanticIndex, so a change to SemanticIndex can break BuildServerIntegration, while a change to BuildServerIntegration can't break SemanticIndex.
Position
Below the diagonal: BuildServerIntegration uses a module listed above it, which is the healthy direction.
BuildServerIntegration uses SKUtilities, so a change to SKUtilities can break BuildServerIntegration, while a change to BuildServerIntegration can't break SKUtilities.
Position
Below the diagonal: BuildServerIntegration uses a module listed above it, which is the healthy direction.
BuildServerIntegration uses SwiftSourceKitPlugin, so a change to SwiftSourceKitPlugin can break BuildServerIntegration, while a change to BuildServerIntegration can't break SwiftSourceKitPlugin.
Position
Below the diagonal: BuildServerIntegration uses a module listed above it, which is the healthy direction.
BuildServerIntegration uses SKOptions, so a change to SKOptions can break BuildServerIntegration, while a change to BuildServerIntegration can't break SKOptions.
Position
Below the diagonal: BuildServerIntegration uses a module listed above it, which is the healthy direction.
BuildServerIntegration uses SourceKitLSP, so a change to SourceKitLSP can break BuildServerIntegration, while a change to BuildServerIntegration can't break SourceKitLSP.
Position
Below the diagonal: BuildServerIntegration uses a module listed above it, which is the healthy direction.
BuildServerIntegration uses LanguageServerProtocolExtensions, so a change to LanguageServerProtocolExtensions can break BuildServerIntegration, while a change to BuildServerIntegration can't break LanguageServerProtocolExtensions.
Position
Below the diagonal: BuildServerIntegration uses a module listed above it, which is the healthy direction.
BuildServerIntegration uses CompletionScoring, so a change to CompletionScoring can break BuildServerIntegration, while a change to BuildServerIntegration can't break CompletionScoring.
Position
Below the diagonal: BuildServerIntegration uses a module listed above it, which is the healthy direction.
InProcessClient uses ToolchainRegistry, so a change to ToolchainRegistry can break InProcessClient, while a change to InProcessClient can't break ToolchainRegistry.
Position
Below the diagonal: InProcessClient uses a module listed above it, which is the healthy direction.
InProcessClient uses BuildServerIntegration, so a change to BuildServerIntegration can break InProcessClient, while a change to InProcessClient can't break BuildServerIntegration.
Position
Below the diagonal: InProcessClient uses a module listed above it, which is the healthy direction.
SwiftSourceKitClientPlugin uses SourceKitD, so a change to SourceKitD can break SwiftSourceKitClientPlugin, while a change to SwiftSourceKitClientPlugin can't break SourceKitD.
Position
Below the diagonal: SwiftSourceKitClientPlugin uses a module listed above it, which is the healthy direction.
SwiftSourceKitClientPlugin uses BuildServerIntegration, so a change to BuildServerIntegration can break SwiftSourceKitClientPlugin, while a change to SwiftSourceKitClientPlugin can't break BuildServerIntegration.
Position
Below the diagonal: SwiftSourceKitClientPlugin uses a module listed above it, which is the healthy direction.
sourcekit-lsp uses BuildServerIntegration, so a change to BuildServerIntegration can break sourcekit-lsp, while a change to sourcekit-lsp can't break BuildServerIntegration.
Position
Below the diagonal: sourcekit-lsp uses a module listed above it, which is the healthy direction.
Findings mapped to OWASP categories; the specific CVEs/secrets are in the Security dimension cards below and findings.md (redacted only on the public version of this report).
OWASP category
Findings
Severity
A02:2025 — Security Misconfiguration
3
Medium
Roadmap
Top priorities: Add a CI workflow that builds and runs the test suite on every push/PR; Resolve the 220 No direct assertions finding(s) in Test Quality — start with SelectionRangeTests.swift (110), ConvertStoredPropertyToComputedTests.swift (23), ConvertComputedPropertyToZeroParameterFunctionTests.swift (20); Resolve the 1 No ADRs found finding(s) in ADR Quality — start with Package.swift.
Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.
Do this
Helps
Effort
Dimension
Resolve the 1 No ADRs found finding(s) in ADR Quality — start with Package.swift.
Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
Resolve the 1 `asLspSymbolKind` spells `Lsp` where 52 names in the project spell it… finding(s) in Naming Consistency — start with SourceKitLSPServer.swift.
Resolve the 220 No direct assertions finding(s) in Test Quality — start with SelectionRangeTests.swift (110), ConvertStoredPropertyToComputedTests.swift (23), ConvertComputedPropertyToZeroParameterFunctionTests.swift (20).
Nothing pauses a release for a human: publish as a draft release (or gate the release job on a protected tag/manual dispatch) so a bad build can be stopped before users can download it.
Code Duplication: Edited copy of a member (25 corresponding lines)
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 — 3
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 — 344
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 — 276
Recorded, with no effect on how the codebase functions.
Present so the survey is complete, not because it needs doing.
Could not be resolved — 24
Something this survey could not settle
from the outside, and which could be critical or serious. Either a control was required and no
positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves
nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean
result. These are excluded from the score rather than awarded a pass, so the number on the cover neither
rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each
one is named under Limitations.
Methodology & how to trust this report
This survey is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. All 37 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.8, the weighted average across measured dimensions.
Every figure here is one of two 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. 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.
What we checked — 37 dimensions across the health lenses
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, 600 of 623 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 or a scanner, not a narrative.
Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
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
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 — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: the Swift half could not be measured — the Swift suite in . produced no coverage export. Coverage is excluded from the score rather than counted as a near-zero. This is OUR limitation, not a defect in the repo.
D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This repository declares 1 of its own test(s) unreliable. The built-in reliability runner does not support this repository's ecosystem (.swift), so the suite was not re-run and no reliability score is given — these are the repository's own declarations, not our measurement.
D12 Dependency Hygiene — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Not scored — 21 SwiftPM declaration(s) across 2 `Package.swift` and 0 committed pin(s) were read for PINNING discipline (0 defect(s) reported), but the outdated signal comes from listing each declared repository's release tags rather than from a registry, and none of them resolved to a version to compare, so this dimension's own question is only partly answered. NOT a finding that these dependencies are current or healthy.
D14 License Compliance — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 3 of this repository's SwiftPM dependencies could not be fetched at a pinned revision and are repositories api.deps.dev has not indexed, so their licences were not read and the verdict does not cover them: indexstore-db, swift-package-manager, swift-tools-protocols.
D21 Naming Consistency — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22 identifies the intentionally-exposed surface from `IsPackable` and `.Contracts` project names, MSBuild conventions read off the loaded project set. This target exposed no such projects, so the probe never ran; this says nothing about whether the repository has a public API. This repository commits no C#/VB source at all, so there was never an MSBuild project set to read these conventions off. That is OUR side and it is a COLLECTOR gap, not an environment fault: no published-package marker D22 reads admitted any project here, so this ecosystem's public API has no collector, and the remedy is to write one — no change to the scan image can close it.
D24 Comment Value — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 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.
D32 Data Compliance (PII/GDPR) — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `SourceKitLSPDevUtils/Sources/ConfigSchemaGen/ConfigSchemaGen.swift`, `Sources/BuildServerIntegration/BuildServerHooks.swift`, `Sources/BuildServerIntegration/BuildServerManager.swift`, `Sources/BuildServerIntegration/BuildServerManagerDelegate.swift`, `Sources/BuildServerIntegration/BuildServerMessageDependencyTracker.swift`, … (+214 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.
D44 Platform End-of-Life — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This dimension reads a project's own statement about the platform it runs on: a TargetFramework in a .NET project file, a .nvmrc or .python-version, a capped requires-python, a Rust toolchain file or Cargo.toml rust-version, a .go-version, .java-version, .ruby-version, .tool-versions or .sdkmanrc, a go.mod go directive, a Maven or Gradle Java level or toolchain, a Gemfile's ruby directive, a mix.exs elixir requirement, a rebar.config minimum_otp_vsn, a pubspec.yaml SDK constraint, a build.sbt scalaVersion, or a framework major pinned by a dependency constraint. This repository carries none of them, so nothing about its platform was established. That is a gap in this analyzer's coverage, NOT a finding that the platform is supported — a language whose runtime is declared elsewhere (Package.swift, a REDACTED) is simply not read here yet.
AX1 Captive dependencies — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads Microsoft.Extensions.DependencyInjection registrations in C# and Spring beans in Java/Kotlin only, and this repository defines its own container in Sources/SourceKitLSP/LanguageServiceRegistry.swift, 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.
AX6 Interface segregation — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is computed over the public interfaces this run's compilations declare, and none was loaded, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
AXR1 Runtime accessibility — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via REDACTED (REDACTED). docker build failed (exit 1) — ------ REDACTED:13 -------------------- 11 | ##===----------------------------------------------------------------------===## 12 | 13 | >>> FROM swiftlang/swift:nightly-main-jammy 14 | 15 | RUN \ -------------------- ERROR: failed to solve: failed to register layer: write /usr/lib/swift/embedded/Swift.swiftmodule/armv7-apple-none-macho.swiftmodule: no space left on device; runtime evidence skipped.
C1 Data Protection — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These personal data controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks personal data controls.
C2 Access Controls — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These authorization controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks authorization controls.
C3 Audit Trail — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These audit controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks audit controls.
GD1 Unfinished & placeholder code — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, F#, JavaScript/TypeScript, Dart, Ruby and Scala source only, and no C#, F#, JavaScript/TypeScript, Dart, Ruby or Scala was found, and this repository's Python, Swift, c is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
IC1 Incompleteness & stubs — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, JavaScript/TypeScript, Java, Dart, Ruby and Scala source only, and no C#, JavaScript/TypeScript, Java, Dart, Ruby or Scala was found, and this repository's Python, Swift, c is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
M4 Documentation accuracy — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
S1 Web-Security Posture — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These web-security controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks web-security controls.
X12 Unreachable branch — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
X16 Unfloored truncation loop — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, PHP, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Java, PHP, Dart, Ruby, Scala or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X18 Disposal-pattern correctness — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Dart, Ruby, Scala and PHP source only, and no C# was loaded and no JavaScript/TypeScript, Java, Kotlin, Dart, Ruby, Scala or PHP was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X2 Cancellation propagation — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Go, PHP, Dart, Kotlin, Ruby, Scala, Java, Python and Rust source only, and no C# was loaded, and no named async function in this repository's JavaScript/TypeScript, nor any Go, PHP or Dart function or Kotlin suspend function, makes a request that can be cancelled (fetch, axios, ky, ofetch, got, undici, node:http; net/http, net.Dial; amphp; Dio; Ktor, OkHttp), so there is nothing to judge, 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.
X27 Collection changed while being enumerated — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
X29 Per-element action decided by a fixed element — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript (Vue and Svelte components included), Java, Rust, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Java, Rust, Dart, Ruby, Scala or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X4 Structured logging — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Python, PHP, Dart, Ruby, Scala and Rust source only, and no C# was loaded, and this repository's JavaScript/TypeScript, Python and PHP make no call through a named logger, 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.
X5 Nullable reference types — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax and MSBuild project configuration, TypeScript source and its tsconfig files, Java source and its package and module declarations, PHP source and its PHPStan and Psalm configuration, Dart source and its pubspec language version, Ruby source and its Sorbet and Steep configuration, Scala source and its build's explicit-nulls, WartRemover and Scalafix settings, and Kotlin source only, and no C# was loaded, no TypeScript was found, and this repository's C, Python, Swift 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.
Repo exclusion declarations (.gitattributes linguist-generated/vendored, .editorconfig generated_code): none declared — every source file was scored.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
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.
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.
D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
D21 Naming Consistency: Naming consistency compares each name with the convention its structural peers follow in this repository: it cannot tell whether a consistently used name is a good one, and languages other than C# and TypeScript are not measured.
D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
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.
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.
AX9 CQS / query purity: Handlers are found by interface/name convention — a query handler using neither is not seen. Mutation is a resolved write/publish invocation (SaveChanges/repository/bus), so a write hidden behind a hand-rolled wrapper, reflection, or a string-keyed service locator resolves to a non-persistence type and isn't flagged; it detects that a query writes state, not whether the write is a legitimate read-side cache update. Clean means "no resolved write/publish in a query body", not a proof of CQS purity.
M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
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.
30 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was sourcekitd_api_uid_t.init at 56. A further 9 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 SourceKitLSPServer.handle at 63 — they are counted neither in the figure above nor in this dimension's score. 3 files carry no cyclomatic complexity row at all for this reason — every one of their over-threshold methods was excluded, so the exclusion is disclosed nowhere in the file itself: Sources/SourceKitLSP/MessageHandlingDependencyTracker.swift (MessageHandlingDependencyTracker.init at 46), Sources/SwiftLanguageService/SyntaxHighlightingTokenParser.swift (SyntaxHighlightingTokenParser.parseKindAndModifiers at 42), Sources/SwiftLanguageService/SwiftLanguageService.swift (sourcekitd_api_uid_t.asCompletionItemKind at 22). They are named here because the per-file figures other dimensions report are taken BEFORE this exclusion, so such a file can show a high maximum complexity elsewhere in this report and nothing here, with nothing to reconcile the two.
+ 25 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 5 bodies over 30 down to 30 or less in Cyclomatic Complexity — start with sourcekitd_api_uid_t.init (cyclomatic 56), Pattern.singleScore (cyclomatic 41), CodeCompletionSession.completionsFromSKDResponse (cyclomatic 33). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 5 together lifts Cyclomatic Complexity from 6.6 to about 7.3/10, projected with the scoring formula itself and assuming each lands exactly at 30; a cleaner split scores higher.
Detailed fixes: d1_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
+ 46 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 1 body over 60 down to 60 or less in Cognitive Complexity — start with Pattern.singleScore (cognitive 97). — Refactoring it lifts Cognitive Complexity from 6.0 to about 6.5/10.
Detailed fixes: d2_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D3 · God Classes8.8 / 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.
Resolve the 13 MethodTooLong finding(s) in God Classes — start with SourceKitLSPServer.swift (2), SwiftPMBuildServer.swift (2), CodeCompletionSession.swift. — One of this dimension's main actionable groups (13 warning-level).
Resolve the 9 FileTooLong finding(s) in God Classes — start with SourceKitLSPServer.swift, BuildServerManager.swift, SwiftLanguageService.swift. — One of this dimension's main actionable groups (9 warning-level).
Resolve the 4 TooManyMethods finding(s) in God Classes — start with SourceKitLSPServer.swift, SwiftLanguageService.swift, ClangLanguageService.swift. — One of this dimension's main actionable groups (4 warning-level).
Detailed fixes: d3_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: How much of the production code is copy-pasted: the share of production lines inside a reported copy (every copy of a duplicated block or of an edited member, each line once), 10 at none and 0 at a quarter of the lines.
Method: Code duplication via token-stream sliding windows with type-aware normalization (locals masked, type names preserved), scored on the share of production lines inside a reported copy (each line once; 10 at none, 0 at a quarter). Deterministic.
40 duplicated block group(s) detected. 3.8 % of the production lines (2,206 of 58,509) are in a reported copy. A further 54 rows report members as variants of one another; the share counts each copied line once, however many rows cite it. 1 of the 94 are in trees this repository does not ship — vendored, example/demo, project-template, fixture and benchmark code — and are ranked below the shipped groups rather than excluded from them: the duplication there is real and is still counted in this dimension's score. The dimensions that publish a production-file census leave those trees out of theirs, so this count is deliberately drawn over the wider population.
+ 42 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 5 Duplicated block (6 lines × 2) finding(s) in Code Duplication — start with SkipUnless.swift, SourceKitLSPServer.swift, ReduceCommand.swift. — One of this dimension's main actionable groups (5 warning-level).
Resolve the 4 Edited copy of a member (11 corresponding lines) finding(s) in Code Duplication — start with ModuleProximity.swift, FixedCompilationDatabaseBuildServer.swift, SKDResponseArray.swift. — One of this dimension's main actionable groups (4 warning-level).
Resolve the 4 Edited copy of a member (12 corresponding lines) finding(s) in Code Duplication — start with AdjustPositionToStartOfArgument.swift, SelectionRange.swift, FixedCompilationDatabaseBuildServer.swift. — One of this dimension's main actionable groups (4 warning-level).
Detailed fixes: d4_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D5 · Coupling8.4 / 10Strong✓ 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.
58 production modules (SwiftPM+CMake), 0 dependency cycle(s), 2 unstable depended-on module(s). Read from the build's own module declarations; 9 module(s) off the main sequence, with abstractness counted on 24 of the 58 (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).
Off the main sequence: ClangLanguageService (SwiftPM) · ×9
Unstable project ClangLanguageService (CMake)
Unstable project SwiftLanguageService (CMake)
What to do
Resolve the 9 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (9 warning-level).
Resolve the 1 Unstable project ClangLanguageService (CMake) finding(s) in Coupling. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 Unstable project SwiftLanguageService (CMake) finding(s) in Coupling. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d5_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
Resolve the 17 Low cohesion finding(s) in Cohesion (LCOM4) — start with SourceKitLSPServer.swift, DocumentationLanguageService.swift, LocationSortKey.swift. — One of this dimension's main actionable groups (17 warning-level).
Detailed fixes: d6_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D10 · Test Quality8.0 / 10Strong✓ 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.
2 skipped (1 with a documented reason), 273 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 416 tests (3 harness-style project(s) excluded from the assertion penalty).
No assertions: testNoToolchain · ×53Tests/BuildServerIntegrationTests/SwiftPMBuildServerTests.swift:147
Resolve the 220 No direct assertions finding(s) in Test Quality — start with SelectionRangeTests.swift (110), ConvertStoredPropertyToComputedTests.swift (23), ConvertComputedPropertyToZeroParameterFunctionTests.swift (20). — One of this dimension's main actionable groups (220 recommendation-level).
Resolve the 53 No assertions finding(s) in Test Quality — start with PatternTests.swift (17), BinaryCodingTests.swift (6), CandidateBatchTests.swift (6). — One of this dimension's main actionable groups (53 warning-level).
Resolve the 1 Skipped test finding(s) in Test Quality — start with WorkspaceSymbolInfoTests.swift. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d10_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
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.
0 of 8 SwiftPM package(s) use a banned license. SwiftPM has no package registry, so each package's licence is the one its repository declares: 0 of them read from the licence file the repository carries at the revision Package.resolved pins, and 8 — unpinned, or whose licence file could not be read or named — from api.deps.dev, which reports the licence the repository declares today. Graded: every package a committed Package.resolved pins, direct and transitive, and every declared dependency none pins. 11 of them are declared by a manifest that commits no Package.resolved (a library, whose resolution is its consumer's), so their own dependencies are resolved by whoever builds it and are not in this verdict. ★ 3 package(s) could not be read at a pinned revision and are not known to the index, and were NOT graded — this verdict does not cover them: `indexstore-db`, `swift-package-manager`, `swift-tools-protocols`.
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.
Resolve the 1 Hotspot finding(s) in Churn × Complexity Hotspots — start with CodeCompletionSession.swift. — 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 Factor9.1 / 10Exemplary✓ 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.
19 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is Sources/SourceKitLSP/WorkspaceSymbols.swift. Counted over 222 of the 348 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 · ×4
Further sole-owners (lower concentration)
✓ On the Gold path — maintain.
Detailed fixes: d16_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
39 deducted task-comment markers across 58509 LoC (0.1/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.
Resolve the 25 TodoComment finding(s) in Explicit Debt — start with SourceKitLSPServer.swift (6), PopularityTable.swift (3), SwiftPMBuildServer.swift (3). — One of this dimension's main actionable groups (25 warning-level).
Resolve the 14 FixmeComment finding(s) in Explicit Debt — start with ASTCompletionItem.swift (7), CompletionProvider.swift (4), CompletionSession.swift (2). — One of this dimension's main actionable groups (14 warning-level).
Detailed fixes: d17_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D20 · ADR Quality0.0 / 10Critical✓ Tool-verified
What it measures: Whether architecture decisions are recorded well (context, decision, consequences).
Method: Every ADR read by its section structure: nine located rules (a missing Decision, Context or Consequences section, a stale status, two records deciding the same question, a dangling supersede link, a number-only title, a single option, no named cost, no status where the log uses one, no enforcement field where the log adopted one), each a fixed deduction from 10; the score is the mean over evaluated records. Deterministic, no model. Advisory.
Resolve the 1 No ADRs found finding(s) in ADR Quality — start with Package.swift. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d20_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether names — types, methods, variables — are clear and consistent.
Method: Seven vocabulary-free rules (N1-N7) mine each naming convention from the repository and flag a name that breaks a convention its structural peers in the same unit follow; production C# and TypeScript, each its own population. Deterministic, no model, no sample. Advisory.
1 naming inconsistencies among 53 declarations measured against a convention their peers follow.
`asLspSymbolKind` spells `Lsp` where 52 names in the project spell it `LSP`Sources/SourceKitLSP/SourceKitLSPServer.swift:2869
What to do
Resolve the 1 `asLspSymbolKind` spells `Lsp` where 52 names in the project spell it… finding(s) in Naming Consistency — start with SourceKitLSPServer.swift. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d21_recommendation.md · top locations in Appendix A, every location in findings.md.
1 of 2 build units (SwiftPM) flagged as possibly oversized/incoherent.
Projects may be oversized for their cohesion
What to do
Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d26_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: How far you must trace to follow a call — low indirection and co-located slices read easier.
Method: Call indirection (interface hops, cross-namespace calls, slice-locality scaled) over a sampled set of method invocations, size-aware baseline. Sampled; confidence discounted by symbol-resolution gaps. C# also names each pass-through layer (a class whose every public method only forwards its own parameters to one collaborator) as a located finding; the score is not affected.
Coverage: Slice locality from the first namespace segments, SAMPLED (≤400 methods) — not exhaustive.
7 % of calls cross a namespace and 2 % go through an interface, but 100 % of collaborators are co-located — so a call's collaborators sit together and tracing stays easy. Baseline: small — navigation cost is tolerated.
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.
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).
semgrep found no security issues. semgrep hit a parse error in 1 file(s) — `Sources/Csourcekitd/include/CodeCompletionSwiftInterop.h` — so no absence of findings in them is evidence of anything, and nothing in them was analysed. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them.
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.
32 of 222 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is Sources/SwiftLanguageService/SelectionRange.swift. Counted over 222 of the 348 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
Resolve the 2 Orphaned knowledge finding(s) in Knowledge Freshness — start with SelectionRange.swift, ApplyDeMorganLaw.swift. — One of this dimension's main actionable groups (2 issue-level).
Resolve the 30 Orphaned file finding(s) in Knowledge Freshness — start with RemoveRedundantParentheses.swift, ConvertJSONToCodableStruct.swift, OptionSchema.swift. — One of this dimension's main actionable groups (30 recommendation-level).
Resolve the 1 Further orphaned files (smaller) finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d34_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
Resolve the 10 Change coupling finding(s) in Change Coupling — start with BuildServerManager.swift (2), JSONCompilationDatabaseBuildServer.swift, InProcessSourceKitLSPClient.swift. — One of this dimension's main actionable groups (10 warning-level).
Resolve the 1 Change-coupling hub finding(s) in Change Coupling — start with CursorInfo.swift. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d35_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
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.
Other · Architecture — Whether dependencies point inward (Domain ← Application ← Infrastructure/Web) — the clean-architecture dependency rule, checked across the project graph.
Method: Layer violations by name-segment inference (Domain/Core to Application to Infrastructure/Web) over the project-reference graph. Exhaustive over all projects, deterministic.
Do you agree with this assessment?
AX8 · Test isolation10.0 / 10Exemplary✓ Tool-verified
Other · Architecture — Whether production projects stay free of references to test projects — tests may depend on production, never the reverse.
Method: Csproj graph: each production project checked for references to test projects (identified by test-framework presence, not name). Zero violations is clean. Deterministic.
Other · Architecture — Whether read (query) handlers stay side-effect-free — a query that writes persistent state or raises events breaks CQS and makes reads unsafe to retry, cache, or route to a read replica.
Method: Roslyn scan: CQRS handlers classified query-vs-command by interface (IQueryHandler/ICommandHandler/IRequestHandler<TQuery,TResult>) and name convention (*Query/Get*/Find* vs *Command); each query handler's body checked for persistent-state writes (SaveChanges/repository Add-Update) or event publishes by resolved invocation. Deterministic, type-level, exhaustive over the detected handlers.
Coverage: Population: CQRS handlers identified by IQueryHandler/ICommandHandler/IRequestHandler interface + *Query/Get*/Find*/*Command NAME convention; query purity then checked exhaustively within that set — a query handler using neither convention is invisible, and mutation is a resolved persistence/publish CALL, not full dataflow.
Maturity · Maturity — Whether the repository and its projects have a README, and whether it is substantive.
Method: Filesystem scan: README presence, word count, and headings for depth; git history for staleness. Exhaustive across root and project dirs, deterministic.
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.
Maturity · Maturity — Whether the repository is organised deliberately: production code and tests are set apart in a way its ecosystem or the repository itself declares.
Method: Filesystem scan: src/test folder separation and namespace-prefix consistency (majority RootNamespace agreement). Exhaustive across projects, deterministic.
Maturity · Maturity — Whether the project's current-state documentation describes the code that exists.
Method: Every current-state document's checkable claims looked up in the tree (links, versions, and artefact counts an order of magnitude off), plus two README checks: an advertised infrastructure product with no footprint, and a module the CHANGELOG records as removed. Deterministic, no model. Advisory.
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?
P2 · Observability5.0 / 10Adequate✓ Tool-verified
Readiness · Readiness — Whether the code is diagnosable in production — structured logging, tracing/metrics, health checks.
Only 1/3 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `.`, `SourceKitLSPDevUtils`.
What to do
Extend structured logging to the remaining runnable modules so everything you run is diagnosable in production.
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 CodeQL's Swift pack (Swift/Xcode) (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: CodeQL's Swift pack (Swift/Xcode) — 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.
Readiness · Readiness — Whether releases are automated and safely reversible (probes, rolling updates, approval gates) — from manifests/pipeline files, not the live environment.
Method: Filesystem scan: deployment manifests/IaC (K8s YAML, Helm, Terraform) for rolling updates, probes, approval gates, migration hooks. Exhaustive, deterministic.
What to do
Nothing pauses a release for a human: publish as a draft release (or gate the release job on a protected tag/manual dispatch) so a bad build can be stopped before users can download it.
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 each language's code 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.
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.
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` 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. (×14) — Sources/TSCExtensions/Process+Run.swift:85, Sources/SwiftSyntaxCodeActions/PackageManifestEdits.swift:70, Sources/SwiftSyntaxCodeActions/PackageManifestEdits.swift:122, …
What to do
Swallowed exception (caught, then discarded)
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.
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.
D11 Test Reliability — 1 observation(s) recorded · This repository declares 1 of its own test(s) unreliable. The built-in reliability runner does not support this repository's ecosystem (.swift), so the suite was not re-run and no reliability score is given — these are the repository's own declarations, not our measurement.
X10 Duplicated predicate — 3 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
X7 Silent fallback defaults — 5 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 3 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.
C3 Audit Trail — Not assessed: these audit controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks audit controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
P6 Release Hygiene — not evidenced — no changelog, version stamp or semver release tag in the repo
Not included — 73 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.
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 function in this Python code is served by a threaded web framework (a Flask, Bottle or FastAPI route, a Django or Pyramid view), so no module is shared between request threads. No Swift request handler (a Vapor, Hummingbird, Kitura, Swifter or Perfect route handler, as a method or a registered closure) is declared, so no state is shared between request threads.
AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
AX6 Interface segregation — not assessed — interface segregation is computed over a type surface that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
AX7 Slice cohesion — not applicable — not a vertical-slice architecture
AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
AXR1 Runtime accessibility — docker build failed (exit 1) — ------ REDACTED:13 -------------------- 11 | ##===----------------------------------------------------------------------===## 12 | 13 | >>> FROM swiftlang/swift:nightly-main-jammy 14 | 15 | RUN \ -------------------- ERROR: failed to solve: failed to register layer: write /usr/lib/swift/embedded/Swift.swiftmodule/armv7-apple-none-macho.swiftmodule: no space left on device; runtime evidence skipped This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
C1 Data Protection — Not assessed: these personal data controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks personal data controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
C2 Access Controls — Not assessed: these authorization controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks authorization controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
C4 Data Retention — No personal data detected in a persisted data model — no PII-named property (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a SwiftData @Model, a Core Data, Realm, GRDB or Fluent type, a GRDB or SQLite.swift column, or in a SQL CREATE TABLE or ALTER TABLE — and no database or data-store client (CoreData, SwiftData, GRDB, RealmSwift, SQLite, 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 property (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a SwiftData @Model, a Core Data, Realm, GRDB or Fluent type, a GRDB or SQLite.swift column, or in a SQL CREATE TABLE or ALTER TABLE — and no database or data-store client (CoreData, SwiftData, GRDB, RealmSwift, SQLite, Firebase, …) imported either, so this repository keeps no personal data for a data subject to erase, export or consent over.
D12 Dependency Hygiene — Not scored — 21 SwiftPM declaration(s) across 2 `Package.swift` and 0 committed pin(s) were read for PINNING discipline (0 defect(s) reported), but the outdated signal comes from listing each declared repository's release tags rather than from a registry, and none of them resolved to a version to compare, so this dimension's own question is only partly answered. 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.
D19 Documentation Quality — No runnable or published unit to look for an example in, and no multi-project root README to look for a map in; the other documentation kinds are withheld (see the gaps), so documentation quality is not applicable here.
D22 Internal API Consistency — The exposed public-API surface could not be collected — no C#/VB projects loaded.
D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
D24 Comment Value — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only — this repository's production source is .py, .swift, 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
D30 Dependency Vulnerabilities — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Swift Package.swift/Package.resolved — not scanned yet).
D32 Data Compliance (PII/GDPR) — 219 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
D36 Supply-chain Provenance & Signing — No CI/build pipeline found (.github/.forgejo/.gitea workflows, .circleci, .buildkite, .woodpecker, .teamcity, .gitlab-ci.yml, .travis.yml, bitbucket-pipelines.yml, .drone.yml, .cirrus.yml, .woodpecker.yml, appveyor.yml, azure-pipelines*.yml, .pipelines/, .vsts-ci/, .azuredevops/, Jenkinsfile); there is no build to attest provenance for.
D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
D43 Malicious Dependencies — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Swift Package.swift/Package.resolved — not scanned yet).
D44 Platform End-of-Life — Platform end-of-life not assessed — this repository declares no platform this pass reads
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 — Swift suite
DM1 Domain Modelling — not scored — this repository shows none of the 3 signals this lens looks for
ED2 Event/command shape — not scored — deciding whether a command has more than one competing handler requires resolving the call graph, and this analysis resolves a call's owner only where the receiver's type is written down in the source. Reported as guidance rather than measured
ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
GD1 Unfinished & placeholder code — no source files were read — this check reads C#, F#, JavaScript/TypeScript, Dart, Ruby and Scala, and none was read for this repository's product. That is a limit of the analyzer, not a finding about your code.
IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
P12 CI test-gate honesty — no CI workflow found
P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the Python, Swift source, so there is no service whose uptime a failing dependency could take down
P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
P9 Domain vs controller coverage — coverage not measured: this check compares the coverage of the analyzer's own test run across the domain and web layers, and that run measured none here — Test coverage (D8) says why
PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for `Benchmark("…")` in a file importing package-benchmark, or package-benchmark in Package.swift, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
S1 Web-Security Posture — Not assessed: these web-security controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks web-security controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
X1 Async correctness — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X12 Unreachable branch — X12 reached only 1% of this repository's production lines — swift (57,958 lines), c (1,169 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
X13 Undrained process stream — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X14 Bypassable address classification — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X16 Unfloored truncation loop — not 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
X17 Uncapped recursion over a caller-supplied document — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X18 Disposal-pattern correctness — not 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
X19 Unrestored process-global state — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X2 Cancellation propagation — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
X20 Mistyped argument guard — This check asks whether an argument guard reports an EMPTY value as a NULL one, which needs a language that throws a null-specific argument exception — .NET's ArgumentNullException, the JVM's NullPointerException, Dart's ArgumentError.notNull. This repository contains none of those languages: the ones it is written in have a single exception for a bad argument, so there is no pair of exceptions to confuse and nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
X21 Side-effecting pattern guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X22 Contradicted release guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X23 Unguarded diagnostic materialisation — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X24 Document value interpolated into markup unescaped — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X25 Inert configuration knob — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X26 Unsynchronised callback handoff — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X27 Collection changed while being enumerated — X27 reached only 1% of this repository's production lines — swift (57,958 lines), c (1,169 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
X29 Per-element action decided by a fixed element — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
X30 Support guard that admits what it rejects — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
X4 Structured logging — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
X5 Nullable reference types — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
X6 Hand-rolled structured-format parsing — 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.
Orphaned knowledge Sources/SwiftLanguageService/SelectionRange.swift:1— No living knowledge remains for this large file — its last meaningful change has decayed away; if it breaks, no one currently understands it. Schedule a read-through / add characterisation tests before it bites.
Orphaned knowledge Sources/SwiftSyntaxCodeActions/ApplyDeMorganLaw.swift:1— No living knowledge remains for this large file — its last meaningful change has decayed away; if it breaks, no one currently understands it. Schedule a read-through / add characterisation tests before it bites.
D11 · Test Reliability· Test declared unreliable · ×1
Test declared unreliable: testCancellation Tests/SourceKitLSPTests/LifecycleTests.swift:62— This test is disabled or skipped with a reason naming unreliability — the repository's own words: "Flaky in CI: https://github.com/swiftlang/sourcekit-lsp/issues/2783". A test that is skipped for flakiness is neither passing nor protecting the code it covers; either stabilise it or delete it, but do not leave it disabled indefinitely. (Found by reading the repository's own test source — the suite itself was not re-run, since the reliability runner does not support this ecosystem.)
No assertions: testNoToolchain Tests/BuildServerIntegrationTests/SwiftPMBuildServerTests.swift:147— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: testIntegers Tests/CompletionScoringTests/BinaryCodingTests.swift:37— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: testBools Tests/CompletionScoringTests/BinaryCodingTests.swift:70— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: testStrings Tests/CompletionScoringTests/BinaryCodingTests.swift:74— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: testArrays Tests/CompletionScoringTests/BinaryCodingTests.swift:80— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: testDictionaries Tests/CompletionScoringTests/BinaryCodingTests.swift:84— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: testSemanticClassificationComponents Tests/CompletionScoringTests/BinaryCodingTests.swift:88— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: testPrioritizeUserSymbolsOverSDK Tests/CompletionScoringTests/CandidateBatchTests.swift:471— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: test33239581 Tests/CompletionScoringTests/CandidateBatchTests.swift:525— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: test48642189 Tests/CompletionScoringTests/CandidateBatchTests.swift:534— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: test30956224 Tests/CompletionScoringTests/CandidateBatchTests.swift:647— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: test31615625 Tests/CompletionScoringTests/CandidateBatchTests.swift:655— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: test76104403 Tests/CompletionScoringTests/CandidateBatchTests.swift:679— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: testSymbolNotoriety Tests/CompletionScoringTests/CompletionScoreTests.swift:123— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: testTypeReferencePercentages Tests/CompletionScoringTests/CompletionScoreTests.swift:130— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: testModuleCombinesWithReferenceFrequency Tests/CompletionScoringTests/CompletionScoreTests.swift:137— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: testMethodReferencePercentages Tests/CompletionScoringTests/CompletionScoreTests.swift:152— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: testModulePopularity Tests/CompletionScoringTests/CompletionScoreTests.swift:167— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: testNonMatches Tests/CompletionScoringTests/InfluencingIdentifiersTests.swift:45— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: testIdentifierPositions Tests/CompletionScoringTests/InfluencingIdentifiersTests.swift:50— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: testTokenPositions Tests/CompletionScoringTests/InfluencingIdentifiersTests.swift:55— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: testTokenCoverage Tests/CompletionScoringTests/InfluencingIdentifiersTests.swift:60— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: testCaseInvariance Tests/CompletionScoringTests/InfluencingIdentifiersTests.swift:68— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: testInertTerms Tests/CompletionScoringTests/InfluencingIdentifiersTests.swift:73— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: testScoring Tests/CompletionScoringTests/PatternTests.swift:255— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
TodoComment Sources/TSCExtensions/Process+Run.swift:128— // TODO: We should also terminate all child processes (https://github.com/swiftlang/sourcekit-lsp/issues/2080)
TodoComment Sources/SwiftExtensions/Process+terminate.swift:32— // TODO: We should also terminate all child processes (https://github.com/swiftlang/sourcekit-lsp/issues/2080)
TodoComment Sources/SwiftLanguageService/CursorInfo.swift:218— // TODO: Remove once https://github.com/swiftlang/swift/issues/86432 is fixed
TodoComment Sources/SourceKitLSP/SourceKitLSPServer.swift:2309— // TODO: Remove this workaround once https://github.com/swiftlang/swift/issues/75600 is fixed
TodoComment Sources/SourceKitLSP/SourceKitLSPServer.swift:2370— // TODO: Remove this workaround once https://github.com/swiftlang/swift/issues/75600 is fixed
TodoComment Sources/SourceKitLSP/SourceKitLSPServer.swift:2410— // TODO: Remove this workaround once https://github.com/swiftlang/swift/issues/75600 is fixed
TodoComment Sources/SourceKitLSP/SourceKitLSPServer.swift:2562— // TODO: Remove this workaround once https://github.com/swiftlang/swift/issues/75600 is fixed
TodoComment Sources/SourceKitLSP/SourceKitLSPServer.swift:2655— // TODO: Remove this workaround once https://github.com/swiftlang/swift/issues/75600 is fixed
TodoComment Sources/SourceKitLSP/SourceKitLSPServer.swift:2708— // TODO: Remove this workaround once https://github.com/swiftlang/swift/issues/75600 is fixed
TodoComment Sources/SourceKitD/SKDRequestDictionary.swift:105— // TODO: Implement a better redacted log that contains keys, number of — 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 Sources/SourceKitD/SKDResponse.swift:76— // TODO: Implement a better redacted log that contains keys, number of — 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 Sources/SemanticIndex/SemanticIndexManager.swift:340— // TODO: Ideally this would be a type like any Collection<DocumentURI> & Sendable but that doesn't work due to — 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 Sources/SemanticIndex/SemanticIndexManager.swift:974— // TODO: When we can index multiple targets concurrently in SwiftPM, increase the batch size to half the — 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 Sources/Diagnose/StderrStreamConcurrencySafe.swift:19— // TODO: @preconcurrency needed because stderr is not sendable on Linux https://github.com/swiftlang/swift/issues/75601
TodoComment Sources/CompletionScoring/Text/InfluencingIdentifiers.swift:91— // TODO: We could turn this loop inside out to walk the candidate tokens first, and skip the ones that are shorter — 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 Sources/CompletionScoring/Semantics/Components/Popularity.swift:44— // TODO: remove once `PopularityTable` is removed. — 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 Sources/CompletionScoring/Semantics/Components/PopularityTable.swift:15— // TODO: deprecate — 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 Sources/CompletionScoring/Semantics/Components/PopularityTable.swift:150— // TODO: deprecate — 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 Sources/CompletionScoring/Semantics/Components/PopularityTable.swift:168— // TODO: deprecate — 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 Sources/ClangLanguageService/ClangLanguageService.swift:338— // TODO: We want to know the build settings that are currently transmitted to clangd, not whichever ones we would — 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 Sources/ClangLanguageService/ClangLanguageService.swift:778— // TODO: This is a workaround for clangd not respecting the compilation — 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 Sources/BuildServerIntegration/BuildServerManager.swift:637— // TODO: Forward file watch patterns from this initialize request to the client — 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 Sources/BuildServerIntegration/SwiftPMBuildServer.swift:431— // TODO: Remove this workaround once https://github.com/swiftlang/swift-package-manager/issues/8038 is fixed.
TodoComment Sources/BuildServerIntegration/SwiftPMBuildServer.swift:645— // TODO: Query The SwiftPM build server for the document's language and add it to SourceItem.data — 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 Sources/BuildServerIntegration/SwiftPMBuildServer.swift:779— // TODO: Support preparation of multiple targets at once. (https://github.com/swiftlang/sourcekit-lsp/issues/1262)
Low cohesion: SourceKitLSPServer (LCOM4 32) Sources/SourceKitLSP/SourceKitLSPServer.swift:41— SourceKitLSPServer's methods fall into 32 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 32 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: DocumentationLanguageService (LCOM4 11) Sources/DocumentationLanguageService/DocumentationLanguageService.swift:27— DocumentationLanguageService's methods fall into 11 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 11 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: Sequence (LCOM4 10) Sources/SourceKitLSP/LocationSortKey.swift:44— Sequence's methods fall into 10 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 10 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: String (LCOM4 9) Sources/BuildServerIntegration/CompilationDatabase.swift:207— String's methods fall into 9 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 9 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: ClangLanguageService (LCOM4 7) Sources/ClangLanguageService/ClangLanguageService.swift:40— ClangLanguageService's methods fall into 7 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 7 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: UncheckedIndex (LCOM4 7) Sources/SemanticIndex/CheckedIndex.swift:339— UncheckedIndex's methods fall into 7 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 7 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: SwiftLanguageService (LCOM4 7) Sources/SwiftLanguageService/SwiftLanguageService.swift:123— SwiftLanguageService's methods fall into 7 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 7 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: LegacyBuildServer (LCOM4 6) Sources/BuildServerIntegration/LegacyBuildServer.swift:36— LegacyBuildServer's methods fall into 6 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 6 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: Array (LCOM4 6) Sources/Diagnose/CommandLineArgumentsReducer.swift:140— Array's methods fall into 6 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 6 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: Collection (LCOM4 6) Sources/SemanticIndex/TaskScheduler.swift:808— Collection's methods fall into 6 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 6 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: SourceKitD (LCOM4 5) Sources/SourceKitD/SourceKitD.swift:105— SourceKitD's methods fall into 5 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 5 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: BuildServerManager (LCOM4 4) Sources/BuildServerIntegration/BuildServerManager.swift:395— BuildServerManager's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: FixedCompilationDatabaseBuildServer (LCOM4 4) Sources/BuildServerIntegration/FixedCompilationDatabaseBuildServer.swift:30— FixedCompilationDatabaseBuildServer's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: TestSourceKitLSPClient (LCOM4 4) Sources/SKTestSupport/TestSourceKitLSPClient.swift:92— TestSourceKitLSPClient's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: CapabilityRegistry (LCOM4 4) Sources/SourceKitLSP/CapabilityRegistry.swift:22— CapabilityRegistry's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: Connection (LCOM4 4) Sources/SwiftSourceKitPlugin/CodeCompletion/Connection.swift:49— Connection's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: ToolchainRegistry (LCOM4 4) Sources/ToolchainRegistry/ToolchainRegistry.swift:34— ToolchainRegistry's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
FixmeComment Sources/SwiftSourceKitPlugin/CompletionProvider.swift:371— // FIXME: make it optional? — 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.
FixmeComment Sources/SwiftSourceKitPlugin/CompletionProvider.swift:500— // FIXME: special operator ? — 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.
FixmeComment Sources/SwiftSourceKitPlugin/CompletionProvider.swift:503— // FIXME: special literal ? — 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.
FixmeComment Sources/SwiftSourceKitPlugin/CompletionProvider.swift:508— // FIXME: special unknown ? — 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.
FixmeComment Sources/SwiftSourceKitPlugin/CodeCompletion/Connection.swift:169— // FIXME: move line:column translation into C++ impl. so that we can avoid reading the file an extra time here. — 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.
FixmeComment Sources/SwiftSourceKitPlugin/ASTCompletion/ASTCompletionItem.swift:246— // FIXME: add a "deinit" kind. — 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.
FixmeComment Sources/SwiftSourceKitPlugin/ASTCompletion/ASTCompletionItem.swift:249— // FIXME: add a "subscript" kind. — 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.
FixmeComment Sources/SwiftSourceKitPlugin/ASTCompletion/ASTCompletionItem.swift:254— // FIXME: add an "operator kind". — 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.
FixmeComment Sources/SwiftSourceKitPlugin/ASTCompletion/ASTCompletionItem.swift:261— // FIXME: add a "literal" kind? — 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.
FixmeComment Sources/SwiftSourceKitPlugin/ASTCompletion/ASTCompletionItem.swift:264— // FIXME: figure out a kind for this. — 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.
FixmeComment Sources/SwiftSourceKitPlugin/ASTCompletion/ASTCompletionItem.swift:267— // FIXME: add a "macro" kind? — 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.
FixmeComment Sources/SwiftSourceKitPlugin/ASTCompletion/ASTCompletionItem.swift:305— // FIXME: we don't know whether the super class is from this module or another. — 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.
FixmeComment Sources/SwiftSourceKitPlugin/ASTCompletion/CompletionSession.swift:179— // FIXME: 'baseExprScope' might still be populated for implicit self — 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.
FixmeComment Sources/SwiftSourceKitPlugin/ASTCompletion/CompletionSession.swift:302— // FIXME: Handle unknown severity? — 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.
Swallowed exception (caught, then discarded) Sources/TSCExtensions/Process+Run.swift:85— `catch` 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) Sources/SwiftSyntaxCodeActions/PackageManifestEdits.swift:70— `catch` 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) Sources/SwiftSyntaxCodeActions/PackageManifestEdits.swift:122— `catch` 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) Sources/SwiftSyntaxCodeActions/PackageManifestEdits.swift:176— `catch` 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) Sources/SwiftSourceKitPluginCommon/CompletionResultsArray.swift:190— `catch` 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) Sources/SwiftLanguageService/Diagnostic.swift:188— `catch` 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) Sources/SwiftLanguageService/DiagnosticReportManager.swift:311— `catch` 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) Sources/SwiftLanguageService/SwiftLanguageService.swift:693— `catch` 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) Sources/SourceKitLSP/SourceKitLSPServer.swift:208— `catch` 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) Sources/SKUtilities/Debouncer.swift:68— `catch` 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) Sources/SKTestSupport/SkipUnless.swift:230— `catch` 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) Sources/SKTestSupport/SkipUnless.swift:461— `catch` 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) Sources/LanguageServerProtocolExtensions/WorkDoneProgressManager.swift:112— `catch` 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) Sources/BuildServerIntegration/SwiftPMBuildServer.swift:176— `catch` 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.
MethodTooLong: SourceKitLSPServer.handle Sources/SourceKitLSP/SourceKitLSPServer.swift:636— MethodTooLong — handle runs 153 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 53 over it, 1.53× 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: SwiftPMBuildServer.init Sources/BuildServerIntegration/SwiftPMBuildServer.swift:229— MethodTooLong — init runs 138 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 38 over it, 1.38× 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: CodeCompletionSession.completionsFromSKDResponse Sources/SwiftLanguageService/CodeCompletionSession.swift:498— MethodTooLong — completionsFromSKDResponse runs 138 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 38 over it, 1.38× 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: SemanticIndexManager.scheduleIndexing Sources/SemanticIndex/SemanticIndexManager.swift:867— MethodTooLong — scheduleIndexing runs 120 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 20 over it, 1.20× 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: SyntaxHighlightingTokenParser.parseKindAndModifiers Sources/SwiftLanguageService/SyntaxHighlightingTokenParser.swift:88— MethodTooLong — parseKindAndModifiers runs 120 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 20 over it, 1.20× 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: Toolchain.init Sources/ToolchainRegistry/Toolchain.swift:235— MethodTooLong — init runs 114 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 14 over it, 1.14× 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: SwiftLanguageService.removeUnusedImports Sources/SwiftLanguageService/RemoveUnusedImports.swift:112— MethodTooLong — removeUnusedImports runs 109 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 9 over it, 1.09× 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: Diagnostic.init Sources/SwiftLanguageService/Diagnostic.swift:168— MethodTooLong — init runs 105 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 5 over it, 1.05× 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: Pattern.singleScore Sources/CompletionScoring/Text/Pattern.swift:452— MethodTooLong — singleScore runs 103 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 3 over it, 1.03× 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: SourceKitLSPServer.serverCapabilities Sources/SourceKitLSP/SourceKitLSPServer.swift:1024— MethodTooLong — serverCapabilities runs 103 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 3 over it, 1.03× 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: BuildServerManager.init Sources/BuildServerIntegration/BuildServerManager.swift:580— MethodTooLong — init runs 101 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 1 over it, 1.01× 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: SwiftPMBuildServer.prepare Sources/BuildServerIntegration/SwiftPMBuildServer.swift:791— MethodTooLong — prepare runs 101 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 1 over it, 1.01× 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: UpdateIndexStoreTaskDescription.updateIndexStore Sources/SemanticIndex/UpdateIndexStoreTaskDescription.swift:286— MethodTooLong — updateIndexStore runs 101 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 1 over it, 1.01× 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.
Change coupling: JSONCompilationDatabaseBuildServer.swift ↔ LegacyBuildServer.swift Sources/BuildServerIntegration/JSONCompilationDatabaseBuildServer.swift:1— `Sources/BuildServerIntegration/JSONCompilationDatabaseBuildServer.swift` and `Sources/BuildServerIntegration/LegacyBuildServer.swift` change together 67% of the time (49 of the 73 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 49 shared commits counted here, the most recent 3 are `cb176437` Make a couple parameters in the `BuildTarget` initializer defaulted (at that commit the files were still `Sources/BuildSystemIntegration/JSONCompilationDatabaseBuildSystem.swift` and `Sources/BuildSystemIntegration/LegacyBuildServerBuildSystem.swift`); `0bdbb507` Review `CompilationDatabaseBuildSystem` (at that commit the files were still `Sources/BuildSystemIntegration/CompilationDatabaseBuildSystem.swift` and `Sources/BuildSystemIntegration/BuildServerBuildSystem.swift`); `12923b6d` Implement `toolchain(for:)` using BSP (at that commit the files were still `Sources/BuildSystemIntegration/CompilationDatabaseBuildSystem.swift` and `Sources/BuildSystemIntegration/BuildServerBuildSystem.swift`) — run `git show` on any of them.
Change coupling: InProcessSourceKitLSPClient.swift ↔ TestSourceKitLSPClient.swift Sources/InProcessClient/InProcessSourceKitLSPClient.swift:1— `Sources/InProcessClient/InProcessSourceKitLSPClient.swift` and `Sources/SKTestSupport/TestSourceKitLSPClient.swift` 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). They sit in different directories, but in this ecosystem the namespace is declared in the FILE, not by the folder — so the two may well share one namespace and reference each other with no import for this pass to see. Read the pair before acting: if one derives from or overrides the other, the dependency is explicit in the type declaration and the co-change is definitional; if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE and the thing to add is a comment saying so; if they simply belong together, co-locate them; if none of these 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 `a6c926fa` Relax atomic memory orderings; switch semaphore to release/acquire; `83de30d2` Migrate atomic call sites to Synchronization.Atomic and ThreadSafeBox; `c692a83f` Construct `LanguageServiceRegistry` outside of `SourceKitLSP` module — run `git show` on any of them.
Change coupling: IndexCommand.swift ↔ TestSourceKitLSPClient.swift Sources/Diagnose/IndexCommand.swift:1— `Sources/Diagnose/IndexCommand.swift` and `Sources/SKTestSupport/TestSourceKitLSPClient.swift` change together 54% of the time (7 of the 13 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 different directories, but in this ecosystem the namespace is declared in the FILE, not by the folder — so the two may well share one namespace and reference each other with no import for this pass to see. Read the pair before acting: if one derives from or overrides the other, the dependency is explicit in the type declaration and the co-change is definitional; if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE and the thing to add is a comment saying so; if they simply belong together, co-locate them; if none of these 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 `5fba1699` Generalize `PollIndexRequest` and `BarrierRequest` into a single `Syn…; `947e5269` Reduce the number of public imports; `d8e0fff6` Make background indexing a proper option in `SourceKitLSPOptions` — run `git show` on any of them.
Change coupling: Rename.swift ↔ RelatedIdentifiers.swift Sources/SourceKitLSP/Rename.swift:1— `Sources/SourceKitLSP/Rename.swift` and `Sources/SwiftLanguageService/RelatedIdentifiers.swift` change together 53% of the time (9 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). They sit in different directories, but in this ecosystem the namespace is declared in the FILE, not by the folder — so the two may well share one namespace and reference each other with no import for this pass to see. Read the pair before acting: if one derives from or overrides the other, the dependency is explicit in the type declaration and the co-change is definitional; if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE and the thing to add is a comment saying so; if they simply belong together, co-locate them; if none of these 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 `69ab356b` Log contextual requests that affect sourcekitd’s global state (at that commit the file was still `Sources/SourceKitLSP/Swift/RelatedIdentifiers.swift`); `8c15e279` use a helper document in cursorInfo() (at that commit the file was still `Sources/SourceKitLSP/Swift/RelatedIdentifiers.swift`); `5bae73fc` Use fallback build settings if build system doesn’t provide build set… (at that commit the file was still `Sources/SourceKitLSP/Swift/RelatedIdentifiers.swift`) — run `git show` on any of them.
Change coupling: OpenInterface.swift ↔ VariableTypeInfo.swift Sources/SwiftLanguageService/OpenInterface.swift:1— `Sources/SwiftLanguageService/OpenInterface.swift` and `Sources/SwiftLanguageService/VariableTypeInfo.swift` change together 52% of the time (16 of the 31 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 16 shared commits counted here, the most recent 3 are `5bae73fc` Use fallback build settings if build system doesn’t provide build set… (at that commit the files were still `Sources/SourceKitLSP/Swift/OpenInterface.swift` and `Sources/SourceKitLSP/Swift/VariableTypeInfo.swift`); `0784041c` Support Semantic Functionality in Macro Expansion Reference Documents… (at that commit the files were still `Sources/SourceKitLSP/Swift/OpenInterface.swift` and `Sources/SourceKitLSP/Swift/VariableTypeInfo.swift`); `191d366a` Add a maximum duration for sourcekitd requests (at that commit the files were still `Sources/SourceKitLSP/Swift/OpenInterface.swift` and `Sources/SourceKitLSP/Swift/VariableTypeInfo.swift`) — run `git show` on any of them.
Change coupling: ClangLanguageService.swift ↔ SwiftLanguageService.swift Sources/ClangLanguageService/ClangLanguageService.swift:1— `Sources/ClangLanguageService/ClangLanguageService.swift` and `Sources/SwiftLanguageService/SwiftLanguageService.swift` change together 51% of the time (90 of the 175 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 different directories, but in this ecosystem the namespace is declared in the FILE, not by the folder — so the two may well share one namespace and reference each other with no import for this pass to see. Read the pair before acting: if one derives from or overrides the other, the dependency is explicit in the type declaration and the co-change is definitional; if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE and the thing to add is a comment saying so; if they simply belong together, co-locate them; if none of these holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 90 shared commits counted here, the most recent 3 are `f2a12145` Scope language service instances per workspace; `8639c193` Add codeAction/resolve support; `2a360c04` address comments — run `git show` on any of them.
Change coupling: BuildServerManager.swift ↔ CustomBuildServerTestProject.swift Sources/BuildServerIntegration/BuildServerManager.swift:1— `Sources/BuildServerIntegration/BuildServerManager.swift` and `Sources/SKTestSupport/CustomBuildServerTestProject.swift` change together 50% of the time (11 of the 22 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 different directories, but in this ecosystem the namespace is declared in the FILE, not by the folder — so the two may well share one namespace and reference each other with no import for this pass to see. Read the pair before acting: if one derives from or overrides the other, the dependency is explicit in the type declaration and the co-change is definitional; if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE and the thing to add is a comment saying so; if they simply belong together, co-locate them; if none of these 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 `3bb4690d` Terminate pending background indexing and preparation tasks when shut… (at that commit the file was still `Sources/BuildSystemIntegration/BuildSystemManager.swift`); `71e74045` If the compiler arguments only contain `-o`, add the output path as `… (at that commit the file was still `Sources/BuildSystemIntegration/BuildSystemManager.swift`); `4991e156` Re-index header files when they are modified (at that commit the file was still `Sources/BuildSystemIntegration/BuildSystemManager.swift`) — run `git show` on any of them.
Change coupling: WorkDoneProgressManager.swift ↔ SwiftLanguageService.swift Sources/LanguageServerProtocolExtensions/WorkDoneProgressManager.swift:1— `Sources/LanguageServerProtocolExtensions/WorkDoneProgressManager.swift` and `Sources/SwiftLanguageService/SwiftLanguageService.swift` 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). They sit in different directories, but in this ecosystem the namespace is declared in the FILE, not by the folder — so the two may well share one namespace and reference each other with no import for this pass to see. Read the pair before acting: if one derives from or overrides the other, the dependency is explicit in the type declaration and the co-change is definitional; if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE and the thing to add is a comment saying so; if they simply belong together, co-locate them; if none of these 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 `189f32ae` Remove workarounds that are no longer needed (at that commit the files were still `Sources/SourceKitLSP/WorkDoneProgressManager.swift` and `Sources/SourceKitLSP/Swift/SwiftLanguageService.swift`); `d8e0fff6` Make background indexing a proper option in `SourceKitLSPOptions` (at that commit the files were still `Sources/SourceKitLSP/WorkDoneProgressManager.swift` and `Sources/SourceKitLSP/Swift/SwiftLanguageService.swift`); `3003fe19` Allow prefixing of the token for a `WorkDoneProgress` with a custom s… (at that commit the files were still `Sources/SourceKitLSP/WorkDoneProgressManager.swift` and `Sources/SourceKitLSP/Swift/SwiftLanguageService.swift`) — run `git show` on any of them.
Change coupling: BuildServerManager.swift ↔ SourceKitIndexDelegate.swift Sources/BuildServerIntegration/BuildServerManager.swift:1— `Sources/BuildServerIntegration/BuildServerManager.swift` and `Sources/SourceKitLSP/SourceKitIndexDelegate.swift` 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). They sit in different directories, but in this ecosystem the namespace is declared in the FILE, not by the folder — so the two may well share one namespace and reference each other with no import for this pass to see. Read the pair before acting: if one derives from or overrides the other, the dependency is explicit in the type declaration and the co-change is definitional; if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE and the thing to add is a comment saying so; if they simply belong together, co-locate them; if none of these holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 5 shared commits counted here, the most recent 3 are `a6c291b8` Do not block SourceKit-LSP functionality when a build server takes lo…; `33d803f1` Change methods that were only public for testing purposes to be `@_sp… (at that commit the file was still `Sources/SKCore/BuildSystemManager.swift`); `deed5e4c` Remove a couple underscored properties/methods (at that commit the file was still `Sources/SKCore/BuildSystemManager.swift`) — run `git show` on any of them.
Change coupling: Package.swift ↔ Plugin.swift Package.swift:1— `Package.swift` and `Sources/SwiftSourceKitPlugin/Plugin.swift` 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). They sit in different directories, but in this ecosystem the namespace is declared in the FILE, not by the folder — so the two may well share one namespace and reference each other with no import for this pass to see. Read the pair before acting: if one derives from or overrides the other, the dependency is explicit in the type declaration and the co-change is definitional; if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE and the thing to add is a comment saying so; if they simply belong together, co-locate them; if none of these holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 5 shared commits counted here, the most recent 3 are `4b2fa319` Allow injection of a pre-initialized sourcekitd connection; `8ac9cd64` Resolve `/usr/bin/*` shims on macOS; `c7ca73ae` Drop support for building with Swift 6.1 — run `git show` on any of them.
FileTooLong: SourceKitLSP/SourceKitLSPServer.swift Sources/SourceKitLSP/SourceKitLSPServer.swift— FileTooLong — 1826 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 1326 over it, 3.65× 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: BuildServerIntegration/BuildServerManager.swift Sources/BuildServerIntegration/BuildServerManager.swift— FileTooLong — 1268 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 768 over it, 2.54× 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: SwiftLanguageService/SwiftLanguageService.swift Sources/SwiftLanguageService/SwiftLanguageService.swift— FileTooLong — 957 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 457 over it, 1.91× 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: Text/Pattern.swift Sources/CompletionScoring/Text/Pattern.swift— FileTooLong — 852 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 352 over it, 1.70× 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: BuildServerIntegration/SwiftPMBuildServer.swift Sources/BuildServerIntegration/SwiftPMBuildServer.swift— FileTooLong — 649 significant lines (blank, comment-only and punctuation-only lines excluded), about 90% of them inside a single declaration: preparationTaskID (83-1011). The bar is 500 significant lines; this is 149 over it, 1.30× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: SwiftLanguageService/CodeCompletionSession.swift Sources/SwiftLanguageService/CodeCompletionSession.swift— FileTooLong — 612 significant lines (blank, comment-only and punctuation-only lines excluded), about 90% of them inside a single declaration: CodeCompletionSession (84-987). The bar is 500 significant lines; this is 112 over it, 1.22× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: SemanticIndex/SemanticIndexManager.swift Sources/SemanticIndex/SemanticIndexManager.swift— FileTooLong — 574 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 74 over it, 1.15× 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: SwiftLanguageService/Rename.swift Sources/SwiftLanguageService/Rename.swift— FileTooLong — 527 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 27 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: SemanticIndex/UpdateIndexStoreTaskDescription.swift Sources/SemanticIndex/UpdateIndexStoreTaskDescription.swift— FileTooLong — 512 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 12 over it, 1.02× 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.
Off the main sequence: ClangLanguageService (SwiftPM) — ClangLanguageService (SwiftPM): abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 1 project(s), so it's rigid to change.
Off the main sequence: ConfigSchemaGen — ConfigSchemaGen: abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 1 project(s), so it's rigid to change.
Off the main sequence: DocumentationLanguageService — DocumentationLanguageService: abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 1 project(s), so it's rigid to change.
Off the main sequence: SwiftExtensions (SwiftPM) — SwiftExtensions (SwiftPM): abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 6 project(s), so it's rigid to change.
Off the main sequence: SwiftLanguageService (SwiftPM) — SwiftLanguageService (SwiftPM): abstractness 0.05, instability 0.00, distance 0.95 — zone of pain — concrete and depended on by 1 project(s), so it's rigid to change.
Off the main sequence: Diagnose (SwiftPM) — Diagnose (SwiftPM): abstractness 0.06, instability 0.00, distance 0.94 — zone of pain — concrete and depended on by 1 project(s), so it's rigid to change.
Off the main sequence: SourceKitLSP (SwiftPM) — SourceKitLSP (SwiftPM): abstractness 0.06, instability 0.00, distance 0.94 — zone of pain — concrete and depended on by 2 project(s), so it's rigid to change.
Off the main sequence: BuildServerIntegration (SwiftPM) — BuildServerIntegration (SwiftPM): abstractness 0.11, instability 0.00, distance 0.89 — zone of pain — concrete and depended on by 3 project(s), so it's rigid to change.
Off the main sequence: TSCExtensions (SwiftPM) — TSCExtensions (SwiftPM): abstractness 0.00, instability 0.25, distance 0.75 — zone of pain — concrete and depended on by 3 project(s), so it's rigid to change.
Duplicated block (6 lines × 2) Sources/SKTestSupport/SkipUnless.swift:237— Sources/SKTestSupport/SkipUnless.swift:237-242 | Sources/SKTestSupport/SkipUnless.swift:357-366 — 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 `Sources/SKTestSupport/SkipUnless.swift:237` it begins part-way through the construct above it, 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. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (6 lines × 2) Sources/SourceKitLSP/SourceKitLSPServer.swift:2631— Sources/SourceKitLSP/SourceKitLSPServer.swift:2631-2636 | Sources/SourceKitLSP/SourceKitLSPServer.swift:2697-2702 — 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. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (6 lines × 2) Sources/Diagnose/ReduceCommand.swift:65— Sources/Diagnose/ReduceCommand.swift:65-70 | Sources/Diagnose/ReduceFrontendCommand.swift:72-77 — 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. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (6 lines × 2) Sources/SwiftSyntaxCodeActions/AddDocumentation.swift:101— Sources/SwiftSyntaxCodeActions/AddDocumentation.swift:101-106 | Sources/SwiftSyntaxCodeActions/SyntaxRefactoringCodeActionProvider.swift:260-265 — 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.
Duplicated block (6 lines × 2) Sources/SwiftSyntaxCodeActions/ConvertStoredPropertyToComputed.swift:26— Sources/SwiftSyntaxCodeActions/ConvertStoredPropertyToComputed.swift:26-33 | Sources/SwiftSyntaxCodeActions/SyntaxRefactoringCodeActionProvider.swift:249-254 — 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.
TooManyMethods: SourceKitLSPServer Sources/SourceKitLSP/SourceKitLSPServer.swift:41— TooManyMethods — 127 methods, declared across 5 files: SourceKitLSP/SourceKitLSPServer.swift (104), SourceKitLSP/WorkspaceSymbols.swift (14), SourceKitLSP/Rename.swift (7), Diagnose/IndexCommand.swift (1), +1 more file(s). The bar is 30 methods; this is 97 over it, 4.23× the bar. That list is where to read them, not a suggestion to split the file: the members belong to the type wherever they are declared, so moving them between files leaves the count unchanged. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: SwiftLanguageService Sources/SwiftLanguageService/SwiftLanguageService.swift:123— TooManyMethods — 98 methods, declared across 26 files: SwiftLanguageService/SwiftLanguageService.swift (48), SwiftLanguageService/Rename.swift (10), SwiftLanguageService/SemanticTokens.swift (6), SwiftLanguageService/CursorInfo.swift (4), +22 more file(s). The bar is 30 methods; this is 68 over it, 3.27× the bar. That list is where to read them, not a suggestion to split the file: the members belong to the type wherever they are declared, so moving them between files leaves the count unchanged. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: ClangLanguageService Sources/ClangLanguageService/ClangLanguageService.swift:40— TooManyMethods — 56 methods. The bar is 30 methods; this is 26 over it, 1.87× the bar. Most of these members implement SourceKitLSP.LanguageService (47 of 55 members), so moving them onto a smaller type would remove them from that contract rather than reduce it. To reduce it, split the contract instead: give each cohesive group of operations its own smaller interface and its own implementing type. Where the contract has to stay whole, move the work behind these members into collaborator types, so what is left here is a forward per member rather than a responsibility per member.
TooManyMethods: BuildServerManager Sources/BuildServerIntegration/BuildServerManager.swift:395— TooManyMethods — 54 methods, declared across 2 files: BuildServerIntegration/BuildServerManager.swift (52), DocumentationLanguageService/BuildSystemIntegrationExtensions.swift (2). The bar is 30 methods; this is 24 over it, 1.80× the bar. That list is where to read them, not a suggestion to split the file: the members belong to the type wherever they are declared, so moving them between files leaves the count unchanged. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
D4 · Code Duplication· Edited copy of a member (11 corresponding lines) · ×4
Edited copy of a member (11 corresponding lines) Sources/CompletionScoring/Semantics/Components/ModuleProximity.swift:54— Sources/CompletionScoring/Semantics/Components/ModuleProximity.swift:54-70 | Sources/CompletionScoring/Semantics/Components/StructuralProximity.swift:47-57 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (11 corresponding lines) Sources/BuildServerIntegration/FixedCompilationDatabaseBuildServer.swift:97— Sources/BuildServerIntegration/FixedCompilationDatabaseBuildServer.swift:97-107 | Sources/BuildServerIntegration/LegacyBuildServer.swift:158-168 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (11 corresponding lines) Sources/SourceKitD/SKDResponseArray.swift:62— Sources/SourceKitD/SKDResponseArray.swift:62-72 | Sources/SwiftExtensions/Sequence+AsyncMap.swift:15-26 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (11 corresponding lines) Sources/CompletionScoringTestSupport/SymbolGenerator.swift:87— Sources/CompletionScoringTestSupport/SymbolGenerator.swift:87-97 | Sources/CompletionScoringTestSupport/SymbolGenerator.swift:99-109 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (12 corresponding lines) · ×4
Edited copy of a member (12 corresponding lines) Sources/SwiftLanguageService/AdjustPositionToStartOfArgument.swift:70— Sources/SwiftLanguageService/AdjustPositionToStartOfArgument.swift:70-81 | Sources/SwiftLanguageService/AdjustPositionToStartOfIdentifier.swift:52-63 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (12 corresponding lines) Sources/SwiftLanguageService/SelectionRange.swift:184— Sources/SwiftLanguageService/SelectionRange.swift:184-212 | Sources/SwiftLanguageService/SelectionRange.swift:323-334 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (12 corresponding lines) Sources/BuildServerIntegration/FixedCompilationDatabaseBuildServer.swift:84— Sources/BuildServerIntegration/FixedCompilationDatabaseBuildServer.swift:84-95 | Sources/BuildServerIntegration/LegacyBuildServer.swift:144-156 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (12 corresponding lines) Sources/SwiftSourceKitPlugin/CompletionProvider.swift:218— Sources/SwiftSourceKitPlugin/CompletionProvider.swift:218-229 | Sources/SwiftSourceKitPlugin/CompletionProvider.swift:231-242 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (8 corresponding lines) · ×4
Edited copy of a member (8 corresponding lines) Sources/CompletionScoring/Text/CandidateBatch.swift:151— Sources/CompletionScoring/Text/CandidateBatch.swift:151-158 | Sources/CompletionScoring/Text/CandidateBatch.swift:160-167 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (8 corresponding lines) Sources/SKTestSupport/Assertions.swift:123— Sources/SKTestSupport/Assertions.swift:123-130 | Sources/SKTestSupport/Assertions.swift:133-140 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (8 corresponding lines) Sources/DocumentationLanguageService/DocCSymbolInformation.swift:40— Sources/DocumentationLanguageService/DocCSymbolInformation.swift:40-47 | Sources/DocumentationLanguageService/DocCSymbolInformation.swift:49-57 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (8 corresponding lines) Sources/BuildServerIntegration/BuildSettingsLogger.swift:44— Sources/BuildServerIntegration/BuildSettingsLogger.swift:44-51 | Sources/SemanticIndex/UpdateIndexStoreTaskDescription.swift:826-837 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Duplicated block (9 lines × 2) Sources/ClangLanguageService/SemanticTokenTranslator.swift:50— Sources/ClangLanguageService/SemanticTokenTranslator.swift:50-58 | Sources/ClangLanguageService/SemanticTokenTranslator.swift:64-74 — 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 `Sources/ClangLanguageService/SemanticTokenTranslator.swift:50` it begins part-way through the construct above it, 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.
Duplicated block (9 lines × 2) Sources/SemanticIndex/TaskScheduler.swift:721— Sources/SemanticIndex/TaskScheduler.swift:721-730 | Sources/SemanticIndex/TaskScheduler.swift:747-755 — 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. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (9 lines × 2) Sources/SwiftLanguageService/InlayHintResolve.swift:74— Sources/SwiftLanguageService/InlayHintResolve.swift:74-82 | Sources/SwiftLanguageService/TypeDefinition.swift:28-36 — 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.
Duplicated block (9 lines × 2) Sources/SourceKitD/SKDResponseArray.swift:95— Sources/SourceKitD/SKDResponseArray.swift:95-103 | Sources/SwiftSourceKitPlugin/SKDRequestArrayReader.swift:60-68 — 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. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (5 lines × 2) Sources/CompletionScoring/Utilities/SwiftExtensions.swift:239— Sources/CompletionScoring/Utilities/SwiftExtensions.swift:239-243 | Sources/CompletionScoring/Utilities/SwiftExtensions.swift:252-256 — 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 (5 lines × 2) Sources/SwiftSyntaxCodeActions/ApplyDeMorganLaw.swift:252— Sources/SwiftSyntaxCodeActions/ApplyDeMorganLaw.swift:252-256 | Sources/SwiftSyntaxCodeActions/ApplyDeMorganLaw.swift:366-370 — 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Sources/SwiftSyntaxCodeActions/ApplyDeMorganLaw.swift:364` calls `isAndOperator` and `Sources/SwiftSyntaxCodeActions/ApplyDeMorganLaw.swift:250` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (5 lines × 2) Sources/SwiftSourceKitClientPlugin/ClientPlugin.swift:23— Sources/SwiftSourceKitClientPlugin/ClientPlugin.swift:23-27 | Sources/SwiftSourceKitPlugin/Plugin.swift:164-168 — 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.
Duplicated block (5 lines × 2) Sources/SwiftLanguageService/Rename.swift:362— Sources/SwiftLanguageService/Rename.swift:362-366 | Sources/SwiftLanguageService/Rename.swift:413-417 — 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 `Sources/SwiftLanguageService/Rename.swift:362` it does not close everything it opens, 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· Edited copy of a member (20 corresponding lines) · ×3
Edited copy of a member (20 corresponding lines) Sources/Diagnose/DiagnoseCommand.swift:268— Sources/Diagnose/DiagnoseCommand.swift:268-287 | Sources/Diagnose/DiagnoseCommand.swift:295-319 — These two members are one piece of code written twice and then edited apart: 20 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (20 corresponding lines) Sources/BuildServerIntegration/BuildTargetIdentifierExtensions.swift:76— Sources/BuildServerIntegration/BuildTargetIdentifierExtensions.swift:76-95 | Sources/BuildServerIntegration/BuildTargetIdentifierExtensions.swift:124-145 — These two members are one piece of code written twice and then edited apart: 20 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (20 corresponding lines) Sources/BuildServerIntegration/BuildTargetIdentifierExtensions.swift:45— Sources/BuildServerIntegration/BuildTargetIdentifierExtensions.swift:45-71 | Sources/BuildServerIntegration/BuildTargetIdentifierExtensions.swift:102-121 — These two members are one piece of code written twice and then edited apart: 20 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (17 corresponding lines) · ×3
Edited copy of a member (17 corresponding lines) Sources/SwiftSyntaxCodeActions/GenerateEnumCaseAccessors.swift:31— Sources/SwiftSyntaxCodeActions/GenerateEnumCaseAccessors.swift:31-54 | Sources/SwiftSyntaxCodeActions/GenerateEnumCaseAccessors.swift:107-123 — These two members are one piece of code written twice and then edited apart: 17 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (17 corresponding lines) Sources/SourceKitLSP/LSP+CopiedFileMap.swift:83— Sources/SourceKitLSP/LSP+CopiedFileMap.swift:83-99 | Sources/SourceKitLSP/LSP+CopiedFileMap.swift:103-119 — These two members are one piece of code written twice and then edited apart: 17 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (17 corresponding lines) Sources/CompletionScoring/Text/Pattern.swift:1133— Sources/CompletionScoring/Text/Pattern.swift:1133-1150 | Sources/CompletionScoring/Text/Pattern.swift:1152-1168 — These two members are one piece of code written twice and then edited apart: 17 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (7 corresponding lines) · ×3
Edited copy of a member (7 corresponding lines) Sources/BuildServerIntegration/CompilationDatabase.swift:74— Sources/BuildServerIntegration/CompilationDatabase.swift:74-80 | Sources/ToolchainRegistry/XCToolchainPlist.swift:107-115 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (7 corresponding lines) Sources/CompletionScoring/Text/CandidateBatch.swift:211— Sources/CompletionScoring/Text/CandidateBatch.swift:211-217 | Sources/CompletionScoring/Text/CandidateBatch.swift:219-225 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (7 corresponding lines) Sources/SourceKitD/SKDRequestDictionary.swift:47— Sources/SourceKitD/SKDRequestDictionary.swift:47-53 | Sources/SwiftSourceKitPlugin/SKDResponseDictionaryBuilder.swift:18-26 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Duplicated block (15 lines × 2) Sources/SKUtilities/LineTable.swift:329— Sources/SKUtilities/LineTable.swift:329-343 | Sources/SKUtilities/LineTable.swift:352-366 — 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 (15 lines × 2) Sources/SKUtilities/LineTable.swift:435— Sources/SKUtilities/LineTable.swift:435-449 | Sources/SKUtilities/LineTable.swift:472-486 — 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 `Sources/SKUtilities/LineTable.swift:435` it begins part-way through the construct above it, 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.
Duplicated block (15 lines × 2) Sources/SwiftSyntaxCodeActions/OpaqueParameterToGeneric.swift:182— Sources/SwiftSyntaxCodeActions/OpaqueParameterToGeneric.swift:182-196 | Sources/SwiftSyntaxCodeActions/OpaqueParameterToGeneric.swift:200-214 — 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 `Sources/SwiftSyntaxCodeActions/OpaqueParameterToGeneric.swift:182` it begins part-way through the construct above it, 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. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (11 lines × 2) Sources/BuildServerIntegration/BuildTargetIdentifierExtensions.swift:76— Sources/BuildServerIntegration/BuildTargetIdentifierExtensions.swift:76-86 | Sources/BuildServerIntegration/BuildTargetIdentifierExtensions.swift:124-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. Read the line range as the matched WINDOW rather than a finished unit: at `Sources/BuildServerIntegration/BuildTargetIdentifierExtensions.swift:76` it does not close everything it opens, 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.
Duplicated block (11 lines × 2) Sources/SKUtilities/LineTable.swift:261— Sources/SKUtilities/LineTable.swift:261-271 | Sources/SKUtilities/LineTable.swift:307-318 — 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 `Sources/SKUtilities/LineTable.swift:261` it begins part-way through the construct above it, 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. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (11 lines × 2) Sources/SwiftLanguageService/SwiftTestingScanner.swift:172— Sources/SwiftLanguageService/SwiftTestingScanner.swift:172-183 | Sources/SwiftLanguageService/SyntacticSwiftXCTestScanner.swift:34-44 — 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 `Sources/SwiftLanguageService/SwiftTestingScanner.swift:172` it does not close everything it opens, 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.
Duplicated block (10 lines × 2) Sources/Diagnose/CommandLineArgumentsReducer.swift:84— Sources/Diagnose/CommandLineArgumentsReducer.swift:84-93 | Sources/Diagnose/CommandLineArgumentsReducer.swift:101-110 — 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. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (10 lines × 2) Sources/SKTestSupport/MultiFileTestProject.swift:132— Sources/SKTestSupport/MultiFileTestProject.swift:132-141 | Sources/SKTestSupport/SwiftPMTestProject.swift:179-188 — 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.
Duplicated block (10 lines × 2) Sources/SemanticIndex/SemanticIndexManager.swift:434— Sources/SemanticIndex/SemanticIndexManager.swift:434-443 | Sources/SemanticIndex/SemanticIndexManager.swift:463-472 — 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.
D4 · Code Duplication· Edited copy of a member (30 corresponding lines) · ×2
Edited copy of a member (30 corresponding lines) Sources/SwiftSourceKitPlugin/SKDResponseArrayBuilder.swift:40— Sources/SwiftSourceKitPlugin/SKDResponseArrayBuilder.swift:40-69 | Sources/SwiftSourceKitPlugin/SKDResponseDictionaryBuilder.swift:43-72 — These two members are one piece of code written twice and then edited apart: 30 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (30 corresponding lines) Sources/BuildServerIntegration/BuildServerMessageDependencyTracker.swift:47— Sources/BuildServerIntegration/BuildServerMessageDependencyTracker.swift:47-76 | Sources/BuildServerIntegration/BuildServerMessageDependencyTracker.swift:78-108 — These two members are one piece of code written twice and then edited apart: 30 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (18 corresponding lines) · ×2
Edited copy of a member (18 corresponding lines) Sources/BuildServerIntegration/SwiftToolchainResolver.swift:58— Sources/BuildServerIntegration/SwiftToolchainResolver.swift:58-77 | Sources/BuildServerIntegration/SwiftToolchainResolver.swift:79-96 — These two members are one piece of code written twice and then edited apart: 18 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (18 corresponding lines) Sources/ToolchainRegistry/ToolchainRegistry.swift:348— Sources/ToolchainRegistry/ToolchainRegistry.swift:348-366 | Sources/ToolchainRegistry/ToolchainRegistry.swift:369-386 — These two members are one piece of code written twice and then edited apart: 18 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (25 corresponding lines) · ×2
Edited copy of a member (25 corresponding lines) Sources/SemanticIndex/CheckedIndex.swift:451— Sources/SemanticIndex/CheckedIndex.swift:451-475 | Sources/SemanticIndex/CheckedIndex.swift:479-510 — These two members are one piece of code written twice and then edited apart: 25 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (25 corresponding lines) Sources/CompletionScoring/Text/Pattern.swift:147— Sources/CompletionScoring/Text/Pattern.swift:147-172 | Sources/CompletionScoring/Text/Pattern.swift:174-198 — These two members are one piece of code written twice and then edited apart: 25 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (19 corresponding lines) · ×2
Edited copy of a member (19 corresponding lines) Sources/BuildServerIntegration/SplitShellCommand.swift:60— Sources/BuildServerIntegration/SplitShellCommand.swift:60-79 | Sources/BuildServerIntegration/SplitShellCommand.swift:97-115 — These two members are one piece of code written twice and then edited apart: 19 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (19 corresponding lines) Sources/SourceKitLSP/CapabilityRegistry.swift:255— Sources/SourceKitLSP/CapabilityRegistry.swift:255-273 | Sources/SourceKitLSP/CapabilityRegistry.swift:275-293 — These two members are one piece of code written twice and then edited apart: 19 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (4 members, 12+ corresponding lines) · ×2
Edited copies of one member (4 members, 12+ corresponding lines) Sources/Diagnose/SourceReducer.swift:367— Sources/Diagnose/SourceReducer.swift:367-385 | Sources/Diagnose/SourceReducer.swift:437-451 | Sources/Diagnose/SourceReducer.swift:487-498 | Sources/Diagnose/SourceReducer.swift:500-511 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 12 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
Edited copies of one member (4 members, 12+ corresponding lines) Sources/CompletionScoring/Semantics/Components/Availability.swift:54— Sources/CompletionScoring/Semantics/Components/Availability.swift:54-66 | Sources/CompletionScoring/Semantics/Components/ScopeProximity.swift:66-80 | Sources/CompletionScoring/Semantics/Components/SynchronicityCompatibility.swift:50-61 | Sources/CompletionScoring/Semantics/Components/TypeCompatibility.swift:65-76 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 12 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (10 corresponding lines) · ×2
Edited copy of a member (10 corresponding lines) Sources/SKTestSupport/FileManager+findFiles.swift:17— Sources/SKTestSupport/FileManager+findFiles.swift:17-26 | Sources/SKTestSupport/FileManager+findFiles.swift:29-38 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (10 corresponding lines) Sources/Diagnose/CommandLineArgumentsReducer.swift:19— Sources/Diagnose/CommandLineArgumentsReducer.swift:19-28 | Sources/Diagnose/SourceReducer.swift:25-34 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 9+ corresponding lines) · ×2
Edited copies of one member (3 members, 9+ corresponding lines) Sources/SourceKitLSP/DocumentSnapshot+PositionConversions.swift:82— Sources/SourceKitLSP/DocumentSnapshot+PositionConversions.swift:82-90 | Sources/SourceKitLSP/DocumentSnapshot+PositionConversions.swift:182-190 | Sources/SourceKitLSP/DocumentSnapshot+PositionConversions.swift:192-200 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 9 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 9+ corresponding lines) Sources/SourceKitD/SourceKitDCore.swift:67— Sources/SourceKitD/SourceKitDCore.swift:67-77 | Sources/SwiftSourceKitClientPlugin/ClientPlugin.swift:65-73 | Sources/SwiftSourceKitPlugin/Plugin.swift:291-300 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 9 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (14 corresponding lines) · ×2
Edited copy of a member (14 corresponding lines) Sources/SwiftSyntaxCodeActions/AddDocumentation.swift:112— Sources/SwiftSyntaxCodeActions/AddDocumentation.swift:112-125 | Sources/SwiftSyntaxCodeActions/AddDocumentation.swift:138-151 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (14 corresponding lines) Sources/SwiftLanguageService/CodeCompletionSession.swift:402— Sources/SwiftLanguageService/CodeCompletionSession.swift:402-415 | Sources/SwiftLanguageService/SwiftLanguageService.swift:352-365 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Duplicated block (8 lines × 2) Sources/SKTestSupport/CheckCoding.swift:67— Sources/SKTestSupport/CheckCoding.swift:67-74 | Sources/SKTestSupport/CheckCoding.swift:103-110 — 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 `Sources/SKTestSupport/CheckCoding.swift:67` it begins part-way through the construct above it, 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.
Duplicated block (8 lines × 2) Sources/SKTestSupport/CustomBuildServerTestProject.swift:279— Sources/SKTestSupport/CustomBuildServerTestProject.swift:279-286 | Sources/SKTestSupport/SwiftPMTestProject.swift:183-190 — 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.
Duplicated block (7 lines × 2) Sources/BuildServerIntegration/SwiftPMBuildServer.swift:902— Sources/BuildServerIntegration/SwiftPMBuildServer.swift:902-909 | Sources/SemanticIndex/UpdateIndexStoreTaskDescription.swift:662-668 — 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 `Sources/BuildServerIntegration/SwiftPMBuildServer.swift:902` it begins part-way through the construct above it, 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. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (7 lines × 2) Sources/Diagnose/CommandLineArgumentsReducer.swift:45— Sources/Diagnose/CommandLineArgumentsReducer.swift:45-51 | Sources/Diagnose/SourceReducer.swift:81-87 — 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.
sourcekitd_api_uid_t.init (cyclomatic 56) Sources/SwiftSourceKitPlugin/CompletionProvider.swift:445— sourcekitd_api_uid_t.init has cyclomatic complexity 56 (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.
Pattern.singleScore (cyclomatic 41) Sources/CompletionScoring/Text/Pattern.swift:452— Pattern.singleScore has cyclomatic complexity 41 (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.
CodeCompletionSession.completionsFromSKDResponse (cyclomatic 33) Sources/SwiftLanguageService/CodeCompletionSession.swift:498— CodeCompletionSession.completionsFromSKDResponse has cyclomatic complexity 33 (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.
Diagnostic.init (cyclomatic 33) Sources/SwiftLanguageService/Diagnostic.swift:168— Diagnostic.init has cyclomatic complexity 33 (threshold 15). Of this number, 30 points are the body's own statements and 3 belong to one function item inside it that branches. 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.
BuildServerConfig.forSwiftPMBuildServer (cyclomatic 32) Sources/BuildServerIntegration/ExternalBuildServerAdapter.swift:92— BuildServerConfig.forSwiftPMBuildServer has cyclomatic complexity 32 (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.
PriorityBucket.init (cyclomatic 26) Sources/SwiftSourceKitPlugin/ASTCompletion/ASTCompletionItem.swift:566— PriorityBucket.init has cyclomatic complexity 26 (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. This is NOT this file's highest cyclomatic complexity: Kind.init (cyclomatic 40) is higher and carries no row of its own — it was excluded as a flat dispatcher (a long switch/match over independent cases: many branches, almost no nesting), which this dimension does not treat as a refactor obligation. It is named here so the ranking you see in this file is not mistaken for the whole of it; the excluded method is counted neither in this dimension's figures nor in its score.
SemanticIndexManager.scheduleIndexing (cyclomatic 25) Sources/SemanticIndex/SemanticIndexManager.swift:867— SemanticIndexManager.scheduleIndexing has cyclomatic complexity 25 (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.
UpdateIndexStoreTaskDescription.updateIndexStore (cyclomatic 24) Sources/SemanticIndex/UpdateIndexStoreTaskDescription.swift:286— UpdateIndexStoreTaskDescription.updateIndexStore has cyclomatic complexity 24 (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.
BuildServerManager.buildSettingsInferredFromMainFile (cyclomatic 23) Sources/BuildServerIntegration/BuildServerManager.swift:1366— BuildServerManager.buildSettingsInferredFromMainFile has cyclomatic complexity 23 (threshold 15). Most of this is not in the body itself: 11 of the 23 points are its own statements and the rest belongs to one function item inside it that branches (mainFileAndSettings). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
Pattern.populateMatchingRangesForAcronymMatch (cyclomatic 23) Sources/CompletionScoring/Text/Pattern.swift:271— Pattern.populateMatchingRangesForAcronymMatch has cyclomatic complexity 23 (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.
Toolchain.init (cyclomatic 23) Sources/ToolchainRegistry/Toolchain.swift:235— Toolchain.init has cyclomatic complexity 23 (threshold 15). Of this number, 20 points are the body's own statements and 3 belong to one function item inside it that branches. 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.
SourceKitLSPServer.rename (cyclomatic 22) Sources/SourceKitLSP/Rename.swift:280— SourceKitLSPServer.rename has cyclomatic complexity 22 (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.
XMLToMarkdown.toMarkdown (cyclomatic 22) Sources/SwiftLanguageService/CommentXML.swift:77— XMLToMarkdown.toMarkdown has cyclomatic complexity 22 (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.
SwiftPMBuildServer.prepare (cyclomatic 21) Sources/BuildServerIntegration/SwiftPMBuildServer.swift:791— SwiftPMBuildServer.prepare has cyclomatic complexity 21 (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.
SwiftLanguageService.expandMacro (cyclomatic 20) Sources/SwiftLanguageService/MacroExpansion.swift:137— SwiftLanguageService.expandMacro has cyclomatic complexity 20 (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.
SwiftLanguageService.removeUnusedImports (cyclomatic 20) Sources/SwiftLanguageService/RemoveUnusedImports.swift:112— SwiftLanguageService.removeUnusedImports has cyclomatic complexity 20 (threshold 15). Of this number, 15 points are the body's own statements and 5 belong to one function item inside it that branches. 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.
AddExplicitEnumRawValues.textRefactor (cyclomatic 20) Sources/SwiftSyntaxCodeActions/AddExplicitEnumRawValues.swift:48— AddExplicitEnumRawValues.textRefactor has cyclomatic complexity 20 (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.
SourceKitLSPServer.indexBasedDefinition (cyclomatic 19) Sources/SourceKitLSP/SourceKitLSPServer.swift:1914— SourceKitLSPServer.indexBasedDefinition has cyclomatic complexity 19 (threshold 15). Of this number, 17 points are the body's own statements and 2 belong to one function item inside it that branches. 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. This is NOT this file's highest cyclomatic complexity: SourceKitLSPServer.handle (cyclomatic 63) is higher and carries no row of its own — it was excluded as a flat dispatcher (a long switch/match over independent cases: many branches, almost no nesting), which this dimension does not treat as a refactor obligation. It is named here so the ranking you see in this file is not mistaken for the whole of it; the excluded method is counted neither in this dimension's figures nor in its score.
SemanticIndexManager.filesToIndex (cyclomatic 18) Sources/SemanticIndex/SemanticIndexManager.swift:505— SemanticIndexManager.filesToIndex 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.
ConvertStringConcatenationToStringInterpolation.refactor (cyclomatic 18) Sources/SwiftSyntaxCodeActions/ConvertStringConcatenationToStringInterpolation.swift:21— ConvertStringConcatenationToStringInterpolation.refactor 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.
BuildServerManager.init (cyclomatic 17) Sources/BuildServerIntegration/BuildServerManager.swift:580— BuildServerManager.init has cyclomatic complexity 17 (threshold 15). Of this number, 16 points are the body's own statements and 1 belongs to one function item inside it that branches. 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.
JSONSchemaBuilder.buildJSONSchema (cyclomatic 17) SourceKitLSPDevUtils/Sources/ConfigSchemaGen/JSONSchema.swift:106— JSONSchemaBuilder.buildJSONSchema has cyclomatic complexity 17 (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.
SwiftLanguageService.findFunctionLikeRange (cyclomatic 17) Sources/SwiftLanguageService/Rename.swift:502— SwiftLanguageService.findFunctionLikeRange has cyclomatic complexity 17 (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.
SwiftLanguageService.textEdit (cyclomatic 17) Sources/SwiftLanguageService/Rename.swift:798— SwiftLanguageService.textEdit has cyclomatic complexity 17 (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.
build-script-helper.get_swiftpm_options (cyclomatic 17) Utilities/build-script-helper.py:98— build-script-helper.get_swiftpm_options has cyclomatic complexity 17 (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.
TaskScheduler.poke (cyclomatic 16) Sources/SemanticIndex/TaskScheduler.swift:662— TaskScheduler.poke 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.
DiagnosticReportManager.requestReport (cyclomatic 16) Sources/SwiftLanguageService/DiagnosticReportManager.swift:111— DiagnosticReportManager.requestReport 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.
SwiftLanguageService.editsToRename (cyclomatic 16) Sources/SwiftLanguageService/Rename.swift:858— SwiftLanguageService.editsToRename has cyclomatic complexity 16 (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.
RequestHandler.handleRequest (cyclomatic 16) Sources/SwiftSourceKitPlugin/Plugin.swift:55— RequestHandler.handleRequest has cyclomatic complexity 16 (threshold 15). Of this number, 15 points are the body's own statements and 1 belongs to one function item inside it that branches. 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.
RemoveRedundantParentheses.canRemoveParentheses (cyclomatic 16) Sources/SwiftSyntaxCodeActions/RemoveRedundantParentheses.swift:72— RemoveRedundantParentheses.canRemoveParentheses 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.
Hotspot: Sources/SwiftLanguageService/CodeCompletionSession.swift Sources/SwiftLanguageService/CodeCompletionSession.swift:498— Sources/SwiftLanguageService/CodeCompletionSession.swift changed 7 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 33 in CodeCompletionSession.completionsFromSKDResponse at line 498. 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-08-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 11:54:30 -08:00' --until='2026-11-14 11:54:30 -08:00' --full-history --no-merges -- Sources/SwiftLanguageService/CodeCompletionSession.swift`: 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.
Pattern.singleScore (cognitive 97) Sources/CompletionScoring/Text/Pattern.swift:452— Pattern.singleScore has cognitive complexity 97 (threshold 15). Drivers by points: if/else 22 (56 pts), ternaries 4 (17 pts), boolean chains 12, loops 4 (12 pts) (nesting depth added 55). 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.
sourcekitd_api_uid_t.init (cognitive 51) Sources/SwiftSourceKitPlugin/CompletionProvider.swift:445— sourcekitd_api_uid_t.init has cognitive complexity 51 (threshold 15). Drivers by points: ternaries 25 (50 pts), match/switch 1 (nesting depth added 25). 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.
CodeCompletionSession.completionsFromSKDResponse (cognitive 44) Sources/SwiftLanguageService/CodeCompletionSession.swift:498— CodeCompletionSession.completionsFromSKDResponse has cognitive complexity 44 (threshold 15). Drivers by points: if/else 24 (30 pts), boolean chains 12, match/switch 1 (2 pts) (nesting depth added 7). 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.
Toolchain.init (cognitive 42) Sources/ToolchainRegistry/Toolchain.swift:235— Toolchain.init has cognitive complexity 42 (threshold 15). Drivers by points: if/else 22 (39 pts), boolean chains 2, loops 1 (nesting depth added 17). Of this number, 36 points are the body's own statements and 6 belong to one function item inside it that branches. 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.
BuildServerConfig.forSwiftPMBuildServer (cognitive 38) Sources/BuildServerIntegration/ExternalBuildServerAdapter.swift:92— BuildServerConfig.forSwiftPMBuildServer has cognitive complexity 38 (threshold 15). Drivers by points: if/else 22, loops 7 (14 pts), boolean chains 2 (nesting depth added 7). 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.
Diagnostic.init (cognitive 38) Sources/SwiftLanguageService/Diagnostic.swift:168— Diagnostic.init has cognitive complexity 38 (threshold 15). Drivers by points: if/else 20 (23 pts), boolean chains 10, match/switch 2 (4 pts), error handling 1 (nesting depth added 5). Of this number, 35 points are the body's own statements and 3 belong to one function item inside it that branches. 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.
SemanticIndexManager.filesToIndex (cognitive 37) Sources/SemanticIndex/SemanticIndexManager.swift:505— SemanticIndexManager.filesToIndex has cognitive complexity 37 (threshold 15). Drivers by points: if/else 12 (31 pts), boolean chains 3, loops 2 (3 pts) (nesting depth added 20). 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.
SemanticIndexManager.scheduleIndexing (cognitive 37) Sources/SemanticIndex/SemanticIndexManager.swift:867— SemanticIndexManager.scheduleIndexing has cognitive complexity 37 (threshold 15). Drivers by points: if/else 14 (25 pts), loops 5 (9 pts), match/switch 2, boolean chains 1 (nesting depth added 15). 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.
AddExplicitEnumRawValues.textRefactor (cognitive 37) Sources/SwiftSyntaxCodeActions/AddExplicitEnumRawValues.swift:48— AddExplicitEnumRawValues.textRefactor has cognitive complexity 37 (threshold 15). Drivers by points: if/else 14 (30 pts), loops 3 (5 pts), boolean chains 1, match/switch 1 (nesting depth added 18). 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.
Pattern.populateMatchingRangesForAcronymMatch (cognitive 36) Sources/CompletionScoring/Text/Pattern.swift:271— Pattern.populateMatchingRangesForAcronymMatch has cognitive complexity 36 (threshold 15). Drivers by points: boolean chains 14, if/else 6 (12 pts), loops 2 (5 pts), ternaries 2 (5 pts) (nesting depth added 12). 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.
TaskScheduler.poke (cognitive 34) Sources/SemanticIndex/TaskScheduler.swift:662— TaskScheduler.poke has cognitive complexity 34 (threshold 15). Drivers by points: if/else 10 (23 pts), loops 3 (7 pts), match/switch 2 (4 pts) (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.
UpdateIndexStoreTaskDescription.updateIndexStore (cognitive 33) Sources/SemanticIndex/UpdateIndexStoreTaskDescription.swift:286— UpdateIndexStoreTaskDescription.updateIndexStore has cognitive complexity 33 (threshold 15). Drivers by points: if/else 9 (15 pts), error handling 2 (7 pts), loops 5 (7 pts), match/switch 2 (4 pts) (nesting depth added 15). 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.
Pattern.bestScore (cognitive 31) Sources/CompletionScoring/Text/Pattern.swift:1007— Pattern.bestScore has cognitive complexity 31 (threshold 15). Drivers by points: if/else 9 (25 pts), loops 2 (4 pts), boolean chains 2 (nesting depth added 18). 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.
OSLogScraper.requestInfo (cognitive 31) Sources/Diagnose/OSLogScraper.swift:44— OSLogScraper.requestInfo has cognitive complexity 31 (threshold 15). Drivers by points: if/else 10 (25 pts), loops 2 (3 pts), match/switch 1 (3 pts) (nesting depth added 18). 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.
SourceKitLSPServer.rename (cognitive 30) Sources/SourceKitLSP/Rename.swift:280— SourceKitLSPServer.rename has cognitive complexity 30 (threshold 15). Drivers by points: if/else 13 (21 pts), match/switch 2 (4 pts), loops 3, boolean chains 2 (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.
JSONSchemaBuilder.buildJSONSchema (cognitive 30) SourceKitLSPDevUtils/Sources/ConfigSchemaGen/JSONSchema.swift:106— JSONSchemaBuilder.buildJSONSchema has cognitive complexity 30 (threshold 15). Drivers by points: if/else 6 (19 pts), loops 3 (10 pts), match/switch 1 (nesting depth added 20). 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.
SwiftPMBuildServer.buildTargetSources (cognitive 29) Sources/BuildServerIntegration/SwiftPMBuildServer.swift:643— SwiftPMBuildServer.buildTargetSources has cognitive complexity 29 (threshold 15). Drivers by points: if/else 7 (15 pts), loops 4 (7 pts), ternaries 2 (6 pts), boolean chains 1 (nesting depth added 15). 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.
SourceKitLSPServer.indexBasedDefinition (cognitive 28) Sources/SourceKitLSP/SourceKitLSPServer.swift:1914— SourceKitLSPServer.indexBasedDefinition has cognitive complexity 28 (threshold 15). Drivers by points: if/else 11 (19 pts), boolean chains 9 (nesting depth added 8). Of this number, 26 points are the body's own statements and 2 belong to one function item inside it that branches. 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.
ConvertStringConcatenationToStringInterpolation.refactor (cognitive 27) Sources/SwiftSyntaxCodeActions/ConvertStringConcatenationToStringInterpolation.swift:21— ConvertStringConcatenationToStringInterpolation.refactor has cognitive complexity 27 (threshold 15). Drivers by points: if/else 10 (19 pts), boolean chains 4, ternaries 3, loops 1 (nesting depth added 9). 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.
SourceKitD.send (cognitive 26) Sources/SourceKitD/SourceKitD.swift:330— SourceKitD.send has cognitive complexity 26 (threshold 15). Drivers by points: if/else 8 (15 pts), loops 2 (7 pts), boolean chains 2, error handling 1, ternaries 1 (nesting depth added 12). 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.
Pattern.matchLocation (cognitive 25) Sources/CompletionScoring/Text/Pattern.swift:70— Pattern.matchLocation has cognitive complexity 25 (threshold 15). Drivers by points: if/else 4 (11 pts), ternaries 2 (6 pts), boolean chains 4, loops 1 (4 pts) (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.
SourceKitLSPServer.initialize (cognitive 25) Sources/SourceKitLSP/SourceKitLSPServer.swift:888— SourceKitLSPServer.initialize has cognitive complexity 25 (threshold 15). Drivers by points: if/else 10 (17 pts), ternaries 2 (4 pts), boolean chains 2, loops 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.
SwiftLanguageService.expandMacro (cognitive 25) Sources/SwiftLanguageService/MacroExpansion.swift:137— SwiftLanguageService.expandMacro has cognitive complexity 25 (threshold 15). Drivers by points: if/else 9 (14 pts), error handling 2 (4 pts), boolean chains 3, match/switch 2 (3 pts), loops 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.
RewriteSourceKitPlaceholders.swift.rewriteSourceKitPlaceholders (cognitive 24) Sources/SwiftLanguageService/RewriteSourceKitPlaceholders.swift:23— RewriteSourceKitPlaceholders.swift.rewriteSourceKitPlaceholders has cognitive complexity 24 (threshold 15). Drivers by points: if/else 8 (18 pts), ternaries 1 (3 pts), match/switch 1 (2 pts), loops 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.
SwiftLanguageService.removeUnusedImports (cognitive 22) Sources/SwiftLanguageService/RemoveUnusedImports.swift:112— SwiftLanguageService.removeUnusedImports has cognitive complexity 22 (threshold 15). Drivers by points: if/else 13 (17 pts), boolean chains 3, loops 1, match/switch 1 (nesting depth added 4). Of this number, 19 points are the body's own statements and 3 belong to one function item inside it that branches. 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.
ExternalBuildServerAdapter.getConfigPath (cognitive 21) Sources/BuildServerIntegration/ExternalBuildServerAdapter.swift:357— ExternalBuildServerAdapter.getConfigPath has cognitive complexity 21 (threshold 15). Drivers by points: if/else 11 (19 pts), boolean chains 1, loops 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.
SourceKitLSPServer.implementation (cognitive 21) Sources/SourceKitLSP/SourceKitLSPServer.swift:2089— SourceKitLSPServer.implementation has cognitive complexity 21 (threshold 15). Drivers by points: if/else 8 (13 pts), boolean chains 3, loops 3, ternaries 1 (2 pts) (nesting depth added 6). Of this number, 16 points are the body's own statements and 5 belong to one function item inside it that branches. 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.
ConvertStringConcatenationToStringInterpolation.preflight (cognitive 21) Sources/SwiftSyntaxCodeActions/ConvertStringConcatenationToStringInterpolation.swift:150— ConvertStringConcatenationToStringInterpolation.preflight has cognitive complexity 21 (threshold 15). Drivers by points: if/else 8 (15 pts), boolean chains 5, loops 1 (nesting depth added 7). 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.
SourceKitLSPServer.symbolItems (cognitive 20) Sources/SourceKitLSP/WorkspaceSymbols.swift:108— SourceKitLSPServer.symbolItems has cognitive complexity 20 (threshold 15). Drivers by points: if/else 7 (12 pts), loops 6 (8 pts) (nesting depth added 7). 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.
BuildServerManager.init (cognitive 19) Sources/BuildServerIntegration/BuildServerManager.swift:580— BuildServerManager.init has cognitive complexity 19 (threshold 15). Drivers by points: if/else 12 (14 pts), boolean chains 4, error handling 1 (nesting depth added 2). Of this number, 17 points are the body's own statements and 2 belong to one function item inside it that branches. 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.
SwiftPMBuildServer.searchForConfig (cognitive 19) Sources/BuildServerIntegration/SwiftPMBuildServer.swift:156— SwiftPMBuildServer.searchForConfig has cognitive complexity 19 (threshold 15). Drivers by points: if/else 11 (14 pts), error handling 1 (3 pts), boolean chains 2 (nesting depth added 5). 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.
SwiftPMBuildServer.loadBuildDescriptionWithRetryOnOutputFileMapWriteErrorOnWindows (cognitive 19) Sources/BuildServerIntegration/SwiftPMBuildServer.swift:427— SwiftPMBuildServer.loadBuildDescriptionWithRetryOnOutputFileMapWriteErrorOnWindows has cognitive complexity 19 (threshold 15). Drivers by points: if/else 5 (11 pts), boolean chains 5, error handling 1 (2 pts), loops 1 (nesting depth added 7). 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.
RemoveRedundantParentheses.canRemoveParentheses (cognitive 19) Sources/SwiftSyntaxCodeActions/RemoveRedundantParentheses.swift:72— RemoveRedundantParentheses.canRemoveParentheses has cognitive complexity 19 (threshold 15). Drivers by points: if/else 9, boolean chains 6, match/switch 2 (4 pts) (nesting depth added 2). 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.
OutOfProcessSourceKitRequestExecutor.requestResult (cognitive 18) Sources/Diagnose/SourceKitDRequestExecutor.swift:100— OutOfProcessSourceKitRequestExecutor.requestResult has cognitive complexity 18 (threshold 15). Drivers by points: if/else 9 (13 pts), match/switch 2 (4 pts), boolean chains 1 (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.
SourceKitLSPServer.subtypes (cognitive 18) Sources/SourceKitLSP/SourceKitLSPServer.swift:2696— SourceKitLSPServer.subtypes has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8 (14 pts), boolean chains 3, loops 1 (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.
SourceKitLSPServer.members (cognitive 18) Sources/SourceKitLSP/WorkspaceSymbols.swift:628— SourceKitLSPServer.members has cognitive complexity 18 (threshold 15). Drivers by points: boolean chains 5, ternaries 1 (4 pts), if/else 1 (3 pts), loops 2 (3 pts), match/switch 1 (3 pts) (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.
Workspace.swift.createIndex (cognitive 18) Sources/SourceKitLSP/Workspace.swift:78— Workspace.swift.createIndex has cognitive complexity 18 (threshold 15). Drivers by points: if/else 10 (14 pts), boolean chains 2, error handling 1 (2 pts) (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.
DiagnosticReportManager.requestReport (cognitive 18) Sources/SwiftLanguageService/DiagnosticReportManager.swift:111— DiagnosticReportManager.requestReport has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7 (9 pts), boolean chains 7, error handling 1, ternaries 1 (nesting depth added 2). 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.
FoldingRangeFinder.addTrivia (cognitive 18) Sources/SwiftLanguageService/FoldingRange.swift:54— FoldingRangeFinder.addTrivia has cognitive complexity 18 (threshold 15). Drivers by points: if/else 3 (7 pts), match/switch 2 (6 pts), loops 2 (4 pts), boolean chains 1 (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.
InlayHintManager.processEdits (cognitive 18) Sources/SwiftLanguageService/InlayHintManager.swift:94— InlayHintManager.processEdits has cognitive complexity 18 (threshold 15). Drivers by points: if/else 9 (15 pts), boolean chains 2, loops 1 (nesting depth added 6). Of this number, 11 points are the body's own statements and 7 belong to one function item inside it that branches. 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.
BuildServerManager.buildSettingsInferredFromMainFile::mainFileAndSettings (cognitive 17) Sources/BuildServerIntegration/BuildServerManager.swift:1392— BuildServerManager.buildSettingsInferredFromMainFile::mainFileAndSettings has cognitive complexity 17 (threshold 15). Drivers by points: if/else 10 (15 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.
CompilerCommandLineOption.matchesIgnoringFrontend (cognitive 17) Sources/BuildServerIntegration/CompilerCommandLineOption.swift:99— CompilerCommandLineOption.matchesIgnoringFrontend has cognitive complexity 17 (threshold 15). Drivers by points: if/else 11 (14 pts), match/switch 1 (2 pts), loops 1 (nesting depth added 4). 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.
SwiftPMBuildServer.prepare (cognitive 17) Sources/BuildServerIntegration/SwiftPMBuildServer.swift:791— SwiftPMBuildServer.prepare has cognitive complexity 17 (threshold 15). Drivers by points: if/else 12 (14 pts), match/switch 2, ternaries 1 (nesting depth added 2). 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.
ToolchainRegistry.init (cognitive 17) Sources/ToolchainRegistry/ToolchainRegistry.swift:198— ToolchainRegistry.init has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (9 pts), loops 5 (7 pts), boolean chains 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.
build-script-helper.get_swiftpm_options (cognitive 17) Utilities/build-script-helper.py:98— build-script-helper.get_swiftpm_options has cognitive complexity 17 (threshold 15). Drivers by points: if/else 10 (12 pts), boolean chains 2, loops 1 (2 pts), ternaries 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.
BuildServerManager.mainFiles (cognitive 16) Sources/BuildServerIntegration/BuildServerManager.swift:1880— BuildServerManager.mainFiles has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (16 pts) (nesting depth added 9). 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.
DefinitionLocations.swift.definitionLocations (cognitive 16) Sources/SourceKitLSP/DefinitionLocations.swift:32— DefinitionLocations.swift.definitionLocations has cognitive complexity 16 (threshold 15). Drivers by points: if/else 11 (15 pts), boolean chains 1 (nesting depth added 4). 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.
XMLToMarkdown.toMarkdown (cognitive 16) Sources/SwiftLanguageService/CommentXML.swift:77— XMLToMarkdown.toMarkdown has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (13 pts), match/switch 2 (3 pts) (nesting depth added 6). 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.
PriorityBucket.init (cognitive 16) Sources/SwiftSourceKitPlugin/ASTCompletion/ASTCompletionItem.swift:566— PriorityBucket.init has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (8 pts), match/switch 3 (6 pts), boolean chains 2 (nesting depth added 4). 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.
ConvertIfLetToGuard.statementGuaranteesExit (cognitive 16) Sources/SwiftSyntaxCodeActions/ConvertIfLetToGuard.swift:179— ConvertIfLetToGuard.statementGuaranteesExit has cognitive complexity 16 (threshold 15). Drivers by points: if/else 4 (9 pts), match/switch 3 (6 pts), boolean chains 1 (nesting depth added 8). 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.
InlineVariable.nodeToRefactor (cognitive 16) Sources/SwiftSyntaxCodeActions/InlineVariable.swift:27— InlineVariable.nodeToRefactor has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (13 pts), boolean chains 2, loops 1 (nesting depth added 7). 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.
ClassTooLong: CodeCompletionSession Sources/SwiftLanguageService/CodeCompletionSession.swift:84— ClassTooLong — 550 significant lines (blank, comment-only and punctuation-only lines excluded), 22 methods. The bar is 400 significant lines; this is 150 over it, 1.38× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
Change-coupling hub: CursorInfo.swift → OpenInterface.swift, RelatedIdentifiers.swift, SemanticRefactoring.swift, VariableTypeInfo.swift Sources/SwiftLanguageService/CursorInfo.swift— `Sources/SwiftLanguageService/CursorInfo.swift` changes together with 4 other files — `Sources/SwiftLanguageService/OpenInterface.swift`, `Sources/SwiftLanguageService/RelatedIdentifiers.swift`, `Sources/SwiftLanguageService/SemanticRefactoring.swift`, `Sources/SwiftLanguageService/VariableTypeInfo.swift` — none of which declares a dependency on it: one file is the hub of 4 separate couplings, not 4 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 4.
D4 · Code Duplication· Members sharing a duplicated core (4 members, 50+ identical tokens) · ×1
Members sharing a duplicated core (4 members, 50+ identical tokens) Sources/SKUtilities/LineTable.swift:235— Sources/SKUtilities/LineTable.swift:235-271 | Sources/SKUtilities/LineTable.swift:280-318 | Sources/SKUtilities/LineTable.swift:433-461 | Sources/SKUtilities/LineTable.swift:470-502 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
D4 · Code Duplication· Edited copy of a member (29 corresponding lines) · ×1
Edited copy of a member (29 corresponding lines) Sources/SwiftLanguageService/CodeCompletionSession.swift:284— Sources/SwiftLanguageService/CodeCompletionSession.swift:284-321 | Sources/SwiftLanguageService/CodeCompletionSession.swift:323-351 — These two members are one piece of code written twice and then edited apart: 29 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (24 corresponding lines) · ×1
Edited copy of a member (24 corresponding lines) Sources/SourceKitD/SKDRequestArray.swift:51— Sources/SourceKitD/SKDRequestArray.swift:51-74 | Sources/SourceKitD/SKDRequestDictionary.swift:69-92 — These two members are one piece of code written twice and then edited apart: 24 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (41 corresponding lines) · ×1
Edited copy of a member (41 corresponding lines) Sources/SwiftSyntaxCodeActions/PackageManifestEdits.swift:33— Sources/SwiftSyntaxCodeActions/PackageManifestEdits.swift:33-73 | Sources/SwiftSyntaxCodeActions/PackageManifestEdits.swift:77-125 — These two members are one piece of code written twice and then edited apart: 41 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (33 corresponding lines) · ×1
Edited copy of a member (33 corresponding lines) Sources/SwiftLanguageService/SelectionRange.swift:286— Sources/SwiftLanguageService/SelectionRange.swift:286-319 | Sources/SwiftLanguageService/SelectionRange.swift:338-370 — These two members are one piece of code written twice and then edited apart: 33 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (21 corresponding lines) · ×1
Edited copy of a member (21 corresponding lines) Sources/SKUtilities/LineTable.swift:374— Sources/SKUtilities/LineTable.swift:374-399 | Sources/SourceKitLSP/DocumentSnapshot+PositionConversions.swift:27-47 — These two members are one piece of code written twice and then edited apart: 21 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (15 corresponding lines) · ×1
Edited copy of a member (15 corresponding lines) Sources/SwiftLanguageService/SwiftTestingScanner.swift:172— Sources/SwiftLanguageService/SwiftTestingScanner.swift:172-191 | Sources/SwiftLanguageService/SyntacticSwiftXCTestScanner.swift:34-48 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (6 members, 12+ corresponding lines) · ×1
Edited copies of one member (6 members, 12+ corresponding lines) Sources/CompletionScoring/Semantics/Components/Availability.swift:39— Sources/CompletionScoring/Semantics/Components/Availability.swift:39-52 | Sources/CompletionScoring/Semantics/Components/ModuleProximity.swift:40-52 | Sources/CompletionScoring/Semantics/Components/ScopeProximity.swift:49-64 | Sources/CompletionScoring/Semantics/Components/StructuralProximity.swift:34-45 | Sources/CompletionScoring/Semantics/Components/SynchronicityCompatibility.swift:36-48 | Sources/CompletionScoring/Semantics/Components/TypeCompatibility.swift:51-63 — These 6 members are one piece of code written 6 times and then edited apart: every two of them correspond over at least 12 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 6 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 8+ corresponding lines) · ×1
Edited copies of one member (3 members, 8+ corresponding lines) Sources/SKTestSupport/Assertions.swift:16— Sources/SKTestSupport/Assertions.swift:16-23 | Sources/SKTestSupport/Assertions.swift:80-88 | Sources/SKTestSupport/Assertions.swift:144-151 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 8 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 12+ corresponding lines) · ×1
Edited copies of one member (3 members, 12+ corresponding lines) Sources/CompletionScoring/Semantics/SemanticClassification.swift:263— Sources/CompletionScoring/Semantics/SemanticClassification.swift:263-275 | Sources/CompletionScoring/Semantics/SemanticClassification.swift:281-294 | Sources/CompletionScoring/Semantics/SemanticClassification.swift:300-311 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 12 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (6 corresponding lines) · ×1
Edited copy of a member (6 corresponding lines) Sources/CompletionScoring/Utilities/Serialization/Conformances/Array+BinaryCodable.swift:24— Sources/CompletionScoring/Utilities/Serialization/Conformances/Array+BinaryCodable.swift:24-29 | Sources/CompletionScoring/Utilities/Serialization/Conformances/Dictionary+BinaryCodable.swift:29-35 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Duplicated block (25–26 lines × 2) Sources/SKUtilities/LineTable.swift:235— Sources/SKUtilities/LineTable.swift:235-259 | Sources/SKUtilities/LineTable.swift:280-305 — 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 `Sources/SKUtilities/LineTable.swift:235` it does not close everything it opens, 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.
Duplicated block (22 lines × 2) Sources/BuildServerIntegration/BuildServerManager.swift:2059— Sources/BuildServerIntegration/BuildServerManager.swift:2059-2080 | Sources/BuildServerIntegration/BuildServerManager.swift:2134-2155 — 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 `Sources/BuildServerIntegration/BuildServerManager.swift:2059` it begins part-way through the construct above it, 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.
Duplicated block (16 lines × 2) Sources/SourceKitLSP/SourceKitLSPServer.swift:2600— Sources/SourceKitLSP/SourceKitLSPServer.swift:2600-2615 | Sources/SourceKitLSP/SourceKitLSPServer.swift:2677-2692 — 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 (12–13 lines × 4) Sources/SourceKitD/sourcekitd_functions.swift:16— Sources/SourceKitD/sourcekitd_functions.swift:16-28 | Sources/SourceKitD/sourcekitd_functions.swift:98-109 | Sources/SourceKitD/sourcekitd_functions.swift:173-184 | Sources/SourceKitD/sourcekitd_functions.swift:230-241 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Sources/SourceKitD/sourcekitd_functions.swift:16` it does not close everything it opens, 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Sources/SourceKitD/sourcekitd_functions.swift:31` calls `loadOptional` and `Sources/SourceKitD/sourcekitd_functions.swift:187` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (13 lines × 2) Sources/SKTestSupport/PluginPaths.swift:62— Sources/SKTestSupport/PluginPaths.swift:62-74 | Sources/SKTestSupport/PluginPaths.swift:76-88 — 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 `Sources/SKTestSupport/PluginPaths.swift:62` it begins part-way through the construct above it, 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.
Duplicated block (12 lines × 2) Sources/SwiftLanguageService/CodeCompletionSession.swift:404— Sources/SwiftLanguageService/CodeCompletionSession.swift:404-415 | Sources/SwiftLanguageService/SwiftLanguageService.swift:354-365 — 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 `Sources/SwiftLanguageService/CodeCompletionSession.swift:404` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (10 lines × 3) Sources/Diagnose/SourceReducer.swift:442— Sources/Diagnose/SourceReducer.swift:442-451 | Sources/Diagnose/SourceReducer.swift:489-498 | Sources/Diagnose/SourceReducer.swift:502-511 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Sources/Diagnose/SourceReducer.swift:442` 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.
Duplicated block (9–10 lines × 2) SourceKitLSPDevUtils/Sources/ConfigSchemaGen/OptionSchema.swift:248— SourceKitLSPDevUtils/Sources/ConfigSchemaGen/OptionSchema.swift:248-257 | SourceKitLSPDevUtils/Sources/ConfigSchemaGen/OptionSchema.swift:278-286 — 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 `SourceKitLSPDevUtils/Sources/ConfigSchemaGen/OptionSchema.swift:248` 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.
Duplicated block (8–9 lines × 2) Sources/SemanticIndex/TaskScheduler.swift:698— Sources/SemanticIndex/TaskScheduler.swift:698-706 | Sources/SemanticIndex/TaskScheduler.swift:745-752 — 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 `Sources/SemanticIndex/TaskScheduler.swift:698` it does not close everything it opens, 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Sources/SemanticIndex/TaskScheduler.swift:696` calls `dependencies` and `Sources/SemanticIndex/TaskScheduler.swift:743` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (8 lines × 3) Sources/SemanticIndex/TaskScheduler.swift:700— Sources/SemanticIndex/TaskScheduler.swift:700-708 | Sources/SemanticIndex/TaskScheduler.swift:721-729 | Sources/SemanticIndex/TaskScheduler.swift:747-754 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (7 lines × 4) Sources/SKUtilities/LineTable.swift:261— Sources/SKUtilities/LineTable.swift:261-267 | Sources/SKUtilities/LineTable.swift:307-313 | Sources/SKUtilities/LineTable.swift:451-457 | Sources/SKUtilities/LineTable.swift:488-498 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Sources/SKUtilities/LineTable.swift:261` it begins part-way through the construct above it, 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. Note first that the copies are not typed on the same thing: the declarations holding them bind `callerLine` to `UInt = #line` in one and `UInt = #line ) -> (line: Int` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (5 lines × 3) Sources/SwiftLanguageService/InlayHintResolve.swift:76— Sources/SwiftLanguageService/InlayHintResolve.swift:76-80 | Sources/SwiftLanguageService/SignatureHelp.swift:144-148 | Sources/SwiftLanguageService/TypeDefinition.swift:30-34 — 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 all 3 call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `Sources/SwiftLanguageService/InlayHintResolve.swift:76` 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.
Duplicated block (6 lines × 3) Sources/SwiftSyntaxCodeActions/AddExplicitEnumRawValues.swift:150— Sources/SwiftSyntaxCodeActions/AddExplicitEnumRawValues.swift:150-155 | Sources/SwiftSyntaxCodeActions/GenerateEnumCaseAccessors.swift:24-29 | Sources/SwiftSyntaxCodeActions/GenerateEnumCaseAccessors.swift:100-105 — there are 3 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 3 sites; resolving a subset leaves the remainder to drift apart.
Duplicated block (5 lines × 6) Sources/SourceKitD/SKDRequestArray.swift:84— Sources/SourceKitD/SKDRequestArray.swift:84-88 | Sources/SourceKitD/SKDRequestDictionary.swift:96-100 | Sources/SourceKitD/SKDResponse.swift:67-71 | Sources/SourceKitD/SKDResponseArray.swift:107-111 | Sources/SourceKitD/SKDResponseDictionary.swift:87-91 | Sources/SwiftSourceKitPlugin/SKDResponse.swift:76-80 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 6 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 6 times. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. The matched lines also register a scope-exit action (a `defer`-style statement) that runs when the function holding them returns: moved into a called unit it would run when THAT unit returns instead — before the caller uses what it releases — so keep the registration at the call site and extract only the work around it, or have the extracted unit hand the resource back for the caller to register.
No direct assertions: testCandidateBatchCreation Tests/CompletionScoringPerfTests/CandidateBatchPerfTests.swift:18— No conventional assertion call was detected, and 10 of 10 tests in `CompletionScoringPerfTests` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: testCandidateBatchBulkLoading Tests/CompletionScoringPerfTests/CandidateBatchPerfTests.swift:27— No conventional assertion call was detected, and 10 of 10 tests in `CompletionScoringPerfTests` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: testFastConcurrentScoringPerformance Tests/CompletionScoringPerfTests/ScoringPerfTests.swift:65— No conventional assertion call was detected, and 10 of 10 tests in `CompletionScoringPerfTests` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: testFullScoringAndSelectionPerformanceWithoutInfluencers Tests/CompletionScoringPerfTests/ScoringPerfTests.swift:69— No conventional assertion call was detected, and 10 of 10 tests in `CompletionScoringPerfTests` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: testFullScoringAndSelectionPerformanceWithInfluencers Tests/CompletionScoringPerfTests/ScoringPerfTests.swift:73— No conventional assertion call was detected, and 10 of 10 tests in `CompletionScoringPerfTests` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: testFullScoringAndSelectionPerformanceWithInfluencersAndSingleLetterFilter Tests/CompletionScoringPerfTests/ScoringPerfTests.swift:77— No conventional assertion call was detected, and 10 of 10 tests in `CompletionScoringPerfTests` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: testFullScoringAndSelectionPerformanceWithoutInfluencersAndSingleLetterFilter Tests/CompletionScoringPerfTests/ScoringPerfTests.swift:81— No conventional assertion call was detected, and 10 of 10 tests in `CompletionScoringPerfTests` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: testThoroughConcurrentScoringPerformance Tests/CompletionScoringPerfTests/ScoringPerfTests.swift:152— No conventional assertion call was detected, and 10 of 10 tests in `CompletionScoringPerfTests` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: testInfluencingIdentifiersInIsolation Tests/CompletionScoringPerfTests/ScoringPerfTests.swift:195— No conventional assertion call was detected, and 10 of 10 tests in `CompletionScoringPerfTests` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: testTokenizingInIsolation Tests/CompletionScoringPerfTests/ScoringPerfTests.swift:208— No conventional assertion call was detected, and 10 of 10 tests in `CompletionScoringPerfTests` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: testStringLiteralWithCursorInWord Tests/SourceKitLSPTests/SelectionRangeTests.swift:23— No conventional assertion call was detected, and 111 of 138 tests in `SourceKitLSPTests` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: testStringLiteralWithCursorInWord2 Tests/SourceKitLSPTests/SelectionRangeTests.swift:36— No conventional assertion call was detected, and 111 of 138 tests in `SourceKitLSPTests` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: testStringLiteralWithCursorInWord3 Tests/SourceKitLSPTests/SelectionRangeTests.swift:49— No conventional assertion call was detected, and 111 of 138 tests in `SourceKitLSPTests` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: testStringLiteralWithCursorInWhitespace Tests/SourceKitLSPTests/SelectionRangeTests.swift:62— No conventional assertion call was detected, and 111 of 138 tests in `SourceKitLSPTests` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: testStringLiteralWithUnicodeChars Tests/SourceKitLSPTests/SelectionRangeTests.swift:75— No conventional assertion call was detected, and 111 of 138 tests in `SourceKitLSPTests` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: testStringLiteralWithStringInterpolation Tests/SourceKitLSPTests/SelectionRangeTests.swift:84— No conventional assertion call was detected, and 111 of 138 tests in `SourceKitLSPTests` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: testStringConcatenation Tests/SourceKitLSPTests/SelectionRangeTests.swift:99— No conventional assertion call was detected, and 111 of 138 tests in `SourceKitLSPTests` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: testNegativeIntegerLiteral Tests/SourceKitLSPTests/SelectionRangeTests.swift:117— No conventional assertion call was detected, and 111 of 138 tests in `SourceKitLSPTests` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: testFloatLiteral Tests/SourceKitLSPTests/SelectionRangeTests.swift:130— No conventional assertion call was detected, and 111 of 138 tests in `SourceKitLSPTests` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: testBinaryExpression Tests/SourceKitLSPTests/SelectionRangeTests.swift:139— No conventional assertion call was detected, and 111 of 138 tests in `SourceKitLSPTests` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: testComplexConditionalExpression Tests/SourceKitLSPTests/SelectionRangeTests.swift:146— No conventional assertion call was detected, and 111 of 138 tests in `SourceKitLSPTests` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: testSimpleVariableDeclaration Tests/SourceKitLSPTests/SelectionRangeTests.swift:164— No conventional assertion call was detected, and 111 of 138 tests in `SourceKitLSPTests` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: testMultipleBindingsInSingleDeclaration Tests/SourceKitLSPTests/SelectionRangeTests.swift:176— No conventional assertion call was detected, and 111 of 138 tests in `SourceKitLSPTests` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: testVariableWithExplicitType Tests/SourceKitLSPTests/SelectionRangeTests.swift:189— No conventional assertion call was detected, and 111 of 138 tests in `SourceKitLSPTests` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: testLazyVariable Tests/SourceKitLSPTests/SelectionRangeTests.swift:202— No conventional assertion call was detected, and 111 of 138 tests in `SourceKitLSPTests` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
Orphaned file Sources/SwiftSyntaxCodeActions/RemoveRedundantParentheses.swift: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 Sources/SwiftSyntaxCodeActions/ConvertJSONToCodableStruct.swift: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 SourceKitLSPDevUtils/Sources/ConfigSchemaGen/OptionSchema.swift: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 Sources/SwiftSyntaxCodeActions/ConvertStringConcatenationToStringInterpolation.swift: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 Sources/DocumentationLanguageService/DocCServer.swift: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 Sources/SwiftSyntaxCodeActions/ConvertIfLetToGuard.swift: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 Sources/DocumentationLanguageService/DocCCatalogIndexManager.swift: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 Sources/SwiftSyntaxCodeActions/OpaqueParameterToGeneric.swift: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 SourceKitLSPDevUtils/Sources/ConfigSchemaGen/JSONSchema.swift: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 Sources/SwiftSyntaxCodeActions/PackageManifestEdits.swift: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 Sources/SwiftLanguageService/SignatureHelp.swift: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 Sources/SwiftLanguageService/RewriteSourceKitPlaceholders.swift: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 SourceKitLSPDevUtils/Sources/ConfigSchemaGen/ConfigSchemaGen.swift: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 Sources/DocumentationLanguageService/DocCDocumentationManager.swift: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 Sources/SwiftLanguageService/SwiftCodeLensScanner.swift: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 Sources/SwiftLanguageService/CommentXML.swift: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 Sources/SKUtilities/LRUCache.swift: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 Sources/SwiftSyntaxCodeActions/ConvertComputedPropertyToZeroParameterFunction.swift: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 SourceKitLSPDevUtils/Sources/ConfigSchemaGen/TypeDeclResolver.swift: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 Sources/SwiftSyntaxCodeActions/ConvertZeroParameterFunctionToComputedProperty.swift: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 Sources/SwiftLanguageService/SwiftPlaygroundsScanner.swift: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 Sources/SourceKitLSP/SourceKitLSPCommandMetadata.swift: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 Sources/SwiftLanguageService/InlayHintResolve.swift: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 Sources/SwiftSyntaxCodeActions/IndentationRemover.swift: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 Sources/SwiftSyntaxCodeActions/DeclModifierRemover.swift: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.
Silent fallback default in catch Sources/SwiftLanguageService/SwiftLanguageService.swift:1515— `localReferences` turns every thrown error into `[]` — a data error becomes a silent behavior change with no trail. Log the error or let it propagate (`throws`). 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 at the `catch`, `guard` or `??`, or in the doc comment, and the row stops firing.
Silent fallback default in catch Sources/SwiftSyntaxCodeActions/PackageManifestEdits.swift:70— `addTargetActions` turns every thrown error into `[]` — a data error becomes a silent behavior change with no trail. Log the error or let it propagate (`throws`). 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 at the `catch`, `guard` or `??`, or in the doc comment, and the row stops firing.
Silent fallback default in catch Sources/SwiftSyntaxCodeActions/PackageManifestEdits.swift:122— `addTestTargetActions` turns every thrown error into `[]` — a data error becomes a silent behavior change with no trail. Log the error or let it propagate (`throws`). 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 at the `catch`, `guard` or `??`, or in the doc comment, and the row stops firing.
Silent fallback default in catch Sources/SwiftSyntaxCodeActions/PackageManifestEdits.swift:176— `addProductActions` turns every thrown error into `[]` — a data error becomes a silent behavior change with no trail. Log the error or let it propagate (`throws`). 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 at the `catch`, `guard` or `??`, or in the doc comment, and the row stops firing.
Silent fallback default in catch Sources/SwiftSyntaxCodeActions/SyntaxRefactoringCodeActionProvider.swift:83— `codeActions` turns every thrown error into `[]` — a data error becomes a silent behavior change with no trail. Log the error or let it propagate (`throws`). 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 at the `catch`, `guard` or `??`, or in the doc comment, and the row stops firing.
Off-boarding risk: anonymized user #1 — If anonymized user #1 becomes unavailable, 4 significant file(s) lose their only recent owner: Sources/CompletionScoring/Utilities/SwiftExtensions.swift, Sources/Diagnose/RunSourcekitdRequestCommand.swift, Sources/BuildServerIntegration/BuildServerMessageDependencyTracker.swift, Sources/BuildServerIntegration/BuiltInBuildServer.swift. Pair on, review, or document these before any departure.
Off-boarding risk: anonymized user #2 — If anonymized user #2 becomes unavailable, 3 significant file(s) lose their only recent owner: Sources/SourceKitLSP/WorkspaceSymbols.swift, Sources/SourceKitLSP/EntryPointManager.swift, Sources/SourceKitLSP/LSP+CopiedFileMap.swift. Pair on, review, or document these before any departure.
Off-boarding risk: anonymized user #3 — If anonymized user #3 becomes unavailable, 3 significant file(s) lose their only recent owner: Sources/SwiftSyntaxCodeActions/ConvertStringConcatenationToStringInterpolation.swift, Sources/SwiftLanguageService/InlayHintResolve.swift, Sources/SwiftLanguageService/TypeDefinition.swift. Pair on, review, or document these before any departure.
Off-boarding risk: anonymized user #4 — If anonymized user #4 becomes unavailable, 3 significant file(s) lose their only recent owner: Sources/SwiftSyntaxCodeActions/InlineVariable.swift, Sources/SwiftSyntaxCodeActions/ToggleTestDisabled.swift, Sources/SwiftSyntaxCodeActions/FormatRawStringLiteral.swift. Pair on, review, or document these before any departure.
Duplicated predicate Sources/SwiftLanguageService/SwiftLanguageService.swift:476— `$0.is(CodeBlockSyntax.self) || $0.is(MemberBlockSyntax.self)` appears character-identically in 3 files — Sources/SwiftLanguageService/SwiftLanguageService.swift, Sources/SwiftSyntaxCodeActions/InvertIfCondition.swift, Sources/SwiftSyntaxCodeActions/SyntaxRefactoringCodeActionProvider.swift. 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 Sources/SwiftSyntaxCodeActions/ConvertCommentToDocComment.swift:52— `$0.kind == .codeBlockItem || $0.kind == .memberBlockItem` appears character-identically in 2 files — Sources/SwiftSyntaxCodeActions/ConvertCommentToDocComment.swift, Sources/SwiftSyntaxCodeActions/ConvertStringConcatenationToStringInterpolation.swift. 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 Sources/SourceKitLSP/SourceKitLSPServer.swift:2141— `occurrence.roles.contains(.definition) || occurrence.roles.contains(.declaration)` appears character-identically in 2 files — Sources/SourceKitLSP/SourceKitLSPServer.swift, Sources/SwiftLanguageService/DiagnosticReportManager.swift. 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.
D10 · Test Quality· Test project verifies nothing · ×1
Test project verifies nothing: CompletionScoringPerfTests Tests/CompletionScoringPerfTests/CandidateBatchPerfTests.swift:18— No conventional assertion call was detected in 10 of 10 tests in `CompletionScoringPerfTests` — the project as a whole, not one method. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a suite that genuinely checks nothing. If it is the latter, this project passes unconditionally and cannot fail.
D16 · Bus Factor· Further sole-owners (lower concentration) · ×1
Further sole-owners (lower concentration) — 4 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 (19 single-owned of 222 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; 222 of the 348 production source files in this repository met that bar). They are anonymized user #5 (2 file(s)), anonymized user #6 (2 file(s)), anonymized user #7 (1 file(s)), anonymized user #8 (1 file(s)) — spread or document their files in the same way, at lower priority than the named off-boarding risks above. The files folded here: Sources/SwiftSyntaxCodeActions/ApplyDeMorganLaw.swift, Sources/SwiftSyntaxCodeActions/ConvertJSONToCodableStruct.swift, Sources/SwiftSyntaxCodeActions/GenerateEnumCaseAccessors.swift, Sources/SwiftSyntaxCodeActions/AddExplicitEnumRawValues.swift, Sources/SwiftLanguageService/CodeCompletionContext.swift, Sources/SwiftSyntaxCodeActions/InvertIfCondition.swift.
No ADRs found Package.swift:7— No ADRs found. No recognised ADR directory (`docs/adr/`, `docs/decisions/`, `adr/`, `docs/rfcs/`, an `ADR0001/` folder, or their siblings) exists anywhere in this tree. What was searched, so you can tell an empty log from a search that missed one: every directory under the tree (build output, dependencies and VCS metadata excepted), for a document that is either any non-index page inside a recognised ADR directory, whatever its name and however deeply nested (`docs/adr/use-postgres.md`, `docs/adr/2024/0001-x.md`); or a file anywhere whose name is ADR-shaped (`0001-use-postgres.md`, `adr-012-caching.md`); or, when neither turned anything up, a document carrying the decision-record signature (an "Architecture Decision Record" heading, or Status / Context / Decision / Consequences as section headings). A decision log that clears none of these — unnumbered files outside any recognised directory, without those headings — is not seen by this check and this row is then wrong. If that is your case, say so rather than renaming anything; otherwise, consider recording architectural decisions in `docs/adr/`. ADRs are expected here because `Package.swift` makes this repository a deployable product (line 7).
D21 · Naming Consistency· `asLspSymbolKind` spells `Lsp` where 52 names in the project spell it `LSP` · ×1
`asLspSymbolKind` spells `Lsp` where 52 names in the project spell it `LSP` Sources/SourceKitLSP/SourceKitLSPServer.swift:2869— 52 of 53 names in project BuildServerIntegration spell the token `LSP` (52 of 53; unit: names in project BuildServerIntegration containing `LSP`). Peers: BuildServerSpec.createBuiltInBuildServerAdapter(messagesToSourceKitLSPHandler) (Sources/BuildServerIntegration/BuildServerManager.swift:206); BuildServerSpec.createBuildServerAdapter(messagesToSourceKitLSPHandler) (Sources/BuildServerIntegration/BuildServerManager.swift:241); BuiltInBuildServerAdapter.connectionToSourceKitLSP (Sources/BuildServerIntegration/BuiltInBuildServerAdapter.swift:65); BuiltInBuildServerAdapter.init(connectionToSourceKitLSP) (Sources/BuildServerIntegration/BuiltInBuildServerAdapter.swift:71); ExternalBuildServerAdapter.messagesToSourceKitLSPHandler (Sources/BuildServerIntegration/ExternalBuildServerAdapter.swift:228). Rename to `asLSPSymbolKind`. [rule N6]
D26 · Project Cohesion· Projects may be oversized for their cohesion · ×1
Projects may be oversized for their cohesion — 1 of 2 project(s) overshoot their size bounds, lowering Project Cohesion to 0.0/10. The most over is `(repository root)` (57574 LoC, 612 module-visible types across 33 directories). Review these for cohesion — draw the boundary inside the module first (group each responsibility into its own package or directory and keep the cross-boundary members non-public), since splitting a published package moves types between packages and breaks consumers.
D34 · Knowledge Freshness· Further orphaned files (smaller) · ×1
Further orphaned files (smaller) — 30 smaller file(s) also have no living knowledge — folded into the freshness score and metrics rather than raised one row each — most significant first: Sources/SwiftSyntaxCodeActions/RemoveRedundantParentheses.swift, Sources/SwiftSyntaxCodeActions/ConvertJSONToCodableStruct.swift, SourceKitLSPDevUtils/Sources/ConfigSchemaGen/OptionSchema.swift, Sources/SwiftSyntaxCodeActions/ConvertStringConcatenationToStringInterpolation.swift, Sources/DocumentationLanguageService/DocCServer.swift, Sources/SwiftSyntaxCodeActions/ConvertIfLetToGuard.swift, Sources/DocumentationLanguageService/DocCCatalogIndexManager.swift, Sources/SwiftSyntaxCodeActions/OpaqueParameterToGeneric.swift (and 22 more) (32 orphaned of 222 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; 222 of the 348 production source files in this repository met that bar). 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.
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.
Logging is not universal — Only 1/3 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `.`, `SourceKitLSPDevUtils`.
No SAST — No static application security testing detected. For this repository's stack, add CodeQL's Swift pack (Swift/Xcode) (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.
Skipped (documented): testToolsets Tests/BuildServerIntegrationTests/SwiftPMBuildServerTests.swift:1267— Skipped with a documented reason — a deferral, not lazy debt: conditionally enabled — runs only when its .enabled(if:) condition holds
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.
none (dependency manifest found, not scanned for vulnerabilities here)
—
none (dependency manifest found, not scanned for vulnerabilities here): not applicable — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Swift Package.swift/Package.resolved — not scanned yet).
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 219 file(s) — `SourceKitLSPDevUtils/Sources/ConfigSchemaGen/ConfigSchemaGen.swift`, `Sources/BuildServerIntegration/BuildServerHooks.swift`, `Sources/BuildServerIntegration/BuildServerManager.swift`, `Sources/BuildServerIntegration/BuildServerManagerDelegate.swift`, `Sources/BuildServerIntegration/BuildServerMessageDependencyTracker.swift`, … (+214 more) — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real.
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.
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.
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.
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.
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.
none (dependency manifest found, not scanned for vulnerabilities here)
—
none (dependency manifest found, not scanned for vulnerabilities here): not applicable — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Swift Package.swift/Package.resolved — not scanned yet).
0
—
Run 01a1dc22-8496-7454-ad64-23b89bc3be24 · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.
Issues: 3 · Warnings: 344 · Recommendations: 275 · Info: 1 — Appendix A · all findings · full markdown report.
Generated by the Canine Code Analyzer: deterministic code-health analysis. 14-11-2026 @ 22:16 UTC.
Downloadable artifacts
Machine-readable and reproducible from this commit + frozen rubric — drop them straight into a contract appendix, a CRA dossier, or a downstream SCA / VEX tool.