Public report of swiftlang/sourcekit-lsp, published 28 October 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 report Measured under the Code Assurance Index, an open standard for code quality, using its published scoring rules (rubric version 2026.10.5). 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, 28 October 2026, 21:16 UTC · Survey ID cd_7fad0e076d294c74b0a1b9c29c515faf

swiftlang/sourcekit-lsp

Measured 28 October 2026, 21:13 UTC, at code version cc39266

No regression since the last survey Test reliability: not measured

A regression is a drop of 0.5 points or more in the score, or of 2.5 or more out of 10 in a dimension, since the last survey.

Test reliability is not measured: The suite could not be re-run, but the repository declares tests of its own unreliable.

CAI score 53out of 100 Adequate
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,014 lines of product code in 58 projects, tests not counted · Estimated rebuild effort: about 0.7 person-years · Weakest lens: Production Readiness, 31

Findings by how serious they are

3 critical 298 serious 276 minor

24 dimensions are left out of the score. For each one, Watchdog either couldn't measure it in this code, or found no evidence of the safeguard it looks 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

Watchdog
Producer
Canine Development
Analyzer
Watchdog engine 1.0.0
Measured
28 October 2026, 21:13 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 Watchdog. It is open to any tool that implements it, and today Watchdog is the only one that does.

The score is deterministic, which means the same code always gets the same score. Watchdog works 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 ▸

52of 52 dimensions measured by tools.
553of 577 findings point to an exact file and line, so you can open each one in the code. The other 24 concern the repository as a whole, such as missing documentation.
52dimensions across 6 lenses, read from 58,014 lines of product code in 58 projects.
Chapters

Executive summary

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 31, 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 69.

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,014 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 for The lenses don't count equally. The weakest lens counts most, the next weakest a little less, and so on, so a weak area pulls the score down instead of being averaged away. In the bar below, each part's width shows how much that lens counts and its colour shows its rating. Improving the widest part moves the score most, and as that lens improves, it counts for less, because another lens becomes the weakest.
Production Readiness 31 · counts for 46%Maturity 62 · counts for 25%Code Health 76 · counts for 14%Performance 79 · counts for 8%Architecture 88 · counts for 4%Security and Compliance 100 · counts for 2%

If Production Readiness rose from 31 to 70, the lowest score rated Strong, the score would rise from 53 to about 69.

Code composition: what the lines of code are
Product code 52%Tests 48%
New since the last survey: 7 findings

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

  • Cognitive Complexity · SourceKitLSPServer.subtypes (cognitive 18) Sources/SourceKitLSP/SourceKitLSPServer.swift
  • Code Duplication · Duplicated block (16 lines × 2) Sources/SourceKitLSP/SourceKitLSPServer.swift
  • Coupling · Off the main sequence: DocumentationLanguageService
  • Churn × Complexity Hotspots · Hotspot: Sources/SourceKitLSP/MessageHandlingDependencyTracker.swift Sources/SourceKitLSP/MessageHandlingDependencyTracker.swift
  • Knowledge Freshness · Orphaned knowledge Sources/SwiftSyntaxCodeActions/ApplyDeMorganLaw.swift
  • Change Coupling · Change-coupling hub: SwiftLanguageService.swift → ClangLanguageService.swift, DocumentationLanguageService.swift, WorkDoneProgressManager.swift Sources/SwiftLanguageService/SwiftLanguageService.swift
  • Exception handling · Swallowed exception (caught, then discarded) Sources/TSCExtensions/Process+Run.swift

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

Fixed since the last survey: 8 findings

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

  • Cognitive Complexity · SourceKitLSPServer.containerUSRs (cognitive 18) Sources/SourceKitLSP/WorkspaceSymbols.swift
  • Code Duplication · Duplicated block (15–16 lines × 2) Sources/SourceKitLSP/SourceKitLSPServer.swift
  • Code Duplication · Duplicated block (11 lines × 2) Sources/SourceKitLSP/SourceKitLSPServer.swift
  • Coupling · Unstable project DocumentationLanguageService
  • Coupling · Unstable project SemanticIndex (SwiftPM)
  • Churn × Complexity Hotspots · Hotspot: Sources/BuildServerIntegration/ExternalBuildServerAdapter.swift Sources/BuildServerIntegration/ExternalBuildServerAdapter.swift
  • Change Coupling · Change coupling: ClangLanguageService.swift ↔ SwiftLanguageService.swift Sources/ClangLanguageService/ClangLanguageService.swift
  • Change Coupling · Change coupling: WorkDoneProgressManager.swift ↔ SwiftLanguageService.swift Sources/LanguageServerProtocolExtensions/WorkDoneProgressManager.swift
Rebuild cost: about €110,000 · Estimate
Cost to rebuild€36,000 to €180,000, for 594 to 1,886 hours of work, about 0.7 person-years for 1 to 2 engineers
Difficulty of the problemStandard, 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.
SizeMedium: 58,014 lines of product code
What it is notNot a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one.

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

Top priorities

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

1
Resolve the 1 No ADRs found finding(s) in ADR Quality.
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.
Raises the score by about 5 points · Medium effort · Architecture documentation

Diagnosis: what the measurements show together

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

