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.
If Production Readiness rose from 31 to 70, the lowest score rated Strong, the score would rise from 53 to about 69.
New since the last survey: 7 findings
- 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
Fixed since the last survey: 8 findings
- 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 problem | Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.7 at a score of 53. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it. |
| Size | Medium: 58,014 lines of product code |
| What it is not | Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one. |
Top priorities
Diagnosis: what the measurements show together
Architecture — module dependency graph
Architecture: which parts of the code depend on which
| uses → | 1 SourceKitLSPDevUtils~SourceKitLSPDevUtils | 2 Sources.SKTestSupport.INPUTS.AbstractBuildServer | 3 SwiftSyntaxExtensions | 4 Utilities | 5 SwiftExtensions | 6 SwiftSourceKitPluginCommon | 7 SwiftSyntaxCodeActions | 8 TSCExtensions | 9 SourceKitD | 10 ToolchainRegistry | 11 SwiftLanguageService | 12 SourceKitLSPDevUtils~ConfigSchemaGen | 13 SKTestSupport | 14 DocumentationLanguageService | 15 SemanticIndex | 16 SKUtilities | 17 SwiftSourceKitPlugin | 18 SKOptions | 19 Diagnose | 20 SourceKitLSP | 21 LanguageServerProtocolExtensions | 22 ClangLanguageService | 23 CompletionScoring | 24 BuildServerIntegration | 25 InProcessClient | 26 SwiftSourceKitClientPlugin | 27 sourcekit-lsp |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 SourceKitLSPDevUtils~SourceKitLSPDevUtils | |||||||||||||||||||||||||||
| 2 Sources.SKTestSupport.INPUTS.AbstractBuildServer | |||||||||||||||||||||||||||
| 3 SwiftSyntaxExtensions | |||||||||||||||||||||||||||
| 4 Utilities | |||||||||||||||||||||||||||
| 5 SwiftExtensions | 1 | 1 | |||||||||||||||||||||||||
| 6 SwiftSourceKitPluginCommon | 2 | 5 | 1 | 4 | |||||||||||||||||||||||
| 7 SwiftSyntaxCodeActions | 48 | 15 | 3 | 13 | 31 | ||||||||||||||||||||||
| 8 TSCExtensions | 1 | 1 | 1 | ||||||||||||||||||||||||
| 9 SourceKitD | 1 | 2 | 8 | 1 | 1 | 17 | |||||||||||||||||||||
| 10 ToolchainRegistry | 2 | 3 | 2 | 10 | |||||||||||||||||||||||
| 11 SwiftLanguageService | 1 | 14 | 47 | 2 | 6 | 3 | 4 | 43 | 3 | 8 | 71 | 12 | 2 | 50 | |||||||||||||
| 12 SourceKitLSPDevUtils~ConfigSchemaGen | 3 | 1 | 3 | 1 | 14 | ||||||||||||||||||||||
| 13 SKTestSupport | 1 | 4 | 4 | 2 | 1 | 17 | 6 | 7 | 6 | 8 | 49 | ||||||||||||||||
| 14 DocumentationLanguageService | 2 | 1 | 1 | 1 | 1 | 6 | 1 | 1 | 8 | 1 | 26 | ||||||||||||||||
| 15 SemanticIndex | 4 | 2 | 1 | 3 | 17 | 1 | 2 | 13 | 1 | 3 | 29 | ||||||||||||||||
| 16 SKUtilities | 1 | 1 | 1 | 2 | 1 | 4 | 1 | ||||||||||||||||||||
| 17 SwiftSourceKitPlugin | 2 | 2 | 29 | 3 | 1 | 1 | 2 | 28 | 25 | ||||||||||||||||||
| 18 SKOptions | 3 | 1 | 12 | ||||||||||||||||||||||||
| 19 Diagnose | 3 | 4 | 5 | 2 | 1 | 5 | 1 | 3 | 3 | 32 | |||||||||||||||||
| 20 SourceKitLSP | 5 | 5 | 12 | 7 | 4 | 14 | 5 | 32 | 5 | 4 | 33 | 1 | 4 | 41 | |||||||||||||
| 21 LanguageServerProtocolExtensions | 1 | 2 | 3 | ||||||||||||||||||||||||
| 22 ClangLanguageService | 1 | 3 | 2 | 1 | 6 | 1 | 15 | 1 | 5 | ||||||||||||||||||
| 23 CompletionScoring | 5 | 6 | 18 | 1 | 1 | 32 | |||||||||||||||||||||
| 24 BuildServerIntegration | 2 | 2 | 7 | 3 | 2 | 25 | 8 | 1 | 15 | 7 | |||||||||||||||||
| 25 InProcessClient | 1 | 1 | 2 | 1 | |||||||||||||||||||||||
| 26 SwiftSourceKitClientPlugin | 3 | 1 | |||||||||||||||||||||||||
| 27 sourcekit-lsp | 3 | 3 |
5→15 SwiftExtensions uses SemanticIndex part of a loop✕
- Connections
- 1 pair of types, where a type in SwiftExtensions uses a type in SemanticIndex.
- The types involved
SwiftExtensions.TransitiveClosure.swift→SemanticIndex.Collection
- Direction
- SwiftExtensions uses SemanticIndex, so a change to SemanticIndex can break SwiftExtensions, while a change to SwiftExtensions can't break SemanticIndex.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
5→24 SwiftExtensions uses BuildServerIntegration part of a loop✕
- Connections
- 1 pair of types, where a type in SwiftExtensions uses a type in BuildServerIntegration.
- The types involved
SwiftExtensions.Platform→BuildServerIntegration.String
- Direction
- SwiftExtensions uses BuildServerIntegration, so a change to BuildServerIntegration can break SwiftExtensions, while a change to SwiftExtensions can't break BuildServerIntegration.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
6→9 SwiftSourceKitPluginCommon uses SourceKitD part of a loop✕
- Connections
- 2 pairs of types, where a type in SwiftSourceKitPluginCommon uses a type in SourceKitD.
- The types involved
SwiftSourceKitPluginCommon.CompletionResult→SourceKitD.sourcekitd_api_uid_tSwiftSourceKitPluginCommon.sourcekitd_api_variant_t→SourceKitD.sourcekitd_api_uid_t
- Direction
- SwiftSourceKitPluginCommon uses SourceKitD, so a change to SourceKitD can break SwiftSourceKitPluginCommon, while a change to SwiftSourceKitPluginCommon can't break SourceKitD.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
6→17 SwiftSourceKitPluginCommon uses SwiftSourceKitPlugin part of a loop✕
- Connections
- 5 pairs of types, where a type in SwiftSourceKitPluginCommon uses a type in SwiftSourceKitPlugin.
- The types involved
SwiftSourceKitPluginCommon.CompletionResult→SwiftSourceKitPlugin.BoolSwiftSourceKitPluginCommon.CompletionResult→SwiftSourceKitPlugin.Int64SwiftSourceKitPluginCommon.CompletionResultsArray→SwiftSourceKitPlugin.BoolSwiftSourceKitPluginCommon.sourcekitd_api_variant_t→SwiftSourceKitPlugin.BoolSwiftSourceKitPluginCommon.sourcekitd_api_variant_t→SwiftSourceKitPlugin.Int64
- Direction
- SwiftSourceKitPluginCommon uses SwiftSourceKitPlugin, so a change to SwiftSourceKitPlugin can break SwiftSourceKitPluginCommon, while a change to SwiftSourceKitPluginCommon can't break SwiftSourceKitPlugin.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
6→22 SwiftSourceKitPluginCommon uses ClangLanguageService part of a loop✕
- Connections
- 1 pair of types, where a type in SwiftSourceKitPluginCommon uses a type in ClangLanguageService.
- The types involved
SwiftSourceKitPluginCommon.StringEntry→ClangLanguageService.UInt32
- Direction
- SwiftSourceKitPluginCommon uses ClangLanguageService, so a change to ClangLanguageService can break SwiftSourceKitPluginCommon, while a change to SwiftSourceKitPluginCommon can't break ClangLanguageService.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
6→23 SwiftSourceKitPluginCommon uses CompletionScoring part of a loop✕
- Connections
- 4 pairs of types, where a type in SwiftSourceKitPluginCommon uses a type in CompletionScoring.
- The types involved
SwiftSourceKitPluginCommon.CompletionResult→CompletionScoring.Int32SwiftSourceKitPluginCommon.CompletionResult→CompletionScoring.UInt8SwiftSourceKitPluginCommon.CompletionResultsArray→CompletionScoring.UnsafeBufferPointerSwiftSourceKitPluginCommon.sourcekitd_api_variant_t→CompletionScoring.UInt64
- Direction
- SwiftSourceKitPluginCommon uses CompletionScoring, so a change to CompletionScoring can break SwiftSourceKitPluginCommon, while a change to SwiftSourceKitPluginCommon can't break CompletionScoring.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
7→11 SwiftSyntaxCodeActions uses SwiftLanguageService part of a loop✕
- Connections
- 48 pairs of types, where a type in SwiftSyntaxCodeActions uses a type in SwiftLanguageService. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
SwiftSyntaxCodeActions.ApplyDeMorganLaw→SwiftLanguageService.CodeActionSwiftSyntaxCodeActions.Context→SwiftLanguageService.TypeSyntaxSwiftSyntaxCodeActions.ConvertCommentToDocComment→SwiftLanguageService.TokenSyntaxSwiftSyntaxCodeActions.ConvertComputedPropertyToStored→SwiftLanguageService.VariableDeclSyntaxSwiftSyntaxCodeActions.ConvertComputedPropertyToZeroParameterFunction→SwiftLanguageService.FunctionDeclSyntaxSwiftSyntaxCodeActions.ConvertComputedPropertyToZeroParameterFunction→SwiftLanguageService.VariableDeclSyntaxSwiftSyntaxCodeActions.ConvertIfLetToGuard→SwiftLanguageService.CodeActionSwiftSyntaxCodeActions.ConvertIfLetToGuard→SwiftLanguageService.ConditionElementListSyntaxSwiftSyntaxCodeActions.ConvertIfLetToGuard→SwiftLanguageService.ConditionElementSyntaxSwiftSyntaxCodeActions.ConvertIfLetToGuard→SwiftLanguageService.GuardStmtSyntaxSwiftSyntaxCodeActions.ConvertIfLetToGuard→SwiftLanguageService.IfExprSyntaxSwiftSyntaxCodeActions.ConvertIntegerLiteral→SwiftLanguageService.CodeActionSwiftSyntaxCodeActions.ConvertStoredPropertyToComputed→SwiftLanguageService.VariableDeclSyntaxSwiftSyntaxCodeActions.ConvertStringConcatenationToStringInterpolation→SwiftLanguageService.ExprListSyntaxSwiftSyntaxCodeActions.ConvertZeroParameterFunctionToComputedProperty→SwiftLanguageService.FunctionDeclSyntaxSwiftSyntaxCodeActions.ConvertZeroParameterFunctionToComputedProperty→SwiftLanguageService.VariableDeclSyntaxSwiftSyntaxCodeActions.DeMorganTransformer→SwiftLanguageService.TokenKindSwiftSyntaxCodeActions.DeclModifierRemover→SwiftLanguageService.TokenSyntaxSwiftSyntaxCodeActions.DeclSyntax→SwiftLanguageService.TokenSyntaxSwiftSyntaxCodeActions.DeclSyntax→SwiftLanguageService.TypeSyntaxSwiftSyntaxCodeActions.ExprType→SwiftLanguageService.TokenKindSwiftSyntaxCodeActions.ExprType→SwiftLanguageService.TokenSyntaxSwiftSyntaxCodeActions.FormatRawStringLiteral→SwiftLanguageService.StringLiteralExprSyntaxSwiftSyntaxCodeActions.GenerateEnumCaseAccessors.swift→SwiftLanguageService.EnumCaseElementSyntaxSwiftSyntaxCodeActions.GenerateEnumCaseAccessors.swift→SwiftLanguageService.TypeSyntax
- Direction
- SwiftSyntaxCodeActions uses SwiftLanguageService, so a change to SwiftLanguageService can break SwiftSyntaxCodeActions, while a change to SwiftSyntaxCodeActions can't break SwiftLanguageService.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
7→17 SwiftSyntaxCodeActions uses SwiftSourceKitPlugin part of a loop✕
- Connections
- 15 pairs of types, where a type in SwiftSyntaxCodeActions uses a type in SwiftSourceKitPlugin.
- The types involved
SwiftSyntaxCodeActions.ConvertCommentToDocComment→SwiftSourceKitPlugin.BoolSwiftSyntaxCodeActions.ConvertIfLetToGuard→SwiftSourceKitPlugin.BoolSwiftSyntaxCodeActions.ConvertIfLetToGuard.swift→SwiftSourceKitPlugin.BoolSwiftSyntaxCodeActions.DeMorganTransformer→SwiftSourceKitPlugin.BoolSwiftSyntaxCodeActions.ExprSyntax→SwiftSourceKitPlugin.BoolSwiftSyntaxCodeActions.GenerateEnumCaseAccessors.swift→SwiftSourceKitPlugin.BoolSwiftSyntaxCodeActions.IndentationRemover→SwiftSourceKitPlugin.BoolSwiftSyntaxCodeActions.InlineVariable→SwiftSourceKitPlugin.BoolSwiftSyntaxCodeActions.RemoveRedundantParentheses→SwiftSourceKitPlugin.BoolSwiftSyntaxCodeActions.ResolveSupportProperties→SwiftSourceKitPlugin.BoolSwiftSyntaxCodeActions.SyntaxCodeActionProvider.swift→SwiftSourceKitPlugin.PositionSwiftSyntaxCodeActions.TargetNodeFinder→SwiftSourceKitPlugin.BoolSwiftSyntaxCodeActions.ToggleTestDisabled→SwiftSourceKitPlugin.BoolSwiftSyntaxCodeActions.Trivia→SwiftSourceKitPlugin.BoolSwiftSyntaxCodeActions.UnresolvedData→SwiftSourceKitPlugin.Position
- Direction
- SwiftSyntaxCodeActions uses SwiftSourceKitPlugin, so a change to SwiftSourceKitPlugin can break SwiftSyntaxCodeActions, while a change to SwiftSyntaxCodeActions can't break SwiftSourceKitPlugin.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
7→19 SwiftSyntaxCodeActions uses Diagnose part of a loop✕
- Connections
- 3 pairs of types, where a type in SwiftSyntaxCodeActions uses a type in Diagnose.
- The types involved
SwiftSyntaxCodeActions.IndentationRemover→Diagnose.TriviaPieceSwiftSyntaxCodeActions.SyntaxCodeActionProvider.swift→Diagnose.SourceFileSyntaxSwiftSyntaxCodeActions.SyntaxCodeActionScope→Diagnose.SourceFileSyntax
- Direction
- SwiftSyntaxCodeActions uses Diagnose, so a change to Diagnose can break SwiftSyntaxCodeActions, while a change to SwiftSyntaxCodeActions can't break Diagnose.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
7→20 SwiftSyntaxCodeActions uses SourceKitLSP part of a loop✕
- Connections
- 13 pairs of types, where a type in SwiftSyntaxCodeActions uses a type in SourceKitLSP.
- The types involved
SwiftSyntaxCodeActions.AddDocumentation→SourceKitLSP.SourceEditSwiftSyntaxCodeActions.AddExplicitEnumRawValues→SourceKitLSP.SourceEditSwiftSyntaxCodeActions.ConvertJSONToCodableStruct→SourceKitLSP.SourceEditSwiftSyntaxCodeActions.DeMorganCandidateSequence→SourceKitLSP.DocumentSnapshotSwiftSyntaxCodeActions.DeMorganCandidateSequence→SourceKitLSP.SequenceSwiftSyntaxCodeActions.GenerateEnumCaseAccessors.swift→SourceKitLSP.SourceEditSwiftSyntaxCodeActions.GenerateEnumCaseAsAccessors→SourceKitLSP.SourceEditSwiftSyntaxCodeActions.GenerateEnumCaseIsAccessors→SourceKitLSP.SourceEditSwiftSyntaxCodeActions.InlineVariable→SourceKitLSP.SourceEditSwiftSyntaxCodeActions.SwapBinaryOperands→SourceKitLSP.SourceEditSwiftSyntaxCodeActions.SyntaxCodeActionProvider.swift→SourceKitLSP.DocumentSnapshotSwiftSyntaxCodeActions.SyntaxCodeActionScope→SourceKitLSP.DocumentSnapshotSwiftSyntaxCodeActions.ToggleTestDisabled→SourceKitLSP.SourceEdit
- Direction
- SwiftSyntaxCodeActions uses SourceKitLSP, so a change to SourceKitLSP can break SwiftSyntaxCodeActions, while a change to SwiftSyntaxCodeActions can't break SourceKitLSP.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
7→24 SwiftSyntaxCodeActions uses BuildServerIntegration part of a loop✕
- Connections
- 31 pairs of types, where a type in SwiftSyntaxCodeActions uses a type in BuildServerIntegration. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
SwiftSyntaxCodeActions.AddDocumentation→BuildServerIntegration.StringSwiftSyntaxCodeActions.AddExplicitEnumRawValues→BuildServerIntegration.StringSwiftSyntaxCodeActions.AddSeparatorsToIntegerLiteral→BuildServerIntegration.StringSwiftSyntaxCodeActions.ConvertCommentToDocComment→BuildServerIntegration.StringSwiftSyntaxCodeActions.ConvertComputedPropertyToStored→BuildServerIntegration.StringSwiftSyntaxCodeActions.ConvertComputedPropertyToZeroParameterFunction→BuildServerIntegration.StringSwiftSyntaxCodeActions.ConvertJSONToCodableStruct→BuildServerIntegration.StringSwiftSyntaxCodeActions.ConvertStoredPropertyToComputed→BuildServerIntegration.StringSwiftSyntaxCodeActions.ConvertStringConcatenationToStringInterpolation→BuildServerIntegration.StringSwiftSyntaxCodeActions.ConvertZeroParameterFunctionToComputedProperty→BuildServerIntegration.StringSwiftSyntaxCodeActions.ExprSyntax→BuildServerIntegration.StringSwiftSyntaxCodeActions.FormatRawStringLiteral→BuildServerIntegration.StringSwiftSyntaxCodeActions.GenerateEnumCaseAccessors.swift→BuildServerIntegration.StringSwiftSyntaxCodeActions.GenerateEnumCaseAsAccessors→BuildServerIntegration.StringSwiftSyntaxCodeActions.GenerateEnumCaseIsAccessors→BuildServerIntegration.StringSwiftSyntaxCodeActions.IndentationRemover→BuildServerIntegration.StringSwiftSyntaxCodeActions.InlineVariable→BuildServerIntegration.StringSwiftSyntaxCodeActions.InvertIfCondition→BuildServerIntegration.StringSwiftSyntaxCodeActions.JSONObject→BuildServerIntegration.StringSwiftSyntaxCodeActions.JSONType→BuildServerIntegration.StringSwiftSyntaxCodeActions.MigrateToNewIfLetSyntax→BuildServerIntegration.StringSwiftSyntaxCodeActions.OpaqueParameterToGeneric→BuildServerIntegration.StringSwiftSyntaxCodeActions.PackageManifestEdits→BuildServerIntegration.StringSwiftSyntaxCodeActions.RemoveRedundantParentheses→BuildServerIntegration.StringSwiftSyntaxCodeActions.RemoveSeparatorsFromIntegerLiteral→BuildServerIntegration.String
- Direction
- SwiftSyntaxCodeActions uses BuildServerIntegration, so a change to BuildServerIntegration can break SwiftSyntaxCodeActions, while a change to SwiftSyntaxCodeActions can't break BuildServerIntegration.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
8→17 TSCExtensions uses SwiftSourceKitPlugin part of a loop✕
- Connections
- 1 pair of types, where a type in TSCExtensions uses a type in SwiftSourceKitPlugin.
- The types involved
TSCExtensions.SwitchableProcessResultExitStatus→SwiftSourceKitPlugin.Bool
- Direction
- TSCExtensions uses SwiftSourceKitPlugin, so a change to SwiftSourceKitPlugin can break TSCExtensions, while a change to TSCExtensions can't break SwiftSourceKitPlugin.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
8→23 TSCExtensions uses CompletionScoring part of a loop✕
- Connections
- 1 pair of types, where a type in TSCExtensions uses a type in CompletionScoring.
- The types involved
TSCExtensions.TaskPriority→CompletionScoring.Int32
- Direction
- TSCExtensions uses CompletionScoring, so a change to CompletionScoring can break TSCExtensions, while a change to TSCExtensions can't break CompletionScoring.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
8→24 TSCExtensions uses BuildServerIntegration part of a loop✕
- Connections
- 1 pair of types, where a type in TSCExtensions uses a type in BuildServerIntegration.
- The types involved
TSCExtensions.SwitchableProcessResultExitStatus→BuildServerIntegration.String
- Direction
- TSCExtensions uses BuildServerIntegration, so a change to BuildServerIntegration can break TSCExtensions, while a change to TSCExtensions can't break BuildServerIntegration.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
9→5 SourceKitD uses SwiftExtensions✕
- Connections
- 1 pair of types, where a type in SourceKitD uses a type in SwiftExtensions.
- The types involved
SourceKitD.SourceKitD→SwiftExtensions.Result
- Direction
- SourceKitD uses SwiftExtensions, so a change to SwiftExtensions can break SourceKitD, while a change to SourceKitD can't break SwiftExtensions.
- Position
- Below the diagonal: SourceKitD uses a module listed above it, which is the healthy direction.
9→6 SourceKitD uses SwiftSourceKitPluginCommon✕
- Connections
- 2 pairs of types, where a type in SourceKitD uses a type in SwiftSourceKitPluginCommon.
- The types involved
SourceKitD.SKDResponseArray→SwiftSourceKitPluginCommon.sourcekitd_api_variant_tSourceKitD.SKDResponseDictionary→SwiftSourceKitPluginCommon.sourcekitd_api_variant_t
- Direction
- SourceKitD uses SwiftSourceKitPluginCommon, so a change to SwiftSourceKitPluginCommon can break SourceKitD, while a change to SourceKitD can't break SwiftSourceKitPluginCommon.
- Position
- Below the diagonal: SourceKitD uses a module listed above it, which is the healthy direction.
9→17 SourceKitD uses SwiftSourceKitPlugin part of a loop✕
- Connections
- 8 pairs of types, where a type in SourceKitD uses a type in SwiftSourceKitPlugin.
- The types involved
SourceKitD.SKDResponseArray→SwiftSourceKitPlugin.BoolSourceKitD.SourceKitD→SwiftSourceKitPlugin.BoolSourceKitD.SourceKitD→SwiftSourceKitPlugin.SKDResponseArrayBuilderSourceKitD.SourceKitD→SwiftSourceKitPlugin.SKDResponseDictionaryBuilderSourceKitD.SourceKitD→SwiftSourceKitPlugin.SKDResponseValueSourceKitD.SourceKitD.swift→SwiftSourceKitPlugin.BoolSourceKitD.sourcekitd_api_uid_t→SwiftSourceKitPlugin.BoolSourceKitD.sourcekitd_api_uid_t→SwiftSourceKitPlugin.ItemKind
- Direction
- SourceKitD uses SwiftSourceKitPlugin, so a change to SwiftSourceKitPlugin can break SourceKitD, while a change to SourceKitD can't break SwiftSourceKitPlugin.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
9→20 SourceKitD uses SourceKitLSP part of a loop✕
- Connections
- 1 pair of types, where a type in SourceKitD uses a type in SourceKitLSP.
- The types involved
SourceKitD.SKDRequestArray→SourceKitLSP.Sequence
- Direction
- SourceKitD uses SourceKitLSP, so a change to SourceKitLSP can break SourceKitD, while a change to SourceKitD can't break SourceKitLSP.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
9→23 SourceKitD uses CompletionScoring part of a loop✕
- Connections
- 1 pair of types, where a type in SourceKitD uses a type in CompletionScoring.
- The types involved
SourceKitD.DLOpenFlags→CompletionScoring.Int32
- Direction
- SourceKitD uses CompletionScoring, so a change to CompletionScoring can break SourceKitD, while a change to SourceKitD can't break CompletionScoring.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
9→24 SourceKitD uses BuildServerIntegration part of a loop✕
- Connections
- 17 pairs of types, where a type in SourceKitD uses a type in BuildServerIntegration.
- The types involved
SourceKitD.ContextualRequest→BuildServerIntegration.KindSourceKitD.DLError→BuildServerIntegration.ErrorSourceKitD.PluginPaths→BuildServerIntegration.StringSourceKitD.PluginPaths→BuildServerIntegration.URLSourceKitD.SKDError→BuildServerIntegration.ErrorSourceKitD.SKDRequestArray→BuildServerIntegration.StringSourceKitD.SKDRequestDictionary→BuildServerIntegration.StringSourceKitD.SKDResponse→BuildServerIntegration.StringSourceKitD.SKDResponseArray→BuildServerIntegration.StringSourceKitD.SKDResponseDictionary→BuildServerIntegration.StringSourceKitD.SourceKitD→BuildServerIntegration.StringSourceKitD.SourceKitD→BuildServerIntegration.URLSourceKitD.SourceKitD.swift→BuildServerIntegration.StringSourceKitD.SourceKitDCore→BuildServerIntegration.URLSourceKitD.SourceKitDCoreImpl→BuildServerIntegration.URLSourceKitD.SourceKitDRegistry→BuildServerIntegration.URLSourceKitD.dlopen.swift→BuildServerIntegration.String
- Direction
- SourceKitD uses BuildServerIntegration, so a change to BuildServerIntegration can break SourceKitD, while a change to SourceKitD can't break BuildServerIntegration.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
10→9 ToolchainRegistry uses SourceKitD✕
- Connections
- 2 pairs of types, where a type in ToolchainRegistry uses a type in SourceKitD.
- The types involved
ToolchainRegistry.Toolchain→SourceKitD.MutexToolchainRegistry.Toolchain→SourceKitD.PluginPaths
- Direction
- ToolchainRegistry uses SourceKitD, so a change to SourceKitD can break ToolchainRegistry, while a change to ToolchainRegistry can't break SourceKitD.
- Position
- Below the diagonal: ToolchainRegistry uses a module listed above it, which is the healthy direction.
10→17 ToolchainRegistry uses SwiftSourceKitPlugin part of a loop✕
- Connections
- 3 pairs of types, where a type in ToolchainRegistry uses a type in SwiftSourceKitPlugin.
- The types involved
ToolchainRegistry.SwiftVersion→SwiftSourceKitPlugin.BoolToolchainRegistry.Toolchain→SwiftSourceKitPlugin.BoolToolchainRegistry.ToolchainRegistry→SwiftSourceKitPlugin.Bool
- Direction
- ToolchainRegistry uses SwiftSourceKitPlugin, so a change to SwiftSourceKitPlugin can break ToolchainRegistry, while a change to ToolchainRegistry can't break SwiftSourceKitPlugin.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
10→23 ToolchainRegistry uses CompletionScoring part of a loop✕
- Connections
- 2 pairs of types, where a type in ToolchainRegistry uses a type in CompletionScoring.
- The types involved
ToolchainRegistry.SwiftVersion→CompletionScoring.ComparableToolchainRegistry.ToolchainRegisterReason→CompletionScoring.Comparable
- Direction
- ToolchainRegistry uses CompletionScoring, so a change to CompletionScoring can break ToolchainRegistry, while a change to ToolchainRegistry can't break CompletionScoring.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
10→24 ToolchainRegistry uses BuildServerIntegration part of a loop✕
- Connections
- 10 pairs of types, where a type in ToolchainRegistry uses a type in BuildServerIntegration.
- The types involved
ToolchainRegistry.SwiftVersion→BuildServerIntegration.StringToolchainRegistry.SwiftVersionParsingError→BuildServerIntegration.ErrorToolchainRegistry.SwiftVersionParsingError→BuildServerIntegration.StringToolchainRegistry.Toolchain→BuildServerIntegration.StringToolchainRegistry.Toolchain→BuildServerIntegration.URLToolchainRegistry.Toolchain.swift→BuildServerIntegration.URLToolchainRegistry.ToolchainRegistry→BuildServerIntegration.StringToolchainRegistry.ToolchainRegistry→BuildServerIntegration.URLToolchainRegistry.XCToolchainPlist→BuildServerIntegration.StringToolchainRegistry.XCToolchainPlist→BuildServerIntegration.URL
- Direction
- ToolchainRegistry uses BuildServerIntegration, so a change to BuildServerIntegration can break ToolchainRegistry, while a change to ToolchainRegistry can't break BuildServerIntegration.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
11→3 SwiftLanguageService uses SwiftSyntaxExtensions✕
- Connections
- 1 pair of types, where a type in SwiftLanguageService uses a type in SwiftSyntaxExtensions.
- The types involved
SwiftLanguageService.FunctionCallExprSyntax→SwiftSyntaxExtensions.SwiftTestingDisabledTrait
- Direction
- SwiftLanguageService uses SwiftSyntaxExtensions, so a change to SwiftSyntaxExtensions can break SwiftLanguageService, while a change to SwiftLanguageService can't break SwiftSyntaxExtensions.
- Position
- Below the diagonal: SwiftLanguageService uses a module listed above it, which is the healthy direction.
11→7 SwiftLanguageService uses SwiftSyntaxCodeActions✕
- Connections
- 14 pairs of types, where a type in SwiftLanguageService uses a type in SwiftSyntaxCodeActions.
- The types involved
SwiftLanguageService.CodeCompletionSession→SwiftSyntaxCodeActions.TriviaSwiftLanguageService.DocumentSymbolsFinder→SwiftSyntaxCodeActions.SyntaxSwiftLanguageService.DocumentSymbolsFinder→SwiftSyntaxCodeActions.TriviaSwiftLanguageService.FoldingRangeFinder→SwiftSyntaxCodeActions.SyntaxSwiftLanguageService.FoldingRangeFinder→SwiftSyntaxCodeActions.TriviaSwiftLanguageService.OutermostFunctionCallFinder→SwiftSyntaxCodeActions.SyntaxSwiftLanguageService.SelectionRange.swift→SwiftSyntaxCodeActions.SyntaxSwiftLanguageService.StartOfArgumentFinder→SwiftSyntaxCodeActions.SyntaxSwiftLanguageService.StartOfIdentifierFinder→SwiftSyntaxCodeActions.SyntaxSwiftLanguageService.SwiftLanguageService→SwiftSyntaxCodeActions.TriviaSwiftLanguageService.SwiftTestingScanner.swift→SwiftSyntaxCodeActions.ExprSyntaxSwiftLanguageService.SyntacticSwiftTestingTestScanner→SwiftSyntaxCodeActions.EnumDeclSyntaxSwiftLanguageService.TokenSyntax→SwiftSyntaxCodeActions.TriviaSwiftLanguageService.TupleExprSyntax→SwiftSyntaxCodeActions.ExprSyntax
- Direction
- SwiftLanguageService uses SwiftSyntaxCodeActions, so a change to SwiftSyntaxCodeActions can break SwiftLanguageService, while a change to SwiftLanguageService can't break SwiftSyntaxCodeActions.
- Position
- Below the diagonal: SwiftLanguageService uses a module listed above it, which is the healthy direction.
11→9 SwiftLanguageService uses SourceKitD✕
- Connections
- 47 pairs of types, where a type in SwiftLanguageService uses a type in SourceKitD. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
SwiftLanguageService.CodeAction→SourceKitD.SKDResponseArraySwiftLanguageService.CodeCompletionSession→SourceKitD.SKDRequestDictionarySwiftLanguageService.CodeCompletionSession→SourceKitD.SKDResponseArraySwiftLanguageService.CodeCompletionSession→SourceKitD.SKDResponseDictionarySwiftLanguageService.CodeCompletionSession→SourceKitD.SourceKitDSwiftLanguageService.CodeCompletionSession→SourceKitD.sourcekitd_api_keysSwiftLanguageService.CursorInfo→SourceKitD.SKDResponseDictionarySwiftLanguageService.CursorInfo→SourceKitD.SourceKitDSwiftLanguageService.Diagnostic→SourceKitD.SKDResponseDictionarySwiftLanguageService.DiagnosticRelatedInformation→SourceKitD.SKDResponseDictionarySwiftLanguageService.DiagnosticReportManager→SourceKitD.SourceKitDSwiftLanguageService.DiagnosticReportManager→SourceKitD.sourcekitd_api_keysSwiftLanguageService.DiagnosticReportManager→SourceKitD.sourcekitd_api_requestsSwiftLanguageService.DiagnosticStage→SourceKitD.SourceKitDSwiftLanguageService.DiagnosticStage→SourceKitD.sourcekitd_api_uid_tSwiftLanguageService.ParameterInformation→SourceKitD.SKDResponseDictionarySwiftLanguageService.ParameterInformation→SourceKitD.sourcekitd_api_keysSwiftLanguageService.RefactoringEdit→SourceKitD.SKDResponseDictionarySwiftLanguageService.RefactoringEdit→SourceKitD.sourcekitd_api_keysSwiftLanguageService.RefactoringResponse→SourceKitD.SKDResponseDictionarySwiftLanguageService.RefactoringResponse→SourceKitD.sourcekitd_api_keysSwiftLanguageService.SignatureHelp→SourceKitD.SKDResponseDictionarySwiftLanguageService.SignatureHelp→SourceKitD.sourcekitd_api_keysSwiftLanguageService.SignatureInformation→SourceKitD.SKDResponseDictionarySwiftLanguageService.SignatureInformation→SourceKitD.sourcekitd_api_keys
- Direction
- SwiftLanguageService uses SourceKitD, so a change to SourceKitD can break SwiftLanguageService, while a change to SwiftLanguageService can't break SourceKitD.
- Position
- Below the diagonal: SwiftLanguageService uses a module listed above it, which is the healthy direction.
11→10 SwiftLanguageService uses ToolchainRegistry✕
- Connections
- 2 pairs of types, where a type in SwiftLanguageService uses a type in ToolchainRegistry.
- The types involved
SwiftLanguageService.SwiftCodeLensScanner→ToolchainRegistry.ToolchainSwiftLanguageService.SwiftLanguageService→ToolchainRegistry.Toolchain
- Direction
- SwiftLanguageService uses ToolchainRegistry, so a change to ToolchainRegistry can break SwiftLanguageService, while a change to SwiftLanguageService can't break ToolchainRegistry.
- Position
- Below the diagonal: SwiftLanguageService uses a module listed above it, which is the healthy direction.
11→13 SwiftLanguageService uses SKTestSupport part of a loop✕
- Connections
- 6 pairs of types, where a type in SwiftLanguageService uses a type in SKTestSupport.
- The types involved
SwiftLanguageService.ExpandMacroCommand→SKTestSupport.TextDocumentIdentifierSwiftLanguageService.RemoveUnusedImportsCommand→SKTestSupport.TextDocumentIdentifierSwiftLanguageService.SemanticRefactorCommand→SKTestSupport.TextDocumentIdentifierSwiftLanguageService.SwiftLanguageService→SKTestSupport.DocumentDiagnosticReportSwiftLanguageService.SwiftLanguageService→SKTestSupport.LocationsOrLocationLinksResponseSwiftLanguageService.SwiftLanguageService→SKTestSupport.TextDocumentIdentifier
- Direction
- SwiftLanguageService uses SKTestSupport, so a change to SKTestSupport can break SwiftLanguageService, while a change to SwiftLanguageService can't break SKTestSupport.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
11→15 SwiftLanguageService uses SemanticIndex part of a loop✕
- Connections
- 3 pairs of types, where a type in SwiftLanguageService uses a type in SemanticIndex.
- The types involved
SwiftLanguageService.CodeCompletionSession→SemanticIndex.StateSwiftLanguageService.DiagnosticReportManager→SemanticIndex.CheckedIndexSwiftLanguageService.DiagnosticReportManager→SemanticIndex.UncheckedIndex
- Direction
- SwiftLanguageService uses SemanticIndex, so a change to SemanticIndex can break SwiftLanguageService, while a change to SwiftLanguageService can't break SemanticIndex.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
11→16 SwiftLanguageService uses SKUtilities part of a loop✕
- Connections
- 4 pairs of types, where a type in SwiftLanguageService uses a type in SKUtilities.
- The types involved
SwiftLanguageService.DiagnosticReportManager→SKUtilities.LRUCacheSwiftLanguageService.InlayHintManager→SKUtilities.LRUCacheSwiftLanguageService.MacroExpansionManager→SKUtilities.LRUCacheSwiftLanguageService.SwiftLanguageService→SKUtilities.Debouncer
- Direction
- SwiftLanguageService uses SKUtilities, so a change to SKUtilities can break SwiftLanguageService, while a change to SwiftLanguageService can't break SKUtilities.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
11→17 SwiftLanguageService uses SwiftSourceKitPlugin part of a loop✕
- Connections
- 43 pairs of types, where a type in SwiftLanguageService uses a type in SwiftSourceKitPlugin. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
SwiftLanguageService.AttributeSyntax→SwiftSourceKitPlugin.BoolSwiftLanguageService.ClosureCompletionFormat→SwiftSourceKitPlugin.BoolSwiftLanguageService.CodeAction→SwiftSourceKitPlugin.TextEditSwiftLanguageService.CodeCompletionContext.swift→SwiftSourceKitPlugin.PositionSwiftLanguageService.CodeCompletionSession→SwiftSourceKitPlugin.BoolSwiftLanguageService.CodeCompletionSession→SwiftSourceKitPlugin.CompletionItemSwiftLanguageService.CodeCompletionSession→SwiftSourceKitPlugin.PositionSwiftLanguageService.CompletionRequestContext→SwiftSourceKitPlugin.PositionSwiftLanguageService.Diagnostic→SwiftSourceKitPlugin.BoolSwiftLanguageService.DiagnosticReportManager→SwiftSourceKitPlugin.BoolSwiftLanguageService.DocumentFormatting.swift→SwiftSourceKitPlugin.TextEditSwiftLanguageService.FoldingRangeFinder→SwiftSourceKitPlugin.BoolSwiftLanguageService.FunctionDeclSyntax→SwiftSourceKitPlugin.BoolSwiftLanguageService.GeneratedInterfaceManager→SwiftSourceKitPlugin.BoolSwiftLanguageService.GeneratedInterfaceManager→SwiftSourceKitPlugin.PositionSwiftLanguageService.InFlightInlayHintRefreshTask→SwiftSourceKitPlugin.BoolSwiftLanguageService.InlayHintCacheEntry→SwiftSourceKitPlugin.BoolSwiftLanguageService.InlayHintManager→SwiftSourceKitPlugin.BoolSwiftLanguageService.InlayHintResolveData→SwiftSourceKitPlugin.PositionSwiftLanguageService.OutermostFunctionCallFinder→SwiftSourceKitPlugin.BoolSwiftLanguageService.Range→SwiftSourceKitPlugin.BoolSwiftLanguageService.RewriteSourceKitPlaceholders.swift→SwiftSourceKitPlugin.BoolSwiftLanguageService.SignatureInformation→SwiftSourceKitPlugin.BoolSwiftLanguageService.StringLiteralExprSyntax→SwiftSourceKitPlugin.BoolSwiftLanguageService.SwiftCompileCommand→SwiftSourceKitPlugin.Bool
- Direction
- SwiftLanguageService uses SwiftSourceKitPlugin, so a change to SwiftSourceKitPlugin can break SwiftLanguageService, while a change to SwiftLanguageService can't break SwiftSourceKitPlugin.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
11→18 SwiftLanguageService uses SKOptions part of a loop✕
- Connections
- 3 pairs of types, where a type in SwiftLanguageService uses a type in SKOptions.
- The types involved
SwiftLanguageService.CodeCompletionSession→SKOptions.SourceKitLSPOptionsSwiftLanguageService.DiagnosticReportManager→SKOptions.SourceKitLSPOptionsSwiftLanguageService.SwiftLanguageService→SKOptions.SourceKitLSPOptions
- Direction
- SwiftLanguageService uses SKOptions, so a change to SKOptions can break SwiftLanguageService, while a change to SwiftLanguageService can't break SKOptions.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
11→19 SwiftLanguageService uses Diagnose part of a loop✕
- Connections
- 8 pairs of types, where a type in SwiftLanguageService uses a type in Diagnose.
- The types involved
SwiftLanguageService.CacheKey→Diagnose.IDSwiftLanguageService.CodeCompletionContext.swift→Diagnose.SourceFileSyntaxSwiftLanguageService.CompletionRequestContext→Diagnose.SourceFileSyntaxSwiftLanguageService.DiagnosticReportManager→Diagnose.IDSwiftLanguageService.DiagnosticReportManager→Diagnose.SourceFileSyntaxSwiftLanguageService.DocumentableSymbol→Diagnose.SourceFileSyntaxSwiftLanguageService.SelectionRange.swift→Diagnose.SourceFileSyntaxSwiftLanguageService.VariableTypeInfo→Diagnose.SourceFileSyntax
- Direction
- SwiftLanguageService uses Diagnose, so a change to Diagnose can break SwiftLanguageService, while a change to SwiftLanguageService can't break Diagnose.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
11→20 SwiftLanguageService uses SourceKitLSP part of a loop✕
- Connections
- 71 pairs of types, where a type in SwiftLanguageService uses a type in SourceKitLSP. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
SwiftLanguageService.CodeAction→SourceKitLSP.DocumentSnapshotSwiftLanguageService.CodeCompletionContext.swift→SourceKitLSP.DocumentSnapshotSwiftLanguageService.CodeCompletionSession→SourceKitLSP.DocumentSnapshotSwiftLanguageService.CompletionRequestContext→SourceKitLSP.DocumentSnapshotSwiftLanguageService.CursorInfo→SourceKitLSP.DocumentManagerSwiftLanguageService.CursorInfo→SourceKitLSP.DocumentSnapshotSwiftLanguageService.Diagnostic→SourceKitLSP.DocumentManagerSwiftLanguageService.Diagnostic→SourceKitLSP.DocumentSnapshotSwiftLanguageService.DiagnosticRelatedInformation→SourceKitLSP.DocumentManagerSwiftLanguageService.DiagnosticRelatedInformation→SourceKitLSP.DocumentSnapshotSwiftLanguageService.DiagnosticReportManager→SourceKitLSP.DocumentManagerSwiftLanguageService.DiagnosticReportManager→SourceKitLSP.DocumentSnapshotSwiftLanguageService.DiagnosticReportManager→SourceKitLSP.SyntaxTreeManagerSwiftLanguageService.DocumentFormatting.swift→SourceKitLSP.DocumentSnapshotSwiftLanguageService.DocumentSymbolsFinder→SourceKitLSP.DocumentSnapshotSwiftLanguageService.DocumentSymbolsFinder→SourceKitLSP.SequenceSwiftLanguageService.FoldingRangeFinder→SourceKitLSP.DocumentSnapshotSwiftLanguageService.GeneratedInterfaceManager→SourceKitLSP.DocumentSnapshotSwiftLanguageService.GeneratedInterfaceManager→SourceKitLSP.GeneratedInterfaceDocumentURLDataSwiftLanguageService.InlayHintManager→SourceKitLSP.DocumentSnapshotSwiftLanguageService.InlayHintManager→SourceKitLSP.HooksSwiftLanguageService.MacroExpansionManager→SourceKitLSP.DocumentSnapshotSwiftLanguageService.MacroExpansionManager→SourceKitLSP.MacroExpansionReferenceDocumentURLDataSwiftLanguageService.OpenGeneratedInterfaceDocumentDetails→SourceKitLSP.DocumentSnapshotSwiftLanguageService.OpenGeneratedInterfaceDocumentDetails→SourceKitLSP.GeneratedInterfaceDocumentURLData
- Direction
- SwiftLanguageService uses SourceKitLSP, so a change to SourceKitLSP can break SwiftLanguageService, while a change to SwiftLanguageService can't break SourceKitLSP.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
11→21 SwiftLanguageService uses LanguageServerProtocolExtensions part of a loop✕
- Connections
- 12 pairs of types, where a type in SwiftLanguageService uses a type in LanguageServerProtocolExtensions.
- The types involved
SwiftLanguageService.CodeCompletionSession→LanguageServerProtocolExtensions.DocumentURISwiftLanguageService.CompletionItemData→LanguageServerProtocolExtensions.DocumentURISwiftLanguageService.DiagnosticReportManager→LanguageServerProtocolExtensions.DocumentURISwiftLanguageService.DocumentFormatting.swift→LanguageServerProtocolExtensions.DocumentURISwiftLanguageService.GeneratedInterfaceManager→LanguageServerProtocolExtensions.DocumentURISwiftLanguageService.InlayHintManager→LanguageServerProtocolExtensions.DocumentURISwiftLanguageService.InlayHintResolveData→LanguageServerProtocolExtensions.DocumentURISwiftLanguageService.MacroExpansionManager→LanguageServerProtocolExtensions.DocumentURISwiftLanguageService.RefactoringResponse→LanguageServerProtocolExtensions.DocumentURISwiftLanguageService.SemanticRefactoring→LanguageServerProtocolExtensions.DocumentURISwiftLanguageService.SwiftLanguageService→LanguageServerProtocolExtensions.DocumentURISwiftLanguageService.SwiftLanguageService.swift→LanguageServerProtocolExtensions.DocumentURI
- Direction
- SwiftLanguageService uses LanguageServerProtocolExtensions, so a change to LanguageServerProtocolExtensions can break SwiftLanguageService, while a change to SwiftLanguageService can't break LanguageServerProtocolExtensions.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
11→22 SwiftLanguageService uses ClangLanguageService part of a loop✕
- Connections
- 2 pairs of types, where a type in SwiftLanguageService uses a type in ClangLanguageService.
- The types involved
SwiftLanguageService.CompletionSessionID→ClangLanguageService.UInt32SwiftLanguageService.SyntaxHighlightingTokens→ClangLanguageService.UInt32
- Direction
- SwiftLanguageService uses ClangLanguageService, so a change to ClangLanguageService can break SwiftLanguageService, while a change to SwiftLanguageService can't break ClangLanguageService.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
11→24 SwiftLanguageService uses BuildServerIntegration part of a loop✕
- Connections
- 50 pairs of types, where a type in SwiftLanguageService uses a type in BuildServerIntegration. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
SwiftLanguageService.AnnotatedCompletionText.swift→BuildServerIntegration.StringSwiftLanguageService.AnnotatedCompletionTextParserDelegate→BuildServerIntegration.StringSwiftLanguageService.AttributeSyntax→BuildServerIntegration.StringSwiftLanguageService.CodeAction→BuildServerIntegration.StringSwiftLanguageService.CodeCompletionSession→BuildServerIntegration.StringSwiftLanguageService.CommentXML.swift→BuildServerIntegration.StringSwiftLanguageService.CommentXMLError→BuildServerIntegration.ErrorSwiftLanguageService.CompoundDeclName→BuildServerIntegration.StringSwiftLanguageService.CursorInfo→BuildServerIntegration.StringSwiftLanguageService.CursorInfoError→BuildServerIntegration.ErrorSwiftLanguageService.CursorInfoError→BuildServerIntegration.StringSwiftLanguageService.DiagnosticReportManager→BuildServerIntegration.StringSwiftLanguageService.DocumentFormatting.swift→BuildServerIntegration.AbsolutePathSwiftLanguageService.DocumentFormatting.swift→BuildServerIntegration.StringSwiftLanguageService.DocumentSymbolsFinder→BuildServerIntegration.StringSwiftLanguageService.DocumentableSymbol→BuildServerIntegration.StringSwiftLanguageService.EnumCaseElementSyntax→BuildServerIntegration.StringSwiftLanguageService.ExpandMacroCommand→BuildServerIntegration.StringSwiftLanguageService.FunctionCallExprSyntax→BuildServerIntegration.StringSwiftLanguageService.FunctionDeclSyntax→BuildServerIntegration.StringSwiftLanguageService.GeneratedInterfaceManager→BuildServerIntegration.StringSwiftLanguageService.InitializerDeclSyntax→BuildServerIntegration.StringSwiftLanguageService.InlayHint→BuildServerIntegration.StringSwiftLanguageService.MacroExpansionManager→BuildServerIntegration.StringSwiftLanguageService.MemberAccessExprSyntax→BuildServerIntegration.String
- Direction
- SwiftLanguageService uses BuildServerIntegration, so a change to BuildServerIntegration can break SwiftLanguageService, while a change to SwiftLanguageService can't break BuildServerIntegration.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
12→7 SourceKitLSPDevUtils~ConfigSchemaGen uses SwiftSyntaxCodeActions✕
- Connections
- 3 pairs of types, where a type in SourceKitLSPDevUtils~ConfigSchemaGen uses a type in SwiftSyntaxCodeActions.
- The types involved
SourceKitLSPDevUtils~ConfigSchemaGen.OptionSchemaContext→SwiftSyntaxCodeActions.EnumDeclSyntaxSourceKitLSPDevUtils~ConfigSchemaGen.OptionSchemaContext→SwiftSyntaxCodeActions.TriviaSourceKitLSPDevUtils~ConfigSchemaGen.TypeDeclCollector→SwiftSyntaxCodeActions.EnumDeclSyntax
- Direction
- SourceKitLSPDevUtils~ConfigSchemaGen uses SwiftSyntaxCodeActions, so a change to SwiftSyntaxCodeActions can break SourceKitLSPDevUtils~ConfigSchemaGen, while a change to SourceKitLSPDevUtils~ConfigSchemaGen can't break SwiftSyntaxCodeActions.
- Position
- Below the diagonal: SourceKitLSPDevUtils~ConfigSchemaGen uses a module listed above it, which is the healthy direction.
12→11 SourceKitLSPDevUtils~ConfigSchemaGen uses SwiftLanguageService✕
- Connections
- 1 pair of types, where a type in SourceKitLSPDevUtils~ConfigSchemaGen uses a type in SwiftLanguageService.
- The types involved
SourceKitLSPDevUtils~ConfigSchemaGen.OptionSchemaContext→SwiftLanguageService.TypeSyntax
- Direction
- SourceKitLSPDevUtils~ConfigSchemaGen uses SwiftLanguageService, so a change to SwiftLanguageService can break SourceKitLSPDevUtils~ConfigSchemaGen, while a change to SourceKitLSPDevUtils~ConfigSchemaGen can't break SwiftLanguageService.
- Position
- Below the diagonal: SourceKitLSPDevUtils~ConfigSchemaGen uses a module listed above it, which is the healthy direction.
12→17 SourceKitLSPDevUtils~ConfigSchemaGen uses SwiftSourceKitPlugin part of a loop✕
- Connections
- 3 pairs of types, where a type in SourceKitLSPDevUtils~ConfigSchemaGen uses a type in SwiftSourceKitPlugin.
- The types involved
SourceKitLSPDevUtils~ConfigSchemaGen.ConfigSchemaGen→SwiftSourceKitPlugin.BoolSourceKitLSPDevUtils~ConfigSchemaGen.OptionDocumentBuilder→SwiftSourceKitPlugin.BoolSourceKitLSPDevUtils~ConfigSchemaGen.OptionTypeSchama→SwiftSourceKitPlugin.Bool
- Direction
- SourceKitLSPDevUtils~ConfigSchemaGen uses SwiftSourceKitPlugin, so a change to SwiftSourceKitPlugin can break SourceKitLSPDevUtils~ConfigSchemaGen, while a change to SourceKitLSPDevUtils~ConfigSchemaGen can't break SwiftSourceKitPlugin.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
12→19 SourceKitLSPDevUtils~ConfigSchemaGen uses Diagnose part of a loop✕
- Connections
- 1 pair of types, where a type in SourceKitLSPDevUtils~ConfigSchemaGen uses a type in Diagnose.
- The types involved
SourceKitLSPDevUtils~ConfigSchemaGen.TypeDeclResolver→Diagnose.SourceFileSyntax
- Direction
- SourceKitLSPDevUtils~ConfigSchemaGen uses Diagnose, so a change to Diagnose can break SourceKitLSPDevUtils~ConfigSchemaGen, while a change to SourceKitLSPDevUtils~ConfigSchemaGen can't break Diagnose.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
12→24 SourceKitLSPDevUtils~ConfigSchemaGen uses BuildServerIntegration part of a loop✕
- Connections
- 14 pairs of types, where a type in SourceKitLSPDevUtils~ConfigSchemaGen uses a type in BuildServerIntegration.
- The types involved
SourceKitLSPDevUtils~ConfigSchemaGen.Case→BuildServerIntegration.StringSourceKitLSPDevUtils~ConfigSchemaGen.CodingKeys→BuildServerIntegration.StringSourceKitLSPDevUtils~ConfigSchemaGen.ConfigSchemaGenError→BuildServerIntegration.ErrorSourceKitLSPDevUtils~ConfigSchemaGen.ConfigSchemaGenError→BuildServerIntegration.StringSourceKitLSPDevUtils~ConfigSchemaGen.Enum→BuildServerIntegration.StringSourceKitLSPDevUtils~ConfigSchemaGen.Error→BuildServerIntegration.ErrorSourceKitLSPDevUtils~ConfigSchemaGen.JSONSchema→BuildServerIntegration.StringSourceKitLSPDevUtils~ConfigSchemaGen.OptionDocumentBuilder→BuildServerIntegration.StringSourceKitLSPDevUtils~ConfigSchemaGen.OptionSchemaContext→BuildServerIntegration.StringSourceKitLSPDevUtils~ConfigSchemaGen.OptionTypeSchama→BuildServerIntegration.KindSourceKitLSPDevUtils~ConfigSchemaGen.Property→BuildServerIntegration.StringSourceKitLSPDevUtils~ConfigSchemaGen.Struct→BuildServerIntegration.StringSourceKitLSPDevUtils~ConfigSchemaGen.WritePlan→BuildServerIntegration.StringSourceKitLSPDevUtils~ConfigSchemaGen.WritePlan→BuildServerIntegration.URL
- Direction
- SourceKitLSPDevUtils~ConfigSchemaGen uses BuildServerIntegration, so a change to BuildServerIntegration can break SourceKitLSPDevUtils~ConfigSchemaGen, while a change to SourceKitLSPDevUtils~ConfigSchemaGen can't break BuildServerIntegration.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
13→7 SKTestSupport uses SwiftSyntaxCodeActions✕
- Connections
- 1 pair of types, where a type in SKTestSupport uses a type in SwiftSyntaxCodeActions.
- The types involved
SKTestSupport.Marker→SwiftSyntaxCodeActions.Substring
- Direction
- SKTestSupport uses SwiftSyntaxCodeActions, so a change to SwiftSyntaxCodeActions can break SKTestSupport, while a change to SKTestSupport can't break SwiftSyntaxCodeActions.
- Position
- Below the diagonal: SKTestSupport uses a module listed above it, which is the healthy direction.
13→9 SKTestSupport uses SourceKitD✕
- Connections
- 4 pairs of types, where a type in SKTestSupport uses a type in SourceKitD.
- The types involved
SKTestSupport.PendingNotifications→SourceKitD.MutexSKTestSupport.PluginPaths.swift→SourceKitD.PluginPathsSKTestSupport.SkipUnless→SourceKitD.SourceKitDSKTestSupport.TestSourceKitLSPClient→SourceKitD.Mutex
- Direction
- SKTestSupport uses SourceKitD, so a change to SourceKitD can break SKTestSupport, while a change to SKTestSupport can't break SourceKitD.
- Position
- Below the diagonal: SKTestSupport uses a module listed above it, which is the healthy direction.
13→10 SKTestSupport uses ToolchainRegistry✕
- Connections
- 4 pairs of types, where a type in SKTestSupport uses a type in ToolchainRegistry.
- The types involved
SKTestSupport.MultiFileTestProject→ToolchainRegistry.ToolchainRegistrySKTestSupport.SkipUnless→ToolchainRegistry.SwiftVersionSKTestSupport.SwiftPMTestProject→ToolchainRegistry.ToolchainRegistrySKTestSupport.TestSourceKitLSPClient→ToolchainRegistry.ToolchainRegistry
- Direction
- SKTestSupport uses ToolchainRegistry, so a change to ToolchainRegistry can break SKTestSupport, while a change to SKTestSupport can't break ToolchainRegistry.
- Position
- Below the diagonal: SKTestSupport uses a module listed above it, which is the healthy direction.
13→11 SKTestSupport uses SwiftLanguageService✕
- Connections
- 2 pairs of types, where a type in SKTestSupport uses a type in SwiftLanguageService.
- The types involved
SKTestSupport.Marker→SwiftLanguageService.RangeSKTestSupport.MultiFileTestProject→SwiftLanguageService.Range
- Direction
- SKTestSupport uses SwiftLanguageService, so a change to SwiftLanguageService can break SKTestSupport, while a change to SKTestSupport can't break SwiftLanguageService.
- Position
- Below the diagonal: SKTestSupport uses a module listed above it, which is the healthy direction.
13→12 SKTestSupport uses SourceKitLSPDevUtils~ConfigSchemaGen✕
- Connections
- 1 pair of types, where a type in SKTestSupport uses a type in SourceKitLSPDevUtils~ConfigSchemaGen.
- The types involved
SKTestSupport.ConfigureLoggingTrait→SourceKitLSPDevUtils~ConfigSchemaGen.Case
- Direction
- SKTestSupport uses SourceKitLSPDevUtils~ConfigSchemaGen, so a change to SourceKitLSPDevUtils~ConfigSchemaGen can break SKTestSupport, while a change to SKTestSupport can't break SourceKitLSPDevUtils~ConfigSchemaGen.
- Position
- Below the diagonal: SKTestSupport uses a module listed above it, which is the healthy direction.
13→17 SKTestSupport uses SwiftSourceKitPlugin part of a loop✕
- Connections
- 17 pairs of types, where a type in SKTestSupport uses a type in SwiftSourceKitPlugin.
- The types involved
SKTestSupport.Assertions.swift→SwiftSourceKitPlugin.BoolSKTestSupport.CustomBuildServer→SwiftSourceKitPlugin.BoolSKTestSupport.CustomBuildServer→SwiftSourceKitPlugin.ConnectionSKTestSupport.CustomBuildServerTestProject→SwiftSourceKitPlugin.BoolSKTestSupport.DummyBuildServerManagerConnectionToClient→SwiftSourceKitPlugin.BoolSKTestSupport.ExternalBuildServerTestProject→SwiftSourceKitPlugin.BoolSKTestSupport.IndexedSingleSwiftFileTestProject→SwiftSourceKitPlugin.BoolSKTestSupport.LocationsOrLocationLinksResponse→SwiftSourceKitPlugin.LocationSKTestSupport.MultiFileTestProject→SwiftSourceKitPlugin.BoolSKTestSupport.MultiFileTestProject→SwiftSourceKitPlugin.LocationSKTestSupport.MultiFileTestProject→SwiftSourceKitPlugin.PositionSKTestSupport.PerfTestCase→SwiftSourceKitPlugin.BoolSKTestSupport.PluginPaths.swift→SwiftSourceKitPlugin.BoolSKTestSupport.SkipUnless→SwiftSourceKitPlugin.BoolSKTestSupport.SwiftPMTestProject→SwiftSourceKitPlugin.BoolSKTestSupport.TestSourceKitLSPClient→SwiftSourceKitPlugin.BoolSKTestSupport.TestSourceKitLSPClient→SwiftSourceKitPlugin.RequestHandler
- Direction
- SKTestSupport uses SwiftSourceKitPlugin, so a change to SwiftSourceKitPlugin can break SKTestSupport, while a change to SKTestSupport can't break SwiftSourceKitPlugin.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
13→18 SKTestSupport uses SKOptions part of a loop✕
- Connections
- 6 pairs of types, where a type in SKTestSupport uses a type in SKOptions.
- The types involved
SKTestSupport.CustomBuildServerTestProject→SKOptions.SourceKitLSPOptionsSKTestSupport.ExternalBuildServerTestProject→SKOptions.SourceKitLSPOptionsSKTestSupport.MultiFileTestProject→SKOptions.SourceKitLSPOptionsSKTestSupport.SwiftPMTestProject→SKOptions.SourceKitLSPOptionsSKTestSupport.SwiftPMTestProject→SKOptions.SwiftPMBuildSystemSKTestSupport.TestSourceKitLSPClient→SKOptions.SourceKitLSPOptions
- Direction
- SKTestSupport uses SKOptions, so a change to SKOptions can break SKTestSupport, while a change to SKTestSupport can't break SKOptions.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
13→20 SKTestSupport uses SourceKitLSP part of a loop✕
- Connections
- 7 pairs of types, where a type in SKTestSupport uses a type in SourceKitLSP.
- The types involved
SKTestSupport.Assertions.swift→SourceKitLSP.SequenceSKTestSupport.CustomBuildServer→SourceKitLSP.SequenceSKTestSupport.CustomBuildServerTestProject→SourceKitLSP.HooksSKTestSupport.MultiFileTestProject→SourceKitLSP.HooksSKTestSupport.SwiftPMTestProject→SourceKitLSP.HooksSKTestSupport.TestSourceKitLSPClient→SourceKitLSP.HooksSKTestSupport.TestSourceKitLSPClient→SourceKitLSP.SourceKitLSPServer
- Direction
- SKTestSupport uses SourceKitLSP, so a change to SourceKitLSP can break SKTestSupport, while a change to SKTestSupport can't break SourceKitLSP.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
13→21 SKTestSupport uses LanguageServerProtocolExtensions part of a loop✕
- Connections
- 6 pairs of types, where a type in SKTestSupport uses a type in LanguageServerProtocolExtensions.
- The types involved
SKTestSupport.FileData→LanguageServerProtocolExtensions.DocumentURISKTestSupport.IndexedSingleSwiftFileTestProject→LanguageServerProtocolExtensions.DocumentURISKTestSupport.MultiFileTestProject→LanguageServerProtocolExtensions.DocumentURISKTestSupport.MultiFileTestProject→LanguageServerProtocolExtensions.LanguageSKTestSupport.TestSourceKitLSPClient→LanguageServerProtocolExtensions.DocumentURISKTestSupport.TestSourceKitLSPClient→LanguageServerProtocolExtensions.Language
- Direction
- SKTestSupport uses LanguageServerProtocolExtensions, so a change to LanguageServerProtocolExtensions can break SKTestSupport, while a change to SKTestSupport can't break LanguageServerProtocolExtensions.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
13→23 SKTestSupport uses CompletionScoring part of a loop✕
- Connections
- 8 pairs of types, where a type in SKTestSupport uses a type in CompletionScoring.
- The types involved
SKTestSupport.Assertions.swift→CompletionScoring.UIntSKTestSupport.CheckCoding.swift→CompletionScoring.UIntSKTestSupport.CustomBuildServerTestProject→CompletionScoring.UIntSKTestSupport.MultiEntrySemaphore→CompletionScoring.UIntSKTestSupport.RepeatUntilExpectedResult.swift→CompletionScoring.UIntSKTestSupport.SkipUnless→CompletionScoring.UIntSKTestSupport.TestSourceKitLSPClient→CompletionScoring.UIntSKTestSupport.WrappedSemaphore→CompletionScoring.UInt
- Direction
- SKTestSupport uses CompletionScoring, so a change to CompletionScoring can break SKTestSupport, while a change to SKTestSupport can't break CompletionScoring.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
13→24 SKTestSupport uses BuildServerIntegration part of a loop✕
- Connections
- 49 pairs of types, where a type in SKTestSupport uses a type in BuildServerIntegration. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
SKTestSupport.CheckCoding.swift→BuildServerIntegration.StringSKTestSupport.CreateBinary.swift→BuildServerIntegration.StringSKTestSupport.CreateBinary.swift→BuildServerIntegration.URLSKTestSupport.CustomBuildServer→BuildServerIntegration.InitializeBuildResponseSKTestSupport.CustomBuildServer→BuildServerIntegration.StringSKTestSupport.CustomBuildServer→BuildServerIntegration.TextDocumentSourceKitOptionsResponseSKTestSupport.CustomBuildServer→BuildServerIntegration.URLSKTestSupport.CustomBuildServerTestProject→BuildServerIntegration.StringSKTestSupport.CustomBuildServerTestProject→BuildServerIntegration.URLSKTestSupport.DefaultProperties→BuildServerIntegration.StringSKTestSupport.DefaultSDKPath.swift→BuildServerIntegration.StringSKTestSupport.DocumentPositions→BuildServerIntegration.StringSKTestSupport.DummyBuildServerManagerConnectionToClient→BuildServerIntegration.BuildServerManagerConnectionToClientSKTestSupport.DummyBuildServerManagerConnectionToClient→BuildServerIntegration.StringSKTestSupport.Error→BuildServerIntegration.ErrorSKTestSupport.ExpectationNotFulfilledError→BuildServerIntegration.ErrorSKTestSupport.ExpectationNotFulfilledError→BuildServerIntegration.StringSKTestSupport.ExternalBuildServerTestProject→BuildServerIntegration.StringSKTestSupport.FileData→BuildServerIntegration.StringSKTestSupport.FileManager→BuildServerIntegration.StringSKTestSupport.FileManager→BuildServerIntegration.URLSKTestSupport.FindTool.swift→BuildServerIntegration.StringSKTestSupport.FindTool.swift→BuildServerIntegration.URLSKTestSupport.GenericError→BuildServerIntegration.ErrorSKTestSupport.GenericError→BuildServerIntegration.String
- Direction
- SKTestSupport uses BuildServerIntegration, so a change to BuildServerIntegration can break SKTestSupport, while a change to SKTestSupport can't break BuildServerIntegration.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
14→9 DocumentationLanguageService uses SourceKitD✕
- Connections
- 2 pairs of types, where a type in DocumentationLanguageService uses a type in SourceKitD.
- The types involved
DocumentationLanguageService.DocCReferenceResolutionService→SourceKitD.MutexDocumentationLanguageService.ResponseError→SourceKitD.SKDError
- Direction
- DocumentationLanguageService uses SourceKitD, so a change to SourceKitD can break DocumentationLanguageService, while a change to DocumentationLanguageService can't break SourceKitD.
- Position
- Below the diagonal: DocumentationLanguageService uses a module listed above it, which is the healthy direction.
14→10 DocumentationLanguageService uses ToolchainRegistry✕
- Connections
- 1 pair of types, where a type in DocumentationLanguageService uses a type in ToolchainRegistry.
- The types involved
DocumentationLanguageService.DocumentationLanguageService→ToolchainRegistry.Toolchain
- Direction
- DocumentationLanguageService uses ToolchainRegistry, so a change to ToolchainRegistry can break DocumentationLanguageService, while a change to DocumentationLanguageService can't break ToolchainRegistry.
- Position
- Below the diagonal: DocumentationLanguageService uses a module listed above it, which is the healthy direction.
14→13 DocumentationLanguageService uses SKTestSupport✕
- Connections
- 1 pair of types, where a type in DocumentationLanguageService uses a type in SKTestSupport.
- The types involved
DocumentationLanguageService.DocumentationLanguageService→SKTestSupport.LocationsOrLocationLinksResponse
- Direction
- DocumentationLanguageService uses SKTestSupport, so a change to SKTestSupport can break DocumentationLanguageService, while a change to DocumentationLanguageService can't break SKTestSupport.
- Position
- Below the diagonal: DocumentationLanguageService uses a module listed above it, which is the healthy direction.
14→15 DocumentationLanguageService uses SemanticIndex part of a loop✕
- Connections
- 1 pair of types, where a type in DocumentationLanguageService uses a type in SemanticIndex.
- The types involved
DocumentationLanguageService.SymbolOccurrence→SemanticIndex.CheckedIndex
- Direction
- DocumentationLanguageService uses SemanticIndex, so a change to SemanticIndex can break DocumentationLanguageService, while a change to DocumentationLanguageService can't break SemanticIndex.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
14→16 DocumentationLanguageService uses SKUtilities part of a loop✕
- Connections
- 1 pair of types, where a type in DocumentationLanguageService uses a type in SKUtilities.
- The types involved
DocumentationLanguageService.DocCCatalogIndexManager→SKUtilities.LRUCache
- Direction
- DocumentationLanguageService uses SKUtilities, so a change to SKUtilities can break DocumentationLanguageService, while a change to DocumentationLanguageService can't break SKUtilities.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
14→17 DocumentationLanguageService uses SwiftSourceKitPlugin part of a loop✕
- Connections
- 6 pairs of types, where a type in DocumentationLanguageService uses a type in SwiftSourceKitPlugin.
- The types involved
DocumentationLanguageService.DocCServer→SwiftSourceKitPlugin.BoolDocumentationLanguageService.DocCSymbolInformation→SwiftSourceKitPlugin.BoolDocumentationLanguageService.DocumentationLanguageService→SwiftSourceKitPlugin.BoolDocumentationLanguageService.DocumentationLanguageService→SwiftSourceKitPlugin.PositionDocumentationLanguageService.SymbolLocator→SwiftSourceKitPlugin.BoolDocumentationLanguageService.SymbolOccurrence→SwiftSourceKitPlugin.Bool
- Direction
- DocumentationLanguageService uses SwiftSourceKitPlugin, so a change to SwiftSourceKitPlugin can break DocumentationLanguageService, while a change to DocumentationLanguageService can't break SwiftSourceKitPlugin.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
14→18 DocumentationLanguageService uses SKOptions part of a loop✕
- Connections
- 1 pair of types, where a type in DocumentationLanguageService uses a type in SKOptions.
- The types involved
DocumentationLanguageService.DocumentationLanguageService→SKOptions.SourceKitLSPOptions
- Direction
- DocumentationLanguageService uses SKOptions, so a change to SKOptions can break DocumentationLanguageService, while a change to DocumentationLanguageService can't break SKOptions.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
14→19 DocumentationLanguageService uses Diagnose part of a loop✕
- Connections
- 1 pair of types, where a type in DocumentationLanguageService uses a type in Diagnose.
- The types involved
DocumentationLanguageService.DocumentationLanguageService→Diagnose.SourceFileSyntax
- Direction
- DocumentationLanguageService uses Diagnose, so a change to Diagnose can break DocumentationLanguageService, while a change to DocumentationLanguageService can't break Diagnose.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
14→20 DocumentationLanguageService uses SourceKitLSP part of a loop✕
- Connections
- 8 pairs of types, where a type in DocumentationLanguageService uses a type in SourceKitLSP.
- The types involved
DocumentationLanguageService.DocumentationLanguageService→SourceKitLSP.AnnotatedTestItemDocumentationLanguageService.DocumentationLanguageService→SourceKitLSP.DocumentManagerDocumentationLanguageService.DocumentationLanguageService→SourceKitLSP.DocumentSnapshotDocumentationLanguageService.DocumentationLanguageService→SourceKitLSP.HooksDocumentationLanguageService.DocumentationLanguageService→SourceKitLSP.LanguageServiceDocumentationLanguageService.DocumentationLanguageService→SourceKitLSP.SourceEditDocumentationLanguageService.DocumentationLanguageService→SourceKitLSP.SourceKitLSPServerDocumentationLanguageService.DocumentationLanguageService→SourceKitLSP.Workspace
- Direction
- DocumentationLanguageService uses SourceKitLSP, so a change to SourceKitLSP can break DocumentationLanguageService, while a change to DocumentationLanguageService can't break SourceKitLSP.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
14→23 DocumentationLanguageService uses CompletionScoring part of a loop✕
- Connections
- 1 pair of types, where a type in DocumentationLanguageService uses a type in CompletionScoring.
- The types involved
DocumentationLanguageService.Component→CompletionScoring.Symbol
- Direction
- DocumentationLanguageService uses CompletionScoring, so a change to CompletionScoring can break DocumentationLanguageService, while a change to DocumentationLanguageService can't break CompletionScoring.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
14→24 DocumentationLanguageService uses BuildServerIntegration part of a loop✕
- Connections
- 26 pairs of types, where a type in DocumentationLanguageService uses a type in BuildServerIntegration. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
DocumentationLanguageService.Component→BuildServerIntegration.StringDocumentationLanguageService.DocCCatalogIndex→BuildServerIntegration.URLDocumentationLanguageService.DocCCatalogIndexManager→BuildServerIntegration.URLDocumentationLanguageService.DocCCheckedIndexError→BuildServerIntegration.StringDocumentationLanguageService.DocCDocumentationError→BuildServerIntegration.StringDocumentationLanguageService.DocCDocumentationManager→BuildServerIntegration.BuildServerManagerDocumentationLanguageService.DocCDocumentationManager→BuildServerIntegration.StringDocumentationLanguageService.DocCDocumentationManager→BuildServerIntegration.URLDocumentationLanguageService.DocCIndexError→BuildServerIntegration.StringDocumentationLanguageService.DocCReferenceResolutionContext→BuildServerIntegration.URLDocumentationLanguageService.DocCReferenceResolutionService→BuildServerIntegration.StringDocumentationLanguageService.DocCServer→BuildServerIntegration.StringDocumentationLanguageService.DocCServer→BuildServerIntegration.URLDocumentationLanguageService.DocCServerError→BuildServerIntegration.StringDocumentationLanguageService.DocCSymbolLink→BuildServerIntegration.StringDocumentationLanguageService.DocumentationLanguageService→BuildServerIntegration.StringDocumentationLanguageService.DocumentationLanguageService→BuildServerIntegration.URLDocumentationLanguageService.EmptySymbolGraph.swift→BuildServerIntegration.StringDocumentationLanguageService.MarkdownTitleFinder→BuildServerIntegration.StringDocumentationLanguageService.ReferenceResolutionError→BuildServerIntegration.StringDocumentationLanguageService.ResolvedInformation→BuildServerIntegration.StringDocumentationLanguageService.ResolvedInformation→BuildServerIntegration.URLDocumentationLanguageService.ResponseError→BuildServerIntegration.ErrorDocumentationLanguageService.SymbolInformation→BuildServerIntegration.StringDocumentationLanguageService.SymbolLocator→BuildServerIntegration.String
- Direction
- DocumentationLanguageService uses BuildServerIntegration, so a change to BuildServerIntegration can break DocumentationLanguageService, while a change to DocumentationLanguageService can't break BuildServerIntegration.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
15→8 SemanticIndex uses TSCExtensions✕
- Connections
- 4 pairs of types, where a type in SemanticIndex uses a type in TSCExtensions.
- The types involved
SemanticIndex.Process→TSCExtensions.ProcessCancellationBehaviorSemanticIndex.QueuedTask→TSCExtensions.TaskPrioritySemanticIndex.SemanticIndexManager→TSCExtensions.TaskPrioritySemanticIndex.TaskScheduler→TSCExtensions.TaskPriority
- Direction
- SemanticIndex uses TSCExtensions, so a change to TSCExtensions can break SemanticIndex, while a change to SemanticIndex can't break TSCExtensions.
- Position
- Below the diagonal: SemanticIndex uses a module listed above it, which is the healthy direction.
15→9 SemanticIndex uses SourceKitD✕
- Connections
- 2 pairs of types, where a type in SemanticIndex uses a type in SourceKitD.
- The types involved
SemanticIndex.ModuleVariantTracker→SourceKitD.MutexSemanticIndex.UncheckedIndex→SourceKitD.Mutex
- Direction
- SemanticIndex uses SourceKitD, so a change to SourceKitD can break SemanticIndex, while a change to SemanticIndex can't break SourceKitD.
- Position
- Below the diagonal: SemanticIndex uses a module listed above it, which is the healthy direction.
15→10 SemanticIndex uses ToolchainRegistry✕
- Connections
- 1 pair of types, where a type in SemanticIndex uses a type in ToolchainRegistry.
- The types involved
SemanticIndex.UpdateIndexStoreTaskDescription→ToolchainRegistry.Toolchain
- Direction
- SemanticIndex uses ToolchainRegistry, so a change to ToolchainRegistry can break SemanticIndex, while a change to SemanticIndex can't break ToolchainRegistry.
- Position
- Below the diagonal: SemanticIndex uses a module listed above it, which is the healthy direction.
15→14 SemanticIndex uses DocumentationLanguageService✕
- Connections
- 3 pairs of types, where a type in SemanticIndex uses a type in DocumentationLanguageService.
- The types involved
SemanticIndex.CheckedIndex→DocumentationLanguageService.DocCSymbolInformationSemanticIndex.CheckedIndex→DocumentationLanguageService.DocCSymbolLinkSemanticIndex.CheckedIndex→DocumentationLanguageService.SymbolOccurrence
- Direction
- SemanticIndex uses DocumentationLanguageService, so a change to DocumentationLanguageService can break SemanticIndex, while a change to SemanticIndex can't break DocumentationLanguageService.
- Position
- Below the diagonal: SemanticIndex uses a module listed above it, which is the healthy direction.
15→17 SemanticIndex uses SwiftSourceKitPlugin part of a loop✕
- Connections
- 17 pairs of types, where a type in SemanticIndex uses a type in SwiftSourceKitPlugin.
- The types involved
SemanticIndex.AnyIndexTaskDescription→SwiftSourceKitPlugin.BoolSemanticIndex.CheckedIndex→SwiftSourceKitPlugin.BoolSemanticIndex.Collection→SwiftSourceKitPlugin.BoolSemanticIndex.InMemoryDocumentManager→SwiftSourceKitPlugin.BoolSemanticIndex.IndexInjector→SwiftSourceKitPlugin.BoolSemanticIndex.IndexOutOfDateChecker→SwiftSourceKitPlugin.BoolSemanticIndex.IndexSymbolKind→SwiftSourceKitPlugin.BoolSemanticIndex.OpaqueQueuedIndexTask→SwiftSourceKitPlugin.BoolSemanticIndex.PreparationTaskDescription→SwiftSourceKitPlugin.BoolSemanticIndex.Process→SwiftSourceKitPlugin.BoolSemanticIndex.QueuedTask→SwiftSourceKitPlugin.BoolSemanticIndex.SemanticIndexManager→SwiftSourceKitPlugin.BoolSemanticIndex.TaskDescriptionProtocol→SwiftSourceKitPlugin.BoolSemanticIndex.TaskScheduler→SwiftSourceKitPlugin.BoolSemanticIndex.UncheckedIndex→SwiftSourceKitPlugin.BoolSemanticIndex.UpToDateTracker→SwiftSourceKitPlugin.BoolSemanticIndex.UpdateIndexStoreTaskDescription→SwiftSourceKitPlugin.Bool
- Direction
- SemanticIndex uses SwiftSourceKitPlugin, so a change to SwiftSourceKitPlugin can break SemanticIndex, while a change to SemanticIndex can't break SwiftSourceKitPlugin.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
15→18 SemanticIndex uses SKOptions part of a loop✕
- Connections
- 1 pair of types, where a type in SemanticIndex uses a type in SKOptions.
- The types involved
SemanticIndex.SemanticIndexManager→SKOptions.PreparationBatchingStrategy
- Direction
- SemanticIndex uses SKOptions, so a change to SKOptions can break SemanticIndex, while a change to SemanticIndex can't break SKOptions.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
15→20 SemanticIndex uses SourceKitLSP part of a loop✕
- Connections
- 2 pairs of types, where a type in SemanticIndex uses a type in SourceKitLSP.
- The types involved
SemanticIndex.IndexOutOfDateChecker→SourceKitLSP.SymbolLocationSemanticIndex.UpToDateTracker→SourceKitLSP.Sequence
- Direction
- SemanticIndex uses SourceKitLSP, so a change to SourceKitLSP can break SemanticIndex, while a change to SemanticIndex can't break SourceKitLSP.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
15→21 SemanticIndex uses LanguageServerProtocolExtensions part of a loop✕
- Connections
- 13 pairs of types, where a type in SemanticIndex uses a type in LanguageServerProtocolExtensions.
- The types involved
SemanticIndex.CheckedIndex→LanguageServerProtocolExtensions.DocumentURISemanticIndex.FileAndOutputPath→LanguageServerProtocolExtensions.DocumentURISemanticIndex.FileIndexInfo→LanguageServerProtocolExtensions.LanguageSemanticIndex.FileToIndex→LanguageServerProtocolExtensions.DocumentURISemanticIndex.InMemoryDocumentManager→LanguageServerProtocolExtensions.DocumentURISemanticIndex.InProgressPrepareForEditorTask→LanguageServerProtocolExtensions.DocumentURISemanticIndex.IndexOutOfDateChecker→LanguageServerProtocolExtensions.DocumentURISemanticIndex.Invocation→LanguageServerProtocolExtensions.LanguageSemanticIndex.SemanticIndexManager→LanguageServerProtocolExtensions.DocumentURISemanticIndex.SemanticIndexManager→LanguageServerProtocolExtensions.LanguageSemanticIndex.UncheckedIndex→LanguageServerProtocolExtensions.DocumentURISemanticIndex.UpdateIndexStoreTaskDescription→LanguageServerProtocolExtensions.DocumentURISemanticIndex.UpdateIndexStoreTaskDescription→LanguageServerProtocolExtensions.Language
- Direction
- SemanticIndex uses LanguageServerProtocolExtensions, so a change to LanguageServerProtocolExtensions can break SemanticIndex, while a change to SemanticIndex can't break LanguageServerProtocolExtensions.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
15→22 SemanticIndex uses ClangLanguageService part of a loop✕
- Connections
- 1 pair of types, where a type in SemanticIndex uses a type in ClangLanguageService.
- The types involved
SemanticIndex.IndexTaskDescription→ClangLanguageService.UInt32
- Direction
- SemanticIndex uses ClangLanguageService, so a change to ClangLanguageService can break SemanticIndex, while a change to SemanticIndex can't break ClangLanguageService.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
15→23 SemanticIndex uses CompletionScoring part of a loop✕
- Connections
- 3 pairs of types, where a type in SemanticIndex uses a type in CompletionScoring.
- The types involved
SemanticIndex.CheckedIndex→CompletionScoring.SymbolSemanticIndex.IndexTaskStatus→CompletionScoring.ComparableSemanticIndex.TargetPreparationPurpose→CompletionScoring.Comparable
- Direction
- SemanticIndex uses CompletionScoring, so a change to CompletionScoring can break SemanticIndex, while a change to SemanticIndex can't break CompletionScoring.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
15→24 SemanticIndex uses BuildServerIntegration part of a loop✕
- Connections
- 29 pairs of types, where a type in SemanticIndex uses a type in BuildServerIntegration. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
SemanticIndex.AnyIndexTaskDescription→BuildServerIntegration.StringSemanticIndex.CheckedIndex→BuildServerIntegration.OutputPathSemanticIndex.CheckedIndex→BuildServerIntegration.StringSemanticIndex.FileAndOutputPath→BuildServerIntegration.OutputPathSemanticIndex.FileIndexInfo→BuildServerIntegration.BuildTargetIdentifierSemanticIndex.FileIndexInfo→BuildServerIntegration.OutputPathSemanticIndex.FileToIndex→BuildServerIntegration.StringSemanticIndex.IndexClosedError→BuildServerIntegration.ErrorSemanticIndex.IndexClosedError→BuildServerIntegration.StringSemanticIndex.IndexInjector→BuildServerIntegration.URLSemanticIndex.IndexOutOfDateChecker→BuildServerIntegration.StringSemanticIndex.IndexTaskDescription→BuildServerIntegration.StringSemanticIndex.Invocation→BuildServerIntegration.AbsolutePathSemanticIndex.Invocation→BuildServerIntegration.FileBuildSettingsSemanticIndex.Invocation→BuildServerIntegration.StringSemanticIndex.ModuleMapEntry→BuildServerIntegration.StringSemanticIndex.ModuleVariantTracker→BuildServerIntegration.StringSemanticIndex.PreparationTaskDescription→BuildServerIntegration.BuildServerManagerSemanticIndex.PreparationTaskDescription→BuildServerIntegration.BuildTargetIdentifierSemanticIndex.PreparationTaskDescription→BuildServerIntegration.StringSemanticIndex.Process→BuildServerIntegration.AbsolutePathSemanticIndex.Process→BuildServerIntegration.StringSemanticIndex.SemanticIndexManager→BuildServerIntegration.BuildServerManagerSemanticIndex.SemanticIndexManager→BuildServerIntegration.BuildTargetIdentifierSemanticIndex.SemanticIndexManager→BuildServerIntegration.String
- Direction
- SemanticIndex uses BuildServerIntegration, so a change to BuildServerIntegration can break SemanticIndex, while a change to SemanticIndex can't break BuildServerIntegration.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
16→7 SKUtilities uses SwiftSyntaxCodeActions✕
- Connections
- 1 pair of types, where a type in SKUtilities uses a type in SwiftSyntaxCodeActions.
- The types involved
SKUtilities.LineTable→SwiftSyntaxCodeActions.Substring
- Direction
- SKUtilities uses SwiftSyntaxCodeActions, so a change to SwiftSyntaxCodeActions can break SKUtilities, while a change to SKUtilities can't break SwiftSyntaxCodeActions.
- Position
- Below the diagonal: SKUtilities uses a module listed above it, which is the healthy direction.
16→11 SKUtilities uses SwiftLanguageService✕
- Connections
- 1 pair of types, where a type in SKUtilities uses a type in SwiftLanguageService.
- The types involved
SKUtilities.Debouncer→SwiftLanguageService.Parameter
- Direction
- SKUtilities uses SwiftLanguageService, so a change to SwiftLanguageService can break SKUtilities, while a change to SKUtilities can't break SwiftLanguageService.
- Position
- Below the diagonal: SKUtilities uses a module listed above it, which is the healthy direction.
16→15 SKUtilities uses SemanticIndex✕
- Connections
- 1 pair of types, where a type in SKUtilities uses a type in SemanticIndex.
- The types involved
SKUtilities.LRUCache→SemanticIndex.Collection
- Direction
- SKUtilities uses SemanticIndex, so a change to SemanticIndex can break SKUtilities, while a change to SKUtilities can't break SemanticIndex.
- Position
- Below the diagonal: SKUtilities uses a module listed above it, which is the healthy direction.
16→17 SKUtilities uses SwiftSourceKitPlugin part of a loop✕
- Connections
- 2 pairs of types, where a type in SKUtilities uses a type in SwiftSourceKitPlugin.
- The types involved
SKUtilities.LineTable→SwiftSourceKitPlugin.BoolSKUtilities.LineTable→SwiftSourceKitPlugin.Position
- Direction
- SKUtilities uses SwiftSourceKitPlugin, so a change to SwiftSourceKitPlugin can break SKUtilities, while a change to SKUtilities can't break SwiftSourceKitPlugin.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
16→20 SKUtilities uses SourceKitLSP part of a loop✕
- Connections
- 1 pair of types, where a type in SKUtilities uses a type in SourceKitLSP.
- The types involved
SKUtilities.Dictionary→SourceKitLSP.Sequence
- Direction
- SKUtilities uses SourceKitLSP, so a change to SourceKitLSP can break SKUtilities, while a change to SKUtilities can't break SourceKitLSP.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
16→23 SKUtilities uses CompletionScoring part of a loop✕
- Connections
- 4 pairs of types, where a type in SKUtilities uses a type in CompletionScoring.
- The types involved
SKUtilities.Dictionary→CompletionScoring.AffirmativeSKUtilities.Dictionary→CompletionScoring.BinaryDecoderSKUtilities.Dictionary→CompletionScoring.BinaryEncoderSKUtilities.LineTable→CompletionScoring.UInt
- Direction
- SKUtilities uses CompletionScoring, so a change to CompletionScoring can break SKUtilities, while a change to SKUtilities can't break CompletionScoring.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
16→24 SKUtilities uses BuildServerIntegration part of a loop✕
- Connections
- 1 pair of types, where a type in SKUtilities uses a type in BuildServerIntegration.
- The types involved
SKUtilities.LineTable→BuildServerIntegration.String
- Direction
- SKUtilities uses BuildServerIntegration, so a change to BuildServerIntegration can break SKUtilities, while a change to SKUtilities can't break BuildServerIntegration.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
17→5 SwiftSourceKitPlugin uses SwiftExtensions✕
- Connections
- 2 pairs of types, where a type in SwiftSourceKitPlugin uses a type in SwiftExtensions.
- The types involved
SwiftSourceKitPlugin.ASTCompletionItem→SwiftExtensions.LazyValueSwiftSourceKitPlugin.Connection→SwiftExtensions.LazyValue
- Direction
- SwiftSourceKitPlugin uses SwiftExtensions, so a change to SwiftExtensions can break SwiftSourceKitPlugin, while a change to SwiftSourceKitPlugin can't break SwiftExtensions.
- Position
- Below the diagonal: SwiftSourceKitPlugin uses a module listed above it, which is the healthy direction.
17→6 SwiftSourceKitPlugin uses SwiftSourceKitPluginCommon✕
- Connections
- 2 pairs of types, where a type in SwiftSourceKitPlugin uses a type in SwiftSourceKitPluginCommon.
- The types involved
SwiftSourceKitPlugin.CompletionResultsArrayBuilder→SwiftSourceKitPluginCommon.CompletionResultSwiftSourceKitPlugin.CompletionResultsArrayBuilder→SwiftSourceKitPluginCommon.StringEntry
- Direction
- SwiftSourceKitPlugin uses SwiftSourceKitPluginCommon, so a change to SwiftSourceKitPluginCommon can break SwiftSourceKitPlugin, while a change to SwiftSourceKitPlugin can't break SwiftSourceKitPluginCommon.
- Position
- Below the diagonal: SwiftSourceKitPlugin uses a module listed above it, which is the healthy direction.
17→9 SwiftSourceKitPlugin uses SourceKitD✕
- Connections
- 29 pairs of types, where a type in SwiftSourceKitPlugin uses a type in SourceKitD. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
SwiftSourceKitPlugin.ASTCompletionItem→SourceKitD.SourceKitDSwiftSourceKitPlugin.CompletionProvider→SourceKitD.SourceKitDSwiftSourceKitPlugin.CompletionResultsArrayBuilder→SourceKitD.SourceKitDSwiftSourceKitPlugin.CompletionSession→SourceKitD.SourceKitDSwiftSourceKitPlugin.Connection→SourceKitD.SourceKitDSwiftSourceKitPlugin.Error→SourceKitD.SKDResponseSwiftSourceKitPlugin.Error→SourceKitD.SourceKitDSwiftSourceKitPlugin.GenericPluginError→SourceKitD.SKDResponseSwiftSourceKitPlugin.GenericPluginError→SourceKitD.SourceKitDSwiftSourceKitPlugin.InvalidRequest→SourceKitD.SKDResponseSwiftSourceKitPlugin.InvalidRequest→SourceKitD.SourceKitDSwiftSourceKitPlugin.NotRecommendedReason→SourceKitD.SourceKitDSwiftSourceKitPlugin.RequestHandler→SourceKitD.SourceKitDSwiftSourceKitPlugin.SKDRequestArrayReader→SourceKitD.SourceKitDSwiftSourceKitPlugin.SKDRequestDictionaryReader→SourceKitD.SourceKitDSwiftSourceKitPlugin.SKDRequestDictionaryReader→SourceKitD.sourcekitd_api_uid_tSwiftSourceKitPlugin.SKDResponse→SourceKitD.SKDResponseSwiftSourceKitPlugin.SKDResponse→SourceKitD.SourceKitDSwiftSourceKitPlugin.SKDResponseArrayBuilder→SourceKitD.SKDResponseSwiftSourceKitPlugin.SKDResponseArrayBuilder→SourceKitD.SourceKitDSwiftSourceKitPlugin.SKDResponseDictionaryBuilder→SourceKitD.SKDResponseSwiftSourceKitPlugin.SKDResponseDictionaryBuilder→SourceKitD.SourceKitDSwiftSourceKitPlugin.SKDResponseDictionaryBuilder→SourceKitD.sourcekitd_api_uid_tSwiftSourceKitPlugin.SourceKitDCoreForPlugin→SourceKitD.DLHandleSwiftSourceKitPlugin.SourceKitDCoreForPlugin→SourceKitD.SourceKitDCore
- Direction
- SwiftSourceKitPlugin uses SourceKitD, so a change to SourceKitD can break SwiftSourceKitPlugin, while a change to SwiftSourceKitPlugin can't break SourceKitD.
- Position
- Below the diagonal: SwiftSourceKitPlugin uses a module listed above it, which is the healthy direction.
17→11 SwiftSourceKitPlugin uses SwiftLanguageService✕
- Connections
- 3 pairs of types, where a type in SwiftSourceKitPlugin uses a type in SwiftLanguageService.
- The types involved
SwiftSourceKitPlugin.CompletionItem→SwiftLanguageService.RangeSwiftSourceKitPlugin.ExtendedCompletionInfo→SwiftLanguageService.DiagnosticSwiftSourceKitPlugin.TextEdit→SwiftLanguageService.Range
- Direction
- SwiftSourceKitPlugin uses SwiftLanguageService, so a change to SwiftLanguageService can break SwiftSourceKitPlugin, while a change to SwiftSourceKitPlugin can't break SwiftLanguageService.
- Position
- Below the diagonal: SwiftSourceKitPlugin uses a module listed above it, which is the healthy direction.
17→16 SwiftSourceKitPlugin uses SKUtilities✕
- Connections
- 1 pair of types, where a type in SwiftSourceKitPlugin uses a type in SKUtilities.
- The types involved
SwiftSourceKitPlugin.Document→SKUtilities.LineTable
- Direction
- SwiftSourceKitPlugin uses SKUtilities, so a change to SKUtilities can break SwiftSourceKitPlugin, while a change to SwiftSourceKitPlugin can't break SKUtilities.
- Position
- Below the diagonal: SwiftSourceKitPlugin uses a module listed above it, which is the healthy direction.
17→20 SwiftSourceKitPlugin uses SourceKitLSP part of a loop✕
- Connections
- 1 pair of types, where a type in SwiftSourceKitPlugin uses a type in SourceKitLSP.
- The types involved
SwiftSourceKitPlugin.TextEdit→SourceKitLSP.DocumentSnapshot
- Direction
- SwiftSourceKitPlugin uses SourceKitLSP, so a change to SourceKitLSP can break SwiftSourceKitPlugin, while a change to SwiftSourceKitPlugin can't break SourceKitLSP.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
17→22 SwiftSourceKitPlugin uses ClangLanguageService part of a loop✕
- Connections
- 2 pairs of types, where a type in SwiftSourceKitPlugin uses a type in ClangLanguageService.
- The types involved
SwiftSourceKitPlugin.ASTCompletionItem→ClangLanguageService.UInt32SwiftSourceKitPlugin.ItemKind→ClangLanguageService.UInt32
- Direction
- SwiftSourceKitPlugin uses ClangLanguageService, so a change to ClangLanguageService can break SwiftSourceKitPlugin, while a change to SwiftSourceKitPlugin can't break ClangLanguageService.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
17→23 SwiftSourceKitPlugin uses CompletionScoring part of a loop✕
- Connections
- 28 pairs of types, where a type in SwiftSourceKitPlugin uses a type in CompletionScoring. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
SwiftSourceKitPlugin.ASTCompletionItem→CompletionScoring.AvailabilitySwiftSourceKitPlugin.ASTCompletionItem→CompletionScoring.CompletionKindSwiftSourceKitPlugin.ASTCompletionItem→CompletionScoring.FlairSwiftSourceKitPlugin.ASTCompletionItem→CompletionScoring.ModuleProximitySwiftSourceKitPlugin.ASTCompletionItem→CompletionScoring.ScopeProximitySwiftSourceKitPlugin.ASTCompletionItem→CompletionScoring.SemanticClassificationSwiftSourceKitPlugin.ASTCompletionItem→CompletionScoring.StructuralProximitySwiftSourceKitPlugin.ASTCompletionItem→CompletionScoring.SynchronicityCompatibilitySwiftSourceKitPlugin.ASTCompletionItem→CompletionScoring.TypeCompatibilitySwiftSourceKitPlugin.Bool→CompletionScoring.BinaryDecoderSwiftSourceKitPlugin.Bool→CompletionScoring.BinaryEncoderSwiftSourceKitPlugin.CompletionContext→CompletionScoring.ScopeSwiftSourceKitPlugin.CompletionItem→CompletionScoring.CompletionScoreSwiftSourceKitPlugin.CompletionItem→CompletionScoring.SemanticClassificationSwiftSourceKitPlugin.CompletionProvider→CompletionScoring.UInt64SwiftSourceKitPlugin.CompletionProvider.swift→CompletionScoring.[String: Popularity]SwiftSourceKitPlugin.CompletionResultsArrayBuilder→CompletionScoring.UInt64SwiftSourceKitPlugin.CompletionResultsArrayBuilder→CompletionScoring.UInt8SwiftSourceKitPlugin.CompletionSession→CompletionScoring.CandidateBatchSwiftSourceKitPlugin.CompletionSession→CompletionScoring.PopularitySwiftSourceKitPlugin.CompletionSession→CompletionScoring.PopularityIndexSwiftSourceKitPlugin.CompletionSession→CompletionScoring.PopularityTableSwiftSourceKitPlugin.CompletionSorting→CompletionScoring.PatternSwiftSourceKitPlugin.Connection→CompletionScoring.PopularityIndexSwiftSourceKitPlugin.Connection→CompletionScoring.PopularityTable
- Direction
- SwiftSourceKitPlugin uses CompletionScoring, so a change to CompletionScoring can break SwiftSourceKitPlugin, while a change to SwiftSourceKitPlugin can't break CompletionScoring.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
17→24 SwiftSourceKitPlugin uses BuildServerIntegration part of a loop✕
- Connections
- 25 pairs of types, where a type in SwiftSourceKitPlugin uses a type in BuildServerIntegration.
- The types involved
SwiftSourceKitPlugin.ASTCompletionItem→BuildServerIntegration.KindSwiftSourceKitPlugin.ASTCompletionItem→BuildServerIntegration.StringSwiftSourceKitPlugin.CompletionContext→BuildServerIntegration.KindSwiftSourceKitPlugin.CompletionContext→BuildServerIntegration.StringSwiftSourceKitPlugin.CompletionItem→BuildServerIntegration.StringSwiftSourceKitPlugin.CompletionResultsArrayBuilder→BuildServerIntegration.StringSwiftSourceKitPlugin.CompletionSession→BuildServerIntegration.KindSwiftSourceKitPlugin.CompletionSession→BuildServerIntegration.StringSwiftSourceKitPlugin.CompletionSorting→BuildServerIntegration.StringSwiftSourceKitPlugin.Connection→BuildServerIntegration.StringSwiftSourceKitPlugin.Document→BuildServerIntegration.StringSwiftSourceKitPlugin.Error→BuildServerIntegration.StringSwiftSourceKitPlugin.ExtendedCompletionInfo→BuildServerIntegration.StringSwiftSourceKitPlugin.GenericPluginError→BuildServerIntegration.StringSwiftSourceKitPlugin.Location→BuildServerIntegration.CopiedFileMapSwiftSourceKitPlugin.Location→BuildServerIntegration.StringSwiftSourceKitPlugin.Position→BuildServerIntegration.StringSwiftSourceKitPlugin.SKDRequestArrayReader→BuildServerIntegration.StringSwiftSourceKitPlugin.SKDRequestDictionaryReader→BuildServerIntegration.StringSwiftSourceKitPlugin.SKDResponse→BuildServerIntegration.ErrorSwiftSourceKitPlugin.SKDResponse→BuildServerIntegration.StringSwiftSourceKitPlugin.SourceKitDCoreForPlugin→BuildServerIntegration.URLSwiftSourceKitPlugin.SourceKitPluginError→BuildServerIntegration.ErrorSwiftSourceKitPlugin.TextEdit→BuildServerIntegration.StringSwiftSourceKitPlugin.WithArrayOfCStrings.swift→BuildServerIntegration.String
- Direction
- SwiftSourceKitPlugin uses BuildServerIntegration, so a change to BuildServerIntegration can break SwiftSourceKitPlugin, while a change to SwiftSourceKitPlugin can't break BuildServerIntegration.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
18→17 SKOptions uses SwiftSourceKitPlugin✕
- Connections
- 3 pairs of types, where a type in SKOptions uses a type in SwiftSourceKitPlugin.
- The types involved
SKOptions.ExperimentalFeature→SwiftSourceKitPlugin.BoolSKOptions.SourceKitLSPOptions→SwiftSourceKitPlugin.BoolSKOptions.SwiftPMOptions→SwiftSourceKitPlugin.Bool
- Direction
- SKOptions uses SwiftSourceKitPlugin, so a change to SwiftSourceKitPlugin can break SKOptions, while a change to SKOptions can't break SwiftSourceKitPlugin.
- Position
- Below the diagonal: SKOptions uses a module listed above it, which is the healthy direction.
18→21 SKOptions uses LanguageServerProtocolExtensions part of a loop✕
- Connections
- 1 pair of types, where a type in SKOptions uses a type in LanguageServerProtocolExtensions.
- The types involved
SKOptions.SourceKitLSPOptions→LanguageServerProtocolExtensions.DocumentURI
- Direction
- SKOptions uses LanguageServerProtocolExtensions, so a change to LanguageServerProtocolExtensions can break SKOptions, while a change to SKOptions can't break LanguageServerProtocolExtensions.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
18→24 SKOptions uses BuildServerIntegration part of a loop✕
- Connections
- 12 pairs of types, where a type in SKOptions uses a type in BuildServerIntegration.
- The types involved
SKOptions.BackgroundPreparationMode→BuildServerIntegration.StringSKOptions.BuildConfiguration→BuildServerIntegration.StringSKOptions.CompilationDatabaseOptions→BuildServerIntegration.StringSKOptions.ExperimentalFeature→BuildServerIntegration.StringSKOptions.FallbackBuildSystemOptions→BuildServerIntegration.StringSKOptions.LoggingOptions→BuildServerIntegration.StringSKOptions.SourceKitDOptions→BuildServerIntegration.StringSKOptions.SourceKitLSPOptions→BuildServerIntegration.StringSKOptions.SourceKitLSPOptions→BuildServerIntegration.URLSKOptions.SwiftPMBuildSystem→BuildServerIntegration.StringSKOptions.SwiftPMOptions→BuildServerIntegration.StringSKOptions.WorkspaceType→BuildServerIntegration.String
- Direction
- SKOptions uses BuildServerIntegration, so a change to BuildServerIntegration can break SKOptions, while a change to SKOptions can't break BuildServerIntegration.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
19→7 Diagnose uses SwiftSyntaxCodeActions✕
- Connections
- 3 pairs of types, where a type in Diagnose uses a type in SwiftSyntaxCodeActions.
- The types involved
Diagnose.FirstImportFinder→SwiftSyntaxCodeActions.SyntaxDiagnose.Signpost→SwiftSyntaxCodeActions.SubstringDiagnose.Visitor→SwiftSyntaxCodeActions.Syntax
- Direction
- Diagnose uses SwiftSyntaxCodeActions, so a change to SwiftSyntaxCodeActions can break Diagnose, while a change to Diagnose can't break SwiftSyntaxCodeActions.
- Position
- Below the diagonal: Diagnose uses a module listed above it, which is the healthy direction.
19→9 Diagnose uses SourceKitD✕
- Connections
- 4 pairs of types, where a type in Diagnose uses a type in SourceKitD.
- The types involved
Diagnose.Array→SourceKitD.SKDResponseArrayDiagnose.Array→SourceKitD.sourcekitd_api_functions_tDiagnose.Array→SourceKitD.sourcekitd_api_keysDiagnose.OutOfProcessSourceKitRequestExecutor→SourceKitD.PluginPaths
- Direction
- Diagnose uses SourceKitD, so a change to SourceKitD can break Diagnose, while a change to Diagnose can't break SourceKitD.
- Position
- Below the diagonal: Diagnose uses a module listed above it, which is the healthy direction.
19→10 Diagnose uses ToolchainRegistry✕
- Connections
- 5 pairs of types, where a type in Diagnose uses a type in ToolchainRegistry.
- The types involved
Diagnose.DiagnoseCommand→ToolchainRegistry.ToolchainDiagnose.DiagnoseCommand→ToolchainRegistry.ToolchainRegistryDiagnose.ReduceCommand→ToolchainRegistry.ToolchainDiagnose.ReduceFrontendCommand→ToolchainRegistry.ToolchainDiagnose.ReproducerBundle.swift→ToolchainRegistry.Toolchain
- Direction
- Diagnose uses ToolchainRegistry, so a change to ToolchainRegistry can break Diagnose, while a change to Diagnose can't break ToolchainRegistry.
- Position
- Below the diagonal: Diagnose uses a module listed above it, which is the healthy direction.
19→11 Diagnose uses SwiftLanguageService✕
- Connections
- 2 pairs of types, where a type in Diagnose uses a type in SwiftLanguageService.
- The types involved
Diagnose.Array→SwiftLanguageService.RangeDiagnose.FirstImportFinder→SwiftLanguageService.SyntaxProtocol
- Direction
- Diagnose uses SwiftLanguageService, so a change to SwiftLanguageService can break Diagnose, while a change to Diagnose can't break SwiftLanguageService.
- Position
- Below the diagonal: Diagnose uses a module listed above it, which is the healthy direction.
19→13 Diagnose uses SKTestSupport✕
- Connections
- 1 pair of types, where a type in Diagnose uses a type in SKTestSupport.
- The types involved
Diagnose.Array→SKTestSupport.TextDocumentIdentifier
- Direction
- Diagnose uses SKTestSupport, so a change to SKTestSupport can break Diagnose, while a change to Diagnose can't break SKTestSupport.
- Position
- Below the diagonal: Diagnose uses a module listed above it, which is the healthy direction.
19→17 Diagnose uses SwiftSourceKitPlugin✕
- Connections
- 5 pairs of types, where a type in Diagnose uses a type in SwiftSourceKitPlugin.
- The types involved
Diagnose.Array→SwiftSourceKitPlugin.BoolDiagnose.IndexLogMessageHandler→SwiftSourceKitPlugin.BoolDiagnose.SourceReducer→SwiftSourceKitPlugin.BoolDiagnose.SourceReducer.swift→SwiftSourceKitPlugin.BoolDiagnose.TriviaPiece→SwiftSourceKitPlugin.Bool
- Direction
- Diagnose uses SwiftSourceKitPlugin, so a change to SwiftSourceKitPlugin can break Diagnose, while a change to Diagnose can't break SwiftSourceKitPlugin.
- Position
- Below the diagonal: Diagnose uses a module listed above it, which is the healthy direction.
19→18 Diagnose uses SKOptions✕
- Connections
- 1 pair of types, where a type in Diagnose uses a type in SKOptions.
- The types involved
Diagnose.IndexCommand→SKOptions.ExperimentalFeature
- Direction
- Diagnose uses SKOptions, so a change to SKOptions can break Diagnose, while a change to Diagnose can't break SKOptions.
- Position
- Below the diagonal: Diagnose uses a module listed above it, which is the healthy direction.
19→20 Diagnose uses SourceKitLSP part of a loop✕
- Connections
- 3 pairs of types, where a type in Diagnose uses a type in SourceKitLSP.
- The types involved
Diagnose.IndexLogMessageHandler→SourceKitLSP.LogMessageNotificationDiagnose.ReducerResult→SourceKitLSP.SourceEditDiagnose.Visitor→SourceKitLSP.SourceEdit
- Direction
- Diagnose uses SourceKitLSP, so a change to SourceKitLSP can break Diagnose, while a change to Diagnose can't break SourceKitLSP.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
19→23 Diagnose uses CompletionScoring part of a loop✕
- Connections
- 3 pairs of types, where a type in Diagnose uses a type in CompletionScoring.
- The types involved
Diagnose.Array→CompletionScoring.BinaryDecoderDiagnose.Array→CompletionScoring.BinaryEncoderDiagnose.DiagnoseProgressState→CompletionScoring.Comparable
- Direction
- Diagnose uses CompletionScoring, so a change to CompletionScoring can break Diagnose, while a change to Diagnose can't break CompletionScoring.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
19→24 Diagnose uses BuildServerIntegration part of a loop✕
- Connections
- 32 pairs of types, where a type in Diagnose uses a type in BuildServerIntegration. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
Diagnose.Asi→BuildServerIntegration.StringDiagnose.BundleComponent→BuildServerIntegration.StringDiagnose.CodingKeys→BuildServerIntegration.StringDiagnose.DiagnoseCommand→BuildServerIntegration.StringDiagnose.DiagnoseCommand→BuildServerIntegration.URLDiagnose.EventType→BuildServerIntegration.StringDiagnose.GenericError→BuildServerIntegration.ErrorDiagnose.GenericError→BuildServerIntegration.StringDiagnose.IndexCommand→BuildServerIntegration.StringDiagnose.OSLogScraper→BuildServerIntegration.StringDiagnose.OutOfProcessSourceKitRequestExecutor→BuildServerIntegration.URLDiagnose.ReduceCommand→BuildServerIntegration.StringDiagnose.ReduceFrontendCommand→BuildServerIntegration.StringDiagnose.ReduceSwiftFrontend.swift→BuildServerIntegration.StringDiagnose.RemoveFunctionBodies→BuildServerIntegration.StringDiagnose.RemoveMembersAndCodeBlockItems→BuildServerIntegration.StringDiagnose.RemoveTopLevelItems→BuildServerIntegration.StringDiagnose.ReproducerBundle.swift→BuildServerIntegration.URLDiagnose.RequestInfo→BuildServerIntegration.StringDiagnose.RequestInfo→BuildServerIntegration.URLDiagnose.RequestInfo.swift→BuildServerIntegration.StringDiagnose.RunSourceKitdRequestCommand→BuildServerIntegration.StringDiagnose.RunSourceKitdRequestCommand→BuildServerIntegration.URLDiagnose.Signpost→BuildServerIntegration.StringDiagnose.SourceReducer.swift→BuildServerIntegration.String
- Direction
- Diagnose uses BuildServerIntegration, so a change to BuildServerIntegration can break Diagnose, while a change to Diagnose can't break BuildServerIntegration.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
20→9 SourceKitLSP uses SourceKitD✕
- Connections
- 5 pairs of types, where a type in SourceKitLSP uses a type in SourceKitD.
- The types involved
SourceKitLSP.DocumentManager→SourceKitD.MutexSourceKitLSP.SourceKitLSPServer→SourceKitD.MutexSourceKitLSP.Usage→SourceKitD.sourcekitd_api_uid_tSourceKitLSP.Usage→SourceKitD.sourcekitd_api_valuesSourceKitLSP.Workspace→SourceKitD.Mutex
- Direction
- SourceKitLSP uses SourceKitD, so a change to SourceKitD can break SourceKitLSP, while a change to SourceKitLSP can't break SourceKitD.
- Position
- Below the diagonal: SourceKitLSP uses a module listed above it, which is the healthy direction.
20→10 SourceKitLSP uses ToolchainRegistry✕
- Connections
- 5 pairs of types, where a type in SourceKitLSP uses a type in ToolchainRegistry.
- The types involved
SourceKitLSP.LanguageService→ToolchainRegistry.ToolchainSourceKitLSP.SourceKitLSPServer→ToolchainRegistry.ToolchainRegistrySourceKitLSP.Workspace→ToolchainRegistry.ToolchainSourceKitLSP.Workspace→ToolchainRegistry.ToolchainRegistrySourceKitLSP.Workspace.swift→ToolchainRegistry.ToolchainRegistry
- Direction
- SourceKitLSP uses ToolchainRegistry, so a change to ToolchainRegistry can break SourceKitLSP, while a change to SourceKitLSP can't break ToolchainRegistry.
- Position
- Below the diagonal: SourceKitLSP uses a module listed above it, which is the healthy direction.
20→11 SourceKitLSP uses SwiftLanguageService✕
- Connections
- 12 pairs of types, where a type in SourceKitLSP uses a type in SwiftLanguageService.
- The types involved
SourceKitLSP.CrossLanguageName→SwiftLanguageService.CompoundDeclNameSourceKitLSP.DocumentSnapshot→SwiftLanguageService.RangeSourceKitLSP.DocumentSnapshot→SwiftLanguageService.SourceKitDPositionSourceKitLSP.DocumentSnapshot→SwiftLanguageService.SyntaxProtocolSourceKitLSP.LanguageService→SwiftLanguageService.CodeActionSourceKitLSP.LanguageService→SwiftLanguageService.InlayHintSourceKitLSP.LanguageService→SwiftLanguageService.SignatureHelpSourceKitLSP.MacroExpansionReferenceDocumentURLData→SwiftLanguageService.RangeSourceKitLSP.SourceKitLSPServer→SwiftLanguageService.CodeActionSourceKitLSP.SourceKitLSPServer→SwiftLanguageService.InlayHintSourceKitLSP.SourceKitLSPServer→SwiftLanguageService.SignatureHelpSourceKitLSP.TestDiscovery.swift→SwiftLanguageService.Range
- Direction
- SourceKitLSP uses SwiftLanguageService, so a change to SwiftLanguageService can break SourceKitLSP, while a change to SourceKitLSP can't break SwiftLanguageService.
- Position
- Below the diagonal: SourceKitLSP uses a module listed above it, which is the healthy direction.
20→13 SourceKitLSP uses SKTestSupport✕
- Connections
- 7 pairs of types, where a type in SourceKitLSP uses a type in SKTestSupport.
- The types involved
SourceKitLSP.CodeActionResolveMetadata→SKTestSupport.TextDocumentIdentifierSourceKitLSP.ExecuteCommandRequest→SKTestSupport.TextDocumentIdentifierSourceKitLSP.LanguageService→SKTestSupport.DocumentDiagnosticReportSourceKitLSP.LanguageService→SKTestSupport.LocationsOrLocationLinksResponseSourceKitLSP.SourceKitLSPCommandMetadata→SKTestSupport.TextDocumentIdentifierSourceKitLSP.SourceKitLSPServer→SKTestSupport.DocumentDiagnosticReportSourceKitLSP.SourceKitLSPServer→SKTestSupport.LocationsOrLocationLinksResponse
- Direction
- SourceKitLSP uses SKTestSupport, so a change to SKTestSupport can break SourceKitLSP, while a change to SourceKitLSP can't break SKTestSupport.
- Position
- Below the diagonal: SourceKitLSP uses a module listed above it, which is the healthy direction.
20→14 SourceKitLSP uses DocumentationLanguageService✕
- Connections
- 4 pairs of types, where a type in SourceKitLSP uses a type in DocumentationLanguageService.
- The types involved
SourceKitLSP.DefinitionLocationsResult→DocumentationLanguageService.SymbolOccurrenceSourceKitLSP.SourceKitLSPServer→DocumentationLanguageService.SymbolOccurrenceSourceKitLSP.TestDiscovery→DocumentationLanguageService.SymbolOccurrenceSourceKitLSP.TestDiscovery.swift→DocumentationLanguageService.SymbolInformation
- Direction
- SourceKitLSP uses DocumentationLanguageService, so a change to DocumentationLanguageService can break SourceKitLSP, while a change to SourceKitLSP can't break DocumentationLanguageService.
- Position
- Below the diagonal: SourceKitLSP uses a module listed above it, which is the healthy direction.
20→15 SourceKitLSP uses SemanticIndex✕
- Connections
- 14 pairs of types, where a type in SourceKitLSP uses a type in SemanticIndex.
- The types involved
SourceKitLSP.ContainerChainFilter→SemanticIndex.CollectionSourceKitLSP.DefinitionLocations.swift→SemanticIndex.CheckedIndexSourceKitLSP.DocumentManager→SemanticIndex.InMemoryDocumentManagerSourceKitLSP.Hooks→SemanticIndex.IndexHooksSourceKitLSP.SourceKitLSPServer→SemanticIndex.CheckedIndexSourceKitLSP.SourceKitLSPServer→SemanticIndex.TaskSchedulerSourceKitLSP.SourceKitLSPServer.swift→SemanticIndex.CheckedIndexSourceKitLSP.TestDiscovery→SemanticIndex.CheckedIndexSourceKitLSP.Workspace→SemanticIndex.CheckedIndexSourceKitLSP.Workspace→SemanticIndex.IndexCheckLevelSourceKitLSP.Workspace→SemanticIndex.SemanticIndexManagerSourceKitLSP.Workspace→SemanticIndex.TaskSchedulerSourceKitLSP.Workspace→SemanticIndex.UncheckedIndexSourceKitLSP.Workspace.swift→SemanticIndex.UncheckedIndex
- Direction
- SourceKitLSP uses SemanticIndex, so a change to SemanticIndex can break SourceKitLSP, while a change to SourceKitLSP can't break SemanticIndex.
- Position
- Below the diagonal: SourceKitLSP uses a module listed above it, which is the healthy direction.
20→16 SourceKitLSP uses SKUtilities✕
- Connections
- 5 pairs of types, where a type in SourceKitLSP uses a type in SKUtilities.
- The types involved
SourceKitLSP.Document→SKUtilities.LineTableSourceKitLSP.DocumentSnapshot→SKUtilities.LineTableSourceKitLSP.EntryPointManager→SKUtilities.DebouncerSourceKitLSP.SourceEdit→SKUtilities.LineTableSourceKitLSP.SyntaxTreeManager→SKUtilities.LRUCache
- Direction
- SourceKitLSP uses SKUtilities, so a change to SKUtilities can break SourceKitLSP, while a change to SourceKitLSP can't break SKUtilities.
- Position
- Below the diagonal: SourceKitLSP uses a module listed above it, which is the healthy direction.
20→17 SourceKitLSP uses SwiftSourceKitPlugin✕
- Connections
- 32 pairs of types, where a type in SourceKitLSP uses a type in SwiftSourceKitPlugin. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
SourceKitLSP.AnnotatedTestItem→SwiftSourceKitPlugin.BoolSourceKitLSP.CapabilityRegistry→SwiftSourceKitPlugin.BoolSourceKitLSP.CapabilityRegistry→SwiftSourceKitPlugin.CompletionOptionsSourceKitLSP.ContainerChainFilter→SwiftSourceKitPlugin.BoolSourceKitLSP.DefinitionLocations.swift→SwiftSourceKitPlugin.LocationSourceKitLSP.DefinitionLocationsResult→SwiftSourceKitPlugin.LocationSourceKitLSP.DocumentManager→SwiftSourceKitPlugin.BoolSourceKitLSP.DocumentSnapshot→SwiftSourceKitPlugin.PositionSourceKitLSP.EntryPointManager→SwiftSourceKitPlugin.BoolSourceKitLSP.GeneratedInterfaceDetails→SwiftSourceKitPlugin.PositionSourceKitLSP.ID→SwiftSourceKitPlugin.BoolSourceKitLSP.LanguageService→SwiftSourceKitPlugin.BoolSourceKitLSP.LanguageService→SwiftSourceKitPlugin.CompletionItemSourceKitLSP.LanguageService→SwiftSourceKitPlugin.LocationSourceKitLSP.LanguageService→SwiftSourceKitPlugin.PositionSourceKitLSP.LanguageService→SwiftSourceKitPlugin.TextEditSourceKitLSP.LanguageServiceType→SwiftSourceKitPlugin.BoolSourceKitLSP.MemberFilter→SwiftSourceKitPlugin.BoolSourceKitLSP.MessageHandlingDependencyTracker→SwiftSourceKitPlugin.BoolSourceKitLSP.NameTranslatorService→SwiftSourceKitPlugin.BoolSourceKitLSP.Sequence→SwiftSourceKitPlugin.BoolSourceKitLSP.SourceKitLSPServer→SwiftSourceKitPlugin.BoolSourceKitLSP.SourceKitLSPServer→SwiftSourceKitPlugin.CompletionItemSourceKitLSP.SourceKitLSPServer→SwiftSourceKitPlugin.ConnectionSourceKitLSP.SourceKitLSPServer→SwiftSourceKitPlugin.Location
- Direction
- SourceKitLSP uses SwiftSourceKitPlugin, so a change to SwiftSourceKitPlugin can break SourceKitLSP, while a change to SourceKitLSP can't break SwiftSourceKitPlugin.
- Position
- Below the diagonal: SourceKitLSP uses a module listed above it, which is the healthy direction.
20→18 SourceKitLSP uses SKOptions✕
- Connections
- 5 pairs of types, where a type in SourceKitLSP uses a type in SKOptions.
- The types involved
SourceKitLSP.LanguageService→SKOptions.SourceKitLSPOptionsSourceKitLSP.LogMessageNotification→SKOptions.SourceKitLSPOptionsSourceKitLSP.SourceKitLSPServer→SKOptions.SourceKitLSPOptionsSourceKitLSP.Workspace→SKOptions.SourceKitLSPOptionsSourceKitLSP.Workspace.swift→SKOptions.SourceKitLSPOptions
- Direction
- SourceKitLSP uses SKOptions, so a change to SKOptions can break SourceKitLSP, while a change to SourceKitLSP can't break SKOptions.
- Position
- Below the diagonal: SourceKitLSP uses a module listed above it, which is the healthy direction.
20→19 SourceKitLSP uses Diagnose✕
- Connections
- 4 pairs of types, where a type in SourceKitLSP uses a type in Diagnose.
- The types involved
SourceKitLSP.DocumentSnapshot→Diagnose.IDSourceKitLSP.ID→Diagnose.IDSourceKitLSP.SyntaxTreeManager→Diagnose.IDSourceKitLSP.SyntaxTreeManager→Diagnose.SourceFileSyntax
- Direction
- SourceKitLSP uses Diagnose, so a change to Diagnose can break SourceKitLSP, while a change to SourceKitLSP can't break Diagnose.
- Position
- Below the diagonal: SourceKitLSP uses a module listed above it, which is the healthy direction.
20→21 SourceKitLSP uses LanguageServerProtocolExtensions part of a loop✕
- Connections
- 33 pairs of types, where a type in SourceKitLSP uses a type in LanguageServerProtocolExtensions. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
SourceKitLSP.CapabilityRegistry→LanguageServerProtocolExtensions.LanguageSourceKitLSP.CrossLanguageName→LanguageServerProtocolExtensions.LanguageSourceKitLSP.DefinitionLocations.swift→LanguageServerProtocolExtensions.DocumentURISourceKitLSP.Document→LanguageServerProtocolExtensions.DocumentURISourceKitLSP.Document→LanguageServerProtocolExtensions.LanguageSourceKitLSP.DocumentManager→LanguageServerProtocolExtensions.DocumentURISourceKitLSP.DocumentManager→LanguageServerProtocolExtensions.LanguageSourceKitLSP.DocumentSelector→LanguageServerProtocolExtensions.LanguageSourceKitLSP.DocumentSnapshot→LanguageServerProtocolExtensions.DocumentURISourceKitLSP.DocumentSnapshot→LanguageServerProtocolExtensions.LanguageSourceKitLSP.GeneratedInterfaceDetails→LanguageServerProtocolExtensions.DocumentURISourceKitLSP.GeneratedInterfaceDocumentURLData→LanguageServerProtocolExtensions.DocumentURISourceKitLSP.ID→LanguageServerProtocolExtensions.DocumentURISourceKitLSP.IndexProgressManager→LanguageServerProtocolExtensions.WorkDoneProgressManagerSourceKitLSP.LanguageService→LanguageServerProtocolExtensions.DocumentURISourceKitLSP.LanguageServiceRegistry→LanguageServerProtocolExtensions.LanguageSourceKitLSP.MacroExpansionReferenceDocumentURLData→LanguageServerProtocolExtensions.DocumentURISourceKitLSP.NameTranslatorService→LanguageServerProtocolExtensions.DocumentURISourceKitLSP.OnDiskDocumentManager→LanguageServerProtocolExtensions.DocumentURISourceKitLSP.OnDiskDocumentManager→LanguageServerProtocolExtensions.LanguageSourceKitLSP.ReferenceDocumentURL→LanguageServerProtocolExtensions.DocumentURISourceKitLSP.ResolveItemData→LanguageServerProtocolExtensions.DocumentURISourceKitLSP.SharedWorkDoneProgressManager→LanguageServerProtocolExtensions.WorkDoneProgressManagerSourceKitLSP.SourceFilesWithSameRealpathInferrer→LanguageServerProtocolExtensions.DocumentURISourceKitLSP.SourceKitLSPServer→LanguageServerProtocolExtensions.DocumentURI
- Direction
- SourceKitLSP uses LanguageServerProtocolExtensions, so a change to LanguageServerProtocolExtensions can break SourceKitLSP, while a change to SourceKitLSP can't break LanguageServerProtocolExtensions.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
20→22 SourceKitLSP uses ClangLanguageService part of a loop✕
- Connections
- 1 pair of types, where a type in SourceKitLSP uses a type in ClangLanguageService.
- The types involved
SourceKitLSP.SemanticTokenTypes→ClangLanguageService.UInt32
- Direction
- SourceKitLSP uses ClangLanguageService, so a change to ClangLanguageService can break SourceKitLSP, while a change to SourceKitLSP can't break ClangLanguageService.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
20→23 SourceKitLSP uses CompletionScoring part of a loop✕
- Connections
- 4 pairs of types, where a type in SourceKitLSP uses a type in CompletionScoring.
- The types involved
SourceKitLSP.AnnotatedTestItem→CompletionScoring.SymbolSourceKitLSP.DocumentSnapshot→CompletionScoring.UIntSourceKitLSP.ID→CompletionScoring.ComparableSourceKitLSP.TestItem→CompletionScoring.Symbol
- Direction
- SourceKitLSP uses CompletionScoring, so a change to CompletionScoring can break SourceKitLSP, while a change to SourceKitLSP can't break CompletionScoring.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
20→24 SourceKitLSP uses BuildServerIntegration part of a loop✕
- Connections
- 41 pairs of types, where a type in SourceKitLSP uses a type in BuildServerIntegration. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
SourceKitLSP.CallHierarchyItem→BuildServerIntegration.CopiedFileMapSourceKitLSP.CapabilityRegistry→BuildServerIntegration.StringSourceKitLSP.ContainerChainFilter→BuildServerIntegration.StringSourceKitLSP.CrossLanguageName→BuildServerIntegration.StringSourceKitLSP.DefinitionLocations.swift→BuildServerIntegration.StringSourceKitLSP.Document→BuildServerIntegration.StringSourceKitLSP.DocumentManager→BuildServerIntegration.StringSourceKitLSP.DocumentSelector→BuildServerIntegration.StringSourceKitLSP.DocumentSnapshot→BuildServerIntegration.StringSourceKitLSP.DocumentSnapshot→BuildServerIntegration.URLSourceKitLSP.Error→BuildServerIntegration.ErrorSourceKitLSP.FallThroughToNextLanguageService→BuildServerIntegration.ErrorSourceKitLSP.GeneratedInterfaceDocumentURLData→BuildServerIntegration.StringSourceKitLSP.Hooks→BuildServerIntegration.BuildServerHooksSourceKitLSP.LanguageService→BuildServerIntegration.FileBuildSettingsSourceKitLSP.LanguageService→BuildServerIntegration.StringSourceKitLSP.LogMessageNotification+representingStructureUsingEmojiPrefixIfNecessary.swift→BuildServerIntegration.StringSourceKitLSP.MacroExpansionReferenceDocumentURLData→BuildServerIntegration.StringSourceKitLSP.MemberFilter→BuildServerIntegration.StringSourceKitLSP.NameTranslatorService→BuildServerIntegration.StringSourceKitLSP.Parameters→BuildServerIntegration.StringSourceKitLSP.QualifiedWorkspaceSymbolQuery→BuildServerIntegration.StringSourceKitLSP.ReferenceDocumentURL→BuildServerIntegration.StringSourceKitLSP.ReferenceDocumentURL→BuildServerIntegration.URLSourceKitLSP.ReferenceDocumentURLError→BuildServerIntegration.Error
- Direction
- SourceKitLSP uses BuildServerIntegration, so a change to BuildServerIntegration can break SourceKitLSP, while a change to SourceKitLSP can't break BuildServerIntegration.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
21→17 LanguageServerProtocolExtensions uses SwiftSourceKitPlugin✕
- Connections
- 1 pair of types, where a type in LanguageServerProtocolExtensions uses a type in SwiftSourceKitPlugin.
- The types involved
LanguageServerProtocolExtensions.WorkDoneProgressManager→SwiftSourceKitPlugin.Connection
- Direction
- LanguageServerProtocolExtensions uses SwiftSourceKitPlugin, so a change to SwiftSourceKitPlugin can break LanguageServerProtocolExtensions, while a change to LanguageServerProtocolExtensions can't break SwiftSourceKitPlugin.
- Position
- Below the diagonal: LanguageServerProtocolExtensions uses a module listed above it, which is the healthy direction.
21→20 LanguageServerProtocolExtensions uses SourceKitLSP✕
- Connections
- 2 pairs of types, where a type in LanguageServerProtocolExtensions uses a type in SourceKitLSP.
- The types involved
LanguageServerProtocolExtensions.WorkDoneProgressManager→SourceKitLSP.CapabilityRegistryLanguageServerProtocolExtensions.WorkDoneProgressManager→SourceKitLSP.SourceKitLSPServer
- Direction
- LanguageServerProtocolExtensions uses SourceKitLSP, so a change to SourceKitLSP can break LanguageServerProtocolExtensions, while a change to LanguageServerProtocolExtensions can't break SourceKitLSP.
- Position
- Below the diagonal: LanguageServerProtocolExtensions uses a module listed above it, which is the healthy direction.
21→24 LanguageServerProtocolExtensions uses BuildServerIntegration part of a loop✕
- Connections
- 3 pairs of types, where a type in LanguageServerProtocolExtensions uses a type in BuildServerIntegration.
- The types involved
LanguageServerProtocolExtensions.DocumentURI→BuildServerIntegration.StringLanguageServerProtocolExtensions.Language→BuildServerIntegration.StringLanguageServerProtocolExtensions.WorkDoneProgressManager→BuildServerIntegration.String
- Direction
- LanguageServerProtocolExtensions uses BuildServerIntegration, so a change to BuildServerIntegration can break LanguageServerProtocolExtensions, while a change to LanguageServerProtocolExtensions can't break BuildServerIntegration.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
22→10 ClangLanguageService uses ToolchainRegistry✕
- Connections
- 1 pair of types, where a type in ClangLanguageService uses a type in ToolchainRegistry.
- The types involved
ClangLanguageService.ClangLanguageService→ToolchainRegistry.Toolchain
- Direction
- ClangLanguageService uses ToolchainRegistry, so a change to ToolchainRegistry can break ClangLanguageService, while a change to ClangLanguageService can't break ToolchainRegistry.
- Position
- Below the diagonal: ClangLanguageService uses a module listed above it, which is the healthy direction.
22→11 ClangLanguageService uses SwiftLanguageService✕
- Connections
- 3 pairs of types, where a type in ClangLanguageService uses a type in SwiftLanguageService.
- The types involved
ClangLanguageService.ClangLanguageService→SwiftLanguageService.CodeActionClangLanguageService.ClangLanguageService→SwiftLanguageService.InlayHintClangLanguageService.ClangLanguageService→SwiftLanguageService.SignatureHelp
- Direction
- ClangLanguageService uses SwiftLanguageService, so a change to SwiftLanguageService can break ClangLanguageService, while a change to ClangLanguageService can't break SwiftLanguageService.
- Position
- Below the diagonal: ClangLanguageService uses a module listed above it, which is the healthy direction.
22→13 ClangLanguageService uses SKTestSupport✕
- Connections
- 2 pairs of types, where a type in ClangLanguageService uses a type in SKTestSupport.
- The types involved
ClangLanguageService.ClangLanguageService→SKTestSupport.DocumentDiagnosticReportClangLanguageService.ClangLanguageService→SKTestSupport.LocationsOrLocationLinksResponse
- Direction
- ClangLanguageService uses SKTestSupport, so a change to SKTestSupport can break ClangLanguageService, while a change to ClangLanguageService can't break SKTestSupport.
- Position
- Below the diagonal: ClangLanguageService uses a module listed above it, which is the healthy direction.
22→15 ClangLanguageService uses SemanticIndex✕
- Connections
- 1 pair of types, where a type in ClangLanguageService uses a type in SemanticIndex.
- The types involved
ClangLanguageService.ClangLanguageService→SemanticIndex.Process
- Direction
- ClangLanguageService uses SemanticIndex, so a change to SemanticIndex can break ClangLanguageService, while a change to ClangLanguageService can't break SemanticIndex.
- Position
- Below the diagonal: ClangLanguageService uses a module listed above it, which is the healthy direction.
22→17 ClangLanguageService uses SwiftSourceKitPlugin✕
- Connections
- 6 pairs of types, where a type in ClangLanguageService uses a type in SwiftSourceKitPlugin.
- The types involved
ClangLanguageService.ClangBuildSettings→SwiftSourceKitPlugin.BoolClangLanguageService.ClangLanguageService→SwiftSourceKitPlugin.BoolClangLanguageService.ClangLanguageService→SwiftSourceKitPlugin.CompletionItemClangLanguageService.ClangLanguageService→SwiftSourceKitPlugin.PositionClangLanguageService.ClangLanguageService→SwiftSourceKitPlugin.TextEditClangLanguageService.UInt32→SwiftSourceKitPlugin.Bool
- Direction
- ClangLanguageService uses SwiftSourceKitPlugin, so a change to SwiftSourceKitPlugin can break ClangLanguageService, while a change to ClangLanguageService can't break SwiftSourceKitPlugin.
- Position
- Below the diagonal: ClangLanguageService uses a module listed above it, which is the healthy direction.
22→18 ClangLanguageService uses SKOptions✕
- Connections
- 1 pair of types, where a type in ClangLanguageService uses a type in SKOptions.
- The types involved
ClangLanguageService.ClangLanguageService→SKOptions.SourceKitLSPOptions
- Direction
- ClangLanguageService uses SKOptions, so a change to SKOptions can break ClangLanguageService, while a change to ClangLanguageService can't break SKOptions.
- Position
- Below the diagonal: ClangLanguageService uses a module listed above it, which is the healthy direction.
22→20 ClangLanguageService uses SourceKitLSP✕
- Connections
- 15 pairs of types, where a type in ClangLanguageService uses a type in SourceKitLSP.
- The types involved
ClangLanguageService.ClangLanguageService→SourceKitLSP.AnnotatedTestItemClangLanguageService.ClangLanguageService→SourceKitLSP.CodeActionRequestClangLanguageService.ClangLanguageService→SourceKitLSP.CrossLanguageNameClangLanguageService.ClangLanguageService→SourceKitLSP.DocumentSnapshotClangLanguageService.ClangLanguageService→SourceKitLSP.ExecuteCommandRequestClangLanguageService.ClangLanguageService→SourceKitLSP.HooksClangLanguageService.ClangLanguageService→SourceKitLSP.LanguageServerStateClangLanguageService.ClangLanguageService→SourceKitLSP.LanguageServiceClangLanguageService.ClangLanguageService→SourceKitLSP.RenameLocationClangLanguageService.ClangLanguageService→SourceKitLSP.SourceEditClangLanguageService.ClangLanguageService→SourceKitLSP.SourceKitLSPServerClangLanguageService.ClangLanguageService→SourceKitLSP.WeakWorkspaceClangLanguageService.ClangLanguageService→SourceKitLSP.WorkspaceClangLanguageService.ClangLanguageService→SourceKitLSP.WorkspaceEditClangLanguageService.SemanticTokensLegendTranslator→SourceKitLSP.SemanticTokensLegend
- Direction
- ClangLanguageService uses SourceKitLSP, so a change to SourceKitLSP can break ClangLanguageService, while a change to ClangLanguageService can't break SourceKitLSP.
- Position
- Below the diagonal: ClangLanguageService uses a module listed above it, which is the healthy direction.
22→21 ClangLanguageService uses LanguageServerProtocolExtensions✕
- Connections
- 1 pair of types, where a type in ClangLanguageService uses a type in LanguageServerProtocolExtensions.
- The types involved
ClangLanguageService.ClangLanguageService→LanguageServerProtocolExtensions.DocumentURI
- Direction
- ClangLanguageService uses LanguageServerProtocolExtensions, so a change to LanguageServerProtocolExtensions can break ClangLanguageService, while a change to ClangLanguageService can't break LanguageServerProtocolExtensions.
- Position
- Below the diagonal: ClangLanguageService uses a module listed above it, which is the healthy direction.
22→24 ClangLanguageService uses BuildServerIntegration part of a loop✕
- Connections
- 5 pairs of types, where a type in ClangLanguageService uses a type in BuildServerIntegration.
- The types involved
ClangLanguageService.ClangBuildSettings→BuildServerIntegration.FileBuildSettingsClangLanguageService.ClangBuildSettings→BuildServerIntegration.StringClangLanguageService.ClangBuildSettings→BuildServerIntegration.URLClangLanguageService.ClangLanguageService→BuildServerIntegration.StringClangLanguageService.ClangLanguageService→BuildServerIntegration.URL
- Direction
- ClangLanguageService uses BuildServerIntegration, so a change to BuildServerIntegration can break ClangLanguageService, while a change to ClangLanguageService can't break BuildServerIntegration.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
23→11 CompletionScoring uses SwiftLanguageService✕
- Connections
- 5 pairs of types, where a type in CompletionScoring uses a type in SwiftLanguageService.
- The types involved
CompletionScoring.CandidateBatch→SwiftLanguageService.RangeCompletionScoring.ContiguousZeroBasedIndexedCollection→SwiftLanguageService.RangeCompletionScoring.SwiftExtensions.swift→SwiftLanguageService.RangeCompletionScoring.UnsafeBufferPointer→SwiftLanguageService.RangeCompletionScoring.UnsafeStorage→SwiftLanguageService.Range
- Direction
- CompletionScoring uses SwiftLanguageService, so a change to SwiftLanguageService can break CompletionScoring, while a change to CompletionScoring can't break SwiftLanguageService.
- Position
- Below the diagonal: CompletionScoring uses a module listed above it, which is the healthy direction.
23→15 CompletionScoring uses SemanticIndex✕
- Connections
- 6 pairs of types, where a type in CompletionScoring uses a type in SemanticIndex.
- The types involved
CompletionScoring.ContiguousZeroBasedIndexedCollection→SemanticIndex.CollectionCompletionScoring.UnsafeArray→SemanticIndex.CollectionCompletionScoring.UnsafeBufferPointer→SemanticIndex.CollectionCompletionScoring.UnsafeMutableBufferPointer→SemanticIndex.CollectionCompletionScoring.UnsafeMutablePointer→SemanticIndex.CollectionCompletionScoring.UnsafeStorage→SemanticIndex.Collection
- Direction
- CompletionScoring uses SemanticIndex, so a change to SemanticIndex can break CompletionScoring, while a change to CompletionScoring can't break SemanticIndex.
- Position
- Below the diagonal: CompletionScoring uses a module listed above it, which is the healthy direction.
23→17 CompletionScoring uses SwiftSourceKitPlugin✕
- Connections
- 18 pairs of types, where a type in CompletionScoring uses a type in SwiftSourceKitPlugin.
- The types involved
CompletionScoring.CandidateBatch→SwiftSourceKitPlugin.BoolCompletionScoring.Comparable→SwiftSourceKitPlugin.BoolCompletionScoring.CompletionScore→SwiftSourceKitPlugin.BoolCompletionScoring.ContentType→SwiftSourceKitPlugin.BoolCompletionScoring.Flair→SwiftSourceKitPlugin.Int64CompletionScoring.HeapIndex→SwiftSourceKitPlugin.BoolCompletionScoring.InfluencingIdentifiers→SwiftSourceKitPlugin.BoolCompletionScoring.MatchCollator→SwiftSourceKitPlugin.BoolCompletionScoring.Pattern→SwiftSourceKitPlugin.BoolCompletionScoring.Popularity→SwiftSourceKitPlugin.BoolCompletionScoring.PopularityIndex→SwiftSourceKitPlugin.BoolCompletionScoring.PopularityScoreComponent→SwiftSourceKitPlugin.BoolCompletionScoring.PopularityTable→SwiftSourceKitPlugin.SKDRequestDictionaryReaderCompletionScoring.RejectionFilter→SwiftSourceKitPlugin.BoolCompletionScoring.SwiftExtensions.swift→SwiftSourceKitPlugin.BoolCompletionScoring.TextScore→SwiftSourceKitPlugin.BoolCompletionScoring.UTF8Byte→SwiftSourceKitPlugin.BoolCompletionScoring.UnsafeArray→SwiftSourceKitPlugin.Bool
- Direction
- CompletionScoring uses SwiftSourceKitPlugin, so a change to SwiftSourceKitPlugin can break CompletionScoring, while a change to CompletionScoring can't break SwiftSourceKitPlugin.
- Position
- Below the diagonal: CompletionScoring uses a module listed above it, which is the healthy direction.
23→20 CompletionScoring uses SourceKitLSP✕
- Connections
- 1 pair of types, where a type in CompletionScoring uses a type in SourceKitLSP.
- The types involved
CompletionScoring.UnsafeStackArray→SourceKitLSP.Sequence
- Direction
- CompletionScoring uses SourceKitLSP, so a change to SourceKitLSP can break CompletionScoring, while a change to CompletionScoring can't break SourceKitLSP.
- Position
- Below the diagonal: CompletionScoring uses a module listed above it, which is the healthy direction.
23→22 CompletionScoring uses ClangLanguageService✕
- Connections
- 1 pair of types, where a type in CompletionScoring uses a type in ClangLanguageService.
- The types involved
CompletionScoring.RejectionFilter→ClangLanguageService.UInt32
- Direction
- CompletionScoring uses ClangLanguageService, so a change to ClangLanguageService can break CompletionScoring, while a change to CompletionScoring can't break ClangLanguageService.
- Position
- Below the diagonal: CompletionScoring uses a module listed above it, which is the healthy direction.
23→24 CompletionScoring uses BuildServerIntegration part of a loop✕
- Connections
- 32 pairs of types, where a type in CompletionScoring uses a type in BuildServerIntegration. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
CompletionScoring.Availability→BuildServerIntegration.StringCompletionScoring.Candidate→BuildServerIntegration.StringCompletionScoring.CandidateBatch→BuildServerIntegration.StringCompletionScoring.CompletionKind→BuildServerIntegration.StringCompletionScoring.CompletionScoreComponent→BuildServerIntegration.StringCompletionScoring.ComponentDebugDescription→BuildServerIntegration.StringCompletionScoring.Flair→BuildServerIntegration.StringCompletionScoring.GenericError→BuildServerIntegration.ErrorCompletionScoring.GenericError→BuildServerIntegration.StringCompletionScoring.InfluencingIdentifiers→BuildServerIntegration.StringCompletionScoring.MatchCollator→BuildServerIntegration.MatchCompletionScoring.MatchCollator→BuildServerIntegration.StringCompletionScoring.ModuleProximity→BuildServerIntegration.StringCompletionScoring.ModuleSymbolReferenceTable→BuildServerIntegration.StringCompletionScoring.Pattern→BuildServerIntegration.StringCompletionScoring.PopularityIndex→BuildServerIntegration.StringCompletionScoring.PopularityTable→BuildServerIntegration.StringCompletionScoring.RawCompletionScoreComponent→BuildServerIntegration.StringCompletionScoring.RejectionFilter→BuildServerIntegration.MatchCompletionScoring.RejectionFilter→BuildServerIntegration.StringCompletionScoring.RescoredMatch→BuildServerIntegration.StringCompletionScoring.Scope→BuildServerIntegration.StringCompletionScoring.ScopeProximity→BuildServerIntegration.StringCompletionScoring.SemanticClassification→BuildServerIntegration.StringCompletionScoring.StructuralProximity→BuildServerIntegration.String
- Direction
- CompletionScoring uses BuildServerIntegration, so a change to BuildServerIntegration can break CompletionScoring, while a change to CompletionScoring can't break BuildServerIntegration.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
24→5 BuildServerIntegration uses SwiftExtensions✕
- Connections
- 2 pairs of types, where a type in BuildServerIntegration uses a type in SwiftExtensions.
- The types involved
BuildServerIntegration.BuildServerManager→SwiftExtensions.CacheBuildServerIntegration.JSONCompilationDatabaseBuildServer→SwiftExtensions.LazyValue
- Direction
- BuildServerIntegration uses SwiftExtensions, so a change to SwiftExtensions can break BuildServerIntegration, while a change to BuildServerIntegration can't break SwiftExtensions.
- Position
- Below the diagonal: BuildServerIntegration uses a module listed above it, which is the healthy direction.
24→7 BuildServerIntegration uses SwiftSyntaxCodeActions✕
- Connections
- 2 pairs of types, where a type in BuildServerIntegration uses a type in SwiftSyntaxCodeActions.
- The types involved
BuildServerIntegration.String→SwiftSyntaxCodeActions.SubstringBuildServerIntegration.UnixCommandParser→SwiftSyntaxCodeActions.Substring
- Direction
- BuildServerIntegration uses SwiftSyntaxCodeActions, so a change to SwiftSyntaxCodeActions can break BuildServerIntegration, while a change to BuildServerIntegration can't break SwiftSyntaxCodeActions.
- Position
- Below the diagonal: BuildServerIntegration uses a module listed above it, which is the healthy direction.
24→10 BuildServerIntegration uses ToolchainRegistry✕
- Connections
- 7 pairs of types, where a type in BuildServerIntegration uses a type in ToolchainRegistry.
- The types involved
BuildServerIntegration.BuildServerConfig→ToolchainRegistry.ToolchainRegistryBuildServerIntegration.BuildServerManager→ToolchainRegistry.ToolchainBuildServerIntegration.BuildServerManager→ToolchainRegistry.ToolchainRegistryBuildServerIntegration.BuildServerSpec→ToolchainRegistry.ToolchainRegistryBuildServerIntegration.JSONCompilationDatabaseBuildServer→ToolchainRegistry.ToolchainRegistryBuildServerIntegration.SwiftPMBuildServer→ToolchainRegistry.ToolchainBuildServerIntegration.SwiftPMBuildServer→ToolchainRegistry.ToolchainRegistry
- Direction
- BuildServerIntegration uses ToolchainRegistry, so a change to ToolchainRegistry can break BuildServerIntegration, while a change to BuildServerIntegration can't break ToolchainRegistry.
- Position
- Below the diagonal: BuildServerIntegration uses a module listed above it, which is the healthy direction.
24→15 BuildServerIntegration uses SemanticIndex✕
- Connections
- 3 pairs of types, where a type in BuildServerIntegration uses a type in SemanticIndex.
- The types involved
BuildServerIntegration.BuildServerManager→SemanticIndex.CollectionBuildServerIntegration.BuildSettingsLogger→SemanticIndex.InvocationBuildServerIntegration.ExternalBuildServerAdapter→SemanticIndex.Process
- Direction
- BuildServerIntegration uses SemanticIndex, so a change to SemanticIndex can break BuildServerIntegration, while a change to BuildServerIntegration can't break SemanticIndex.
- Position
- Below the diagonal: BuildServerIntegration uses a module listed above it, which is the healthy direction.
24→16 BuildServerIntegration uses SKUtilities✕
- Connections
- 2 pairs of types, where a type in BuildServerIntegration uses a type in SKUtilities.
- The types involved
BuildServerIntegration.BuildServerManager→SKUtilities.DebouncerBuildServerIntegration.SwiftToolchainResolver→SKUtilities.LRUCache
- Direction
- BuildServerIntegration uses SKUtilities, so a change to SKUtilities can break BuildServerIntegration, while a change to BuildServerIntegration can't break SKUtilities.
- Position
- Below the diagonal: BuildServerIntegration uses a module listed above it, which is the healthy direction.
24→17 BuildServerIntegration uses SwiftSourceKitPlugin✕
- Connections
- 25 pairs of types, where a type in BuildServerIntegration uses a type in SwiftSourceKitPlugin.
- The types involved
BuildServerIntegration.BuildServerManager→SwiftSourceKitPlugin.BoolBuildServerIntegration.BuildServerManager.swift→SwiftSourceKitPlugin.BoolBuildServerIntegration.BuildServerManagerConnectionToClient→SwiftSourceKitPlugin.BoolBuildServerIntegration.BuildServerManagerConnectionToClient→SwiftSourceKitPlugin.ConnectionBuildServerIntegration.BuildServerMessageDependencyTracker→SwiftSourceKitPlugin.BoolBuildServerIntegration.BuiltInBuildServer→SwiftSourceKitPlugin.BoolBuildServerIntegration.Character→SwiftSourceKitPlugin.BoolBuildServerIntegration.CopiedFileMap→SwiftSourceKitPlugin.BoolBuildServerIntegration.DetermineBuildServer.swift→SwiftSourceKitPlugin.BoolBuildServerIntegration.ExternalBuildServerAdapter→SwiftSourceKitPlugin.BoolBuildServerIntegration.FileBuildSettings→SwiftSourceKitPlugin.BoolBuildServerIntegration.FixedCompilationDatabaseBuildServer→SwiftSourceKitPlugin.BoolBuildServerIntegration.FixedCompilationDatabaseBuildServer→SwiftSourceKitPlugin.ConnectionBuildServerIntegration.JSONCompilationDatabaseBuildServer→SwiftSourceKitPlugin.BoolBuildServerIntegration.JSONCompilationDatabaseBuildServer→SwiftSourceKitPlugin.ConnectionBuildServerIntegration.LegacyBuildServer→SwiftSourceKitPlugin.BoolBuildServerIntegration.MainFilesProvider→SwiftSourceKitPlugin.BoolBuildServerIntegration.SourceFileInfo→SwiftSourceKitPlugin.BoolBuildServerIntegration.SplitShellCommand.swift→SwiftSourceKitPlugin.BoolBuildServerIntegration.String→SwiftSourceKitPlugin.BoolBuildServerIntegration.SwiftPMBuildServer→SwiftSourceKitPlugin.BoolBuildServerIntegration.SwiftPMBuildServer→SwiftSourceKitPlugin.ConnectionBuildServerIntegration.URL→SwiftSourceKitPlugin.BoolBuildServerIntegration.UnixCommandParser→SwiftSourceKitPlugin.BoolBuildServerIntegration.WindowsCommandParser→SwiftSourceKitPlugin.Bool
- Direction
- BuildServerIntegration uses SwiftSourceKitPlugin, so a change to SwiftSourceKitPlugin can break BuildServerIntegration, while a change to BuildServerIntegration can't break SwiftSourceKitPlugin.
- Position
- Below the diagonal: BuildServerIntegration uses a module listed above it, which is the healthy direction.
24→18 BuildServerIntegration uses SKOptions✕
- Connections
- 8 pairs of types, where a type in BuildServerIntegration uses a type in SKOptions.
- The types involved
BuildServerIntegration.BuildServerConfig→SKOptions.SourceKitLSPOptionsBuildServerIntegration.BuildServerManager→SKOptions.SourceKitLSPOptionsBuildServerIntegration.BuildServerSpec→SKOptions.SourceKitLSPOptionsBuildServerIntegration.DetermineBuildServer.swift→SKOptions.SourceKitLSPOptionsBuildServerIntegration.ExternalBuildServerAdapter→SKOptions.SourceKitLSPOptionsBuildServerIntegration.FallbackBuildSettings.swift→SKOptions.FallbackBuildSystemOptionsBuildServerIntegration.SwiftPMBuildServer→SKOptions.BuildConfigurationBuildServerIntegration.SwiftPMBuildServer→SKOptions.SourceKitLSPOptions
- Direction
- BuildServerIntegration uses SKOptions, so a change to SKOptions can break BuildServerIntegration, while a change to BuildServerIntegration can't break SKOptions.
- Position
- Below the diagonal: BuildServerIntegration uses a module listed above it, which is the healthy direction.
24→20 BuildServerIntegration uses SourceKitLSP✕
- Connections
- 1 pair of types, where a type in BuildServerIntegration uses a type in SourceKitLSP.
- The types involved
BuildServerIntegration.SwiftPMBuildServer→SourceKitLSP.Workspace
- Direction
- BuildServerIntegration uses SourceKitLSP, so a change to SourceKitLSP can break BuildServerIntegration, while a change to BuildServerIntegration can't break SourceKitLSP.
- Position
- Below the diagonal: BuildServerIntegration uses a module listed above it, which is the healthy direction.
24→21 BuildServerIntegration uses LanguageServerProtocolExtensions✕
- Connections
- 15 pairs of types, where a type in BuildServerIntegration uses a type in LanguageServerProtocolExtensions.
- The types involved
BuildServerIntegration.AbsolutePath→LanguageServerProtocolExtensions.DocumentURIBuildServerIntegration.BuildServerManager→LanguageServerProtocolExtensions.DocumentURIBuildServerIntegration.BuildServerManager→LanguageServerProtocolExtensions.LanguageBuildServerIntegration.BuildSettingsLogger→LanguageServerProtocolExtensions.DocumentURIBuildServerIntegration.CompilationDatabaseCompileCommand→LanguageServerProtocolExtensions.DocumentURIBuildServerIntegration.CopiedFileMap→LanguageServerProtocolExtensions.DocumentURIBuildServerIntegration.DetermineBuildServer.swift→LanguageServerProtocolExtensions.DocumentURIBuildServerIntegration.FallbackBuildSettings.swift→LanguageServerProtocolExtensions.DocumentURIBuildServerIntegration.FallbackBuildSettings.swift→LanguageServerProtocolExtensions.LanguageBuildServerIntegration.FileBuildSettings→LanguageServerProtocolExtensions.DocumentURIBuildServerIntegration.FileBuildSettings→LanguageServerProtocolExtensions.LanguageBuildServerIntegration.LegacyBuildServer→LanguageServerProtocolExtensions.DocumentURIBuildServerIntegration.MainFilesProvider→LanguageServerProtocolExtensions.DocumentURIBuildServerIntegration.SwiftPMBuildServer→LanguageServerProtocolExtensions.DocumentURIBuildServerIntegration.TextDocumentSourceKitOptionsResponse→LanguageServerProtocolExtensions.DocumentURI
- Direction
- BuildServerIntegration uses LanguageServerProtocolExtensions, so a change to LanguageServerProtocolExtensions can break BuildServerIntegration, while a change to BuildServerIntegration can't break LanguageServerProtocolExtensions.
- Position
- Below the diagonal: BuildServerIntegration uses a module listed above it, which is the healthy direction.
24→23 BuildServerIntegration uses CompletionScoring✕
- Connections
- 7 pairs of types, where a type in BuildServerIntegration uses a type in CompletionScoring.
- The types involved
BuildServerIntegration.OutputPath→CompletionScoring.ComparableBuildServerIntegration.String→CompletionScoring.BinaryDecoderBuildServerIntegration.String→CompletionScoring.BinaryEncoderBuildServerIntegration.String→CompletionScoring.UIntBuildServerIntegration.String→CompletionScoring.UInt8BuildServerIntegration.String→CompletionScoring.UTF8BytesBuildServerIntegration.UnixCommandParser→CompletionScoring.UInt8
- Direction
- BuildServerIntegration uses CompletionScoring, so a change to CompletionScoring can break BuildServerIntegration, while a change to BuildServerIntegration can't break CompletionScoring.
- Position
- Below the diagonal: BuildServerIntegration uses a module listed above it, which is the healthy direction.
25→10 InProcessClient uses ToolchainRegistry✕
- Connections
- 1 pair of types, where a type in InProcessClient uses a type in ToolchainRegistry.
- The types involved
InProcessClient.InProcessSourceKitLSPClient→ToolchainRegistry.ToolchainRegistry
- Direction
- InProcessClient uses ToolchainRegistry, so a change to ToolchainRegistry can break InProcessClient, while a change to InProcessClient can't break ToolchainRegistry.
- Position
- Below the diagonal: InProcessClient uses a module listed above it, which is the healthy direction.
25→18 InProcessClient uses SKOptions✕
- Connections
- 1 pair of types, where a type in InProcessClient uses a type in SKOptions.
- The types involved
InProcessClient.InProcessSourceKitLSPClient→SKOptions.SourceKitLSPOptions
- Direction
- InProcessClient uses SKOptions, so a change to SKOptions can break InProcessClient, while a change to InProcessClient can't break SKOptions.
- Position
- Below the diagonal: InProcessClient uses a module listed above it, which is the healthy direction.
25→20 InProcessClient uses SourceKitLSP✕
- Connections
- 2 pairs of types, where a type in InProcessClient uses a type in SourceKitLSP.
- The types involved
InProcessClient.InProcessSourceKitLSPClient→SourceKitLSP.HooksInProcessClient.InProcessSourceKitLSPClient→SourceKitLSP.SourceKitLSPServer
- Direction
- InProcessClient uses SourceKitLSP, so a change to SourceKitLSP can break InProcessClient, while a change to InProcessClient can't break SourceKitLSP.
- Position
- Below the diagonal: InProcessClient uses a module listed above it, which is the healthy direction.
25→24 InProcessClient uses BuildServerIntegration✕
- Connections
- 1 pair of types, where a type in InProcessClient uses a type in BuildServerIntegration.
- The types involved
InProcessClient.InProcessSourceKitLSPClient→BuildServerIntegration.URL
- Direction
- InProcessClient uses BuildServerIntegration, so a change to BuildServerIntegration can break InProcessClient, while a change to InProcessClient can't break BuildServerIntegration.
- Position
- Below the diagonal: InProcessClient uses a module listed above it, which is the healthy direction.
26→9 SwiftSourceKitClientPlugin uses SourceKitD✕
- Connections
- 3 pairs of types, where a type in SwiftSourceKitClientPlugin uses a type in SourceKitD.
- The types involved
SwiftSourceKitClientPlugin.SourceKitDCoreForPlugin→SourceKitD.DLHandleSwiftSourceKitClientPlugin.SourceKitDCoreForPlugin→SourceKitD.SourceKitDCoreSwiftSourceKitClientPlugin.SourceKitDCoreForPlugin→SourceKitD.sourcekitd_api_functions_t
- Direction
- SwiftSourceKitClientPlugin uses SourceKitD, so a change to SourceKitD can break SwiftSourceKitClientPlugin, while a change to SwiftSourceKitClientPlugin can't break SourceKitD.
- Position
- Below the diagonal: SwiftSourceKitClientPlugin uses a module listed above it, which is the healthy direction.
26→24 SwiftSourceKitClientPlugin uses BuildServerIntegration✕
- Connections
- 1 pair of types, where a type in SwiftSourceKitClientPlugin uses a type in BuildServerIntegration.
- The types involved
SwiftSourceKitClientPlugin.SourceKitDCoreForPlugin→BuildServerIntegration.URL
- Direction
- SwiftSourceKitClientPlugin uses BuildServerIntegration, so a change to BuildServerIntegration can break SwiftSourceKitClientPlugin, while a change to SwiftSourceKitClientPlugin can't break BuildServerIntegration.
- Position
- Below the diagonal: SwiftSourceKitClientPlugin uses a module listed above it, which is the healthy direction.
27→18 sourcekit-lsp uses SKOptions✕
- Connections
- 3 pairs of types, where a type in sourcekit-lsp uses a type in SKOptions.
- The types involved
sourcekit-lsp.SourceKitLSP→SKOptions.BuildConfigurationsourcekit-lsp.SourceKitLSP→SKOptions.SourceKitLSPOptionssourcekit-lsp.SourceKitLSP→SKOptions.WorkspaceType
- Direction
- sourcekit-lsp uses SKOptions, so a change to SKOptions can break sourcekit-lsp, while a change to sourcekit-lsp can't break SKOptions.
- Position
- Below the diagonal: sourcekit-lsp uses a module listed above it, which is the healthy direction.
27→24 sourcekit-lsp uses BuildServerIntegration✕
- Connections
- 3 pairs of types, where a type in sourcekit-lsp uses a type in BuildServerIntegration.
- The types involved
sourcekit-lsp.PathPrefixMapping→BuildServerIntegration.Stringsourcekit-lsp.SourceKitLSP→BuildServerIntegration.Stringsourcekit-lsp.SourceKitLSP→BuildServerIntegration.URL
- Direction
- sourcekit-lsp uses BuildServerIntegration, so a change to BuildServerIntegration can break sourcekit-lsp, while a change to sourcekit-lsp can't break BuildServerIntegration.
- Position
- Below the diagonal: sourcekit-lsp uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A02:2025 — Security Misconfiguration | 3 | Medium |
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.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 1 No ADRs found finding(s) in ADR Quality. | +5.3 pts | Low | ADR Quality |
| Add a CI workflow that builds and runs the test suite on every push/PR. | +8.1 pts | Medium | CI/CD gates |
| Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them. | +5.0 pts | Medium | Architecture documentation |
| Resolve the 2 Orphaned knowledge finding(s) in Knowledge Freshness — start with SelectionRange.swift, ApplyDeMorganLaw.swift. | +1.7 pts | Low | Knowledge Freshness |
| Extend structured logging to the remaining runnable modules so everything you run is diagnosable in production. | +2.8 pts | Medium | Observability |
| 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 pts | Medium | Deployment & 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 pts | High | Test Quality |
| Resolve the 4 Off-boarding risk finding(s) in Bus Factor. | +0.6 pts | Low | Bus Factor |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| Sources/SwiftLanguageService/SwiftLanguageService.swift | 5.5 | Mixed | God Classes: TooManyMethods: SwiftLanguageService |
| Sources/SemanticIndex/TaskScheduler.swift | 5.6 | Mixed | Cyclomatic Complexity: TaskScheduler.poke (cyclomatic 16) |
| Sources/SwiftSourceKitPlugin/CompletionProvider.swift | 6.0 | Mixed | Explicit Debt: FixmeComment |
| Sources/SwiftSourceKitPlugin/ASTCompletion/ASTCompletionItem.swift | 6.0 | Mixed | Explicit Debt: FixmeComment |
| Sources/SemanticIndex/SemanticIndexManager.swift | 6.0 | Mixed | Explicit Debt: TodoComment |
| Sources/BuildServerIntegration/BuildServerManager.swift | 6.0 | Mixed | Explicit Debt: TodoComment |
| Sources/BuildServerIntegration/SwiftPMBuildServer.swift | 6.0 | Mixed | Explicit Debt: TodoComment |
| Sources/SourceKitLSP/SourceKitLSPServer.swift | 6.0 | Mixed | Explicit Debt: TodoComment |
| Sources/ClangLanguageService/ClangLanguageService.swift | 6.0 | Mixed | Explicit Debt: TodoComment |
| Sources/Diagnose/CommandLineArgumentsReducer.swift | 6.3 | Mixed | Code Duplication: Duplicated block (10 lines × 2) |
| Sources/SwiftSourceKitPlugin/CodeCompletion/Connection.swift | 6.7 | Mixed | Explicit Debt: FixmeComment |
| Sources/SwiftLanguageService/CursorInfo.swift | 6.7 | Mixed | Explicit Debt: TodoComment |
| Sources/CompletionScoring/Semantics/Components/PopularityTable.swift | 6.9 | Mixed | Explicit Debt: TodoComment |
| Sources/SourceKitD/SourceKitD.swift | 7.0 | Mixed | Cognitive Complexity: SourceKitD.send (cognitive 26) |
| Sources/ToolchainRegistry/ToolchainRegistry.swift | 7.0 | Mixed | Cognitive Complexity: ToolchainRegistry.init (cognitive 17) |
| Tests/CompletionScoringTests/PatternTests.swift | 7.0 | Mixed | Test Quality: No assertions: testScoring |
| Sources/CompletionScoring/Text/Pattern.swift | 7.0 | Mixed | Cyclomatic Complexity: Pattern.singleScore (cyclomatic 41) |
| Sources/SwiftLanguageService/CodeCompletionSession.swift | 7.1 | Mixed | Cyclomatic Complexity: CodeCompletionSession.completionsFromSKDResponse (cyclomatic 31) |
| Tests/CompletionScoringTests/BinaryCodingTests.swift | 7.1 | Mixed | Test Quality: No assertions: testIntegers |
| Tests/CompletionScoringTests/CandidateBatchTests.swift | 7.1 | Mixed | Test Quality: No assertions: testPrioritizeUserSymbolsOverSDK |
How the grades work
A definite problem that already costs you something and drags the score down: a missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here tends to cause failures elsewhere.
Likely wrong, but not failing yet. It degrades the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to carry for two years either.
Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.
Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.
Methodology & how to trust this report
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.
What we checked — 52 dimensions across the health lenses
- Can you open the finding? Real findings cite a repo-relative file and line you can open at the cited line — never an absolute scratch path. Here, 553 of 577 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it — Roslyn, git, a scanner, or (for a handful of documentation/naming dimensions) an LLM labelled sampled · advisory — not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Watchdog duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy · checkov | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.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 |
Run transparency — what happened this run
- 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.
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
- 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 Complexity
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.
What to do
- Bring the 5 bodies over 30 down to 30 or less in Cyclomatic Complexity — start with sourcekitd_api_uid_t.init (cyclomatic 56), Pattern.singleScore (cyclomatic 41), 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.
- 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.
D2 · Cognitive Complexity
51 method(s) exceeded the cognitive complexity threshold of 15; the worst was Pattern.singleScore at 97.
What to do
- Bring the 1 body over 60 down to 60 or less in Cognitive Complexity — start with Pattern.singleScore (cognitive 97). — Refactoring it lifts Cognitive Complexity from 6.0 to about 6.5/10.
- 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.
D3 · God Classes
27 god class(es) detected.
What to do
- Resolve the 13 MethodTooLong finding(s) in God Classes — start with SourceKitLSPServer.swift (2), SwiftPMBuildServer.swift (2), CodeCompletionSession.swift. — One of this dimension's main actionable groups (13 warning-level).
- Resolve the 9 FileTooLong finding(s) in God Classes — start with SourceKitLSPServer.swift, BuildServerManager.swift, SwiftLanguageService.swift. — One of this dimension's main actionable groups (9 warning-level).
- Resolve the 4 TooManyMethods finding(s) in God Classes — start with SourceKitLSPServer.swift, SwiftLanguageService.swift, ClangLanguageService.swift. — One of this dimension's main actionable groups (4 warning-level).
- 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.
D4 · Code Duplication
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.
What to do
- Resolve the 5 Duplicated block (6 lines × 2) finding(s) in Code Duplication — start with SkipUnless.swift, SourceKitLSPServer.swift, ReduceCommand.swift. — One of this dimension's main actionable groups (5 warning-level).
- Resolve the 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).
- 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).
- 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.
D5 · Coupling
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).
What to do
- Resolve the 9 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (9 warning-level).
- Resolve the 1 Unstable project ClangLanguageService (CMake) finding(s) in Coupling. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Unstable project SwiftLanguageService (CMake) finding(s) in Coupling. — One of this dimension's main actionable groups (1 warning-level).
- 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.
D6 · Cohesion (LCOM4)
17 of 98 classes have LCOM4 above 3.
What to do
- 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).
- 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.
D9 · Test Distribution
416 test methods: 384 unit, 32 integration, 0 BDD, 0 e2e.
D10 · Test Quality
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).
What to do
- Resolve the 220 No direct assertions finding(s) in Test Quality — start with SelectionRangeTests.swift (110), ConvertStoredPropertyToComputedTests.swift (23), ConvertComputedPropertyToZeroParameterFunctionTests.swift (20). — One of this dimension's main actionable groups (220 recommendation-level).
- Resolve the 53 No assertions finding(s) in Test Quality — start with PatternTests.swift (17), BinaryCodingTests.swift (6), CandidateBatchTests.swift (6). — One of this dimension's main actionable groups (53 warning-level).
- Resolve the 1 Skipped test finding(s) in Test Quality — start with WorkspaceSymbolInfoTests.swift. — One of this dimension's main actionable groups (1 warning-level).
- 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.
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D14 · License Compliance
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`.
D15 · Churn × Complexity Hotspots
Top hotspots: Sources/SourceKitLSP/SourceKitLSPServer.swift (16×62=992); Sources/SwiftLanguageService/CodeCompletionSession.swift (6×31=186); Sources/SourceKitLSP/MessageHandlingDependencyTracker.swift (2×46=92)
What to do
- 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).
D16 · Bus Factor
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.
D17 · Explicit Debt
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.
What to do
- Resolve the 25 TodoComment finding(s) in Explicit Debt — start with SourceKitLSPServer.swift (6), PopularityTable.swift (3), SwiftPMBuildServer.swift (3). — One of this dimension's main actionable groups (25 warning-level).
- Resolve the 14 FixmeComment finding(s) in Explicit Debt — start with ASTCompletionItem.swift (7), CompletionProvider.swift (4), CompletionSession.swift (2). — One of this dimension's main actionable groups (14 warning-level).
- 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.
D20 · ADR Quality
No architecture decision records were found.
What to do
- Resolve the 1 No ADRs found finding(s) in ADR Quality. — One of this dimension's main actionable groups (1 recommendation-level).
D26 · Project Cohesion
1 of 2 build units (SwiftPM) flagged as possibly oversized/incoherent.
What to do
- Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion. — One of this dimension's main actionable groups (1 recommendation-level).
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
semgrep found no security issues. semgrep hit a parse error in 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.
D31 · IaC & Container Security
3 finding(s): 0 critical, 0 high, 0 medium, 3 low.
D34 · Knowledge Freshness
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.
What to do
- Resolve the 2 Orphaned knowledge finding(s) in Knowledge Freshness — start with SelectionRange.swift, ApplyDeMorganLaw.swift. — One of this dimension's main actionable groups (2 issue-level).
- Resolve the 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).
- Resolve the 1 Further orphaned files (smaller) finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
D35 · Change Coupling
Strongest change-coupling: CursorInfo.swift↔SemanticRefactoring.swift 69%; InProcessSourceKitLSPClient.swift↔TestSourceKitLSPClient.swift 69%; JSONCompilationDatabaseBuildServer.swift↔LegacyBuildServer.swift 67%
What to do
- 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).
- 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).
Frontend & cross-cutting dimensions
AX10 · Code composition
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 cycles
AX4 · Dependency direction
AX8 · Test isolation
AX9 · CQS / query purity
M1 · Documentation (README)
What to do
- Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
- Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
- No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
- Add a C4 context/container diagram (Structurizr, PlantUML or Mermaid) or an architecture.md overview.
M3 · Folder & project structure
M4 · Documentation accuracy
P1 · CI/CD gates
- No CI workflow found (.github/workflows, azure-pipelines.yml, .gitlab-ci.yml, …) — changes aren't gated by an automated build/test.
What to do
- Add a CI workflow that builds and runs the test suite on every push/PR.
P2 · Observability
- 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 tooling
- 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 & Rollback
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 hygiene
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 hygiene
X1 · Async correctness
X12 · Unreachable branch
X13 · Undrained process stream
X14 · Bypassable address classification
X15 · Unvalidated length from an untrusted reader
X17 · Uncapped recursion over a caller-supplied document
X19 · Unrestored process-global state
X21 · Side-effecting pattern guard
X22 · Contradicted release guard
X23 · Unguarded diagnostic materialisation
X24 · Document value interpolated into markup unescaped
X25 · Inert configuration knob
X26 · Unsynchronised callback handoff
X27 · Collection changed while being enumerated
X28 · Index access outside its own emptiness guard
X3 · Exception handling
- `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 rejects
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 76% | Strong | Solid. |
| Architecture | 88% | Adequate — gated by D26 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Maturity | 62% | Adequate — gated by M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 31% | Weak — gated by P1, P3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 100% | Exemplary | Strongest area. |
| Performance | 79% | Strong | Solid. |
Unscored — 3 check(s) recorded observations but carry no score
- 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
- 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
- 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)
Critical — 3 finding(s)
- Orphaned knowledge Sources/SwiftLanguageService/SelectionRange.swift:1
- Orphaned knowledge Sources/SwiftSyntaxCodeActions/ApplyDeMorganLaw.swift:1
- Test declared unreliable: testCancellation Tests/SourceKitLSPTests/LifecycleTests.swift:62
Serious — 298 finding(s)
- No assertions: testNoToolchain Tests/BuildServerIntegrationTests/SwiftPMBuildServerTests.swift:147
- No assertions: testIntegers Tests/CompletionScoringTests/BinaryCodingTests.swift:37
- No assertions: testBools Tests/CompletionScoringTests/BinaryCodingTests.swift:70
- No assertions: testStrings Tests/CompletionScoringTests/BinaryCodingTests.swift:74
- No assertions: testArrays Tests/CompletionScoringTests/BinaryCodingTests.swift:80
- No assertions: testDictionaries Tests/CompletionScoringTests/BinaryCodingTests.swift:84
- No assertions: testSemanticClassificationComponents Tests/CompletionScoringTests/BinaryCodingTests.swift:88
- No assertions: testPrioritizeUserSymbolsOverSDK Tests/CompletionScoringTests/CandidateBatchTests.swift:471
- No assertions: test33239581 Tests/CompletionScoringTests/CandidateBatchTests.swift:525
- No assertions: test48642189 Tests/CompletionScoringTests/CandidateBatchTests.swift:534
- No assertions: test30956224 Tests/CompletionScoringTests/CandidateBatchTests.swift:647
- No assertions: test31615625 Tests/CompletionScoringTests/CandidateBatchTests.swift:655
- No assertions: test76104403 Tests/CompletionScoringTests/CandidateBatchTests.swift:679
- No assertions: testSymbolNotoriety Tests/CompletionScoringTests/CompletionScoreTests.swift:123
- No assertions: testTypeReferencePercentages Tests/CompletionScoringTests/CompletionScoreTests.swift:130
- No assertions: testModuleCombinesWithReferenceFrequency Tests/CompletionScoringTests/CompletionScoreTests.swift:137
- No assertions: testMethodReferencePercentages Tests/CompletionScoringTests/CompletionScoreTests.swift:152
- No assertions: testModulePopularity Tests/CompletionScoringTests/CompletionScoreTests.swift:167
- No assertions: testNonMatches Tests/CompletionScoringTests/InfluencingIdentifiersTests.swift:45
- No assertions: testIdentifierPositions Tests/CompletionScoringTests/InfluencingIdentifiersTests.swift:50
- No assertions: testTokenPositions Tests/CompletionScoringTests/InfluencingIdentifiersTests.swift:55
- No assertions: testTokenCoverage Tests/CompletionScoringTests/InfluencingIdentifiersTests.swift:60
- No assertions: testCaseInvariance Tests/CompletionScoringTests/InfluencingIdentifiersTests.swift:68
- No assertions: testInertTerms Tests/CompletionScoringTests/InfluencingIdentifiersTests.swift:73
- No assertions: testScoring Tests/CompletionScoringTests/PatternTests.swift:255
- TodoComment Sources/TSCExtensions/Process+Run.swift:128
- TodoComment Sources/SwiftExtensions/Process+terminate.swift:32
- TodoComment Sources/SwiftLanguageService/CursorInfo.swift:218
- TodoComment Sources/SourceKitLSP/SourceKitLSPServer.swift:2244
- TodoComment Sources/SourceKitLSP/SourceKitLSPServer.swift:2305
- TodoComment Sources/SourceKitLSP/SourceKitLSPServer.swift:2345
- TodoComment Sources/SourceKitLSP/SourceKitLSPServer.swift:2497
- TodoComment Sources/SourceKitLSP/SourceKitLSPServer.swift:2590
- TodoComment Sources/SourceKitLSP/SourceKitLSPServer.swift:2643
- TodoComment Sources/SourceKitD/SKDRequestDictionary.swift:105
- TodoComment Sources/SourceKitD/SKDResponse.swift:76
- TodoComment Sources/SemanticIndex/SemanticIndexManager.swift:356
- TodoComment Sources/SemanticIndex/SemanticIndexManager.swift:990
- TodoComment Sources/Diagnose/StderrStreamConcurrencySafe.swift:19
- TodoComment Sources/CompletionScoring/Text/InfluencingIdentifiers.swift:91
- TodoComment Sources/CompletionScoring/Semantics/Components/Popularity.swift:44
- TodoComment Sources/CompletionScoring/Semantics/Components/PopularityTable.swift:15
- TodoComment Sources/CompletionScoring/Semantics/Components/PopularityTable.swift:150
- TodoComment Sources/CompletionScoring/Semantics/Components/PopularityTable.swift:168
- TodoComment Sources/ClangLanguageService/ClangLanguageService.swift:338
- TodoComment Sources/ClangLanguageService/ClangLanguageService.swift:778
- TodoComment Sources/BuildServerIntegration/BuildServerManager.swift:624
- TodoComment Sources/BuildServerIntegration/SwiftPMBuildServer.swift:431
- TodoComment Sources/BuildServerIntegration/SwiftPMBuildServer.swift:645
- TodoComment Sources/BuildServerIntegration/SwiftPMBuildServer.swift:779
- Low cohesion: SourceKitLSPServer (LCOM4 31) Sources/SourceKitLSP/SourceKitLSPServer.swift:41
- Low cohesion: DocumentationLanguageService (LCOM4 11) Sources/DocumentationLanguageService/DocumentationLanguageService.swift:27
- Low cohesion: String (LCOM4 9) Sources/BuildServerIntegration/CompilationDatabase.swift:207
- Low cohesion: Sequence (LCOM4 9) Sources/SourceKitLSP/SourceKitLSPServer.swift:2903
- Low cohesion: ClangLanguageService (LCOM4 7) Sources/ClangLanguageService/ClangLanguageService.swift:40
- Low cohesion: UncheckedIndex (LCOM4 7) Sources/SemanticIndex/CheckedIndex.swift:339
- Low cohesion: SwiftLanguageService (LCOM4 7) Sources/SwiftLanguageService/SwiftLanguageService.swift:123
- Low cohesion: LegacyBuildServer (LCOM4 6) Sources/BuildServerIntegration/LegacyBuildServer.swift:36
- Low cohesion: Array (LCOM4 6) Sources/Diagnose/CommandLineArgumentsReducer.swift:140
- Low cohesion: Collection (LCOM4 6) Sources/SemanticIndex/TaskScheduler.swift:687
- Low cohesion: SourceKitD (LCOM4 5) Sources/SourceKitD/SourceKitD.swift:105
- Low cohesion: BuildServerManager (LCOM4 4) Sources/BuildServerIntegration/BuildServerManager.swift:392
- Low cohesion: FixedCompilationDatabaseBuildServer (LCOM4 4) Sources/BuildServerIntegration/FixedCompilationDatabaseBuildServer.swift:30
- Low cohesion: TestSourceKitLSPClient (LCOM4 4) Sources/SKTestSupport/TestSourceKitLSPClient.swift:92
- Low cohesion: CapabilityRegistry (LCOM4 4) Sources/SourceKitLSP/CapabilityRegistry.swift:22
- Low cohesion: Connection (LCOM4 4) Sources/SwiftSourceKitPlugin/CodeCompletion/Connection.swift:49
- Low cohesion: ToolchainRegistry (LCOM4 4) Sources/ToolchainRegistry/ToolchainRegistry.swift:30
- FixmeComment Sources/SwiftSourceKitPlugin/CompletionProvider.swift:371
- FixmeComment Sources/SwiftSourceKitPlugin/CompletionProvider.swift:500
- FixmeComment Sources/SwiftSourceKitPlugin/CompletionProvider.swift:503
- FixmeComment Sources/SwiftSourceKitPlugin/CompletionProvider.swift:508
- FixmeComment Sources/SwiftSourceKitPlugin/CodeCompletion/Connection.swift:169
- FixmeComment Sources/SwiftSourceKitPlugin/ASTCompletion/ASTCompletionItem.swift:246
- FixmeComment Sources/SwiftSourceKitPlugin/ASTCompletion/ASTCompletionItem.swift:249
- FixmeComment Sources/SwiftSourceKitPlugin/ASTCompletion/ASTCompletionItem.swift:254
- FixmeComment Sources/SwiftSourceKitPlugin/ASTCompletion/ASTCompletionItem.swift:261
- FixmeComment Sources/SwiftSourceKitPlugin/ASTCompletion/ASTCompletionItem.swift:264
- FixmeComment Sources/SwiftSourceKitPlugin/ASTCompletion/ASTCompletionItem.swift:267
- FixmeComment Sources/SwiftSourceKitPlugin/ASTCompletion/ASTCompletionItem.swift:305
- FixmeComment Sources/SwiftSourceKitPlugin/ASTCompletion/CompletionSession.swift:179
- FixmeComment Sources/SwiftSourceKitPlugin/ASTCompletion/CompletionSession.swift:302
- Swallowed exception (caught, then discarded) Sources/TSCExtensions/Process+Run.swift:85
- Swallowed exception (caught, then discarded) Sources/SwiftSyntaxCodeActions/PackageManifestEdits.swift:70
- Swallowed exception (caught, then discarded) Sources/SwiftSyntaxCodeActions/PackageManifestEdits.swift:122
- Swallowed exception (caught, then discarded) Sources/SwiftSyntaxCodeActions/PackageManifestEdits.swift:176
- Swallowed exception (caught, then discarded) Sources/SwiftSourceKitPluginCommon/CompletionResultsArray.swift:190
- Swallowed exception (caught, then discarded) Sources/SwiftLanguageService/Diagnostic.swift:188
- Swallowed exception (caught, then discarded) Sources/SwiftLanguageService/DiagnosticReportManager.swift:311
- Swallowed exception (caught, then discarded) Sources/SwiftLanguageService/SwiftLanguageService.swift:689
- Swallowed exception (caught, then discarded) Sources/SourceKitLSP/SourceKitLSPServer.swift:208
- Swallowed exception (caught, then discarded) Sources/SKUtilities/Debouncer.swift:68
- Swallowed exception (caught, then discarded) Sources/SKTestSupport/SkipUnless.swift:224
- Swallowed exception (caught, then discarded) Sources/SKTestSupport/SkipUnless.swift:455
- Swallowed exception (caught, then discarded) Sources/LanguageServerProtocolExtensions/WorkDoneProgressManager.swift:112
- Swallowed exception (caught, then discarded) Sources/BuildServerIntegration/SwiftPMBuildServer.swift:176
- MethodTooLong: SourceKitLSPServer.handle Sources/SourceKitLSP/SourceKitLSPServer.swift:596
- MethodTooLong: SwiftPMBuildServer.init Sources/BuildServerIntegration/SwiftPMBuildServer.swift:229
- MethodTooLong: CodeCompletionSession.completionsFromSKDResponse Sources/SwiftLanguageService/CodeCompletionSession.swift:491
- MethodTooLong: SemanticIndexManager.scheduleIndexing Sources/SemanticIndex/SemanticIndexManager.swift:883
- MethodTooLong: SyntaxHighlightingTokenParser.parseKindAndModifiers Sources/SwiftLanguageService/SyntaxHighlightingTokenParser.swift:88
- MethodTooLong: Toolchain.init Sources/ToolchainRegistry/Toolchain.swift:235
- MethodTooLong: SwiftLanguageService.removeUnusedImports Sources/SwiftLanguageService/RemoveUnusedImports.swift:112
- MethodTooLong: Diagnostic.init Sources/SwiftLanguageService/Diagnostic.swift:168
- MethodTooLong: Pattern.singleScore Sources/CompletionScoring/Text/Pattern.swift:452
- MethodTooLong: SourceKitLSPServer.serverCapabilities Sources/SourceKitLSP/SourceKitLSPServer.swift:982
- MethodTooLong: BuildServerManager.init Sources/BuildServerIntegration/BuildServerManager.swift:567
- MethodTooLong: SwiftPMBuildServer.prepare Sources/BuildServerIntegration/SwiftPMBuildServer.swift:791
- MethodTooLong: UpdateIndexStoreTaskDescription.updateIndexStore Sources/SemanticIndex/UpdateIndexStoreTaskDescription.swift:286
- FileTooLong: SourceKitLSP/SourceKitLSPServer.swift Sources/SourceKitLSP/SourceKitLSPServer.swift
- FileTooLong: BuildServerIntegration/BuildServerManager.swift Sources/BuildServerIntegration/BuildServerManager.swift
- FileTooLong: SwiftLanguageService/SwiftLanguageService.swift Sources/SwiftLanguageService/SwiftLanguageService.swift
- FileTooLong: Text/Pattern.swift Sources/CompletionScoring/Text/Pattern.swift
- FileTooLong: BuildServerIntegration/SwiftPMBuildServer.swift Sources/BuildServerIntegration/SwiftPMBuildServer.swift
- FileTooLong: SwiftLanguageService/CodeCompletionSession.swift Sources/SwiftLanguageService/CodeCompletionSession.swift
- FileTooLong: SemanticIndex/SemanticIndexManager.swift Sources/SemanticIndex/SemanticIndexManager.swift
- FileTooLong: SwiftLanguageService/Rename.swift Sources/SwiftLanguageService/Rename.swift
- FileTooLong: SemanticIndex/UpdateIndexStoreTaskDescription.swift Sources/SemanticIndex/UpdateIndexStoreTaskDescription.swift
- Change coupling: InProcessSourceKitLSPClient.swift ↔ TestSourceKitLSPClient.swift Sources/InProcessClient/InProcessSourceKitLSPClient.swift:1
- Change coupling: JSONCompilationDatabaseBuildServer.swift ↔ LegacyBuildServer.swift Sources/BuildServerIntegration/JSONCompilationDatabaseBuildServer.swift:1
- Change coupling: BuildServerManager.swift ↔ CustomBuildServerTestProject.swift Sources/BuildServerIntegration/BuildServerManager.swift:1
- Change coupling: OpenInterface.swift ↔ VariableTypeInfo.swift Sources/SwiftLanguageService/OpenInterface.swift:1
- Change coupling: ClangLanguageService.swift ↔ DocumentationLanguageService.swift Sources/ClangLanguageService/ClangLanguageService.swift:1
- Change coupling: IndexCommand.swift ↔ TestSourceKitLSPClient.swift Sources/Diagnose/IndexCommand.swift:1
- Change coupling: SemanticRefactoring.swift ↔ VariableTypeInfo.swift Sources/SwiftLanguageService/SemanticRefactoring.swift:1
- Change coupling: BuildServerManager.swift ↔ SourceKitIndexDelegate.swift Sources/BuildServerIntegration/BuildServerManager.swift:1
- Change coupling: Package.swift ↔ Plugin.swift Package.swift:1
- Off the main sequence: ClangLanguageService (SwiftPM)
- Off the main sequence: ConfigSchemaGen
- Off the main sequence: DocumentationLanguageService
- Off the main sequence: SwiftExtensions (SwiftPM)
- Off the main sequence: SwiftLanguageService (SwiftPM)
- Off the main sequence: Diagnose (SwiftPM)
- Off the main sequence: SourceKitLSP (SwiftPM)
- Off the main sequence: BuildServerIntegration (SwiftPM)
- Off the main sequence: TSCExtensions (SwiftPM)
- Duplicated block (6 lines × 2) Sources/SKTestSupport/SkipUnless.swift:231
- Duplicated block (6 lines × 2) Sources/SourceKitLSP/SourceKitLSPServer.swift:2566
- Duplicated block (6 lines × 2) Sources/Diagnose/ReduceCommand.swift:65
- Duplicated block (6 lines × 2) Sources/SwiftSyntaxCodeActions/AddDocumentation.swift:101
- Duplicated block (6 lines × 2) Sources/SwiftSyntaxCodeActions/ConvertStoredPropertyToComputed.swift:26
- Duplicated block (5 lines × 2) Sources/BuildServerIntegration/BuildServerManager.swift:1966
- Duplicated block (5 lines × 2) Sources/CompletionScoring/Utilities/SwiftExtensions.swift:239
- Duplicated block (5 lines × 2) Sources/SwiftLanguageService/InlayHintResolve.swift:76
- Duplicated block (5 lines × 2) Sources/SwiftSyntaxCodeActions/ApplyDeMorganLaw.swift:252
- Duplicated block (5 lines × 2) Sources/SwiftSourceKitClientPlugin/ClientPlugin.swift:23
- TooManyMethods: SourceKitLSPServer Sources/SourceKitLSP/SourceKitLSPServer.swift:41
- TooManyMethods: SwiftLanguageService Sources/SwiftLanguageService/SwiftLanguageService.swift:123
- TooManyMethods: ClangLanguageService Sources/ClangLanguageService/ClangLanguageService.swift:40
- TooManyMethods: BuildServerManager Sources/BuildServerIntegration/BuildServerManager.swift:392
- Hotspot: Sources/SourceKitLSP/SourceKitLSPServer.swift Sources/SourceKitLSP/SourceKitLSPServer.swift:596
- Hotspot: Sources/SwiftLanguageService/CodeCompletionSession.swift Sources/SwiftLanguageService/CodeCompletionSession.swift:491
- Hotspot: Sources/SourceKitLSP/MessageHandlingDependencyTracker.swift Sources/SourceKitLSP/MessageHandlingDependencyTracker.swift:165
- Change-coupling hub: CursorInfo.swift → OpenInterface.swift, RelatedIdentifiers.swift, SemanticRefactoring.swift, VariableTypeInfo.swift Sources/SwiftLanguageService/CursorInfo.swift
- Change-coupling hub: RelatedIdentifiers.swift → Rename.swift, SemanticTokens.swift, VariableTypeInfo.swift Sources/SwiftLanguageService/RelatedIdentifiers.swift
- Change-coupling hub: SwiftLanguageService.swift → ClangLanguageService.swift, DocumentationLanguageService.swift, WorkDoneProgressManager.swift Sources/SwiftLanguageService/SwiftLanguageService.swift
- Duplicated block (15 lines × 2) Sources/SKUtilities/LineTable.swift:329
- Duplicated block (15 lines × 2) Sources/SKUtilities/LineTable.swift:435
- Duplicated block (15 lines × 2) Sources/SwiftSyntaxCodeActions/OpaqueParameterToGeneric.swift:182
- Duplicated block (11 lines × 2) Sources/BuildServerIntegration/BuildTargetIdentifierExtensions.swift:76
- Duplicated block (11 lines × 2) Sources/SKUtilities/LineTable.swift:261
- Duplicated block (11 lines × 2) Sources/SwiftLanguageService/SwiftTestingScanner.swift:172
- Duplicated block (9 lines × 2) Sources/ClangLanguageService/SemanticTokenTranslator.swift:50
- Duplicated block (9 lines × 2) Sources/SemanticIndex/TaskScheduler.swift:605
- Duplicated block (9 lines × 2) Sources/SourceKitD/SKDResponseArray.swift:95
- Duplicated block (7 lines × 2) Sources/BuildServerIntegration/SwiftPMBuildServer.swift:902
- Duplicated block (7 lines × 2) Sources/SKUtilities/LineTable.swift:451
- Duplicated block (7 lines × 2) Sources/Diagnose/CommandLineArgumentsReducer.swift:45
- Duplicated block (10 lines × 2) Sources/Diagnose/CommandLineArgumentsReducer.swift:84
- Duplicated block (10 lines × 2) Sources/SKTestSupport/MultiFileTestProject.swift:132
- 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
- PriorityBucket.init (cyclomatic 26) Sources/SwiftSourceKitPlugin/ASTCompletion/ASTCompletionItem.swift:566
- SemanticIndexManager.scheduleIndexing (cyclomatic 25) Sources/SemanticIndex/SemanticIndexManager.swift:883
- UpdateIndexStoreTaskDescription.updateIndexStore (cyclomatic 24) Sources/SemanticIndex/UpdateIndexStoreTaskDescription.swift:286
- BuildServerManager.buildSettingsInferredFromMainFile (cyclomatic 23) Sources/BuildServerIntegration/BuildServerManager.swift:1302
- Pattern.populateMatchingRangesForAcronymMatch (cyclomatic 23) Sources/CompletionScoring/Text/Pattern.swift:271
- Toolchain.init (cyclomatic 23) Sources/ToolchainRegistry/Toolchain.swift:235
- SourceKitLSPServer.rename (cyclomatic 22) Sources/SourceKitLSP/Rename.swift:280
- XMLToMarkdown.toMarkdown (cyclomatic 22) Sources/SwiftLanguageService/CommentXML.swift:77
- SwiftPMBuildServer.prepare (cyclomatic 21) Sources/BuildServerIntegration/SwiftPMBuildServer.swift:791
- SwiftLanguageService.expandMacro (cyclomatic 20) Sources/SwiftLanguageService/MacroExpansion.swift:137
- SwiftLanguageService.removeUnusedImports (cyclomatic 20) Sources/SwiftLanguageService/RemoveUnusedImports.swift:112
- AddExplicitEnumRawValues.textRefactor (cyclomatic 20) Sources/SwiftSyntaxCodeActions/AddExplicitEnumRawValues.swift:48
- SourceKitLSPServer.indexBasedDefinition (cyclomatic 19) Sources/SourceKitLSP/SourceKitLSPServer.swift:1849
- SemanticIndexManager.filesToIndex (cyclomatic 18) Sources/SemanticIndex/SemanticIndexManager.swift:521
- ConvertStringConcatenationToStringInterpolation.refactor (cyclomatic 18) Sources/SwiftSyntaxCodeActions/ConvertStringConcatenationToStringInterpolation.swift:21
- BuildServerManager.init (cyclomatic 17) Sources/BuildServerIntegration/BuildServerManager.swift:567
- JSONSchemaBuilder.buildJSONSchema (cyclomatic 17) SourceKitLSPDevUtils/Sources/ConfigSchemaGen/JSONSchema.swift:106
- SwiftLanguageService.findFunctionLikeRange (cyclomatic 17) Sources/SwiftLanguageService/Rename.swift:502
- SwiftLanguageService.textEdit (cyclomatic 17) Sources/SwiftLanguageService/Rename.swift:798
- build-script-helper.get_swiftpm_options (cyclomatic 17) Utilities/build-script-helper.py:98
- TaskScheduler.poke (cyclomatic 16) Sources/SemanticIndex/TaskScheduler.swift:554
- DiagnosticReportManager.requestReport (cyclomatic 16) Sources/SwiftLanguageService/DiagnosticReportManager.swift:111
- SwiftLanguageService.editsToRename (cyclomatic 16) Sources/SwiftLanguageService/Rename.swift:858
- RequestHandler.handleRequest (cyclomatic 16) Sources/SwiftSourceKitPlugin/Plugin.swift:55
- RemoveRedundantParentheses.canRemoveParentheses (cyclomatic 16) Sources/SwiftSyntaxCodeActions/RemoveRedundantParentheses.swift:72
- Skipped test: testBinarySwiftModuleSymbolsNotIndexed Tests/SourceKitLSPTests/WorkspaceSymbolInfoTests.swift:167
- 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
- Diagnostic.init (cognitive 38) Sources/SwiftLanguageService/Diagnostic.swift:168
- SemanticIndexManager.filesToIndex (cognitive 37) Sources/SemanticIndex/SemanticIndexManager.swift:521
- SemanticIndexManager.scheduleIndexing (cognitive 37) Sources/SemanticIndex/SemanticIndexManager.swift:883
- AddExplicitEnumRawValues.textRefactor (cognitive 37) Sources/SwiftSyntaxCodeActions/AddExplicitEnumRawValues.swift:48
- Pattern.populateMatchingRangesForAcronymMatch (cognitive 36) Sources/CompletionScoring/Text/Pattern.swift:271
- TaskScheduler.poke (cognitive 34) Sources/SemanticIndex/TaskScheduler.swift:554
- UpdateIndexStoreTaskDescription.updateIndexStore (cognitive 33) Sources/SemanticIndex/UpdateIndexStoreTaskDescription.swift:286
- Pattern.bestScore (cognitive 31) Sources/CompletionScoring/Text/Pattern.swift:1007
- OSLogScraper.requestInfo (cognitive 31) Sources/Diagnose/OSLogScraper.swift:44
- SourceKitLSPServer.rename (cognitive 30) Sources/SourceKitLSP/Rename.swift:280
- JSONSchemaBuilder.buildJSONSchema (cognitive 30) SourceKitLSPDevUtils/Sources/ConfigSchemaGen/JSONSchema.swift:106
- SwiftPMBuildServer.buildTargetSources (cognitive 29) Sources/BuildServerIntegration/SwiftPMBuildServer.swift:643
- SourceKitLSPServer.indexBasedDefinition (cognitive 28) Sources/SourceKitLSP/SourceKitLSPServer.swift:1849
- ConvertStringConcatenationToStringInterpolation.refactor (cognitive 27) Sources/SwiftSyntaxCodeActions/ConvertStringConcatenationToStringInterpolation.swift:21
- SourceKitD.send (cognitive 26) Sources/SourceKitD/SourceKitD.swift:330
- Pattern.matchLocation (cognitive 25) Sources/CompletionScoring/Text/Pattern.swift:70
- SourceKitLSPServer.initialize (cognitive 25) Sources/SourceKitLSP/SourceKitLSPServer.swift:846
- SwiftLanguageService.expandMacro (cognitive 25) Sources/SwiftLanguageService/MacroExpansion.swift:137
- RewriteSourceKitPlaceholders.swift.rewriteSourceKitPlaceholders (cognitive 24) Sources/SwiftLanguageService/RewriteSourceKitPlaceholders.swift:23
- SwiftLanguageService.removeUnusedImports (cognitive 22) Sources/SwiftLanguageService/RemoveUnusedImports.swift:112
- ExternalBuildServerAdapter.getConfigPath (cognitive 21) Sources/BuildServerIntegration/ExternalBuildServerAdapter.swift:357
- SourceKitLSPServer.implementation (cognitive 21) Sources/SourceKitLSP/SourceKitLSPServer.swift:2024
- ConvertStringConcatenationToStringInterpolation.preflight (cognitive 21) Sources/SwiftSyntaxCodeActions/ConvertStringConcatenationToStringInterpolation.swift:150
- SourceKitLSPServer.symbolItems (cognitive 20) Sources/SourceKitLSP/WorkspaceSymbols.swift:108
- BuildServerManager.init (cognitive 19) Sources/BuildServerIntegration/BuildServerManager.swift:567
- SwiftPMBuildServer.searchForConfig (cognitive 19) Sources/BuildServerIntegration/SwiftPMBuildServer.swift:156
- SwiftPMBuildServer.loadBuildDescriptionWithRetryOnOutputFileMapWriteErrorOnWindows (cognitive 19) Sources/BuildServerIntegration/SwiftPMBuildServer.swift:427
- RemoveRedundantParentheses.canRemoveParentheses (cognitive 19) Sources/SwiftSyntaxCodeActions/RemoveRedundantParentheses.swift:72
- OutOfProcessSourceKitRequestExecutor.requestResult (cognitive 18) Sources/Diagnose/SourceKitDRequestExecutor.swift:100
- SourceKitLSPServer.subtypes (cognitive 18) Sources/SourceKitLSP/SourceKitLSPServer.swift:2631
- SourceKitLSPServer.members (cognitive 18) Sources/SourceKitLSP/WorkspaceSymbols.swift:628
- Workspace.swift.createIndex (cognitive 18) Sources/SourceKitLSP/Workspace.swift:78
- DiagnosticReportManager.requestReport (cognitive 18) Sources/SwiftLanguageService/DiagnosticReportManager.swift:111
- FoldingRangeFinder.addTrivia (cognitive 18) Sources/SwiftLanguageService/FoldingRange.swift:54
- InlayHintManager.processEdits (cognitive 18) Sources/SwiftLanguageService/InlayHintManager.swift:94
- BuildServerManager.buildSettingsInferredFromMainFile::mainFileAndSettings (cognitive 17) Sources/BuildServerIntegration/BuildServerManager.swift:1328
- CompilerCommandLineOption.matchesIgnoringFrontend (cognitive 17) Sources/BuildServerIntegration/CompilerCommandLineOption.swift:99
- SwiftPMBuildServer.prepare (cognitive 17) Sources/BuildServerIntegration/SwiftPMBuildServer.swift:791
- ToolchainRegistry.init (cognitive 17) Sources/ToolchainRegistry/ToolchainRegistry.swift:168
- build-script-helper.get_swiftpm_options (cognitive 17) Utilities/build-script-helper.py:98
- BuildServerManager.mainFiles (cognitive 16) Sources/BuildServerIntegration/BuildServerManager.swift:1816
- DefinitionLocations.swift.definitionLocations (cognitive 16) Sources/SourceKitLSP/DefinitionLocations.swift:32
- XMLToMarkdown.toMarkdown (cognitive 16) Sources/SwiftLanguageService/CommentXML.swift:77
- PriorityBucket.init (cognitive 16) Sources/SwiftSourceKitPlugin/ASTCompletion/ASTCompletionItem.swift:566
- ConvertIfLetToGuard.statementGuaranteesExit (cognitive 16) Sources/SwiftSyntaxCodeActions/ConvertIfLetToGuard.swift:179
- InlineVariable.nodeToRefactor (cognitive 16) Sources/SwiftSyntaxCodeActions/InlineVariable.swift:27
- ClassTooLong: CodeCompletionSession Sources/SwiftLanguageService/CodeCompletionSession.swift:84
- Members sharing a duplicated core (4 members, 50+ identical tokens) Sources/SourceKitD/sourcekitd_functions.swift:16
- Duplicated block (25–26 lines × 2) Sources/SKUtilities/LineTable.swift:235
- Duplicated block (15–23 lines × 2) Sources/SKOptions/SourceKitLSPOptions.swift:519
- Duplicated block (22 lines × 2) Sources/BuildServerIntegration/BuildServerManager.swift:1995
- Duplicated block (16 lines × 2) Sources/SourceKitLSP/SourceKitLSPServer.swift:2535
- Duplicated block (12–13 lines × 4) Sources/SourceKitD/sourcekitd_functions.swift:16
- Duplicated block (13 lines × 2) Sources/SKTestSupport/PluginPaths.swift:62
- Duplicated block (12 lines × 2) Sources/SwiftLanguageService/CodeCompletionSession.swift:397
- Duplicated block (10 lines × 3) Sources/Diagnose/SourceReducer.swift:442
- Duplicated block (9–10 lines × 2) SourceKitLSPDevUtils/Sources/ConfigSchemaGen/OptionSchema.swift:248
- Duplicated block (8–9 lines × 2) Sources/SemanticIndex/TaskScheduler.swift:582
- Duplicated block (8 lines × 3) Sources/SemanticIndex/TaskScheduler.swift:584
- Duplicated block (8 lines × 2) Sources/SKTestSupport/CheckCoding.swift:67
- Duplicated block (6 lines × 3) Sources/SwiftSyntaxCodeActions/AddExplicitEnumRawValues.swift:150
- Duplicated block (5 lines × 4) Sources/SourceKitD/SKDRequestArray.swift:84
- Unstable project ClangLanguageService (CMake)
- Unstable project SwiftLanguageService (CMake)
- No CI pipeline
Minor — 275 finding(s)
- No direct assertions: testCandidateBatchCreation Tests/CompletionScoringPerfTests/CandidateBatchPerfTests.swift:18
- No direct assertions: testCandidateBatchBulkLoading Tests/CompletionScoringPerfTests/CandidateBatchPerfTests.swift:27
- No direct assertions: testFastConcurrentScoringPerformance Tests/CompletionScoringPerfTests/ScoringPerfTests.swift:65
- No direct assertions: testFullScoringAndSelectionPerformanceWithoutInfluencers Tests/CompletionScoringPerfTests/ScoringPerfTests.swift:69
- No direct assertions: testFullScoringAndSelectionPerformanceWithInfluencers Tests/CompletionScoringPerfTests/ScoringPerfTests.swift:73
- No direct assertions: testFullScoringAndSelectionPerformanceWithInfluencersAndSingleLetterFilter Tests/CompletionScoringPerfTests/ScoringPerfTests.swift:77
- No direct assertions: testFullScoringAndSelectionPerformanceWithoutInfluencersAndSingleLetterFilter Tests/CompletionScoringPerfTests/ScoringPerfTests.swift:81
- No direct assertions: testThoroughConcurrentScoringPerformance Tests/CompletionScoringPerfTests/ScoringPerfTests.swift:152
- No direct assertions: testInfluencingIdentifiersInIsolation Tests/CompletionScoringPerfTests/ScoringPerfTests.swift:195
- No direct assertions: testTokenizingInIsolation Tests/CompletionScoringPerfTests/ScoringPerfTests.swift:208
- No direct assertions: testStringLiteralWithCursorInWord Tests/SourceKitLSPTests/SelectionRangeTests.swift:23
- No direct assertions: testStringLiteralWithCursorInWord2 Tests/SourceKitLSPTests/SelectionRangeTests.swift:36
- No direct assertions: testStringLiteralWithCursorInWord3 Tests/SourceKitLSPTests/SelectionRangeTests.swift:49
- No direct assertions: testStringLiteralWithCursorInWhitespace Tests/SourceKitLSPTests/SelectionRangeTests.swift:62
- No direct assertions: testStringLiteralWithUnicodeChars Tests/SourceKitLSPTests/SelectionRangeTests.swift:75
- No direct assertions: testStringLiteralWithStringInterpolation Tests/SourceKitLSPTests/SelectionRangeTests.swift:84
- No direct assertions: testStringConcatenation Tests/SourceKitLSPTests/SelectionRangeTests.swift:99
- No direct assertions: testNegativeIntegerLiteral Tests/SourceKitLSPTests/SelectionRangeTests.swift:117
- No direct assertions: testFloatLiteral Tests/SourceKitLSPTests/SelectionRangeTests.swift:130
- No direct assertions: testBinaryExpression Tests/SourceKitLSPTests/SelectionRangeTests.swift:139
- No direct assertions: testComplexConditionalExpression Tests/SourceKitLSPTests/SelectionRangeTests.swift:146
- No direct assertions: testSimpleVariableDeclaration Tests/SourceKitLSPTests/SelectionRangeTests.swift:164
- No direct assertions: testMultipleBindingsInSingleDeclaration Tests/SourceKitLSPTests/SelectionRangeTests.swift:176
- No direct assertions: testVariableWithExplicitType Tests/SourceKitLSPTests/SelectionRangeTests.swift:189
- No direct assertions: testLazyVariable Tests/SourceKitLSPTests/SelectionRangeTests.swift:202
- Orphaned file Sources/SwiftSyntaxCodeActions/RemoveRedundantParentheses.swift:1
- Orphaned file Sources/SwiftSyntaxCodeActions/ConvertJSONToCodableStruct.swift:1
- Orphaned file SourceKitLSPDevUtils/Sources/ConfigSchemaGen/OptionSchema.swift:1
- Orphaned file Sources/SwiftSyntaxCodeActions/ConvertStringConcatenationToStringInterpolation.swift:1
- Orphaned file Sources/DocumentationLanguageService/DocCServer.swift:1
- Orphaned file Sources/SwiftSyntaxCodeActions/ConvertIfLetToGuard.swift:1
- Orphaned file Sources/DocumentationLanguageService/DocCCatalogIndexManager.swift:1
- Orphaned file Sources/SwiftSyntaxCodeActions/OpaqueParameterToGeneric.swift:1
- Orphaned file SourceKitLSPDevUtils/Sources/ConfigSchemaGen/JSONSchema.swift:1
- Orphaned file Sources/SwiftSyntaxCodeActions/PackageManifestEdits.swift:1
- Orphaned file Sources/SwiftLanguageService/SignatureHelp.swift:1
- Orphaned file Sources/SwiftLanguageService/RewriteSourceKitPlaceholders.swift:1
- Orphaned file SourceKitLSPDevUtils/Sources/ConfigSchemaGen/ConfigSchemaGen.swift:1
- Orphaned file Sources/DocumentationLanguageService/DocCDocumentationManager.swift:1
- Orphaned file Sources/SourceKitLSP/DefinitionLocations.swift:1
- Orphaned file Sources/SwiftLanguageService/SwiftCodeLensScanner.swift:1
- Orphaned file Sources/SwiftLanguageService/CommentXML.swift:1
- Orphaned file Sources/SKUtilities/LRUCache.swift:1
- Orphaned file Sources/SwiftSyntaxCodeActions/ConvertComputedPropertyToZeroParameterFunction.swift:1
- Orphaned file SourceKitLSPDevUtils/Sources/ConfigSchemaGen/TypeDeclResolver.swift:1
- Orphaned file Sources/SwiftSyntaxCodeActions/ConvertZeroParameterFunctionToComputedProperty.swift:1
- Orphaned file Sources/SwiftLanguageService/SwiftPlaygroundsScanner.swift:1
- Orphaned file Sources/SourceKitLSP/SourceKitLSPCommandMetadata.swift:1
- Orphaned file Sources/SwiftLanguageService/InlayHintResolve.swift:1
- Orphaned file Sources/SwiftSyntaxCodeActions/IndentationRemover.swift:1
- Silent fallback default in catch Sources/SwiftLanguageService/SwiftLanguageService.swift:1511
- Silent fallback default in catch Sources/SwiftSyntaxCodeActions/PackageManifestEdits.swift:70
- Silent fallback default in catch Sources/SwiftSyntaxCodeActions/PackageManifestEdits.swift:122
- Silent fallback default in catch Sources/SwiftSyntaxCodeActions/PackageManifestEdits.swift:176
- Silent fallback default in catch Sources/SwiftSyntaxCodeActions/SyntaxRefactoringCodeActionProvider.swift:83
- Off-boarding risk: anonymized user #1
- Off-boarding risk: anonymized user #2
- Off-boarding risk: anonymized user #3
- Off-boarding risk: anonymized user #4
- REDACTED
- REDACTED
- REDACTED
- Duplicated predicate Sources/SwiftLanguageService/SwiftLanguageService.swift:476
- Duplicated predicate Sources/SwiftSyntaxCodeActions/ConvertCommentToDocComment.swift:52
- Duplicated predicate Sources/SourceKitLSP/SourceKitLSPServer.swift:2076
- Test project verifies nothing: CompletionScoringPerfTests Tests/CompletionScoringPerfTests/CandidateBatchPerfTests.swift:18
- Further sole-owners (lower concentration)
- No ADRs found
- Projects may be oversized for their cohesion
- Further orphaned files (smaller)
- No ADRs
- No architecture diagram/doc
- Logging is not universal
- No SAST
Minor — 1 finding(s)
- Skipped (documented): testToolsets Tests/BuildServerIntegrationTests/SwiftPMBuildServerTests.swift:1267
Appendix B — Reproduction & audit trail
| Dimension | Tool | Version | Command | Findings | Raw output |
|---|---|---|---|---|---|
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-8140090459da4024b9d1db13846a241a/history.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-8140090459da4024b9d1db13846a241a/tree.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-tree.json |
| D29 · Static Analysis (SAST) | semgrep | — | semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/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 . | 0 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | none (dependency manifest found, not scanned for vulnerabilities here) | — | none (dependency manifest found, not scanned for vulnerabilities here): not applicable — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Swift Package.swift/Package.resolved — not scanned yet). | 0 | — |
| D31 · IaC & Container Security | trivy | — | trivy config --format json --quiet . | 3 | artifacts/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 & Signing | provenance | — | provenance: not applicable — No CI/build pipeline found (.github/.forgejo/.gitea workflows, .circleci, .buildkite, .woodpecker, .teamcity, .gitlab-ci.yml, .travis.yml, bitbucket-pipelines.yml, .drone.yml, .cirrus.yml, .woodpecker.yml, appveyor.yml, azure-pipelines*.yml, .pipelines/, .vsts-ci/, .azuredevops/, Jenkinsfile); there is no build to attest provenance for. | 0 | — |
| D37 · Vulnerability-disclosure Policy | disclosure | — | disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | none (dependency manifest found, not scanned for vulnerabilities here) | — | none (dependency manifest found, not scanned for vulnerabilities here): not applicable — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Swift Package.swift/Package.resolved — not scanned yet). | 0 | — |