Where the investment is most exposed · Value at risk
This code would cost about €110,000 to build again, about 0.7 person-years of work. Its weakest lens is Production Readiness, at 31 (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

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.

arch BuildServerIntegration (CMake) BuildServerIntegration (CMake) LanguageServerProtocolExtensions (CMake) LanguageServerProtocolExtensions (CMake) BuildServerIntegration (CMake)->LanguageServerProtocolExtensions (CMake) SKOptions (CMake) SKOptions (CMake) BuildServerIntegration (CMake)->SKOptions (CMake) SKUtilities (CMake) SKUtilities (CMake) BuildServerIntegration (CMake)->SKUtilities (CMake) SourceKitD (CMake) SourceKitD (CMake) BuildServerIntegration (CMake)->SourceKitD (CMake) SwiftExtensions (CMake) SwiftExtensions (CMake) BuildServerIntegration (CMake)->SwiftExtensions (CMake) TSCExtensions (CMake) TSCExtensions (CMake) BuildServerIntegration (CMake)->TSCExtensions (CMake) ToolchainRegistry (CMake) ToolchainRegistry (CMake) BuildServerIntegration (CMake)->ToolchainRegistry (CMake) ClangLanguageService (CMake) ClangLanguageService (CMake) ClangLanguageService (CMake)->BuildServerIntegration (CMake) ClangLanguageService (CMake)->LanguageServerProtocolExtensions (CMake) ClangLanguageService (CMake)->SKOptions (CMake) SourceKitLSP (CMake) SourceKitLSP (CMake) ClangLanguageService (CMake)->SourceKitLSP (CMake) ClangLanguageService (CMake)->SwiftExtensions (CMake) ClangLanguageService (CMake)->TSCExtensions (CMake) ClangLanguageService (CMake)->ToolchainRegistry (CMake) Csourcekitd (CMake) Csourcekitd (CMake) Diagnose (CMake) Diagnose (CMake) Diagnose (CMake)->BuildServerIntegration (CMake) InProcessClient (CMake) InProcessClient (CMake) Diagnose (CMake)->InProcessClient (CMake) Diagnose (CMake)->SKOptions (CMake) Diagnose (CMake)->SKUtilities (CMake) Diagnose (CMake)->SourceKitD (CMake) Diagnose (CMake)->SwiftExtensions (CMake) Diagnose (CMake)->TSCExtensions (CMake) Diagnose (CMake)->ToolchainRegistry (CMake) InProcessClient (CMake)->BuildServerIntegration (CMake) InProcessClient (CMake)->ClangLanguageService (CMake) InProcessClient (CMake)->SKOptions (CMake) InProcessClient (CMake)->SourceKitLSP (CMake) SwiftLanguageService (CMake) SwiftLanguageService (CMake) InProcessClient (CMake)->SwiftLanguageService (CMake) InProcessClient (CMake)->TSCExtensions (CMake) InProcessClient (CMake)->ToolchainRegistry (CMake) InProcessClient (SwiftPM) InProcessClient (SwiftPM) LanguageServerProtocolExtensions (CMake)->SourceKitD (CMake) LanguageServerProtocolExtensions (CMake)->SwiftExtensions (CMake) SKOptions (CMake)->LanguageServerProtocolExtensions (CMake) SKUtilities (CMake)->SwiftExtensions (CMake) SemanticIndex (CMake) SemanticIndex (CMake) SemanticIndex (CMake)->BuildServerIntegration (CMake) SemanticIndex (CMake)->SwiftExtensions (CMake) SemanticIndex (CMake)->TSCExtensions (CMake) SemanticIndex (CMake)->ToolchainRegistry (CMake) SourceKitD (CMake)->Csourcekitd (CMake) SourceKitD (CMake)->SwiftExtensions (CMake) SourceKitLSP (CMake)->BuildServerIntegration (CMake) SourceKitLSP (CMake)->LanguageServerProtocolExtensions (CMake) SourceKitLSP (CMake)->SKOptions (CMake) SourceKitLSP (CMake)->SKUtilities (CMake) SourceKitLSP (CMake)->SemanticIndex (CMake) SourceKitLSP (CMake)->SourceKitD (CMake) SourceKitLSP (CMake)->SwiftExtensions (CMake) SourceKitLSP (CMake)->TSCExtensions (CMake) SourceKitLSP (CMake)->ToolchainRegistry (CMake) SwiftExtensions (SwiftPM) SwiftExtensions (SwiftPM) SwiftLanguageService (CMake)->BuildServerIntegration (CMake) SwiftLanguageService (CMake)->Csourcekitd (CMake) SwiftLanguageService (CMake)->LanguageServerProtocolExtensions (CMake) SwiftLanguageService (CMake)->SKOptions (CMake) SwiftLanguageService (CMake)->SKUtilities (CMake) SwiftLanguageService (CMake)->SemanticIndex (CMake) SwiftLanguageService (CMake)->SourceKitD (CMake) SwiftLanguageService (CMake)->SourceKitLSP (CMake) SwiftLanguageService (CMake)->SwiftExtensions (CMake) SwiftLanguageService (CMake)->TSCExtensions (CMake) SwiftLanguageService (CMake)->ToolchainRegistry (CMake) SwiftSourceKitPlugin (CMake) SwiftSourceKitPlugin (CMake) SwiftSourceKitPlugin (CMake)->Csourcekitd (CMake) TSCExtensions (CMake)->SwiftExtensions (CMake) ToolchainRegistry (CMake)->LanguageServerProtocolExtensions (CMake) ToolchainRegistry (CMake)->SKUtilities (CMake) ToolchainRegistry (CMake)->SwiftExtensions (CMake) ToolchainRegistry (CMake)->TSCExtensions (CMake) sourcekit-lsp (CMake) sourcekit-lsp (CMake) sourcekit-lsp (CMake)->BuildServerIntegration (CMake) sourcekit-lsp (CMake)->Diagnose (CMake) sourcekit-lsp (CMake)->InProcessClient (CMake) sourcekit-lsp (CMake)->LanguageServerProtocolExtensions (CMake) sourcekit-lsp (CMake)->SKOptions (CMake) sourcekit-lsp (CMake)->SemanticIndex (CMake) sourcekit-lsp (CMake)->SourceKitLSP (CMake) sourcekit-lsp (CMake)->ToolchainRegistry (CMake) sourcekit-lsp (SwiftPM) sourcekit-lsp (SwiftPM) sourcekit-lsp (SwiftPM)->InProcessClient (SwiftPM) __more__ +38 more projects

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 155 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.
uses →1 SourceKitLSPDevUtils~SourceKitLSPDevUtils2 Sources.SKTestSupport.INPUTS.AbstractBuildServer3 SwiftSyntaxExtensions4 Utilities5 SwiftExtensions6 SwiftSourceKitPluginCommon7 SwiftSyntaxCodeActions8 TSCExtensions9 SourceKitD10 ToolchainRegistry11 SwiftLanguageService12 SourceKitLSPDevUtils~ConfigSchemaGen13 SKTestSupport14 DocumentationLanguageService15 SemanticIndex16 SKUtilities17 SwiftSourceKitPlugin18 SKOptions19 Diagnose20 SourceKitLSP21 LanguageServerProtocolExtensions22 ClangLanguageService23 CompletionScoring24 BuildServerIntegration25 InProcessClient26 SwiftSourceKitClientPlugin27 sourcekit-lsp
1 SourceKitLSPDevUtils~SourceKitLSPDevUtils
2 Sources.SKTestSupport.INPUTS.AbstractBuildServer
3 SwiftSyntaxExtensions
4 Utilities
5 SwiftExtensions11
6 SwiftSourceKitPluginCommon2514
7 SwiftSyntaxCodeActions481531331
8 TSCExtensions111
9 SourceKitD1281117
10 ToolchainRegistry23210
11 SwiftLanguageService11447263443387112250
12 SourceKitLSPDevUtils~ConfigSchemaGen313114
13 SKTestSupport1442117676849
14 DocumentationLanguageService211116118126
15 SemanticIndex42131712131329
16 SKUtilities1112141
17 SwiftSourceKitPlugin222931122825
18 SKOptions3112
19 Diagnose34521513332
20 SourceKitLSP5512741453254331441
21 LanguageServerProtocolExtensions123
22 ClangLanguageService1321611515
23 CompletionScoring56181132
24 BuildServerIntegration227322581157
25 InProcessClient1121
26 SwiftSourceKitClientPlugin31
27 sourcekit-lsp33
Uses a module listed above itPart of a loopThe module itself
1 SourceKitLSPDevUtils~SourceKitLSPDevUtils2 Sources.SKTestSupport.INPUTS.AbstractBuildServer3 SwiftSyntaxExtensions4 Utilities5 SwiftExtensions6 SwiftSourceKitPluginCommon7 SwiftSyntaxCodeActions8 TSCExtensions9 SourceKitD10 ToolchainRegistry11 SwiftLanguageService12 SourceKitLSPDevUtils~ConfigSchemaGen13 SKTestSupport14 DocumentationLanguageService15 SemanticIndex16 SKUtilities17 SwiftSourceKitPlugin18 SKOptions19 Diagnose20 SourceKitLSP21 LanguageServerProtocolExtensions22 ClangLanguageService23 CompletionScoring24 BuildServerIntegration25 InProcessClient26 SwiftSourceKitClientPlugin27 sourcekit-lspSourceKitLSPDevUtils~SourceKitLSPDevUtils1Sources.SKTestSupport.INPUTS.AbstractBuildServer2SwiftSyntaxExtensions3Utilities4SwiftExtensions5SwiftSourceKitPluginCommon6SwiftSyntaxCodeActions7TSCExtensions8SourceKitD9ToolchainRegistry10SwiftLanguageService11SourceKitLSPDevUtils~ConfigSchemaGen12SKTestSupport13DocumentationLanguageService14SemanticIndex15SKUtilities16SwiftSourceKitPlugin17SKOptions18Diagnose19SourceKitLSP20LanguageServerProtocolExtensions21ClangLanguageService22CompletionScoring23BuildServerIntegration24InProcessClient25SwiftSourceKitClientPlugin26sourcekit-lsp27112514481531331111128111723210114472634433871122503131141442117676849211116118126421317121313291112141222931122825311234521513332551274145325433144112313216115155618113222732258115711213133

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

At a glance — Architecture · 88% · Adequate · gated by D26 ·

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

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

At a glance — Security · 100% · Exemplary ·

At a glance — Performance · 79% · Strong ·

Security & Compliance — OWASP Top-10 mapping

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 categoryFindingsSeverity
A02:2025 — Security Misconfiguration3Medium

Roadmap

Establish a CI workflow to build and test on every push, ensuring immediate feedback on code changes. Resolve the lack of architectural decision records by documenting key design choices in a dedicated folder to preserve institutional knowledge. Address the 220 missing test assertions, prioritizing SelectionRangeTests.swift, to improve code reliability. Finally, extend structured logging across all runnable modules to ensure full observability and diagnosability in production.

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

Do thisHelpsEffortDimension
Resolve the 1 No ADRs found finding(s) in ADR Quality.+5.3 ptsLowADR Quality
Add a CI workflow that builds and runs the test suite on every push/PR.+8.1 ptsMediumCI/CD gates
Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.+5.0 ptsMediumArchitecture documentation
Resolve the 2 Orphaned knowledge finding(s) in Knowledge Freshness — start with SelectionRange.swift, ApplyDeMorganLaw.swift.+1.7 ptsLowKnowledge Freshness
Extend structured logging to the remaining runnable modules so everything you run is diagnosable in production.+2.8 ptsMediumObservability
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.+2.8 ptsMediumDeployment & Rollback
Resolve the 220 No direct assertions finding(s) in Test Quality — start with SelectionRangeTests.swift (110), ConvertStoredPropertyToComputedTests.swift (23), ConvertComputedPropertyToZeroParameterFunctionTests.swift (20).+3.6 ptsHighTest Quality
Resolve the 4 Off-boarding risk finding(s) in Bus Factor.+0.6 ptsLowBus Factor

File quality

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

FileScoreBandWorst signal
Sources/SwiftLanguageService/SwiftLanguageService.swift5.5MixedGod Classes: TooManyMethods: SwiftLanguageService
Sources/SemanticIndex/TaskScheduler.swift5.6MixedCyclomatic Complexity: TaskScheduler.poke (cyclomatic 16)
Sources/SwiftSourceKitPlugin/CompletionProvider.swift6.0MixedExplicit Debt: FixmeComment
Sources/SwiftSourceKitPlugin/ASTCompletion/ASTCompletionItem.swift6.0MixedExplicit Debt: FixmeComment
Sources/SemanticIndex/SemanticIndexManager.swift6.0MixedExplicit Debt: TodoComment
Sources/BuildServerIntegration/BuildServerManager.swift6.0MixedExplicit Debt: TodoComment
Sources/BuildServerIntegration/SwiftPMBuildServer.swift6.0MixedExplicit Debt: TodoComment
Sources/SourceKitLSP/SourceKitLSPServer.swift6.0MixedExplicit Debt: TodoComment
Sources/ClangLanguageService/ClangLanguageService.swift6.0MixedExplicit Debt: TodoComment
Sources/Diagnose/CommandLineArgumentsReducer.swift6.3MixedCode Duplication: Duplicated block (10 lines × 2)
Sources/SwiftSourceKitPlugin/CodeCompletion/Connection.swift6.7MixedExplicit Debt: FixmeComment
Sources/SwiftLanguageService/CursorInfo.swift6.7MixedExplicit Debt: TodoComment
Sources/CompletionScoring/Semantics/Components/PopularityTable.swift6.9MixedExplicit Debt: TodoComment
Sources/SourceKitD/SourceKitD.swift7.0MixedCognitive Complexity: SourceKitD.send (cognitive 26)
Sources/ToolchainRegistry/ToolchainRegistry.swift7.0MixedCognitive Complexity: ToolchainRegistry.init (cognitive 17)
Tests/CompletionScoringTests/PatternTests.swift7.0MixedTest Quality: No assertions: testScoring
Sources/CompletionScoring/Text/Pattern.swift7.0MixedCyclomatic Complexity: Pattern.singleScore (cyclomatic 41)
Sources/SwiftLanguageService/CodeCompletionSession.swift7.1MixedCyclomatic Complexity: CodeCompletionSession.completionsFromSKDResponse (cyclomatic 31)
Tests/CompletionScoringTests/BinaryCodingTests.swift7.1MixedTest Quality: No assertions: testIntegers
Tests/CompletionScoringTests/CandidateBatchTests.swift7.1MixedTest Quality: No assertions: testPrioritizeUserSymbolsOverSDK

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 — 298

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

Watchdog is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. 52 of 52 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); none rely on LLM judgement. Overall confidence is 0.8 — the weighted average across measured dimensions; it falls as more of the score leans on LLM-assisted judgement and rises when it's fully tool-backed.

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

What we checked — 52 dimensions across the health lenses
D1D2D3D4D5D6D9D10D13D14D15D16D17D20D26D28D29D31D34D35AX10AX3AX4AX8AX9M1M2M3M4P1P2P3P4PF2PF3X1X12X13X14X15X17X19X21X22X23X24X25X26X27X28X3X30

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
  1. 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, 553 of 577 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.)
  2. Is there a tool behind the number? Every score below names the method that produced it — Roslyn, git, a scanner, or (for a handful of documentation/naming dimensions) an LLM labelled sampled · advisory — not a narrative.
  3. 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.

MethodBacksVersionEvaluator
Roslyn static analysisComplexity, cohesion, coupling, dead code, API surface, layering5.3.0✓ deterministic
Native secret scannerHardcoded secrets / credentials1.0.0✓ deterministic
Watchdog duplication detector (in-process)Code duplication1.0.0✓ deterministic
Coverage (coverlet / dotnet-coverage)Line & branch coverage10.0.400✓ deterministic
NuGet / dotnetOutdated, vulnerable & deprecated dependencies10.0.400✓ deterministic
git / LibGit2SharpChurn hotspots, knowledge concentration, history2.43.0 · 0.31.0✓ deterministic
gitleaks · semgrep · trivy · checkovSecrets in history, SAST, CVEs, IaC & container, PII / GDPR1.86.0 · 0.69.3 · 3.2.533✓ deterministic
LLM (sampled · advisory)Documentation quality, ADR conformance, naming — sampled over a bounded sample; advisory, never a deterministic measurement—◐ LLM · sampled · advisory

Every finding is locatable in findings.md. Run 01a1845c-5f11-7c86-b057-4d6e93758a55.

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

Run transparency — what happened this run

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

  • D8 Code Coverage — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: the 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. In the meantime, commit (or publish into the working tree) the lcov/Cobertura report your CI produces and the real number is read on the next scan. You can widen what we reach: optional: commit the lcov/Cobertura report your CI produces, and the real number is read on the next scan.
  • D11 Test Reliability — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 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 — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Not scored — 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 — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 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 — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D21's deterministic naming rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. Until then its declarations carry no naming verdict this run — this says nothing about whether its names are consistent.
  • D22 Internal API Consistency — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22 identifies the intentionally-exposed surface from `IsPackable` and `.Contracts` project names, MSBuild conventions read off the loaded project set. This target exposed no such projects, so the probe never ran; this says nothing about whether the repository has a public API. This repository commits no C#/VB source at all, so there was never an MSBuild project set to read these conventions off. That is OUR side and it is 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 — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
  • D27 Navigability — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Navigability is taken over call sites whose callee resolved. For C# that population includes calls into referenced assemblies; for this language only calls declared inside the repository count, so the abstention threshold reads the repository's use of its standard library as a resolution failure. That is a limit of this analyzer, not a build problem in this repository.
  • D32 Data Compliance (PII/GDPR) — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `SourceKitLSPDevUtils/Sources/ConfigSchemaGen/ConfigSchemaGen.swift`, `Sources/BuildServerIntegration/BuildServerHooks.swift`, `Sources/BuildServerIntegration/BuildServerManager.swift`, `Sources/BuildServerIntegration/BuildServerManagerDelegate.swift`, `Sources/BuildServerIntegration/BuildServerMessageDependencyTracker.swift`, … (+213 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 — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This 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 — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads Microsoft.Extensions.DependencyInjection registrations in C# and Spring beans in Java/Kotlin only, and this repository 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 — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check 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 — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 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-none-none-eabi.swiftmodule: no space left on device; runtime evidence skipped.
  • C1 Data Protection — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These 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 — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These authorization controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks authorization controls.
  • C3 Audit Trail — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These 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 — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, F#, JavaScript/TypeScript, Dart, Ruby and Scala source only, and 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 — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, JavaScript/TypeScript, Java, Dart, Ruby and Scala source only, and 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 — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), 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 — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These web-security controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks web-security controls.
  • X16 Unfloored truncation loop — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, 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 — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, 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 — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, 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; 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.
  • X29 Per-element action decided by a fixed element — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, 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 — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, 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 — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax 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

Watchdog assesses the repository exactly as committed, and only the repository. By design it does not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.

Per-dimension blind spots

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

  • D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
  • D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
  • D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
  • D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
  • D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
  • D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
  • D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
  • D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
  • D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
  • D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
  • D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
  • D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
  • D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
  • D20 ADR Quality: ADR quality is an LLM read of the decision records present — it cannot know about decisions made and never recorded, and its verdict is sampled and advisory.
  • D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
  • D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
  • D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
  • 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: Onboarding quality is an LLM read of the docs/setup present — it cannot run the onboarding or measure how long a real new joiner takes; the verdict is sampled and advisory.
  • 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".

Dimensions

D1 · Cyclomatic Complexity6.6 / 10Adequate✓ Tool-verified

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

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

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

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

sourcekitd_api_uid_t.init (cyclomatic 56)Sources/SwiftSourceKitPlugin/CompletionProvider.swift:445
Pattern.singleScore (cyclomatic 41)Sources/CompletionScoring/Text/Pattern.swift:452
Diagnostic.init (cyclomatic 33)Sources/SwiftLanguageService/Diagnostic.swift:168
BuildServerConfig.forSwiftPMBuildServer (cyclomatic 32)Sources/BuildServerIntegration/ExternalBuildServerAdapter.swift:92
CodeCompletionSession.completionsFromSKDResponse (cyclomatic 31)Sources/SwiftLanguageService/CodeCompletionSession.swift:491

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

What to do

  1. 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), Diagnostic.init (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.
  2. Stand up a CI pipeline, then gate Cyclomatic Complexity in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

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

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

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

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

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

51 method(s) exceeded the cognitive complexity threshold of 15; the worst was Pattern.singleScore at 97.

Pattern.singleScore (cognitive 97)Sources/CompletionScoring/Text/Pattern.swift:452
sourcekitd_api_uid_t.init (cognitive 51)Sources/SwiftSourceKitPlugin/CompletionProvider.swift:445
CodeCompletionSession.completionsFromSKDResponse (cognitive 42)Sources/SwiftLanguageService/CodeCompletionSession.swift:491
Toolchain.init (cognitive 42)Sources/ToolchainRegistry/Toolchain.swift:235
BuildServerConfig.forSwiftPMBuildServer (cognitive 38)Sources/BuildServerIntegration/ExternalBuildServerAdapter.swift:92

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

What to do

  1. 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.
  2. Stand up a CI pipeline, then gate Cognitive Complexity in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

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

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.

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

27 god class(es) detected.

MethodTooLong: SourceKitLSPServer.handle · ×13Sources/SourceKitLSP/SourceKitLSPServer.swift:596
FileTooLong: SourceKitLSP/SourceKitLSPServer.swift · ×9Sources/SourceKitLSP/SourceKitLSPServer.swift
TooManyMethods: SourceKitLSPServer · ×4Sources/SourceKitLSP/SourceKitLSPServer.swift:41
ClassTooLong: CodeCompletionSessionSources/SwiftLanguageService/CodeCompletionSession.swift:84

What to do

  1. 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).
  2. 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).
  3. 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).
  4. Stand up a CI pipeline, then gate God Classes in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

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

D4 · Code Duplication9.7 / 10Stronggated by 39 serious findings✓ Tool-verified

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

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

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

38 duplicated block group(s) detected. One further row reports members as variants of one another; it aggregates block groups already counted above and is not itself counted.

Duplicated block (6 lines × 2) · ×5Sources/SKTestSupport/SkipUnless.swift:231
Duplicated block (5 lines × 2) · ×5Sources/BuildServerIntegration/BuildServerManager.swift:1966
Duplicated block (15 lines × 2) · ×3Sources/SKUtilities/LineTable.swift:329
Duplicated block (11 lines × 2) · ×3Sources/BuildServerIntegration/BuildTargetIdentifierExtensions.swift:76
Duplicated block (9 lines × 2) · ×3Sources/ClangLanguageService/SemanticTokenTranslator.swift:50

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

What to do

  1. 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).
  2. Resolve the 5 Duplicated block (5 lines × 2) finding(s) in Code Duplication — start with BuildServerManager.swift, SwiftExtensions.swift, InlayHintResolve.swift. — One of this dimension's main actionable groups (5 warning-level).
  3. Resolve the 3 Duplicated block (15 lines × 2) finding(s) in Code Duplication — start with LineTable.swift (2), OpaqueParameterToGeneric.swift. — One of this dimension's main actionable groups (3 warning-level).
  4. Stand up a CI pipeline, then gate Code Duplication in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. Hardens enforcement from Documented toward Verified — provenance only; does not change the score.

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

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.

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

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

  1. Resolve the 9 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (9 warning-level).
  2. Resolve the 1 Unstable project ClangLanguageService (CMake) finding(s) in Coupling. — One of this dimension's main actionable groups (1 warning-level).
  3. Resolve the 1 Unstable project SwiftLanguageService (CMake) finding(s) in Coupling. — One of this dimension's main actionable groups (1 warning-level).
  4. Stand up a CI pipeline, then gate Coupling in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

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

D6 · Cohesion (LCOM4)7.9 / 10Strong✓ Tool-verified

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

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

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

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

17 of 98 classes have LCOM4 above 3.

Low cohesion: SourceKitLSPServer (LCOM4 31) · ×17Sources/SourceKitLSP/SourceKitLSPServer.swift:41

What to do

  1. Resolve the 17 Low cohesion finding(s) in Cohesion (LCOM4) — start with SourceKitLSPServer.swift (2), DocumentationLanguageService.swift, CompilationDatabase.swift. — One of this dimension's main actionable groups (17 warning-level).
  2. Stand up a CI pipeline, then gate Cohesion (LCOM4) in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. Hardens enforcement from Documented toward Verified — provenance only; does not change the score.

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

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

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

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

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

416 test methods: 384 unit, 32 integration, 0 BDD, 0 e2e.

✓ On the Gold path — maintain.

Detailed fixes: d9_recommendation.md.

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.

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

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
Skipped test: testBinarySwiftModuleSymbolsNotIndexedTests/SourceKitLSPTests/WorkspaceSymbolInfoTests.swift:167
No direct assertions: testCandidateBatchCreation · ×220Tests/CompletionScoringPerfTests/CandidateBatchPerfTests.swift:18
Test project verifies nothing: CompletionScoringPerfTestsTests/CompletionScoringPerfTests/CandidateBatchPerfTests.swift:18
Skipped (documented): testToolsetsTests/BuildServerIntegrationTests/SwiftPMBuildServerTests.swift:1267

What to do

  1. 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).
  2. 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).
  3. 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).
  4. Stand up a CI pipeline, then gate Test Quality in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

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

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

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

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

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

Secret scan ran and found no leaked secrets.

✓ On the Gold path — maintain.

Detailed fixes: d13_recommendation.md.

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

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

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

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

0 of 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`.

✓ On the Gold path — maintain.

Detailed fixes: d14_recommendation.md.

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

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

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

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

Top hotspots: Sources/SourceKitLSP/SourceKitLSPServer.swift (16×62=992); Sources/SwiftLanguageService/CodeCompletionSession.swift (6×31=186); Sources/SourceKitLSP/MessageHandlingDependencyTracker.swift (2×46=92)

Hotspot: Sources/SourceKitLSP/SourceKitLSPServer.swift · ×3Sources/SourceKitLSP/SourceKitLSPServer.swift:596

What to do

  1. Resolve the 3 Hotspot finding(s) in Churn × Complexity Hotspots — start with SourceKitLSPServer.swift, CodeCompletionSession.swift, MessageHandlingDependencyTracker.swift. — One of this dimension's main actionable groups (3 warning-level).

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

D16 · Bus Factor9.0 / 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.

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

21 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 221 of the 347 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.

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

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

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

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

39 deducted task-comment markers across 58014 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.

TodoComment · ×25Sources/TSCExtensions/Process+Run.swift:128
FixmeComment · ×14Sources/SwiftSourceKitPlugin/CompletionProvider.swift:371

What to do

  1. 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).
  2. 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).
  3. Stand up a CI pipeline, then gate Explicit Debt in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

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

D20 · ADR Quality0.0 / 10Critical✓ Tool-verified

What it measures: Whether architecture decisions are recorded well (context, decision, consequences).

Method: Per-ADR judgment by language model at low temperature with two-pass stability; confidence is share of ADRs evaluated; enforcement-field presence detected deterministically. Advisory.

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

No architecture decision records were found.

No ADRs found

What to do

  1. Resolve the 1 No ADRs found finding(s) in ADR Quality. — 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.

D26 · Project Cohesion0.0 / 10Critical✓ Tool-verified

What it measures: Whether each project is a focused, coherent unit rather than an oversized grab-bag.

Method: Project size overshoot penalties (LoC / public-type count / namespace count, 2-of-3 flag) weighted by log magnitude. Exhaustive across projects, deterministic, LLM-independent.

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

1 of 2 build units (SwiftPM) flagged as possibly oversized/incoherent.

Projects may be oversized for their cohesion

What to do

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

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

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

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

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

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

✓ On the Gold path — maintain.

Detailed fixes: d28_recommendation.md.

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

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

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

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

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

semgrep found no security issues. semgrep hit a parse error in 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.

✓ On the Gold path — maintain.

Detailed fixes: d29_recommendation.md.

D31 · IaC & Container Security9.9 / 10Exemplary✓ Tool-verified

What it measures: Whether Dockerfiles / Terraform / Kubernetes config follow security best practices.

Method: IaC/container misconfiguration scan via trivy config (REDACTED/Terraform/K8s/Helm/CloudFormation); severity rules to 0-10 moderate normalizer. NotApplicable without manifests. Exhaustive, deterministic.

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

3 finding(s): 0 critical, 0 high, 0 medium, 3 low.

REDACTED

✓ On the Gold path — maintain.

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

D34 · Knowledge Freshness8.5 / 10Adequategated by 2 critical findings✓ Tool-verified

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

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

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

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

Orphaned knowledge · ×2Sources/SwiftLanguageService/SelectionRange.swift:1
Orphaned file · ×31Sources/SwiftSyntaxCodeActions/RemoveRedundantParentheses.swift:1
Further orphaned files (smaller)

What to do

  1. 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).
  2. Resolve the 31 Orphaned file finding(s) in Knowledge Freshness — start with RemoveRedundantParentheses.swift, ConvertJSONToCodableStruct.swift, OptionSchema.swift. — One of this dimension's main actionable groups (31 recommendation-level).
  3. 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.

D35 · Change Coupling9.4 / 10Stronggated by 12 serious findings✓ Tool-verified

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

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

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

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

Strongest change-coupling: CursorInfo.swift↔SemanticRefactoring.swift 69%; InProcessSourceKitLSPClient.swift↔TestSourceKitLSPClient.swift 69%; JSONCompilationDatabaseBuildServer.swift↔LegacyBuildServer.swift 67%

Change coupling: InProcessSourceKitLSPClient.swift ↔ TestSourceKitLSPClient.swift · ×9Sources/InProcessClient/InProcessSourceKitLSPClient.swift:1
Change-coupling hub: CursorInfo.swift → OpenInterface.swift, RelatedIdentifiers.swift, SemanticRefactoring.swift, VariableTypeInfo.swift · ×3Sources/SwiftLanguageService/CursorInfo.swift

What to do

  1. Resolve the 9 Change coupling finding(s) in Change Coupling — start with BuildServerManager.swift (2), InProcessSourceKitLSPClient.swift, JSONCompilationDatabaseBuildServer.swift. — One of this dimension's main actionable groups (9 warning-level).
  2. Resolve the 3 Change-coupling hub finding(s) in Change Coupling — start with CursorInfo.swift, RelatedIdentifiers.swift, SwiftLanguageService.swift. — One of this dimension's main actionable groups (3 warning-level).

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

Frontend & cross-cutting dimensions

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

AX10 · Code composition10.0 / 10Exemplary✓ Tool-verified

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

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

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

What to do

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

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

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

AX4 · Dependency direction10.0 / 10Exemplary✓ Tool-verified

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.

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.

AX9 · CQS / query purity10.0 / 10Exemplary✓ Tool-verified

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.

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

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

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

What to do

  • Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
  • Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
M2 · Architecture documentation0.0 / 10Critical✓ Tool-verified

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

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

  • No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
  • No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.

What to do

  • Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
  • Add a C4 context/container diagram (Structurizr, PlantUML or Mermaid) or an architecture.md overview.
M3 · Folder & project structure10.0 / 10Exemplary✓ Tool-verified

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

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

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

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

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

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.
P2 · Observability5.0 / 10Adequate✓ Tool-verified

Readiness · Readiness — Whether the code is diagnosable in production — structured logging, tracing/metrics, health checks.

Method: Filesystem/Roslyn scan: structured-logging frameworks (Serilog, NLog), OpenTelemetry, and health-check endpoint patterns. Exhaustive, deterministic.

  • 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.
P3 · Security & performance tooling0.0 / 10Critical✓ Tool-verified

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

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

  • No static application security testing detected. For this repository's stack, add 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.
P4 · Deployment & Rollback5.0 / 10Adequate✓ Tool-verified

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.
PF2 · Allocation hygiene6.4 / 10Adequate✓ Tool-verified

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

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

What to do

  • Raise allocation-aware density on the hot paths — currently 43 use(s) across 61,057 production line(s) (~0.7/1k). More of the idioms below on the allocation-heavy paths climbs this toward 10.
  • Swift: on hot paths, reserveCapacity before appending, use ContiguousArray for class-element arrays, work in place with withUnsafeBufferPointer/withUnsafeTemporaryAllocation, and make large values ~Copyable with borrowing/consuming parameters.
PF3 · Async & latency hygiene10.0 / 10Exemplary✓ Tool-verified

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Other · Code Health — Whether a `for` loop leaves the `dict`, `set` or `deque` it is walking alone — CPython's iterators over those check that the collection has not changed size since the loop began, so a body that removes from (or empties) the very collection the loop is walking makes the next step raise `RuntimeError: dictionary changed size during iteration` and the remaining items are never seen.

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

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.

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

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

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

  • `catch` 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)
X30 · Support guard that admits what it rejects10.0 / 10Exemplary○ Nothing flagged

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

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

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.

LensScoreRatingImpact
Code Health76%StrongSolid.
Architecture88%Adequate — gated by D26Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Maturity62%Adequate — gated by M2Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Readiness31%Weak — gated by P1, P3Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Security100%ExemplaryStrongest area.
Performance79%StrongSolid.
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 — 61 check(s) not relevant to this codebase

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

  • AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
  • AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
  • AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
  • AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
  • AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
  • AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
  • AC7 A11y enforcement — No web markup found — accessibility is not applicable to this repository.
  • AX1 Captive dependencies — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
  • AX2 Stateful singletons — No container singleton was found, so there is no shared instance for concurrent requests to race on. No 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-none-none-eabi.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.
  • D21 Naming Consistency — Naming consistency is measured on C# only; Python, Swift not measured.
  • D22 Internal API Consistency — The exposed public-API surface could not be collected — no C#/VB projects loaded.
  • D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ projects each declaring an entity of their own. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
  • D24 Comment Value — D24 reads C# and Visual Basic comments only — this repository's production source is .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
  • D27 Navigability — D27 counts a call into the standard library or a dependency as unresolved for this repository's language (.swift), so too few call sites counted as resolved to assess navigability. Not scored: this is a gap in the analyzer, not a verdict about this repository.
  • 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) — 218 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
  • D36 Supply-chain Provenance & Signing — No CI/build pipeline found (.github/.forgejo/.gitea workflows, .circleci, .buildkite, .woodpecker, .teamcity, .gitlab-ci.yml, .travis.yml, bitbucket-pipelines.yml, .drone.yml, .cirrus.yml, .woodpecker.yml, appveyor.yml, azure-pipelines*.yml, .pipelines/, .vsts-ci/, .azuredevops/, Jenkinsfile); there is no build to attest provenance for.
  • D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
  • D39 IL Efficiency — D39 measures the IL emitted by a .NET build; this repository has no .NET solution or project files, so the dimension does not apply.
  • D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
  • D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
  • D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
  • 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 — no coverage report found on disk — produce a coverage report in a standard format (lcov — `swift test --enable-code-coverage` (SwiftPM) or `xcodebuild test -scheme <YourScheme> -enableCodeCoverage YES` (an .xcodeproj/.xcworkspace suite), then `xcrun llvm-cov export -format=lcov`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures, or wire coverage collection into CI, to enable this cross-layer check
  • PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for `Benchmark("…")` in a 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.
  • 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.
  • 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
  • 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
  • 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.
  • 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
  • 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.

Critical — 3 finding(s)
D34 · Knowledge Freshness · Orphaned knowledge · ×2
  • 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.)
Serious — 298 finding(s)
D10 · Test Quality · No assertions · ×53
  • 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* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, 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* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, 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* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, 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* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, 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* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, 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* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, 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* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, 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* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, 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* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, 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* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, 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* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, 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* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, 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* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, 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* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, 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* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, 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* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, 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* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, 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* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, 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* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, 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* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, 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* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, 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* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, 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* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, 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* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, 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* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, 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.
  • + 28 more in this group — see findings.md.
D17 · Explicit Debt · TodoComment · ×25
  • 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:2244 — // TODO: Remove this workaround once https://github.com/swiftlang/swift/issues/75600 is fixed
  • TodoComment Sources/SourceKitLSP/SourceKitLSPServer.swift:2305 — // TODO: Remove this workaround once https://github.com/swiftlang/swift/issues/75600 is fixed
  • TodoComment Sources/SourceKitLSP/SourceKitLSPServer.swift:2345 — // TODO: Remove this workaround once https://github.com/swiftlang/swift/issues/75600 is fixed
  • TodoComment Sources/SourceKitLSP/SourceKitLSPServer.swift:2497 — // TODO: Remove this workaround once https://github.com/swiftlang/swift/issues/75600 is fixed
  • TodoComment Sources/SourceKitLSP/SourceKitLSPServer.swift:2590 — // TODO: Remove this workaround once https://github.com/swiftlang/swift/issues/75600 is fixed
  • TodoComment Sources/SourceKitLSP/SourceKitLSPServer.swift:2643 — // 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:356 — // 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:990 — // 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:624 — // 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)
D6 · Cohesion (LCOM4) · Low cohesion · ×17
  • Low cohesion: SourceKitLSPServer (LCOM4 31) Sources/SourceKitLSP/SourceKitLSPServer.swift:41 — SourceKitLSPServer's methods fall into 31 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 31 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: 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: Sequence (LCOM4 9) Sources/SourceKitLSP/SourceKitLSPServer.swift:2903 — Sequence'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:687 — 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:392 — 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:30 — 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.
D17 · Explicit Debt · FixmeComment · ×14
  • 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.
X3 · Exception handling · Swallowed exception (caught, then discarded) · ×14
  • 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:689 — `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:224 — `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:455 — `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.
D3 · God Classes · MethodTooLong · ×13
  • MethodTooLong: SourceKitLSPServer.handle Sources/SourceKitLSP/SourceKitLSPServer.swift:596 — MethodTooLong — handle runs 151 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 51 over it, 1.51× 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:491 — MethodTooLong — completionsFromSKDResponse runs 137 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 37 over it, 1.37× 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:883 — 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:982 — 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:567 — 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.
D3 · God Classes · FileTooLong · ×9
  • FileTooLong: SourceKitLSP/SourceKitLSPServer.swift Sources/SourceKitLSP/SourceKitLSPServer.swift — FileTooLong — 1786 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 1286 over it, 3.57× 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 — 1225 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 725 over it, 2.45× 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 — 955 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 455 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 — 606 significant lines (blank, comment-only and punctuation-only lines excluded), about 90% of them inside a single declaration: CodeCompletionSession (84-978). The bar is 500 significant lines; this is 106 over it, 1.21× 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 — 585 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 85 over it, 1.17× 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.
D35 · Change Coupling · Change coupling · ×9
  • Change coupling: InProcessSourceKitLSPClient.swift ↔ TestSourceKitLSPClient.swift Sources/InProcessClient/InProcessSourceKitLSPClient.swift:1 — `Sources/InProcessClient/InProcessSourceKitLSPClient.swift` and `Sources/SKTestSupport/TestSourceKitLSPClient.swift` change together 69% of the time (11 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 11 shared commits counted here, the most recent 3 are `99cac8f9` Update for the ThreadSafeBox.value setter removal; `a6c926fa` Relax atomic memory orderings; switch semaphore to release/acquire; `83de30d2` Migrate atomic call sites to Synchronization.Atomic and ThreadSafeBox — run `git show` on any of them.
  • 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: BuildServerManager.swift ↔ CustomBuildServerTestProject.swift Sources/BuildServerIntegration/BuildServerManager.swift:1 — `Sources/BuildServerIntegration/BuildServerManager.swift` and `Sources/SKTestSupport/CustomBuildServerTestProject.swift` change together 57% of the time (12 of the 21 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 12 shared commits counted here, the most recent 3 are `99cac8f9` Update for the ThreadSafeBox.value setter removal; `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`) — 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 55% of the time (17 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 17 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 ↔ DocumentationLanguageService.swift Sources/ClangLanguageService/ClangLanguageService.swift:1 — `Sources/ClangLanguageService/ClangLanguageService.swift` and `Sources/DocumentationLanguageService/DocumentationLanguageService.swift` change together 55% of the time (12 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 12 shared commits counted here, the most recent 3 are `f84abc1e` Use 'weak let' for immutable weak references (SE-0481); `f2a12145` Scope language service instances per workspace; `1c99daab` [TestDiscovery] Prefer syntactic scan results over semantic index — 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: SemanticRefactoring.swift ↔ VariableTypeInfo.swift Sources/SwiftLanguageService/SemanticRefactoring.swift:1 — `Sources/SwiftLanguageService/SemanticRefactoring.swift` and `Sources/SwiftLanguageService/VariableTypeInfo.swift` change together 52% of the time (15 of the 29 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 15 shared commits counted here, the most recent 3 are `6f98029f` Rename `SKDValue` to `SKDRequestValue` (at that commit the files were still `Sources/SourceKitLSP/Swift/SemanticRefactoring.swift` and `Sources/SourceKitLSP/Swift/VariableTypeInfo.swift`); `b5fd79fb` Generate sourcekitd UIDs instead of manually maintaining the list (at that commit the files were still `Sources/SourceKitLSP/Swift/SemanticRefactoring.swift` and `Sources/SourceKitLSP/Swift/VariableTypeInfo.swift`); `3991fae8` Define methods on `SourceKitD` to create arrays and dictionaries inst… (at that commit the files were still `Sources/SourceKitLSP/Swift/SemanticRefactoring.swift` and `Sources/SourceKitLSP/Swift/VariableTypeInfo.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.
D5 · Coupling · Off the main sequence · ×9
  • 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.
D4 · Code Duplication · Duplicated block (6 lines × 2) · ×5
  • Duplicated block (6 lines × 2) Sources/SKTestSupport/SkipUnless.swift:231 — Sources/SKTestSupport/SkipUnless.swift:231-236 | Sources/SKTestSupport/SkipUnless.swift:351-360 — 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:231` 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:2566 — Sources/SourceKitLSP/SourceKitLSPServer.swift:2566-2571 | Sources/SourceKitLSP/SourceKitLSPServer.swift:2632-2637 — 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.
D4 · Code Duplication · Duplicated block (5 lines × 2) · ×5
  • Duplicated block (5 lines × 2) Sources/BuildServerIntegration/BuildServerManager.swift:1966 — Sources/BuildServerIntegration/BuildServerManager.swift:1966-1970 | Sources/BuildServerIntegration/BuildServerManager.swift:2044-2049 — 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:1966` 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 (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/SwiftLanguageService/InlayHintResolve.swift:76 — Sources/SwiftLanguageService/InlayHintResolve.swift:76-80 | Sources/SwiftLanguageService/SignatureHelp.swift:144-148 — 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/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 (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.
D3 · God Classes · TooManyMethods · ×4
  • TooManyMethods: SourceKitLSPServer Sources/SourceKitLSP/SourceKitLSPServer.swift:41 — TooManyMethods — 123 methods, declared across 5 files: SourceKitLSP/SourceKitLSPServer.swift (100), SourceKitLSP/WorkspaceSymbols.swift (14), SourceKitLSP/Rename.swift (7), Diagnose/IndexCommand.swift (1), +1 more file(s). The bar is 30 methods; this is 93 over it, 4.10× 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 — 97 methods, declared across 26 files: SwiftLanguageService/SwiftLanguageService.swift (47), SwiftLanguageService/Rename.swift (10), SwiftLanguageService/SemanticTokens.swift (6), SwiftLanguageService/CursorInfo.swift (4), +22 more file(s). The bar is 30 methods; this is 67 over it, 3.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: 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:392 — TooManyMethods — 52 methods, declared across 2 files: BuildServerIntegration/BuildServerManager.swift (50), DocumentationLanguageService/BuildSystemIntegrationExtensions.swift (2). The bar is 30 methods; this is 22 over it, 1.73× 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.
D15 · Churn × Complexity Hotspots · Hotspot · ×3
  • Hotspot: Sources/SourceKitLSP/SourceKitLSPServer.swift Sources/SourceKitLSP/SourceKitLSPServer.swift:596 — Sources/SourceKitLSP/SourceKitLSPServer.swift changed 16 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 62 in SourceKitLSPServer.handle at line 596. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-30..2026-10-28, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-30 10:50:55 -07:00' --until='2026-10-28 10:50:55 -07:00' --full-history --no-merges -- Sources/SourceKitLSP/SourceKitLSPServer.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.
  • Hotspot: Sources/SwiftLanguageService/CodeCompletionSession.swift Sources/SwiftLanguageService/CodeCompletionSession.swift:491 — Sources/SwiftLanguageService/CodeCompletionSession.swift changed 6 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 31 in CodeCompletionSession.completionsFromSKDResponse at line 491. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-30..2026-10-28, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-30 10:50:55 -07:00' --until='2026-10-28 10:50:55 -07: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.
  • Hotspot: Sources/SourceKitLSP/MessageHandlingDependencyTracker.swift Sources/SourceKitLSP/MessageHandlingDependencyTracker.swift:165 — Sources/SourceKitLSP/MessageHandlingDependencyTracker.swift changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 46 in MessageHandlingDependencyTracker.init at line 165. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-30..2026-10-28, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-30 10:50:55 -07:00' --until='2026-10-28 10:50:55 -07:00' --full-history --no-merges -- Sources/SourceKitLSP/MessageHandlingDependencyTracker.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.
D35 · Change Coupling · Change-coupling hub · ×3
  • 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.
  • Change-coupling hub: RelatedIdentifiers.swift → Rename.swift, SemanticTokens.swift, VariableTypeInfo.swift Sources/SwiftLanguageService/RelatedIdentifiers.swift — `Sources/SwiftLanguageService/RelatedIdentifiers.swift` changes together with 3 other files — `Sources/SourceKitLSP/Rename.swift`, `Sources/SwiftLanguageService/SemanticTokens.swift`, `Sources/SwiftLanguageService/VariableTypeInfo.swift` — none of which declares a dependency on it: one file is the hub of 3 separate couplings, not 3 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 3.
  • Change-coupling hub: SwiftLanguageService.swift → ClangLanguageService.swift, DocumentationLanguageService.swift, WorkDoneProgressManager.swift Sources/SwiftLanguageService/SwiftLanguageService.swift — `Sources/SwiftLanguageService/SwiftLanguageService.swift` changes together with 3 other files — `Sources/ClangLanguageService/ClangLanguageService.swift`, `Sources/DocumentationLanguageService/DocumentationLanguageService.swift`, `Sources/LanguageServerProtocolExtensions/WorkDoneProgressManager.swift` — none of which declares a dependency on it: one file is the hub of 3 separate couplings, not 3 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 3.
D4 · Code Duplication · Duplicated block (15 lines × 2) · ×3
  • 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.
D4 · Code Duplication · Duplicated block (11 lines × 2) · ×3
  • 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.
D4 · Code Duplication · Duplicated block (9 lines × 2) · ×3
  • 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:605 — Sources/SemanticIndex/TaskScheduler.swift:605-614 | Sources/SemanticIndex/TaskScheduler.swift:628-636 — 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/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.
D4 · Code Duplication · Duplicated block (7 lines × 2) · ×3
  • 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/SKUtilities/LineTable.swift:451 — Sources/SKUtilities/LineTable.swift:451-457 | Sources/SKUtilities/LineTable.swift:488-498 — 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:451` 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 (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.
D4 · Code Duplication · Duplicated block (10 lines × 2) · ×2
  • 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:178-187 — 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.
D1 · Cyclomatic Complexity · sourcekitd_api_uid_t.init (cyclomatic 56) · ×1
  • 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.
D1 · Cyclomatic Complexity · Pattern.singleScore (cyclomatic 41) · ×1
  • 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.
D1 · Cyclomatic Complexity · Diagnostic.init (cyclomatic 33) · ×1
  • 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.
D1 · Cyclomatic Complexity · BuildServerConfig.forSwiftPMBuildServer (cyclomatic 32) · ×1
  • 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.
D1 · Cyclomatic Complexity · CodeCompletionSession.completionsFromSKDResponse (cyclomatic 31) · ×1
  • CodeCompletionSession.completionsFromSKDResponse (cyclomatic 31) Sources/SwiftLanguageService/CodeCompletionSession.swift:491 — CodeCompletionSession.completionsFromSKDResponse has cyclomatic complexity 31 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · PriorityBucket.init (cyclomatic 26) · ×1
  • 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.
D1 · Cyclomatic Complexity · SemanticIndexManager.scheduleIndexing (cyclomatic 25) · ×1
  • SemanticIndexManager.scheduleIndexing (cyclomatic 25) Sources/SemanticIndex/SemanticIndexManager.swift:883 — 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.
D1 · Cyclomatic Complexity · UpdateIndexStoreTaskDescription.updateIndexStore (cyclomatic 24) · ×1
  • 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.
D1 · Cyclomatic Complexity · BuildServerManager.buildSettingsInferredFromMainFile (cyclomatic 23) · ×1
  • BuildServerManager.buildSettingsInferredFromMainFile (cyclomatic 23) Sources/BuildServerIntegration/BuildServerManager.swift:1302 — 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.
D1 · Cyclomatic Complexity · Pattern.populateMatchingRangesForAcronymMatch (cyclomatic 23) · ×1
  • 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.
D1 · Cyclomatic Complexity · Toolchain.init (cyclomatic 23) · ×1
  • 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.
D1 · Cyclomatic Complexity · SourceKitLSPServer.rename (cyclomatic 22) · ×1
  • 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.
D1 · Cyclomatic Complexity · XMLToMarkdown.toMarkdown (cyclomatic 22) · ×1
  • 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.
D1 · Cyclomatic Complexity · SwiftPMBuildServer.prepare (cyclomatic 21) · ×1
  • 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.
D1 · Cyclomatic Complexity · SwiftLanguageService.expandMacro (cyclomatic 20) · ×1
  • 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.
D1 · Cyclomatic Complexity · SwiftLanguageService.removeUnusedImports (cyclomatic 20) · ×1
  • 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.
D1 · Cyclomatic Complexity · AddExplicitEnumRawValues.textRefactor (cyclomatic 20) · ×1
  • 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.
D1 · Cyclomatic Complexity · SourceKitLSPServer.indexBasedDefinition (cyclomatic 19) · ×1
  • SourceKitLSPServer.indexBasedDefinition (cyclomatic 19) Sources/SourceKitLSP/SourceKitLSPServer.swift:1849 — 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 62) 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.
D1 · Cyclomatic Complexity · SemanticIndexManager.filesToIndex (cyclomatic 18) · ×1
  • SemanticIndexManager.filesToIndex (cyclomatic 18) Sources/SemanticIndex/SemanticIndexManager.swift:521 — 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.
D1 · Cyclomatic Complexity · ConvertStringConcatenationToStringInterpolation.refactor (cyclomatic 18) · ×1
  • 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.
D1 · Cyclomatic Complexity · BuildServerManager.init (cyclomatic 17) · ×1
  • BuildServerManager.init (cyclomatic 17) Sources/BuildServerIntegration/BuildServerManager.swift:567 — 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.
D1 · Cyclomatic Complexity · JSONSchemaBuilder.buildJSONSchema (cyclomatic 17) · ×1
  • 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.
D1 · Cyclomatic Complexity · SwiftLanguageService.findFunctionLikeRange (cyclomatic 17) · ×1
  • 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.
D1 · Cyclomatic Complexity · SwiftLanguageService.textEdit (cyclomatic 17) · ×1
  • 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.
D1 · Cyclomatic Complexity · build-script-helper.get_swiftpm_options (cyclomatic 17) · ×1
  • 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.
D1 · Cyclomatic Complexity · TaskScheduler.poke (cyclomatic 16) · ×1
  • TaskScheduler.poke (cyclomatic 16) Sources/SemanticIndex/TaskScheduler.swift:554 — 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.
D1 · Cyclomatic Complexity · DiagnosticReportManager.requestReport (cyclomatic 16) · ×1
  • 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.
D1 · Cyclomatic Complexity · SwiftLanguageService.editsToRename (cyclomatic 16) · ×1
  • 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.
D1 · Cyclomatic Complexity · RequestHandler.handleRequest (cyclomatic 16) · ×1
  • 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.
D1 · Cyclomatic Complexity · RemoveRedundantParentheses.canRemoveParentheses (cyclomatic 16) · ×1
  • 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.
D10 · Test Quality · Skipped test · ×1
  • Skipped test: testBinarySwiftModuleSymbolsNotIndexed Tests/SourceKitLSPTests/WorkspaceSymbolInfoTests.swift:167 — Skipped — throws XCTSkip
D2 · Cognitive Complexity · Pattern.singleScore (cognitive 97) · ×1
  • 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.
D2 · Cognitive Complexity · sourcekitd_api_uid_t.init (cognitive 51) · ×1
  • 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.
D2 · Cognitive Complexity · CodeCompletionSession.completionsFromSKDResponse (cognitive 42) · ×1
  • CodeCompletionSession.completionsFromSKDResponse (cognitive 42) Sources/SwiftLanguageService/CodeCompletionSession.swift:491 — CodeCompletionSession.completionsFromSKDResponse has cognitive complexity 42 (threshold 15). Drivers by points: if/else 23 (29 pts), boolean chains 11, 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.
D2 · Cognitive Complexity · Toolchain.init (cognitive 42) · ×1
  • 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.
D2 · Cognitive Complexity · BuildServerConfig.forSwiftPMBuildServer (cognitive 38) · ×1
  • 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.
D2 · Cognitive Complexity · Diagnostic.init (cognitive 38) · ×1
  • 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.
D2 · Cognitive Complexity · SemanticIndexManager.filesToIndex (cognitive 37) · ×1
  • SemanticIndexManager.filesToIndex (cognitive 37) Sources/SemanticIndex/SemanticIndexManager.swift:521 — 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.
D2 · Cognitive Complexity · SemanticIndexManager.scheduleIndexing (cognitive 37) · ×1
  • SemanticIndexManager.scheduleIndexing (cognitive 37) Sources/SemanticIndex/SemanticIndexManager.swift:883 — 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.
D2 · Cognitive Complexity · AddExplicitEnumRawValues.textRefactor (cognitive 37) · ×1
  • 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.
D2 · Cognitive Complexity · Pattern.populateMatchingRangesForAcronymMatch (cognitive 36) · ×1
  • 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.
D2 · Cognitive Complexity · TaskScheduler.poke (cognitive 34) · ×1
  • TaskScheduler.poke (cognitive 34) Sources/SemanticIndex/TaskScheduler.swift:554 — 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.
D2 · Cognitive Complexity · UpdateIndexStoreTaskDescription.updateIndexStore (cognitive 33) · ×1
  • 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.
D2 · Cognitive Complexity · Pattern.bestScore (cognitive 31) · ×1
  • 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.
D2 · Cognitive Complexity · OSLogScraper.requestInfo (cognitive 31) · ×1
  • 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.
D2 · Cognitive Complexity · SourceKitLSPServer.rename (cognitive 30) · ×1
  • 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.
D2 · Cognitive Complexity · JSONSchemaBuilder.buildJSONSchema (cognitive 30) · ×1
  • 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.
D2 · Cognitive Complexity · SwiftPMBuildServer.buildTargetSources (cognitive 29) · ×1
  • 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.
D2 · Cognitive Complexity · SourceKitLSPServer.indexBasedDefinition (cognitive 28) · ×1
  • SourceKitLSPServer.indexBasedDefinition (cognitive 28) Sources/SourceKitLSP/SourceKitLSPServer.swift:1849 — 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.
D2 · Cognitive Complexity · ConvertStringConcatenationToStringInterpolation.refactor (cognitive 27) · ×1
  • 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.
D2 · Cognitive Complexity · SourceKitD.send (cognitive 26) · ×1
  • 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.
D2 · Cognitive Complexity · Pattern.matchLocation (cognitive 25) · ×1
  • 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.
D2 · Cognitive Complexity · SourceKitLSPServer.initialize (cognitive 25) · ×1
  • SourceKitLSPServer.initialize (cognitive 25) Sources/SourceKitLSP/SourceKitLSPServer.swift:846 — 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.
D2 · Cognitive Complexity · SwiftLanguageService.expandMacro (cognitive 25) · ×1
  • 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.
D2 · Cognitive Complexity · RewriteSourceKitPlaceholders.swift.rewriteSourceKitPlaceholders (cognitive 24) · ×1
  • 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.
D2 · Cognitive Complexity · SwiftLanguageService.removeUnusedImports (cognitive 22) · ×1
  • 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.
D2 · Cognitive Complexity · ExternalBuildServerAdapter.getConfigPath (cognitive 21) · ×1
  • 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.
D2 · Cognitive Complexity · SourceKitLSPServer.implementation (cognitive 21) · ×1
  • SourceKitLSPServer.implementation (cognitive 21) Sources/SourceKitLSP/SourceKitLSPServer.swift:2024 — 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.
D2 · Cognitive Complexity · ConvertStringConcatenationToStringInterpolation.preflight (cognitive 21) · ×1
  • 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.
D2 · Cognitive Complexity · SourceKitLSPServer.symbolItems (cognitive 20) · ×1
  • 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.
D2 · Cognitive Complexity · BuildServerManager.init (cognitive 19) · ×1
  • BuildServerManager.init (cognitive 19) Sources/BuildServerIntegration/BuildServerManager.swift:567 — 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.
D2 · Cognitive Complexity · SwiftPMBuildServer.searchForConfig (cognitive 19) · ×1
  • 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.
D2 · Cognitive Complexity · SwiftPMBuildServer.loadBuildDescriptionWithRetryOnOutputFileMapWriteErrorOnWindows (cognitive 19) · ×1
  • 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.
D2 · Cognitive Complexity · RemoveRedundantParentheses.canRemoveParentheses (cognitive 19) · ×1
  • 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.
D2 · Cognitive Complexity · OutOfProcessSourceKitRequestExecutor.requestResult (cognitive 18) · ×1
  • 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.
D2 · Cognitive Complexity · SourceKitLSPServer.subtypes (cognitive 18) · ×1
  • SourceKitLSPServer.subtypes (cognitive 18) Sources/SourceKitLSP/SourceKitLSPServer.swift:2631 — 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.
D2 · Cognitive Complexity · SourceKitLSPServer.members (cognitive 18) · ×1
  • 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.
D2 · Cognitive Complexity · Workspace.swift.createIndex (cognitive 18) · ×1
  • 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.
D2 · Cognitive Complexity · DiagnosticReportManager.requestReport (cognitive 18) · ×1
  • 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.
D2 · Cognitive Complexity · FoldingRangeFinder.addTrivia (cognitive 18) · ×1
  • 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.
D2 · Cognitive Complexity · InlayHintManager.processEdits (cognitive 18) · ×1
  • 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.
D2 · Cognitive Complexity · BuildServerManager.buildSettingsInferredFromMainFile · ×1
  • BuildServerManager.buildSettingsInferredFromMainFile::mainFileAndSettings (cognitive 17) Sources/BuildServerIntegration/BuildServerManager.swift:1328 — 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.
D2 · Cognitive Complexity · CompilerCommandLineOption.matchesIgnoringFrontend (cognitive 17) · ×1
  • 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.
D2 · Cognitive Complexity · SwiftPMBuildServer.prepare (cognitive 17) · ×1
  • 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.
D2 · Cognitive Complexity · ToolchainRegistry.init (cognitive 17) · ×1
  • ToolchainRegistry.init (cognitive 17) Sources/ToolchainRegistry/ToolchainRegistry.swift:168 — 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.
D2 · Cognitive Complexity · build-script-helper.get_swiftpm_options (cognitive 17) · ×1
  • 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.
D2 · Cognitive Complexity · BuildServerManager.mainFiles (cognitive 16) · ×1
  • BuildServerManager.mainFiles (cognitive 16) Sources/BuildServerIntegration/BuildServerManager.swift:1816 — 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.
D2 · Cognitive Complexity · DefinitionLocations.swift.definitionLocations (cognitive 16) · ×1
  • 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.
D2 · Cognitive Complexity · XMLToMarkdown.toMarkdown (cognitive 16) · ×1
  • 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.
D2 · Cognitive Complexity · PriorityBucket.init (cognitive 16) · ×1
  • 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.
D2 · Cognitive Complexity · ConvertIfLetToGuard.statementGuaranteesExit (cognitive 16) · ×1
  • 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.
D2 · Cognitive Complexity · InlineVariable.nodeToRefactor (cognitive 16) · ×1
  • 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.
D3 · God Classes · ClassTooLong · ×1
  • ClassTooLong: CodeCompletionSession Sources/SwiftLanguageService/CodeCompletionSession.swift:84 — ClassTooLong — 544 significant lines (blank, comment-only and punctuation-only lines excluded), 22 methods. The bar is 400 significant lines; this is 144 over it, 1.36× 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.
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/SourceKitD/sourcekitd_functions.swift:16 — Sources/SourceKitD/sourcekitd_functions.swift:16-94 | Sources/SourceKitD/sourcekitd_functions.swift:98-169 | Sources/SourceKitD/sourcekitd_functions.swift:173-226 | Sources/SourceKitD/sourcekitd_functions.swift:230-287 — 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 · Duplicated block (25–26 lines × 2) · ×1
  • 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.
D4 · Code Duplication · Duplicated block (15–23 lines × 2) · ×1
  • Duplicated block (15–23 lines × 2) Sources/SKOptions/SourceKitLSPOptions.swift:519 — Sources/SKOptions/SourceKitLSPOptions.swift:519-541 | Sources/ToolchainRegistry/Toolchain.swift:167-181 — 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/SKOptions/SourceKitLSPOptions.swift:519` 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.
D4 · Code Duplication · Duplicated block (22 lines × 2) · ×1
  • Duplicated block (22 lines × 2) Sources/BuildServerIntegration/BuildServerManager.swift:1995 — Sources/BuildServerIntegration/BuildServerManager.swift:1995-2016 | Sources/BuildServerIntegration/BuildServerManager.swift:2070-2091 — 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:1995` 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.
D4 · Code Duplication · Duplicated block (16 lines × 2) · ×1
  • Duplicated block (16 lines × 2) Sources/SourceKitLSP/SourceKitLSPServer.swift:2535 — Sources/SourceKitLSP/SourceKitLSPServer.swift:2535-2550 | Sources/SourceKitLSP/SourceKitLSPServer.swift:2612-2627 — 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 · Duplicated block (12–13 lines × 4) · ×1
  • 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.
D4 · Code Duplication · Duplicated block (13 lines × 2) · ×1
  • 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.
D4 · Code Duplication · Duplicated block (12 lines × 2) · ×1
  • Duplicated block (12 lines × 2) Sources/SwiftLanguageService/CodeCompletionSession.swift:397 — Sources/SwiftLanguageService/CodeCompletionSession.swift:397-408 | 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:397` 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.
D4 · Code Duplication · Duplicated block (10 lines × 3) · ×1
  • 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.
D4 · Code Duplication · Duplicated block (9–10 lines × 2) · ×1
  • 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.
D4 · Code Duplication · Duplicated block (8–9 lines × 2) · ×1
  • Duplicated block (8–9 lines × 2) Sources/SemanticIndex/TaskScheduler.swift:582 — Sources/SemanticIndex/TaskScheduler.swift:582-590 | Sources/SemanticIndex/TaskScheduler.swift:626-633 — 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:582` 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:580` calls `dependencies` and `Sources/SemanticIndex/TaskScheduler.swift:624` 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.
D4 · Code Duplication · Duplicated block (8 lines × 3) · ×1
  • Duplicated block (8 lines × 3) Sources/SemanticIndex/TaskScheduler.swift:584 — Sources/SemanticIndex/TaskScheduler.swift:584-592 | Sources/SemanticIndex/TaskScheduler.swift:605-613 | Sources/SemanticIndex/TaskScheduler.swift:628-635 — 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.
D4 · Code Duplication · Duplicated block (8 lines × 2) · ×1
  • 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.
D4 · Code Duplication · Duplicated block (6 lines × 3) · ×1
  • 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.
D4 · Code Duplication · Duplicated block (5 lines × 4) · ×1
  • Duplicated block (5 lines × 4) Sources/SourceKitD/SKDRequestArray.swift:84 — Sources/SourceKitD/SKDRequestArray.swift:84-88 | Sources/SourceKitD/SKDResponse.swift:67-71 | Sources/SourceKitD/SKDResponseArray.swift:107-111 | 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 4 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 4 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.
D5 · Coupling · Unstable project ClangLanguageService (CMake) · ×1
  • Unstable project ClangLanguageService (CMake) — ClangLanguageService (CMake) has instability 0.88 with 1 dependents.
D5 · Coupling · Unstable project SwiftLanguageService (CMake) · ×1
  • Unstable project SwiftLanguageService (CMake) — SwiftLanguageService (CMake) has instability 0.92 with 1 dependents.
P1 · CI/CD gates · No CI pipeline · ×1
  • No CI pipeline — No CI workflow found (.github/workflows, azure-pipelines.yml, .gitlab-ci.yml, …) — changes aren't gated by an automated build/test.
Minor — 275 finding(s)
D10 · Test Quality · No direct assertions · ×220
  • 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.
  • + 195 more in this group — see findings.md.
D34 · Knowledge Freshness · Orphaned file · ×31
  • 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/SourceKitLSP/DefinitionLocations.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.
  • + 6 more in this group — see findings.md.
X7 · Silent fallback defaults · Silent fallback default in catch · ×5
  • Silent fallback default in catch Sources/SwiftLanguageService/SwiftLanguageService.swift:1511 — `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.
D16 · Bus Factor · Off-boarding risk · ×4
  • Off-boarding risk: anonymized user #1 — If anonymized user #1 becomes unavailable, 5 significant file(s) lose their only recent owner: Sources/CompletionScoring/Utilities/SwiftExtensions.swift, Sources/Diagnose/RunSourcekitdRequestCommand.swift, Sources/BuildServerIntegration/BuildServerMessageDependencyTracker.swift, Sources/Diagnose/ReduceCommand.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, 4 significant file(s) lose their only recent owner: Sources/SwiftSyntaxCodeActions/ConvertStringConcatenationToStringInterpolation.swift, Sources/SourceKitLSP/DefinitionLocations.swift, Sources/SwiftLanguageService/InlayHintResolve.swift, Sources/SwiftLanguageService/TypeDefinition.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/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 #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.
D31 · IaC & Container Security · Low IaC · ×3
  • REDACTED
  • REDACTED
  • REDACTED
X10 · Duplicated predicate · Duplicated predicate · ×3
  • 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:2076 — `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 (21 single-owned of 221 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; 221 of the 347 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.
D20 · ADR Quality · No ADRs found · ×1
  • No ADRs found — 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/`.
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)` (57079 LoC, 610 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) — 31 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 23 more) (33 orphaned of 221 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; 221 of the 347 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.
M2 · Architecture documentation · No ADRs · ×1
  • No ADRs — No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
M2 · Architecture documentation · No architecture diagram/doc · ×1
  • No architecture diagram/doc — No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.
P2 · Observability · Logging is not universal · ×1
  • 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`.
P3 · Security & performance tooling · No SAST · ×1
  • 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.
Minor — 1 finding(s)
D10 · Test Quality · Skipped (documented) · ×1
  • 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.

DimensionToolVersionCommandFindingsRaw output
D28 · Secrets (history)gitleaks—gitleaks detect --no-banner --config /opt/gitleaks-rules/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-8140090459da4024b9d1db13846a241a/history.json --exit-code 0 --source .0artifacts/raw/gitleaks-history.json
D28 · Secrets (history)gitleaks—gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-8140090459da4024b9d1db13846a241a/tree.json --exit-code 0 --source .0artifacts/raw/gitleaks-tree.json
D29 · Static Analysis (SAST)semgrep—semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/watchdog-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt .0artifacts/raw/semgrep.json
D30 · Dependency Vulnerabilitiesnone (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—
D31 · IaC & Container Securitytrivy—trivy config --format json --quiet .3artifacts/raw/trivy-config.json
D32 · Data Compliance (PII/GDPR)semgrep—semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. semgrep could not parse 218 file(s) — `SourceKitLSPDevUtils/Sources/ConfigSchemaGen/ConfigSchemaGen.swift`, `Sources/BuildServerIntegration/BuildServerHooks.swift`, `Sources/BuildServerIntegration/BuildServerManager.swift`, `Sources/BuildServerIntegration/BuildServerManagerDelegate.swift`, `Sources/BuildServerIntegration/BuildServerMessageDependencyTracker.swift`, … (+213 more) — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real.0—
D36 · Supply-chain Provenance & Signingprovenance—provenance: not applicable — No CI/build pipeline found (.github/.forgejo/.gitea workflows, .circleci, .buildkite, .woodpecker, .teamcity, .gitlab-ci.yml, .travis.yml, bitbucket-pipelines.yml, .drone.yml, .cirrus.yml, .woodpecker.yml, appveyor.yml, azure-pipelines*.yml, .pipelines/, .vsts-ci/, .azuredevops/, Jenkinsfile); there is no build to attest provenance for.0—
D37 · Vulnerability-disclosure Policydisclosure—disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.0—
D40 · Network Egress Confinementruntime-hardening—runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.0—
D41 · Kernel & Syscall Confinementruntime-hardening—runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.0—
D42 · Runtime Threat Enforcementruntime-hardening—runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.0—
D43 · Malicious Dependenciesnone (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 01a1845c-5f11-7c86-b057-4d6e93758a55 · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.

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.

⬇ Findings, MITRE CWE-tagged .sarif⬇ Health changelog .md